CN114503708A

CN114503708A - Message processing method, device, terminal and nonvolatile storage medium

Info

Publication number: CN114503708A
Application number: CN202080069575.2A
Authority: CN
Inventors: 许阳
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2020-01-06
Filing date: 2020-01-06
Publication date: 2022-05-13
Anticipated expiration: 2040-01-06
Also published as: CN114503708B; WO2021138772A1

Abstract

The invention discloses a message processing method, a message processing device, a terminal and a nonvolatile storage medium. Wherein, the method comprises the following steps: the terminal sends first information to a network side entity, wherein the first information comprises at least one of the following information: the Paging Cause parameter value, the characteristic information of the data packet, the service information and the mapping relation, wherein the mapping relation comprises the corresponding relation between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information; and the terminal receives the reply message of the network side entity. The invention solves the technical problem of low safety of message processing.

Description

Message processing method, device, terminal and nonvolatile storage medium

Technical Field

The present invention relates to the field of communications, and in particular, to a message processing method, apparatus, terminal, and non-volatile storage medium.

Background

At present, when downlink user plane data reaches a network side entity, the network side entity sends a Paging message (Paging) to search for a terminal, and the terminal needs to determine whether to respond to the Paging message when receiving the Paging message. And initiating a Non Access Stratum (NAS) message or an Access Stratum (AS) message if the paging message is determined to be responded, so AS to establish a user plane connection for transmitting data.

In order to effectively judge whether a reply is needed or not after a terminal receives a Paging message, a Paging Cause (Paging Cause) parameter is introduced into the Paging message to indicate which service is paged. However, since the Paging message is a plaintext message, one Paging message may have an identity (identity, abbreviated as ID) of a plurality of User equipments (User Equipment, abbreviated as UE), that is, one Paging message may be paged to a plurality of terminals at the same time, and different terminals may need to customize the received parameters of the Paging Cause differently, and the content carried in the Paging message is easily known by a third party in the transmission process of the Paging message, so that introduction of the parameters of the Paging Cause leakage of User privacy easily, and there is a technical problem of low security of message processing.

In view of the above technical problem of low security of message processing, no effective solution has been proposed at present.

Disclosure of Invention

The embodiment of the invention provides a message processing method, a message processing device, a terminal and a nonvolatile storage medium, which at least solve the technical problem of low safety of message processing.

According to an aspect of an embodiment of the present invention, a message processing method is provided. The method can comprise the following steps: the terminal sends first information to a network side entity, wherein the first information comprises at least one of the following information: the Paging Cause parameter value, the characteristic information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information; and the terminal receives the reply message of the network side entity.

Optionally, the receiving, by the terminal, a reply message of the network side entity includes: and the terminal receives a reply message sent by the network side entity for updating the first information.

Optionally, the reply message comprises at least one of: the network side entity updates the first information successfully; the network side entity receives the parameter in the first information, wherein the received result may include the parameter received by the network side entity and/or an unacceptable parameter in the first information; and the network side entity updates the first information to obtain updated information.

Optionally, the first information is one or two of the following data: the value of the Paging Cause parameter, the characteristic information of the data packet, and the service information, wherein the second information corresponding to the first information is determined by the network side entity or sent to the network side entity by the application server, and the second information is data of at least one of the following data: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

Optionally, the second information is determined according to the user subscription information.

Optionally, the user subscription information is provided by a user data management UDM or a policy control function PCF.

Optionally, the second information is sent to the terminal by the network side entity in a reply message.

Optionally, the terminal sends the first information to the network side entity, including: and the terminal sends the first information to the network side entity through the non-access stratum NAS message or the access stratum AS layer message.

Optionally, the NAS message is a registration request message or a protocol data unit PDU session modification request, and the network side entity is a core network element.

Optionally, the first information is updated by a network element of the core network.

Optionally, the first information is sent by a network element of the core network to a base station of the network side entity.

Optionally, the AS layer message is a radio resource control recovery RRC message, and the network side entity is a base station.

Optionally, the first information is updated by the base station.

Optionally, the first information is sent by the base station to a core network element of the network side entity.

Optionally, the method further comprises: the terminal and the application server negotiate the first information through the user plane connection.

Optionally, the content of the first information is changed periodically or non-periodically with a request message of the terminal.

Optionally, values of Paging Cause parameters carried in reply messages received by different terminals are different.

According to an aspect of the embodiment of the present invention, another message processing method is also provided. The method can comprise the following steps: the terminal sends a terminal identification to a network side entity; the terminal receives a reply message sent by the network side entity based on the terminal identification, wherein the reply message carries first information, and the first information comprises at least one of the following information: the Paging Cause parameter value, the feature information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the following mapping relationship between at least two of the following corresponding relationships between any two data: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

Optionally, the sending, by the terminal, the terminal identifier to the network side entity includes: and the terminal sends the terminal identification to the network side entity through the non-access stratum NAS message.

Optionally, the NAS message is a registration request message, and the network side entity is a core network element.

Optionally, the first information is obtained by the core network element according to the terminal identifier, and the first information is sent to the base station of the network side entity by the core network element.

Optionally, the method further comprises: the terminal sends a first indication to the network side entity, wherein the first indication is used for informing the network side entity that the terminal needs to acquire first information.

Optionally, the first information is sent to the network-side entity by the application server.

Optionally, the first information is user subscription information.

Optionally, the first information sent by the network side entity and received by the terminal is one or two of the following data: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information, the method also comprises the following steps: the terminal determines second information corresponding to the first information, or receives the second information corresponding to the first information and sent by the application server, wherein the second information is at least one of the following data: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

Optionally, the terminal sends the second information to the network side entity through another NAS message.

Optionally, the another NAS message is a registration request complete message.

According to an aspect of the embodiment of the present invention, another message processing method is also provided. The method can comprise the following steps: the network side entity acquires first information sent by a terminal, wherein the first information comprises at least one of the following information: the Paging Cause parameter value, the characteristic information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information; and the network side entity sends a reply message to the terminal based on the first information.

Optionally, the sending, by the network entity, the reply message to the terminal based on the first information includes: and the network side entity updates the first information and sends the obtained reply message to the terminal.

Optionally, the first information is one or two of the following data: the value of the Paging Cause parameter, the characteristic information of the data packet, and part of the information in the service information, the method further comprises: the network side entity determines second information corresponding to the first information, or receives the second information corresponding to the first information, wherein the second information is determined by the application server, and the second information is at least one of the following data: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

Optionally, the user data management UDM or the policy control function PCF provides the user subscription information.

Optionally, the network side entity sends the second information to the terminal in a reply message.

Optionally, the acquiring, by the network entity, the first information sent by the terminal includes: the network side entity acquires first information sent by the terminal through a non-access stratum (NAS) message or an Access Stratum (AS) layer message.

Optionally, the core network element updates the first information.

Optionally, the core network element sends the first information to a base station of the network side entity.

Optionally, the base station updates the first information.

Optionally, the base station sends the first information to a core network element of the network side entity.

Optionally, values of the Paging Cause parameter carried in the reply message sent by the network side entity to different terminals are different.

According to an aspect of the embodiment of the present invention, another message processing method is also provided. The method can comprise the following steps: a network side entity acquires a terminal identifier sent by a terminal; the network side entity sends a reply message to the terminal based on the terminal identifier, wherein the reply message carries first information, and the first information comprises at least one of the following information: the Paging Cause parameter value, the characteristic information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

Optionally, the acquiring, by the network entity, the terminal identifier sent by the terminal includes: and the network side entity acquires the terminal identification sent by the terminal through the non-access stratum NAS message.

Optionally, the method further comprises: and the core network element acquires the first information according to the terminal identifier and sends the first information to the base station of the network side entity.

Optionally, the method further comprises: the network side entity acquires a first indication sent by the terminal, wherein the first indication is used for informing the network side entity that the terminal needs to acquire first information.

Optionally, the network side entity obtains the first information sent by the application server.

Optionally, the first information is user subscription information.

Optionally, the first information sent by the network entity to the terminal is one or two of the following data: the value of the Paging Cause parameter, the characteristic information of the data packet, and the service information, wherein the second information corresponding to the first information is determined by the terminal or sent to the terminal by the application server, and the second information is at least one of the following data: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

Optionally, the network entity obtains second information sent by the terminal through another NAS message.

Optionally, the another NAS message is a registration request complete message.

According to an aspect of the embodiment of the present invention, another message processing method is also provided. The method can comprise the following steps: the terminal sends first information to a network side entity, wherein the first information is periodically or aperiodically dynamically updated information; the terminal receives a reply message sent by the network side entity based on the first information; and the terminal receives a Paging message initiated by a network side entity, wherein the value of a Paging reason Paging Cause parameter carried in the Paging message is determined based on the first information.

Optionally, the first information comprises at least one of: the Paging Cause parameter value, the characteristic information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

According to an aspect of the embodiment of the invention, a terminal is also provided. The terminal may include: the first signal transmitting circuit is configured to transmit first information to a network side entity, where the first information includes at least one of: the Paging Cause parameter value, the characteristic information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information; and the first signal receiving circuit is used for receiving a reply message sent by the network side entity based on the first information.

According to an aspect of the embodiment of the present invention, another terminal is also provided. The terminal may include: the second signal sending circuit is used for sending the terminal identification to the network side entity; a second signal receiving circuit, configured to receive a reply message sent by a network entity based on a terminal identifier, where the reply message carries first information, and the first information includes at least one of the following: the Paging Cause parameter value, the characteristic information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

According to an aspect of the embodiment of the present invention, another terminal is also provided. The terminal may include: the third signal sending circuit is used for sending first information to the network side entity, wherein the first information is periodically or aperiodically dynamically updated information; a third signal receiving circuit, configured to receive a reply message sent by the network entity based on the first information; and receiving a Paging message initiated by a network side entity, wherein the value of a Paging reason Paging Cause parameter carried in the Paging message is determined based on the first information.

According to an aspect of the embodiment of the present invention, a message processing apparatus is also provided. The apparatus may include: a first sending unit, configured to enable the terminal to send first information to the network side entity, where the first information includes at least one of the following: the Paging Cause parameter value, the characteristic information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information; a first receiving unit, configured to enable the terminal to receive a reply message of the network side entity.

Optionally, the first receiving unit includes: and the receiving module is used for enabling the terminal to receive the reply message sent by the network side entity for updating the first information.

Optionally, the first sending unit includes: and the sending module is used for enabling the terminal to send the first information to the network side entity through the non-access stratum NAS message or the access stratum AS layer message.

Optionally, the first information is updated by the base station.

Optionally, the apparatus further comprises: and the negotiation unit is used for enabling the terminal and the application server to negotiate the first information through the user interface connection.

According to an aspect of the embodiment of the present invention, another message processing apparatus is also provided. The device also includes: the second sending unit is used for sending the terminal identification to the network side entity by the terminal; a second receiving unit, configured to enable the terminal to receive a reply message sent by the network side entity based on the terminal identifier, where the reply message carries first information, and the first information includes at least one of the following: the Paging Cause parameter value, the feature information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the following mapping relationship between at least two of the following corresponding relationships between any two data: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

Optionally, the second sending unit includes: and the sending module is used for enabling the terminal to send the terminal identification to the network side entity through the non-access stratum NAS message.

Optionally, the apparatus further comprises: and a third sending unit, configured to enable the terminal to send a first instruction to the network side entity, where the first instruction is used to notify the network side entity that the terminal needs to acquire the first information.

Optionally, the first information is user subscription information.

Optionally, the first information sent by the network side entity and received by the terminal is one or two of the following data: the value of the Paging Cause parameter, the characteristic information of the data packet, the service information, the device also includes: a first determining unit, configured to enable the terminal to determine second information corresponding to the first information, or receive the second information corresponding to the first information, where the second information is data of at least one of the following data: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

Optionally, the apparatus further comprises: and a fourth sending unit, configured to enable the terminal to send the second information to the network side entity through another NAS message.

Optionally, the another NAS message is a registration request complete message.

According to an aspect of the embodiment of the present invention, another message processing apparatus is also provided. The device also includes: a first obtaining unit, configured to enable a network entity to obtain first information sent by a terminal, where the first information includes at least one of: the Paging Cause parameter value, the characteristic information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information; and a fifth sending unit, configured to enable the network side entity to send the reply message to the terminal based on the first information.

Optionally, the fifth sending unit includes: and the first updating module is used for updating the first information by the network side entity and sending the obtained reply message to the terminal.

Optionally, the first information is one or two of the following data: the value of the Paging Cause parameter, the characteristic information of the data packet, and part of the information in the service information, the apparatus further includes: a second determining unit, configured to enable the network side entity to determine second information corresponding to the first information, or receive second information corresponding to the first information determined by the application server, where the second information is data of at least one of the following data: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

Optionally, the apparatus is further configured to cause the user data management UDM or the policy control function PCF to provide the user subscription information.

Optionally, the fifth sending unit is configured to enable the network side entity to send the second information to the terminal in a reply message.

Optionally, the first obtaining unit includes: the first obtaining module is used for enabling the network side entity to obtain first information sent by the terminal through a non-access stratum (NAS) message or an Access Stratum (AS) layer message.

Optionally, the apparatus further comprises: and the first updating unit is used for enabling the core network element to update the first information.

Optionally, the apparatus further comprises: a sixth sending unit, configured to enable the core network element to send the first information to the base station of the network side entity.

Optionally, the apparatus further comprises: and the second updating unit is used for enabling the base station to update the first information.

Optionally, the apparatus further comprises: a seventh sending unit, configured to enable the base station to send the first information to a core network element of the network side entity.

According to an aspect of the embodiment of the present invention, another message processing apparatus is also provided. The device also includes: a second obtaining unit, configured to enable a network entity to obtain a terminal identifier sent by a terminal; an eighth sending unit, configured to enable the network side entity to send a reply message to the terminal based on the terminal identifier, where the reply message carries first information, and the first information includes at least one of the following: the Paging Cause parameter value, the characteristic information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

Optionally, the second obtaining unit includes: and the second acquisition module is used for enabling the network side entity to acquire the terminal identifier sent by the terminal through the non-access stratum NAS message.

Optionally, the apparatus further comprises: a third obtaining unit, configured to enable a core network element to obtain the first information according to the terminal identifier; and a ninth sending unit, configured to send the first information to a base station of the network side entity.

Optionally, the apparatus further comprises: and a fourth obtaining unit, configured to enable a network entity to obtain a first instruction sent by the terminal, where the first instruction is used to notify the network entity that the terminal needs to obtain the first information.

Optionally, the apparatus further comprises: and a fifth obtaining unit, configured to enable the network side entity to obtain the first information sent by the application server.

Optionally, the first information is user subscription information.

Optionally, the apparatus further comprises: and a sixth obtaining unit, configured to obtain, by the network entity, second information sent by the terminal through another NAS message.

