WO2019034058A1

WO2019034058A1 - Message transmission method and apparatus, information acquisition method and apparatus, terminal, and access and mobility management function

Info

Publication number: WO2019034058A1
Application number: PCT/CN2018/100502
Authority: WO
Inventors: 卢飞; 朱进国
Original assignee: 中兴通讯股份有限公司
Priority date: 2017-08-14
Filing date: 2018-08-14
Publication date: 2019-02-21
Also published as: CN109392082A

Abstract

A message transmission method and apparatus, an information acquisition method and apparatus, a terminal, and an access and mobility management function. The message transmission method comprises: sending a registration request message to a first access and mobility management function (AMF), wherein the registration request message carries validity information about a global unique temporary identifier allocated by a second AMF for a terminal, wherein the validity information is used for determining whether to acquire, from the second AMF, a non-3rd generation partnership project (3GPP) access context.

Description

Message transmission, information acquisition method, device, terminal, and access and mobility management entity

The present disclosure claims the priority of the Chinese patent application entitled "Message Transmission Method and Apparatus, Terminal, Access and Mobility Management Entity" on August 14, 2017, application number 201710693599.5, the entire contents of the application The disclosure is incorporated by reference.

Technical field

The present disclosure relates to the field of communication technologies, for example, to a message transmission, an information acquisition method, an apparatus, a terminal, and an access and mobility management entity.

Background technique

Mobile communications has evolved into the 4th-Generation Mobile Communication Technology (4G) phase. Compared with previous generations, the 4G network architecture is based on the Internet Protocol (IP) transmission. The 3rd Generation Partnership Project (3GPP) is studying the 5th-Generation Mobile Communication Technology (5G) network architecture.

5G-Globally Unique Temporary Identity (5G-Globally Unique Temporary Identity, 5G-GUTI) allocated by AMF in the process of 3GPP Access and Mobility Management Function (AMF) and non-3GPP access to AMF The format is the same. When the UE carries multiple 5G-GUTIs in the registration request message, the AMF cannot determine whether the context needs to be obtained according to the 5G-GUTI to the peer AMF. If the UE acquires the context only according to multiple 5G-GUTIs, the UE may be caused by the UE. The AMF that is accessed by the 5G RAN under the same PLMN is different from the AMF that is not accessed by the 3GPP. If the AMF obtains the context from the peer AMF that allocates 5G-GUTI to each of the multiple 5G-GUTIs obtained, it will cause unnecessary information. Make the cost.

Summary of the invention

An embodiment of the present disclosure provides a message sending, an information acquiring method, an apparatus, a terminal, and an access and mobility management entity, so as to solve at least the AMF cannot be determined when the terminal registration request message carries multiple 5G-GUTIs in the related art. Whether you need to get the context of the peer AMF.

The present disclosure provides a message sending method, including: sending a registration request message to a first access and mobility management entity AMF, where the registration request message carries validity information of a globally unique temporary identifier allocated by the second AMF to the terminal. And wherein the validity information is used to determine whether to obtain a non-3rd Generation Partnership Project 3GPP access context to the second AMF.

The present disclosure also provides an information acquisition method, including: receiving a registration request message, where the registration request message carries validity information of a globally unique temporary identifier assigned by the specified access and mobility management entity AMF to the terminal; The information determines whether a non-3rd Generation Partnership Project 3GPP access context is obtained from the designated AMF.

The present disclosure further provides a message sending apparatus, including: a sending module, configured to send a registration request message to a first access and mobility management entity AMF, where the registration request message carries a second AMF for the terminal to be globally unique Validity information of the temporary identity, wherein the validity information is used to determine whether to obtain a non-3rd Generation Partnership Project 3GPP access context to the second AMF.

The present disclosure further provides an information obtaining apparatus, comprising: a receiving module, configured to receive a registration request message, wherein the registration request message carries the validity of the global unique temporary identifier allocated by the specified access and mobility management entity AMF for the terminal And a determining module configured to determine whether to obtain a non-3rd Generation Partnership Project 3GPP access context from the designated AMF based on the validity information.

The present disclosure provides a storage medium including a stored program that executes the above-described message transmitting method while the program is running.

The present disclosure also provides a storage medium including a stored program that executes the above-described information acquisition method while the program is running.

The present disclosure also provides a processor that is configured to run a program that executes the above-described message sending method while the program is running.

The present disclosure provides a processor that is configured to run a program that executes the above-described information acquisition method while the program is running.

DRAWINGS

1 is a schematic structural diagram of interworking between a 3GPP and a non-3GPP access network in a 5G network according to an embodiment;

2 is a schematic structural diagram of interworking between a 4G network and a 5G network according to an embodiment;

FIG. 3 is a schematic flowchart of a registration process of a UE in a 5G network access according to an embodiment; FIG.

4 is a flowchart of a UE moving from 4G to 5G RAN 3GPP access according to an embodiment;

FIG. 5 is a block diagram showing the hardware structure of a mobile terminal according to an embodiment of a message sending method;

FIG. 6 is a schematic flowchart of a message sending method according to an embodiment; FIG.

FIG. 7 is a schematic flowchart diagram of an information acquisition method according to an embodiment; FIG.

FIG. 8 is a structural block diagram of a message sending apparatus according to an embodiment; FIG.

FIG. 9 is a structural block diagram of an information acquiring apparatus according to an embodiment; FIG.

