WO2018201816A1 - Message transmission method and device - Google Patents

Abstract

A message transmission method and device, the implementation of the method comprising: an access and mobility management function (AMF) receives a first message from a terminal device, wherein the first message carries a second message to be sent to at least one third-party device, the third-party device being a network device other than the terminal device and the AMF; the first message carries a first parameter, and the second message carries a second parameter; the first parameter is used to identify the first message, and the second parameter is used to identify the second message; and the second message is sent to the third-party device, wherein the second message carries the second parameter. The terminal device uses two layers of parameters to identify a first message and a second message respectively. Thus, for the AMF and the third-party device, when the terminal device sends a plurality of messages of the same type as a first message, the first message and a second message may still be distinguished, thereby avoiding confusion.

Description

Message transmission method, and device

This application claims the priority of the Chinese Patent Application, filed on May 4, 2017, the application Serial No. .

Technical field

The present invention relates to the field of communications 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 standards group has developed the next generation mobile communication network architecture (Next Generation System), called the fifth generation. Mobile communication technology (5th-Generation, 5G) network architecture. The architecture not only supports the wireless technology defined by the 3GPP standard group to access the 5G core network, but also supports the non-3GPP (non-3GPP) access technology through the non-3GPP Interworking Function (N3IWF) or The next generation packet data gateway (ngPDG) accesses the 5G core network. The wireless technologies defined by the foregoing 3GPP standard group include: Long Term Evolution (LTE), 5G 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 (QoS) control, and accounting information statistics. The control plane network element is mainly responsible for user registration authentication, mobility management, and sending packet forwarding policies and QoS control policies to the UPF. The control plane network element can be further subdivided into a Core Access and Mobility Management Function (AMF) and a Session Management Function (SMF). Among them, AMF is responsible for the registration process when the user accesses and the location management during the user's movement. When the SMF is responsible for the user to initiate the service, the network side establishes a corresponding session connection, and provides a specific service for the user. In particular, the N4 interface between the SMF and the UPF sends a packet forwarding policy and a QoS policy to the UPF.

An important difference in the 5G architecture compared to the 4G architecture is that the access and mobility management functions AMF are separated from the session management function SMF. This means that when the user equipment (User Equipment, UE) initiates a session, that is, the UE uses the N1 interface between the UE and the AMF to send a Non-Access Stadium (NAS) request message, and carries the session in the NAS request message. Management (SMS) message, AMF needs to forward the above SM message to SMF processing.

However, the current communication protocol mechanism does not provide a scheme for distinguishing between the NAS request message and the SM message by the AMF and the SMF respectively, and the AMF and the SMF cannot distinguish the messages when the terminal device sends the multiple NAS request messages; further, the AMF After sending a reply message with the SMF, the UE side also cannot identify which reply of the 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

The embodiment of the invention provides a method for transmitting a message and a device for avoiding confusion when the terminal device sends multiple messages of the same type to the AMF.

An embodiment of the present invention provides a method for transmitting a message, including:

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

Sending 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 may be carried to the third message of the third-party device; it may be understood that the third message is sent to the third-party device, The type of the second message is determined; since the type of the second message may be many, the third-party device may be specifically defined in the embodiment of the present invention. In addition, the second message may not necessarily have only one, even if only one of the second messages can be sent to multiple third-party devices, the third-party device should not be understood as the only one device.

The first parameter and the 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 determines 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 the two parameters to retrieve or refer to the first message and the second message.

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

In an optional implementation, an implementation of the reply message of the first message is further provided, where the method further includes:

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

Because the second parameter is used to distinguish the second message, the second parameter may be carried in the response message of the second message, and the AMF may put the response message into the reply message of the first message, and then the reply message arrives at the terminal. After the device, the first parameter determines that the reply message is used for the first message, and the second parameter determines 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.

It should be noted that, based on the foregoing description, the first message may be any message that is transmitted between the terminal device and the AMF, as long as the message sent to the third-party device is included therein to satisfy the technical problem involved in the embodiments of the present invention. category. Therefore, the above examples of NAS request messages or NAS transfer messages should not be construed as limiting the uniqueness of the embodiments of the present invention.