Optionally, the another NAS message is a registration request complete message.

According to an aspect of the embodiment of the present invention, another message processing apparatus is also provided. The device also includes: a tenth sending unit, configured to enable the terminal to send the first information to the network entity, where the first information is dynamically updated periodically or aperiodically; a third receiving unit, configured to enable the terminal to receive a reply message sent by the network side entity based on the first information; and a fourth receiving unit, configured to enable the terminal to receive a Paging message initiated by the network side entity, where a value of a Paging Cause parameter carried in the Paging message is determined based on the first information.

According to an aspect of the embodiment of the present invention, there is also provided a nonvolatile storage medium. The nonvolatile storage medium comprises a stored program, wherein the device where the nonvolatile storage medium is located is controlled to execute the message processing method of the embodiment of the invention when the program runs.

According to an aspect of the embodiment of the present invention, there is also provided a communication system. The communication system is used for running a program, wherein the program executes the message processing method of the embodiment of the invention when running.

According to an aspect of the embodiment of the invention, an electronic device is also provided. The electronic device may include a memory in which a computer program is stored and a processor configured to execute the computer program to perform the claimed message processing method of the embodiment of the present invention.

In the embodiment of the present invention, a terminal sends first information to a network side entity, where the first information includes at least one of the following: the Paging Cause parameter value, the characteristic information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information; and the terminal receives the reply message of the network side entity. That is to say, the embodiment of the present invention introduces the set first information, so as to implement the broadcast of the value of the Paging Cause parameter of the terminal user granularity, and avoid that the value of the Paging Cause parameter in the Paging message is established by standardization, so that a third-party attacker cannot determine what the specific service content corresponds to the value of the Paging Cause parameter in the triggered Paging message, thereby implementing the technical effect of improving the security of message processing, and further solving the technical problem of low security of message processing.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:

FIG. 1 is a flow chart of a message processing method according to an embodiment of the invention;

FIG. 2 is a flow diagram of another message processing method according to an embodiment of the invention;

FIG. 3 is a flow diagram of another message processing method according to an embodiment of the invention;

FIG. 4 is a flow diagram of another message processing method according to an embodiment of the invention;

FIG. 5 is a flow diagram of another message processing method according to an embodiment of the invention;

fig. 6 is an interaction diagram of a paging procedure in a CM-IDLE state of a terminal according to a related art;

fig. 7 is an interaction diagram of a paging procedure in an RRC-Inactive state of a terminal according to the related art;

fig. 8 is an interactive diagram illustrating a Paging procedure of a terminal in a CM-IDLE state to carry a Paging Cause parameter according to a related art;

fig. 9 is an interactive diagram illustrating a Paging procedure with a Paging Cause parameter when a terminal is in an RRC-Inactive state according to the related art;

FIG. 10 is an interaction diagram of a method for updating first information through a NAS message according to an embodiment of the invention;

fig. 11 is an interaction diagram of a method for updating first information through an AS message according to an embodiment of the present invention;

fig. 12 is an interaction diagram of a method for transmitting first information through NAS messages according to an embodiment of the present invention;

fig. 13 is an interaction diagram of a method for deriving a value of a Paging Cause parameter according to first information when a terminal is in a CM-IDLE state according to an embodiment of the present invention;

fig. 14 is an interaction diagram of a method for deriving a value of a Paging Cause parameter according to first information when a terminal is in an RRC-Inactive state according to an embodiment of the present invention;

FIG. 15 is a schematic diagram of a terminal according to an embodiment of the present invention;

fig. 16 is a schematic diagram of another terminal according to an embodiment of the present invention;

fig. 17 is a schematic diagram of another terminal according to an embodiment of the present invention;

fig. 18 is a schematic diagram of a message processing apparatus according to an embodiment of the present invention;

FIG. 19 is a schematic diagram of another message processing apparatus according to an embodiment of the present invention;

FIG. 20 is a schematic diagram of another message processing apparatus according to an embodiment of the present invention; and

fig. 21 is a schematic diagram of another message processing apparatus according to an embodiment of the present invention.

Detailed Description

In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

Example 1

In accordance with an embodiment of the present invention, there is provided a method embodiment of a message processing method, it being noted that the steps illustrated in the flowchart of the figure may be performed in a computer system such as a set of computer-executable instructions and that, although a logical order is illustrated in the flowchart, in some cases the steps illustrated or described may be performed in an order different than that presented herein.

The message processing method of the embodiment of the present invention is described below from the terminal side.

Fig. 1 is a flowchart of a message processing method according to an embodiment of the present invention. As shown in fig. 1, the method comprises the steps of:

step S102, the terminal sends first information to the network side entity, and the first information comprises at least one of the following: the value of Paging Cause parameter, the characteristic information of data packet, the service information and the mapping relation.

In the technical solution provided in the foregoing step S102 of the present application, the mapping relationship includes a corresponding relationship between any two of the following data: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

In this embodiment, first information is introduced, and a terminal sends the first information to a network side entity, where the content of the first information may be user-granularity content obtained on demand, and may include at least one of the following: the value of Paging Cause parameter, the characteristic information of data packet, the service information and the mapping relation.

The network-side entity in this embodiment may be a third Generation Partnership Project (3 GPP) network, including a core network element and/or a base station (RAN), and may send a paging message to the terminal. The Paging Cause parameter can enhance the Paging message, and can be carried by the Paging message to indicate to the terminal which service is to send out Paging, that is, which service data packet reaches the network side entity, and the terminal can determine what service triggers the Paging message according to the value of the Paging Cause parameter, so as to further determine whether to respond to the Paging message. The value of the Paging Cause parameter may be 101, 102, 103, 104, 105, etc., and is not limited herein.

The downlink Data (DL Data) packet of this embodiment may be a downlink Data packet sent by an application server to a network side entity, where the characteristic information of the Data packet is information carried in the Data packet, and the specific content of the Paging Cause parameter may be obtained by the network side entity according to the characteristic information of the Data packet, for example, according to the content in a Type of Service (ToS) field in an Internet Protocol (IP) Data packet header, where the content in the ToS field is sometimes also a Differentiated Service Code Point (DSCP) value, and is added by the application server, that is, the characteristic information of the Data packet may indicate what the Service corresponding to the Data packet is, and the characteristic information of different Data packets may indicate different Services or different attributes in the same Service (for example, the originator of the voice call), wherein ToS takes on values of 1, 2, 3, 4, and so on, without any limitation here.

The service information of this embodiment may be related information of a service initiator, for example, including a calling phone number, an IP Multimedia Subsystem (IMS) voice-phone number, a short message, internet data, and the like, which is not limited herein, where a data packet may be triggered by IMS voice.

The mapping relationship of this embodiment may include a correspondence relationship between any two of the following data: the value of the Paging Cause parameter, the feature information of the data packet, and the service information, for example, a corresponding relationship between the value of the Paging Cause parameter carried in the Paging message and the service information (including a service originator, such as a calling phone number), or a corresponding relationship between the value of the parameter carried in the Paging message and the feature information of the data packet sent by the application server, as shown in table 1.

TABLE 1 contents and mapping relations included in the first information

Characteristic information of data packet	Value of the Paging Cause parameter	Service information
ToS value is 1	101	IMS voice-telephone number x1
ToS value is 2	102	IMS voice-telephone number x2
ToS value is 3	103	IMS voice-other numbers
ToS value is 4	104	Short message
ToS value or others	105	Data on internet

Table 1 shows an example of content and a mapping relationship included in first information according to an embodiment of the present invention, where the first information includes a value of a Paging Cause parameter, packet feature information, and service information, where a ToS value of the packet feature information may be 1, a value of a corresponding Paging Cause parameter is 101, and the corresponding service information may be an IMS voice-telephone number x 1; the ToS value of the data packet feature information may be 2, the value of the corresponding Paging Cause parameter is 103, and the corresponding service information may be an IMS voice-telephone number x 2; the ToS value of the data packet feature information can be 3, the value of the corresponding Paging Cause parameter is 103, and the corresponding service information can be IMS voice-other telephone numbers; the ToS value of the data packet characteristic information can be 4, the value of the corresponding Paging Cause parameter is 104, and the corresponding service information can be a short message; the ToS value of the data packet feature information may be other, the value of the corresponding Paging Cause parameter is 105, and the corresponding service information may be internet data.

It should be noted that the service information of this embodiment may include one or more service identifiers, i.e., different services (including different telephone numbers, contacts, packets, etc.) may be represented by service identifiers. The 5 service information (IMS voice-phone number x1, IMS voice-phone number x2, IMS voice-phone number x2, short message and internet data) as in table 1 can be represented by 5 different service identities.

The mapping relationship can be stored in the terminal and the network side entity, so that when a data packet received by the network side entity contains a specific ToS value, the value of the corresponding Paging Cause parameter is put into a page and broadcasted through a Paging message, and the corresponding service information can be obtained according to the value of the Paging Cause parameter after the corresponding terminal receives the Paging message.

The terminal of this embodiment may send, to the network-side entity, first information including at least one of: for example, the terminal may only notify the corresponding relationship between the two rows on the left side of table 1 to the 3GPP network (core network element and/or base station), and the service information itself is retained.

Step S104, the terminal receives the reply message of the network side entity.

In the technical solution provided in step S104 of the present application, when the terminal sends the first information to the network side entity, the network side entity sends a reply message to the terminal based on the first information, where the reply message may be a reply message obtained by the network side entity performing corresponding processing on the first information, for example, a reply message obtained by updating the first information, and the reply message may also carry information related to the first information.

When the Paging message is triggered, the value of the Paging Cause parameter can be determined and determined according to the characteristic information of the data packet. Optionally, the embodiment further determines a value of the Paging Cause parameter in combination with the content of the first information.

As an optional example, the IDLE connection management state (CM-IDLE state) is that the connection between the terminal and the base station and the N2 connection between the base station and the core network element are both released, the connection management state (RRC-Inactive state) is that the connection between the terminal and the base station is released, but the N2 connection of the terminal is not released, and in the case that the terminal is in the IDLE connection management state (CM-IDLE state) or in the connection management state (RRC-Inactive state), the application server sends a data packet carrying a DSCP value to the core network element, the core network element derives a value of the Paging Cause parameter according to the first information and the DSCP value, for example, the first information includes a mapping relationship between the DSCP value and the value of the Paging Cause parameter, the core network element may determine a value of the Paging Cause parameter based on the mapping relationship and the DSCP value, and then the core network element may send a Paging message carrying the value of the Paging Cause parameter to the base station, the base station sends the Paging message carrying the value of the Paging Cause parameter to the terminal, so that the terminal can know that the corresponding service information is available according to the mapping relation between the value of the Paging Cause parameter in the stored first information and the service information after receiving the Paging message, and further determine whether to reply to the Paging message. The method comprises the steps that under the condition that a terminal is in a CM-IDLE state, the terminal sends a reply message to a core network element, wherein the reply message can be a Service Request (Service Request) message, and under the condition that the terminal is in an RRC-Inactive state, the terminal sends the reply message to a base station, wherein the reply message can be a line resource control recovery Request (RRC Resume Request) message.

As another optional example, when the terminal is in a connection management state (RRC-Inactive state), the application server sends a data packet carrying a DSCP value to the core network element, the core network element sends a Paging message carrying the DSCP value to the base station, the base station derives a value of the Paging Cause parameter according to the first information and the DSCP value, for example, the first information includes a mapping relationship between the DSCP value and the value of the Paging Cause parameter, the base station may determine the value of the Paging Cause parameter based on the mapping relationship and the DSCP value, and then the base station sends the Paging message carrying the value of the Paging Cause parameter to the terminal, so that after the terminal receives the Paging message, the terminal can know that the corresponding service information is obtained according to the mapping relationship between the value of the Paging Cause parameter and the service information, and then determine whether to reply to the Paging message, and sends a reply message, which may be an RRC Resume Request message, to the base station.

It should be noted that the terminal in this embodiment may be a User Equipment (UE) having a wireless communication function, such as a smart phone (for example, a mobile phone using an Android system or a mobile phone using an IOS system), a tablet computer, an intelligent wearable device (for example, an Augmented Reality (AR) device, a Virtual Reality (VR) device, or a smart watch), and the like, which is not limited herein.

In the related art, in order to effectively judge whether a reply is required or not after a terminal receives a Paging message, a Paging Cause parameter is introduced into the Paging message for indicating which service triggers the Paging message, but the Paging Cause parameter causes safety and privacy problems because the Paging message is a plaintext message. In this embodiment, the terminal sends first information to the network entity, where the first information includes at least one of the following: the Paging Cause parameter value, the characteristic information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information; and the terminal receives the reply message of the network side entity. That is to say, the embodiment introduces the set first information, and implements the broadcast of the value of the Paging Cause parameter of the terminal user granularity, while avoiding that the value of the Paging Cause parameter in the Paging message is established by standardization, so that a third-party attacker cannot determine what the specific service content corresponding to the value of the Paging Cause parameter in the triggered Paging message is, thereby implementing the technical effect of improving the security of message processing, and further solving the technical problem of low security of message processing.

The above steps of this embodiment are further explained below.

As an optional implementation manner, the receiving, by the terminal, the reply message of the network side entity includes: and the terminal receives a reply message sent by the network side entity for updating the first information.

In this embodiment, the first information sent by the terminal to the network-side entity may be updated except for the case where the content of the first information changes, and the first information may be updated frequently on the terminal side or the network-side entity side. Optionally, when the terminal receives a reply message from the network-side entity, the content of the first information is updated by the network-side entity, which may be that the network-side entity updates the content of the first information periodically or aperiodically, and particularly, the value of the Paging Cause parameter in the first information is updated by the network-side entity, so as to obtain the reply message, and the terminal receives the reply message sent by the network-side entity after the first information is updated by the network-side entity, so that the content of the first information can be changed continuously with each update of the first information, and a third-party attacker cannot determine what the specific time service content corresponding to the value of the Paging Cause parameter in the Paging message is, thereby protecting the privacy of the user, avoiding the privacy leakage of the user, and further achieving a technical effect of improving the security of message processing.

As an optional implementation, the reply message includes at least one of: the network side entity updates the first information successfully; the network side entity receives the parameter in the first information, wherein the received result may include the parameter received by the network side entity and/or an unacceptable parameter in the first information; and the network side entity updates the first information to obtain updated information.

