RU2785151C2 - Information processing method and device - Google Patents

Abstract

FIELD: networks.

SUBSTANCE: invention relates to means for providing expected network information about the behavior of a terminal device. The data analysis network element receives information about the behavior of a terminal device of a plurality of terminal devices. The network element of data analysis determines the expected network information about the behavior of the terminal device based on the information about the behavior of the terminal device. The data analysis network element transmits the expected network information about the behavior of the terminal device to the user data network control element. Since the data analysis network element is an operator-controlled network element, compared with the expected third-party or server tag behavior information service provided by the application function network element in the prior art, the expected tag behavior network information in the present invention has higher reliability. and more realism.

EFFECT: improving the reliability of providing expected network information about the behavior of the end device.

15 cl, 4 tbl, 29 dwg

Description

The technical field to which the invention belongs

Embodiments of the present disclosure relate to the field of communication technologies and, in particular, to an information processing method and device.

State of the art

^5th Generation (5G) communication technologies use Massive Internet of Things (mIoT) end devices. In the prior art, on the 5G network side, a third party network element (e.g., an Application Function (AF) network element) is allowed to provide some expected third party or service server UE behavioral information, and then the 5G network element in a 5G network can use the expected third-party or service server information about the behavior of the end device provided by the AF network element. For example, a 5G network element may store expected network information about the behavior of a tag in a united data management (UDM) network element as part of the tag's subscription information.

However, the process in which the AF NE provides expected third-party or service server information about the behavior of the terminal device in the 5G NE is not mandatory. Therefore, when the AF network element does not provide the expected network information about the behavior of the tag, the network element UDM may not update the mIoT subscription information of the tag. Additionally, for the operator's network, the expected network tag behavior information provided to the AF by the network element has a relatively low reliability.

Disclosure of the essence of the invention

Embodiments of the present disclosure provide a method and apparatus for processing information for providing expected network information about the behavior of a tag with relatively high reliability.

To solve the above technical problem, embodiments of the present disclosure provide the following technical solutions:

According to a first aspect, the present disclosure provides an information processing method, including: obtaining, by a data analysis network element, information about the behavior of a terminal of a plurality of terminals; determining, by the data analysis network element, expected network information about the behavior of the terminal device based on the information about the behavior of the terminal device; and transmitting, by the data analysis network element, expected network information about the behavior of the terminal device to the user data network control element.

This embodiment of the present disclosure provides a method for processing information. The data analysis network element obtains the behavior information of the terminal device of the plurality of terminal devices, determines the expected network information of the behavior of the terminal device based on the behavior information of the terminal device of the plurality of terminal devices, and then transmits the expected network information of the behavior of the terminal device to the user data network control element. Because the data analysis network element is an operator-controlled network element, compared with the expected third-party or service server tag behavior information provided by the application function network element in the prior art, the expected tag behavior network information has higher reliability and is more valid. Additionally, the expected network information about the behavior of the tag provided by the data analysis network element is more complete. Additionally, the expected network tag behavior information provided by the data analysis network element may further be used to check the expected third party or service server tag behavior information provided by the application function network element.

In a possible implementation, obtaining by the data analysis network element information about the behavior of the terminal device of a plurality of terminal devices includes: obtaining by the data analysis network element, from at least two main network elements, information about the behavior of the terminal device, respectively corresponding to at least two main network elements in information about the behavior of the end device. The data analysis network element obtains, from at least two main network elements, information about the behavior of the terminal device, which is related to a plurality of terminal devices and which is located on at least two main network elements, so that the behavior information of the terminal device received network element data analysis, can be more complete.

In an exemplary implementation, the method presented in this embodiment of the present disclosure further includes: transmitting, by the data analysis network element, a first request message to at least two primary network elements, where the first request message requests tag behavior information that corresponds to a set end devices and is located on at least two main network elements. Thus, at least two main network elements are initiated to communicate information about the behavior of the terminal device of the plurality of terminal devices to the data analysis network element.

In an exemplary implementation, the first request message includes filtering information that indicates a tag behavior information collection range for each of the plurality of tags. On the one hand, for at least two basic network elements, it is convenient to define the range of obtaining information about the behavior of the terminal device of each terminal device. On the other hand, the core network element obtains the tag behavior information of each tag based on the filtering information, so that the tag behavior information obtained by the at least two core network elements can satisfy the requirements of the network side.

In an exemplary implementation, the filtering information includes one or more of the following information: tag identification information, network area corresponding to the tag, tag type corresponding to the tag, and time window corresponding to the tag. This further narrows the range of obtaining information about the behavior of the end device, at least two main network elements.

For example, the identification information of a terminal device in this embodiment of the present disclosure may be one or more of the following: an Internet protocol (IP) address, a subscription permanent identifier (SUPI), a permanent equipment identifier, PEI), generic public subscription identifier (GPSI), international mobile subscriber identifier (IMSI), international mobile equipment identity (IMEI), IP address 5-tuple (5 -tuple) and a mobile station international integrated service digital network number (MSISDN). Reference may be made to this description in order to describe the terminal identification information in the following embodiments. Details are not described further.

In an exemplary implementation, the tag behavior information includes tag identification information and one or more of the following information associated with the tag: core network element identification, location information, link start time, link end time, packet delay, number of packets, the packet size and at least one piece of data of the first type of terminal device, which corresponds to the main network element. Therefore, the received information about the behavior of the target device has a wider coverage and is more complete.

In an exemplary implementation, the location information corresponding to the tag includes time and location, and the location information indicates the location of the tag at a specific time.

For example, the location information of the terminal device in this embodiment of the present disclosure may be one or more of the following information: radio access network identifier (RAN ID), cell ID (Cell ID), tracking area (Tracking Area, TA), routing area (Routing Area , RA) and the global positioning system (GPS). Reference may be made herein to this description in order to obtain location information of a terminal device in the following embodiments. Details are not described further.

In a possible implementation, obtaining by the data analysis network element information about the behavior of a terminal device of a plurality of terminal devices includes: obtaining by the data analysis network element from the network element of operation, administration and maintenance information about the behavior of the terminal device, respectively, corresponding to at least two main network elements in information about the behavior of the end device.

In a possible implementation, the expected network information about the behavior of the tag includes one or more of the following information: indication of the stationary state, trajectory of the tag, periodic link indicator, link duration, link period, scheduled link time, maximum packet transmission delay, maximum time packet transmission response, the number of buffered packets, and at least one piece of data of the second type.

In an exemplary implementation, the expected tag behavior network information includes expected tag behavior network information corresponding to at least one group of tags in the plurality of tags.

In an exemplary implementation, the method presented in this embodiment of the present disclosure further includes: transmitting, by the analysis network element, to the user data network element, first tag information corresponding to expected network information about the behavior of the tag, where the first tag information includes: the identification information of the terminals or the identification information of a group of terminals.

In an exemplary implementation, the expected tag behavior network information includes expected tag behavior network information corresponding to at least two core network elements such that after receiving the expected tag behavior network information, the user data network control passes to each core network element. element based on the expected network side tag behavior information corresponding to at least two core network elements, the expected network tag behavior information corresponding to each core network element.

In an exemplary implementation, the method presented in this embodiment of the present disclosure further includes: transmitting, by the analysis network element, at least one of the identification information and type information of at least two basic network elements to the data management network element user. The core network element identification information indicates the core network element corresponding to the expected network behavior information of the tag, and the core network element type information indicates the type of the core network element corresponding to the expected network behavior information of the tag. Thus, the user data control network element defines the main network element to which the expected network information about the behavior of the terminal is transmitted.

In an exemplary implementation, the method presented in this embodiment of the present disclosure further includes: determining, by a data analysis network element, a tag exception type based on expected network information about the behavior of the tag; and transmitting, by the data analysis network element, the alarm information to the policy control function network element, where the alarm information indicates the exception type of the terminal. Thus, the network element of the policy control function determines the exception type of the terminal device, and then takes additional measures, such as shutting down the network used for the failed terminal device.

In an exemplary implementation, the method presented in this embodiment of the present disclosure further includes: receiving, by the data analysis network element, a second request message from the user data network element, wherein the second request message requests expected network information about the behavior of the tag, and the second message request includes identification information of a plurality of terminals. The data analysis network element may obtain expected network information about the behavior of the tag in response to a request from the user data network element.

According to a second aspect, an embodiment of the present disclosure provides a method for transmitting information, including: receiving, by a core network element, a first request message from a data analysis network element that requests tag behavior information corresponding to a plurality of tags; and transmitting, by the core network element, to the analysis network element, based on the first request message, tag behavior information that corresponds to the plurality of tags and that resides in the core network element. The core network element receives the first request message from the data analysis network element and sends to the data analysis network element, upon initiation of the first request message, terminal behavior information that corresponds to the plurality of terminals and resides in the main network element. Thus, the data analysis network element can obtain more complete information about the behavior of the terminal device.

In an exemplary implementation, the first request message includes filtering information that indicates a tag behavior information acquisition range for each of the plurality of tags.

In an exemplary implementation, the filtering information includes one or more of the following information: tag identification information, network area corresponding to the tag, tag type corresponding to the tag, and time window corresponding to the tag.

In an exemplary implementation, the tag behavior information includes tag identification information and one or more of the following information associated with the tag: core network element identification, location information, link start time, link end time, packet delay, number of packets, the packet size and at least one piece of data of the first type of terminal device, which corresponds to the main network element.

In an exemplary implementation, the location information corresponding to the tag includes time and location, and the tag is at that location at the time.

In an exemplary implementation, the core network element may communicate to the data analysis network element using the O&M network element tag behavior information that corresponds to a plurality of terminals and resides in the core network element. In particular, the main network element transmits to the operation, administration and maintenance network element information about the behavior of the terminal device, which corresponds to a plurality of terminal devices and resides on the main network element; and the operation, administration, and maintenance network element is configured to transmit to the data analysis network element information about the behavior of the tag, which corresponds to the plurality of tags, and which resides in the main network element.

According to a third aspect, an embodiment of the present disclosure provides an information processing method, including: receiving, by a user data network element, expected network information about the behavior of a tag from a data analysis network element; and using the user data web control the expected network behavior information of the tag as user subscription data.

This embodiment of the present disclosure provides a method for processing information. The user data network element receives the expected tag behavior network information from the data analysis network element, and stores the expected tag behavior network information as the tag user subscription data. Thus, the reliability of the expected network information about the behavior of the terminal provided by the data analysis network element can be higher.

In an exemplary implementation, the method presented in this embodiment of the present disclosure further includes: transmitting, by the user data network control, a second request message to the data analysis network element, where the second request message requests expected network information about the behavior of the tag, and the second request message includes identification information of a plurality of terminals.

In a possible implementation, the expected network information about the behavior of the tag includes one or more of the following information: indication of the stationary state, trajectory of the tag, periodic link indicator, link duration, link period, scheduled link time, maximum packet transmission delay, maximum time packet transmission response, the number of buffered packets, and at least one piece of data of the second type.

In an exemplary implementation, the expected tag behavior network information includes expected tag behavior network information corresponding to at least one group of tags in the plurality of tags.

In an exemplary implementation, the method presented in this embodiment of the present disclosure further includes: receiving, by the user data network element, first tag information that corresponds to expected network information about the behavior of the tag, from the data analysis network element, where the first tag information includes identification information of terminal devices or identification information of a group of terminal devices.

In an exemplary implementation, the expected tag behavior network information includes expected tag behavior network information corresponding to at least two basic network elements.

In an exemplary implementation, the method presented in this embodiment of the present disclosure further includes: receiving, by the user data network element, at least one of the identification information and type information of at least two basic network elements from the data analysis network element. The core network element identification information indicates the core network element corresponding to the expected network behavior information of the tag, and the core network element type information indicates the type of the core network element corresponding to the expected network behavior information of the tag.

According to a fourth aspect, the present disclosure provides an information processing apparatus. The information processing device may implement the method in accordance with any of the first aspect or possible implementations of the first aspect, and therefore may also obtain beneficial effects in accordance with any of the first aspect or possible implementations of the first aspect. The information processing device may be a data analysis network element or may be a device, such as a chip, applied to the data analysis network element that can support the data analysis network element when implementing the method according to any of the first aspect or possible implementations of the first aspect. The information processing apparatus may implement the above method with software, hardware, or hardware executing the corresponding software.

The information processing apparatus according to the fourth aspect includes: an acquisition unit configured to obtain information about the behavior of a terminal device of a plurality of terminal devices; a determination unit configured to determine expected network behavior information of the terminal device based on the behavior information of the terminal device; and a transmission unit configured to transmit expected network information about the behavior of the terminal device to the user data network control element.

In an exemplary implementation, the acquiring unit is specifically configured to obtain, from at least two base network elements, tag behavior information corresponding to at least two base network elements in the tag behavior information.

In an exemplary implementation, the transmission unit is further configured to transmit a first request message to at least two primary network elements, and the first request message requests tag behavior information that corresponds to the plurality of tags and resides on at least two primary network elements.

In an exemplary implementation, the first request message includes filtering information that indicates a range of tag behavior information for each of the plurality of tags.

In an exemplary implementation, the filtering information includes one or more of the following information: tag identification information, network area corresponding to the tag, tag type corresponding to the tag, and time window corresponding to the tag.

In an exemplary implementation, the tag behavior information includes tag identification information and one or more of the following information associated with the tag: core network element identification, location information, link start time, link end time, packet delay, number of packets, the packet size and at least one piece of data of the first type of terminal device, which corresponds to the main network element.

In an exemplary implementation, the location information corresponding to the tag includes a time period and a location. The location information indicates the specific location of the terminal device in each time period. The location information may be the location of the tag that corresponds to each of the one or more time periods.

In an exemplary implementation, the acquiring unit is specifically configured to obtain from the network element operation, administration, and maintenance information about the behavior of the tag, respectively corresponding to at least two main network elements in the information about the behavior of the tag.

In a possible implementation, the expected network information about the behavior of the tag includes one or more of the following information: indication of the stationary state, the trajectory of the tag, the periodic link indicator, the link duration, the link period, the scheduled link time, the maximum packet transmission delay, the maximum time packet transmission response, the number of buffered packets, and at least one piece of data of the second type.

In an exemplary implementation, the expected tag behavior network information includes expected tag behavior network information corresponding to at least one group of tags in the plurality of tags.

In an exemplary implementation, the transmission unit is further configured to send to the user data network control element first tag information corresponding to expected network information about the behavior of the tag, where the first tag information includes tag identification information or tag group identification information.

In an exemplary implementation, the expected tag behavior network information includes expected tag behavior network information corresponding to at least two basic network elements.

In an exemplary implementation, the transmission unit is further configured to transmit at least one of the identification information and type information of each of the at least two basic network elements to the user data network element. The core network element identification information indicates the core network element corresponding to the expected network behavior information of the tag, and the core network element type information indicates the type of the core network element corresponding to the expected network behavior information of the tag.

In an exemplary implementation, the determiner is further configured to determine the tag exception type based on expected network information about the tag's behavior. The transmission unit is further configured to send the alarm information to the policy control function network element, where the alarm information indicates the exception type of the terminal device.

In an exemplary implementation, the information processing apparatus further includes a receiving unit configured to receive a second request message from the user data network control element, where the second request message requests expected network information about the behavior of the tag, and the second request message includes identification information of a plurality end devices.

In a possible implementation, this embodiment of the present disclosure further provides an information processing device. The information processing device may be a data analysis network element or a chip applied to the data analysis network element. The information processing device includes a processor and a communication interface. The communication interface is configured to support the information processing device while performing the steps of receiving and transmitting a message/data on the side of the information processing device, which are described in any of the first aspect or possible implementations of the first aspect. The processor is configured to support the information processing device while performing the message/data processing steps on the information processing device side as described in any of the first aspect or possible implementations of the first aspect. For the particular step concerned, refer to the descriptions in any of the first aspect or possible implementations of the first aspect. The details are again not described here.

Alternatively, the communication interface and the processor of the information processing device are connected to each other.

Alternatively, the information processing device may further include a memory configured to store code and data. The processor, communication interface and memory are connected to each other.

According to a fifth aspect, the present disclosure provides an information transfer device. The communication device may implement the method in accordance with any of the second aspect or possible implementations of the second aspect, and therefore may also obtain benefits in accordance with any one of the second aspect or possible implementations of the second aspect. The communication device may be a core network element, or may be a device, such as a chip, applied to the core network element that can support the core network element when implementing the method according to any of the second aspect or possible implementations of the second aspect. The communication device may implement the above method with software, hardware, or hardware executing the corresponding software.

An information transmission apparatus according to a fifth aspect of the present disclosure includes a transmission unit configured to transmit, to the data analysis network element, tag behavior information that corresponds to a plurality of tags and resides in the main network element.

In an exemplary implementation, the method presented in this embodiment of the present disclosure further includes a receive unit configured to receive a first request message from the data analysis network element and which requests tag behavior information corresponding to the plurality of tags. The transmission unit is specifically configured to transmit to the data analysis network element, based on the first request message, information about the behavior of the terminal device, which corresponds to the plurality of terminal devices, and which is located in the main network element.

In an exemplary implementation, the first request message includes filtering information used to indicate ranges of tag behavior information.

In an exemplary implementation, the filtering information includes one or more of the following information: tag identification information, network area corresponding to the tag, tag type corresponding to the tag, and time window corresponding to the tag.

In an exemplary implementation, the tag behavior information includes tag identification information and one or more of the following information: core network element identification information, location information, link start time, link end time, packet delay, number of packets, packet size, and, at least one piece of data of the first terminal type, which corresponds to the main network element.

In an exemplary implementation, the location information corresponding to the tag includes time and location, and the tag is at that location in time.

In an exemplary implementation, the transmission unit is specifically configured to communicate to the O&M network element tag behavior information that corresponds to the plurality of tags and resides in the core network element. The operation, administration, and maintenance network element is configured to transmit to the data analysis network element information about the behavior of a terminal device, which corresponds to a plurality of terminal devices, and which is located in the main network element.