10 is a schematic flow chart of Embodiment 1;

11 is a schematic flow chart of the second embodiment;

FIG. 12 is a schematic flow chart of the third embodiment.

Detailed ways

The present disclosure will be hereinafter described with reference to the drawings in conjunction with the embodiments.

The terms "first" or "second" and the like in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe the specified order or order.

FIG. 1 is a schematic structural diagram of interworking between a 3GPP network and a non-3GPP access network in a 5G network according to an embodiment; FIG. 2 is a schematic structural diagram of interworking between a 4G network and a 5G network according to an embodiment. The functions of multiple network elements in the architecture shown in Figure 1 and Figure 2 are as follows:

User equipment (UE): accesses the 5G network through the wireless air interface and obtains services. The terminal exchanges information through the air interface and the base station, and performs mobility management through non-access stratum (NAS) and core network. Entity interaction information.

Radio Access Network (RAN): responsible for air interface resource scheduling and air interface connection management of the terminal accessing the network. The 3GPP access base station in the 5G network is called a 5G RAN. In order to ensure the consistency of the N2 interface and the N1 interface, a non-3GPP Interworking Function (N3IWF) is introduced in the 5G system and the non-3GPP access system, which is responsible for forwarding NAS messages in the non-3GPP system and selecting AMF. The data plane channel between the User Plane Function (UPF) and the N3IWF is established.

Mobile management entity: In the 5G core network, AMF mainly controls user mobility management, including location registration and temporary identity allocation, maintaining idle state (IDLE) and connection (CONNECT) state, and state transition.

Session Management Function (SMF): The functions mainly include the maintenance of the Protocol Data Unit (PDU) session, including the functions of session management such as creation, modification, and deletion; and the function of triggering paging in the IDLE state. .

User Plane Function (UPF): It is the user plane access point of the terminal accessing the Public Data Network (PDN) network, which can be responsible for allocating the user's Internet Protocol (IP) address and session path. Functions such as binding and updating are anchor points for users to switch or move between the 3GPP system and the non-3GPP system, thereby ensuring business continuity.

FIG. 3 is a schematic flowchart of a registration process of a UE in a 5G network access according to an embodiment. The AMF accessed by the UE from the N3IWF under the same Public Land Mobile Network (PLMN) must be the same AMF as the AMF accessed from the 5G RAN.

Step 300: The UE sends a Radio Resource Connection (RRC) message to the 5G RAN, where the message carries a registration request (Registration Request) message, and the registration request message carries a globally unique temporary identifier (5G-Globally Unique Temporary Identity, 5G- GUTI) and initial access indication, or International Mobile Station Identity (IMSI) and initial access indication. The initial access indication is used to notify the network that this registration request message belongs to the initial access request. If the UE is already accessing the non-3GPP network of the same PLMN and the AMF allocates the 5G-GUTI, the UE will carry the 5G-GUTI in the registration request message.

In step 301, the 5G RAN selects AMF (new AMF) and forwards the registration request message to the AMF.

Step 302: If the registration request message carries the 5G-GUTI in step 300, the AMF selects the original AMF according to the 5G-GUTI, and sends a UE Context Transfer Request message to the original AMF to obtain the user IMSI and mobility management. (Mobility Management, MM) context.

Step 303: The original AMF returns a UE context transfer response (UE context Transfer Response) message to the target AMF (new AMF), where the message carries the user IMSI and the MM context. If the AMF still has the MM in the non-3GPP access. Context, the original AMF also returns the MM context of the non-3GPP access and the N2-application protocol (N2AP) identity (Identity, ID) binding relationship with the N3IWF.

Step 304: The target AMF sends a registration complete notification (Registration Complete Notify message) to the original AMF to notify the original AMF that the UE has been taken over by the target AMF.

Step 305: The target AMF sends a UE context management-registration request message to the unified data management (UDM), where the message carries the IMSI, the UE access type, and the PLMN ID.

Step 306: The UDM returns a UE context management-registration response message to the target AMF, where the message carries the user's subscription data.

Step 307: The UDM sends a UE context management-Removal request message to the original AMF, indicating that the original AMF can delete the UE context.

Step 308, the original AMF returns a UE context management-Removal Response message to the UDM.

Step 309: The target AMF may initiate an N2 AP request message to update the N2-AP binding relationship to the N3IWF, where the message carries an N2-AP Transport Network Layer (TNL) address and an N2-AP ID. This step is to ensure that under the same PLMN, the AMF selected by the non-3GPP access and the AMF selected by the 3GPP 5G access are the same AMF.

Step 310: The N3IWF updates the binding relationship and returns an N2 AP response message.

Step 311: If the target AMF accepts the registration request, the target AMF returns a Registration Accept message to the UE, where the message carries the newly allocated GUTI and carries a valid registration area.

Step 312: The UE returns a Registration Complete message to the target AMF, indicating that the GUTI has taken effect.

4 is a flow chart of a UE moving from 4G to 5G RAN 3GPP access according to an embodiment. As shown in FIG. 4, the method includes the following steps.

In step 401, the UE registers in the 5G network of the PLMN1, and the 5G-GUTI1 is allocated by the AMF1.

Step 402: The UE moves to the 4G network of the same PLMN. In the 4G network, the MME allocates 4G-GUTI2 to the UE.