In an optional implementation, the embodiment of the present invention further provides a specific implementation of the AMF selecting 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 the third party device based on the type of the second message.

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

Or the second message includes: an extensible authentication protocol EAP message, where the third-party device includes: an Authentication Server Function (AUSF);

Or the second message includes: a short message, where the third party device includes: a Short Message Service Function (SMSF).

It is to be understood that there may be many types of second messages based on the foregoing description, and thus the above examples should not be construed as limiting the uniqueness of the embodiments of the present invention.

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

Session establishment message, session modification message, or session deletion message.

The SM message is the second message sent to the SMF, so the SM message can be any function that the SMF can provide. The above three are examples of more common messages.

In an optional implementation, the first message carries the first parameter, where the first parameter carries the first parameter, including:

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 a message header, which is usually the protocol header of the message, and the other part except the message header is the message body.

In an optional implementation, an optional implementation that the first message carries the second message is further provided, where the second message that is sent to the at least one third-party device in the first message includes: The second message is included in a container cell of a message.

Based on the second message being included in the container cell, the container cell can have a container header and a container body, so the second parameter can be carried in the container header or container body.

In an optional implementation, an implementation of other messages carried in the second message is also provided, where the second message carries a message family type, and the message family type is used to determine the message attribution. Standard organization.

The message family type can be used to inform the AMF how to identify the type of the second message. The type of the second message will use a relatively short, for example, sequence number to indicate the type of the message. Different sequence numbers in different message families will indicate different meanings. Therefore, informing the message family type will enable the AMF to accurately identify the type of the second message, thereby accurately determining which third party device is.

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

In an optional implementation, an implementation scheme of the terminal device using different types of access networks is also provided, as follows: the first message further includes:

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

The sending, by the AMF, the reply message to the terminal device includes:

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

An optional implementation manner is further provided, where the access type parameter is carried in the first message, 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, an optional implementation of the first parameter and the second parameter is further provided as follows: at least one of the first parameter and the second parameter is a process transaction identifier (Procedure Transaction Identity, PTI) parameters.

The second embodiment of the present invention further 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 to the at least one third-party device, where the third-party device is the terminal device and the network device other than the AMF, and the first message carries the first parameter. The second message carries the second parameter, where 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 from the second message, and accordingly, in the network. When the AMF and the third-party device return the reply message, the two-layer parameters may be separately used to identify, so that the terminal device can distinguish which reply the reply message is to which message.

In an optional implementation, 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, the reply message carrying the response message, where the reply message carries the first parameter, and the response message carries the second parameter;

Determining, by the terminal device, that the reply message is used to reply to the first message according to the first parameter that is carried in the reply message, and determining, according to the second parameter carried in the response message, that the response message is used to respond 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.

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;

Or 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, where the third-party device includes: a short message service function SMSF.

In an optional implementation manner, the SM message includes:

Session establishment message, session modification message, or session deletion message.

In an optional implementation manner, the carrying 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 an optional implementation manner, the carrying, by the first message, the second message sent to the at least one third-party device includes: the second message is included in a container cell of the first 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, the message family types include: 3rd Generation Partnership Project 3GPP, Internet Engineering Task Force IETF, Institute of Electrical and Electronics Engineers IEEE, International Telecommunications 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 a type of access network;

The receiving the reply message includes:

The reply message is received using an 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, at least one of the first parameter and the second parameter is a process transaction identifier PTI parameter.

The third embodiment of the present invention further provides an access and mobility management function entity, including:

a first receiving unit, configured to receive a first message from the terminal device, where the first message carries a second message sent to the at least one third-party device, where the third-party device is the terminal device and the access And the network device other than the mobile management function entity AMF, the first message carries a 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 is 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 function entity further includes:

a second receiving unit, configured to receive, by the third-party device, a response message that includes the second message of the second parameter, 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, where 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 transport message.

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

And a device selection unit, configured to select the third-party device based on a 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;

Or 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, where the third-party device includes: a short message service function SMSF.