In a possible implementation, this embodiment of the present disclosure further provides an information transfer device. The communication device may be a core network element or a chip applied to the core network element. The information transmission device includes a processor and a communication interface. The communication interface is configured to support the information transfer device while performing the steps of receiving and transmitting a message/data on the side of the information transfer device, which are described in any of the second aspect or possible implementations of the second aspect. The processor is configured to support the communication device while performing the message/data processing step on the communication device side, which is described in any of the second aspect or possible implementations of the second aspect. Reference may be made to the description in any of the second aspect or possible implementations of the second aspect for the description of the particular step involved. The details are again not described here.

Alternatively, the communication interface and the processor of the communication device are connected to each other.

Alternatively, the communication device may further include a memory configured to store code and data. The processor, communication interface and memory are connected to each other.

According to a sixth aspect, the present disclosure provides an information processing apparatus. The information processing device may implement the method according to any of the third aspect or possible implementations of the third aspect, and therefore can also obtain beneficial effects according to any one of the third aspect or possible implementations of the third aspect. The information processing device may be a user data network element or may be a device, such as a chip applied to the user data network element, that can support the user data network element when implementing the method according to any of the third aspect or possible implementations of the third aspect. The information processing apparatus may implement the above method with software, hardware, or hardware executing the corresponding software.

The information processing apparatus according to the sixth aspect includes: a transmission unit configured to send, to the data analysis network element, a second request message used to request expected network behavior information of a terminal device, the second request message including identification information of a plurality of terminal devices; and a receiving unit configured to receive expected network information about the behavior of the terminal device from the data analysis network element.

In an exemplary implementation, the expected tag behavior network information includes expected tag behavior network information corresponding to at least one group of tags in the plurality of tags.

In an exemplary implementation, the receiving unit is further configured to receive first tag information that corresponds to expected network information about tag behavior from a data analysis network element, where the first tag information includes tag identification information or tag group identification information.

In a possible implementation, the expected network information about the behavior of the tag includes one or more of the following information: indication of the stationary state, trajectory of the tag, periodic link indicator, link duration, link period, scheduled link time, maximum packet transmission delay, maximum time packet transmission response, the number of buffered packets, and at least one data fragment of the second type.

In an exemplary implementation, the expected tag behavior network information includes expected tag behavior network information corresponding to at least two basic network elements.

In a possible implementation, the receiving unit is further configured to receive at least one of the identification information and the type information of each of the at least two basic network elements from the data analysis network element. The core network element identification information indicates the core network element corresponding to the expected network behavior information of the tag, and the core network element type information indicates the type of the core network element corresponding to the expected network behavior information of the tag.

In a possible implementation, this embodiment of the present disclosure further provides an information processing device. The information processing device may be a user data network element or a chip applied to a user data network element. The information processing device includes a processor and a communication interface. The communication interface is configured to support the information processing device while performing the steps of receiving and transmitting a message/data on the side of the information processing device, which are described in any of the third aspect or possible implementations of the third aspect. The processor is configured to support the information processing device while performing the message/data processing step on the information processing device side, which is described in any of the third aspect or possible implementations of the third aspect. Reference may be made to descriptions of any of the third aspect or possible implementations of the third aspect in order to describe the particular step involved. The details are again not described here.

Alternatively, the communication interface and the processor of the information processing device are connected to each other.

Alternatively, the information processing device may further include a memory configured to store code and data. The processor, communication interface and memory are connected to each other.

According to an eighth aspect, an embodiment of the present disclosure provides a computer-readable storage medium. A computer-readable storage medium stores a computer program or instruction. When a computer program or instruction is run on the computer, the computer is enabled to perform the information transfer method according to any of the second aspect or possible implementations of the second aspect.

According to a ninth aspect, an embodiment of the present disclosure provides a computer-readable storage medium. A computer-readable storage medium stores a computer program or instruction. When a computer program or instruction is run on the computer, the computer is enabled to perform the information processing method in accordance with any of the third aspect or possible implementations of the third aspect.

According to a tenth aspect, the present disclosure provides a computer program product including an instruction. When a computer program product is run on a computer, the computer is enabled to execute one or more of the first aspect and possible implementations of the first aspect.

According to an eleventh aspect, the present disclosure provides a computer program product including an instruction. When a computer program product is executed on a computer, the computer is enabled to execute one or more of the second aspect or possible implementations of the second aspect.

According to a twelfth aspect, the present disclosure provides a computer program product including an instruction. When a computer program product is executed on a computer, the computer is enabled to execute one or more of the third aspect or possible implementations of the third aspect.

According to a thirteenth aspect, the present disclosure provides a chip. The chip includes a processor and an interface circuit. The interface circuit is connected to the processor. The processor is configured to run a computer program or instruction to implement one or more of the first aspect or possible implementations of the first aspect.

According to a fourteenth aspect, the present disclosure provides a chip. The chip includes a processor and an interface circuit. The interface circuit is connected to the processor. The processor is configured to execute a computer program or instruction to implement one or more of the second aspect or possible implementations of the second aspect.

According to a fifteenth aspect, the present disclosure provides a chip. The chip includes a processor and an interface circuit. The interface circuit is connected to the processor. The processor is configured to run a computer program or instruction to implement one or more of the third aspect or possible implementations of the third aspect.

Alternatively, the above-described chip in the present invention may further include at least one memory. At least one memory stores an instruction or a computer program.

According to a sixteenth aspect, an embodiment of the present disclosure provides a communication system. The communication system includes: an information processing device in accordance with the fourth aspect and possible implementations of the fourth aspect, at least two information transmission devices in accordance with the fifth aspect or possible implementations of the fifth aspect, and an information processing device in accordance with the sixth aspect or possible realizations of the sixth aspect.

According to a seventeenth aspect, an embodiment of the present disclosure provides a method for determining tag exclusion information. The method includes: receiving, by a network element, analyzing data from the first network element, indication information used to indicate that a terminal is faulty; obtaining, by the data analysis network element, information about the behavior of the terminal at the second network element based on the indication information; and determining, by the analysis network element, the tag exclusion information based on the behavior information of the tag.

In an exemplary implementation, the method presented in this embodiment of the present disclosure further includes: receiving, by the data analysis network element from the first network element, one or more of the following information corresponding to the tag: tag identification information, network area, tag type, time information and information about the behavior of the terminal device in the first network element.

In an exemplary implementation, the method presented in this embodiment of the present disclosure further includes: obtaining, by the data analysis network element, information about the behavior of a tag on the first network element. Accordingly, the method provided in this embodiment of the present disclosure further includes: obtaining, by the data analysis network element, tag behavior information based on tag behavior information on the first network element and tag behavior information tag device on the second network element .

In particular, the data analysis network element associates information about the behavior of a tag on the first network element with information about the behavior of the tag on the second network element based on the identification information of the tag to obtain information about the behavior of the tag. The data analysis network element determines the tag exclusion information based on the tag behavior information obtained through the association.

In a possible implementation, obtaining by the analysis network element, based on the indication information, information about the behavior of the terminal device, which corresponds to the terminal device and which is located on the second network element, includes: sending the analysis data network element a request message to the second network element, where the request message requests information about the behavior of the terminal device on the second network element; and receiving, by the analysis data network element, a response message from the second network element, where the response message includes information about the behavior of the terminal device in the second network element.

In an exemplary implementation, the request message includes one or more of the following tag-specific information: tag identification information, network area, tag type, and time information.

In a possible implementation, information about the behavior of a tag on the second network element includes tag identification information for the tag and one or more of the following information corresponding to the tag: identification information of the second network element, location information, communication start time, communication end time , packet delay, number of packets, packet size, mobility re-registration frequency information, DNN reachability after failure, number of terminals in geographic area, persistent SUPI subscription identifier persistent equipment identifier PEI association update information, roaming status information and, at least one piece of data of the first terminal type in the second network element.

In an exemplary implementation, the data analysis network element determining tag exception information based on the tag behavior data includes: determining the tag exception information by the data analysis network element based on the tag behavior information and the expected tag behavior network information.

Specifically, determining by the data analysis network element the tag exception information based on the behavior of the tag device includes: determining by the data analysis network element the tag exception information based on the tag behavior information for the tag device and expected network behavior information of the tag device includes: determining, by the data analysis network element, tag exclusion information based on tag behavior information in the first network element, tag behavior information for the tag in the second network element, and expected tag behavior network information.

In an exemplary implementation, the method presented in this embodiment of the present disclosure further includes: obtaining, by the data analysis network element, expected network information about the behavior of the tag from the application function network element.

In an exemplary implementation, the method presented in this embodiment of the present disclosure further includes: obtaining, by the data analysis network element, expected network information about the behavior of the terminal device from the application function network element using the network exposure function network element.

In an exemplary implementation, the tag exception information includes one or more of the following information associated with the tag: identification information, exception type, exception ID, and tag exception level. The exception identifier is used to identify the type of exception, and the exception level indicates the extent or value of the exception type.

In an exemplary implementation, the method presented in this embodiment of the present disclosure further includes: transmitting, by the data analysis network element, tag exclusion information to a third network element, where the exclusion information is used to perform policy control on the tag.

According to an eighteenth aspect, an embodiment of the present disclosure provides a method for determining tag exclusion information. The method includes: determining by the first network element that the terminal device is faulty; transmitting, by the first network element, indication information to the data analysis network element, where the indication information indicates that the terminal device is faulty; receiving, by the analysis data network element, the indication information from the first network element; obtaining, by the data analysis network element, information about the behavior of the terminal at the second network element based on the indication information; and determining, by the analysis network element, the tag exclusion information based on the behavior information of the tag.

In an exemplary implementation, the method presented in this embodiment of the present disclosure further includes: transmitting, by the data analysis network element, tag exception information to a third network element; receiving, by the third network element, exclusion information from the data analysis network element; and executing by the third network element the policy control on the terminal based on the exclusion information.

In an exemplary implementation, the first network element may be any one or more of a session network element, a mobility management network element, a user plane network element, a policy control function network element, or a user data network element. The second network element may be any one or more of a session network element, a mobility management network element, a user plane network element, a policy control function network element, or a user data network element. The first network element and the second network element may be the same network element or may be different network elements.

In an exemplary implementation, the third network element may be an application function network element or a policy management function network element.

In an exemplary implementation, determining by the first network element that a tag is down includes: determining by the first network element that a tag is down based on expected network information about the behavior of the tag on the first network element and information about the behavior of the tag on the first network element.

In a possible implementation, information about the behavior of the tag on the second network element includes identification information of the tag and one or more of the following data corresponding to the tag: identification of the second network element, location information, communication start time, communication end time, packet delay , number of packets, packet size, mobility re-registration frequency information, DNN reachability after failure, number of terminals in geographic area, SUPI-persistent equipment identifier, PEI association update information, roaming status information, and, at least one data fragment of the first terminal type on the second network element.

According to a nineteenth aspect, the present disclosure provides an apparatus for determining tag exception information. The terminal exclusion information determination device may implement the method according to any one of the seventeenth aspect or possible implementations of the seventeenth aspect, and therefore can also obtain the beneficial effects according to any one of the seventeenth aspect or possible implementations of the seventeenth aspect. The apparatus for determining the terminal exclusion information may be a data analysis network element or may be a device, such as a chip, applied to the data analysis network element that can support the data analysis network element when implementing the method according to any one of the seventeenth aspect or possible implementations of the seventeenth aspect. . The apparatus for determining the terminal exclusion information may implement the above method with software.

In an example, a device for determining tag exception information includes: a receiving unit configured to receive from the first network element indication information used to indicate that the tag device is faulty, where the receiving unit is configured to receive information about the behavior of the tag device on the second the network element based on the indication information; and a processing unit configured to determine the exclusion information of the tag based on the behavior information of the tag.

In an exemplary implementation, the receiving unit is further configured to receive from the first network element one or more of the following information corresponding to the tag: tag identification information, network area, tag type, time information, mobility reregistration frequency information, reachability after failure DNN, number of terminals in a geographic area, SUPI-PEI association update information, roaming status information, and terminal behavior information in the first network element.

In a possible implementation, the receiving unit is further configured to receive information about the behavior of the terminal device in the first network element; and the processing unit is further configured to obtain tag behavior information for the tag by associating tag behavior information for the tag on the first network element and tag behavior information for the tag on the second network element.

In an exemplary implementation, the tag exclusion information determination device further includes a transmission unit configured to send a request message to the second network element, where the request message requests information about the behavior of the tag on the second network element. The receiving unit is specifically configured to receive a response message from the second network element, where the response message includes information about the behavior of the terminal device in the second network element.

In an exemplary implementation, the request message includes one or more of the following tag-specific information: tag identification information, network area, tag type, and time information.

In a possible implementation, information about the behavior of the tag on the second network element includes the tag's identifier and one or more of the following information corresponding to the tag: identification information of the second network element, location information, communication start time, communication end time, packet delay, number of packets, packet size, mobility re-registration frequency information, DNN reachability after failure, number of terminals in geographic area, SUPI persistent subscription identifier PEI, association update information, roaming status information and at least at least one piece of data of the first terminal type on the second network element.

In an exemplary implementation, the processing unit is specifically configured to determine tag exclusion information based on tag behavior data and expected network tag behavior information.

In an exemplary implementation, the processing unit is specifically configured to determine the tag exclusion information based on the expected network behavior information of the tag and the tag behavior information for the tag that is obtained by associating the tag behavior information on the first network element and the behavior information end device on the second network element.

In a possible implementation, the receive unit is further configured to receive expected network information about the behavior of the terminal device from the network element of the application function.

In an exemplary implementation, the receiving unit is further configured to obtain expected network information about the behavior of the terminal device from the application function network element by using the network exposure function network element.

In an exemplary implementation, the tag exception information includes one or more of the following information associated with the tag: identification information, exception type, exception ID, and tag exception level. The exception identifier is used to identify the type of exception, and the exception level indicates the extent or value of the exception type.

In a possible implementation, the transmission unit is further configured to transmit terminal exception information to a third network element.

In another example, this embodiment of the present disclosure further provides a device for determining tag exclusion information. The terminal exclusion information determining device may be a data analysis network element or a chip applied to the data analysis network element. The tag exception information determination device includes a processor and a communication interface. The communication interface is configured to support the device for determining tag exception information when performing the steps of receiving and transmitting a message/data on the device side for determining tag exception information, which are described in any of the seventeenth aspect or possible implementations of the seventeenth aspect. The processor is configured to support the information processing device while performing the message/data processing step on the device side to determine tag exception information, which is described in any of the seventeenth aspect or possible implementations of the seventeenth aspect. Reference may be made to the description in any of the seventeenth aspect or possible implementations of the seventeenth aspect for the description of the particular step involved. The details are again not described here.

In an exemplary implementation, a communication interface and a device processor for determining tag exception information are connected to each other.

In an exemplary implementation, a device for determining tag exception information may further include a memory configured to store code and data. The processor, communication interface and memory are connected to each other.

According to a twentieth aspect, the present disclosure provides a communication system. The communication system includes a first network element, a data analysis network element that communicates with the first network element, and a second network element that communicates with the data analysis network element. The first network element is configured to: determine that the terminal device is faulty, and transmit indication information to the data analysis network element, where the indication information indicates that the terminal device is faulty. The data analysis network element is configured to: receive indication information from the first network element and obtain information about the behavior of the terminal device in the second network element based on the indication information. The data analysis network element is further configured to determine tag exclusion information based on tag behavior information.

In an exemplary implementation, the first network element may be any one or more of a session network element, a mobility network element, or a user data network element.

In an exemplary implementation, the communication system further includes a third network element that communicates with the data analysis network element. The data analysis network element is further configured to transmit terminal exclusion information to the third network element. The third network element is configured to: receive exclusion information from the data analysis network element, and perform policy control on the terminal device based on the exclusion information.

In an exemplary implementation, the third network element may be an application function network element or a policy management function network element.

In a possible implementation, that the first network element is configured to determine that the tag is faulty, specifically includes: the first network element is configured to determine that the tag is faulty based on expected network information about the tag's behavior for the tag on the first network element and information about the behavior of the terminal device on the first network element.

In an exemplary implementation, the first network element is further configured to send to the data analysis network element one or more of the following information corresponding to the terminal device: identification information of the terminal device, network area, type of terminal device, time information, and information about the behavior of the terminal device in the first network element.

According to a twenty-first aspect, an embodiment of the present disclosure provides a computer-readable storage medium. A computer-readable storage medium stores a computer program or instruction. When a computer program or instruction is run on the computer, the computer is enabled to execute the method for determining the terminal exception information according to any one of the seventeenth aspect or possible implementations of the seventeenth aspect.

According to a twenty-second aspect, an embodiment of the present disclosure provides a computer-readable storage medium. A computer-readable storage medium stores a computer program or instructions. When the computer program or instructions are run on the computer, the computer is enabled to execute the method of determining the terminal exception information according to any one of the eighteenth aspect or possible implementations of the eighteenth aspect.

According to a twenty-third aspect, the present disclosure provides a computer program product including instructions. When a computer program product is executed on a computer, the computer is enabled to execute one or more of the seventeenth aspect and possible implementations of the seventeenth aspect.

According to a twenty-fourth aspect, the present disclosure provides a computer program product including instructions. When a computer program product is executed on a computer, the computer is enabled to execute one or more of the eighteenth aspect or possible implementations of the eighteenth aspect.

According to a twenty-fifth aspect, the present disclosure provides a chip. The chip includes a processor and an interface circuit. The interface circuit is connected to the processor. The processor is configured to execute a computer program or instructions for implementing one or more of the seventeenth aspect or possible implementations of the seventeenth aspect.

According to a twenty-sixth aspect, the present disclosure provides a chip. The chip includes a processor and an interface circuit. The interface circuit is connected to the processor. The processor is configured to execute a computer program or instructions for implementing one or more of the eighteenth aspect or possible implementations of the eighteenth aspect.

Brief description of the drawings

Fig. 1 is an architectural diagram of a communication system according to an embodiment of the present disclosure;

fig. 2 is an architectural diagram of a 5G network according to an embodiment of the present disclosure;

fig. 3 is a flowchart of an information processing method and an information transmission method according to an embodiment of the present disclosure;

fig. 4 is a flowchart of an information processing method and an information transmission method according to an embodiment of the present disclosure;

fig. 5 is a flowchart of an information processing method according to an embodiment of the present disclosure;

fig. 6 is a flowchart of an information processing method and an information transmission method according to an embodiment of the present disclosure;

fig. 7 is a flowchart of an information processing method and an information transmission method according to an embodiment of the present disclosure;

