CN111954200A - Message transmission method and device - Google Patents

Abstract

A message transmission method and device, wherein the implementation of the method includes: an AMF receiving a first message from a terminal device; the first message carries a second message sent to at least one third-party device, the third-party device being the the terminal device and the network device other than the AMF, the first message carries the first parameter, the second message carries the second parameter, and the first parameter is used to identify the first message , the second parameter is used to identify the second message; the second message is sent to the third-party device, where the second message carries the second parameter. The terminal device uses two layers of parameters to identify the first message and the second message respectively, so for AMF and third-party devices, when the terminal device sends multiple messages of the same type as the first message, the first message can still be distinguished. message and second message, thus avoiding confusion.

Description

Message transmission method and device

technical field

The present invention relates to the field of communication technologies, and in particular, to a message transmission method and device.

Background technique

In order to meet the challenges of wireless broadband technology and maintain the leading edge of the Third Generation Partnership Project (3GPP) network, the 3GPP standard group has formulated the next generation mobile communication network architecture (Next Generation System), called the fifth generation mobile communication network. Communication technology (5th-Generation, 5G) network architecture. The architecture not only supports the wireless technologies defined by the 3GPP standards group to access the 5G Core network (5G Core network), but also supports non-3GPP (non-3GPP) access technologies through the non-3GPP Interworking Function (N3IWF) or Next Generation Packet Data Gateway (ngPDG) accesses the 5G core network. The wireless technologies defined by the above-mentioned 3GPP standard group include: Long Term Evolution (Long Term Evolution, LTE), 5G Radio Access Network (Radio Access Network, RAN), and the like.

Among them, the functions of the 5G core network are divided into a user plane function (UPF) and a control plane function (CP). The user plane network element is mainly responsible for packet data packet forwarding, quality of service (Quality of Service, QoS) control, and charging information statistics. The control plane network element is mainly responsible for user registration and authentication, mobility management, and delivery of data packet forwarding policies and QoS control policies to the UPF. The control plane network elements can be further subdivided into an access and mobility management function (Core Access and Mobility Management Function, AMF) and a session management function (Session Management Function, SMF). Among them, the AMF is responsible for the registration process during user access and the location management during user movement. SMF is responsible for establishing corresponding session connections on the network side when users initiate services to provide users with specific services, especially delivering data packet forwarding policies and QoS policies to UPF based on the N4 interface between SMF and UPF.

An important difference of the 5G architecture compared to the 4G architecture is the separation of the access and mobility management function AMF from the session management function SMF. This means that when a user equipment (User Equipment, UE) initiates a session, that is, the UE sends a non-access stratum (Non-Access Stadium, NAS) request message using the N1 interface between the UE and the AMF, and the NAS request message carries the session Management (Session Management, SM) message, the AMF needs to forward the above SM message to the SMF for processing.

However, the current communication protocol mechanism does not provide a solution for AMF and SMF to distinguish NAS request messages and SM messages respectively, so that when a terminal device sends multiple NAS request messages, AMF and SMF cannot distinguish these messages; further, AMF After sending the reply message with the SMF, the UE side cannot identify which NAS request message the reply message is for. Therefore, the current communication protocol may cause confusion when the UE sends multiple NAS request messages.

SUMMARY OF THE INVENTION

Embodiments of the present invention provide a message transmission method and device, which are used to avoid confusion when a terminal device sends multiple messages of the same type to the AMF.

On the one hand, an embodiment of the present invention provides a method for transmitting a message, including:

The access and mobility management function entity AMF receives a first message from a terminal device; the first message carries a second message sent to at least one third-party device, where the third-party device is the terminal device and the AMF other network devices, the first message carries the first parameter, the second message carries the second parameter, the first parameter is used to identify the first message, and the second parameter is used for identifying the second message;

Send the second message to the third-party device, where the second message carries the second parameter.

In this embodiment, the first message is a message sent by the terminal device to the AMF, and can be carried to the second message of the third-party device; it can be understood that since the second message is to be sent to the third-party device, the third-party device will The type of the second message is determined; since there may be many types of the second message, the specific third-party device may not be limited in this embodiment of the present invention. In addition, there is no need to have only one second message, and even if there is only one second message, it can be sent to multiple third-party devices, so the third-party device should not be understood as the only one device.

The above-mentioned first parameter and second parameter are used to identify the first message and the second message respectively; therefore, the first parameter and the second parameter should be different and unique; the network device and the terminal device can pass the first parameter and the second parameter uniquely determine the first message and the second message. Since the first parameter and the second parameter are unique, both the network device and the terminal device can use these two parameters to retrieve or index the first message and the second message.

The first parameter carried in the above-mentioned first message can be used to associate the message flow of the same mobility management process initiated on the same access technology, that is, the message flow of the same mobility management process initiated on the same access technology. A transaction (transaction), such as a registration process initiated by the UE on the 3GPP access technology, the first message is a registration request message, and the terminal and the first network device can use the first parameter in the registration request message to associate the registration process. registration request message and registration response message, the registration response message includes a registration acceptance message or a registration rejection message. Optionally, the first parameter may specifically be an Access Transaction Identity (ATI), or a Mobility Transaction Identity (MTI), or an Access and Mobility Transaction Identity (AMTI) ), or a 5G transaction identity (5G Transaction Identity, 5GTI), the present invention does not limit the specific naming of the first parameter.

In an optional implementation manner, an implementation scheme of the reply message of the first message is also provided, and the method further includes:

After receiving the response message for the second message including the second parameter, the AMF sends a reply message for the first message to the terminal device, where the reply message carries the response message, and the The reply message carries the first parameter, and the response message carries the second parameter.