In an optional implementation manner, the SM message includes:

Session establishment message, session modification message, or session deletion message.

In an optional implementation manner, the carrying 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 an optional implementation manner, the carrying, by the first message, the second message sent to the at least one third-party device includes: the second message is included in a container cell of the first 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 Electronics Engineers IEEE, International Telecommunication Union ITU, European Telecommunications Standards Institute ETSI, and International Organization for Standardization 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 a type of access network;

The second sending unit is configured to send the reply message to the terminal device by using an 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.

The fourth 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 terminal device and the access and mobility management function entity AMF The first network 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;

And 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, after the sending unit sends the first message to the AMF, a reply message from the AMF, where the reply message carries the response message, where the reply message carries the a first parameter, where the response message carries the second parameter;

a message confirming unit, configured to determine, according to the first parameter carried in the reply message, that the reply message is used to reply to the first message, and determine the response message according to the second parameter carried in the response message 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 a type of access network;

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

The fifth embodiment of the present invention further provides an access and mobility management function entity, including: an input and output device, a processor, and a memory, where executable instructions are stored, and the processor is executing the Execution of the instructions implements the method flow of any of the preceding aspects.

The 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, and the processor executes the executable instruction to implement the foregoing two The method flow of any of the aspects provided by the aspect.

The seventh embodiment of the present invention further provides a storage medium, where the storage medium includes executable instructions, and in the case that the executable instructions are executed, the method flow of any one of the foregoing aspects or the two aspects is implemented. .

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

In the embodiment of the present invention, the terminal device includes a second message sent to the third device in the first message sent to the AMF, and the first message and the second message are respectively identified by using two layers of parameters, then for the AMF and the In the case of a three-party device, when the terminal device sends a plurality of messages of the same type as the first message, the first message and the second message can still be distinguished, so that confusion can be avoided.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the background art, the drawings to be used in the embodiments of the present invention or the background art will be described below.

1 is a schematic structural diagram of a system 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 structural diagram of a NAS message according to an embodiment of the present invention;

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

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

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

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

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

8 is a schematic structural view 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 description

The embodiments of the present invention are described below in conjunction with the accompanying drawings in the embodiments of the present invention.

If the system is a 5G communication system, as shown in Figure 1, it includes: UE, Radio Access Network (RNA) or Access Network (AN), User Interface Function (User Port Function). , UPF), Data Network (DN), AMF, SMF, Packet Control Function (PCF), Application Function (AF), Authentication Server Function (AUSF), Unified Data Management (UDM); communicate using the N1-N15 interface.

FIG. 2 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 the at least one third-party device, where the first message carries the first parameter, and 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. The first parameter and the second parameter are unique and are used to distinguish different messages; then, the device that receives the first message and the second message may use, in addition to distinguishing between the first message and the second message, For other purposes such as indexing.

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

203: After executing the content of the second message request, the third device returns a response message of the second message, where 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 foregoing reply message, the terminal device finds the first parameter and the second parameter after parsing, and then determining, according to the first parameter, that the reply message user replies to the first message, and may determine, 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, the terminal device includes a second message addressed to the third device in the first message sent to the AMF, and uses the two layers of parameters to identify the first message and the second message respectively, then for the AMF and the third party. In the case of the device, 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 that confusion can be avoided.

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

When the UE sends multiple NAS messages to the AMF, and both carry the Session Management (SM) request message, the AMF and the SMF will not be able to distinguish the received NAS messages, so the AMF and the SMF are The side will be confused; correspondingly, the reply message sent by the AMF and the SMF, the UE side will also be unable to identify which NAS message and the SM request message were sent before.

The embodiment of the present invention is to solve the problem that the AMF and other devices on the network side track and identify the messages of the multiple processes in the case that the UE initiates multiple processes to the AMF, and the embodiment of the present invention can also support multiple types of Message nesting and message routing. In the example of the embodiment, the SM request message may be carried in the NAS message, and the other types of message parameters may be further extended to implement message routing based on the specific message type. The embodiment of the present invention can be applied to a 5G system architecture, including a 3GPP access and a non-3GPP access scenario, and can be applied to any access or session management process. The following embodiment uses a session management process as an example for illustration. Network elements involved in the examples of this embodiment include: AMF, SMF, UE, AN, and the like. 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 solid Access Gateway Function (AGF), etc.