fig. 8 is a flowchart of an information processing method and an information transmission method according to an embodiment of the present disclosure;

fig. 9 is a flowchart of an information processing method and an information transmission method according to an embodiment of the present disclosure;

fig. 10 is a flowchart of an information processing method according to an embodiment of the present disclosure;

fig. 11A and FIG. 11B are flowcharts of an information processing method according to an embodiment of the present disclosure;

fig. 12A and FIG. 12B are flow charts of an information processing method according to an embodiment of the present disclosure;

fig. 13 is a flowchart of a method for determining tag exception information according to an embodiment of the present disclosure;

fig. 14 is a flowchart of a method for determining tag exclusion information according to an embodiment of the present disclosure;

fig. 15 is a flowchart of a method for determining tag exception information according to an embodiment of the present disclosure;

fig. 16 is a diagram of an information processing apparatus according to an embodiment of the present disclosure;

fig. 17 is a diagram of an information processing apparatus according to an embodiment of the present disclosure;

fig. 18 is a diagram of an information processing apparatus according to an embodiment of the present disclosure;

fig. 19 is a diagram of an information transmission apparatus according to an embodiment of the present disclosure;

fig. 20 is a diagram of an information transmission apparatus according to an embodiment of the present disclosure;

fig. 21 is a diagram of an information transmission apparatus according to an embodiment of the present disclosure;

fig. 22 is a diagram of an information processing apparatus according to an embodiment of the present disclosure;

fig. 23 is a diagram of an information processing apparatus according to an embodiment of the present disclosure;

fig. 24 is a diagram of an information processing apparatus according to an embodiment of the present disclosure;

fig. 25 is a diagram of an apparatus for determining terminal exclusion information according to an embodiment of the present disclosure;

fig. 26 is a diagram of an apparatus for determining terminal exclusion information according to an embodiment of the present disclosure; and

fig. 27 is a circuit diagram of a chip according to an embodiment of the present disclosure.

Implementation of the invention

In order to more clearly state the technical solutions in the embodiments of the present disclosure, the embodiments of the present disclosure use terms such as "first" and "second" to distinguish the same or similar elements that have basically the same function and purpose. For example, the first primary network element and the second primary network element are merely used to distinguish between different primary network elements, and are not intended to limit the sequence of the first primary network element and the second primary network element. One skilled in the art will appreciate that terms such as "first" and "second" do not limit the number or sequence of execution, and that terms such as "first" and "second" do not indicate a particular difference.

It should be noted that in the present invention, words such as "example" or "for example" are used to represent an example, illustration, or description. Any embodiment or scheme described as "example" or "for example" in the present invention should not be explained as being more preferable or having more advantages than another embodiment or scheme. Precisely, the use of words such as "example" or "for example" is intended to represent a related concept in a certain way.

The network architecture and service scenario described in the embodiments of the present disclosure are intended to more clearly describe the technical solutions in the embodiments of the present disclosure and do not represent limitations of the technical solutions presented in the embodiments of the present disclosure. A person skilled in the art may be aware that with the development of network architecture and the advent of new service scenarios, the technical solutions presented in the embodiments of the present disclosure are also applicable to similar technical problems.

In the present invention, "at least one" refers to one or more, and "many" refers to two or more. The term "and/or" describes association relationships for describing related objects and represents that three relationships can exist. For example, A and/or B may represent the following three cases: only A exists, both A and B exist, and only B exists. A and B can be singular or plural. The "/" character usually indicates an "or" relationship between related entities. "At least one of the following elements (fragments)" or an equivalent expression thereof indicates any combination of these elements, including any combination of a single element (fragment) or plural elements (fragments). For example, at least one of a, b, or c may represent a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, and c may be singular or plural.

The technical solutions in the embodiments of the present disclosure may be applied to various communication systems such as a code division multiple access (CDMA) system, a time division multiple access (TDMA) system, a multiple frequency division multiple access (FDMA), orthogonal frequency-division multiple access (OFDMA), single carrier FDMA, SC-FDMA and other system. The terms "system" and "network" can be interchanged. Wireless technologies such as universal terrestrial radio access (UTRA) and CDMA2000 can be implemented in a CDMA system. UTRA may include wideband CDMA (wideband CDMA, WCDMA) and other varieties of CDMA. CDMA2000 can cover the interim standard (IS) 2000 (IS-2000), IS-95 standard and IS-856 standard. Wireless technologies such as the global system for mobile communication (GSM) may be implemented in a TDMA system. Wireless technologies such as evolved universal terrestrial radio access (evolved UTRA, E-UTRA), ultra mobile broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Flash OFDMA may be implemented in an OFDMA system. UTRA corresponds to UMTS and E-UTRA corresponds to an enhanced version of UMTS. A new version of UMTS, namely E-UTRA, is used in 3GPP Long Term Evolution (LTE), and various versions developed based on LTE. The 5G communication system and New Radio (NR) are next-generation communication systems under study. Additionally, communication systems can be further applied to future-oriented communication technology, all of which are applicable to the technical solutions provided in the embodiments of the present disclosure.

The system architecture and service scenario described in the embodiments of the present disclosure are intended to more clearly describe the technical solutions in the embodiments of the present disclosure and do not represent limitations of the technical solutions presented in the embodiments of the present disclosure. A person skilled in the art may be aware that with the development of network architecture and the advent of new service scenarios, the technical solutions presented in the embodiments of the present disclosure are also applicable to similar technical problems. In the embodiments of the present disclosure, an example is used for description in which the provided method is applied to an NR system or a 5G network.

Fig. 1 is an architectural diagram of a communication system to which an information processing method and an information transmission method according to an embodiment of the present disclosure are applied. As shown in FIG. 1, the communication system includes a user data management network element 101, at least two main network elements (Fig. 1 shows only two main network elements, for example, the first main network element 102 and the second main network element 103. It should be understood that there may be more than two basic network elements in an actual process), a data analysis network element 104 and a policy control function (PCF) network element 107 .

In this embodiment of the present disclosure, the at least two core network elements may include one or more core network control plane network elements. For example, at least two core network elements may be a session management function (SMF) network element and an access and mobility management function (AMF) network element.

In an exemplary implementation, one or more of the user data management network element 101 of at least two core network elements, the data analysis network element 104 and the policy management function network element 107 may be virtual network elements, and the network elements may communicate with each other. using a service operation. In another possible implementation, one or more of the user data management network element 101 of at least two core network elements, the data analysis network element 104 and the policy management function network element 107 may be physical network elements, and the network elements are connected to each other via existing standard interface.

In an example, as shown in FIG. 1, the communication system may further include one or more terminals (two terminals are used as an example in FIG. 1, and the two terminals are the first terminal 105 and the second terminal 106). One or more terminal devices are connected to the main network elements in a wired or wireless manner.

In this embodiment of the present disclosure, terminal devices may be widely distributed in a communication network. Each terminal can be fixed or mobile.

The at least two core network elements are configured to provide the data analysis network element 104 with tag behavior information that corresponds to each of the plurality of tags and resides in at least two core network elements.

For example, the first primary network element 102 is configured to provide the data analysis network element 104 with tag behavior information that respectively corresponds to the first tag 105 and the second tag 106 and resides on the first primary network element 102.

The PCF network element 107 is configured to transmit or receive signals or data that is between the PCF network element 107 and the AF network element or the SMF network element, or may be configured to receive a data analysis result, such as a tag exclusion type from the network element data analysis.

For example, if the communication system is applied to a ^4th generation (4G) network, a control plane network element in a 4G network may be a mobility management entity (MME).

For example, if the communication system is applied to a 5G network as shown in FIG. 2, the data analysis network element 104 may be a network data analytics function (NWDAF) network element. Network elements corresponding to at least two main network elements can be any two different network elements in the following set of network elements, for example, 5G network system function network elements (5G System Network Function, 5GS NF). For example, at least two basic network elements may be an SMF network element and an AMF network element. The user data management network element 101 may be any of a unified data management (UDM) network element, a user data repository (UDR) network element, and a home subscriber server (HSS) network element.

For example, the first primary network element 102 is an AMF network element and the second primary network element 103 is an SMF network element.

Additionally, as shown in FIG. 2, the 5G network may further include an application function (AF) network element, a user plane function (UPF), an access device (e.g., an access network (AN)), a server function network element authentication server function (AUSF), network slice selection function (NSSF) network element, network exposure function (NEF) network element, network repository function (NRF) network element, network data network (DN), network element operation, administration and maintenance (operation administrative and maintenance, OAM), etc. This is not specifically limited in this embodiment of the present disclosure.

As shown in FIG. 2, the OAM network element may span the network elements of the access network and the core network, and may collect data from the network elements of the access network and the core network. In addition, the OAM network element in this embodiment of the present disclosure may also obtain tag behavior data that corresponds to the tag and resides on each core network element.

The end device communicates with the AMF NE via the N1 interface (N1 for short). The AMF NE communicates with the SMF NE through an interface N11 (abbreviated as N11). The SMF NE communicates with one or more UPF NEs via an N4 interface (N4 for short). Any two of one or more UPF NEs communicate with each other via an N9 interface (N9 for short). The UPF network element communicates with the data network (DN) via the N6 interface (N6 for short). An end device accesses the network using an access device (eg, a RAN device). The access device communicates with the AMF network element via the N2 interface (N2 for short). The SMF network element communicates with the PCF network element via an N7 interface (N7 for short) and the PCF network element communicates with the AF network element via an N5 interface. The access device communicates with the UPF NE via the N3 interface (N3 for short). Any two or more AMF network elements communicate with each other through an N14 interface (N14 for short). The SMF NE communicates with the UDM NE via an N10 interface (N10 for short). The AMF NE communicates with the AUSF NE through an N12 interface (N12 for short). The AUSF network element communicates with the UDM network element via an N13 interface (N13 for short). The AMF NE communicates with the UDM NE through an N8 interface (N8 for short).

Note that both the 3rd AF NE and the operator AF in FIG. 2 are AF network elements. The differences are that the 3rd AF network element (for example, the WeChat service server or the Alipay payment service server) is not managed or controlled by the operator, the operator AF network element (for example, the proxy-call session control function function, P-CSCF), the network element in the IP multimedia system is managed and controlled by the operator, and that the 3rd AF network element must communicate with the NWDAF network element using the NEF network element.

It should be noted that the names of the interfaces between the various network elements in FIG. 2 are just examples, and interfaces may have different names in specific implementations. This is not specifically limited in this embodiment of the present disclosure.

Note that an access device, an AF network element, an AMF network element, an SMF network element, an AUSF network element, a UDM network element, a UPF network element, a PCF network element, and the like. in fig. 2 are just names and names are not a limitation for devices. In the 5G network and other future network, the network elements corresponding to the access device, AF network element, AMF network element, SMF network element, AUSF network element, UDM network element, UPF network element, and PCF network element may alternatively have other names. This is not specifically limited in this embodiment of the present disclosure. For example, the UDM network element may alternatively be replaced by a home subscriber server (HSS), a user subscription database (USD), a database object, and the like. This is uniformly described in this document. The details are again not described below.

For example, an access device in embodiments of the present disclosure is a device that accesses a core network, such as a base station, a broadband network gateway (BNG), an aggregation switch, or a ^3rd generation partnership project access device. partnership project, 3GPP). The base stations may include base stations in various forms such as a macro base station, a micro base station (also referred to as a small cell), a relay station, and an access point.

For example, the AMF network element in embodiments of the present disclosure may further perform functions such as registration management, mobility management, and lawful interception. This is not specifically limited in this embodiment of the present disclosure.

For example, the SMF network element in embodiments of the present disclosure is configured to perform session management, including session management functions such as session establishment, session change, session release, internet protocol (IP) address. endpoint allocation and management, NE UPF selection and management, and lawful interception.

For example, in addition to the function of the user plane function network element shown in FIG. 2, the UPF network element in the embodiments of the present disclosure may further implement the user plane functions of a serving gateway (SGW) and a packet data network gateway (PGW). Additionally, the UPF network element may alternatively be a software-defined network (software defined network, SDN) switch (switch). This is not specifically limited in this embodiment of the present disclosure.

For example, the AUSF network element in the embodiments of the present disclosure is configured to perform authentication at a terminal device based on subscription data of a user of the terminal device.

For example, the UDM network element in the embodiments of the present disclosure is configured to store user subscription data. Additionally, the UDM network element further has functions such as authentication, user identification, and subscription management. This is not specifically limited in this embodiment of the present disclosure.

For example, the PCF network element in the embodiments of the present disclosure is further used for policy-related functions such as providing a policy rule and supporting a unified policy architecture to control network behavior.

Alternatively, the user plane function network element of FIG. 2 may be implemented by a single device, or may be implemented jointly by multiple devices, or may be a logical functional unit in a device. This is not specifically limited in the embodiments of the present disclosure.

The network element SMF is configured to re-allocate the network element UPF to the terminal device based on the location information of the terminal device, the indication of data from the terminal device, the location information between the network element UPF and the terminal device, or the quality of service of the network element UPF to re-establish a session between the terminal device and by a newly dedicated UPF network element to optimize the user plane, thereby improving the quality of the user experience of the re-established session.

The access device is configured to provide data services to the terminal device, for example, to receive data from the terminal device or to transmit data to the terminal device. In actual use, the access device may be a base station. In embodiments of the present disclosure, a base station (BS) may be a device that communicates with a user equipment (UE) or other communication station such as a relay station, and the base station may provide a communication coverage area in a particular physical areas.

The network element PCF is configured to: receive service information from the network element AF, generate and distribute, based on the service information, QoS parameters corresponding to the service flow, and may further be configured to: receive the data analysis result from the network element NWDAF and take appropriate action on based on the result of the data analysis, for example, accept the NE exception type from the NWDAF, and shutdown the network with one click to disable the service of the tag.

The AF network element may be configured to provide expected 3rd party or server side service information about the behavior of the tag to the UDM network element. In particular, the AF network element initiates an Nef_ParameterProvision_Update NEF request service operation to the network element to provide expected third-party or server-side service information about the behavior of the tag of each of the one or more NEF tags to the network element. The request service operation Nnef_ParameterProvision_Update passes the identification information of the target device and the ID of the reference transaction. The reference transaction ID is used to identify an interaction request between the AF network element and the NEF network element.

The NEF network element first determines whether the request service operation Nnef_ParameterProvision_Update from the network element AF is valid. When the NEF network element determines that the Nnef_ParameterProvision_Update request service operation is valid, the NEF network element sends the Nudm_ParameterProvision_Update request service operation to the UDM network element to provide the UDM network element with expected 3rd party or server side service information about the tag behavior of each of the one or more tags from AF network element. The request service operation Nudm_ParameterProvision_Update further comprises an NEF reference ID to identify a request for communication between the NEF network element and the UDM network element.

The network element UDM first performs authentication to determine if the network element's AF request is valid. If the network element's AF request is valid, the UDM network element first maps the tag's identity (e.g., maps the tag's identity from GPSI to SUPI), uses the expected 3rd party or server-side service tag behavior information of each of the one or more tags from the NE AF as a fragment of the user subscription data of each end device, and initiates a Nudr_DM_Update request service operation on the network element UDR to request the UDR network element to update and store expected third-party or server-side service information about the behavior of the end device of each of the one or more end devices. devices that come from the NE AF. The network element UDR parses the GPSI or maps the GPSI to the SUPI and stores the expected third-party or server-side service information about the behavior of the end device, each of one or more end devices from the network element AF, as the corresponding user subscription data for each one or more end devices . The UDR NE then initiates a Nudm_DM_Update response service operation for the UDM. If the NE UDR is unable to parse the GPSI or map the GPSI to the SUPI, the Nudm_DM_Update response service operation indicates to the UDM that tag behavior data cannot be provided and contains a reason value.

If the network element's UDM determines that the network element's AF request is invalid, the network element's UDM initiates a Nudm_ParameterProvision_Update response service operation on the network element's NEF, and the Nudm_ParameterProvision_Update response service operation indicates that the expected third-party or server-side service information about the behavior of the tag cannot be provided and contains the reason value.

When the NEF network element determines that the Nnef_ParameterProvision_Update request service operation is invalid, the NEF network element initiates a Nnef_ParameterProvision_Update response service operation to the network element AF and the Nnef_ParameterProvision_Update response service operation indicates that the tag behavior data cannot be provided and contains the cause value.

DN is an external network that provides data service.

The NWDAF network element is configured to receive information about the behavior of the terminal device, which corresponds to the terminal device and which is located on different main network elements. The tag behavior information may include tag identification information and tag behavior information. Then, the tag behavior information that corresponds to the tag and that resides on the various core network elements is associated with the identification information of the tag to obtain tag behavior information corresponding to the tag. The tag behavior information includes at least tag behavior information that corresponds to the tag and resides on various core network elements. Additionally, the NWDAF network element is further configured to: parse tag behavior information corresponding to a plurality of tag devices to obtain expected network tag behavior information; and transmit expected network information about the behavior of the terminal device to the user data network control element. When the expected tag behavior network information includes expected tag behavior network information corresponding to at least two basic network elements, the NWDAF network element is further configured to transmit identification information or type information of each of the at least , the two main network elements into the user data network element.

Alternatively, the data analysis network element may obtain from the network element AF the expected 3rd party or service server side behavior information of the tag, and then may check the expected 3rd party or service server side tag behavior information using the expected network tag behavior information. device resulting from the analysis. When it is detected that the expected third-party or server-side service tag behavior information is inconsistent with the network-side expected tag behavior information, the data analysis network element may update the expected network tag behavior information for the expected third-party or server-side service information. about the behavior of the tag, then transmit the updated expected third-party or server-side service information about the behavior of the tag (namely, the expected network information about the behavior of the tag, which is obtained by the data analysis network element through analysis) to the user data network element, so that the user data network control element stores the information as subscription data of the terminal. Alternatively, the data analysis network element may signal to the user data network element that the expected third-party or server-side service information about the behavior of the terminal is unreliable.

Alternatively, the data analysis network element cannot obtain the expected third-party or server-side service information about the behavior of the terminal device from the network element AF. After the data analysis network element passes the expected network tag behavior information to the user data network element, the user data network element can check the expected 3rd party or service server side tag behavior information that is obtained from the network element AF. When the user data network element detects that the expected third-party or server-side service tag behavior information is inconsistent with the expected tag network behavior information, the user data network element may update the expected tag network behavior information to the expected third-party or tag behavior information service server side, and store the updated expected 3rd party or service server side tag behavior information (namely, the expected tag behavior network information obtained by the analysis network element through analysis) as subscription data of the tag device.