Since the second parameter is used to distinguish the second message, the second parameter can be carried in the response message of the second message, and the AMF can put the response message into the reply message of the first message, and then the reply message reaches the terminal. After the device is installed, it can be determined by the first parameter that the reply message is for the above-mentioned first message, and it can be determined by the second parameter that the response message is used to respond to the second message.

In an optional implementation manner, the first message includes: a non-access stratum NAS request message, or a non-access stratum NAS transport message (NAS transport message).

It should be noted that, based on the foregoing description, the first message may be any message transmitted between the terminal device and the AMF, as long as it contains a message sent to a third-party device, it satisfies the technical problem to be solved in the embodiment of the present invention. category. Therefore, the above examples of the NAS request message or the NAS transmission message should not be construed as a unique limitation on the embodiments of the present invention.

In an optional implementation manner, this embodiment of the present invention further provides a specific implementation solution for the AMF to select a third-party device, as follows: before sending the second message to the third-party device, the method further includes:

The AMF selects the third-party device based on the type of the second message.

In this embodiment, the type of the second message determines which device the second message should be sent to, so the AMF can select a third-party device based on the type of the second message.

In an optional implementation manner, an example of several possibilities of the third-party device corresponding to different second message types is also provided, as follows: the second message includes: a session management SM message, the third-party device Including: session management function SMF;

Alternatively, the second message includes: an extensible authentication protocol EAP message, and the third-party device includes: an authentication server function (Authentication Server Function, AUSF);

Or, the second message includes: a short message, and the third-party device includes: a short message service function (ShortMessage Service Function, SMSF).

It can be understood that there may be many types of the second message based on the foregoing description. Therefore, the above examples should not be construed as a unique limitation on the embodiments of the present invention.

In an optional implementation manner, the type of the SM message is further provided, and the SM message includes:

A session establishment message, a session modification message, or a session deletion message.

The SM message is the second message sent to the SMF, so the SM message can be a message of any function provided by the SMF, and the above three are examples of relatively common messages.

In an optional implementation manner, a specific implementation scheme for carrying the first parameter in the first message is also provided, and the first parameter in the first message includes:

The first parameter is carried in the message header of the first message, or the first parameter is carried in the message body of the first message.

In this embodiment, the message header is also called the message header, which is generally the protocol header of the message, and other parts except the message header are the message body.

In an optional implementation manner, an optional implementation solution in which the first message carries the second message is also provided, as follows: the first message carrying the second message sent to at least one third-party device includes: the first message The second message is contained in a container information element of a message.

Based on the fact that the second message is contained in the container information element, the container information element may have a container header and a container body, so the second parameter may be carried in the container header or the container body.

In an optional implementation manner, an implementation solution of other messages carried in the second message is also provided, as follows: the second message carries a message family type, and the message family type is used to determine the attribution of the message standards organization.

The message family type can be used to tell AMF how to identify the type of the second message. The type of the second message will use a relatively short sequence number to represent the type of the message, and different sequence numbers in different message families will represent different meanings , so informing the message family type will enable the AMF to accurately identify the type of the second message, so as to accurately determine which third-party device is.

In an optional implementation manner, an example of a message family type is also provided as follows: the message family type includes: 3rd Generation Partnership Project 3GPP, Internet Engineering Task Force (Internet Engineering Task Force, IETF) Institute of Electrical and Electronic Engineers (Institute for Electrical and Electronics Engineers, IEEE), International Telecommunication Union (International Telecommunication Union, ITU), European Telecommunications Standards Institution (European Telecommunications Standards Institution, ETSI), and International Organization for Standardization (International Organization for Standardization, ISO) at least One.

In an optional implementation manner, an implementation solution for the terminal device to use different types of access networks is also provided, which is specifically as follows: the first message further includes:

an access type parameter, where the access type parameter is used to indicate the type of the access network;

The AMF sending a reply message to the terminal device includes:

The AMF sends the reply message to the terminal device through the access network indicated by the access type parameter.

In an optional implementation manner, a manner of carrying the access type parameter in the first message is also provided, as follows: the first message header carries the access type parameter, or the message of the first message The access type parameter is carried in the body.

In an optional implementation manner, an optional implementation scheme of the first parameter and the second parameter is also provided as follows: at least one of the first parameter and the second parameter is a process transaction identifier (Procedure TransactionIdentity, PTI )parameter.

In the second aspect, the embodiment of the present invention also provides another method for transmitting a message, including:

The terminal device sends a first message to the access and mobility management function entity AMF;

The first message carries a second message sent to at least one third-party device, where the third-party device is the terminal device and a network device other than the AMF, and the first message carries the first parameter, The second message carries the second parameter, the first parameter is used to identify the first message, and the second parameter is used to identify the second message.

It can be understood that two layers of parameters are used on the terminal device side to identify the first message and the second message respectively, so that the AMF and the third-party device can distinguish the first message and the second message, then correspondingly, on the network When the AMF on the side and the third-party device return the reply message, the parameters of the two layers can also be used for identification respectively, so that the terminal device can distinguish which message the above reply message is replying to.

In an optional implementation manner, after the terminal device sends the first message to the access and mobility management function entity AMF, the method further includes:

receiving a reply message from the AMF, where the reply message carries the response message, the reply message carries the first parameter, and the response message carries the second parameter;

The terminal device determines that the reply message is used to reply to the first message according to the first parameter carried in the reply message, and determines that the response message is used to reply according to the second parameter carried in the response message the second message.

In an optional implementation manner, the first message includes: a non-access stratum NAS request message, or a non-access stratum NAS transmission message.