In the embodiment of the present invention, a multi-layer process index parameter (such as: Process Transaction Identity (PTI)) and a container parameter are defined in the NAS message. The above container parameters can support multiple message types, such as 3GPP defined session manager (SMS) type, Short Message Service (SMS) type, or other standard organization-defined extensible authentication protocol (Extensible). Authentication Protocol (EAP) message type, 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 a PTI and a message type. The NAS message body includes an information element (IE) and a UE identifier. (Identity, ID), registration type, container.

The container includes: a PTI, a protocol type, a protocol discriminator, and a container IE. The container IE may contain the specific content of the second message.

More specifically, as shown in FIG. 3B, the horizontal direction 1-8 and the vertical byte 1-m+1 are the storage spaces occupied by the respective parts. The first message includes a security header type, a protocol identifier, an extended protocol identifier, an access and mobile transaction identifier, a message type, a mobility management cell, and a specific content of the second message is included in the container, where the container includes: Container header, PDU session identifier, protocol specifier, message family type, session transaction identifier, message type, session cell; other mobile management cells may be included because the first message may contain messages addressed to other third party devices .

As shown in FIG. 4, it is an example of an embodiment of the present invention, which is specifically 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 an SMF.

In this embodiment, the SM message type is not uniquely defined, and the SM message may be: a PDU session establishment request message.

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

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

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

Further, in order to support the NAS request message carrying a message type other than the SM message, a container parameter (Container) may be defined in the NAS message, and the container parameter may include a protocol identifier, and may further include a protocol type. The protocol type is used to indicate which standard organization is included in the container, such as setting the protocol type to the 3GPP protocol family, or the IETF protocol family, or the IEEE protocol family. The protocol identifier is used to indicate a specific message type, such as a session request message, a session modification message, and the like. Taking the SM message as the SM session setup message as an example, the protocol type is set to the 3GPP protocol suite, and the protocol identifier is set to the PDU session establishment request message. Taking the authentication authentication message as an example, the protocol type is set to IETF, and the protocol identifier is set to an 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 NAS request message also carries the SM message. In order to distinguish from the ongoing session establishment process in 401A, the UE sets the first flow 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. Further, the UE sets the second flow index parameter PTI 2 of the SM message to B2. For the carrying manner of the PTI in the NAS request message and the SM message, reference may be made to the foregoing, and details are not described herein again.

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

402B: The same as the processing mode of the 402A, 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.

404A: The SMF sends an SM response message through the N11 interface, where the SM response message includes a second PTI. Based on the foregoing SM message being a PDU session setup request message, then the SM response message is a PDU Session Establishment 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: Same as 404A processing mode, it should be noted that the SMF sets the second PTI value to B2.

405A: The AMF receives the SM response message from the N11 interface. The AMF carries the above SM response message in the NAS reply message and sends it to the UE. The NAS reply message includes a first PTI, and the AMF sets the first PTI to a 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 may be determined that the NAS reply message corresponds to the previously sent NAS request message with the same first PTI value. The UE corresponds to the previously sent SM message with the same second PTI value based on the second PTI 2=B1 included in the SM response message.

405B: AMF is the same as step 405A, and the AMF sets the first PTI value to A2. The operation principle of the UE is the same as that of the 405A, and details are not described herein again.

This embodiment supports carrying multiple layers of PTI values in a NAS message. The UE and the network side network element respectively distinguish the respective messages based on different PTI values, thereby avoiding message confusion caused by multi-message concurrency. In addition, the embodiment also supports other message types including the SM message 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 taken as an example. The difference from the previous embodiment is that the multi-session concurrency of the embodiment uses different access technologies, that is, the 3GPP side and the Non-3GPP side simultaneously trigger the session flow. The above non-3GPP access technologies include Wireless Local Area Network (WLAN) access, or fixed network access.