It should be noted that, in addition to the main network element, the data analysis network element may additionally obtain information about the behavior of the terminal device from the network element of the radio access network (Radio Access Network, RAN), OAM network element or other server. The data analysis network element is configured to obtain expected network information about the behavior of the terminal device by analyzing information about the behavior of the terminal device.

As shown in Table 1, Table 1 shows information related to terminal behavior data that an NWDAF network element receives from a 5GC NF or a Radio Access Network (RAN).

Table 1 Terminal Behavior Data

Data type Name of the network element that owns the data on the behavior of the end device Function Terminal identification information AMF NE/SMF NE/RAN NE Terminal identification Location Information > Time (Timestamp) AMF NE /RAN NE Terminal time > Location AMF NE /RAN NE The location of the terminal device at the relevant point in time Communication Pattern Information > Communication Start Time SMF NE/UPF NE Start time of communication between end device and SMF NE > Communication End Time SMF NE/UPF NE End time of communication between end device and SMF NE > Registration Time AMF network element The time at which the end device registers with the AMF network device > Deregistration Time AMF network element The time at which the end device is deregistered by the AMF network device > Session Establishment Time PDU SMF NE The time at which the end device establishes a session PDU > Session Modification Time (PDU Session Modification Time) SMF NE Time at which endpoint session PDU changes > Session Release Time (PDU Session Release Time) SMF NE Time at which session PDU is released Network configuration information > (Uplink or Downlink) Packet Delay (UL or DL Packet Delay) SMF NE/UPF NE/RAN NE Indication of the end-to-end delay (server-server-or-DN) of an uplink or downlink packet > (Uplink or Downlink) Packet Size (UL or DL Packet Size) SMF NE/UPF NE/RAN NE Uplink Buffered Packet Size Indication or Downlink Buffered Packet Size > > (uplink or downlink) number of packets (UL or DL Packet Number) SMF NE/UPF NE/RAN NE Indicate the number of buffered uplink packet or the size of the buffered downlink packet > > (Uplink or Downlink) Packet Transfer Start Time SMF NE/UPF NE/RAN NE Specifying the time at which the uplink packet or downlink packet should be transmitted > > (Uplink or Downlink) Packet Transfer End Time SMF NE/UPF NE/RAN NE Specifying the time at which the transmission of an uplink packet or a downlink packet is to be completed > RRC Connection Establishment Time AMF NE/RAN NE Specifying the time at which a Radio Resource Control (RRC) connection should be established > RRC Connection Release Time AMF NE/RAN NE Specifying the time at which the RRC connection should be released At least one piece of data of the first type on the AMF network element (normalized UE behavioral data from AMF) AMF network element Other data about the behavior of the end device on the AMF network element At least one piece of data of the first type on the SMF network element (normalized UE behavioral data from SMF) SMF NE Other data about the behavior of the end device on the SMF network element At least one piece of data of the first type on the UPF network element (normalized UE behavioral data from UPF) UPF network element Other data about the behavior of the end device on the UPF NE At least one data fragment of the first type on the RAN network element (normalized UE behavioral data from RAN) RAN network element Other data about the behavior of the end device on the RAN network element

At least one piece of first type tag behavior data in the AMF network element, SMF network element, UPF network element, and RAN network element is tag behavioral data that can be identified or used by the AMF network element or the SMF network element. Alternatively, each piece of data of the first type may be obtained after normalization processing. Normalization processing generally refers to mapping the physical data value of each data type to a fixed number space using a maximum-minimum normalization method, a Z-score normalization method, or the like. This processing increases the speed of model preparation convergence in the big data analysis process, on the one hand, and provides a sign of data transfer, on the other hand.

For example, the identification information of a terminal device in embodiments of the present disclosure may be one or more of the following: an Internet protocol (IP) address, a subscription permanent identifier (SUPI), a permanent equipment identifier (PEI). ), generic public subscription identifier (GPSI), international mobile subscriber identifier (IMSI), international mobile equipment identity (IMEI), IP address 5-tuple (5- tuple) and the international integrated service digital network number (MSISDN). The description of the terminal identification information in the following embodiments can be understood from this description. Details are not described further.

As shown in Table 2, Table 2 shows the associated contents of the expected network behavior information of the tag in this embodiment of the present disclosure.

Table 2 Expected network information about the behavior of the end device

Data type NE name Function Terminal identification information AMF NE or SMF NE Terminal identification MM information Mobility management information (MM) > Stationary indication AMF network element Specifying whether the terminal is fixed or mobile > UE moving trajectory Indication of the trajectory of the physical movement of the end device, which is expected by a third party At least one piece of data of the second type on the AMF network element (normalized expected UE behavioral data from AMF) Other expected network information about the behavior of the terminal device on the AMF network element SM information SMF NE Session management information (SM) > Periodic communication indicator SMF NE Specifying that endpoint service data is transmitted periodically > Communication duration SMF NE Endpoint service data transfer duration, e.g. five minutes > Communication period (periodic time) Terminal service data transmission period, e.g. every hour > Scheduled communication time Transmission time range of the terminal service, such as a specific day in each week, e.g. 13:00 - 20:00 on Monday > Maximum packet transmission delay (maximum latency) Indication of the maximum downlink packet transmission delay that is acceptable by the third party > Maximum response time for packet transmission (maximum response time) An indication of the reachable time for a terminal that allows a third party to complete downlink data transmission > Suggested number of downlink packets Indicating to the UPF NE the number of packets that the UPF NE needs to buffer when the end device is unreachable > At least one piece of data of the second type on the SMF network element (normalized expected UE behavioral data from SMF) Other expected network information about the behavior of the terminal device on the SMF network element

At least one piece of data of the second type, namely, the expected network information about the behavior of the terminal device on the AMF network element (SMF network element) represents the expected network information about the behavior of the terminal device, which can be identified or used by the AMF network element (SMF network element).

Alternatively, after normalization processing, each piece of at least one piece of data of the second type can be obtained. The normalization processing may refer to mapping the physical data value of each data type to a fixed number space using a maximum-minimum normalization method, a Z-score normalization method, or the like. This processing increases the rate of convergence of the training model in the big data analysis process, on the one hand, and provides a sign of data transfer, on the other hand.

In this embodiment of the present disclosure, the first type and the second type may be the same or may be different. Specifically, the first type is any type of tag behavior data obtained by the data analysis network element from the main network element, NE RAN or terminal device, and the second type is a data type obtained after analysis by the data analysis network element of the behavior data. end device received from the core network element, NE RAN or end device.

Alternatively, a terminal in the present invention may also be referred to as a terminal, user equipment (UE), access terminal, user equipment, subscriber station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user device. The terminal device can be a station (STA) in a wireless local area network (WLAN) or can be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local area network (wireless local loop (WLL), personal digital assistant (PDA), handheld device with wireless capability, computing device or other data processing device connected to a wireless modem, vehicle-mounted device, wearable device, and terminal device in a next generation communication system, for example, a fifth-generation (5G) communication network or a terminal device in a future developed public land mobile network (PLMN).

For example, in embodiments of the present disclosure, the tag may alternatively be a wearable device. A wearable device can also be referred to as a wearable smart device, and is a general term for wearable devices such as glasses, gloves, watches, clothing, and shoes that are developed by applying wearable technology to smart casual wear devices. A wearable device is a portable device that can be worn directly on the body or integrated into the wearer's clothing or accessory. A wearable device is not just a hardware device, it further realizes powerful functions through software support, data sharing, and cloud interaction. Generalized wearable smart devices include full-function and large-sized devices that can realize full or partial functions independently of smartphones, such as smart watches or smart glasses, and also include devices that focus on only one type of application function and must work with other devices such as smartphones, such as various smart bracelets or smart jewelry to track physical signs.

It can be understood that in embodiments of the present disclosure, the information processing method may be performed by the data analysis network element, or may be performed by a device (eg, a chip) applied to the data analysis network element. The information transfer method may be performed by the network element, or may be performed by a device (eg, a chip) applied to the network element. Another way of processing the information may be performed by the user data network element, or may be performed by a device (eg, a chip) applied to the user data network element. In the following embodiments, an example is used in which the information processing method is performed by the data analysis network element, the information transmission method is performed by the main network element, and the other information processing method is performed by the user data control network element.

Embodiment 1

Fig. 3 is a flowchart of an information processing method and an information transmission method according to an embodiment of the present disclosure. The method includes the following steps.

S101: The data analysis network element acquires terminal behavior information of the plurality of terminals.

The tag behavior information for the plurality of tags may include tag behavior information for each of the plurality of tags.

For example, the tag behavior information for the tag includes tag identification information and tag behavior data corresponding to the tag associated with the tag identification information.

In particular, for tag behavior data, refer to the descriptions in Table 1, such as tag location information, link start time, link end time, packet delay, packet size, and number of packets. The details are again not described here.

In the example shown in FIG. 4, S101 can be specifically implemented as follows:

S1011: The data analysis network element obtains, from at least two main network elements, tag behavior information corresponding to at least two main network elements in the tag behavior information.

Specifically, the data analysis network element obtains tag behavior information (including identification information and tag behavior data of each tag) that corresponds to each of the plurality of tags and resides on each of the at least two main network elements. The data analytics network element then associates the tag behavior data of each tag with all major network elements based on the identity of the tag to obtain tag behavior information corresponding to the tag. The tag behavior information corresponding to the tag includes at least tag identification information and tag behavior information that corresponds to the tag and resides on each of the at least two core network elements.

For example, at least two basic network elements are an AMF network element and an SMF network element. According to Table 1, the data analysis network element can obtain from the AMF of the network element information about the behavior 1 of the terminal device, which corresponds to the terminal device 1 and which is located in the AMF network element. The behavior information of the terminal device 1 includes identification information of the terminal device 1 and location information (including time and location) of the terminal device 1 in the AMF network element. The data analysis network element can further obtain information about the behavior of the terminal device 2 of the terminal device 1 in the SMF network element from the network element SMF. The tag behavior information 2 includes identification information of the tag 1, communication pattern information (communication start time and communication end time) of the tag 1 in the SMF network element, and network configuration information (uplink or downlink delay and packet size). and the number of uplink or downlink packets). Then, the data analysis network element associates the behavior information 1 of the terminal device 1 in the AMF network element with the behavior information 2 of the terminal device 1 of the network element SMF, using the identification information of the terminal device 1 to obtain the behavior information of the terminal device corresponding to the terminal device 1.

It should be noted that in this embodiment of the present disclosure, tag behavior data that corresponds to the same tag and that resides on different core network elements may be the same or may be different.

It should be noted that, in this embodiment of the present disclosure, the data analysis network element may alternatively obtain, from the terminal, the radio access network element, and the application function network element, terminal device behavior information that corresponds to the terminal and, that is, is respectively located at the terminal. device, a radio access network element, and an application function network element.

In a real process, if the data analysis network element detects that the terminal behavior information of some types of terminal devices, in some areas of the network or at some time periods needs to be reported and analyzed, the data analysis network element can provide each core network element with a requirement to analyze the above information about the behavior of the tag, so that each main network element receives from the main network element information about the behavior of the terminal device corresponding to the terminal device. In another possible embodiment of the present disclosure, as shown in FIG. 4, the method presented in this embodiment of the present disclosure further includes the following steps.

S1012: The data analysis network element transmits a first request message to each of at least two main network elements (the first main network element and the second main network element are used as an example in Fig. 4), where the first request message requests information about the behavior of the terminal device that corresponds to a plurality of terminal devices and that resides on the core network element.

Alternatively, the first request message contains filtering information, and the filtering information indicates a range of tag behavior information of each of the plurality of tags.

For example, the filtering information includes one or more of the following information: tag identification information, network area corresponding to the tag device, tag type corresponding to the tag device, and time window corresponding to the tag device. For example, the filtering information includes a network area and a tag type that correspond to each tag.

The time window is used by the core network element to determine to receive information about the behavior of the terminal device in a given period of time. For example, the time window is from March 1, 2018 to March 8, 2018. In this case, the core network element may determine to obtain that terminal behavior information that corresponds to the terminal device and which has been in the core network element since March 1, 2018. to March 8, 2018.

The network area is used by the core network element to determine to obtain information about the behavior of a terminal device in a particular area (eg, tracking area (TA), TA list, routing area (RA) or RA list).

For example, when the filtering information includes the tag identification information, the network area, and the tag type, the filtering information is used to direct the core network element to obtain information about the behavior of the tag device in the specified network area or belongs to the specified tag type specified in the identification information. terminal device.

For example, when the filtering information includes the tag identification information, the network region, and the time window, the filtering information is used to direct the core network element to obtain information about the behavior of the tag device in the specified network region or in the specified time window indicated by the tag identification information.

S1013: At least two primary network elements receive the first request message.

It can be understood that in step S1013, each of the at least two main network elements receives the first request message.

S1014: At least two core network elements send to the data analysis network element, based on the first request message, tag behavior information that corresponds to the plurality of tags and that resides on the respective core network elements.

Specifically, each of the at least two core network elements may send a response message to the first request message to the data analysis network element, and the response message contains tag behavior information that corresponds to the plurality of tags and that resides on the respective core network elements. elements.

In particular, the main network element transmits to the data analysis network element information about the behavior of a terminal device of at least one of the plurality of terminal devices on the main network element.

Using the example in which the main network element is an AMF network element, the AMF network element transmits to the analysis network element information about the behavior of the terminal device of at least one terminal device in the AMF network element.

The tag behavior information includes tag identification information and one or more of the following information corresponding to the tag: core network element identification information, location information, link start time, link end time, packet delay, number of packets, packet size, and , at least one piece of data of the first type of terminal device, which corresponds to the main network element.

It should be noted that the title (eg, tag behavior information) of the information obtained by the data analysis network element at S101 in this embodiment of the present disclosure is merely an example. In a particular implementation, the name of the tag behavior information may be another name, such as user behavior information, behavior information, or tag information. This is not specifically limited in this embodiment of the present disclosure. In this embodiment of the present disclosure, a person skilled in the art can understand that in a real process, if one piece of information includes the identification information of a terminal device and one or more of the above data corresponding to a terminal device, then the piece of information can be understood as behavior information terminal device.

The terminal device behavior information that is transmitted by one main network element that corresponds to the plurality of terminal devices and which resides on the main network element includes: identification information of the plurality of terminal devices and terminal device behavior data corresponding to each of the plurality of terminal devices. In particular, see the description in Table 1 for endpoint behavior.

Since the behavioral data of the terminal device transmitted by the various core network elements to the data analysis network element is different, descriptions are given separately below.

Using an example in which the main network element is an AMF network element, the tag behavior information reported to the AMF by the network element includes: tag identification information and location information (including time and location).

Using the example in which the underlying network element is an SMF network element, the tag behavior information reported to the SMF by the network element includes one or more of the following data: communication start time, communication end time, packet delay, number of packets, and packet size. .

Alternatively, S1014 can be implemented as follows: each main network element sends to the operation, administration and maintenance network element, based on the first request message, terminal behavior information that corresponds to the plurality of terminals and which resides on the main network element; and the O&M network element transmits to the data analysis network element the behavioral information of the tag that corresponds to the plurality of tags and that resides on each core network element.

In another example, S101 in this embodiment of the present disclosure may alternatively be implemented as follows: the data analysis network element receives from the operation, administration and maintenance network element information about the behavior of the terminal device that corresponds to each of the plurality of terminal devices, and this, according to at least two main network elements.

In particular, the data analysis network element transmits the first request message to the operation, administration and maintenance network element, and the operation, administration and maintenance network element transmits to the data analysis network element, based on the first request message, information about the behavior of the terminal device, which corresponds to each of the plurality of terminal devices and resides on at least two main network elements.

Terminal behavior information that is provided by the Operations, Administration and Maintenance Network Element for the Data Analysis Network Element, which corresponds to each terminal and which resides on at least two main network elements, may already be stored in the Operations Network Element, administration and maintenance, or may be requested by the operation, administration and maintenance network element of at least two main network elements after receiving the first request message. Specifically, for a process in which the operation, administration, and maintenance network element requests information about the behavior of a terminal device from at least two main network elements, refer to the process in steps S1012 to S1014, provided that the data analysis network element is replaced network element of operation, administration and maintenance.

S102: The data analysis network element determines the expected network behavior information of the tag based on the behavior information of the tag.

In particular, the data analysis network element determines the expected network information about the behavior of the terminal device based on the information about the behavior of the terminal device of each of the plurality of terminal devices.

For example, S102 may be implemented using the following process:

Process 1. The data analysis network element uses the tag behavior data contained in the received tag behavior information (which may be referred to as training data) of each of the plurality of tags as one piece of sample data, and represents each piece of sample data as a vector (x _i1 , ..., x _y , ..., x _iN ), where i=1,2, ..., N, N indicates the number of sample data pieces or can be understood as the number of terminals, and N is an integer greater than or equal to 1; x _y indicates terminal behavior information provided by any of the at least two basic network elements; and specifies the size of each piece of sample data.

Process 2: The data analysis network element groups the terminals corresponding to all the sample data in the training data. The clustering process is as follows. As shown in FIG. 5 uses a three-layer deep neural network as an example. The data analysis network element groups the plurality of terminals corresponding to process 1 into Q terminal groups, and the plurality of terminals in each group have the same expected network behavior information of the terminal.

(1) Input level

(A) According to the definitions in Table 1, x ₁ is the time from the NE AMF, x ₂ is the location from the NE AMF, x ₃ is the communication start time from the NE SMF, x ₄ is the communication end time from the NE SMF, ... and x _M is the first type data fragment from the NE SMF.

(B) M is the measurement data of all terminal behavior information in Table 1.

(2) Hidden level

(A) According to the definitions in Table 2, y _i is a stillness indicator, y ₂ is a tag's movement path, y ₃ is a periodic communication indicator, ..., and y _M is a second type data fragment from the network element SMF.

(B) P is the data dimension of all terminal behavior information in Table 1.

(3) Output level