In this embodiment, the reply message sent by the network entity to update the first information may be a result of the network entity confirming whether the first information is successfully updated, for example, the first information is successfully updated or the first information is not successfully updated; the parameter receiving result may also be a result of the network-side entity receiving the parameter in the first information, where the parameter may include a parameter received by the network-side entity and/or an unacceptable parameter in the first information, for example, the terminal includes the first information in the uplink NAS, and the network-side entity may return to the terminal which parameter in the first information is received, so as to determine the parameter received by the network-side entity and/or the unacceptable parameter, and further may return to the second information corresponding to the first information; the reply message of this embodiment may also be update information obtained by updating the first information by the network side entity, for example, at least one of a value of a Paging Cause parameter, feature information of a data packet, service information, and mapping relationship in the first information is updated, so that the content of the first information is changed, and the first information after the content is changed is determined as the update information.

The second information corresponding to the first information described above of this embodiment is further described below.

As an optional implementation, the first information is one or two of the following data: the value of the Paging Cause parameter, the characteristic information of the data packet, and the service information, wherein the second information corresponding to the first information is determined by the network side entity or sent to the network side entity by the application server, and the second information is data of at least one of the following data: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

In this embodiment, the first information sent by the terminal to the network side entity may include only one or two data of the value of the Paging Cause parameter, the feature information of the data packet, and the service information, that is, the terminal does not send all the value of the Paging Cause parameter, the feature information of the data packet, and the service information to the network side entity, the second information corresponding to the first information may be determined by the network side entity itself according to the content of the received first information, and the data included in the second information and the data included in the first information have an association relationship, where the association relationship may enable the second information to correspond to the first information. Optionally, the second information in this embodiment is determined by the core network element or the base station according to the content of the first information, where the second information may include at least one of a value of the Paging Cause parameter, characteristic information of the data packet, and service information, and the second information and the first information jointly form the value of the Paging Cause parameter, the characteristic information of the data packet, and the service information.

For example, the first information includes a value of a paginghouse parameter, the network side entity determines feature information and service information of a data packet corresponding to the value of one or more paginghouse parameters, and the network side entity determines the feature information and service information of the data packet and a corresponding relationship with the value of the paginghouse parameter as the second information; the first information comprises the characteristic information of the data packet, and the network side entity determines the value and the service information of the Paging Cause parameter corresponding to the characteristic information of one or more data packets, and then the network side entity determines the value and the service information of the Paging Cause parameter and the corresponding relation with the characteristic information of the data packet as the second information; the first information comprises service information, and the network side entity determines the value of a Paging Cause parameter and the characteristic information of a data packet corresponding to one or more service information, and then the network side entity determines the value of the Paging Cause parameter, the characteristic information of the data packet and the corresponding relation with a service identifier as the second information; the first information comprises values of Paging Cause parameters and characteristic information of data packets, and the network side entity determines service information corresponding to the values of one or more Cause parameters and the characteristic information of one or more data packets, and determines the service information and a corresponding relation between the values of one or more Cause parameters and the characteristic information of one or more data packets as the second information; the first information comprises values of the Paging Cause parameters and service information, and the network side entity determines values of one or more Paging Cause parameters and characteristic information of a data packet corresponding to one or more service identifiers, and then determines the characteristic information of the data packet and a corresponding relation between the values of the one or more Paging Cause parameters and the one or more service identifiers as the second information; the first information includes feature information and service information of the data packet, and the network side entity determines a value of a Paging Cause parameter corresponding to the feature information of one or more data packets and one or more service information, and then the network side entity determines the Paging Cause parameter and a corresponding relationship between the feature information of one or more data packets and one or more service identifiers as the second information.

Optionally, in this embodiment, the second information may also be provided to the network-side entity by the application server through the user plane connection.

It should be noted that, in this embodiment, two or more of the service information, the value of the Paging Cause parameter, and the value of the packet feature information may be the same value. In this case, two or three parameters may be combined, that is, the first information or the second information only provides one or two parameters, but essentially a specific value of one parameter corresponds to a specific service, packet feature information, or Paging Cause parameter value. For example, when the DSCP is 001, the service is represented, the value of the Paging Cause parameter and the value of the DSCP may both be the values, and the terminal receives the value and automatically knows that the voice service is the corresponding voice service.

As an optional implementation manner, the second information is determined according to the subscription information of the user.

In this embodiment, the user subscription information may be obtained by a core network element, and the second information is determined by the obtained user subscription information. Optionally, the User subscription information in this embodiment is stored in a network element of the core network, for example, in User Data Management (UDM) or Policy Control Function (PCF), and may be obtained from the UDM or the PCF in a registration process through an Access and Mobility Management Function (AMF) or a Session Management Function (SMF), so as to determine the second information according to the User subscription information.

As an alternative embodiment, the user subscription information is provided by a user data management UDM or a policy control function PCF.

In this embodiment, the user subscription information may be provided by the UDM or the PCF, and the users of different terminals may correspond to different user subscription information, for example, different International Mobile Subscriber identity numbers (IMSI) correspond to different user subscription information.

As an optional implementation manner, the second information is sent to the terminal by the network entity in a reply message.

In this embodiment, when the second information is determined by the network side entity or sent to the network side entity by the application server, the terminal receives the second information sent by the network side entity, and may be carried in a reply message sent to the terminal by the network side entity, so as to send the reply message to the terminal.

As an optional implementation manner, the sending, by the terminal, the first information to the network side entity includes: and the terminal sends the first information to the network side entity through the non-access stratum NAS message or the access stratum AS layer message.

In this embodiment, when the terminal sends the first information to the network side entity, the terminal may send the first information to the network side entity through an NAS message, for example, the terminal sends the NAS message to the network side entity, where the NAS message carries content of the first information; optionally, the terminal sends the first information to the network side entity through an access stratum AS layer message, for example, the terminal sends an AS message to the network side entity, where the AS message carries content of the first information.

As an optional implementation manner, the NAS message is a registration request message or a protocol data unit PDU session modification request, and the network side entity is a core network element.

In this embodiment, in a case that the terminal sends the first information to the network side entity through the NAS message, the NAS message may be a Registration Request (Registration Request) message or a PDU session modification or establishment Request message, and the network side entity is a core network element, that is, the terminal sends the first information to the core network element through the Registration Request message or the PDU session modification or establishment Request.

As an optional implementation, the first information is updated by a network element of the core network.

In this embodiment, when the terminal sends the first information to the core network element through the registration request message or the PDU session modification request, the core network element may update the first information, and optionally, update the content of the first information through the AMF or the SMF, so that the first information is updated through the NAS message (such as the registration request), and the network entity further sends the updated information to the terminal.

As an optional implementation manner, the first information is sent by a core network element to a base station of the network side entity.

In this embodiment, when the terminal sends the first information to the core network element, the core network element may further send the first information to the base station, and optionally, the content of the first information may be sent to the base station by the core network element using an N2 message, for example, the core network element sends an N2 message to the base station, and the content of the first information may be carried by the N2 message.

AS an optional implementation manner, the AS layer message is a radio resource control recovery RRC message, and the network side entity is a base station.

In this embodiment, in a case that the terminal sends the first information to the network side entity through the AS message, the AS layer message may be an RRC message, where the RRC message includes an RRC Setup Complete (RRC Setup Complete) message, that is, the terminal sends the first information to the base station through the RRC message.

As an alternative, the first information is updated by the base station.

In this embodiment, when the first information is sent from the core network element to the base station of the network side entity, the base station may update the first information, so AS to achieve the purpose of updating the first information through the AS message, and the network side entity further sends a reply message to the terminal.

As an optional implementation manner, the first information is sent by the base station to a core network element of the network side entity.

In this embodiment, in the case that the terminal sends the first information to the base station of the network side entity, the base station may also send the first information to the core network element, for example, the base station sends the content of the first information to the core network element through the N2 interface.

In this embodiment, when the first information is sent to the core network element of the network side entity by the base station, the core network element may update the first information, so that the base station may also send the content of the first information to the core network element and update the content, and the network side entity further sends a reply message to the terminal.

As an optional implementation, the method further comprises: the terminal and the application server negotiate the first information through the user plane connection.

In this embodiment, before the terminal sends the first information to the network side entity through the NAS message or the AS message, the terminal and the application server may negotiate content of the first information through user plane connection, so AS to obtain content of the first information of the user granularity AS needed, where the user plane connection is also user plane secure connection, that is, specific content of the first information may be negotiated between the terminal and the application server, and may guarantee security through encrypted connection, and may notify the 3GPP network of the specific content of the first information through the NAS message or the AS message for use.

As an alternative embodiment, the content of the first information is changed periodically or non-periodically with the request message of the terminal.

In this embodiment, the content of the first information may be changed periodically or aperiodically along with a request message sent by the terminal to the network side entity, so that the terminal may update the content of the first information periodically or aperiodically along with the request message of the terminal, that is, the content of the first information may be changed with each update of the first information, especially, the value of the Paging Cause parameter in the first information may be changed with each update of the first information, so that a third-party attacker cannot determine what the specific service content corresponding to the value of the Paging Cause parameter in the plaintext message is, and thus, the plaintext information broadcast in the Paging message may be prevented from being known by the third party by multiple updates, the privacy of the user is protected, and the security of processing the message is improved.

As an optional implementation manner, values of Paging Cause parameters carried in reply messages received by different terminals are different.

In this embodiment, under the condition that the Paging Cause parameter is introduced into the Paging message, different terminal users have different requirements, and thus, different terminals may need different customizations for the value of the received Paging Cause parameter, for example, different terminal users may require to shield incoming calls of specific different telephone numbers, and thus, information added in the Paging Cause parameter of different users is definitely different, and thus, the values of the Paging Cause parameter carried in reply messages received by different terminals of this embodiment are different, and a flexible granularity for adding the value of the Paging Cause parameter to the Paging message may be increased, so as to meet the requirements of different terminal users.

The embodiment of the invention also provides another message processing method from the terminal side.

Fig. 2 is a flow chart of another message processing method according to an embodiment of the present invention. As shown in fig. 2, the method may include the steps of:

step S202, the terminal sends the terminal identification to the network side entity.

In the technical solution provided in the foregoing step S202 of the present application, the terminal sends a terminal identifier to the network side entity, where the terminal identifier may be used to uniquely identify the terminal, and the terminal identifier may be a shallow permanent identifier (SUPI), a global Unique Temporary UE identifier (Globally Unique Temporary UE Identity, GUTI), an IMSI, and a permanent device identifier (PEI).

Step S204, the terminal receives a reply message sent by the network side entity based on the terminal identification, the reply message carries first information, and the first information includes at least one of the following: the value of Paging Cause parameter, the characteristic information of data packet, the service information and the mapping relation.

In the technical solution provided in the foregoing step S204 of the present application, in a case that the terminal sends the terminal identifier to the network side entity, the terminal receives a reply message sent by the network side entity based on the terminal identifier, where the reply message may carry first information for a Registration request reply message (Registration Accept), and the first information includes at least one of: the Paging Cause parameter value, the feature information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the following mapping relationship between at least two of the following corresponding relationships between any two data: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

In this embodiment, first information is introduced, where the first information may be carried in a reply message by a network entity based on a terminal identifier, and is sent to a terminal, and a content of the first information may be a user-granularity content obtained on demand, and may include at least one of the following contents: the value of Paging Cause parameter, the characteristic information of data packet, the service information and the mapping relation.

The network side entity in this embodiment may be a 3GPP network, including a core network element and/or a base station, and may send a paging message to a terminal. The Paging Cause parameter can enhance the Paging message, can be carried by the Paging message, and indicates to the terminal which service sends out Paging, and the terminal can determine what service triggers the Paging message according to the value of the Paging Cause parameter, so as to further determine whether to respond to the Paging message.

The data packet of this embodiment may be a downlink data packet sent by the application server to the network side entity, the feature information of the data packet is information carried in the data packet, and the specific content of the Paging Cause parameter may be obtained by the network side entity according to the feature information of the data packet, for example, obtained according to the content in the ToS field in the IP data packet header, where the content in the ToS field is sometimes also a DSCP value, and added by the application server, that is, the feature information of the data packet may indicate what the service corresponding to the data packet is, and the feature information of different data packets may indicate different services or different attributes in the same service.

The service information of this embodiment may be related information of the service initiator, for example, including a calling phone number, an IMS voice-phone number, a short message, internet data, and the like, which is not limited herein.

The mapping relationship of this embodiment may include a correspondence relationship between any two of the following data: the value of the Paging Cause parameter, the feature information of the data packet, and the service information, for example, a corresponding relationship between the value of the Paging Cause parameter carried in the Paging message and the service information (including a service originator, such as a calling phone number), or a corresponding relationship between the value of the parameter carried in the Paging message and the feature information of the data packet sent by the application server. The mapping relationship of the embodiment can be stored in the terminal and the network entity, so that when a data packet received by the network entity contains a specific ToS value, the value of the corresponding Paging Cause parameter is put into a page and broadcasted through a Paging message, so that the corresponding terminal can know the corresponding service information according to the value of the Paging Cause parameter after receiving the Paging message.

The terminal of this embodiment receives first information that is sent by a network side entity based on a terminal identity and includes at least one of the following: the value of the Paging Cause parameter, the feature information of the data packet, the service information, and the mapping relationship, for example, the network entity may only notify the corresponding relationship between the left two rows in table 1 to the terminal, and the service information itself remains.

The above method of this example is further illustrated below.

As an optional implementation manner, the sending, by the terminal, the terminal identifier to the network side entity includes: and the terminal sends the terminal identification to the network side entity through the non-access stratum NAS message.

In this embodiment, when the terminal sends the terminal identifier to the network side entity, the terminal may send the terminal identifier to the network side entity through an NAS message. Optionally, the terminal in this embodiment sends an uplink NAS message to the network side entity, where the NAS message carries the terminal identifier.

As an optional implementation manner, the NAS message is a registration request message, and the network side entity is a core network element.

In this embodiment, the terminal sends the terminal identifier to the network side entity, which may be that the terminal sends a registration request message to a network element of a core network, where the registration request message may carry the terminal identifier.

As an optional implementation manner, the first information is obtained by the core network element according to the terminal identifier, and the first information is sent to the base station of the network side entity by the core network element.

In this embodiment, when the terminal sends the terminal identifier to the core network element, the first information may be obtained by the core network element according to the terminal identifier, and then the first information may be sent to the terminal by being carried by a reply message by the core network element, or may be sent to a base station of the network side entity by being carried by the core network element, and the base station may send the first information to the terminal by being carried by the reply message.

In this embodiment, the core network element may send the first information to the base station through an N2 message during the registration process. For example, the core network element sends the registration request reply message and the first information in an N2 message to the base station, and the base station obtains the first information and transmits the registration request reply message to the terminal.

As an optional implementation, the method further comprises: the terminal sends a first indication to the network side entity, wherein the first indication is used for informing the network side entity that the terminal needs to acquire first information.

In this embodiment, when the terminal sends the terminal identifier to the network side entity, the terminal may further send a first indication to the network side entity, where the first indication may be carried by the NAS message to notify the network side entity that the terminal needs to acquire the first information.