Step 403: The UE returns to the 5G network of the same PLMN, and the UE sends an RRC message to the 5G RAN, where the message carries a registration request (Registration Request) message, and the registration request message carries 5G-GUTI2 (5G-GUTI2 is 4G-GUTI2) Mapped), 5G-GUTI1 and mobility update indication. The mobile update indication is used to notify the network that this registration request message belongs to a mobility update request.

In step 404, the 5G RAN selects AMF2 (new AMF) and forwards the registration request message to AMF2.

Step 405: The AMF2 selects the original MME according to the 5G-GUTI2, and sends a Context Request message to the MME to obtain the user IMSI and the MM context.

Step 406: The original MME returns a UE context response (Context Response) message to the target AMF2 (new AMF), where the message carries the user IMSI and the MM context.

Step 407: The target AMF2 sends a Context Complete message to the original MME, to notify the original MME that the UE has been taken over by the target AMF2.

Step 408: The AMF2 sends a UE context management-registration request message to the UDM, where the message carries the IMSI, the UE access type, and the PLMN ID.

In step 409, the UDM returns a UE context management-registration response message to the AMF.

Step 410: The UDM sends a Cancel Location Request message to the MME, indicating that the original MME can delete the UE context.

In step 411, the MME returns a Location Cancel Location (ACK) message to the UDM.

Step 412: If the AMF2 accepts the registration request, the AMF2 returns a Registration Accept message to the UE. If the UE registers the 5G-GUTI1 carried in the request message in step 403, the registration accept message may not be carried. The newly allocated GUTI, if the 5G-GUTI1 carried by the UE in the registration request message is not the current AMF allocation, then the AMF2 reassigns the 5G-GUTI and carries it in the Registration Accept message, and carries a valid registration area.

Step 413: The UE returns a Registration Complete message to the AMF2 to indicate that the newly allocated 5G-GUTI has taken effect.

Example 1

The method embodiment provided by this embodiment may be implemented in a mobile terminal, a computer terminal or the like. In this embodiment, the operation is performed on a mobile terminal as an example.

FIG. 5 is a block diagram showing the hardware structure of a mobile terminal in a message sending method according to an embodiment. As shown in FIG. 5, mobile terminal 50 may include one or more (only one of which is shown in FIG. 5) processor 502 (processor 502 may include, but is not limited to, a Microcontroller Unit (MCU) or a programmable logic device A processing device such as a Field-Programmable Gate Array (FPGA), a memory 504 configured to store data, and a transfer device 506 for a communication function. It will be understood by those skilled in the art that the structure shown in FIG. 5 is merely illustrative and does not limit the structure of the above electronic device. For example, mobile terminal 50 may also include more or fewer components than shown in FIG. 5, or have a different configuration than that shown in FIG.

The memory 504 can be configured as a software program and a module for storing application software, such as a program instruction/module corresponding to the message sending method in the embodiment of the present disclosure, and the processor 502 executes a software program and a module stored in the memory 504 to execute a program One or more functional applications and data processing, ie, the methods described below are implemented. Memory 504 can include high speed random access memory and can also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory. In some examples, memory 504 can include memory remotely located relative to processor 502, which can be connected to mobile terminal 50 over a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

Transmission device 506 is arranged to receive or transmit data via a network. The above-described network specific example may include a wireless network provided by a communication provider of the mobile terminal 50. In one example, the transmission device 506 includes a Network Interface Controller (NIC), and the transmission device 506 can be connected to other network devices through the base station to communicate with the Internet. In one example, transmission device 506 can be a radio frequency (RF) module, and transmission device 506 is configured to communicate with the Internet wirelessly.

In this embodiment, a message sending method running on the mobile terminal or running on the network architecture shown in FIG. 1 or FIG. 2 is provided. FIG. 6 is a schematic flowchart of a message sending method according to an embodiment. As shown in FIG. 6, the message sending method provided in this embodiment includes the following steps.

Step 604: Send a registration request message to the first access and mobility management entity AMF, where the registration request message carries validity information of the global unique temporary identifier allocated by the second AMF for the terminal, where the validity information is used for determining Whether to obtain a non-3rd Generation Partnership Project 3GPP access context to the second AMF.

Through the above steps, the registration request message sent to the first AMF carries the validity information of the global unique temporary identifier allocated by the second AMF for the terminal, so that the first AMF can determine whether to the peer AMF based on the validity information. The second AMF is configured to obtain the non-3GPP access context. Therefore, the AMF cannot determine whether the context needs to be obtained from the peer AMF when the terminal is configured to carry multiple 5G-GUTIs, and the unnecessary information is reduced. Make the cost.

In an embodiment, before step 604, the method further includes:

Step 602: After registering from the first base station of the first public land mobile network, move to the second base station of the second public land mobile network and perform access.

In an embodiment, sending the registration request message to the first access and mobility management entity AMF may be performed by: sending a registration request message to the first AMF by using the second base station. For example, the RRC message is sent to the second base station, where the RRC message carries the registration request message; and the second base station forwards the registration request message to the first AMF.

In an embodiment, the validity information may include at least one of the following: a registration state of the terminal under non-3GPP access, a non-registration state of the terminal under non-3GPP access, and a registration state of the terminal under 3GPP access, The non-registered state of the terminal under 3GPP access, the non-3GPP access is valid, and the non-3GPP access is invalid.

In an embodiment, in the case that the validity information includes at least one of the following information, the validity information is used to determine to acquire a non-3GPP access context to the second AMF: the registration state of the terminal under non-3GPP access and non-3GPP Access is valid.

In an embodiment, in the case that the validity information includes at least one of the following information, the validity information is used to determine that the non-3GPP access context is not acquired to the second AMF: the non-registered state of the terminal under the 3GPP access, the terminal The registration state under 3GPP access, the non-registered state in which the terminal is in non-3GPP access, and the non-3GPP access are invalid.

In an embodiment, the execution body of the above steps may be a terminal or the like, but is not limited thereto.

In an embodiment, the foregoing method may be applied to at least one of the following scenarios, but is not limited thereto: the terminal accesses the second AMF through the N3IWF in the second public land mobile network, and passes the first public land mobile network in the second public land mobile network. a base station accesses the third AMF, and then moves to the second public land mobile network to access through the second base station; the terminal accesses the second AMF through the N3IWF in the second public land mobile network, in the first public land mobile network Accessing the 4G network, and then moving to the second public land mobile network to access through the second base station; the terminal accessing the second AMF through the second base station in the second public land mobile network, the terminal moves to the 4G network, and then moves to The second public land mobile network is accessed by the second base station.

In an embodiment, the first base station and the second base station may both be 5G RANs, but the present invention is not limited thereto, and the first base station and the second base station may be better base stations than 5G.

Example 2

An embodiment of the present disclosure also provides an information acquisition method. FIG. 7 is a schematic flowchart diagram of an information acquisition method according to an embodiment. As shown in FIG. 7, the information acquiring method provided in this embodiment includes the following steps.

Step 702: Receive a registration request message, where the registration request message carries validity information of a globally unique temporary identifier assigned by the specified access and mobility management entity AMF to the terminal.

Step 704: Determine, according to the validity information, whether to acquire a non-3rd Generation Partnership Project 3GPP access context to the designated AMF.

Through the above steps, the received registration request message carries the validity information of the globally unique temporary identifier allocated by the specified AMF for the terminal, so that whether the non-3GPP access context is obtained from the peer AMF (designated AMF) can be determined based on the validity information. Therefore, it can be solved that the AMF cannot determine whether the context needs to be acquired to the peer AMF when carrying multiple 5G-GUTIs in the registration request message of the terminal, and reduces unnecessary signaling overhead.

In an embodiment, the foregoing step 704 may be performed as: determining that the non-3GPP access context is acquired to the AMF when the validity information includes at least one of the following information: the registration state of the terminal under non-3GPP access and the non-3GPP The access is valid; if the validity information includes at least one of the following information, determining that the non-3GPP access context is not obtained from the AMF: the terminal is in a non-registered state under the 3GPP access, and the terminal is in a registered state under the 3GPP access, The non-registered state of the terminal under non-3GPP access and the non-3GPP access are invalid.

In an embodiment, the execution body of the above method may be an AMF. In an embodiment, the AMF may be different from the above specified AMF, but is not limited thereto.

Through the description of the above embodiments, those skilled in the art can understand that the method according to the foregoing embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is better. Implementation. Based on such understanding, the technical solution of the present disclosure, which is essential or contributes to the related art, may be embodied in the form of a software product stored in a storage medium (such as a read-only memory (Read-Only Memory). , ROM)/Random Access Memory (RAM), disk or CD-ROM, including a plurality of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, a network device, etc.) to perform the present disclosure The method of any of the embodiments.