(A) Q is the number of groups obtained after clustering the set of terminals. In other words, many terminals are classified into Q categories, and each group of terminals has the same expected network information about the behavior of the terminal, namely:

...

.Thus, all terminals in the training data are classified into Q categories, each category corresponds to one group of terminals (corresponding to one set of terminal identification information), each category is represented using a vector, and the vector is the terminal behavioral feature vector of the group of terminals corresponding to categories, that is

.

Each category's terminal behavior feature vector can be used as user subscription data, namely, expected terminal behavior network information for all terminals in the set of terminals corresponding to the category, as shown in Table 2.

It should be noted that in this embodiment of the present disclosure, the first distance thresholds corresponding to centroids of all categories may be the same or different. This is not limited to this embodiment of the present disclosure.

In the example, the tag behavior information is the duration of the link, and the first distance thresholds corresponding to all categories are the same. To be specific, for example, the first distance threshold is 5 minutes, the communication duration corresponding to terminal 1 is 10 minutes, the communication duration corresponding to terminal 2 is 20 minutes, the communication duration corresponding to terminal 3 is 14 minutes, the communication duration corresponding to terminal 4 is 12 minutes, the communication duration corresponding to terminal 5 is 18 minutes, the communication duration corresponding to terminal 6 is 21 minutes, and the communication duration corresponding to terminal 7 is 20 minutes.

It is assumed that the centroid selected by the data analysis network element corresponds to category 1, in which the communication duration corresponding to terminal device 3 is 14 minutes, and corresponds to category 2, in which the communication duration corresponding to terminal device 5 is 18 minutes. In this case, the data analysis network element can determine that the 14 min link time corresponding to terminal 3, the 10 min link time corresponding to tag 1, and the 12 min link time corresponding to tag 4 are category 1 and are used as expected network information about the behavior of the terminal device corresponding to the group of terminal devices; and the data analysis network element may determine that a communication duration of 20 minutes corresponding to terminal device 2, a communication duration of 18 minutes corresponding to terminal device 5, a communication duration of 21 minutes corresponding to terminal device 6, and a communication duration of 20 minutes corresponding to terminal device 7 , belongs to category 1 and is used as the expected network information about the behavior of the end device corresponding to another group of end devices.

In this case, the expected tag behavior network information includes expected tag behavior network information corresponding to at least one group of tags in the plurality of tags.

группам оконечных устройств. Сетевой элемент анализа данных может передавать всю ожидаемую сетевую информацию о поведении оконечного устройства в сетевой элемент управления данными пользователя/сетевой элемент функции управления политикой (например, передавать ожидаемую сетевую информацию о поведении оконечного устройства, соответствующую всем Q группам оконечных устройств, в сетевой элемент управления данными пользователя или сетевой элемент функции управления политикой), или может передавать ожидаемую сетевую информацию о поведении оконечного устройства, соответствующую, по меньшей мере, одной из Q групп оконечных устройств, где Q является целым числом больше или равное 1, и сумма количеств оконечных устройств, включенных во все Q группы оконечных устройств, равно количеству множества оконечных устройств.It should be noted that in this embodiment of the present disclosure, the data analysis network element can determine, based on the tag behavior data corresponding to the plurality of tags, expected tag behavior network information corresponding to

endpoint groups. The data analysis network element may send all expected tag behavior network information to the user data network element/policy control function network element (e.g., send expected tag behavior network information corresponding to all Q groups of tags to the data network element user or a network element of a policy control function), or may convey expected network information about the behavior of a tag corresponding to at least one of Q groups of tags, where Q is an integer greater than or equal to 1, and the sum of the numbers of tags included to all Q groups of terminals is equal to the number of multiple terminals.

For example, the plurality of tags are tag 1 to tag 100, tag 1 to tag 20 correspond to a group of expected tag network behavior information, tag 21 to tag 62 correspond to a group of expected network tag behavior information, and terminal device 63 to terminal device 100 correspond to a group of expected network information about the behavior of the terminal device. For the above three groups of expected tag behavior network information, the analytics network element may select at least one group from the three groups as expected tag behavior network information determined by the analytics network element. For example, the expected tag behavior network information defined by the data analysis network element is a group of expected tag behavior network information corresponding to tag 1 over tag 20. Alternatively, for example, the expected tag behavior network information, defined by the data analysis network element is a group of expected tag behavior network information corresponding to tag 1 by tag 20, and a group of expected tag behavior network information corresponding to tag 63 by tag 100.

For example, expected network tag behavior information includes one or more of the following information:

indication of the stationary state, the trajectory of the movement of the target device, the periodic communication indicator, the duration of the communication, the communication period, the scheduled communication time, the maximum packet transmission delay, the maximum packet transmission response time, the number of buffered packets, and at least one data fragment of the second type.

It should be noted that in S102 in this embodiment of the present disclosure, the name of the information (eg, expected tag behavior network information) determined by the data analysis network element based on the tag behavior information is just an example. In an actual process, the name of the information determined by the data analysis network element based on the behavior information of the tag may alternatively be named as expected network information, expected network behavior information, or expected network information of the tag. In this embodiment of the present disclosure, one skilled in the art can appreciate that in an actual process, if one piece of information includes one or more of a steady state indication, tag movement path, periodic communication indicator, communication duration, communication period, scheduled communication time, maximum packet transmission delay, maximum packet transmission response time, number of buffered packets, and at least one piece of data of the second type, then the piece of information can be understood as expected network information about the behavior of the terminal device.

It should be noted that the first type data in this embodiment of the present disclosure is tag behavior information obtained by the data analysis network element from at least one core network element. The second type data is a data type obtained by the data analysis network element based on tag behavior information (including the first type data) received from at least one network element.

For example, the data analysis network element may obtain a stationary state indication and a movement path of the tag in the expected tag behavior network information based on location information (including time and location) in the tag behavior data; may obtain a periodic communication indicator, a communication duration, a communication period, and a scheduled communication time in the expected network behavior information of the tag based on a communication start time and a communication end time in the tag behavior data; and can obtain at least one piece of data of the second type in the expected network tag behavior information based on at least one piece of data of the first type in the tag behavior information. In addition, the first type data is the data analysis network element input, namely, the behavior information of the terminal device, and the second type data is the data analysis network element output, namely, the expected network information of the terminal device behavior.

S103: The data analysis network element transmits the expected network information about the behavior of the terminal device to the user data control network element/policy control function network element.

S104: The user data control network element/policy control function network element receives expected network information about the behavior of the terminal device from the data analysis network element.

S104-1: The user data network element uses the expected network behavior information of the terminal device as user subscription data of the terminal devices.

Specifically, upon receiving the expected network behavior information of the terminal, the user data network control element may use the received expected network behavior information of the terminal as subscription information for each terminal. After receiving the expected network information about the behavior of the tag, the network element of the policy control function may further forward the expected network information about the behavior of the tag to the user data network element.

This embodiment of the present disclosure provides a method for processing information. In this method, the data analysis network element obtains tag behavior information for a plurality of tag devices, then determines expected network tag behavior information based on the tag behavior information for a plurality of tag devices, and passes the expected network behavior information to the data control network element. user/network element of the policy management function. Compared with the prior art in which the expected behavioral network information is provided by the AF network element, the reliability of the expected behavioral network information received by the user data control network element/policy control function network element can be improved.

Alternatively, in another embodiment of the present disclosure, as shown in FIG. 6, the method presented in this embodiment of the present disclosure further includes the following steps.

S105. The data analysis network element transmits to the user data network element the first information of the terminal devices corresponding to the expected network information about the behavior of the terminal device.

It can be understood that the first terminal information corresponding to the expected network behavior information of the terminal device in step S105 and the expected network information of the behavior of the terminal device in step S103 may be sent to the user data network control element using the same message, or may be sent in different messages and sent to the user data web control.

The first tag information indicates expected tag behavior network information corresponding to each tag. The first terminal information may be identification information of a terminal device or identification information of a group of terminal devices. The terminal group identification information indicates the identifier of the terminal group.

For example, if the expected tag behavior network information includes expected tag behavior network information corresponding to at least one group of tags, the expected tag behavior network information corresponding to each of the at least one group of tags , corresponds to the first information list of one terminal device, and the first information list of the terminal device indicates the expected network information about the behavior of the terminal device corresponding to each of the at least one terminal device.

S106. The user data network element receives first tag information that corresponds to expected tag behavior network information from the data analysis network element.

Thus, after receiving the first information of the terminals, the user data network control element can use the expected network behavior information of the terminal corresponding to each terminal as the subscription information corresponding to the terminal. For example, the user data network control element uses the expected network tag behavior information corresponding to tag 1 as the subscription information corresponding to tag 1.

In another embodiment of the present disclosure, as shown in FIG. 7, the method presented in this embodiment of the present disclosure further includes the following steps.

S107. The user data control network element/policy control function network element sends a second request message to the data analysis network element, where the second request message requests expected network information about the behavior of a tag, and the second request message includes identification information of a plurality of tags.

It should be noted that in this embodiment of the present disclosure, if the second request message from the user data network control element to the data analysis network element, after determining the expected network information about the behavior of the terminal device, the network analysis data element sends the expected network information about the behavior of the terminal device to the user data control network element or passes the expected network information about the behavior of the terminal device to the network element of the policy control function.

If the second request message is sent by the policy control function network element to the data analysis network element, the data analysis network element may send the expected network information about the behavior of the terminal device to the network element of the policy control function, and the network element of the policy control function passes the expected network information about the behavior of the terminal device to the main the network element, or the data analysis network element, may send expected network information about the behavior of the tag to the user data control network element.

It can be understood that the second request message includes the identification information of each of the plurality of terminals.

For example, the second request message may be a message newly defined between the user data network element/policy management function network element and the data analysis network element, or may be an Nnwdaf_EventsSubscription_Subscribe service operation. This is not limited to this embodiment of the present disclosure.

Optionally, the second request message further includes at least one of a network area corresponding to the tag, a time window corresponding to the tag, a tag type corresponding to the tag, and the like.

S108: The data analysis network element receives the second request message from the user data control network element/policy control function network element.

Alternatively, the second request message may further convey the above filtering information.

поведения оконечного устройства может быть классифицирован на вектор поведения типа управления мобильностью (mobility management, MM) или вектор поведения типа управления сеансом (session management, SM) оконечного устройства на основании соответствующего основного сетевого элемента. Согласно таблице 1,

можно классифицировать на два типа векторов поведения оконечного устройства, MM-тип

и SM-тип

, на основании AMF и SMF, где S+T=P. Субвектор поведения оконечного устройства MM-типа или SM-типа в каждой категории может использоваться как информация о поведенческих признаках MM-типа или SM-типа всех оконечных устройств в наборе оконечных устройств, соответствующем категории.In the example, the expected network vector

The behavior of a terminal device can be classified into a behavior vector of a mobility management type (MM) or a behavior vector of a session management type (session management, SM) of the terminal device based on the corresponding core network element. According to table 1,

can be classified into two types of terminal behavior vectors, MM-type

and SM-type

, based on AMF and SMF, where S+T=P. The MM-type or SM-type terminal behavior subvector in each category may be used as information about the MM-type or SM-type behavioral features of all terminals in the set of terminals corresponding to the category.

Alternatively, each MM or SM type feature vector corresponds to a distance threshold. When the distance between the new MM type behavior sample data of the tag and the MM type feature vector exceeds the second distance threshold, the core network element may determine that the new tag MM type behavior sample data does not belong to the category corresponding to the MM type feature vector. When the distance between the new tag type SM behavior sample data and the SM type feature vector exceeds the third threshold distance, the core network element may determine that the new tag type SM behavior sample data does not belong to the category corresponding to the SM type feature vector.

The first distance threshold, the second distance threshold, and the third distance threshold are not limited in this embodiment of the present disclosure, and may be set based on a requirement.

In another embodiment of the present disclosure, expected tag behavior network information includes expected tag behavior network information corresponding to at least two basic network elements. Thus, the data analysis network element can further classify the received expected tag behavior network information to determine expected tag behavior network information corresponding to each core network element. Based on this, as shown in FIG. 8, the method presented in this embodiment of the present disclosure further includes the following steps.

S109: The data analysis network element transmits at least one of the identification information and the type information of each of the at least two basic network elements to the user data control network element/policy control function network element. The core network element identity indicates the core network element corresponding to each of a plurality of expected tag behavior network information pieces contained in the tag expected network behavior information. The core network element type information indicates the type, such as MM type or SM type, of the core network element corresponding to each of a plurality of expected tag behavior network information pieces contained in the tag expected network behavior information.

Alternatively, the MM-type core network element may be an AMF network element and the SM-type network element may be an SMF network element.

As an option, to S109, the method presented in this embodiment of the present disclosure further includes: determining, by the network element of data analysis, based on the identification information of the main network element, which is included in each piece of information about the behavior of the tag, the expected network information about tag behavior that corresponds to each core network element and which is in the expected tag behavior network information.

S110: The user data control network element/policy control function network element receives at least one of the identification information and type information that is related to each of the at least two basic network elements and that comes from the data analysis network element .

It can be understood that after S110, the user data network element/policy control function network element can determine the base network element corresponding to the received expected network behavior information of the tag.

In an exemplary embodiment, after S110, the method provided in this embodiment of the present disclosure further includes: transmitting, by the network control data user/network element, a policy control function to each core network element based on at least one of the identification information and basic network element type information, expected terminal behavior network information corresponding to the basic network element.

For example, if the expected tag behavior network information includes expected tag behavior network information corresponding to the AMF of the network element, the user data/policy control function network element sends to the AMF the network element the expected tag behavior network information corresponding to the AMF. network element.

The user data control network element may communicate to each core network element the expected tag behavior network information corresponding to the core network element in the next process.

In the example, when determining that the AMF network element requests registration of the terminal device in the 5G network, the user data control network element passes to the AMF network element the expected network information about the behavior of the terminal device corresponding to the AMF network element. Specifically, the terminal sends an AMF Registration Request to the network element. The registration request contains the identification information of the terminal device, and the registration request requires registration of the terminal device corresponding to the identification information of the terminal device in the 5G network. The AMF network element sends a Nudm_SDM_Get service operation to the user identity network element, and the Nudm_SDM_Get service operation sends the identity of the tag. The user data network element sends to the AMF the network element the expected network MM type tag behavior information corresponding to the tag's identity. The AMF network element sends a registration confirmation to the end device.

In another example, in a process in which the SMF network element requests the establishment of a Protocol Data Unit (PDU) session for a terminal device, the user data control network element sends expected network information about the behavior of the terminal device to the SMF network element, corresponding to the SMF of the network element. For example, the terminal sends a Session Establishment Request PDU to the SMF network element using the AMF network element. The session establishment request contains the identification information of the end device. The SMF network element sends a Nudm_SDM_Get service operation to the user identity network element, and the Nudm_SDM_Get service operation contains the identification information of the tag. The UDM network element sends to the SMF network element the expected network type session management information about the behavior of the terminal device corresponding to the identification information of the terminal device. The SMF network element sends a PDU session establishment confirmation to the end device using the AMF network element.

In yet another possible embodiment, as shown in FIG. 9, the method presented in this embodiment of the present disclosure further includes the following steps.

S111: The analysis network element determines the exception type of the terminal device based on the expected network information about the behavior of the terminal device.

As an example, S111 in this embodiment of the present disclosure may be implemented as follows:

Step 1: The Core NE obtains information about the behavior of the new terminal (see descriptions in Table 1 for specific content). In the present invention, the plurality of terminals that correspond to the received expected network information about the behavior of the terminal is the first terminal, and the new terminal may be the second terminal. If the main network element determines that the behavior information of the second terminal does not match the expected network information about the behavior of the terminal received by the main network element, namely, the distance between the vector generated by the behavior information of the second terminal and the vector generated by the expected network information about the behavior of the tag exceeds a predetermined threshold, the core network element determines that the second tag is faulty. In this case, the main network element transmits to the data analysis network element information about the behavior of the terminal device, which corresponds to the second terminal device and resides in the main network element. The main network element transmits the identification information of the second terminal device to another main network element to instruct the other main network element to send to the data analysis network element information about the behavior of the terminal device, which corresponds to the second terminal device and resides on another main network element.

Alternatively, the main network element may periodically report tag behavior information corresponding to the second tag to the data analysis network element according to a predetermined period.

Step 2: The data analysis network element obtains the terminal device behavior information that comes from at least two main network elements (SMF network element and AMF network element are used as an example), which separately corresponds to the second terminal device, and is located on SMF network element and AMF network element.

Step 3: The data analysis network element obtains the terminal behavior of one failed terminal based on the identity of the first terminal. After accumulating a certain amount of data on the behavior of the terminal device of the faulty terminal devices, the data analysis network element further analyzes the data on the behavior of the abnormal terminal device. If most or all of the anomalous behavior data of a tag is found to be of the same type, the data analysis network element determines the type of tag exclusion.

For example, the exception type could be one or more of the following: (1) misused; (2) interception; and (3) a new end device.

S112: The data analysis network element transmits the alarm information to the policy control function network element, where the alarm information indicates the exception type of the terminal device.

S113: The policy control function network element receives alarm information from the data analysis network element, and then the policy control function network element can take additional measures on the failed terminal, such as one-click shutdown, which specifically prevents the network from serving the failed terminal. device.

Fig. 10 shows a specific embodiment of an information processing method according to embodiments of the present disclosure. The method includes the following steps.

S201: The UDM network element passes the first service operation to the NWDAF network element, where the first service operation is used to subscribe to the expected network behavior information of the terminal device.

For example, the first service operation could be the Nnwdaf_EventsSubscription_Subscribe service operation.

For the specific contents of the first service operation, refer to the descriptions of the second request message in the above embodiment. The details are again not described here.

S202: The NWDAF network element transmits the second service operation separately to the AMF network element and the SMF network element, where the second service operation is used to subscribe to tag behavior information that separately corresponds to the tag and resides on the AMF network element and the SMF network element.

For example, the second service operation is the Nnf_UEBehavioralDataCollectionSubscription_Subscribe service operation.

For the specific contents of the second service operation, see the descriptions of the first request message in the above embodiment. The details are again not described here.

S203: The AMF network element informs the NWDAF network element of the tag behavior information that corresponds to the tag and is in the AMF network element.

S204: The SMF network element informs the NWDAF network element of the tag behavior information that corresponds to the tag and is in the SMF network element.