In an optional implementation manner, the second message includes: a session management SM message, and the third-party device includes: a session management function SMF;

Alternatively, the second message includes: an Extensible Authentication Protocol EAP message, and the third-party device includes: an authentication server function AUSF;

Or, the second message includes: a short message, and the third-party device includes: a short message service function SMSF.

In an optional implementation manner, the SM message includes:

A session establishment message, a session modification message, or a session deletion message.

In an optional implementation manner, the first parameter carried in the first message includes:

The first parameter is carried in the message header of the first message, or the first parameter is carried in the message body of the first message.

In an optional implementation manner, the carrying of the second message sent to at least one third-party device in the first message includes: the container information element of the first message includes the second message.

In an optional implementation manner, the second message carries a message family type, and the message family type is used to determine a standard organization to which the message belongs.

In an optional implementation manner, the message family types include: 3rd Generation Partnership Project 3GPP, Internet Engineering Task Force IETF, Institute of Electrical and Electronic Engineers IEEE, International Telecommunication Union ITU, European Telecommunications Standards Institute ETSI, and International Standardization Organize at least one of the ISOs.

In an optional implementation manner, the first message further includes:

an access type parameter, where the access type parameter is used to indicate the type of the access network;

The receiving reply message includes:

The reply message is received using the access network indicated by the access type parameter.

In an optional implementation manner, the first message header carries the access type parameter, or the message body of the first message carries the access type parameter.

In an optional implementation manner, at least one of the first parameter and the second parameter is a process transaction identifier PTI parameter.

Three aspects The embodiment of the present invention further provides an access and mobility management functional entity, including:

a first receiving unit, configured to receive a first message from a terminal device; the first message carries a second message sent to at least one third-party device, where the third-party device is the terminal device and the access device and a network device other than the mobility management function entity AMF, the first message carries the first parameter, the second message carries the second parameter, and the first parameter is used to identify the first message, the second parameter is used to identify the second message;

A first sending unit, configured to send the second message to the third-party device, where the second message carries the second parameter.

In an optional implementation manner, the access and mobility management functional entity further includes:

a second receiving unit, receiving a response message of the second message including the second parameter returned by the third-party device, where the response message carries the second parameter;

A second sending unit, configured to send a reply message of the first message to the terminal device, where the reply message carries the response message, and the reply message carries the first parameter.

In an optional implementation manner, the first message includes: a non-access stratum NAS request message, or a non-access stratum NAS transmission message.

In an optional implementation manner, the access and mobility management functional entity further includes:

A device selection unit, configured to select the third-party device based on the type of the second message before the first sending unit sends the second message to the third-party device.

In an optional implementation manner, the second message includes: a session management SM message, and the third-party device includes: a session management function SMF;

Alternatively, the second message includes: an Extensible Authentication Protocol EAP message, and the third-party device includes: an authentication server function AUSF;

Or, the second message includes: a short message, and the third-party device includes: a short message service function SMSF.

In an optional implementation manner, the SM message includes:

A session establishment message, a session modification message, or a session deletion message.

In an optional implementation manner, the first parameter carried in the first message includes:

The first parameter is carried in the message header of the first message, or the first parameter is carried in the message body of the first message.

In an optional implementation manner, the carrying of the second message sent to at least one third-party device in the first message includes: the container information element of the first message includes the second message.

In an optional implementation manner, the second message carries a message family type, and the message family type is used to determine a standard organization to which the message belongs.

In an optional implementation manner, the message family types include: 3rd Generation Partnership Project 3GPP, Internet Engineering Task Force IETF Institute of Electrical and Electronic Engineers IEEE, International Telecommunication Union ITU, European Telecommunications Standards Institute ETSI, and International Organization for Standardization At least one of ISO.

In an optional implementation manner, the first message further includes:

an access type parameter, where the access type parameter is used to indicate the type of the access network;

The second sending unit is configured to send the reply message to the terminal device through the access network indicated by the access type parameter.

In an optional implementation manner, the first message header carries the access type parameter, or the message body of the first message carries the access type parameter.

In an optional implementation manner, at least one of the first parameter and the second parameter identifies a PTI parameter for a process transaction.

Four aspects The embodiment of the present invention further provides a terminal device, including:

A message generating unit, configured to generate a first message, where the first message carries a second message sent to at least one third-party device, where the third-party device is the one between the terminal device and the access and mobility management function entity AMF; external network equipment, the first message carries the first parameter, the second message carries the second parameter, the first parameter is used to identify the first message, and the second parameter is used to identifying the second message;

a sending unit, configured to send the first message to the AMF.

In an optional implementation manner, the terminal device further includes:

a receiving unit, configured to receive a reply message from the AMF after the sending unit sends the first message to the AMF, where the reply message carries the response message, and the reply message carries the the first parameter, the second parameter is carried in the response message;

A message confirmation unit, configured to determine that the reply message is used to reply to the first message according to the first parameter carried in the reply message, and determine that the reply message is used to reply to the first message according to the second parameter carried in the response message in response to the second message.

In an optional implementation manner, the first message further includes:

an access type parameter, where the access type parameter is used to indicate the type of the access network;

The receiving unit is configured to use the access network indicated by the access type parameter to receive the reply message.

Five aspects The embodiment of the present invention further provides an access and mobility management functional entity, including: an input and output device, a processor, and a memory, where executable instructions are stored in the memory, and the processor executes the executable instructions. Executing the instruction implements the method process described in any one of the preceding aspects.

Sixth aspect An embodiment of the present invention further provides a terminal device, including: an input and output device, a processor, and a memory, where executable instructions are stored in the memory, and the processor implements the foregoing two when executing the executable instructions. The method flow described in any one of the aspects provided.