501A: The UE initiates a session establishment process on the 3GPP side, that is, the UE sends a NAS request message, and the NAS request message includes a session message (SM message), and the PTI is set in the previous embodiment 401A, and details are not described herein again. In addition, the UE further includes an access type indication in the NAS request message. The UE may set the above access type to 3GPP access, or LTE access, or 5G RAN access, etc.; assume: RAN.

The access type parameter may be carried in the following manner: the access request parameter is included in the NAS request message header, or the access request 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, where the NAS request message includes a session message (SM message). The PTI is set up in the same manner as the previous embodiment 401B, and details are not described herein again. In addition, the UE sets the access type parameter further included in the NAS request message to non-3GPP access, or WLAN access, or fixed network access.

502A: The previous embodiment 402A is processed by the PTI on the AMF side, and details are not described herein again. In addition, the AMF obtains and stores the access type parameters carried in the NAS request message. The AMF stores the access type parameter of the 3GPP, and can also establish a binding relationship between the NAS request message and the access type.

502B: The previous embodiment 402B is processed by the PTI on the AMF side, and details are not described herein again. In addition, the AMF obtains and stores the access type parameters carried in the NAS request message. The AMF stores non-3GPP access type parameters.

The foregoing 502B and its subsequent steps are the same as the previous embodiment. The AMF sends a reply message to the UE in the 505A.

505A: The AMF sends a reply message of the first NAS request message, and the PTI process is the same as 405A. In addition, the AMF transmits the reply message requested by the NAS to the UE through the access network corresponding to the access type, based on the stored 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 of the second NAS request message, and the PTI process is the same as 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.

In this embodiment, on the basis of the previous embodiment, when the process is concurrent between different access technology networks, the process can be completed in the original access network side.

An embodiment of the present invention further provides an access and mobility management function entity, as shown in FIG. 6, including:

The first receiving unit 601 is configured to receive a first message from the terminal device, where the first message carries a second message sent to the at least one third-party device, where the third-party device is the terminal device and the And the network device other than the mobile management function entity AMF, the first message carries a 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, and the structure included in the embodiment is not necessarily included in the structure unless it is explicitly indicated.

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

The second receiving unit 603 is configured to receive a response message of the second message that is sent by the third-party device that includes the second parameter, 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, where 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 transport message.

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

The device selection unit 605 is 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;

Or 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, where the third-party device includes: a short message service function SMSF.

In an optional implementation manner, the SM message includes:

Session establishment message, session modification message, or session deletion message.

In an optional implementation manner, the carrying 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 an optional implementation manner, the carrying, by the first message, the second message sent to the at least one third-party device includes: the second message is included in a container cell of the first 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 Electronics Engineers IEEE, International Telecommunication Union ITU, European Telecommunications Standards Institute ETSI, and International Organization for Standardization 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 a type of access network;

The second sending unit 604 is configured to send the reply message to the terminal device by using an 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.

The embodiment of the invention further provides a terminal device, as shown in FIG. 7, comprising:

The message generating unit 701 is 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 The first message carries the first parameter, and the second message carries the second parameter, where the first parameter is used to identify the first message, and the second parameter is used by the network device. Identifying the second message;

The sending unit 702 is 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. The structure included in the embodiment is not necessarily included in the structure unless it is explicitly indicated.

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

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

The message confirming unit 704 is configured to determine, according to the first parameter that is carried in the reply message, that the reply message is used to reply to the first message, and determine the response message according to the second parameter carried in the response message. Used to respond 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 a type of access network;

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

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

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

The memory 803 can be used for the buffer required by the processor 802 to perform data processing, and can also be used to provide a storage space requirement for transmitting or receiving data;

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

The memory 803 includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), an Erasable Programmable Read Only Memory (EPROM), or A Compact Disc Read-Only Memory (CD-ROM) for storing related instructions and data. The input and output device 801 is for receiving and transmitting data.

The processor 802 may be one or more central processing units (CPUs). In the case where the processor 802 is a CPU, the CPU may be a single core CPU or a multi-core CPU.

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