As an optional implementation manner, the first information is sent to the network-side entity by the application server.

In this embodiment, the application server may interact with a network side entity, the first information may be sent to the network side entity by the application server, and optionally, the application server notifies the 3GPP network (core network element and/or base station) of the first information, so that the first information is sent to the terminal for use.

The method for informing the network side entity of the first information by the application server in the embodiment does not need to negotiate the content of the first information with the plurality of application servers respectively, thereby being beneficial to improving the flexibility of determining the first information.

As an optional implementation manner, the first information is user subscription information.

In this embodiment, the first information may be user subscription information, and the user subscription information may be stored in a network element of the core network, for example, in the UDM or the PCF. Before the terminal receives the reply message carrying the first information sent by the network side entity, the AMF may obtain the user subscription information from the UDM or PCF in a registration process, and then send the user subscription information to the terminal through a downlink NAS message.

As an optional implementation manner, the first information sent by the network side entity and received by the terminal is one or two of the following data: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information, the method also comprises the following steps: the terminal determines second information corresponding to the first information, or receives the second information corresponding to the first information and sent by the application server, wherein the second information is at least one of the following data: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

In this embodiment, the first information sent by the network-side entity received by the terminal may include only one or two data of the value of the Paging Cause parameter, the feature information of the data packet, and the service information, that is, the network-side entity does not send all the value of the Paging Cause parameter, the feature information of the data packet, and the service information to the terminal, the terminal may determine corresponding second information according to the content of the received first information, an association relationship exists between the data included in the second information and the data included in the first information, the association relationship may enable the second information to correspond to the first information, the second information may include at least one data of the value of the Paging Cause parameter, the feature information of the data packet, and the service information, and the second information and the first information jointly form the value of the Paging Cause parameter, the feature information of the data packet, And (4) service information. Optionally, the second information may also be provided to the network-side entity by the application server through the user plane connection.

For example, the first information includes a value of a paginghouse parameter, the terminal determines feature information and service information of a data packet corresponding to the value of one or more paginghouse parameters, and the terminal determines the feature information and service information of the data packet and a corresponding relationship with the value of the paginghouse parameter as the second information; the first information comprises the characteristic information of the data packet, and the terminal determines the value and the service information of a Paging Cause parameter corresponding to the characteristic information of one or more data packets, and then the terminal determines the value and the service information of the Paging Cause parameter and the corresponding relation with the characteristic information of the data packet as the second information; the first information comprises service information, and the terminal determines the value of a Paging Cause parameter and the characteristic information of a data packet corresponding to one or more service information, and then the terminal determines the value of the Paging Cause parameter, the characteristic information of the data packet and the corresponding relation with a service identifier as the second information; the first information comprises values of Paging Cause parameters and characteristic information of data packets, the terminal determines service information corresponding to the values of one or more Cause parameters and the characteristic information of one or more data packets, and the terminal determines the service information and a corresponding relation between the values of one or more Cause parameters and the characteristic information of one or more data packets as the second information; the first information comprises values of the Paging Cause parameters and service information, and the terminal determines the values of one or more Paging Cause parameters and the characteristic information of a data packet corresponding to one or more service identifiers, and then the terminal determines the characteristic information of the data packet and the corresponding relation between the values of the one or more Paging Cause parameters and the one or more service identifiers as the second information; the first information includes characteristic information and service information of the data packet, and the terminal determines the value of a Paging Cause parameter corresponding to the characteristic information of one or more data packets and one or more service information, and then the terminal determines the Paging Cause parameter and the corresponding relationship between the characteristic information of one or more data packets and one or more service identifiers as the second information.

As an optional implementation manner, the terminal sends the second information to the network side entity through another NAS message.

In a case that the terminal has determined that the second information or the application server has transmitted the second information to the terminal, the terminal transmits the second information to the network side entity, which may be that the terminal transmits the second information to the network side entity through another NAS message.

As an optional implementation, the other NAS message is a registration request complete message.

In this embodiment, the another NAS message may be a Registration request Complete (Registration Complete) message, as in step S1206 of fig. 12. The reply message sent by the terminal receiving network entity based on the terminal identifier may be a registration request reply message, where the registration request reply message carries the first information corresponding to the second information, as in step S1204 in fig. 12. Fig. 12 is an interaction diagram of a method for transmitting first information through a NAS message according to an embodiment of the present invention.

In this embodiment, a terminal sends a terminal identifier to a network side entity; the terminal receives a reply message sent by the network side entity based on the terminal identification, wherein the reply message carries first information, and the first information comprises at least one of the following information: the Paging Cause parameter value, the characteristic information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information. That is to say, the embodiment introduces the set first information, and implements the broadcast of the value of the Paging Cause parameter of the terminal user granularity, while avoiding that the value of the Paging Cause parameter in the Paging message is established by standardization, so that a third-party attacker cannot determine what the specific service content corresponding to the value of the Paging Cause parameter in the triggered Paging message is, thereby implementing the technical effect of improving the security of message processing, and further solving the technical problem of low security of message processing.

The embodiment of the invention also provides another message processing method corresponding to the message processing method shown in fig. 1 from the network side entity.

Fig. 3 is a flow chart of another message processing method according to an embodiment of the present invention. As shown in fig. 3, the method may include the steps of:

step S302, a network side entity acquires first information sent by a terminal, wherein the first information comprises at least one of the following information: the value of Paging Cause parameter, the characteristic information of data packet, the service information and the mapping relation.

In the technical solution provided in the foregoing step S302 of the present application, the mapping relationship includes a corresponding relationship between any two of the following data: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

In this embodiment, first information is introduced, and a network side entity obtains the first information sent by a terminal, where the content of the first information may be user-granularity content obtained as needed, and may include at least one of the following: the value of Paging Cause parameter, the characteristic information of data packet, the service information and the mapping relation.

The network side entity in this embodiment may be a 3GPP network, including a core network element and/or a base station. The Paging Cause parameter can enhance the Paging message, can be carried by the Paging message, and indicates which service to send out Paging to the terminal; the data packet may be a downlink data packet sent by the application server to the network side entity, and the characteristic information of the data packet is information carried in the data packet, for example, obtained according to the content in the ToS field in the IP data packet header, where the content in the ToS field is sometimes also a DSCP value; the service information may be related information of the service initiator, for example, including a calling phone number, an IMS voice-phone number, a short message, internet data, and the like, which is not limited herein.

The mapping relationship of this embodiment may include a correspondence relationship between any two of the following data: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information. The mapping relation can be stored in the terminal and the network side entity, so that when a data packet received by the network side entity contains a specific ToS value, the value of the corresponding Paging Cause parameter is put into Paging and broadcasted through a Paging message, and the corresponding service information can be obtained according to the value of the Paging Cause parameter after the corresponding terminal receives the Paging message.

The network side entity of the embodiment acquires first information which is sent by a terminal and comprises at least one of the following information: for example, the terminal may only notify the corresponding relationship between the two rows on the left side of table 1 to the 3GPP network (core network element and/or base station), and the service information itself is retained.

Step S304, the network side entity sends a reply message to the terminal.

In the technical solution provided in step S304 of the present application, when the network entity obtains the first information sent by the terminal, the network entity sends a reply message to the terminal, where the reply message may be a reply message obtained by the network entity performing corresponding processing on the first information.

When the Paging message is triggered, the network side entity can determine and determine the value of the Paging Cause parameter according to the characteristic information of the data packet. Optionally, the network entity in this embodiment further determines a value of the Paging Cause parameter in combination with the content of the first information.

As an optional example, when the terminal is in a CM-IDLE state or in an RRC-Inactive state, the core network element receives a data packet carrying a DSCP value sent by the application server, the core network element derives a value of a Paging Cause parameter according to the first information and the DSCP value, then the core network element may send a Paging message carrying the value of the Paging Cause parameter to the base station, and the base station sends the Paging message carrying the value of the Paging Cause parameter to the terminal, so that after receiving the Paging message, the terminal can know that corresponding service information is obtained according to a mapping relationship between the value of the Paging Cause parameter in the stored first information and the service information, and further determine whether to reply to the Paging message. The method comprises the steps that under the condition that a terminal is in a CM-IDLE state, the terminal sends a reply message to a core network element, wherein the reply message can be a Service Request (Service Request) message, and under the condition that the terminal is in an RRC-Inactive state, the terminal sends the reply message to a base station, wherein the reply message can be an RRC Resume Request message.

As another optional example, when the terminal is in the RRC-Inactive state, the core network element receives a data packet carrying a DSCP value sent by the application server, the core network element sends a Paging message carrying the DSCP value to the base station, the base station derives a value of the Paging Cause parameter according to the first information and the DSCP value, for example, the first information includes a mapping relationship between the DSCP value and the value of the Paging Cause parameter, the base station may determine the value of the Paging Cause parameter based on the mapping relationship and the DSCP value, then the base station sends the Paging message carrying the value of the Paging Cause parameter to the terminal, so that after receiving the Paging message, the terminal can know that the corresponding service information is obtained according to the mapping relationship between the value of the Paging Cause parameter and the service information, and then determine whether to reply to the Paging message, and the base station receives the reply message sent by the terminal, the reply message here may be an RRC Resume Request message.

The above-described method of this embodiment is further described below.

As an optional implementation manner, the sending, by the network side entity, the reply message to the terminal includes: and the network side entity updates the first information and sends the obtained reply message to the terminal.

In this embodiment, the first information sent by the terminal and received by the network-side entity may be updated except for the case where the content of the first information is changed. Optionally, when the network side entity sends a reply message to the terminal based on the first information, the network side entity updates the content of the first information, particularly updates the value of the Paging Cause parameter in the first information, so as to obtain the reply message, and the network side entity sends the reply message obtained by updating the first information to the terminal, so that the content of the first information can be continuously changed along with each update of the first information, and a third-party attacker cannot determine what the specific time service content corresponds to the value of the Paging Cause parameter in the Paging message, thereby protecting the privacy of the user, avoiding the disclosure of the privacy of the user, and further realizing the technical effect of improving the security of message processing.

In this embodiment, the reply message obtained by the network side entity updating the first information may be a result of the network side entity confirming whether the first information is updated successfully or not, or may be an acceptance result of the network side entity on the parameter in the first information, where the acceptance result may include a parameter accepted and/or an unacceptable parameter by the network side entity in the first information, for example, the terminal includes the first information in the uplink NAS, and the network side entity may return to the terminal which parameter in the first information is accepted, thereby determining the parameter accepted and/or the unacceptable parameter by the network side entity, and further may return to the second information corresponding to the first information; the reply message in this embodiment may also be update information obtained by the network side entity updating the first information, for example, at least one of a value of a Paging Cause parameter, feature information of a data packet, service information, and mapping relationship in the first information is updated, so that the content of the first information is changed, and the first information after the content is changed is determined as the update information.

Second information corresponding to the first information of the embodiment is described below.

As an optional implementation, the first information is one or two of the following data: the value of the Paging Cause parameter, the characteristic information of the data packet, and part of the information in the service information, the method further comprises: the network side entity determines second information corresponding to the first information, or receives the second information corresponding to the first information, wherein the second information is determined by the application server, and the second information is at least one of the following data: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

In this embodiment, the first information sent by the network side entity receiving terminal may include only one or two data of the value of the Paging Cause parameter, the feature information of the data packet, and the service information, that is, the network side entity does not receive all the value of the Paging Cause parameter, the feature information of the data packet, and the service information sent by the terminal, the network side entity may determine corresponding second information according to the content of the received first information, an association relationship may be provided between the data included in the second information and the data included in the first information, the association relationship may enable the second information to correspond to the first information, the second information may include at least one data of the value of the Paging Cause parameter, the feature information of the data packet, and the service information, and the second information and the first information may jointly form the value of the Paging Cause parameter, Characteristic information of the data packet, service information. Optionally, the core network element or the base station of this embodiment determines the second information according to the content of the first information, and sends the second information to the network side entity through the user plane connection.

For example, the first information includes a value of a Paging Cause parameter, the network side entity determines feature information and service information of a data packet corresponding to the value of one or more Paging Cause parameters, and the network side entity determines the feature information and service information of the data packet and a corresponding relationship with the value of the PagingCause parameter as the second information; the first information comprises the characteristic information of the data packet, and the network side entity determines the value of the Paging Cause parameter and the service information corresponding to the characteristic information of one or more data packets, and then the network side entity determines the value of the Paging Cause parameter, the service information and the corresponding relation with the characteristic information of the data packet as the second information; the first information comprises service information, and the network side entity determines the value of a Paging Cause parameter and the characteristic information of a data packet corresponding to one or more service information, and then the network side entity determines the value of the Paging Cause parameter, the characteristic information of the data packet and the corresponding relation with a service identifier as the second information; the first information comprises values of the Paging Cause parameters and characteristic information of the data packets, and the network side entity determines service information corresponding to the values of one or more Paging Cause parameters and the characteristic information of one or more data packets, and determines the service information and a corresponding relation between the values of one or more Paging Cause parameters and the characteristic information of one or more data packets as the second information; the first information comprises values of the Paging Cause parameters and service information, and the network side entity determines values of one or more Paging Cause parameters and characteristic information of a data packet corresponding to one or more service identifiers, and then determines the characteristic information of the data packet and a corresponding relation between the values of the one or more Paging Cause parameters and the one or more service identifiers as the second information; the first information includes feature information and service information of the data packet, and the network side entity determines values of a Paging Cause parameter corresponding to the feature information of one or more data packets and one or more service information, and then the network side entity determines the values of the Paging Cause parameter and a corresponding relationship between the values of the Paging Cause parameter and the feature information of one or more data packets and one or more service identifiers as the second information.

In this embodiment, the core network element may store the user subscription information, for example, the UDM or the PCF stores the user subscription information, and may obtain the user subscription information from the UDM or the PCF in the registration process through the AMF or the SMF, and further determine the second information according to the user subscription information.

As an alternative embodiment, the user data management UDM or the policy control function PCF provides the user subscription information.

In this embodiment, the UDM provider or the PCF may provide the user subscription information, where users of different terminals correspond to different user subscription information, for example, different IMSIs correspond to different user subscription information.

As an optional implementation manner, the network side entity sends the second information to the terminal in a reply message.

In this embodiment, when the network entity determines that the second information or the network entity receives the second information sent by the application server, the network entity sends the second information to the terminal, and the network entity may carry the second information in a reply message sent to the terminal and further send the second information to the terminal.

As an optional implementation manner, the acquiring, by the network entity, the first information sent by the terminal includes: the network side entity acquires first information sent by the terminal through a non-access stratum (NAS) message or an Access Stratum (AS) layer message.