Seventh aspect The embodiment of the present invention further provides a storage medium, the storage medium contains executable instructions, and when the executable instructions are executed, the method flow of any one of the foregoing aspect or the second aspect is implemented. .

As can be seen from the above technical solutions, the embodiments of the present invention have the following advantages:

In this embodiment of the present invention, the first message sent to the AMF by the terminal device includes the second message sent to the third device, and the first message and the second message are respectively identified by two-layer parameters. As far as the third-party device is concerned, when the terminal device sends multiple messages of the same type as the first message, the first message and the second message can still be distinguished, so confusion can be avoided.

Description of drawings

In order to more clearly describe the technical solutions in the embodiments of the present invention or the background technology, the accompanying drawings required in the embodiments or the background technology of the present invention will be described below.

1 is a schematic diagram of a system structure according to an embodiment of the present invention;

2 is a schematic flowchart of a method according to an embodiment of the present invention;

3A is a schematic diagram of a NAS message structure according to an embodiment of the present invention;

3B is a schematic diagram of a NAS message structure according to an embodiment of the present invention;

4 is a schematic flowchart of a method according to an embodiment of the present invention;

5 is a schematic flowchart of a method according to an embodiment of the present invention;

6 is a schematic structural diagram of an AMF according to an embodiment of the present invention;

7 is a schematic structural diagram of a terminal device according to an embodiment of the present invention;

8 is a schematic structural diagram of an AMF according to an embodiment of the present invention;

FIG. 9 is a schematic structural diagram of a terminal device according to an embodiment of the present invention.

Detailed ways

The embodiments of the present invention will be described below with reference to the accompanying drawings in the embodiments of the present invention.

As shown in FIG. 1, it is an example of a 5G communication system, which includes: UE, radio access network (RadioAccess Network, RNA) or access network (Access Network, AN), user interface function (User PortFunction, UPF), Data Network (DN), AMF, SMF, Packet Control Function (PCF), Application Function (AF), Authentication Server Function (AUSF), normalized data Management (Unified Data Management, UDM); respectively use N1 to N15 interfaces for communication.

As shown in FIG. 2, it is a schematic flowchart of a method according to an embodiment of the present invention, including:

201: The terminal device sends a first message to the AMF, where the first message carries a second message sent to at least one third-party device, the first message carries a first parameter, and the second message carries a second parameter;

The above-mentioned first parameter is used to identify the first message, and the second parameter is used to identify the second message. The first parameter and the second parameter are unique and are used to distinguish different messages; then, for the device that receives the first message and the second message, in addition to distinguishing different first messages and second messages, it can also use for indexing and other purposes.

202: After receiving the first message, the AMF obtains the second message, determines to which third device the second message should be sent according to the message type of the second message, and then sends the second message to the third device. The second message carries the above-mentioned second parameter;

203: After the third device executes the content of the second message request, it returns a response message of the second message, and the response message carries the second parameter;

204: After receiving the response message of the second message, the AMF carries the response message of the second message in the reply message of the first message, and sends the reply message to the terminal device.

205: After receiving the reply message, the terminal device parses and finds the first parameter and the second parameter, then it can be determined according to the first parameter that the reply message user replies to the first message, and can be determined according to the second parameter The response message in the reply message is used to respond to the second message.

Based on the above description, it can be seen that the first message sent to the AMF by the terminal device includes the second message sent to the third device, and the first message and the second message are respectively identified by two-layer parameters. In terms of equipment, when the terminal equipment sends multiple messages of the same type as the first message, the first message and the second message can still be distinguished, so confusion can be avoided.

As an example, in the following embodiments, the first message is the NAS message and the second message is the SM request message as an example, then the third-party device will be the SMF; then corresponding to the network structure shown in FIG. The device exemplified in this embodiment includes: UE, AMF, and SMF; for communication among the three, reference may be made to the ports in the system structure shown in FIG. 1 .

When the UE sends multiple NAS messages to the AMF, all of which carry Session Management (SM) request messages, the AMF and SMF will not be able to distinguish the multiple received NAS messages, so the AMF and SMF sides will Confusion occurs; accordingly, for the reply messages sent by AMF and SMF, the UE side will not be able to identify which NAS message and SM request message the reply message is for.

The embodiments of the present invention will solve the problem that when the UE initiates multiple processes to the AMF, the AMF and other devices on the network side track and identify the messages of the multiple processes, and the embodiments of the present invention can also support multiple types of Message nesting and message routing. In the example of this embodiment, the SM request message can be supported in the NAS message, and other multiple types of message parameters can be further extended to implement message routing based on specific message types. The embodiments of the present invention can be applied to 5G system architecture, including 3GPP access and non-3GPP access scenarios; can be applied to any access or session management process, and the following embodiments take the session management process as an example for illustration. The network elements involved in the example of this embodiment include: AMF, SMF, UE, AN, and so on. The AN includes a 3GPP RAN, or a non-3GPP access network, such as a non-3GPP interworking function (N3IWF), a next generation packet data gateway (ngPDG), or a fixed network Access Gateway (access Gateway function, AGF), etc.

In the embodiment of the present invention, it is defined that the NAS message includes a multi-layer process index parameter (eg, a process transaction identifier PTI: Procedure Transaction Identity) and a container parameter (container). The above container parameters can support multiple message types, such as the session message (Session manager, SM) type defined by 3GPP, the Short Message Service (Short Message Service, SMS) type, or the Extensible Authentication Protocol (Extensible Authentication Protocol) defined by other standard organizations. Authentication Protocol, EAP) message type, Dynamic Host Configuration Protocol (Dynamic Host Configuration Protocol, DHCP) message type, etc. as follows:

A schematic diagram of the new NAS message structure, as shown in Figure 3A:

The NAS message includes: a NAS message header and a NAS message body; the NAS message header may include, PTI and a message type (Message type); the NAS message body includes an information element (Information Element, IE), the UE identity (Identity, ID), registration type (registration type), container (Container).

The container includes: PTI, protocol type (Protocol type), protocol identifier (Protocol Discriminator) and container IE. The container IE may contain specific content of the second message.

More specifically, as shown in FIG. 3B , horizontal bytes 1 to 8 and vertical bytes 1 to m+1 are the storage spaces occupied by each part. Wherein the first message includes security header type, protocol identifier, extended protocol identifier, access and mobility transaction identifier, message type... mobility management information element, and the specific content of the second message is contained in a container, and the container includes: Container header, PDU session identifier, protocol specifier, message family type, session transaction identifier, message type, session information element; since the first message can contain messages sent to other third-party devices, it can contain other mobility management information elements .

As shown in FIG. 4, it is an example of the embodiment of the present invention, and the details are as follows:

401A: The UE initiates a session establishment process, that is, the UE sends a NAS request message to the AMF, where the NAS request message includes a session message (SM message) for sending SMF.

In this embodiment, the type of the SM message is not uniquely limited, and the SM message may be: a PDU session establishment request message (Session Establishment Request).

Specifically, the UE sets the first process index parameter (PTI) in the above NAS request message, such as PTI 1=A1, where A1 is any value that is not currently used; the second process index parameter (PTI) is set in the SM message , if PTI 2=B1, the B1 is also any value that is not currently used.

The first PTI may be carried in the following manners: the NAS message header includes the first process index parameter, or the NAS message body includes the first process index parameter.

The second PTI may be carried in the following manners: the SM message header includes the second process index parameter, or the SM message body includes the second process index parameter.

Further, in order to support other message types other than the SM message carried in the NAS request message, a container parameter (Container) may be defined in the NAS message, and the container parameter may include a protocol identifier and further include a protocol type. The protocol type is used to indicate which standard organization defines the message contained in the container. For example, the protocol type is set to the 3GPP protocol suite, the IETF protocol suite, or the IEEE protocol suite. The protocol identifier is used to indicate a specific message type, such as a session request message, a session modification message, and so on. Taking the SM message as an SM session establishment message as an example, the protocol type is set to the 3GPP protocol suite, and the protocol identification code is set to the PDU session establishment request message. Taking the authentication message as an example, the protocol type is set to IETF, and the protocol identifier is set to the Extensible Authentication Protocol (EAP) request message.

401B: The UE initiates another session establishment process, that is, the UE sends another NAS request message, and the above NAS request message also carries the SM message. In order to distinguish it from the ongoing session establishment process in 401A, the UE sets the first process index parameter in the NAS request message to PTI 1=A2, A2 is not equal to A1, and A2 is any value that is not occupied. In addition, the UE sets the second process index parameter PTI 2 of the SM message to B2. The carrying manner of the PTI in the NAS request message and the SM message may refer to the foregoing description, which will not be repeated here.

402A: The AMF receives the NAS request message sent by the UE, and the AMF stores the first PTI and obtains the container parameters. The AMF identifies the message type carried in the container, such as an SM message or an EAP message, based on at least one of the protocol type in the container parameter or the protocol identifier. The AMF selects the next hop processing node for the above message based on the identified message type. For example, the next hop processing node of SM message is SMF, and the next hop processing node of EAP message is AUSF. Taking the SM message as an example, the AMF sends the SM message to the SMF through the N11 interface message, and the SM message includes the second PTI set by the UE. In this embodiment, the AMF will select the SMF.

402B: The same processing method as 402A, it should be noted that: the AMF stores the first PTI with different values, and forwards the SM message to the SMF, where the SM message includes the second PTI.

403: The SMF completes a session related process based on the SM message, such as a session establishment process, a session modification process, or a session deletion process, and the like.

404A: The SMF sends an SM response message through the N11 interface, and the SM response message contains the second PTI. Based on the foregoing SM message is a PDU session establishment request message, the SM response message here is a PDU session establishment response (SessionEstablishment Response) message. The SMF sets the second PTI value to the same value as the previously stored second PTI value, ie PTI 2=B1.

404B: The same processing method as 404A, it should be noted that: the SMF sets the second PTI value to B2.

405A: AMF receives an SM response message from the N11 interface. The AMF carries the above-mentioned SM response message in the NAS reply message and sends it to the UE. The NAS reply message includes the first PTI, and the AMF sets the first PTI as the stored first PTI value, that is, PTI 1=A1.

On the UE side, based on the first PTI 1=A1 included in the NAS message, it can be determined that the NAS reply message corresponds to the previously sent NAS request message with the same first PTI value. Based on the second PTI 2=B1 included in the SM response message, the UE corresponds to the previously sent SM message with the same second PTI value.

405B: AMF is the same as step 405A, AMF sets the first PTI value to A2. The operation principle of the UE is the same as that of 405A, which will not be repeated here.

This embodiment supports carrying multiple layers of PTI values in the NAS message. The UE and the network element on the network side distinguish their respective messages based on different PTI values, so as to avoid message confusion caused by concurrent multiple messages. In addition, this embodiment also supports other message types other than the SM message included in the NAS message, so that the AMF can perform message forwarding based on the message type in the container.