S205: The NWDAF network element determines the expected network tag behavior information based on the tag behavior information that corresponds to the tag and which is in the AMF network element, and the tag behavior information that corresponds to the tag and which is in the SMF network element. element.

For the implementation of S205, see descriptions of S102. The details are again not described here.

S206: The NWDAF network element transmits the third service operation to the UDM network element, where the third service operation transmits the expected network behavior information of the tag.

For example, the third service operation could be the Nnwdaf_EventsSubscription_Notify service operation.

Fig. 11A and FIG. 11B shows a specific embodiment of another information processing method according to embodiments of the present disclosure. The difference between the embodiment shown in FIG. 11A and FIG. 11B and the embodiment shown in FIG. 10 is at step S201 in FIG. 10, the first service operation is performed from the UDM network element to the NWDAF network element, and in step S301 in FIG. 11A and FIG. 11B, the first service operation is performed from the network element PCF to the NWDAF network element. For the contents of the other steps 302-305, respectively, refer to the contents of S202-S205. The details are again not described here. In addition, after S305, the solution shown in FIG. 11A and FIG. 11B further includes the following steps.

S306: The NWDAF network element determines, in the expected tag behavior network information, the expected tag behavior network information corresponding to the AMF of the network element and the expected tag behavior network information corresponding to the SMF of the network element.

S307: The NWDAF network element transmits the third service operation to the PCF network element, where the third service operation includes the expected tag behavior network information corresponding to the AMF of the network element and the expected tag behavior network information corresponding to the SMF of the network element.

For example, the third service operation could be the Nnwdaf_EventsSubscription_Notify service operation.

S308: The PCF network element initiates a fourth service operation for the network element AMF or the network element SMF, where the fourth service operation is used to: transmit to the AMF network element expected tag behavior information corresponding to the AMF network element; and transmitting, to the SMF, the network element, the expected network information about the behavior of the tag corresponding to the SMF to the network element.

For example, the fourth service operation may be the Npcf_UEExpectedBehavioralInfo_Notify service operation.

In addition, the PCF network element may distribute the AMF to the network element the expected network information about the behavior of the terminal type MM corresponding to each category; and distribute to the SMF the network element the expected network behavior information of the terminal type SM corresponding to each category.

S309: The AMF network element obtains the MM-type behavior information of the tag (with reference to Table 2) of the first tag, where the first tag is any of a plurality of tags.

S310: If it is determined that the MM-type tag behavior information of the first tag does not match the expected MM-type tag network behavior information that corresponds to the tag and that comes from the NWDAF of the network element to the AMF network element, the AMF network element determines that the first terminal is faulty.

S311: The AMF network element sends to the NWDAF the network element the MM-type behavior information of the tag corresponding to the first tag.

S312: The AMF network element sends to the SMF the network element the identification information corresponding to the first terminal, and the identification information corresponding to the first terminal is used to direct the SMF to the network element to report NWDAF to the network element. Information about the SM-type behavior of a tag that corresponds to the first tag and resides in the SMF NE. It can be understood that upon receiving the identification information corresponding to the first terminal, the SMF network element informs the NWDAF of the network element the SM-type behavior of the terminal, which corresponds to the first terminal and which is in the SMF network element.

S313: The NWDAF network element sums the MM-type behavior information of the tag from the network element AMF and the SM-type behavior information of the tag from the SMF of the network element that belongs to the first tag, and determines the exclusion type of the first tag.

S314: The NWDAF network element sends the exception type of the first terminal to the PCF network element.

It can be understood that the AMF network element in steps S310-S311 can alternatively be replaced by an SMF network element. When the AMF of the network element is replaced by the SMF of the network element, the identification information corresponding to the first terminal in S312 is supplied from the SMF of the network element to the AMF of the network element.

Fig. 12A and FIG. 12B are a specific flowchart of an information processing method according to an embodiment of the present disclosure. In the solution shown in FIG. 12A and FIG. 12B, for S401-S406, refer to specific content in S301-S306. For information about the specific contents of S416 to S421, see descriptions S309 to S314. The details are again not described here. In the solution shown in FIG. 12A and FIG. 12b:

S407: The NWDAF network element transmits the fifth service operation to the UDM network element, where the fifth service operation includes the expected tag behavior network information corresponding to the AMF of the network element and the expected tag behavior network information corresponding to the SMF of the network element.

For example, the fifth service operation could be the Nnwdaf_EventsSubscription_Notify service operation.

S408: The terminal device sends a Registration Request message to the AMF network element, where the registration request message includes identification information of the terminal device, and the registration request message requests registration of the terminal device corresponding to the identification information of the terminal device with the 5G network.

S409: The AMF network element transmits the sixth service operation to the UDM network element, the sixth service operation including the tag identification information.

For example, the sixth service operation may be a Nudm_SDM_Get service operation.

S410: The UDM network element sends to the AMF the network element the expected network MM-type behavior information of the tag corresponding to the identification information of the tag.

S411: The AMF network element sends a registration confirmation message to the terminal device.

S412: The terminal sends a Session Establishment Request (PDU) message to the SMF network element, where the PDU session request message contains identification information of the terminal.

In particular, the terminal may send a session establishment request message PDU to the SMF network element using the AMF network element.

S413: The SMF network element transmits the seventh service operation to the UDM network element, the seventh service operation including the tag identification information.

For example, the seventh service operation may be a Nudm_SDM_Get service operation.

S414: The UDM network element transmits to the SMF the network element the expected network SM type tag behavior information corresponding to the identification information of the tag.

S415: SMF The network element transmits a Session Establishment Accept (PDU) message to the terminal using the AMF network element.

Option 2 implementation.

Fig. 13 is a flowchart of a method for determining tag exception information according to this embodiment of the present disclosure. The method includes the following steps.

S501: The first network element determines that the terminal device is faulty.

For example, the first network element may be the first primary network element, the user data management network element 101, or the policy management function network element 107 in the communication system shown in FIG. 1. In addition, the first network element may alternatively be a user plane network element. For example, the first primary network element may be a session management network element or a mobility management network element.

It should be understood that in step S501 and the following steps in this embodiment, there may be one terminal, a plurality of terminals, or a group of terminals. The details are again not described below.

In an exemplary implementation of S501 in this embodiment of the present disclosure may be implemented as follows: the first network element determines that the terminal device is out of order based on the expected network information about the behavior of the terminal device (Expected UE behavioral information) on the first network element and behavior information end device on the first network element.

Step 501 can be specifically implemented as follows: if the expected network information about the behavior of the tag on the first network element does not match the behavior information of the tag on the first network element, the first network element determines that the tag is faulty.

The first network element may receive from the user data network element expected network information about the behavior of the tag (eg, with reference to Table 2) on the first network element. The user data network element may obtain expected network information about the behavior of the terminal device from the data analysis network element or the application function network element. For the specific process in which the user data network element obtains the expected network information about the behavior of the tag, see Embodiment 1. The details are again not described here.

In particular, the expected network information about the behavior of the tag on the first network element can be understood as the behavioral signature information of the tag.

For example, information about the behavior of a terminal device in the first network element may include identification information of the terminal device and behavioral data (see Table 1 for examples of information) of the terminal device in the first network element. The tag behavior information at the first network element is the tag behavior data collected at the first network element. Moreover, in addition to the information shown in Table 1, tag behavior data may additionally be shown in Table 3.

Table 3 Endpoint Behavior Data

Data type Name of the network element that owns the end device behavior data Function Mobility re-registration frequency (frequency) AMF network element NE AMF Re-registration Frequency Indication (Different Neighbor Cells) Reachability after DNN failure AMF network element Indication of the presence of a data transmission failure event (signaling) when the target device is reachable Number of endpoints in a geographic area AMF network element Specifying the number of endpoints in a particular area (where the area is typically provided by AF) SUPI-PEI association update UDM network element Indication that the PEI (IMEI (SV)) of the target device (corresponding to a specific SUPI) has been updated Roaming status UDM network element Indication of the roaming status of the end device (regardless of whether the Serving PLMN and/or the end device is in the Home Public Land Mobile Network (HPLMN)) and whether the status notification has been updated

S502: The first network element transmits the indication information to the data analysis network element, where the indication information indicates that the terminal is faulty.

For example, the data analysis network element may be the data analysis network element 104 shown in FIG. 1. For example, the data analysis network element may be an NWDAF network element.

In an exemplary implementation, S502 may be implemented as follows: the first network element may send to the analysis network element an Nnf_EventExposure_Notify service operation carrying indication information, where nf is the name of the first network element. For example, if the first NE is an AMF NE, the service operation may be Namf_EventExposure_Notify. If the first NE is an SMF NE, the service operation may be Nsmf_EventExposure_Notify.

For example, the first network element may separately send to the data analysis network element another message or service operation that conveys indication information, such as a terminal exception notification message or an Nnf_UEAbnormal_Notify service operation.

S503: The data analysis network element receives indication information from the first network element.

S504: The data analysis network element acquires behavior information of the terminal device in the second network element based on the indication information.

It should be understood that in step S504, the data analysis network element may obtain information about the behavior of the terminal device in one or more second network elements. Information about the behavior of the terminal device on one or more second network elements may be the same or different. For example, the second network elements are a policy control function network element and a session control network element. The data analysis network element can obtain terminal behavior information 1 in the policy control function network element and terminal behavior information 2 in the session control network element. Additionally, the behavior information 1 of the terminal device in the network element of the policy control function may differ from the information about the behavior of the terminal device 2 in the session control network element.

It should be understood that one or more second network elements may include a first network element. Of course, one or more second network elements may alternatively not include the first network element. This is not limited to this embodiment of the present disclosure. If one or more second network elements include the first network element, the data analysis network element can obtain information about the behavior of the terminal device from the first network element, which initiates the data analysis network element to determine the exclusion information of the terminal device and the network element other than the first network element. element in one or more second network elements. For example, the first network element is a mobility management network element and the one or more second network elements may include a mobility management network element and a session management network element. In particular, the mobility control network element initiates a data analysis network element to obtain tag exclusion information. In this case, the data analysis network element may obtain information about the behavior of the terminal device from the mobility management network element and the session management network element. When one or more second network elements do not include the first network element, the data analysis network element may obtain tag behavior information from another network element, which triggers the data analysis network element to determine tag exclusion information. For example, if the first network element is a mobility management network element, and one or more second network elements include a policy control function network element and a session control network element, the data analysis network element can obtain information about the behavior of the terminal device from the policy control function network element. or session web control.

It should be noted that when the data analysis network element obtains tag behavior information from one or more second network elements, the data analysis network element may associate the tag behavior information with the one or more second network elements, and determine the tag exclusion information based on information about the behavior of the end device received after the association.

It should be understood that in step S504, when the data analysis network element obtains the behavior information of the tag on at least two second network elements, the data analysis network element should associate the behavior information of the tag with at least two second network elements. elements based on the tag's identity to obtain complete information about the behavior of the tag. Of course, in addition to the tag identification information, the data analysis network element may alternatively associate tag behavior information of the tag with at least two second network elements based on area information, time information, or tag type information. For a process in which the data analysis network element associates tag behavior information with at least two second network elements, see descriptions of S1011 in Embodiment 1. The details are again not described here.

S505: The data analysis network element determines the tag exclusion information based on the behavior information of the tag.

For example, the tag exception information includes one or more of the following information corresponding to the tag: identification information, exception type, exception ID, and exception level of the tag. The exception identifier is used to identify the type of exception, and the exception level indicates the extent or value of the exception type.

In an exemplary embodiment, still referring to FIG. 13, before S504 is provided in this embodiment of the present disclosure, the method provided in this embodiment of the present disclosure further includes the following steps.

S506: The first network element transmits to the data analysis network element one or more of the following information corresponding to the terminal device: identification information of the terminal device, network area, type of the terminal device, time information, and information about the behavior of the terminal device on the first network element.

The functions of tag identification information, network region, tag type, timing information, and tag behavior information in the first network element are shown in Table 4.

Table 4 Functions of the information provided by the first network element to the data analysis network element

Information Function Terminal identification information The tag identification information may be SUPI, PEI, GPSI, IMSI, IMEI, IP, IP 5-tuple or the like, used to identify the tag; or it may be an internal group ID, a UE group ID, or an external group ID used to identify a group of terminals. network area The network area may be a network area (eg, TA, TA list, cell, or cell list) or may be a geographic area (eg, GPS list) that indicates the network area in which the terminal resides. End device type End device type can be iPhone 8, Mate 20, Honor 10 or the like; or may be the operating system (iOS, Android, or Symbian) of the target device, which indicates the type of end device Time Information The time information is a timestamp (Timestamp), a time interval (Time Interval), a time window (Time Window), or the like, indicates a time period in which the terminal is abnormal.

For ease of description, in this embodiment of the present disclosure, information from the first network element to the data analysis network element in S506 may be referred to as tag related information. Terminal related information and indication information may be sent from the first network element to the data analysis network element using the same message (eg, Nnf_EventExposure_Notify service operation). In this way, signaling overhead can be reduced.

Of course, the terminal-related information and the indication information may alternatively be transmitted from the first network element to the data analysis network element using different messages. For example, after the first network element transmits the indication information, the data analysis network element subscribes to the tag behavior information from the first network element, and then the first network element transmits the tag behavior information to the data analysis network element. The specific step is the same as in S504.

S507: The data analysis network element receives from the first network element one or more of the following information corresponding to the tag: tag identification information, network area, tag type, timing information, and tag behavior information on the first network element.

For the specific contents of the identification information of the terminal device, the network area, the type of the terminal device, the time information and the behavior data of the terminal device in the first network element, see the above-mentioned respective descriptions. The details are again not described here.

Accordingly, S504 can be implemented as follows: the data analysis network element obtains information about the behavior of a terminal of one or more terminals in the second network element based on the indication information and any one or more information received at S507.

It should be understood that a terminal identification information may point to one or more terminals (with reference to Table 4). See the descriptions in Table 1 and Table 3 for specific terminal behavior data. Again, details are not described here.

In an exemplary implementation, the tag related information received by the data analysis network element at S507 may be used alone or may be used in a combined manner. For specific usage, refer to the process in which the data analysis network element uses the filtering information in S1012.

In a possible implementation, as shown in FIG. 14, S504 in this embodiment of the present disclosure can be specifically implemented as follows:

S5041: The analysis network element transmits a request message to the second network element, so that the second network element receives a request message from the analysis network element, where the request message requests information about the behavior of a tag on the second network element.

For example, the request message could be an Nnf_EventExposure_Subscribe service operation. That is, the data analysis network element subscribes to data from the second network element.

In an exemplary implementation, the request message may further include one or more of the following tag-specific information: tag ID, network area, tag type, and time information. Refer to Table 4 for details. The information is used to gather information about the behavior of the terminal device on the second network element from the second network element. See table 1 and table 3.

S5042: The data analysis network element receives a response message from the second network element, where the response message includes information about the behavior of the terminal device in the second network element. For example, the response message could be an Nnf_EventExposure_Notify service operation.

For example, the tag behavior information includes any one or more of the following information: identification information of the second network element, location information, communication start time, communication end time, packet delay, number of packets, packet size, and at least one a piece of data of the first type of one or more terminal devices on the second network element. In particular, see Tables 1 and 3 for terminal behavior information.

For at least one piece of data of the first type, see the previous descriptions in Embodiment 1. The details are again not described here. It should be understood that in step S505, if the first network element transmits the behavior information of the terminal device on the first network element to the data analysis network element, in step S5041, the data analysis network element does not need to subscribe to the behavior information of the terminal device on the first network element of the first network element. In this case, the data analysis network element must associate the behavior information of the tag on the first network element and the behavior information of the tag on the second network element based on the identity of the tag to obtain complete information about the behavior of the tag. In addition to tag identification information, the data analysis network element may alternatively associate tag behavior information with at least two second network elements based on area information, time information, or tag type information.

Still with reference to FIG. 14, S505 in this embodiment of the present disclosure can be specifically implemented as follows: the data analysis network element determines the tag exclusion information based on the behavior information of the tag and the expected network behavior information of the tag.

For example, if the analysis network element further obtains information about the behavior of the terminal device on the first network element, S505 in this embodiment of the present disclosure can be specifically implemented as follows: the analysis network element determines the exclusion information of the terminal device based on the information about the behavior of the terminal device on the first network element, information about the behavior of the tag on the second network element, and expected network information about the behavior of the tag.

Expected network information about the behavior of the tag may be pre-stored in the data analysis network element. If the data analysis network element does not have the expected network information about the behavior of the terminal after the network analysis element receives information about the behavior of the terminal, in an exemplary embodiment with reference to FIG. 14, before S505 is provided in this embodiment of the present disclosure, the method provided in this embodiment of the present disclosure further includes the following steps.

S508: The application function network element transmits the expected network information about the behavior of the terminal device to the data analysis network element.

Specifically, up to S508, the method provided in this embodiment of the present disclosure further includes: requesting, by the data analysis network element, the behavioral indicia information of one or more terminals from the application function network element.

As a variant, up to S508, the method presented in this embodiment of the present disclosure further includes: requesting a data analysis network element of behavioral indicia information of one or more terminals from an application function network element using a network exposure function network element.

S509: The data analysis network element obtains the expected network information about the behavior of the terminal device from the application function network element.

Specifically, the method presented in this embodiment of the present disclosure further includes: obtaining by the data analysis network element the expected network information about the behavior of the terminal device from the application function network element using the network exposure function network element.

It should be noted that if the expected network information about the behavior of the tag can be obtained by analyzing the data analysis network element, steps S508 and S509 can be omitted.

In a possible embodiment, still referring to FIG. 14 after S505, the method presented in this embodiment of the present disclosure further includes the following steps.

S510: The data analysis network element transmits the exclusion information to the third network element, where the exclusion information is used to perform policy control on the terminal device.

For example, the third network element may be an AF network element or a policy control function network element. In FIG. 14, an example is used in which the third network element is an AF network element.

S511: The third network element receives exclusion information from the data analysis network element.

Embodiment 3

Fig. 15 shows a method for determining tag exception information according to this embodiment of the present disclosure. The method includes the following steps.

S601: The data analysis network element transmits a first request message to the first network element, where the first request message requests information about the behavior of the failed terminal on the first network element.