Example 3

In the embodiment, a message sending device is also provided, which is used to implement the above-mentioned embodiments, and has not been described again. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is implemented in software in one embodiment, hardware or an implementation of a combination of software and hardware is also possible and contemplated.

FIG. 8 is a structural block diagram of a message sending apparatus according to an embodiment. As shown in FIG. 8, the message sending apparatus provided in this embodiment includes:

The sending module 84 is configured to send a registration request message to the first access and mobility management entity AMF, where the registration request message carries the validity information of the global unique temporary identifier allocated by the second AMF for the terminal, where the validity information It is used to determine whether to obtain a non-3rd Generation Partnership Project 3GPP access context to the second AMF.

In an embodiment, the apparatus further includes a mobile module 82 coupled to the transmitting module 84, configured to be moved from the first base station of the first public land mobile network, to the second base station of the second public land mobile network, and to perform Access.

The first AMF may determine whether to report to the peer AMF based on the validity information, because the registration request message sent to the first AMF carries the validity information of the globally unique temporary identifier allocated by the second AMF to the terminal. The second AMF is configured to obtain the non-3GPP access context. Therefore, the AMF cannot determine whether the context needs to be obtained from the peer AMF when the terminal is configured to carry multiple 5G-GUTIs, and the unnecessary information is reduced. Make the cost.

In an embodiment, the sending module 84 may exist independently in the above device, or may exist in the device together with the moving module 82, but is not limited thereto.

In an embodiment, the foregoing validity information includes at least one of the following: a registration state in which the terminal is in non-3GPP access, a non-registered state in which the terminal is in non-3GPP access, a registration state in which the terminal is in 3GPP access, and a terminal. The non-registered state under the 3GPP access, the non-3GPP access is valid, and the non-3GPP access is invalid.

In an embodiment, in the case that the validity information includes at least one of the following information, the validity information is used to determine to acquire a non-3GPP access context to the second AMF: the registration state of the terminal under non-3GPP access and non-3GPP The access is valid; in the case that the validity information includes at least one of the following information, the validity information is used to determine that the non-3GPP access context is not acquired to the second AMF: the terminal is in a non-registered state under 3GPP access, and the terminal is in 3GPP The registration state under access, the non-registration state of the terminal under non-3GPP access, and the non-3GPP access are invalid.