The embodiment of the present invention further provides a terminal device, including: an input and output device 901, a processor 902, and a memory 903;

The memory 903 can be used by the processor 902 to perform a buffer required for data processing, and can also be used to provide a storage space requirement for transmitting or receiving data;

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

Memory 903 includes, but is not limited to, RAM, ROM, EPROM, or CD-ROM, which is used for related instructions and data. The input and output device 901 is for receiving and transmitting data.

The processor 902 may be one or more CPUs. In the case where the processor 902 is a CPU, the CPU may be a single core CPU or a multi-core CPU.

Executable instructions are stored in the memory 903, and the processor 903 executes the executable instructions to implement the method flow of any one of the foregoing executions 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 AMF and the transmitting unit and the receiving unit of the terminal device in the previous embodiment, and the specific content that the corresponding processor instructs the input and output device to perform may be For the implementation of the foregoing AMF and the terminal device, reference may also be made to the method embodiment, and details are not described herein again.

The embodiment of the present invention further provides a storage medium, where the executable medium includes executable instructions, and in the case that the executable instructions are executed, the method flow of any one of the embodiments provided by the embodiments of the present invention is implemented.

A person skilled in the art can understand that all or part of the steps of implementing the above embodiments can be completed by a program to instruct related hardware, and the above program can be stored in a readable storage medium of a device, when executed, Including all or part of the above steps, the above storage medium, such as: FLASH, EEPROM, and the like.

The foregoing embodiments of the present invention are further described in detail, and it is understood that the various embodiments may be combined, and the above is only the embodiment of the present invention, and It is intended that the present invention be construed as being limited to the scope of the invention.

Claims (34)