For example, the first network element can be any of a session control network element, a policy control function network element, a user data network element, a user plane network element, or a mobility network element.

In an exemplary implementation, the first request message may contain the first instruction. The first instruction is used to direct the first network element to report information about the behavior of the failed terminal on the first network element.

In another possible implementation, the first request message itself may be used to request information about the tag behavior of the failed tag on the first network element.

For example, the first network element is a session control network element. The first request message may be Nsmf_EventExposure_Subscribe. The first instruction includes an Event ID and Event Filter information. On the one hand, the event ID can be used to indicate Abnormal UE behavior information, and the event filter is not specifically specified. The first network element may compare, based on the event ID, the behavior information of the tag at the first network element with the expected network information about the behavior of the tag at the first network element, and if it is found that the behavior information of the tag at the first network element does not match the expected network information about the behavior of the terminal device at the first network element, the first network element additionally reports data about the behavior of the terminal device at the first network element to the data analysis network element. On the other hand, the event identifier may be used to indicate UE behavior information, and the event filter may include indication information (eg, a preflight indicator). The indication information is used to direct the first network element to compare the behavior information of the terminal device on the first network element with the expected network information about the behavior of the terminal device on the first network element, and if it is found that the behavior information of the terminal device on the first network element does not match the expected network element. information about the behavior of the terminal device on the first network element, information about the behavior of the terminal device on the first network element is additionally sent to the data analysis network element.

S602: In response to the first request message, the first network element transmits a first response message to the data analysis network element, where the first response message includes identification information of one or more terminals and terminal behavior information of each of the one or more terminals on the first network element.

For the terminal behavior of each terminal in the first network element, see the descriptions in Embodiment 2. The details are again not described here.

It should be understood that after receiving the first request message, the first network element may perform step 501 to determine that the failed terminal is being served by the first network element, or to determine information about the behavior of the failed terminal.

S603: The data analysis network element requests tag behavior information of one or more tags in the second network element from the second network element based on the identification information of the one or more tags.

In particular, S603 can be implemented as follows: the analysis network element transmits the second request message to the second network element, so that the second network element receives the second request message from the analysis network element. The second request message requests information about the tag behavior of one or more tags in the second network element. The second network element transmits the second response message to the data analysis network element, so that the data analysis network element receives the second response message. The second response message includes information about the tag behavior of one or more tags in the second network element. For example, the second request message may contain a first field, and the first field requests information about the behavior of a terminal device of one or more terminal devices in the second network element. Alternatively, the second request message requests information about the tag behavior of one or more tags in the second network element from the second network element.

For example, the second request message may include identification information of one or more terminals.

S604: The data analysis network element determines exclusion information based on the tag behavior information of one or more terminal devices on the first network element, the tag behavior information of one or more terminal devices on the second network element, and the expected network information about the behavior of the tag device of one or more more end devices.

Specifically, for the specific implementation of S604, refer to the specific implementation process of S505 in Embodiment 2. The details are again not described here.

In an exemplary implementation, after S604, the method provided in this embodiment of the present disclosure further includes S605 and S606. Descriptions of S605 and S606 are the same as descriptions of S510 and S511 in Embodiment 2. The details are again not described here.

It should be understood that the difference between option 3 and option 2 is as follows: in option 2, the first network element initiates, using the indication information, the analysis network element to obtain information about the behavior of the terminal device, so that the analysis network element can determine the exclusion information terminal device based on information about the behavior of the terminal device obtained from the second network element; and in Embodiment 3, after the data analysis network element proactively subscribes to the failed terminal information from the first network element and obtains the identification information of the failed terminal and the terminal behavior information of the failed terminal on the first network element, the data analysis network element obtains, from the second network element, terminal behavior information of the failed terminal on the second network element based on identification information of the failed terminal, and obtains terminal exclusion information by parsing with reference to the behavior information of the failed terminal on the first network element and the behavior information of the failed terminal. end device on the second network element.

The foregoing describes the solutions in the embodiments of the present disclosure mainly in terms of interaction between network elements. It can be understood that, in order to implement the above functions, network elements such as an information processing device and an information transmission device include appropriate hardware structures and/or software modules to perform these functions. One skilled in the art will readily appreciate that, in combination with the example blocks and algorithm steps that are described in the embodiments disclosed in this specification, the present disclosure may be implemented in hardware or a combination of hardware and computer software. The performance of a function by hardware or hardware controlled by computer software depends on the particular application and design constraints of the technical solutions. A person skilled in the art may use different methods to implement the described functions for each particular application, but it should be appreciated that the implementation is not outside the scope of this disclosure.

In embodiments of the present disclosure, the information processing device and the information transmission device may be divided into functional blocks based on the above method examples. For example, each function block may be obtained by division based on a corresponding function, or two or more functions may be integrated into one processing block. An integrated block may be implemented in hardware or may be implemented in a software function block. It should be noted that in the embodiments of the present disclosure, the division into blocks is an example and is simply a logical separation of functions. In a real implementation, a different partitioning method may be used.

Description is given below using an example in which each function block is obtained by dividing based on the corresponding function.

When an integrated block is used, FIG. 16 is a possible diagram of the information processing apparatus in the above embodiments. The information processing device may be a data analysis network element or a chip applied to the data analysis network element. The information processing apparatus includes an acquisition unit 201, a determination unit 202, and a transmission unit 203. The acquisition unit 201 is configured to support the information processing apparatus while executing S101 and S1011 in the above embodiment. The determining unit 202 is configured to support the information processing apparatus when executing S102, S111, and S112 in the above embodiment. The transmission unit 103 is configured to support the information processing apparatus while executing S103, S1012, S105, and S109 in the above embodiment. Alternatively, the information processing apparatus may further include a receiving unit 204 configured to support the information processing apparatus when S108 is executed in the above embodiment. All relevant contents of the steps in the above method embodiments can be cited to describe the functions of the respective functional modules. The details are again not described here.

When an integrated block is used, FIG. 17 is an exemplary logic structure diagram of the information processing apparatus in the above embodiments. The information processing device may be a data analysis network element or a chip applied to the data analysis network element in the above embodiments. The information processing apparatus includes a processing module 212 and a communication module 213 . The processing unit 212 is configured to control the operation of the information processing device. For example, the processing unit 212 is configured to perform a message or data processing step on the side of the information processing apparatus, for example, to support the information processing apparatus in executing S102, S111, and S112 in the above embodiment. The communication unit 213 is configured to support the information processing apparatus while executing S103, S1012, S105, S108, and S109 in the above embodiment; and/or used in another process performed by the device for processing information in the technology described in this description.

Alternatively, the information processing apparatus may further include a storage unit 211 configured to store program code and data of the information processing apparatus.

Processing module 212 may be a processor or a controller. For example, processing module 212 may be a CPU, a general purpose processor, a digital signal processor, an ASIC, a field-programmable gate array or other programmable logic device, a transistorized logic device, a hardware component, or any combination thereof. Processing module 212 may implement or execute various exemplary logical blocks, modules, and circuits described with reference to the content disclosed in the present invention. Alternatively, the processor may be a combination of processors that implement a computing function, such as a combination of one or more microprocessors, or a combination of a digital signal processor and a microprocessor. The communication module 213 may be a transceiver, a transceiver circuit, a communication interface, or the like. The storage module 211 may be a memory.

When the processing unit 212 is the processor 220, the communication unit 213 is the communication interface 230 or transceiver, and the storage unit 211 is the memory 240, the information processing apparatus in the present invention may be the apparatus shown in FIG. eighteen.

Communication interface 230, one or more (including two) processors 220, and memory 240 are connected to each other via bus 210. Bus 210 may be a PCI bus, an EISA bus, or the like. The bus 210 can be divided into an address bus, a data bus, a control bus, and the like. For ease of presentation, the bus in FIG. 18 is indicated by only one thick line, but this does not mean that there is only one tire or only one type of tire. The memory 240 is configured to store the program code and data of the information processing device. The communication interface 230 is configured to support the information processing device when communicating with another device (eg, an information communication device), such as supporting the information processing device when performing S1012, S105, S108, and S109. The processor 220 is configured to support the information processing apparatus in executing the program code and data stored in the memory 240 to implement S102, S111, and S112 provided in the present invention.

When an integrated block is used, FIG. 19 is a possible diagram of the information transmission device in the above embodiments. The communication device may be a core network element or a chip applied to the core network element. The information transmission device includes a receiving unit 301 and a transmitting unit 302 . The receiving unit 301 is configured to support the information transmission device when S1013 is executed in the above embodiment, and the transmission unit 302 is configured to support the information transmission device when S1014 is executed in the previous embodiment. All relevant contents of the steps in the above method embodiments can be cited to describe the functions of the respective functional modules. The details are again not described here.

When an integrated block is used, FIG. 20 is a possible diagram of the logical structure of the information transmission device in the above embodiments. The communication device may be a core network element or a chip applied to the core network element in the above embodiments. The communication device includes a processing module 312 and a communication module 313 . The processing module 312 is configured to monitor and control the operation of the communication device. For example, the processing module 312 is configured to perform a message or data processing step on the communication device side. The communication unit 313 is configured to support the communication device when performing steps S1014 and S1013 in the above embodiment; and/or used in another process performed by the communication device in the technology described in this description.

Alternatively, the communication device may further include a storage unit 311 configured to store program code and data of the communication device.

Processing module 312 may be a processor or a controller. For example, processing module 312 may be a CPU, a general purpose processor, a digital signal processor, an ASIC, a field-programmable gate array or other programmable logic device, a transistorized logic device, a hardware component, or any combination thereof. Processing module 312 may implement or execute various exemplary logical blocks, modules, and circuits described with reference to the content disclosed in the present invention. Alternatively, the processor may be a combination of processors that implement a computing function, such as a combination of one or more microprocessors, or a combination of a digital signal processor and a microprocessor. The communication module 313 may be a transceiver, a transceiver circuit, a communication interface, or the like. The storage module 311 may be a memory.

When the processing unit 312 is the processor 320, the communication unit 313 is the communication interface 330 or transceiver, and the storage unit 311 is the memory 340, the communication device in the present invention may be the device shown in FIG. 21.

Communication interface 330, one or more (including two) processors 320, and memory 340 are connected to each other via bus 310. Bus 310 may be a PCI bus, an EISA bus, or the like. The bus 310 can be divided into an address bus, a data bus, a control bus, and the like. For ease of presentation, the bus in FIG. 21 is indicated by only one thick line, but this does not mean that there is only one tire or only one type of tire. The memory 340 is configured to store the program code and data of the communication device. The communication interface 330 is configured to support the communication device while communicating with another device (eg, a terminal device). The processor 320 is configured to support the communication device while executing the program code and data stored in the memory 340 to implement S1013 and S1014 provided in the present invention.

When an integrated block is used, FIG. 22 is a possible diagram of the information processing apparatus in the above embodiments. The information processing device may be a user data network element or a chip applied to a user data network element. The information processing apparatus includes a receiving unit 401 and a processing unit 402 . The receiving unit 401 is configured to support the information processing apparatus while executing S104, S106, and S110 in the above embodiment. The processing unit 402 is configured to support the information processing apparatus while executing S104-1 in the above embodiment. Alternatively, the information processing apparatus may further include a transmission unit 403 configured to support the information processing apparatus when S107 is executed in the above embodiment. All relevant contents of the steps in the above method embodiments can be cited to describe the functions of the respective functional modules. The details are again not described here.

Alternatively, the information processing device shown in FIG. 22 may alternatively be a policy control function network element or a chip in a policy control function network element. In this case, for the process performed by each block in the information processing apparatus, refer to the foregoing description. The details are again not described here. The difference is that the receiving unit 401 may be configured not to execute S106, but configured to perform S113. In this case, the processing unit 402 may not need to execute S104-1, but may determine the expected tag network behavior information corresponding to each basic network element in the tag expected network behavior information.

When an integrated block is used, FIG. 23 is a possible logic structure diagram of the information processing apparatus in the above embodiments. The information processing device may be a user data network control element or a chip applied to the user data network control element in the above embodiments. The information processing device includes a processing module 412 and a communication module 413 . The processing module 412 is configured to monitor and control the operation of the information processing device. For example, the processing unit 412 is configured to perform a message or data processing step such as S104-1 on the information processing apparatus side. The communication unit 413 is configured to support the information processing apparatus while executing S104, S106, S107, and S110 in the above embodiment; and/or used in another process performed by an information processing device in the technology described herein.

Alternatively, the information processing apparatus may further include a storage unit 411 configured to store program code and data of the information processing apparatus.

Alternatively, when the information processing device is a policy control function network element or a chip applied to the policy control function network element, for steps performed by modules in the information processing device, refer to the above description. The details are again not described here. The difference is that the communication module 413 may be configured not to perform S106, but configured to perform S113. In this case, the processing unit 412 may not need to execute S104-1, but may determine the expected network behavior information of the tag corresponding to each basic network element in the expected network behavior information of the tag.

Processing module 412 may be a processor or a controller. For example, processing module 412 may be a CPU, a general purpose processor, a digital signal processor, an ASIC, a field-programmable gate array, or other programmable logic device, transistorized logic device, or hardware. component or any combination thereof. Processing module 412 may implement or execute various exemplary logical blocks, modules, and circuits described with reference to the content disclosed in the present invention. Alternatively, the processor may be a combination of processors that implement a computing function, such as a combination of one or more microprocessors, or a combination of a digital signal processor and a microprocessor. The communication module 413 may be a transceiver, a transceiver circuit, a communication interface, or the like. The storage module 411 may be a memory.

When the processing unit 412 is the processor 420, the communication unit 413 is the communication interface 430 or transceiver, and the storage unit 411 is the memory 440, the information processing apparatus in the present invention may be the apparatus shown in FIG. 24.

Communication interface 430, one or more (including two) processors 420, and memory 440 are connected to each other via bus 410. Bus 410 may be a PCI bus, an EISA bus, or the like. The bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of presentation, the bus in FIG. 24 is indicated by only one thick line, but this does not mean that there is only one tire or only one type of tire. The memory 440 is configured to store the program code and data of the information processing device. The communication interface 430 is configured to support the information processing device in communication with another device (eg, a communication device). The processor 420 is configured to support the information processing apparatus in executing the program code and data stored in the memory 440 to implement S104, S104-1, S106, S107, and S110 provided in the present invention.

Fig. 25 is a possible device logic structure diagram for determining terminal exclusion information in the above embodiments. The device for determining the exclusion information of the terminal may be a data analysis network element or a chip applied to the data analysis network element in the above embodiments. The apparatus for determining the terminal exclusion information includes a receiving unit 501 and a processing unit 502 .

The receiving unit 501 is configured to support the data analysis network element when executing S503 and S504 in the above embodiment. The processing unit 502 is configured to support the data analysis network element when executing S505 in the above embodiment.

In an exemplary implementation, the receiving unit 501 is further configured to support the data analysis network element when executing S507, S5042, and S509 in the above embodiment. In an exemplary implementation, the device for determining the tag exclusion information may further include a transmission unit 503 configured to support the data analysis network element when executing S5041 and S510 in the above embodiment. In particular, when the device shown in FIG. 25 is configured to implement the steps performed by the analysis network element in Embodiment 2, the transmission block 503 is a possible block.

In an exemplary implementation, a device for determining exclusion information of the terminal shown in FIG. 25 may further include a memory unit configured to store instructions or programs.

When the terminal exception information determination device shown in FIG. 25 uses the structure shown in FIG. 18, transmitting block 503 and receiving block 501 may correspond to communication interface 230, and processing block 502 may correspond to processor 220. In an exemplary implementation, when the apparatus for determining terminal exclusion information shown in FIG. 25 uses the structure shown in FIG. 18, the storage unit may correspond to the memory 240. The communication interface 230 is configured to support a device for determining exclusion information of the terminal shown in FIG. 18 when performing S503 and S504 in the above embodiment. The processor 220 is configured to support an apparatus for determining tag exclusion information shown in FIG. 18 when S505 is executed in the previous embodiment.

In an exemplary implementation, the communication interface 230 is configured to support a device for determining exclusion information of the terminal shown in FIG. 18 when performing S507, S5042, and S509 in the previous embodiment. In an exemplary implementation, the communication interface 230 is further configured to support a device for determining exclusion information of the terminal shown in FIG. 18 when performing S5041 and S510 in the previous embodiment.

Fig. 26 is a possible device logic structure diagram for determining terminal exclusion information in the above embodiments. The device for determining the exclusion information of the terminal may be a data analysis network element or a chip applied to the data analysis network element in the above embodiments. Alternatively, the device for determining the terminal exclusion information may be the first network element or a chip applied to the first network element in the above embodiments. The apparatus for determining terminal exclusion information includes a processing unit 601 and a transmission unit 602 .

For example, the device shown in Fig. 26 is a data analysis network element or a chip applied to the data analysis network element in the above embodiments. The transmission unit 602 is configured to support the data analysis network element when executing S601 and S603 in the above embodiment. The processing unit 601 is configured to support the data analysis network element when executing S604 in the above embodiment. The transmission unit 602 is further configured to support the data analysis network element when executing S605 in the above embodiment.

For another example, the device shown in FIG. 26 represents the first network element or chip applied to the first network element in the above embodiments. The processing unit 601 is configured to support the first network element while executing S501 in the above embodiment. The transmission unit 602 is configured to support the first network element while executing S502 in the above embodiment.

In an exemplary implementation, the transmission unit 602 is further configured to support the first network element while executing S506 in the above embodiment.

In a possible implementation, the device shown in FIG. 26 may further include a memory unit configured to store instructions or programs.

When the device shown in FIG. 26 uses the structure shown in FIG. 18, a transmission block 602 may correspond to a communication interface 230, and a processing block 602 may correspond to a processor 220. In an exemplary implementation, when the device for determining tag exclusion information shown in FIG. 26 uses the structure shown in FIG. 18, the memory block may correspond to memory 240.

For example, when the device shown in FIG. 18 is a data analysis network element, the communication interface 230 is configured to support a device for determining exclusion information of the terminal device shown in FIG. 18 when performing S601, S603, and S605 in the above embodiment. The processor 220 is configured to support an apparatus for determining tag exclusion information shown in FIG. 18 when S604 is executed in the above embodiment.