As shown in FIG. 5 , it is another example provided by the embodiment of the present invention. In this embodiment, a multi-session concurrent scenario is still used as an example. The difference from the previous embodiment is that the multi-session concurrency in this embodiment adopts different access technologies, that is, the 3GPP side and the Non-3GPP side trigger the session flow at the same time. The above-mentioned non-3GPP access technologies include wireless local area network (Wireless Local Area Network, WLAN) access, or fixed network access, and the like.

501A: The UE initiates a session establishment process on the 3GPP side, that is, the UE sends a NAS request message, the NAS request message includes a session message (SM message), and the PTI is set as in the previous embodiment 401A, which is not repeated here. In addition, the UE further includes an access type (Access type) indication in the NAS request message. The UE can set the above-mentioned access type as 3GPP access, or LTE access, or 5G RAN access, etc.; it is assumed to be: RAN.

The manner of carrying the access type parameter may be as follows: the access type parameter is included in the header of the NAS request message, or the access type parameter is included in the NAS request message body.

501B: The UE initiates a session establishment process on the non-3GPP side, that is, the UE sends a NAS request message, and the above NAS request message includes a session message (SM message). The setting of the PTI is the same as that in the previous embodiment 401B, which is not repeated here. In addition, the UE sets the access type parameter included in the NAS request message to non-3GPP access, WLAN access, or fixed network access, and the like.

502A: PTI processing on the AMF side is the previous embodiment 402A, which is not repeated here. In addition, the AMF acquires and stores the access type parameter carried in the NAS request message. The AMF stores the access type parameters of the 3GPP, and can also establish the binding relationship between the NAS request message and the access type.

502B: PTI processing on the AMF side is the previous embodiment 402B, which will not be repeated here. In addition, the AMF acquires and stores the access type parameter carried in the NAS request message. AMF stores non-3GPP access type parameters.

The above-mentioned 502B and its subsequent steps are the same in principle as the previous embodiment, until the AMF sends a reply message to the UE in 505A, so this embodiment will not describe it again.

505A: The AMF sends a reply message to the first NAS request message, and the PTI processing is the same as that of 405A. In addition, based on the stored access type, the AMF transmits the reply message of the above-mentioned NAS request to the UE through the access network corresponding to the above-mentioned access type. For example, when the access type is 3GPP, the AMF sends the NAS reply message to the RAN through the N2 interface. The RAN sends the received NAS message to the UE.

505B: The AMF sends a reply message for the second NAS request message, and the PTI processing is the same as that of 405B. In addition, when the access type stored by the AMF is non-3GPP, the AMF sends the NAS reply message to the N3IWF through the N2 interface. The N3IWF sends the above NAS message to the UE.

This embodiment, on the basis of the previous embodiment, further solves the problem that when the process is concurrent in different access technology networks, the process can always be completed in the original access network side.

The embodiment of the present invention also provides an access and mobility management functional entity, as shown in FIG. 6 , including:

The first receiving unit 601 is configured to receive a first message from a terminal device; the first message carries a second message sent to at least one third-party device, where the third-party device is the terminal device and the terminal device. A network device other than the inbound and mobility management function entity AMF, the first message carries the first parameter, the second message carries the second parameter, and the first parameter is used to identify the first message , the second parameter is used to identify the second message;

The first sending unit 602 is configured to send the second message to the third-party device, where the second message carries the second parameter.

It should be noted that, FIG. 6 is a schematic structural diagram of the AMF structure. If the structures included in this embodiment are not clearly indicated to be included, they should not be construed as necessarily included structures.

In an optional implementation manner, as shown in FIG. 6 , the access and mobility management functional entity further includes:

A second receiving unit 603, receiving a response message of the second message including the second parameter returned by the third-party device, where the response message carries the second parameter;

The second sending unit 604 is configured to send a reply message of the first message to the terminal device, where the reply message carries the response message, and the reply message carries the first parameter.

In an optional implementation manner, the first message includes: a non-access stratum NAS request message, or a non-access stratum NAS transmission message.

In an optional implementation manner, as shown in FIG. 6 , the access and mobility management functional entity further includes:

A device selection unit 605, configured to select the third-party device based on the type of the second message before the first sending unit 602 sends the second message to the third-party device.

In an optional implementation manner, the second message includes: a session management SM message, and the third-party device includes: a session management function SMF;

Alternatively, the second message includes: an Extensible Authentication Protocol EAP message, and the third-party device includes: an authentication server function AUSF;

Or, the second message includes: a short message, and the third-party device includes: a short message service function SMSF.

In an optional implementation manner, the SM message includes:

A session establishment message, a session modification message, or a session deletion message.

In an optional implementation manner, the first parameter carried in the first message includes:

The first parameter is carried in the message header of the first message, or the first parameter is carried in the message body of the first message.

In an optional implementation manner, the carrying of the second message sent to at least one third-party device in the first message includes: the container information element of the first message includes the second message.

In an optional implementation manner, the second message carries a message family type, and the message family type is used to determine a standard organization to which the message belongs.

In an optional implementation manner, the message family types include: 3rd Generation Partnership Project 3GPP, Internet Engineering Task Force IETF Institute of Electrical and Electronic Engineers IEEE, International Telecommunication Union ITU, European Telecommunications Standards Institute ETSI, and International Organization for Standardization At least one of ISO.

In an optional implementation manner, the first message further includes:

an access type parameter, where the access type parameter is used to indicate the type of the access network;

The second sending unit 604 is configured to send the reply message to the terminal device through the access network indicated by the access type parameter.

In an optional implementation manner, the first message header carries the access type parameter, or the message body of the first message carries the access type parameter.

In an optional implementation manner, at least one of the first parameter and the second parameter identifies a PTI parameter for a process transaction.

An embodiment of the present invention also provides a terminal device, as shown in FIG. 7 , including:

A message generating unit 701, configured to generate a first message, where the first message carries a second message sent to at least one third-party device, where the third-party device is the terminal device and the access and mobility management function entity AMF other network devices, the first message carries the first parameter, the second message carries the second parameter, the first parameter is used to identify the first message, and the second parameter is used for identifying the second message;

A sending unit 702, configured to send the first message to the AMF.

It should be noted that, FIG. 7 is a schematic structural diagram of the structure of the terminal device. If the structures included in this embodiment are not clearly indicated to be included, they should not be construed as necessarily included structures.

In an optional implementation manner, the terminal device further includes:

A receiving unit 703, configured to receive a reply message from the AMF after the sending unit 702 sends the first message to the AMF, where the reply message carries the response message, and the reply message carries the reply message the first parameter, the second parameter is carried in the response message;

A message confirmation unit 704, configured to determine that the reply message is used to reply to the first message according to the first parameter carried in the reply message, and determine the response message according to the second parameter carried in the response message for responding to the second message.

In an optional implementation manner, the first message further includes:

an access type parameter, where the access type parameter is used to indicate the type of the access network;

The receiving unit 703 is configured to receive the reply message by using the access network indicated by the access type parameter.

For more specific descriptions of parameters and messages in the terminal-side embodiment, reference may be made to the foregoing method embodiments, and details are not described herein again.

The embodiment of the present invention also provides an access and mobility management functional entity, as shown in FIG. 8 , including: an input and output device 801, a processor 803, and a memory 802;

The memory 802 can be used for the cache required by the processor 803 to perform data processing, and can also be used to provide storage space requirements for the data sent or received;

The above-mentioned input/output device 801, the processor 803, and the memory 802 may be connected to each other through a bus.

The memory 802 includes, but is not limited to, a random access memory (Random Access Memory, RAM), a read only memory (Read-Only Memory, ROM), an erasable programmable read only memory (Erasable Programmable Read Only Memory, EPROM), or a portable Read-only memory (Compact Disc Read-Only Memory, CD-ROM), the memory 802 is used for related instructions and data. Input and output devices 801 are used to receive and transmit data.

The processor 803 may be one or more central processing units (Central Processing Units, CPUs). When the processor 803 is one CPU, the CPU may be a single-core CPU or a multi-core CPU.

Executable instructions are stored in the memory 802, and the processor 803 executes the executable instructions to implement any one of the foregoing method processes executed by the AMF.

An embodiment of the present invention further provides a terminal device, as shown in FIG. 9 , including: an input and output device 901, a processor 903, and a memory 902;

The memory 902 can be used for the cache required by the processor 903 to perform data processing, and can also be used to provide storage space requirements for the data sent or received;

The above-mentioned input/output device 901, the processor 903, and the memory 902 may be connected to each other through a bus.

Memory 902 includes, but is not limited to, RAM, ROM, EPROM, or CD-ROM, which is used for related instructions and data. Input and output devices 901 are used to receive and transmit data.

The processor 903 may be one or more CPUs, and if the processor 903 is one CPU, the CPU may be a single-core CPU or a multi-core CPU.

Executable instructions are stored in the memory 902, and the processor 903 executes the executable instructions to implement any one of the foregoing method processes executed by the terminal device.

In the above embodiments of the AMF and the terminal device, the input and output devices may respectively correspond to the specific functions of the sending unit and the receiving unit of the AMF and the terminal device in the previous embodiments, and the specific content executed by the corresponding processor instructing the input and output devices may be With reference to the foregoing implementation solutions of the AMF and the terminal device, reference may also be made to the method embodiments, which will not be repeated here.

The embodiment of the present invention further provides a storage medium, the storage medium contains executable instructions, and when the executable instructions are executed, the method process of any one of the embodiments of the present invention is implemented.

Those of ordinary skill in the art can understand that all or part of the steps in the method of the above-mentioned embodiments can be completed by instructing the relevant hardware through a program, and the above-mentioned program can be stored in a readable storage medium of a device, and when the program is executed, Including all or part of the above steps, the above storage medium, such as: FLASH, EEPROM, etc.

The above-mentioned specific embodiments further describe the purpose, technical solutions and beneficial effects of the present invention in detail. It should be understood that different embodiments can be combined. The above-mentioned embodiments are only specific embodiments of the present invention, and It is not intended to limit the protection scope of the present invention, and any combination, modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included within the scope disclosed by the embodiments of the present invention.

Claims (28)