In an embodiment, the above device may be located in the terminal, but is not limited thereto.

The embodiment further provides a terminal, including a processor, the processor is configured to run a program, wherein the program is executed to execute the message sending method described above.

In an embodiment, the foregoing multiple modules may be implemented by software or hardware. For the latter, the foregoing may be implemented by, but not limited to, the foregoing multiple modules are all located in the same processor; The modules are located in different processors in any combination.

Example 4

FIG. 9 is a structural block diagram of an information acquiring apparatus according to an embodiment. As shown in FIG. 9, the information acquiring apparatus provided in this embodiment includes:

The receiving module 92 is configured to receive a registration request message, where the registration request message carries validity information of a globally unique temporary identifier assigned by the specified access and mobility management entity AMF to the terminal.

The determining module 94 is coupled to the receiving module 92 and configured to determine whether to obtain a non-3rd Generation Partnership Project 3GPP access context to the designated AMF based on the validity information.

By using the foregoing apparatus, the received registration request message carries the validity information of the globally unique temporary identifier allocated by the specified AMF for the terminal, so that it is determined whether to obtain the non-3GPP access context to the peer AMF (designated AMF) based on the validity information. Therefore, it can be solved that the AMF cannot determine whether the context needs to be acquired to the peer AMF when carrying multiple 5G-GUTIs in the registration request message of the terminal, and reduces unnecessary signaling overhead.

In an embodiment, the validity information may include at least one of the following: a registration state of the terminal under non-3GPP access, a non-registration state of the terminal under non-3GPP access, and a registration state of the terminal under 3GPP access, The terminal is in a non-registered state under 3GPP access, the non-3GPP access is valid, and the non-3GPP access is invalid.

In an embodiment, the determining module 94 is configured to determine to acquire a non-3GPP access context to the designated AMF if the validity information includes at least one of the following information: the registration state of the terminal under non-3GPP access and the non-3GPP The access is valid; if the validity information includes at least one of the following information, it is determined that the non-3GPP access context is not obtained from the specified AMF: the terminal is in the non-registered state under the 3GPP access, and the terminal is in the registration state under the 3GPP access And non-3GPP access is invalid.

In an embodiment, the above device may be located in the AMF. In an embodiment, the AMF may be different from the above specified AMF, but is not limited thereto.

In an embodiment of the present disclosure, an access and mobility management entity AMF is further provided, including: a processor, the processor is configured to run a program, and the program is executed to execute the information acquisition method described above.

Example 5

An embodiment of the present disclosure further provides a storage medium, where the storage medium includes a stored program, wherein the program runs to execute any of the methods described above.

In this embodiment, the foregoing storage medium may include, but is not limited to, one or more mediums that can store program codes, such as a USB flash drive, a ROM, a RAM, a mobile hard disk, a magnetic disk, or an optical disk.

An embodiment of the present disclosure also provides a processor configured to execute a program that executes any of the above methods while the program is running.

For specific examples in this embodiment, reference may be made to the examples described in the foregoing embodiments, and details are not described herein again.

The disclosure is further explained below in conjunction with the embodiments.

Embodiment 1

In this embodiment, the UE accesses the AMF through the N3IWF in the PLMN1, the AMF through the 5G RAN in the PLMN2, and then the 5G RAN access of the mobile PLMN1. FIG. 10 is a schematic flow chart of the first embodiment. As shown in FIG. 10, the flow includes the following steps.

In step 1001, the UE registers in the non-3GPP access of the PLMN1, and the 5G-GUTI1 is allocated by the AMF1 (corresponding to the second AMF or the designated AMF in the above embodiment).

In step 1002, the UE registers in the 5G RAN of the PLMN2, and the 5G-GUTI2 is allocated by the AMF2.

In step 1003, the UE moves to the 5G RAN of the PLMN1 and accesses the UE. The UE sends an RRC message to the 5G RAN. The message carries a registration request (Registration Request) message, and the registration request message carries the 5G-GUTI2 and the mobility access indication. The mobility access indication is used to notify the network that this registration request message belongs to a mobility-induced request. Since the UE is already in the non-3GPP network of the same PLMN1, and the AMF1 allocates the 5G-GUTI1, the UE will also carry the 5G-GUTI1 in the registration request message, and carry the validity information of the 5G-GUTI1, and the 5G-GUTI1 is valid. The sexual information includes non-3GPP access registration state (5GMM-REGISTERED) or non-3GPP access.

In step 1004, the 5G RAN selects the AMF, the selected AMF is AMF3, and forwards the registration request message (corresponding to the registration request message in the above embodiment) to the AMF3 (corresponding to the first AMF in the above embodiment).

In step 1005, the AMF3 selects the original AMF2 (old AMF2) according to the 5G-GUTI2 carried in the registration request message in step 1003 to acquire the 3GPP access context, and sends a UE Context Transfer Request message to the AMF2 to obtain the user IMSI and the MM context. .

In step 1006, the original AMF2 returns a UE context transfer response (UE context Transfer Response) message to the target AMF (new AMF3), where the message carries the user IMSI and the MM context.

In step 1007, the target AMF3 sends a registration completion notification Registration Complete Notify message to the original AMF2 for notifying the original AMF3 that the UE has been taken over by the target AMF3.