In this embodiment, when the network side entity acquires the first information sent by the terminal, the network side entity may acquire the first information sent by the terminal through the NAS message, for example, the network side entity acquires the first information sent by the terminal through the NAS message, where the NAS message carries the content of the first information; optionally, the network side entity obtains the first information sent by the terminal through an AS message, where the AS message carries a content of the first information, for example, the network side entity obtains the first information sent by the terminal through the AS message, where the AS message carries the content of the first information.

As an optional implementation manner, the NAS message is a registration request message or a protocol data unit PDU session establishment request, and the network side entity is a core network element.

In this embodiment, when the network side entity acquires the first information sent by the terminal through the NAS message, the NAS message may be a registration request message or a PDU session establishment request message, where the network side entity is a core network element, that is, the terminal sends the first information to the core network element through the registration request message or the PDU session establishment request.

As an optional implementation, the core network element updates the first information.

In this embodiment, when the core network element acquires the first information sent by the terminal through the registration request message or the protocol data unit PDU session establishment request, the core network element may update the first information, for example, update the content of the first information, may periodically or aperiodically change the content of the first information, and particularly may update a value of a Paging Cause parameter in the first information. Optionally, the content of the first information is updated through the AMF or the SMF, so that the first information is updated through the NAS message, and the network side entity further sends the updated information to the terminal.

As an optional implementation manner, the core network element sends the first information to the base station of the network side entity.

In this embodiment, when the core network element acquires the first information, the core network element may further send the first information to the base station. Optionally, the core network element of this embodiment may send the content of the first information to the base station using an N2 message, for example, the core network element sends an N2 message to the base station, and the N2 message may carry the content of the first information.

In this embodiment, in the case that the network side entity acquires the first information sent by the terminal through the AS message, the AS layer message may be an RRC message, where the RRC message includes an RRC Setup Complete message, that is, the base station acquires the first information sent by the terminal through the RRC message.

As an optional implementation, the base station updates the first information.

In this embodiment, when the core network element sends the first information to the base station, the base station may update the first information, so AS to achieve the purpose of updating the first information through the AS message, and the network entity further sends a reply message to the terminal.

As an optional implementation manner, the base station sends the first information to a core network element of the network side entity.

In this embodiment, when the base station acquires the first information sent by the terminal, the base station may also send the first information to a core network element, for example, the base station may send the content of the first information to the core network element through an N2 interface.

In this embodiment, when the core network element obtains the first information sent by the base station, the core network element may update the first information, so that the base station may also send the content of the first information to the core network element and update the content, and the network side entity further sends a reply message to the terminal.

In this embodiment, before the network side entity obtains the first information sent by the terminal through the NAS message or the AS message, the terminal and the application server may negotiate the content of the first information through the user plane connection, so that the content of the first information of the user granularity may be obtained AS needed, that is, the specific content of the first information may be negotiated between the terminal and the application server, and the security may be ensured through the encrypted connection, and may be notified to the 3GPP network through the NAS or AS message for use.

In this embodiment, the content of the first information may be changed periodically or aperiodically along with a request message sent by the terminal to the network side entity, so that the terminal may update the content of the first information periodically or aperiodically along with the request message of the terminal, that is, the content of the first information may be changed with each update of the first information, especially, the value of the Paging Cause parameter may be changed with each update of the first information, so that a third-party attacker may not determine what the specific service content corresponding to the value of the Paging Cause parameter in the plaintext message is, and thus, the plaintext information broadcast in the Paging message may be prevented from being known by a third party to the corresponding content through multiple updates, the privacy of the user is protected, and the security of processing the message is further improved.

As an optional implementation manner, the values of the Paging Cause parameter carried in the reply message sent by the network side entity to different terminals are different.

In this embodiment, under the condition that the Paging message is introduced with the Paging Cause parameter, different terminals may need to customize the received Paging Cause parameter differently according to different requirements of different terminal users, for example, different terminal users may require to shield incoming calls of specific different telephone numbers, and thus information added in the Paging Cause parameter of different users is definitely different, and thus, the values of the Paging Cause parameter carried in reply messages received by different terminals of this embodiment are different, and even if the same service is used, the values of the Paging Cause parameter carried in reply messages received by different terminals are also different, so that the flexible granularity of adding the value of the Paging Cause parameter to the Paging message can be increased to meet the requirements of different terminal users.

In this embodiment, the network entity obtains first information sent by the terminal, where the first information includes at least one of the following: the Paging Cause parameter value, the characteristic information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information; and the network side entity sends a reply message to the terminal based on the first information. That is to say, the embodiment introduces the set first information, and implements the broadcast of the value of the Paging Cause parameter of the terminal user granularity, while avoiding that the value of the Paging Cause parameter in the Paging message is established by standardization, so that a third-party attacker cannot determine what the specific service content corresponding to the value of the Paging Cause parameter in the triggered Paging message is, thereby implementing the technical effect of improving the security of message processing, and further solving the technical problem of low security of message processing.

The embodiment of the invention also provides another message processing method corresponding to the message processing method shown in fig. 2 from the entity side of the network side.

Fig. 4 is a flow chart of another message processing method according to an embodiment of the present invention. As shown in fig. 4, the method may include the steps of:

step S402, the network side entity obtains the terminal identification sent by the terminal.

In the technical solution provided in the above step S402, the terminal identifier sent by the terminal and acquired by the network entity may be used to uniquely identify the terminal, such as SUPI, GUTI, IMSI, and PEI.

Step S404, the network side entity sends a reply message to the terminal based on the terminal identifier, the reply message carries first information, and the first information includes at least one of the following: the value of Paging Cause parameter, the characteristic information of data packet, the service information and the mapping relation.

In the technical solution provided in step S404 of the present application, when the network entity obtains the terminal identifier sent by the terminal, the network entity sends a reply message to the terminal based on the terminal identifier, where the reply message carries first information, and the first information includes at least one of the following information: the Paging Cause parameter value, the characteristic information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

In this embodiment, the first information is introduced, and the network side entity may carry the first information in the reply message based on the terminal identifier, and send the first information to the terminal, where the content of the first information may be a user-granularity content obtained as needed, and may include at least one of the following contents: the value of Paging Cause parameter, the characteristic information of data packet, the service information and the mapping relation.

The above-described method of this embodiment is further described below.

As an optional implementation manner, the acquiring, by the network entity, the terminal identifier sent by the terminal includes: and the network side entity acquires the terminal identification sent by the terminal through the non-access stratum NAS message.

In this embodiment, when the network entity acquires the terminal identifier sent by the terminal, the network entity may acquire the terminal identifier sent by the terminal through the NAS message. Optionally, the network side entity in this embodiment obtains a portable terminal identifier carried in an uplink NAS message sent by the terminal.

In this embodiment, the terminal identifier sent by the terminal obtained by the network side entity may be a registration request message sent by the core network element obtaining terminal, and the registration request message may carry the terminal identifier.

As an optional implementation, the method further comprises: and the core network element acquires the first information according to the terminal identifier and sends the first information to the base station of the network side entity.

In this embodiment, when the core network element obtains the terminal identifier sent by the terminal, the core network element may obtain the first information according to the terminal identifier, and then send the first information to the terminal through a reply message carrier, or send the first information to a base station of a network side entity, and the base station may send the first information to the terminal through the reply message carrier.

As an optional implementation, the method further comprises: the network side entity acquires a first indication sent by the terminal, wherein the first indication is used for informing the network side entity that the terminal needs to acquire first information.

In this embodiment, when the network side entity acquires the terminal identifier sent by the network side entity, the network side entity may further acquire a first indication sent by the terminal, where the first indication may be carried by the NAS message, so that the network side entity determines that the terminal needs to acquire the first information.

As an optional implementation manner, the network side entity obtains the first information sent by the application server.

In this embodiment, the application server may interact with a network side entity, the network side entity may obtain the first information sent by the application server, and optionally, the application server notifies the first information to a 3GPP network (a core network element and/or a base station) and sends the first information to the terminal, for example, the application server may pre-configure the first information to the core network element, and the core network element stores the first information, for example, stores the first information in the UDM or the PCF, so that the core network element may obtain the first information according to the terminal identifier when receiving the terminal identifier sent by the terminal, and then sends the first information to the terminal by carrying the first information with the reply message.

In this embodiment, the first information may be user subscription information, and the core network element may store the user subscription information, for example, the UDM or the PCF stores the user subscription information. Before the network side entity sends the reply message carrying the first information to the terminal, the AMF may obtain the user subscription information from the UDM or PCF in a registration process, and then send the user subscription information to the terminal through a downlink NAS message.

As an optional implementation manner, the first information sent by the network entity to the terminal is one or two of the following data: the value of the Paging Cause parameter, the characteristic information of the data packet, and the service information, wherein the second information corresponding to the first information is determined by the terminal or sent to the terminal by the application server, and the second information is at least one of the following data: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

In this embodiment, the first information sent by the network entity to the terminal may include only one or two data of the value of the Paging Cause parameter, the feature information of the data packet, and the service information, that is, the network entity does not send all the values of the Paging Cause parameter, the feature information of the data packet, and the service information to the terminal, the terminal may determine corresponding second information according to the content of the received first information, where the data included in the second information and the data included in the first information have an association relationship, the association relationship may enable the second information to correspond to the first information, the second information may include at least one data of the value of the Paging Cause parameter, the feature information of the data packet, and the service information, and the second information and the first information jointly form the value of the Paging Cause parameter, the feature information of the data packet, And (4) service information. Optionally, the second information of this embodiment may also be provided to the network-side entity by the application server through the user plane connection.

In this embodiment, in a case that the second information is determined by the terminal or sent to the terminal by the application server, the network-side entity acquires the second information sent by the terminal, and the network-side entity may acquire the second information sent by the terminal through another NAS message.

In this embodiment, the another NAS message may be a registration request complete message.

In this embodiment, a network entity obtains a terminal identifier sent by a terminal; the network side entity sends a reply message to the terminal based on the terminal identifier, wherein the reply message carries first information, and the first information comprises at least one of the following information: the Paging Cause parameter value, the characteristic information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information. That is to say, the embodiment introduces the set first information, and implements the broadcast of the value of the Paging Cause parameter of the terminal user granularity, while avoiding that the value of the Paging Cause parameter in the Paging message is established by standardization, so that a third-party attacker cannot determine what the specific service content corresponding to the value of the Paging Cause parameter in the triggered Paging message is, thereby implementing the technical effect of improving the security of message processing, and further solving the technical problem of low security of message processing.

Fig. 5 is a flow chart of another message processing method according to an embodiment of the present invention. As shown in fig. 5, the method may include the steps of:

step S502, the terminal sends first information to the network side entity, wherein the first information is dynamically updated periodically or aperiodically.

In the technical solution provided in the foregoing step S502 of the present application, first information is introduced, and a terminal sends the first information to a network side entity, where the content of the first information may be a content of a user granularity obtained as needed, and may be dynamically updated periodically or aperiodically, for example, the content of the first information may be periodically or aperiodically changed along with a request message sent by the terminal to the network side entity, so that the terminal may periodically or aperiodically update the content of the first information along with the request message of the terminal, that is, the content of the first information may change along with each update of the first information, especially a value of a Paging Cause parameter in the first information may change along with each update of the first information, so that a third party attacker cannot determine what a specific service content corresponding to the value of the Paging Cause parameter in a plaintext message is, and thus, by updating for multiple times, it may be avoided that plaintext information broadcasted in a Paging message is known to a third party that the corresponding plaintext message is corresponding to the third party The content protects the privacy of the user, and further improves the safety of processing the message.

As an optional implementation, the first information includes at least one of: the Paging Cause parameter value, the characteristic information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

The mapping relationship of this embodiment may include a correspondence relationship between any two of the following data: the value of the Paging Cause parameter, the feature information of the data packet, and the service information, for example, a corresponding relationship between the value of the Paging Cause parameter carried in the Paging message and the service information (including a service originator, such as a calling phone number), or a corresponding relationship between the value of the parameter carried in the Paging message and the feature information of the data packet sent by the application server. The mapping relationship of the embodiment can be stored in the terminal and the network entity, so that when a data packet received by the network entity contains a specific ToS value, the value of the corresponding Paging Cause parameter is put into a page and broadcasted through a Paging message, so that the corresponding terminal can know the corresponding service information according to the value of the Paging Cause after receiving the Paging message.

Step S504, the terminal receives a reply message sent by the network side entity based on the first information.

In the technical solution provided in the foregoing step S504, in a case that the terminal sends the first information to the network side entity, the terminal receives a reply message sent by the network side entity based on the first information, where the reply message may be a reply message obtained by updating the first information by the network side entity.

In this embodiment, the content of the first information may be updated by the network side entity, and particularly, the value of the Paging Cause parameter in the first information may be updated by the network side entity, so as to obtain a reply message, and the terminal receives the reply message obtained by updating the first information by the network side entity, so that the content of the first information may be continuously changed with each update of the first information, and a third-party attacker may not determine what the specific time service content corresponding to the value of the Paging Cause parameter in the Paging message is, thereby protecting the user privacy, avoiding the user privacy from being revealed, and further achieving the technical effect of improving the security of message processing.

In this embodiment, the reply message may be a result of the network side entity confirming whether the first information is successfully updated; the receiving result may also be a result of the network entity receiving the parameters in the first information, where the receiving result may include the parameters and/or the non-received parameters that are received by the network entity in the first information, for example, the terminal includes the first information in the uplink NAS, and the network entity may return to the terminal which parameters in the first information are received, and further may return the above-mentioned second information corresponding to the first information; the reply message in this embodiment may also be update information obtained by the network side entity updating the first information, for example, at least one of a value of a Paging Cause parameter, feature information of a data packet, service information, and mapping relationship in the first information is updated, so that the content of the first information is changed, and the first information after the content is changed is determined as the update information.

Step S506, the terminal receives a Paging message initiated by the network side entity, wherein the value of the Paging reason Paging Cause parameter carried in the Paging message is determined based on the first information.

In the technical solution provided in step S506 above, when the terminal receives a Paging message initiated by the network side entity, the value of the Paging Cause parameter can be determined according to the feature information of the data packet. Optionally, the embodiment further determines a value of the Paging Cause parameter in combination with the content of the first information.

As an optional example, when the terminal is in a CM-IDLE state or in an RRC-Inactive state, the application server sends a data packet carrying a DSCP value to the core network element, the core network element derives a value of the Paging Cause parameter according to the first information and the DSCP value, for example, the first information includes a mapping relationship between the DSCP value and the value of the Paging Cause parameter, the core network element may determine the value of the Paging Cause parameter based on the mapping relationship and the DSCP value, then the core network element may send a Paging message carrying the value of the Paging Cause parameter to the base station, the base station sends the Paging message carrying the value of the Paging Cause parameter to the terminal, so that the terminal may obtain, after receiving the Paging message, the service information corresponding to the mapping relationship between the value of the Paging Cause parameter in the stored first information and the service information, and then determines whether to reply to the paging message. The method comprises the steps that under the condition that a terminal is in a CM-IDLE state, the terminal sends a reply message to a core network element, wherein the reply message can be a Service Request (Service Request) message, and under the condition that the terminal is in an RRC-Inactive state, the terminal sends the reply message to a base station, wherein the reply message can be an RRC Resume Request message.