For another example, when the device shown in FIG. 18 is the first network element, the processor 220 is configured to support a device for determining exception information of the terminal device shown in FIG. 18 when S501 is executed in the previous embodiment. The communication interface 230 is configured to support a device for determining exclusion information of the terminal device shown in FIG. 18 when S502 is executed in the previous embodiment.

In an exemplary implementation, the communication interface 230 is configured to support a device for determining exclusion information of the terminal shown in FIG. 18 when S506 is executed in the previous embodiment.

An embodiment of the present disclosure provides a communication device. The communication device includes one or more modules configured to implement the method in steps 601-606. One or more modules may correspond to blocks 601-606. Specifically, in this embodiment of the present disclosure, for each step performed by the first network element in the method, the first network element includes a block or module for performing the step in the method. For each step performed by the data analysis network element in the method, the data analysis network element includes a block or module for performing the step in the method. For example, a module that controls or processes the operation of a communication device may be referred to as a processing module, and a module that performs a message or data processing step on the side of the communication device may be referred to as a communication module.

Fig. 27 is a diagram of a chip 150 according to an embodiment of the present disclosure. Chip 150 includes one or more (including two) processors 1510 and interface circuit 1530.

Optionally, chip 150 further includes memory 1540. Memory 1540 may include read-only memory and RAM, and provide operating instructions and data to processor 1510. Memory portion 1540 may further include nonvolatile random access memory (non -volatile random access memory, NVRAM).

In some implementations, memory 1540 stores the following elements, an executable module or a data structure, or a subset or extension of them.

In this embodiment of the present disclosure, the corresponding operation is performed by calling an operation instruction stored in memory 1540 (the operation instruction may be stored in an operating system).

Possible implementation: the data analysis network element, the user data control network element, and the main network element use the same chip structure, and different devices can use different chips to realize the corresponding functions.

The processor 1510 controls the operations of the data analysis network element, the user data control network element, and the main network element. Processor 1510 may also be referred to as a central processing unit (CPU). Memory 1540 may include read only memory and random access memory and provide instructions and data to processor 1510. Memory portion 1540 may further include non-volatile random access memory (NVRAM). For example, in the present invention, memory 1540, interface circuit 1530, and memory 1540 are connected together via a bus system 1520. In addition to the data bus, the bus system 1520 may further include a power bus, a bus control system, a status signal bus, and the like. However, for a clear description of the various types of tires in FIG. 27 are designated as bus system 1520.

The method disclosed in the above embodiments of the present disclosure may be applied to a processor 1510 or implemented by a processor 1510. The processor 1510 may be an integrated circuit chip and has signal processing capability. During implementation, the steps of the above methods may be implemented using a hardware integrated logic circuit in the processor 1510 or using instructions in the form of software. Processor 1510 may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, a discrete logic device with a gate or transistor, or a discrete hardware component. The processor 1510 may implement or execute the methods, steps, and flowcharts that are disclosed in the embodiments of the present disclosure. A general purpose processor may be a microprocessor, or the processor may be any conventional processor, and the like. The steps of the methods disclosed with reference to embodiments of the present disclosure may be directly implemented by a hardware decoding processor, or may be implemented by a combination of hardware and software modules in a decoding processor. A software module may be located on a tangible storage medium of the art, such as random access memory, flash memory, read only memory, programmable read only memory, electrically erasable programmable memory, a register, or the like. The storage medium is located in the memory 1540 and the processor 1510 reads the information in the memory 1540 and implements the steps of the above methods in conjunction with the processor hardware.

Alternatively, the interface circuit 1530 is configured to perform the receiving and transmitting steps processed by the data analysis network element, the user data control network element, and the main network element in the embodiments shown in FIG. 3, fig. 4, fig. 6, fig. 7, fig. 8, fig. 9, fig. 10, fig. 11A and FIG. 11B, FIG. 12A and FIG. 12B, FIG. 13, fig. 14 and FIG. fifteen.

The processor 1510 is configured to perform the steps processed by the data analysis network element, the user data control network element, and the main network element in the embodiments shown in FIG. 3, fig. 4, fig. 6, fig. 7, fig. 8, fig. 9, fig. 10, fig. 11A and FIG. 11B, FIG. 12A and FIG. 12B, FIG. 13, fig. 14 and FIG. fifteen.

In the foregoing embodiment, instructions stored in memory for execution by a processor may be implemented in the form of a computer program product. The computer program product may be stored in memory in advance, or may be downloaded and installed in memory in the form of software.

The computer program product includes one or more computer instructions. When computer program instructions are downloaded and executed on a computer, procedures or functions are generated in whole or in part according to embodiments of the present disclosure. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions may be stored on a computer-readable storage medium or may be transferred from a computer-readable storage medium to another computer-readable storage medium. For example, computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center over a wired connection (such as coaxial cable, optical fiber, or digital subscriber line (DSL) ) or wireless communication (for example, in infrared, radio or microwave bands). A computer-readable storage medium can be any usable media that can be stored on a computer, or a data storage device, such as a server or data center, that combines one or more usable media. The media used may be magnetic media (eg, a floppy disk, hard disk, or magnetic tape), optical media (eg, DVD), semiconductor media (eg, solid state dick, SSD), or the like.

According to an aspect, a computer-readable storage medium is provided. A computer-readable storage medium stores instructions. When executing the instructions, the analysis network element or a chip applied to the analysis network element is configured to execute S102, S111, S112, S103, S1012, S105, S108, and S109 in the embodiments; and/or may be used in another process performed by a data analysis network element or a chip applied to a data analysis network element in the technology described in this specification.

According to another aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores the instruction. When the instruction is executed, the main network element or the chip applied to the main network element is configured to execute S1014 and S1013 in the embodiments; and/or may be used in another process performed by the core network element or chip applied to the core network element in the technology described in this specification.

According to another aspect, a computer-readable storage medium is provided. A computer-readable storage medium stores instructions. When executing the instructions, the user data network element or the chip applied to the user data network element is configured to execute S104-1, S104, S106, S107, and S110 in the embodiments; and/or may be used in another process executed by a user data network element or a chip applied to a user data network element in the technology described in this specification.

According to another aspect, a computer-readable storage medium is provided. A computer-readable storage medium stores instructions. When executing the instructions, the data analysis network element or a chip applied to the data analysis network element is configured to execute S503, S504, S505, S507, S5042, S509, S5041, and S510 in the embodiments; and/or may be used in another process performed by a data analysis network element or a chip applied to a data analysis network element in the technology described in this specification.

According to another aspect, a computer-readable storage medium is provided. A computer-readable storage medium stores instructions. When executing the instructions, the data analysis network element or the chip applied to the data analysis network element is configured to execute S601, S603, S604, and S605 in the embodiments; and/or may be used in another process performed by a data analysis network element or a chip applied to a data analysis network element in the technology described in this specification.

According to another aspect, a computer-readable storage medium is provided. A computer-readable storage medium stores instructions. When executing the instructions, the first network element or the chip applied to the first network element is configured to execute S501, S502, and S506 in the embodiments; and/or may be used in another process performed by the first network element or chip applied to the first network element in the technology described in this specification.

The aforementioned computer-readable storage medium may include: any medium that can store program code, such as a USB flash drive, removable hard disk, read only memory, random access memory, magnetic disk, or optical disk.

According to an aspect, a computer program product is provided including an instruction. A computer program product stores instructions. When executing the instructions, the data analysis network element or a chip applied to the data analysis network element is configured to execute S102, S111, S112, S103, S1012, S105, S108, and S109 in the embodiments; and/or may be used in another process performed by a data analysis network element or a chip applied to a data analysis network element in the technology described in this specification.

According to another aspect, a computer program product is provided including an instruction. The computer program product stores instructions. When the instruction is executed, the main network element or the chip applied to the main network element is configured to execute S1014 and S1013 in the embodiments; and/or may be used in another process performed by the core network element or chip applied to the core network element in the technology described in this specification.

According to another aspect, a computer program product is provided including instructions. A computer program product stores instructions. When executing the instruction, the user data network element or the chip applied to the user data network element is configured to execute S104-1, S104, S106, S107, and S110 in the embodiments; and/or may be used in another process executed by a user data network element or a chip applied to a user data network element in the technology described in this specification.

According to another aspect, a computer program product is provided including instructions. A computer program product stores instructions. When executing the instructions, the data analysis network element or a chip applied to the data analysis network element is configured to execute S503, S504, S505, S507, S5042, S509, S5041, and S510 in the embodiments; and/or may be used in another process performed by a data analysis network element or a chip applied to a data analysis network element in the technology described in this specification.

According to another aspect, a computer program product is provided including instructions. A computer program product stores instructions. When executing the instructions, the data analysis network element or the chip applied to the data analysis network element is configured to execute S601, S603, S604, and S605 in the embodiments; and/or may be used in another process performed by a data analysis network element or a chip applied to a data analysis network element in the technology described in this specification.

According to another aspect, a computer program product is provided including instructions. A computer program product stores instructions. When executing the instructions, the first network element or the chip applied to the first network element is configured to execute S501, S502, and S506 in the embodiments; and/or may be used in another process performed by the first network element or chip applied to the first network element in the technology described in this specification.

According to one aspect, a chip is provided. The chip is applied to the data analysis network element. The chip includes one or more (including two) processors and an interface circuit. The interface circuit is connected to one or more (including two) processors via a communication link. The processor is configured to execute instructions for executing S102, S111, S112, S103, S1012, S105, S108, and S109 in the embodiments; and/or for use in another process performed by the data analysis network element in the technology described in this specification.

According to another aspect, a chip is provided. The chip is applied to the main network element. The chip includes one or more (including two) processors and an interface circuit. The interface circuit is connected to one or more (including two) processors via a communication link. The processor is configured to execute instructions for executing S1014 and S1013 in the embodiments; and/or for use in another process performed by the core network element in the technology described in this specification.

According to another aspect, a chip is provided. The chip is used in the user data network element. The chip includes one or more (including two) processors and an interface circuit. The interface circuit is connected to one or more (including two) processors via a communication link. The processor is configured to execute instructions for executing S104-1, S104, S106, S107, and S110 in the embodiments; and/or for use in another process executed by a user data web control in the technology described in this specification.

According to another aspect, a chip is provided. The chip is applied to the data analysis network element. The chip includes one or more (including two) processors and an interface circuit. The interface circuit is connected to one or more (including two) processors via a communication link. The processor is configured to execute instructions for executing S503, S504, S505, S507, S5042, S509, S5041, and S510 in the embodiments.

According to another aspect, a chip is provided. The chip is applied to the data analysis network element. The chip includes one or more (including two) processors and an interface circuit. The interface circuit is connected to one or more (including two) processors via a communication link. The processor is configured to execute instructions for executing S601, S603, S604, and S605 in the embodiments.

According to another aspect, a chip is provided. The chip is applied to the first network element. The chip includes one or more (including two) processors and an interface circuit. The interface circuit is connected to one or more (including two) processors via a communication link. The processor is configured to execute instructions for executing S501, S502, and S506 in the embodiments.

Additionally, the present disclosure further provides a communication system. The communication system includes an information processing device shown in FIG. 16-fig. 18, the communication device shown in FIG. 19-fig. 21 and the information processing apparatus shown in FIG. 22-fig. 24.

Additionally, the present disclosure further provides a communication system. The communication system includes: a device for determining exclusion information of the terminal shown in FIG. 25 used as a data analysis network element; and a device for determining exclusion information of the terminal shown in FIG. 26 used as the first network element. In particular, for specific steps performed by the data analysis network element and the first network element in the system, see specific descriptions in FIG. 25 and FIG. 26. Details are again not described here.

All or some of the above embodiments may be implemented in software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, the embodiments may be partially implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When computer program instructions are downloaded and executed on a computer, procedures or functions are generated in whole or in part according to embodiments of the present disclosure. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions may be stored on a computer-readable storage medium or may be transferred from a computer-readable storage medium to another computer-readable storage medium. For example, computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center over a wired connection (such as coaxial cable, optical fiber, or digital subscriber line). line (DSL)) or wireless communication (e.g., infrared, radio, or microwave). The media used can be magnetic media (such as a floppy disk, hard disk, or magnetic tape), optical media (such as a DVD), semiconductor media (such as a solid state dick, SSD for short), or the like. .

Although the present disclosure has been described with reference to the embodiments, in the course of implementing the present disclosure, one skilled in the art may understand and implement another variation of the disclosed embodiments by viewing the accompanying drawings, the disclosed contents, and the appended claims. In the claims, "comprising" does not exclude another component or another step, "a" or "one" does not exclude the case of a plurality. One processor or other block may implement several of the functions listed in the claims. Some measures are written in dependent claims that differ from each other, but this does not mean that these measures cannot be combined to obtain a better effect.

Although the present disclosure has been described with reference to specific features and their embodiments, it is obvious that various modifications and combinations can be made to them without departing from the scope of the present disclosure. Accordingly, the description and accompanying drawings are merely an exemplary description of the present disclosure as defined by the appended claims, and are construed as any or all modifications, variations, combinations, or equivalents that fall within the scope of the present disclosure. Obviously, a person skilled in the art can make various modifications and changes to the present disclosure without going beyond the spirit and scope of the present disclosure. The present disclosure is intended to cover these modifications and variations of the present disclosure, provided that they fall within the scope of protection defined by the following claims and their equivalent technologies.

Claims (40)

1. A method for transmitting terminal exception information, comprising the steps of: receive, using the data analysis network element, information about the behavior of the terminal device of the plurality of first terminal devices; determining, by means of the data analysis network element, expected network information about the behavior of the terminal device based on the information about the behavior of the terminal device of the plurality of first terminal devices; transmitting, by means of the data analysis network element, expected network information about the behavior of the terminal device to the first main network element; receive, by means of the data analysis network element, from the first main network element, information about the behavior of the terminal device related to the second terminal device and located in the first main network element, when the information about the behavior of the terminal device, related to the second terminal device and located in the first main network element does not correspond to the expected network information about the behavior of the end device; wherein the second terminal is one of the plurality of first terminals, or the second terminal is a device other than the plurality of first terminals; receiving, by means of the data analysis network element, from the second main network element information about the behavior of the terminal device corresponding to the second terminal device and located in the second main network element; determining, by the data analysis network element, exclusion information of the second terminal device based on the behavior information of the terminal device corresponding to the second terminal device and located in the first main network element, and the behavior information of the terminal device corresponding to the second terminal device and located in the second main network element; and transmitting, by means of the data analysis network element, exclusion information of the second terminal to the network element of the policy control function. 2. The method of claim 1, wherein the tag behavior information comprises tag identification information and one or more of the following information associated with the tag: location information, communication start time, communication end time, or packet size. 3. The method of claim 1, wherein the expected network behavior information of the tag comprises one or more of the following information: indication of the stationary state, the trajectory of the movement of the terminal device, the indicator of periodic communication, the duration of communication, the period of communication, or the planned communication time. 4. The method of claim 1, wherein the expected tag behavior network information comprises expected tag behavior network information corresponding to a base mobility management type network element, or expected tag behavior network information corresponding to a session control type base network element. . 5. The method of claim 1, wherein the expected tag behavior network information comprises expected tag behavior network information corresponding to an access and mobility control function network element, or tag expected behavior network information corresponding to a session control function network element. . 6. The method of claim 1, wherein the tag exception information comprises at least one of: exception type, exception identifier, or exception level. 7. The method according to p. 1, further comprising the step of which transmitting, by means of the data analysis network element, expected network information about the behavior of the terminal device to the user data network control element. 8. The method according to claim 1, further comprising the steps of: receive, by means of the data analysis network element, from the first main network element, the tag behavior information related to the first terminal device and located in the first main network element, when the tag behavior information related to the first terminal device and located in the first main network element network element does not correspond to the expected network information about the behavior of the end device received by the first main network element; receiving, by means of the data analysis network element, from the second main network element information about the behavior of the terminal device corresponding to the first terminal device and located in the second main network element; determining, by the data analysis network element, exclusion information of the first terminal device based on the behavior information of the terminal device corresponding to the first terminal device and located in the first main network element, and the behavior information of the terminal device corresponding to the first terminal device and located in the second main network element. 9. The method of claim 1, wherein the first primary network element is an access and mobility management function (AMF) network element and the second primary network element is a session management function (SMF) network element, or the first primary network element is a network element. an SMF element, and the second primary network element is an AMF network element. 10. The device for transmitting information on the exception of the terminal device, containing: at least one processor and a memory coupled to the at least one processor and storing program instructions for execution by said at least one processor, the program instructions causing, when executed by said at least one processor, the device to execute the method according to any one of claims 1 to 9. 11. A terminal device exclusion information transmission system, comprising: network element data analysis, configured to implement the method according to any one of paragraphs. 1-9; and a policy control function network element configured to receive terminal exclusion information from the data analysis network element. 12. A computer-readable storage medium that stores a program executable by at least one processor, and the program includes instructions for configuring a device containing the specified at least one processor, to implement the method according to any one of paragraphs. 1-9. 13. A method for receiving terminal exception information, comprising the steps of: receive, using the data analysis network element, information about the behavior of the terminal device of the plurality of first terminal devices; determining, by means of the data analysis network element, expected network information about the behavior of the terminal device based on the information about the behavior of the terminal device of the plurality of first terminal devices; transmitting, by means of the data analysis network element, expected network information about the behavior of the terminal device to the first main network element; receive, by means of the data analysis network element, from the first main network element, information about the behavior of the terminal device related to the second terminal device and located in the first main network element, when the information about the behavior of the terminal device, related to the second terminal device and located in the first main network element does not correspond to the expected network information about the behavior of the end device; wherein the second terminal is one of the plurality of first terminals, or the second terminal is a device other than the plurality of first terminals; receiving, by means of the data analysis network element, from the second main network element information about the behavior of the terminal device corresponding to the second terminal device and located in the second main network element; determining, by the analysis network element, tag exclusion information based on the tag behavior information corresponding to the second tag and located in the first core network element and the tag behavior information corresponding to the second tag and located in the second core network element element; and receiving, with the policy control function network element, terminal exclusion information from the data analysis network element. 14. The method of claim 13, further comprising the step of receiving, with the user data network element, expected network information about the behavior of the terminal device from the data analysis network element. 15. The method according to claim 13 or 14, further comprising the step of storing, with the user data network control, expected network information about the behavior of the terminal device as user subscription data.

Images