In step 1008, the AMF3 determines to obtain the non-3GPP access context from the original AMF1 (old AMF1) according to the validity of the 5G-GUTI1 and the 5G-GUTI1 carried in the registration request message in step 1003, and sends a UE context transfer request to the AMF1 (UE Context Transfer Request). The message gets the user IMSI and MM context.

Step 1009: The original AMF1 returns a UE context transfer response (UE context Transfer Response) message to the target AMF (new AMF3), where the message carries the user IMSI, the MM context, and the N2 AP ID binding relationship between the AMF1 and the N3IWF.

In step 1010, the target AMF3 sends a registration complete notification (Registration Complete Notify) message to the original AMF1 for notifying the original AMF1 that the UE has been taken over by the target AMF3.

Step 1011: The AMF3 sends a UE context management-registration request message to the UDM, where the message carries the IMSI, the UE access type, and the PLMN ID.

Step 1012: The UDM returns a UE context management-registration response message to the AMF3, where the message carries the user's subscription data.

Step 1013: The UDM sends a UE context management-Removal request message to the original AMF2, indicating that the original AMF2 can delete the UE context.

In step 1014, the original AMF2 returns a UE context management-Removal Response message to the UDM.

In step 1015, the UDM sends a UE context management-Removal request message to the original AMF1, indicating that the original AMF1 can delete the UE context.

In step 1016, the original AMF1 returns a UE context management-Removal Response message to the UDM.

In step 1017, the AMF3 may initiate an N2 AP request message to the N3IWF to update the binding relationship of the N2-AP, where the message carries the N2-AP TNL address and the N2-AP ID. This step is to ensure that under the same PLMN, the AMF selected by the non-3GPP access and the AMF selected by the 3GPP 5G access are the same AMF.

In step 1018, the N3IWF updates the binding relationship and returns an N2 AP response message.

Step 1019: If the AMF3 accepts the registration request, the AMF3 returns a Registration Accept message to the UE, where the message carries the newly allocated GUTI and carries a valid registration area.

In step 1020, the UE returns a Registration Complete message to the AMF3 to indicate that the GUTI has taken effect.

The SMF that is not related to the present disclosure and the process of interacting with the SMF are omitted in this embodiment.

Embodiment 2

In this embodiment, the UE accesses the AMF through the N3IWF in the PLMN1, and the UE accesses the 4G network in the PLMN2, and then moves to the 5G RAN in the PLMN1 for access. 11 is a schematic flow chart of the second embodiment. As shown in Figure 11, the process includes:

Step 1101: The UE registers in the non-3GPP access of the PLMN1, and allocates 5G-GUTI1 by the AMF1 (corresponding to the second AMF or the designated AMF in the above embodiment).

In step 1102, the UE registers in the 4G RAN of the PLMN2, and the 4G-GUTI2 is allocated by the MME.

Step 1103: The UE moves to the 5G RAN of the PLMN1 and enters the access, and the UE sends an RRC message to the 5G RAN, where the message carries a registration request (Registration Request) message, and the registration request message carries 5G-GUTI2 (mapped by 4G-GUTI2) ) and mobility access instructions. The mobility access indication is used to notify the network that this registration request message belongs to a mobility-induced request. Since the UE is already in the non-3GPP network of the same PLMN1, and the AMF1 allocates 5G-GUTI1, the UE will also carry 5G-GUTI1 in the registration request message, carrying the validity of 5G-GUTI1, and the validity of 5G-GUTI1. Including non-3GPP access registration state (5GMM-REGISTERED) or non-3GPP access is valid.

Step 1104, the 5G RAN selects AMF2 and forwards the registration request message to AMF2.

Step 1105: The AMF2 selects the original MME (old MME) to acquire the 3GPP access context according to the 5G-GUTI2 (mapped by the 4G-GUTI2) carried in the registration request message in the step 1103, and sends a Context Request message to the MME. Obtain the user IMSI and MM context.

In step 1106, the original MME returns a context response (Context Response) message to the target AMF (new AMF2), where the message carries the user IMSI and the MM context.

Step 1107: The target AMF2 sends a Context Complete message to the original MME to notify the original MME that the UE has been taken over by the target AMF2.

Step 1108: The AMF2 determines to obtain the non-3GPP access context from the original AMF1 (old AMF1) according to the validity of the 5G-GUTI1 and the 5G-GUTI1 carried in the registration request message in step 1103, and sends a UE context transfer request to the AMF1 (UE Context Transfer Request). The message gets the user IMSI and MM context.

Step 1109: The original AMF1 returns a UE context transfer response (UE context Transfer Response) message to the target AMF (new AMF2), where the message carries the user IMSI, the MM context, and the N2 AP ID binding relationship between the AMF1 and the N3IWF.

In step 1110, the target AMF2 sends a registration complete notification (Registration Complete Notify message) to the original AMF1 for notifying the original AMF1 that the UE has been taken over by the target AMF2.

Step 1111: The AMF2 sends a UE context management-registration request message to the UDM, where the message carries the IMSI, the UE access type, and the PLMN ID.

Step 1112: The UDM returns a UE context management-registration response message to the AMF2, where the message carries the user's subscription data.

In step 1113, the UDM sends a location cancel request (Cancel Location Request message) to the original MME, indicating that the original MME can delete the UE context.