As another optional example, when the terminal is in an RRC-Inactive state, the application server sends a data packet carrying a DSCP value to the core network element, the core network element sends a Paging message carrying the DSCP value to the base station, the base station derives a value of the Paging Cause parameter according to the first information and the DSCP value, for example, the first information includes a mapping relationship between the DSCP value and the value of the Paging Cause parameter, the base station may determine the value of the Paging Cause parameter based on the mapping relationship and the DSCP value, then the base station sends the Paging message carrying the value of the Paging Cause parameter to the terminal, so that after receiving the Paging message, the terminal can know that the corresponding service information is obtained according to the stored mapping relationship between the value of the Paging Cause parameter and the service information, and then determine whether to reply the Paging message, and send a reply message to the base station, the reply message here may be an RRC Resume Request message.

In the embodiment, a terminal sends first information to a network side entity, wherein the first information is dynamically updated periodically or aperiodically; the terminal receives a reply message sent by the network side entity based on the first information; and the terminal receives a Paging message initiated by a network side entity, wherein the value of a Paging reason Paging Cause parameter carried in the Paging message is determined based on the first information. That is to say, the embodiment introduces the set first information, and implements the broadcast of the value of the Paging Cause parameter of the terminal user granularity, while avoiding that the value of the Paging Cause parameter in the Paging message is established by standardization, so that a third-party attacker cannot determine what the specific service content corresponding to the value of the Paging Cause parameter in the triggered Paging message is, thereby implementing the technical effect of improving the security of message processing, and further solving the technical problem of low security of message processing.

The embodiment realizes the broadcast of the value of the Paging Cause parameter of the terminal user granularity; the content of the first information is updated for multiple times, so that the plaintext information broadcast in the paging message is prevented from being known to the corresponding content by a third party, the privacy is protected, and the safety of message processing is improved; the terminal and the application server can obtain the content of the first information of the user granularity according to the requirement by a negotiation method; the method for the application server to inform the network side entity of the first information is helpful for improving flexibility, namely, the terminal does not need to negotiate the content of the respective first information with a plurality of application servers respectively.

It should be noted that the whole scheme of this embodiment may be used not only for the paging message, but also for other broadcast messages, so that the message processing mechanism of this embodiment may be used not only for the content broadcast in the paging message, but also for any other clear text message propagation, for example, for the downlink system broadcast message, the message in the uplink RRC establishment procedure, for example, the RRC establishment Request message (RRC Setup Request), the RRC establishment message (RRC Setup), and the RRC establishment completion message (RRC Setup Complete); the embodiment can be applied to a fourth Generation mobile communication network (4G for short) and a fifth Generation mobile communication network (5G for short), wherein only The mechanism that The terminal is in The CM-IDLE is used for The 4G network, and The embodiment is suitable for a dual-card terminal which does not support dual-pass and is beneficial to The dual-card terminal to select a proper USIM card to execute service.

Example 2

The technical solution of the present invention in the above-mentioned example 1 is further illustrated below with reference to preferred embodiments.

The paging process is used for the terminal to send a paging message to find the terminal when downlink user plane data arrives at the network in a CM-IDLE state or an RRC-Inactive state, and the terminal may receive the paging message to initiate an NAS message (e.g., Service Request) or an AS message (e.g., RRC Resume) to establish a user plane connection to transmit the data.

The paging message is a plaintext message, and one paging message has IDs of a plurality of user equipments, that is, one paging message can page a plurality of user equipments simultaneously.

Fig. 6 is an interaction diagram of a paging procedure in a CM-IDLE state of a terminal according to a related art. As shown in fig. 6, the method comprises the steps of:

step S601, paging a message.

Step S602, paging message.

Step S603, the terminal receives the reply paging message.

Step S604, the terminal establishes RRC connection with the radio access network.

Step S605, the terminal sends a service request to a network element of the core network.

Fig. 7 is an interaction diagram illustrating a paging procedure of a terminal in an RRC-Inactive state according to the related art. As shown in fig. 7, the method comprises the steps of:

step S701, a core network element sends a downlink tunneling protocol GTP-U data packet to RAN.

Step S702, based on the downlink GTP-U data packet, the RAN sends a paging message to the terminal.

Step S703, the terminal receives the reply paging message.

Step S704, the terminal establishes RRC connection with the RAN.

In order to enable the terminal to respond to the paging message more efficiently, for example, not respond to the paging message for the low priority service; or when the terminal user performs services on a Universal Subscriber Identity Module (USIM) -1, the USIM-2 receives the Paging message, and the terminal user determines that no response is made to avoid service interruption on the USIM-1, so that the Paging message can be enhanced, that is, a Paging Cause parameter is added to Paging, and the value of the Paging Cause parameter is used to indicate what service data packet arrives at the network, so that the Paging message is triggered. Therefore, the terminal can know what triggered Paging message according to the value of the Paging Cause parameter so as to decide whether to respond to the triggered Paging message.

Fig. 8 is an interaction diagram of a Paging procedure in which a terminal carries a Paging Cause parameter in a CM-IDLE state according to a related art. As shown in fig. 8, the method may include the steps of:

step S801, the application server sends DL Data (carrying DSCP value) to the network element of the core network.

Step S802, the core network element derives the value of the Paging Cause parameter according to the DSCP value carried by the DL Data.

Step S803, the core network element sends a Paging message carrying the value of the Paging Cause parameter to the RAN.

Step S804, the RAN sends a Paging message carrying the value of the Paging Cause parameter to the terminal.

Step S805, the terminal determines whether to reply the Paging message according to the value of the Paging Cause parameter.

Step S806, the terminal sends a reply message (Service Request) to the network element of the core network.

Fig. 9 is an interaction diagram of a Paging procedure in which a terminal is in an RRC-Inactive state and carries a Paging Cause parameter according to the related art. As shown in fig. 9, the method may include the steps of:

step S901, the application server sends DL Data (carrying DSCP value) to the network element of the core network.

Step S902, the core network element sends a downlink data packet carrying the relevant parameters of the Paging Cause parameter to the RAN.

Step S903, the RAN derives a value of the Paging Cause parameter according to the relevant parameter of the Paging Cause parameter in the downlink PDU data packet.

Step S904, the RAN sends a Paging message carrying the value of the Paging Cause parameter to the terminal.

Step S905, the terminal determines whether to reply the Paging message according to the value of the Paging Cause parameter.

Step S906, the terminal sends a reply message (Service Request) to the network element of the core network.

It should be noted that the specific content of the Paging Cause parameter is obtained by the core network or the base station according to the information carried in the DL Data packet, for example, according to the content (sometimes also referred to as DSCP value) in the ToS field of the service type in the IP Data packet header. That is, the information carried in the DL data may indicate what the service corresponding to the data packet is, and then the core network or the base station sends the service to the terminal through the Paging Cause parameter based on the information.

After the Paging Cause parameter is introduced, different terminals may need to customize the value of the received Paging Cause parameter differently, because different terminal users have different requirements, for example, different users may require to shield incoming calls of different specific telephone numbers, so that information added in the Paging Cause parameter of different users is definitely different; because the paging message is a broadcast message and the carried content is plaintext, there is a security problem (for example, there is a privacy disclosure problem); the value of the Paging Cause parameter added by different users not only needs the cooperation between the terminal and the 3GPP network, but also needs the cooperation with the application server, because the DSCP value added in the downlink DL Data is added by the application server.

The embodiment introduces the first information, which can be used to describe the mapping relationship between the value of the Paging Cause parameter and the service information, so as to correspond to the Paging message only carrying the value of the Paging Cause; the first information can be updated frequently by the terminal or the network side entity, that is, the value of the Paging Cause parameter changes with each update of the first information, so that a third party attacker cannot determine what the specific service content corresponding to the value of the Paging Cause parameter in the plaintext message is; the terminal and the application server can negotiate first information through the user plane secure connection and inform the 3GPP network of use; or the application server informs the 3GPP network (core network element and/or base station) of the first information, and sends the first information to the terminal for use.

The above-described method of this embodiment is further described below.

In this embodiment, first information is introduced, which may include the following: the value of the Paging Cause parameter when the network side sends the Paging message to the terminal; the mapping relation between the parameter value carried in the paging message and the specific service information (including the service initiator, such as the calling telephone number).

Optionally, the mapping relationship in this embodiment may be a correspondence relationship between a value of a Paging Cause parameter carried in a Paging message and characteristic information carried in a data packet sent by an application server. As shown in table 1, the ToS value is sent to the 3GPP network by the application server, and different values may represent different services or different attributes in the same service (for example, an originator of a voice call). This relationship is stored in the terminal and the 3GPP network, so that when downlink Data (DL Data) received by the 3GPP network includes a specific ToS value, the value of the corresponding Paging Cause parameter is put into the Paging Cause parameter and broadcasted through the Paging message, so that the corresponding terminal can obtain the corresponding service information according to table 1 after receiving the Paging message.

It should be noted that, the specific content of the first information in this embodiment may be negotiated between the terminal and the application server through the user plane secure connection. After negotiating the first information, the first information may be notified to the 3GPP network through an NAS or AS message; or the application server informs the 3GPP network of the first information, and sends the first information to the terminal for use.

The method of the first information transfer of this embodiment is described below.

In this embodiment, the first information may be updated regularly by the terminal or the network side. Except for the situation that the content of the first information is changed, the terminal may also periodically or aperiodically update the content of the first information, especially the parameter value that the Paging Cause can carry), so as to achieve the effect of security protection.

Fig. 10 is an interaction diagram of a method for updating first information through NAS messages according to an embodiment of the present invention. As shown in fig. 10, the method may include the steps of:

as an optional step, step S1001, the terminal and the application server negotiate the content of the first information through the user plane connection.

The negotiation of the content of the first information via the user plane connection can here ensure security via an encrypted connection.

Step S1002, the terminal sends a registration request message carrying the first information to a network element of the core network.

In this embodiment, the terminal may only notify the 3GPP network (core network element and/or base station) of the correspondence between the left two rows in table 1, and the service information is retained by itself.

Step S1003, the core network element updates the first information.

The core network element may update the content of the first information by the AMF or the SMF.

As an optional step, step S1004, the core network element carries the first information through an N2 message and sends the first information to the RAN.

In step S1005, the network side entity may determine the second information corresponding to the first information, or the application server sends the second information corresponding to the first information to the network side entity (a core network element or a base station).

Step S1006, the network entity sends a reply message carrying the second information.

The second information of this embodiment may be data of at least one of the following data: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information; the reply message of this embodiment may include at least one of: confirming whether the content of the first information is updated successfully; the network side entity receives the parameter in the first information, wherein the received result may include the parameter received by the network side entity and/or an unacceptable parameter in the first information; and the network side entity updates the first information to obtain updated information.

Fig. 11 is an interaction diagram of a method for updating first information through an AS message according to an embodiment of the present invention. As shown in fig. 11, the method may include the steps of:

as an optional step, in step S1101, the terminal and the application server negotiate the content of the first information through a user plane connection.

Step S1101 of this embodiment is an optional step, where negotiating the content of the first information through the user plane connection may ensure security through an encrypted connection.

Step S1102, the terminal sends an RRC message carrying the first information to the RAN.

In this embodiment, the AS message sent by the terminal to the RAN may be an RRC message, and the RRC message may carry the first information.

In step S1103, the RAN updates the content of the first information.

As an optional step, in step S1104, the RAN may further send the content of the first information to a core network element through an N2 interface, and update the content of the first information through the core network element.

In step S1105, the network side entity may determine the second information corresponding to the first information, or the application server sends the second information corresponding to the first information to the network side entity (a core network element or a base station).

Step S1106, the network entity sends a reply message carrying the second information.

The second information is data of at least one of the following data: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information; the reply message of this embodiment may include at least one of: confirming whether the content of the first information is updated successfully; the network side entity receives the parameter in the first information, wherein the receiving result may include the parameter received by the network side entity and/or the parameter that is not received in the first information; and the network side entity updates the first information to obtain updated information.

In this embodiment, in addition to the situation that the content of the first information changes, the network entity may also update the content of the first information periodically or aperiodically to achieve the effect of security protection.

Fig. 12 is an interaction diagram of a method for transmitting first information through NAS messages according to an embodiment of the present invention. As shown in fig. 12, the method may include the steps of:

as an optional step, step S1201, the application server pre-configures the first information to a core network element.

Optionally, in this embodiment, the application server interacts with a network element of the core network, and the application server informs the 3GPP network of the first information. The first information may be stored in a core network element (e.g. in a UDM or PCF).

Step S1202, the terminal sends a registration request message carrying the terminal identification to the network element of the core network.

In this embodiment, the NAS message sent by the terminal may be an uplink NAS message, for example, a registration request message, where the registration request message may also carry a first indication while carrying the terminal identifier to notify the network side entity that the first information is to be acquired.

Step S1203, the core network element acquires the first information according to the terminal identifier.

Step S1204, the core network element carries the first information in the registration request reply message to the terminal.

Before step S1204 or in step S1204, step S1205 is performed, and the core network element may send the first information to the base station. That is, the core network element sends an N2 message to the base station in the registration process, and sends the first information to the base station through an N2 message, for example, the core network element sends the registration request reply message and the first information in an N2 message to the base station, that is, the N2 message may carry the first information and the NAS message, and the base station obtains the first information and transparently transmits the registration request reply message to the terminal.

Step S1206, the terminal determines second information corresponding to the first information, or receives the second information corresponding to the first information sent by the application server, and sends the second information to the network side entity through the registration request completion message.

Fig. 13 is an interaction diagram of a method for deriving a value of a Paging Cause parameter according to first information when a terminal is in a CM-IDLE state according to an embodiment of the present invention. As shown in fig. 13, the method may include the steps of:

step S1301, the application server sends DL Data carrying the DSCP value to the core network element.

Step S1302, the core network element derives a value of the Paging Cause parameter according to the first information and the DSCP value carried by the DL Data.

Step S1303, the network element of the core network sends a Paging message carrying the value of the Paging Cause parameter to the RAN.

Step S1304, the RAN sends a Paging message carrying the value of the Paging Cause parameter to the terminal.

Step S1305, the terminal determines whether to reply to the Paging message according to a value of the Paging Cause parameter in the Paging message.

In step S1306, the terminal sends a reply message (service request message) to the network element of the core network.