1. a message transmission method, is characterized in that, comprises: The access and mobility management function entity AMF receives a first message from a terminal device; the first message carries a second message sent to at least one third-party device, where the third-party device is the terminal device and the AMF other network devices, the first message carries the first parameter, the second message carries the second parameter, the first parameter is used to identify the first message, and the second parameter is used for identifying the second message; the AMF selects the third-party device based on the type of the second message; sending, by the AMF, the second message to the third-party device, where the second message carries the second parameter; The AMF receives a response message from the third-party device to the second message containing the second parameter, and sends the response message to the terminal device, where the response message carries the second parameter, The second parameter is used by the terminal device to determine that the response message is for responding to the second message. 2 . The method according to claim 1 , wherein the first message comprises: a non-access stratum NAS request message or a non-access stratum NAS transmission message. 3 . 3. The method according to claim 1 or 2, wherein the second message comprises: a session management SM message, and the third-party device comprises: a session management function SMF; Alternatively, the second message includes: an Extensible Authentication Protocol EAP message, and the third-party device includes: an authentication server function AUSF; Or, the second message includes: a short message, and the third-party device includes: a short message service function SMSF. 4. The method according to claim 3, wherein the SM message comprises: A session establishment message, a session modification message, or a session deletion message. 5. The method according to claim 1 or 2, wherein the second message comprises at least two of a session management SM message, an Extensible Authentication Protocol EAP message, or a short message. 6. The method according to any one of claims 1 to 5, wherein the carrying the first parameter in the first message comprises: The first parameter is carried in the message header of the first message, or the first parameter is carried in the message body of the first message. 7 . The method according to claim 1 , wherein carrying the second message sent to at least one third-party device in the first message comprises: a container information element of the first message includes the second message. 8 . . 8. The method according to claim 1, wherein the second message carries a message family type, and the message family type is used to determine a standard organization to which the message belongs. 9 . The method according to claim 1 , wherein the second parameter is a process transaction identifier (PTI) parameter. 10 . 10. A method for transmitting a message, comprising: The terminal device sends a first message to the access and mobility management function entity AMF; The first message carries a second message sent to at least one third-party device, where the third-party device is the terminal device and a network device other than the AMF, and the first message carries the first parameter, The second message carries the second parameter, the first parameter is used to identify the first message, and the second parameter is used to identify the second message; receiving a response message from the AMF, where the response message carries the second parameter; The terminal device determines that the response message is used to respond to the second message according to the second parameter carried in the response message. The method according to claim 10, wherein the first message comprises: a non-access stratum NAS request message or a non-access stratum NAS transport message. The method according to claim 10 or 11, wherein the second message comprises: a session management SM message, and the third-party device comprises: a session management function SMF; Alternatively, the second message includes: an Extensible Authentication Protocol EAP message, and the third-party device includes: an authentication server function AUSF; Or, the second message includes: a short message, and the third-party device includes: a short message service function SMSF. 13. The method according to claim 10 or 11, wherein the second message comprises at least two of a session management SM message, an Extensible Authentication Protocol EAP message, or a short message. 14. The method according to any one of claims 10 to 13, wherein the carrying the first parameter in the first message comprises: The first parameter is carried in the message header of the first message, or the first parameter is carried in the message body of the first message. 15. The method according to any one of claims 10 to 13, wherein the second parameter is a process transaction identifier (PTI) parameter. 16. An access and mobility management functional entity, characterized by comprising: a first receiving unit, configured to receive a first message from a terminal device; the first message carries a second message sent to at least one third-party device, where the third-party device is the terminal device and the access device and a network device other than the mobility management function entity AMF, the first message carries the first parameter, the second message carries the second parameter, and the first parameter is used to identify the first message, the second parameter is used to identify the second message; a device selection unit, configured to select the third-party device based on the type of the second message before the first sending unit sends the second message to the third-party device; a first sending unit, configured to send the second message to the third-party device, where the second message carries the second parameter; a second receiving unit, receiving a response message of the second message including the second parameter returned by the third-party device, where the response message carries the second parameter; a second sending unit, configured to send the response message to the terminal device, where the response message carries the second parameter, and the second parameter is used by the terminal device to determine that the response message is used to respond to the first Two news. The access and mobility management functional entity according to claim 16, wherein the first message comprises: a non-access stratum NAS request message or a non-access stratum NAS transfer message. The access and mobility management function entity according to claim 16 or 17, wherein the second message comprises: a session management SM message, and the third-party device comprises: a session management function SMF; Alternatively, the second message includes: an Extensible Authentication Protocol EAP message, and the third-party device includes: an authentication server function AUSF; Or, the second message includes: a short message, and the third-party device includes: a short message service function SMSF. 19. The access and mobility management functional entity according to claim 16, wherein the first message carrying the second message sent to at least one third-party device comprises: a container information element in the first message contains the second message. 20. The access and mobility management functional entity according to any one of claims 16 to 19, wherein the first parameter carried in the first message comprises: The first parameter is carried in the message header of the first message, or the first parameter is carried in the message body of the first message. 21. The access and mobility management functional entity according to any one of claims 16 to 20, wherein the second parameter is a process transaction identifier (PTI) parameter. 22. A terminal device, comprising: A message generating unit, configured to generate a first message, where the first message carries a second message sent to at least one third-party device, where the third-party device is the one between the terminal device and the access and mobility management function entity AMF; external network equipment, the first message carries the first parameter, the second message carries the second parameter, the first parameter is used to identify the first message, and the second parameter is used to identifying the second message; a sending unit, configured to send the first message to the AMF; a receiving unit, configured to receive a response message from the AMF, where the response message carries the second parameter; A message confirmation unit, configured to determine that the response message is used to respond to the second message according to the second parameter carried in the response message. 23. The terminal device according to claim 22, wherein the first message comprises: a non-access stratum NAS request message or a non-access stratum NAS transmission message. 24. The terminal device according to claim 22 or 23, wherein the second message comprises: a session management SM message, and the third-party device comprises: a session management function SMF; Alternatively, the second message includes: an Extensible Authentication Protocol EAP message, and the third-party device includes: an authentication server function AUSF; Or, the second message includes: a short message, and the third-party device includes: a short message service function SMSF. 25. The terminal device according to claim 22 or 23, wherein the second message comprises at least two of a session management SM message, an Extensible Authentication Protocol EAP message, or a short message. 26. The terminal device according to any one of claims 22 to 25, wherein the second parameter is a process transaction identifier (PTI) parameter. 27. A computer-readable storage medium, wherein instructions are stored in the computer-readable storage medium, which, when executed on a computer, cause the computer to perform the execution of any one of claims 1-9. Methods. 28. A computer-readable storage medium, wherein instructions are stored in the computer-readable storage medium, which, when executed on a computer, cause the computer to perform the execution of any one of claims 10-15 Methods.

Images