A method for transmitting a message, comprising: The access and mobility management function entity AMF receives the first message from the terminal device; the first message carries a second message sent to the at least one third-party device, where the third-party device is the terminal device and the AMF The first message carries the first parameter, and the second message carries the second parameter, where the first parameter is used to identify the first message, and the second parameter is used by the network device. Identifying the second message; Sending the second message to the third-party device, where the second message carries the second parameter. The method of claim 1 wherein the method further comprises: After receiving the response message of the second message that includes the second parameter, the AMF sends a reply message of the first message to the terminal device, where the reply message carries the response message, The response message carries the first parameter, and the response message carries the second parameter. The method according to claim 1, wherein the first message comprises: a non-access stratum NAS request message, or a non-access stratum NAS transport message. The method of claim 1, wherein before the sending the second message to the third party device, the method further comprises: The AMF selects the third party device based on the type of the second message. The method according to any one of claims 1 to 4, wherein the second message comprises: a session management SM message, and the third party device comprises: a session management function SMF; Or 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, where the third-party device includes: a short message service function SMSF. The method according to claim 5, wherein the SM message comprises: Session establishment message, session modification message, or session deletion message. The method according to claim 1, 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. The method according to claim 1, wherein the carrying the second message to the at least one third party device in the first message comprises: the second message is included in a container cell of the first message. The method of claim 1, wherein the second message carries a message family type, the message family type being used to determine a standard organization to which the message belongs. The method according to claim 9, wherein the message family type comprises: 3rd Generation Partnership Project 3GPP, Internet Engineering Task Force IETF, Institute of Electrical and Electronics Engineers IEEE, International Telecommunication Union ITU, European Telecommunications Standards Institute ETSI, And at least one of the International Organization for Standardization ISO. The method according to claim 2, wherein the first message further comprises: An access type parameter, where the access type parameter is used to indicate a type of access network; The sending, by the AMF, the reply message to the terminal device includes: The AMF sends the reply message to the terminal device by using an access network indicated by the access type parameter. The method according to claim 11, wherein the first message header carries the access type parameter, or the message body of the first message carries the access type parameter. The method according to any one of claims 1 to 4, characterized in that at least one of the first parameter and the second parameter is a process transaction identification PTI parameter. 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 to the at least one third-party device, where the third-party device is the terminal device and the network device other than the AMF, and the first message carries the first parameter. The second message carries the second parameter, where the first parameter is used to identify the first message, and the second parameter is used to identify the second message. The method according to claim 14, wherein 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, the reply message carrying the response message, where the reply message carries the first parameter, and the response message carries the second parameter; Determining, by the terminal device, that the reply message is used to reply to the first message according to the first parameter that is carried in the reply message, and determining, according to the second parameter carried in the response message, that the response message is used to respond The second message. The method according to claim 15, wherein the first message further comprises: An access type parameter, where the access type parameter is used to indicate a type of access network; The receiving the reply message includes: The reply message is received using an access network indicated by the access type parameter. An access and mobility management functional entity, comprising: a first receiving unit, configured to receive a first message from the terminal device, where the first message carries a second message sent to the at least one third-party device, where the third-party device is the terminal device and the access And the network device other than the mobile management function entity AMF, the first message carries a 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 is configured to send the second message to the third-party device, where the second message carries the second parameter. The access and mobility management function entity according to claim 17, wherein the access and mobility management function entity further comprises: a second receiving unit, configured to receive, by the third-party device, a response message that includes the second message of the second parameter, 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, where the reply message carries the first parameter. The access and mobility management function entity according to claim 17, wherein the first message comprises: a non-access stratum NAS request message or a non-access stratum NAS transport message. The access and mobility management function entity according to claim 17, wherein the access and mobility management function entity further comprises: And a device selection unit, configured to select the third-party device based on a type of the second message before the first sending unit sends the second message to the third-party device. The access and mobility management function entity according to any one of claims 17 to 20, wherein the second message comprises: a session management SM message, and the third party device comprises: a session management function SMF; Or 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, where the third-party device includes: a short message service function SMSF. The access and mobility management function entity according to claim 21, wherein the SM message comprises: Session establishment message, session modification message, or session deletion message. The access and mobility management function entity according to claim 17, 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. The access and mobility management function entity according to claim 17, wherein the carrying, by the first message, the second message sent to the at least one third-party device comprises: the container cell of the first message Said the second message. The access and mobility management function entity according to claim 17, 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. The access and mobility management function entity according to claim 25, wherein the message family type comprises: 3rd Generation Partnership Project 3GPP, Internet Engineering Task Force IETF Institute of Electrical and Electronics Engineers IEEE, International Telecommunication Union ITU, Europe At least one of the Telecommunications Standards Institute ETSI and the International Organization for Standardization ISO. The access and mobility management function entity of claim 18, wherein the first message further comprises: An access type parameter, where the access type parameter is used to indicate a type of access network; The second sending unit is configured to send the reply message to the terminal device by using an access network indicated by the access type parameter. The access and mobility management function entity according to claim 27, wherein the first message header carries the access type parameter, or the message body of the first message carries the access type parameter . The access and mobility management function entity according to any one of claims 17 to 20, wherein at least one of the first parameter and the second parameter is a process transaction identifier PTI parameter. 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 terminal device and the access and mobility management function entity AMF The first network 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; And a sending unit, configured to send the first message to the AMF. The terminal device according to claim 30, wherein the terminal device further comprises: a receiving unit, configured to receive, after the sending unit sends the first message to the AMF, a reply message from the AMF, where the reply message carries the response message, where the reply message carries the a first parameter, where the response message carries the second parameter; a message confirming unit, configured to determine, according to the first parameter carried in the reply message, that the reply message is used to reply to the first message, and determine the response message according to the second parameter carried in the response message Responding to the second message. The terminal device according to claim 30 or 31, wherein the first message further includes: An access type parameter, where the access type parameter is used to indicate a type of access network; The receiving unit is configured to receive the reply message by using an access network indicated by the access type parameter. An access and mobility management functional entity includes: an input and output device, a processor, and a memory, wherein Executable instructions are stored in the memory, and the processor executes the executable instructions to implement the method flow of any one of claims 1 to 13. A terminal device includes: an input and output device, a processor, and a memory, wherein Executable instructions are stored in the memory, and the processor executes the executable instructions to implement the method flow of any one of claims 14 to 16.

Images