In step 1114, the original MME returns a Location Cancel Location (ACK) message to the UDM.

In step 1115, the UDM sends a UE context management-removal request message to the original AMF1, indicating that the original AMF1 can delete the UE context.

In step 1116, the original AMF1 returns a UE context management-Removal Response message to the UDM.

Step 1117: The AMF2 may initiate an N2 AP request message to the N3IWF to update the binding relationship of the N2-AP, where the message carries the N2-AP TNL address and the N2-AP ID. This step is to ensure that under the same PLMN, the AMF selected by the non-3GPP access and the AMF selected by the 3GPP 5G access are the same AMF.

In step 1118, the N3IWF updates the binding relationship and returns an N2 AP response message.

Step 1119: If the AMF2 accepts the registration request, the AMF2 returns a Registration Accept message to the UE, where the message carries the newly allocated GUTI and carries a valid registration area.

Step 1120: The UE returns a Registration Complete message to the AMF2 to indicate that the GUTI has taken effect.

Embodiment 3

In this embodiment, the UE accesses the AMF through the 5G RAN in the PLMN1, the UE moves to the 4G network, and then moves to the 5G RAN in the PLMN1 for access. FIG. 12 is a schematic diagram of a process provided by an embodiment of the present disclosure. As shown in FIG. 12, the flow includes the following steps.

Step 1201: The UE registers in the 5G RAN 3GPP access of the PLMN1, and allocates 5G-GUTI1 by the AMF1 (corresponding to the second AMF or the designated AMF in the above embodiment).

In step 1202, the UE registers in the 4G RAN of the PLMN1, and the 4G-GUTI2 is allocated by the MME, and the UE still retains the 5G-GUTI1 in step 1201.

In step 1203, the UE moves to the 5G RAN of the PLMN1 and enters the re-access. The UE sends an RRC message to the 5G RAN. The message carries a registration request (Registration Request) message, and the registration request message carries 5G-GUTI2 (mapped by 4G-GUTI2) And mobile access indication. The mobility access indication is used to notify the network that this registration request message belongs to a mobility-induced request. Because the UE originally accesses and saves 5G-GUTI1 in the 3GPP 5G RAN, the UE will also carry 5G-GUTI1 in the registration request message, and carry the validity of 5G-GUTI1, and the validity of 5G-GUTI1 includes 3GPP access. Non-registered state (5GMM-DEREGISTERED) or non-3GPP access is invalid.

In step 1204, the 5G RAN selects AMF2 and forwards the registration request message to AMF2.

In step 1205, the AMF2 selects the original MME (old MME) to acquire the 3GPP access context according to the 5G-GUTI2 (mapped by the 4G-GUTI2) carried in the registration request message in the step 1203, and sends a Context Request message to the MME. The user IMSI and the MM context are obtained. The AMF determines that the non-3GPP access context is not required to be obtained from the original AMF1 (old AMF1) according to the validity of the 5G-GUTI1 and the 5G-GUTI1 carried in the registration request message in step 1203.

In step 1206, the original MME returns a context response (Context Response message) to the target AMF (new AMF2), where the message carries the user IMSI and the MM context.

Step 1207: The target AMF2 sends a Context Complete message to the original MME, to notify the original MME that the UE has been taken over by the target AMF2.

Step 1208: The AMF2 sends a UE context management-registration request message to the UDM, where the message carries the IMSI, the UE access type, and the PLMN ID.

Step 1209: The UDM returns a UE context management-registration response message to the AMF2, where the message carries the user's subscription data.

Step 1210: The UDM sends a Cancel Location Request message to the original MME, indicating that the original MME can delete the UE context.

In step 1211, the original MME returns a Cancel Location ACK message to the UDM.

Step 1212: If the AMF2 accepts the registration request, the AMF returns a Registration Accept message to the UE, where the message carries the newly allocated GUTI and carries a valid registration area. If the 5G-GUTI1 carried in the registration request message in step 1203 is allocated by AMF2 (AMF1 and AMF2 are exactly the same AMF), then the Registration Accept message may not carry the new GUTI, so the UE will continue to use 5G. -GUTI1.

Step 1213: The UE returns a Registration Complete message to the AMF to indicate that the GUTI has taken effect. If step 1212 does not carry the newly assigned GUTI, this step does not occur.

Obviously, those skilled in the art should understand that the above multiple modules or steps of the present disclosure may be implemented by a general computing device, which may be concentrated on a single computing device or distributed among multiple computing devices. On the network. In an embodiment, the plurality of modules or steps may be implemented by program code executable by the computing device, such that a plurality of modules or steps may be stored in the storage device by the computing device, and at some In some cases, the steps shown or described may be performed in a different order than that herein, or multiple modules or multiple steps may be separately fabricated into multiple integrated circuit modules, or in multiple modules or multiple steps. Multiple modules or steps are made into a single integrated circuit module. As such, the disclosure is not limited to any specific combination of hardware and software.

The above description is only an embodiment of the present disclosure, and is not intended to limit the present disclosure.

Claims

A method for sending a message, comprising:

Sending a registration request message to the first access and mobility management entity AMF, where the registration request message carries validity information of a globally unique temporary identifier allocated by the second AMF for the terminal, wherein the validity information is used for Determining whether to obtain a non-3rd Generation Partnership Project 3GPP access context to the second AMF.
The method of claim 1, wherein the sending the registration request message to the first access and mobility management entity AMF comprises:

A registration request message is sent to the first AMF by the base station.
The method of claim 2, wherein the sending, by the base station, the registration request message to the first AMF comprises:

Sending a radio resource connection RRC message to the base station, so that the base station forwards the registration request message to the first AMF, where the RRC message carries the registration request message.
The method according to claim 1, 2 or 3, wherein the validity information comprises at least one of: a registration state of the terminal under non-3GPP access and a non-3GPP access being valid; or The information includes at least one of the following: the terminal is in a non-registered state under 3GPP access, the terminal is in a registration state under 3GPP access, the terminal is in a non-registered state under non-3GPP access, and the non-3GPP is connected. Invalid.
The method of claim 4, wherein the validity information is used to determine to acquire the non-3GPP access context to the second AMF if the validity information comprises at least one of: The terminal is in a registration state under non-3GPP access and the non-3GPP access is valid.
The method according to claim 4 or 5, wherein, in the case that the validity information comprises at least one of the following information, the validity information is used to determine not to acquire the non-3GPP connection to the second AMF Context: The terminal is in a non-registered state under 3GPP access, the terminal is in a registration state under 3GPP access, the terminal is in a non-registered state under non-3GPP access, and the non-3GPP access is invalid.
An information acquisition method includes:

Receiving a registration request message, where the registration request message carries validity information of a globally unique temporary identifier assigned by the specified access and mobility management entity AMF to the terminal;

Determining whether to obtain a non-3rd Generation Partnership Project 3GPP access context to the designated AMF based on the validity information.
The method according to claim 7, wherein the validity information comprises at least one of: the registration state of the terminal under the non-3GPP access and the non-3GPP access being valid; or the validity information Including at least one of the following: the terminal is in a non-registered state under 3GPP access, the terminal is in a registration state under 3GPP access, the terminal is in a non-registered state under non-3GPP access, and the non-3GPP access is invalid. .
The method of claim 8, wherein determining whether to obtain the non-3GPP access context from the designated AMF according to the validity information comprises:

Determining, in the case that the validity information includes at least one of the following information, acquiring the non-3GPP access context to the specified AMF: the terminal is in a registration state under non-3GPP access and the non-3GPP access is valid;

If the validity information includes at least one of the following information, determining that the non-3GPP access context is not acquired to the specified AMF: the terminal is in a non-registered state under non-3GPP access, and the terminal is in the In the registration state under 3GPP access, the terminal is in the non-registered state under 3GPP access, and the non-3GPP access is invalid.
A message sending device includes:

a sending module, configured to send a registration request message to the first access and mobility management entity AMF, where the registration request message carries validity information of a globally unique temporary identifier allocated by the second AMF to the terminal, where The validity information is used to determine whether to obtain a non-3rd Generation Partnership Project 3GPP access context to the second AMF.
The apparatus according to claim 10, wherein the validity information comprises at least one of: the terminal is in a registration state under non-3GPP access and the non-3GPP access is valid; or the validity information includes the following: At least one of: the terminal is in a non-registered state under 3GPP access, the terminal is in a registration state under 3GPP access, the terminal is in a non-registered state under non-3GPP access, and the non-3GPP access is invalid;

Wherein, in the case that the validity information includes at least one of the following information, the validity information is used to determine to acquire the non-3GPP access context to the second AMF: the terminal is in a non-3GPP access The registration state and the non-3GPP access are valid; in the case that the validity information includes at least one of the following information, the validity information is used to determine not to acquire the non-3GPP access context to the second AMF: The terminal is in a non-registered state under the 3GPP access, the terminal is in a registration state under the 3GPP access, the non-registered state in which the terminal is in non-3GPP access, and the non-3GPP access is invalid.
An information acquiring device includes:

a receiving module, configured to receive a registration request message, where the registration request message carries validity information of a globally unique temporary identifier assigned by the specified access and mobility management entity AMF to the terminal;

A determining module is configured to determine whether to obtain a non-3rd Generation Partnership Project 3GPP access context to the designated AMF based on the validity information.
The apparatus according to claim 12, wherein the validity information comprises at least one of: a registration state of the terminal under the non-3GPP access and a non-3GPP access being valid; or the validity information Including at least one of the following: the terminal is in a non-registered state under 3GPP access, the terminal is in a registration state under 3GPP access, the terminal is in a non-registered state under non-3GPP access, and the non-3GPP access is invalid. .
The apparatus of claim 13 wherein said determining module is configured to:

Determining, in the case that the validity information includes at least one of the following information, acquiring the non-3GPP access context to the specified AMF: the terminal is in a registration state under non-3GPP access and the non-3GPP access is valid;

If the validity information includes at least one of the following information, determining that the non-3GPP access context is not acquired to the specified AMF: the terminal is in a non-registered state under 3GPP access, and the terminal is in 3GPP The registration state under access, the non-registration state of the terminal under non-3GPP access, and the non-3GPP access are invalid.
A terminal, comprising: a processor, the processor being configured to run a program, wherein the program is executed to execute the message transmitting method according to any one of claims 1 to 6.
An access and mobility management entity includes a processor for running a program, wherein the program is executed to execute the information acquisition method of claim 7, 8 or 9.
A storage medium, the storage medium comprising a stored program, wherein the program is executed to perform the method of any one of claims 1 to 9.
A processor for running a program, wherein the program is executed to perform the method of any one of claims 1 to 9.