Fig. 14 is an interaction diagram of a method for deriving a value of a Paging Cause parameter according to first information when a terminal is in an RRC-Inactive state according to an embodiment of the present invention. As shown in fig. 14, the method may include the steps of:

step S1401, the application server sends DL Data carrying DSCP value to the network element of the core network.

Step S1402a, the core network element derives a value of the Paging Cause parameter according to the first information and the DSCP value carried by the DL Data.

Step S1403a, the core network element sends a Paging message carrying the value of the Paging Cause parameter to the RAN.

Step S1402b, the core network element sends a paging message carrying the DSCP value to the RAN.

Step S1403b, the RAN derives a value of the Paging Cause parameter according to the first information and the DSCP value.

In step S1404, the RAN sends a Paging message carrying a value of the Paging Cause parameter to the terminal.

Step S1405, the terminal determines whether to reply the Paging message according to the value of the Paging Cause parameter in the Paging message.

In step S1406, the terminal transmits a reply message (RRC Resume Request message) to the RAN.

It should be noted that the above step S1402 a-step S1403a and step S1402 b-step S1403b only have one possibility.

It should be noted that the message processing mechanism of this embodiment may be used not only for the content broadcasted in the paging message, but also for any other plaintext message to be propagated and used, for example, a downlink system broadcast message, and a message in the uplink RRC establishment procedure, for example, an RRC establishment request message, an RRC establishment message, and an RRC establishment completion message; this embodiment can be applied to embodiments that can be applied to 4G and 5G. For 4G networks only the mechanism is used where the terminal is in CM-IDLE. Wherein, only the mechanism that the terminal is in CM-IDLE is used for the 4G network; the embodiment is suitable for the dual-card terminal which does not support double-pass, and is beneficial to the dual-card terminal to select a proper USIM card to execute the service.

Example 3

The embodiment of the invention also provides the terminal. It should be noted that the terminal of this embodiment may be configured to execute the message processing method shown in fig. 1 according to the embodiment of the present invention.

Fig. 15 is a schematic diagram of a terminal according to an embodiment of the present invention. As shown in fig. 15, the terminal 150 may include: a first signal transmitting circuit 151 and a first signal receiving circuit 152.

The first signal transmitting circuit 151 is configured to transmit first information to a network entity, where the first information includes at least one of: the Paging Cause parameter value, the characteristic information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

The first signal receiving circuit 152 is configured to receive a reply message sent by the network-side entity based on the first information.

The embodiment of the invention also provides another terminal. It should be noted that the terminal of this embodiment may be configured to execute the message processing method shown in fig. 2 according to the embodiment of the present invention.

Fig. 16 is a schematic diagram of another terminal according to an embodiment of the present invention. As shown in fig. 16, the terminal 160 may include: a second signal transmitting circuit 161 and a second signal receiving circuit 162.

And a second signal sending circuit 161, configured to send the terminal identifier to the network entity.

A second signal receiving circuit 162, configured to receive a reply message sent by the network entity based on the terminal identifier, where the reply message carries first information, and the first information includes at least one of the following: the Paging Cause parameter value, the characteristic information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

The embodiment of the invention also provides another terminal. It should be noted that the terminal of this embodiment may be configured to execute the message processing method shown in fig. 3 according to the embodiment of the present invention.

Fig. 17 is a schematic diagram of another terminal according to an embodiment of the present invention. As shown in fig. 17, the terminal 170 may include: a third signal transmitting circuit 171 and a third signal receiving circuit 172.

The third signal transmitting circuit 171 is configured to transmit the first information to the network entity, where the first information is dynamically updated periodically or aperiodically.

A third signal receiving circuit 172, configured to receive a reply message sent by the network side entity based on the first information; and receiving a Paging message initiated by a network side entity, wherein the value of a Paging reason Paging Cause parameter carried in the Paging message is determined based on the first information.

In the related art, in order to effectively judge whether a reply is required or not after a terminal receives a Paging message, a Paging Cause parameter is introduced into the Paging message for indicating which service triggers the Paging message, but the Paging Cause parameter causes safety and privacy problems because the Paging message is a plaintext message. In this embodiment, the set first information is introduced to implement the broadcast of the value of the Paging Cause parameter of the terminal user granularity, and avoid that the value of the Paging Cause parameter in the Paging message is established by standardization, so that a third-party attacker cannot determine what specific service content corresponds to the value of the Paging Cause parameter in the triggered Paging message, thereby implementing the technical effect of improving the security of message processing, and further solving the technical problem of low security of message processing.

Example 4

The embodiment of the invention also provides a message processing device. It should be noted that the message processing apparatus of this embodiment may be used to execute the message processing method shown in fig. 1 according to the embodiment of the present invention.

Fig. 18 is a schematic diagram of a message processing apparatus according to an embodiment of the present invention. As shown in fig. 18, the message processing apparatus 180 may include: a first transmitting unit 181 and a first receiving unit 182.

A first sending unit 181, configured to enable the terminal to send first information to the network entity, where the first information includes at least one of: the Paging Cause parameter value, the characteristic information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

A first receiving unit 182, configured to enable the terminal to receive a reply message of the network side entity.

Optionally, the first receiving unit includes: and the receiving module is used for enabling the terminal to receive the reply message obtained by updating the first information by the network side entity.

Optionally, the user subscription information is provided by a user data management UDM or a policy control function PCF, and different terminals correspond to different user subscription information.

Optionally, the sending module is configured to enable the terminal to send the first information to the network side entity through a non-access stratum NAS message or an access stratum AS layer message.

Optionally, the first information is updated by the base station.

The embodiment of the invention also provides a message processing device. It should be noted that the message processing apparatus of this embodiment may be used to execute the message processing method shown in fig. 2 according to the embodiment of the present invention.

Fig. 19 is a schematic diagram of another message processing apparatus according to an embodiment of the present invention. As shown in fig. 19, the message processing device 190 may include: a second transmitting unit 191 and a second receiving unit 192.

The terminal sends the terminal identifier to the network entity, which is the second sending unit 191.

A second receiving unit 192, configured to enable the terminal to receive a reply message sent by the network entity based on the terminal identifier, where the reply message carries first information, and the first information includes at least one of the following: the Paging Cause parameter value, the feature information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the following mapping relationship between at least two of the following corresponding relationships between any two data: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

Optionally, the first information is user subscription information.

Optionally, the another NAS message is a registration request complete message.

The embodiment of the invention also provides another message processing device. It should be noted that the message processing apparatus of this embodiment may be used to execute the message processing method shown in fig. 3 according to the embodiment of the present invention.

Fig. 20 is a schematic diagram of another message processing apparatus according to an embodiment of the present invention. As shown in fig. 20, the message processing apparatus 200 may include: a first acquisition unit 2001 and a fifth transmission unit 2002.

A first obtaining unit 2001, configured to enable a network entity to obtain first information sent by a terminal, where the first information includes at least one of: the Paging Cause parameter value, the characteristic information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

A fifth sending unit 2002, configured to enable the network side entity to send the reply message to the terminal based on the first information.

Optionally, the apparatus is further configured to enable the user data management UDM or the policy control function PCF to provide user subscription information, where different terminals correspond to different user subscription information.

The embodiment of the invention also provides another message processing device. It should be noted that the message processing apparatus of this embodiment may be used to execute the message processing method shown in fig. 4 according to the embodiment of the present invention.

Fig. 21 is a schematic diagram of another message processing apparatus according to an embodiment of the present invention. As shown in fig. 21, the message processing apparatus 210 may include: a second acquisition unit 212 and an eighth transmission unit 213.

A second obtaining unit 212, configured to enable a network entity to obtain a terminal identifier sent by a terminal;

an eighth sending unit 213, where the network side entity sends a reply message to the terminal based on the terminal identifier, where the reply message carries first information, and the first information includes at least one of the following: the Paging Cause parameter value, the characteristic information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.

Optionally, the first information is user subscription information.

Optionally, the another NAS message is a registration request complete message.

The embodiment of the invention also provides another message processing device. It should be noted that the message processing apparatus of this embodiment may be used to execute the message processing method shown in fig. 5 in the embodiment of the present invention.

Fig. 22 is a schematic diagram of another message processing apparatus according to an embodiment of the present invention. As shown in fig. 22, the message processing apparatus 220 may include: a tenth transmitting unit 221 and a third receiving unit 222.

A tenth sending unit 221, configured to enable the terminal to send the first information to the network entity, where the first information is dynamically updated periodically or aperiodically.

A third receiving unit 222, configured to enable the terminal to receive a reply message of the network side entity; and a fourth receiving unit, configured to enable the terminal to receive a Paging message initiated by the network side entity, where a value of a Paging Cause parameter carried in the Paging message is determined based on the first information.

In the related art, in order to effectively judge whether a reply is required or not after a terminal receives a Paging message, a Paging Cause parameter is introduced into the Paging message to indicate which service triggers the Paging message, but the Paging Cause parameter causes safety and privacy problems because the Paging message is a plaintext message. In this embodiment, the set first information is introduced to implement the broadcast of the value of the Paging Cause parameter of the terminal user granularity, and avoid that the value of the Paging Cause parameter in the Paging message is established by standardization, so that a third-party attacker cannot determine what specific service content corresponds to the value of the Paging Cause parameter in the triggered Paging message, thereby implementing the technical effect of improving the security of message processing, and further solving the technical problem of low security of message processing.

Example 5

The embodiment of the invention also provides a nonvolatile storage medium. The nonvolatile storage medium includes a stored program, wherein the device in which the nonvolatile storage medium is located is controlled to execute the message processing method according to the embodiment of the present invention when the program is executed.

Example 6

The embodiment of the invention also provides a communication system. The communication system is used for running a program, wherein the program executes the message processing method of the embodiment of the invention when running.

Example 7

The embodiment of the invention also provides an electronic device. The electronic device may include a memory in which a computer program is stored and a processor configured to execute the computer program to perform the claimed message processing method of the embodiment of the present invention.

The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.

In the above embodiments of the present invention, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

In the embodiments provided in the present application, it should be understood that the disclosed technology can be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units may be a logical division, and in actual implementation, there may be another division, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network-side entity device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.

The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.

Claims

A message processing method, comprising:

the terminal sends first information to a network side entity, wherein the first information comprises at least one of the following information: the Paging Cause parameter value, the feature information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information;

and the terminal receives the reply message of the network side entity.
The method according to claim 1, wherein the receiving, by the terminal, the reply message of the network-side entity includes:

and the terminal receives a reply message sent by the network side entity for updating the first information.
The method of claim 2, wherein the reply message comprises at least one of:

the network side entity successfully updates the first information;

the network side entity receives the parameter in the first information;

and the network side entity updates the first information to obtain updated information.
The method according to any one of claims 1 to 3, wherein the first information is one or both of the following data:

the value of the Paging Cause parameter, the characteristic information of the data packet, the service information,

second information corresponding to the first information is determined by the network side entity or sent to the network side entity by an application server, and the second information is data of at least one of the following data:

the value of the Paging Cause parameter, the characteristic information of the data packet, and the service information.
The method of claim 4, wherein the second information is determined based on user subscription information.
The method of claim 5, wherein the user subscription information is provided by a User Data Management (UDM) or a Policy Control Function (PCF).
The method of claim 4, wherein the second information is sent by the network-side entity to the terminal in the reply message.
The method according to claim 1, wherein the terminal sends the first information to the network-side entity, and wherein the sending comprises:

and the terminal sends the first information to the network side entity through a non-access stratum (NAS) message or an Access Stratum (AS) layer message.
The method of claim 8, wherein the NAS message is a registration request message or a protocol data unit, PDU, session modification request, and the network-side entity is a core network element.
The method of claim 9, wherein the first information is updated by the core network element.
The method of claim 9, wherein the first information is sent by the core network element to a base station of the network-side entity.
The method of claim 8, wherein the AS layer message is a radio resource control recovery RRC message and the network side entity is a base station.
The method of claim 12, wherein the first information is updated by the base station.
The method of claim 12, wherein the first information is sent by the base station to a core network element of the network-side entity.
The method of claim 14, wherein the first information is updated by the core network element.
The method of any one of claims 1 to 3, or 5 to 15, further comprising:

and the terminal and the application server negotiate the first information through user interface connection.
The method of any one of claims 1 to 3, or 5 to 15,

the content of the first information is changed periodically or non-periodically with a request message of the terminal.
The method of any one of claims 1 to 3, or 5 to 15,

and the values of the Paging Cause parameters carried in the reply messages received by different terminals are different.
A message processing method, comprising:

the terminal sends a terminal identification to a network side entity;

the terminal receives a reply message sent by the network side entity based on the terminal identification, wherein the reply message carries first information, and the first information comprises at least one of the following information: the Paging Cause parameter value, the feature information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the following mapping relationship between at least two of the following corresponding relationships between any two data: the value of the Paging Cause parameter, the characteristic information of the data packet, and the service information.
The method according to claim 19, wherein the terminal sends the terminal identifier to the network-side entity, and wherein the sending comprises:

and the terminal sends the terminal identification to the network side entity through a non-access stratum (NAS) message.
The method of claim 20, wherein the NAS message is a registration request message, and wherein the network-side entity is a core network element.
The method of claim 21, wherein the first information is obtained by the core network element according to the terminal identifier, and wherein the first information is sent to the base station of the network-side entity by the core network element.
The method of claim 19, further comprising:

the terminal sends a first indication to the network side entity, wherein the first indication is used for informing the network side entity that the terminal needs to acquire the first information.
The method according to any one of claims 19 to 23,

the first information is sent to the network side entity by an application server.
The method according to any of claims 19 to 23, wherein the first information is a subscriber subscription information.
The method according to any one of claims 19 to 23, wherein the first information sent by the network side entity and received by the terminal is one or two of the following data:

the value of the Paging Cause parameter, the characteristic information of the data packet, the service information,

the method further comprises the following steps: the terminal determines second information corresponding to the first information, or receives second information corresponding to the first information, wherein the second information is sent by an application server, and the second information is at least one of the following data:

the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.
The method of claim 26,

and the terminal sends the second information to the network side entity through another NAS message.
The method of claim 27, wherein the another NAS message is a registration request complete message.
A message processing method, comprising:

a network side entity acquires first information sent by a terminal, wherein the first information comprises at least one of the following information: the Paging Cause parameter value, the feature information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information;

and the network side entity sends a reply message to the terminal.
The method of claim 29, wherein the network entity sends a reply message to the terminal, and wherein the reply message comprises:

and the network side entity updates the first information and sends the obtained reply message to the terminal.
The method of claim 30, wherein the reply message comprises at least one of:

the network side entity successfully updates the first information;

the network side entity receives the parameter in the first information;

and the network side entity updates the first information to obtain updated information.
The method according to any one of claims 29 to 31, wherein the first information is one or both of the following data:

the value of the Paging Cause parameter, the characteristic information of the data packet, and part of the information in the service information,

the method further comprises the following steps: the network side entity determines second information corresponding to the first information, or receives the second information corresponding to the first information, wherein the second information is determined by an application server, and the second information is at least one of the following data:

the value of the Paging Cause parameter, the characteristic information of the data packet, and the service information.
The method of claim 32, wherein the second information is determined based on user subscription information.
The method of claim 33, wherein a user data management UDM or a policy control function PCF provides the user subscription information.
The method of claim 32, wherein the network entity sends the second information to the terminal in the reply message.
The method of claim 29, wherein the acquiring, by the network entity, the first information sent by the terminal comprises:

and the network side entity acquires the first information sent by the terminal through a non-access stratum (NAS) message or an Access Stratum (AS) layer message.
The method of claim 36, wherein the NAS message is a registration request message or a protocol data unit, PDU, session modification request, and wherein the network side entity is a core network element.
The method of claim 37, wherein the first information is updated by the core network element.
The method of claim 37, wherein the core network element sends the first information to a base station of the network-side entity.
The method of claim 36, wherein the AS layer message is a radio resource control recovery RRC message and the network side entity is a base station.
The method of claim 40, wherein the base station updates the first information.
The method of claim 40, wherein the base station sends the first information to a core network element of the network-side entity.
The method of any one of claims 29 to 31, or any one of claims 33 to 42,

the content of the first information is changed periodically or non-periodically with a request message of the terminal.
The method of any one of claims 29 to 31, or any one of claims 33 to 42,

and the values of the Paging Cause parameters carried in the reply messages sent by the network side entity to different terminals are different.
A message processing method, comprising:

a network side entity acquires a terminal identifier sent by a terminal;

the network side entity sends a reply message to the terminal based on the terminal identification, wherein the reply message carries first information, and the first information comprises at least one of the following information: the Paging Cause parameter value, the feature information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet, and the service information.
The method of claim 45, wherein the acquiring, by the network entity, the terminal identifier sent by the terminal comprises:

and the network side entity acquires the terminal identification sent by the terminal through the non-access stratum (NAS) message.
The method of claim 46, wherein the NAS message is a registration request message, and wherein the network side entity is a core network element.
The method of claim 47, further comprising:

and the core network element acquires the first information according to the terminal identifier and sends the first information to a base station of the network side entity.
The method of claim 45, further comprising:

the network side entity obtains a first indication sent by the terminal, wherein the first indication is used for informing the network side entity that the terminal needs to obtain the first information.
The method of any one of claims 45 to 49,

and the network side entity acquires the first information sent by the application server.
The method according to any one of claims 45 to 49, wherein the first information is a user subscription information.
The method according to any one of claims 45 to 49, wherein the first information sent by the network entity to the terminal is one or two of the following data:

the value of the Paging Cause parameter, the characteristic information of the data packet, the service information,

second information corresponding to the first information is determined by the terminal or sent to the terminal by an application server, and the second information is at least one of the following data:

the value of the Paging Cause parameter, the characteristic information of the data packet, and the service information.
The method of claim 52,

and the network side entity acquires the second information sent by the terminal through another NAS message.
The method of claim 53, wherein the another NAS message is a registration request complete message.
A message processing method, comprising:

a terminal sends first information to a network side entity, wherein the first information is periodically or aperiodically dynamically updated information;

the terminal receives a reply message sent by the network side entity based on the first information;

and the terminal receives a Paging message initiated by the network side entity, wherein the value of a Paging reason Paging Cause parameter carried in the Paging message is determined based on the first information.
The method of claim 55, wherein the first information comprises at least one of: the Paging Cause parameter value, the characteristic information of the data packet, the service information and a mapping relation, wherein the mapping relation comprises a corresponding relation between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet, and the service information.
A terminal, comprising:

a first signal transmitting circuit, configured to transmit first information to a network side entity, where the first information includes at least one of: the Paging Cause parameter value, the feature information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information;

and the first signal receiving circuit is used for receiving the reply message of the network side entity.
A terminal, comprising:

the second signal sending circuit is used for sending the terminal identification to the network side entity;

a second signal receiving circuit, configured to receive a reply message sent by the network side entity based on the terminal identifier, where the reply message carries first information, and the first information includes at least one of:

the Paging Cause parameter value, the feature information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet, and the service information.
A terminal, comprising:

the third signal sending circuit is used for sending first information to a network side entity, wherein the first information is periodically or aperiodically dynamically updated information;

a third signal receiving circuit, configured to receive a reply message sent by the network side entity based on the first information; and receiving a Paging message initiated by the network side entity, wherein the value of a Paging reason Paging Cause parameter carried in the Paging message is determined based on the first information.
A message processing apparatus, comprising:

a first sending unit, configured to enable a terminal to send first information to a network entity, where the first information includes at least one of: the Paging Cause parameter value, the feature information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information;

a first receiving unit, configured to enable the terminal to receive a reply message of the network side entity.
The apparatus of claim 60, wherein the first receiving unit comprises:

a receiving module, configured to enable the terminal to receive a reply message sent by the network entity to update the first information.
The apparatus according to claim 61, wherein the reply message comprises at least one of:

the network side entity successfully updates the first information;

the network side entity receives the parameter in the first information;

and the network side entity updates the first information to obtain updated information.
The apparatus according to any one of claims 60 to 62, wherein the first information is one or both of the following data:

the value of the Paging Cause parameter, the characteristic information of the data packet, the service information,

second information corresponding to the first information is determined by the network side entity or sent to the network side entity by an application server, and the second information is data of at least one of the following data:

the value of the Paging Cause parameter, the characteristic information of the data packet, and the service information.
The apparatus of claim 63, wherein the second information is determined based on user subscription information.
The apparatus of claim 64, wherein the user subscription information is provided by a User Data Management (UDM) or a Policy Control Function (PCF).
The apparatus of claim 63, wherein the second information is sent by the network-side entity to the terminal in the reply message.
The apparatus of claim 60, wherein the first sending unit comprises:

a sending module, configured to enable the terminal to send the first information to the network side entity through a non-access stratum NAS message or an access stratum AS layer message.
The apparatus of claim 67, wherein the NAS message is a registration request message or a Protocol Data Unit (PDU) session modification request, and wherein the network side entity is a core network element.
The apparatus of claim 68, wherein the first information is updated by a network element of the core network.
The apparatus of claim 68, wherein the first information is sent by the core network element to a base station of the network-side entity.
The apparatus of claim 67, wherein the AS layer message is a radio resource control recovery (RRC) message, and wherein the network side entity is a base station.
The apparatus of claim 71, wherein the first information is updated by the base station.
The apparatus of claim 71, wherein the first information is sent by the base station to a core network element of the network-side entity.
The apparatus of claim 73, wherein the first information is updated by a network element of the core network.
The apparatus of any one of claims 60 to 62, or 64 to 74, further comprising:

and the negotiation unit is used for enabling the terminal and the application server to negotiate the first information through user interface connection.
The device of any one of claims 60 to 62, or 64 to 74,

the content of the first information is changed periodically or non-periodically with a request message of the terminal.
The device of any one of claims 60 to 62, or 64 to 74,

and the values of the Paging Cause parameters carried in the reply messages received by different terminals are different.
A message processing apparatus, comprising:

a second sending unit, wherein the terminal sends the terminal identification to the network side entity;

a second receiving unit, configured to enable the terminal to receive a reply message sent by the network side entity based on the terminal identifier, where the reply message carries first information, and the first information includes at least one of the following: the Paging Cause parameter value, the feature information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the following mapping relationship between at least two of the following corresponding relationships between any two data: the value of the Paging Cause parameter, the characteristic information of the data packet, and the service information.
The apparatus of claim 78, wherein the second sending unit comprises:

a sending module, configured to enable the terminal to send the terminal identifier to the network side entity through a non-access stratum NAS message.
The apparatus of claim 79, wherein the NAS message is a registration request message, and wherein the network side entity is a core network element.
The apparatus of claim 80, wherein the first information is obtained by the core network element according to the terminal identifier, and wherein the first information is sent to the base station of the network-side entity by the core network element.
The apparatus of claim 78, further comprising:

a third sending unit, configured to enable the terminal to send a first indication to the network side entity, where the first indication is used to inform the network side entity that the terminal needs to acquire the first information.
The apparatus of any one of claims 78 to 82,

the first information is sent to the network side entity by an application server.
The apparatus of any of claims 78 to 82, wherein the first information is a user subscription information.
The apparatus of any one of claims 78 to 82, wherein the first information sent by the network entity and received by the terminal is one or two of the following data:

the value of the Paging Cause parameter, the characteristic information of the data packet, the service information,

the device further comprises: a first determining unit, configured to enable the terminal to determine second information corresponding to the first information, or receive second information corresponding to the first information, where the second information is data of at least one of the following data, and the second information is sent by an application server:

the value of the Paging Cause parameter, the characteristic information of the data packet, and the service information.
The apparatus of claim 85, further comprising:

a fourth sending unit, configured to enable the terminal to send the second information to the network side entity through another NAS message.
The apparatus of claim 86, wherein the another NAS message is a registration request complete message.
A message processing apparatus, comprising:

a first obtaining unit, configured to enable a network entity to obtain first information sent by a terminal, where the first information includes at least one of: the Paging Cause parameter value, the feature information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet and the service information;

a fifth sending unit, configured to enable the network entity to send a reply message to the terminal.
The apparatus according to claim 88, wherein the fifth transmitting unit comprises:

and the first updating module is used for enabling the network side entity to update the first information and send the obtained reply message to the terminal.
The apparatus according to claim 89, wherein said reply message comprises at least one of:

the network side entity successfully updates the first information;

the network side entity receives the parameter in the first information;

and the network side entity updates the first information to obtain updated information.
The apparatus of any one of claims 88 to 90, wherein the first information is one or both of:

the value of the Paging Cause parameter, the characteristic information of the data packet, and part of the information in the service information,

the device further comprises: a second determining unit, configured to enable the network-side entity to determine second information corresponding to the first information, or receive second information corresponding to the first information, where the second information is determined by an application server, and the second information is data of at least one of the following data:

the value of the Paging Cause parameter, the characteristic information of the data packet and the service information.
The apparatus of claim 91, wherein the second information is determined based on user subscription information.
The apparatus of claim 92, wherein the apparatus is further configured to cause a user data management UDM or a policy control function PCF to provide the user subscription information.
The apparatus of claim 91, wherein the fifth sending unit is configured to enable the network-side entity to send the second information to the terminal in the reply message.
The apparatus according to claim 88, wherein the first obtaining unit comprises:

a first obtaining module, configured to enable the network side entity to obtain the first information sent by the terminal through a non-access stratum NAS message or an access stratum AS layer message.
The apparatus of claim 95, wherein the NAS message is a registration request message or a protocol data unit, PDU, session modification request, and wherein the network side entity is a core network element.
The apparatus of claim 96, further comprising: a first updating unit, configured to enable the core network element to update the first information.
The apparatus of claim 96, further comprising: a sixth sending unit, configured to enable the core network element to send the first information to the base station of the network side entity.
The apparatus of claim 95, wherein the AS layer message is a radio resource control recovery, RRC, message and the network side entity is a base station.
The apparatus of claim 99, further comprising: a second updating unit, configured to enable the base station to update the first information.
The apparatus of claim 99, further comprising: a seventh sending unit, configured to enable the base station to send the first information to a core network element of the network side entity.
The device of any one of claims 88 to 90, or 92 to 101,

the content of the first information is changed periodically or non-periodically with a request message of the terminal.
The device of any one of claims 88 to 90, or 92 to 101,

and the values of the Paging Cause parameters carried in the reply messages sent by the network side entity to different terminals are different.
A message processing apparatus, comprising:

a second obtaining unit, configured to enable a network entity to obtain a terminal identifier sent by a terminal;

an eighth sending unit, configured to enable the network side entity to send a reply message to the terminal based on the terminal identifier, where the reply message carries first information, and the first information includes at least one of the following: the Paging Cause parameter value, the feature information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet, and the service information.
The apparatus according to claim 104, wherein the second obtaining unit comprises:

a second obtaining module, configured to enable the network side entity to obtain the terminal identifier sent by the terminal through a non-access stratum NAS message.
The apparatus of claim 105, wherein the NAS message is a registration request message, and wherein the network-side entity is a core network element.
The apparatus according to claim 106, further comprising:

a third obtaining unit, configured to enable the core network element to obtain the first information according to the terminal identifier;

a ninth sending unit, configured to send the first information to a base station of the network side entity.
The apparatus as claimed in claim 104, further comprising:

a fourth obtaining unit, configured to enable the network entity to obtain a first instruction sent by the terminal, where the first instruction is used to notify the network entity that the terminal needs to obtain the first information.
The apparatus of any one of claims 104 to 108, further comprising:

a fifth obtaining unit, configured to enable the network entity to obtain the first information sent by an application server.
The apparatus of any one of claims 104 to 108, wherein the first information sent by the network entity to the terminal is one or two of the following data:

the value of the Paging Cause parameter, the characteristic information of the data packet, the service information,

second information corresponding to the first information is determined by the terminal or sent to the terminal by an application server, and the second information is at least one of the following data:

the value of the Paging Cause parameter, the characteristic information of the data packet, and the service information.
The apparatus of any one of claims 104-108, wherein the first information is a subscriber subscription information.
The apparatus according to claim 111, wherein the apparatus comprises:

a sixth obtaining unit, configured to obtain, by the network entity, the second information sent by the terminal through another NAS message.
The apparatus of claim 112, wherein the another NAS message is a registration request complete message.
A message processing apparatus, comprising:

a tenth sending unit, configured to enable the terminal to send first information to a network entity, where the first information is dynamically updated periodically or aperiodically;

a third receiving unit, configured to enable the terminal to receive a reply message sent by the network-side entity based on the first information;

a fourth receiving unit, configured to enable the terminal to receive a Paging message initiated by the network side entity, where a value of a Paging Cause parameter carried in the Paging message is determined based on the first information.
The apparatus according to claim 114, wherein the first information comprises at least one of: the Paging Cause parameter value, the feature information of the data packet, the service information and the mapping relationship, wherein the mapping relationship comprises the corresponding relationship between any two data as follows: the value of the Paging Cause parameter, the characteristic information of the data packet, and the service information.
A non-volatile storage medium, comprising a stored program, wherein when the program is executed, a device in which the non-volatile storage medium is located is controlled to execute the message processing method according to any one of claims 1 to 56.
A communication system arranged to run a program, wherein the program when running performs the message processing method of any one of claims 1 to 56.
An electronic device comprising a memory and a processor, wherein the memory has stored therein a computer program, and the processor is configured to execute the computer program to perform the message processing method of any of claims 1 to 56.