WO2019210779A1

WO2019210779A1 - Switching method, device, and system

Info

Publication number: WO2019210779A1
Application number: PCT/CN2019/083340
Authority: WO
Inventors: 宗在峰; 朱奋勤
Original assignee: 华为技术有限公司
Priority date: 2018-05-04
Filing date: 2019-04-19
Publication date: 2019-11-07

Abstract

Embodiments of the present application provide a switching method, device, and system, for enabling a terminal to still be able to switch to a corresponding network slice after switching from a source network to a default mobility management network element in a target network. The method comprises: a target mobility management network element receiving first indication information originating from a source mobility management network element and a context of the terminal, wherein the first indication information is used to indicate that a current registration procedure occurs in a connected state, or the first indication information is used to indicate that the context of the terminal is stored in the source mobility management network element, or the first indication information is used to indicate that it is not required to obtain the context of the terminal according to a global unique temporary identity (GUTI) of the terminal; and the target mobility management network element sending a registration complete notification to the source mobility management network element according to the first indication information after registration is completed, wherein the registration complete notification is used to notify the source mobility management network element that the context of the terminal is no longer valid or that the terminal has registered with the target mobility management network element.

Description

Switching method, device and system

This application claims the priority of the Chinese application filed on May 4, 2018, with the application number 2018104221321.1, the invention name is "Handover Method, Equipment and System", and the application number submitted on February 13, 2019, the application number is 201910121387.9 The priority of the Chinese application entitled "Switching Method, Apparatus, and System" is incorporated herein by reference.

Technical field

The present application relates to the field of communications, and in particular, to a handover method, device, and system.

Background technique

In the prior art, when a terminal switches from a 4th generation (4th generation, 4G) network to a 5th generation (5th generation, 5G) network, a mobility management entity (MME) in the 4G network selects a 5G network. The access and mobility management function (AMF) network element selects the default AMF network element, and does not consider the single network slice selection assistance corresponding to the session of the terminal (single network slice selection assistance) Information, S-NSSAI), therefore, will cause the terminal to be switched to the corresponding network slice when switching from the 4G network to the 5G network, which is not conducive to the isolation of the network slice.

Therefore, how to switch to the corresponding network slice after the terminal switches from the source network to the default mobility management network element in the target network is an urgent problem to be solved.

Summary of the invention

The embodiment of the present application provides a handover method, device, and system, and can still switch to a corresponding network slice after the terminal switches from the source network to the default mobility management network element in the target network.

To achieve the above objective, the embodiment of the present application adopts the following technical solutions:

The first aspect provides a handover method, where the method includes: the target mobility management network element receives first indication information from the source mobility management network element and a context of the terminal, where the first indication information is used to indicate that the current registration process occurs. a connection state; or the first indication information is used to indicate that the context of the terminal is stored in the source mobility management network element; or the first indication information is used to indicate that the global unique temporary identifier GUTI is not required to be obtained according to the terminal a context of the terminal; the target mobility management network element sends a registration completion notification to the source mobility management network element after the registration is completed according to the first indication information, where the registration completion notification is used to notify the source mobility management network element that the context of the terminal is not It is valid again or the terminal has already registered to the target mobility management network element. Based on the solution, after the terminal switches from the source network to the source mobility management network element in the target network, the terminal may be redirected to the target mobility management network element, and the target mobility management network element may be the session of the terminal in the target network. The mobility management network element in the corresponding network slice. Therefore, based on the foregoing solution, after the terminal switches from the source network to the source mobility management network element in the target network, the corresponding network slice can still be switched.

In a possible design, the first indication information includes information of the source mobility management network element.

In a second aspect, a handover method is provided, the method includes: a target mobility management network element receives a registration request of an access device from a terminal and information of a source mobility management network element; and the target mobility management network element according to the source mobility management network Meta-information, sending a context request to the source mobility management network element, the context request is used to request the context of the terminal; the target mobility management network element receives the context of the terminal from the source mobility management network element; the target mobility management network element according to the The information of the source mobility management network element, after the registration is completed, sends a registration completion notification to the source mobility management network element, where the registration completion notification is used to notify the source mobility management network element that the context of the terminal is no longer valid or the terminal has been registered. The target mobile management network element. For the technical effects of the second aspect, reference may be made to the description of the technical effects of the foregoing first aspect, and details are not described herein again.

With reference to the foregoing first aspect or the second aspect, in a possible design, the handover method provided by the embodiment of the present application further includes: the target mobility management network element sends the target mobility management network element to the access device of the terminal as the The next-generation application protocol NGAP terminal identifier and the global mobility management network element identifier GUAMI allocated by the terminal, wherein the NGAP terminal identifier is used to update the NGAP terminal identifier corresponding to the terminal on the access device, and the GUAMI is used to update the access device. The GUAMI corresponding to the terminal. Based on the solution, after the terminal switches to the corresponding network slice, the NGAP terminal identifier and the GUAMI corresponding to the terminal on the access device can be updated in time.

The third aspect provides a handover method, where the method includes: the target mobility management network element receives the first indication information from the source mobility management network element and the context of the terminal, where the first indication information is used to indicate the current handover process. The access device of the terminal does not change; the target mobility management network element sends, according to the first indication information, the next-generation application protocol NGAP terminal identifier and the global mobile management network allocated by the target mobility management network element to the terminal. The NGAP terminal identifier is used to update the NGAP terminal identifier corresponding to the terminal on the access device, and the GUAMI is used to update the GUAMI corresponding to the terminal on the access device. For the technical effects of the third aspect, reference may be made to the description of the technical effects of the foregoing first aspect, and details are not described herein again.

With reference to the foregoing first aspect, the second aspect, or the third aspect, in a possible design, the handover method provided by the embodiment of the present application further includes: the target mobility management network element sends the updated terminal to the access device. Security context, the updated security context of the terminal is used to update the security context of the terminal on the access device. Based on the solution, the security context of the terminal on the access device can be updated in time after the terminal switches to the corresponding network slice.

With reference to the foregoing first aspect or the second aspect or the third aspect, in a possible design, the handover method provided by the embodiment of the present application further includes: the target mobility management network element selects a target intermediate session management network element for the terminal; The mobile management network element sends a session establishment request to the target intermediate session management network element, where the session establishment request carries the second indication information, where the second indication information is used to indicate that the session establishment request is used to switch the session of the terminal, and is in the handover During the process, the access device of the terminal does not change. Based on the solution, the session of the terminal can be switched to the corresponding network slice, and the access device of the terminal does not change during the handover process.

With reference to the above first aspect or the second aspect or the third aspect, in a possible design, the context of the terminal from the source mobility management network element includes the session context of the terminal, wherein the session context of the terminal is the The source mobility management network element is obtained from the source intermediate session management network element, where the session context of the terminal includes the downlink path information of the access device of the terminal and the uplink of the anchor user plane network element corresponding to the session of the terminal. Path information, the uplink path information of the anchor user plane network element is used to establish an uplink path from the target intermediate user plane network element to the anchor user plane function network element, and the downlink path information of the access device is used to establish a slave path The target intermediate user plane network element to the downlink path of the access device; correspondingly, the session establishment request further carries the session context of the terminal. Based on the solution, the target mobility management network element does not need to acquire the session context of the terminal after receiving the session establishment request, but can directly switch the session of the terminal to the corresponding network slice according to the session context carried in the session establishment request.

With reference to the foregoing first aspect, the second aspect, or the third aspect, in a possible design, the handover method provided by the embodiment of the present application further includes: the target mobility management network element determines that the target intermediate session management network element needs to be selected for the terminal. .

In a possible design, the target mobility management network element determines that the target intermediate session management network element needs to be selected for the terminal, including: the target mobility management network element receives the anchor point corresponding to the session of the terminal from the source mobility management network element. Controlling at least one of information of a surface network element or information of a source intermediate session management network element; the target mobility management network element according to at least one of information of the anchor point control plane network element or information of the source intermediate session management network element, It is determined that the target intermediate session management network element needs to be selected for the terminal. Based on the solution, the target mobility management network element can determine that the target intermediate session management network element needs to be selected for the terminal.

In a possible design, the target mobility management network element determines that the target intermediate session management network element needs to be selected for the terminal, including: the target mobility management network element receives third indication information from the source mobility management network element, the third The indication information is used to indicate that the source intermediate session management network element exists; or the third indication information is used to indicate that the intermediate session management network element needs to be reselected for the terminal; the target mobility management network element is configured according to the third indication information. The terminal selects the target intermediate session management network element. Based on the solution, the target mobility management network element can determine that the target intermediate session management network element needs to be selected for the terminal.

A fourth aspect provides a handover method, the method comprising: a source mobility management network element receiving a registration request from a terminal; the source mobility management network element selecting a target mobility management network element for the terminal according to the registration request; source mobility management The network element sends the first indication information and the context of the terminal to the target mobility management network element, where the first indication information is used to indicate that the current registration process occurs in the connected state; or the first indication information is used to indicate that the context of the terminal is stored in the The source mobility management network element; or the first indication information is used to indicate that the context of the terminal is not required to be acquired according to the global unique temporary identifier GUTI of the terminal; the source mobility management network element receives the registration from the target mobility management network element. The completion notification is used to notify the source mobility management network element that the context of the terminal is no longer valid or that the terminal has registered to the target mobility management network element. For the technical effects of the fourth aspect, reference may be made to the description of the technical effects of the foregoing first aspect, and details are not described herein again.

A fifth aspect provides a handover method, the method comprising: a source mobility management network element receiving a registration request from a terminal; the source mobility management network element selecting a target mobility management network element for the terminal according to the registration request; source mobility management The network element sends a re-routing request to the access device of the terminal, where the re-routing request carries the information of the source mobility management network element and the registration request, and the access device sends the registration request to the target mobility management network element and the The source mobile management network element receives the context request sent by the target mobility management network element according to the information of the source mobility management network element, where the context request is used to request the context of the terminal; the source mobility management network element The target mobility management network element sends the context of the terminal; after the registration is completed, the source mobility management network element receives a registration completion notification sent by the target mobility management network element according to the information of the source mobility management network element, and the registration completion notification is used for notification. The source mobile management network element has the context of the terminal no longer valid or the terminal has registered to the target mobile Network element management. For the technical effects of the fifth aspect, reference may be made to the description of the technical effects of the foregoing first aspect, and details are not described herein again.

With reference to the foregoing fourth aspect or the fifth aspect, in a possible design, after the source mobility management network element receives the registration request from the terminal, the method further includes: the source mobility management network element sends the source mobility management network element to the source intermediate session management network element. a session context request for requesting a session context of the terminal; the source mobility management network element receiving a session context of the terminal from the source intermediate session management network element; correspondingly, the context of the terminal includes the terminal a session context, where the session context of the terminal includes the downlink path information of the access device of the terminal and the uplink path information of the anchor user plane network element corresponding to the session of the terminal, and the uplink path of the anchor user plane network element The information is used to establish an uplink path from the target intermediate user plane network element to the anchor user plane function network element, and the downlink path information of the access device is used to establish a downlink from the target intermediate user plane network element to the access device. path. Based on the solution, the target mobility management network element does not need to acquire the session context of the terminal after receiving the session establishment request, but can directly switch the session of the terminal to the corresponding network according to the session context of the terminal carried in the session establishment request. slice.

In a sixth aspect, a handover method is provided, the method includes: a target intermediate session management network element receives a session establishment request from a target mobility management network element, where the session establishment request carries second indication information, where the second indication information is used Instructing the session establishment request to switch the session of the terminal, and the access device of the terminal does not change during the handover process; the target intermediate session management network element is configured from the source intermediate session management network element according to the second indication information. Obtaining a session context of the terminal, where the session context of the terminal includes downlink path information of the access device of the terminal, and uplink path information of the anchor user plane network element corresponding to the session of the terminal, where the anchor user network The uplink path information of the element is used to establish an uplink path from the target intermediate user plane network element to the anchor user plane function network element, and the downlink path information of the access device is used to establish the target intermediate user plane network element to the The downstream path of the access device. Based on the scheme, the target mobility management network element can switch the session of the terminal to the corresponding network slice according to the session context of the terminal.

In a possible design, the target intermediate session management network element obtains the session context of the terminal from the source intermediate session management network element according to the second indication information, including: the target intermediate session management network element according to the second indication information Sending a session context request to the source intermediate session management network element, where the session context request carries fourth indication information, which is used to request a session context of the terminal including the downlink path information of the access device; and the target intermediate session management network element receives The session context of the terminal from the source intermediate session management network element. Based on the solution, the target intermediate session management network element can obtain the session context of the terminal from the source intermediate session management network element.

In a possible design, the method further includes: the target intermediate session management network element sends the uplink path information of the target intermediate user plane network element to the access device, where the uplink path information of the target intermediate user plane network element is used. Establishing an uplink path from the access device to the target intermediate user plane network element. Based on the solution, an uplink path from the access device to the target intermediate user plane network element can be established.

In a seventh aspect, a target mobility management network element is provided, the target mobility management network element having the function of implementing the method of any of the first aspect or the second aspect or the third aspect or the twenty-eighth aspect. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In an eighth aspect, a target mobility management network element is provided, including: a processor and a memory; the memory is configured to store a computer execution instruction, and when the target mobility management network element is running, the processor executes the computer stored by the memory The instruction is executed to cause the target mobility management network element to perform the handover method as described in the first aspect or the second aspect or the third aspect or the twenty-eighth aspect.

A ninth aspect provides a target mobility management network element, including: a processor; the processor is configured to be coupled to a memory, and after reading an instruction in the memory, perform the first aspect or the second according to the instruction according to the instruction The switching method of any of the third aspect or the twenty-eighth aspect.

According to a tenth aspect, there is provided a computer readable storage medium having stored therein instructions that, when executed on a computer, cause the computer to perform the first aspect or the second aspect or the third aspect or The handover method of any of the twenty-eighth aspects.

In an eleventh aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform any of the first or second aspect or the third aspect or the twenty-eighth aspect The switching method described.

A twelfth aspect, a chip system is provided, the chip system comprising a processor for supporting a target mobility management network element to implement the first aspect or the second aspect or the third aspect or the twenty-eighth aspect Functions, such as assigning NGAP terminal IDs and GUAMIs to terminals. In one possible design, the chip system further includes a memory for storing program instructions and data necessary for the target mobility management network element. The chip system can be composed of chips, and can also include chips and other discrete devices.

The technical effects brought by any one of the seventh aspect to the twelfth aspect can be referred to the technology brought by the first aspect or the second aspect or the third aspect or the twenty-eighth aspect. The effect will not be described here.

In a thirteenth aspect, a source mobility management network element is provided, the source mobility management network element having the function of implementing the method of any of the fourth or fifth aspect. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In a fourteenth aspect, a source mobility management network element is provided, including: a processor and a memory; the memory is configured to store a computer execution instruction, and when the source mobility management network element is running, the processor executes the memory storage The computer executes the instructions to cause the source mobility management network element to perform the handover method of any of the above fourth or fifth aspect.

In a fifteenth aspect, a source mobility management network element is provided, including: a processor; the processor is configured to be coupled to a memory, and after reading an instruction in the memory, perform the fourth aspect or the foregoing according to the instruction The handover method of any of the five aspects.

A sixteenth aspect, a computer readable storage medium having instructions stored therein that, when run on a computer, cause the computer to perform any of the fourth aspect or the fifth aspect described above The switching method described.

In a seventeenth aspect, a computer program product comprising instructions for causing a computer to perform the switching method of any of the above fourth or fifth aspects when executed on a computer.

According to an eighteenth aspect, a chip system is provided, the chip system comprising a processor, configured to support a source mobility management network element to implement the functions involved in the fourth aspect or the fifth aspect, for example, selecting a terminal according to a registration request Target mobility management network element. In one possible design, the chip system further includes a memory for storing necessary program instructions and data necessary for the source mobility management network element. The chip system can be composed of chips, and can also include chips and other discrete devices.

For the technical effects brought by any one of the thirteenth to the eighteenth aspects, refer to the technical effects brought by the different design modes in the fourth aspect or the fifth aspect, and details are not described herein again.

In a nineteenth aspect, a target intermediate session management network element is provided, the target intermediate session management network element having the function of implementing the method of any of the sixth aspects. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

According to a twentieth aspect, a target intermediate session management network element includes: a processor and a memory; the memory is configured to store a computer execution instruction, and when the target intermediate session management network element is running, the processor executes the memory storage The computer executes instructions to cause the target intermediate session management network element to perform the handover method of any of the sixth aspects described above.

The twenty-first aspect provides a target intermediate session management network element, including: a processor; the processor is configured to be coupled with a memory, and after reading an instruction in the memory, execute the sixth aspect according to the instruction according to the instruction The switching method described in any one of the preceding claims.

A twenty-second aspect, a computer readable storage medium having stored therein instructions that, when run on a computer, cause the computer to perform the method of any of the sixth aspects above Switch method.

In a twenty-third aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the switching method of any of the above sixth aspects.

A twenty-fourth aspect, a chip system is provided, the chip system comprising a processor, configured to support a target intermediate session management network element to implement the functions involved in the sixth aspect, for example, according to the second indication information, from the middle of the source The session management network element obtains the session context of the terminal. In one possible design, the chip system further includes a memory for storing necessary program instructions and data necessary for the target intermediate session management network element. The chip system can be composed of chips, and can also include chips and other discrete devices.

For the technical effects brought by any one of the nineteenth to twenty-fourth aspects, refer to the technical effects brought by different design modes in the sixth aspect, and details are not described herein again.

A twenty-fifth aspect, a switching system comprising the target mobility management network element capable of performing the handover method according to the above first aspect, according to any one of the seventh to twelfth aspects, And the source mobility management network element that can perform the handover method of the above fourth aspect, according to any one of the thirteenth to eighteenth aspects.

According to a twenty-sixth aspect, there is provided a handover system, comprising: the target mobility management network element capable of performing the handover method according to the second aspect, according to any one of the seventh to twelfth aspects And the source mobility management network element that can perform the handover method of the above fifth aspect, according to any one of the thirteenth to eighteenth aspects.

According to a twenty-seventh aspect, a switching system is provided, the switching system comprising a source mobility management network element, and the handover according to any one of the seventh to twelfth aspects, The target mobility management network element of the method, wherein the source mobility management network element is configured to select a target mobility management network element for the terminal, and send the first indication information and the context of the terminal to the target mobility management network element.

In conjunction with the twenty-fifth aspect, the twenty-sixth aspect, or the twenty-seventh aspect, in a possible design, the switching system further includes the any one of the nineteenth aspect to the twenty-fourth aspect Target intermediate session management network element.

The twenty-eighth aspect provides a handover method, including: the target mobility management network element receives first indication information from the source mobility management network element and a context of the terminal, where the first indication information is used to indicate the target mobility management network element The registration completion notification is not sent in the subsequent process; the target mobility management network element determines not to send the registration completion notification according to the first indication information. Based on the solution, after the terminal switches from the source network to the source mobility management network element in the target network, the terminal may be redirected to the target mobility management network element, and the target mobility management network element may be the session of the terminal in the target network. The mobility management network element in the corresponding network slice. Therefore, based on the foregoing solution, after the terminal switches from the source network to the source mobility management network element in the target network, the corresponding network slice can still be switched.

These and other aspects of the present application will be more readily apparent from the following description of the embodiments.

DRAWINGS

FIG. 1 is a schematic diagram of an existing 4G network and 5G network interworking architecture;

2 is a schematic structural diagram of a handover system according to an embodiment of the present application;

FIG. 3 is a schematic diagram of application of a handover system in a 5G network according to an embodiment of the present application;

FIG. 4 is a schematic structural diagram of hardware of a communication device according to an embodiment of the present disclosure;

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

FIG. 6 is a schematic flowchart 2 of a handover method according to an embodiment of the present disclosure;

FIG. 7 is a schematic flowchart 3 of a handover method according to an embodiment of the present disclosure;

FIG. 8 is a schematic structural diagram of a target mobility management network element according to an embodiment of the present application;

FIG. 9 is a schematic structural diagram of a source mobility management network element according to an embodiment of the present disclosure;

FIG. 10 is a schematic structural diagram of a target intermediate session management network element according to an embodiment of the present disclosure.

detailed description

In order to facilitate the understanding of the technical solutions of the embodiments of the present application, a brief introduction of the related art of the present application is first given as follows.

Network slice:

A network slice is a network that is used to support specific network capabilities and network characteristics. It can be end-to-end (E2E), including the entire network, or multiple networks can share multiple network functions. It is a key technology to meet the network differentiation requirements of 5G mobile communication technology proposed by the 3rd generation partnership project (3GPP). Generally, network characteristics of different network slices are not the same, and network slices are required to be isolated from each other without affecting each other. For example, network slicing of augmented reality (AR) or virtual reality (VR) services requires large bandwidth and low latency; network segmentation of Internet of Things (IOT) services requires massive terminal access. However, the bandwidth is small and there is no requirement for delay.

Network slice selection assistance information (NSSAI):

NSSAI includes multiple S-NSSAIs. S-NSSAI consists of a service type (slice/service type, SST) and a slice differentiator (SD). Among them, SST includes standardization and operator-defined types; SD is optional information supplementing SST to distinguish multiple network slices of the same SST. The types and effects of NSSAI defined in the 23.501 standard are shown in Table 1.

Table I

4G network and 5G network interworking architecture:

As shown in FIG. 1, it is a schematic diagram of an existing 4G network and 5G network interworking architecture. The user plane function (UPF) network element and the packet data network (PDN) user plane function (PGW-U) network element and session are shared between the 4G network and the 5G network. Management function (SMF) network element + PDN gateway control plane function (PGW-C) network element, policy control function (PCF) network element + policy and charging rule function (policy and charging rules function, PCRF) network element, home subscriber server (HSS) + unified data management (UDM) network element. Here, "+" means the setting, UPF is the user plane function of the 5G network, PGW-U is the gateway user plane function of the 4G network corresponding to the UPF, SMF is the session management function of the 5G network, and PGW-C is the corresponding to the SMF. The gateway control plane function in the 4G network, the PCF is the policy control function of the 5G network, and the PCRF is the policy charging rule function of the 4G network corresponding to the PCF. In the embodiment of the present application, for convenience of description, the UDM network element + HSS is referred to as a user data management network element, and the SMF network element + PGW-C network element is referred to as an anchor control plane network element, and the UPF network element is + The PGW-U network element is called an anchor user plane network element, and is uniformly described here, and will not be described below. Certainly, the network device after the above-mentioned connection may also use other names, which is not specifically limited in this embodiment of the present application.

In addition, as shown in FIG. 1 , the above-mentioned 4G network and 5G network interworking architecture may further include an MME and a Serving Gateway (SGW) in the 4G network, and an AMF network element in the 5G network. Optionally, the 4G network and the 5G network interworking architecture may further include a network slice selection function (NSSF) network element. The AMF network element may request the NSSF network element to select a network slice for the terminal, which is not specifically limited in this embodiment.

The terminal accesses the 4G network through an evolved universal terrestrial radio access network (E-UTRAN) device, and the terminal passes the next generation radio access network (NG-RAN) device. Access to 5G networks. The E-UTRAN device communicates with the MME through the S1-MME interface, the E-UTRAN device communicates with the SGW through the S1-U interface, the MME communicates with the SGW through the S11 interface, and the MME communicates with the user data management network element through the S6a interface, and the MME passes the N26 interface. Communicate with the AMF network element, the SGW communicates with the UPF network element + PGW-U network element through the S5-U interface, and the SGW communicates with the SMF network element + PGW-C network element through the S5-C interface, and the UPF network element + PGW-U passes The N3 interface communicates with the NG-RAN device, and the UPF network element + PGW-U network element communicates with the SMF network element + PGW-C network element through the N4 interface, and the SMF network element + PGW-C network element passes the N7 interface and the PCF network element + The PCRF network element communication, the UDM network element + HSS communicates with the SMF network element + PGW-C network element through the N10 interface, the UDM network element + HSS communicates with the AMF network element through the N8 interface, and the PCF network element + PCRF network element passes the N15 interface and AMF network element communication, SMF network element + PGW-C network element communicates with AMF network element through N11 interface, AMF network element communicates with NG-RAN device through N2 interface, and AMF network element communicates with terminal through N1 interface.

It should be noted that the name of the interface between the network elements in FIG. 1 is only an example. In the specific implementation, the interface name may be other names, which is not specifically limited in this embodiment of the present application.

It should be noted that the NG-RAN device in the 5G network may also be referred to as an access device, and the access device refers to a device that accesses the core network, for example, a base station, a broadband network service gateway (broadband network gateway, BNG), aggregation switch, non-3GPP access equipment, etc. The base station may include various types of base stations, such as a macro base station, a micro base station (also referred to as a small station), a relay station, an access point, and the like, which are not specifically limited in this embodiment of the present application.

Of course, there may be other network elements in the 4G network and the 5G network. For example, the 4G network may also include a general packet radio system (GPRS) service support node (SGSN), etc., 5G. The network may also include an authentication service function (AUSF) network element, etc., which is not specifically limited in this embodiment of the present application.

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. In the description of the present application, "a plurality" means two or more than two unless otherwise stated; "A/B" means A or B. In addition, in order to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first", "second", and the like are used to distinguish the same items or similar items whose functions and functions are substantially the same. Those skilled in the art can understand that the words "first", "second" and the like do not limit the number and execution order, and the words "first", "second" and the like are not necessarily limited.

The network architecture and the service scenario described in the embodiments of the present application are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation of the technical solutions provided by the embodiments of the present application. The technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

As shown in FIG. 2, a handover system 20 is provided in the embodiment of the present application. The handover system 20 includes a source mobility management network element 201 and a target mobility management network element 202.

In a possible implementation manner, the source mobility management network element 201 is configured to receive a registration request from the terminal, and after selecting the target mobility management network element 202 for the terminal according to the registration request, send the target mobility management network element 202 to the target mobility management network element 202. The first indication information and the context of the terminal. The first indication information is used to indicate that the current registration process occurs in the connected state; or the first indication information is used to indicate that the context of the terminal is stored in the source mobility management network element 201; or the first indication information is used for It indicates that the context of the terminal does not need to be obtained according to the global unique temporary identity (GUTI) of the terminal.

The target mobility management network element 202 is configured to receive the first indication information from the source mobility management network element 201 and the context of the terminal, and send the registration completion to the source mobility management network element 201 after the registration is completed according to the first indication information. The notification is used to notify the source mobility management network element 201 that the context of the terminal is no longer valid or that the terminal has registered to the target mobility management network element 202.

In another possible implementation manner, the source mobility management network element 201 is configured to receive a registration request from the terminal, and select a target mobility management network element 202 for the terminal according to the registration request, and send the weight to the access device of the terminal. A routing request, the rerouting request carrying information of the source mobility management network element 201 and the registration request.

The target mobility management network element 202 is configured to receive the registration request from the access device and the information of the source mobility management network element, and send a context request to the source mobility management network element 201 according to the information of the source mobility management network element 201, the context. The request is used to request the context of the terminal.

The source mobility management network element 201 is configured to receive a context request from the target mobility management network element 202, and send the context of the terminal to the target mobility management network element 202 according to the context request.

The target mobility management network element 202 is configured to receive the context of the terminal from the source mobility management network element 201, and send a registration completion notification to the source mobility management network element 201 after the registration is completed according to the information of the source mobility management network element 201. The registration completion notification is used to notify the source mobility management network element 201 that the context of the terminal is no longer valid or that the terminal has registered to the target mobility management network element 202.

In another possible implementation manner, the source mobility management network element 201 is configured to select a target mobility management network element 202 for the terminal, and send the first indication information and the context of the terminal to the target mobility management network element 202, where the first indication is The information is used to indicate that the access device of the terminal does not change in the current handover process.

The target mobility management network element 202 is configured to receive the first indication information from the source mobility management network element 201 and the context of the terminal, and send the target mobility management network element 202 to the terminal according to the first indication information. A next generation application protocol (NGAP) terminal identifier and a globally unique AMF identifier (GUAMI), wherein the NGAP terminal identifier is used to update the NGAP terminal identifier corresponding to the terminal on the access device, and the GUAMI is used. Update the GUAMI corresponding to the terminal on the access device.

In another possible implementation, the source mobility management network element 201 is configured to select a target mobility management network element 202 for the terminal, and send the first indication information and the context of the terminal to the target mobility management network element 202, the first indication. The information is used to indicate that the target mobility management network element does not send the registration completion notification in the subsequent process (for example, the registration completion notification is not sent to the source mobility management network element 201, and the registration completion notification is not sent to the MME); the target mobility management network element 202 And receiving the first indication information from the source mobility management network element 201 and the context of the terminal, and determining, according to the first indication information, that the registration completion notification is not sent.

Optionally, the source mobility management network element 201 in the embodiment of the present application may also be referred to as a default mobility management network element, which is not specifically limited in this embodiment of the present application.

Optionally, the source mobility management network element 201 and the target mobility management network element 202 in the embodiment of the present application are generally located in different network slices, which are uniformly described herein, and are not described herein again.

Optionally, the source mobility management network element 201 and the target mobility management network element 202 in the embodiment of the present application may directly communicate with each other, and may also perform communication by forwarding of other devices, which is not specifically limited in this embodiment of the present application.

In the above switching system provided by the embodiment of the present application, after the terminal switches from the source network to the default mobility management network element in the target network, the terminal may be redirected to the target mobility management network element, and the target mobility management network element may The mobility management network element in the network slice corresponding to the session of the terminal in the target network. Therefore, after the terminal switches from the source network to the default mobility management network element in the target network, the terminal can still switch to the corresponding Network slicing.

Optionally, as shown in FIG. 2, the switching system 20 provided by the embodiment of the present application may further include a target intermediate session management network element 204 and a source intermediate session management network element 205.

The target mobility management network element 202 is configured to select a target intermediate session management network element 204 for the terminal, and send a session establishment request to the target intermediate session management network element 204. The session establishment request carries the second indication information, where the second indication information is used to indicate that the session establishment request is used to switch the session of the terminal, and the access device of the terminal does not change during the handover process.

The target intermediate session management network element 204 is configured to receive a session establishment request from the target mobility management network element 202, and obtain a session context of the terminal from the source intermediate session management network element 205 according to the second indication information, where the terminal The session context includes the downlink path information of the access device of the terminal and the uplink path information of the anchor user plane network element corresponding to the session of the terminal, and the uplink path information of the anchor user plane network element is used to establish the target intermediate user plane network. The downlink path of the access device is configured to establish a downlink path from the target intermediate user plane network element to the access device.

Optionally, the source intermediate session management network element in the embodiment of the present application may also be referred to as a default intermediate session management network element, which is not specifically limited in this embodiment of the present application.

Optionally, the source intermediate session management network element 205 and the source mobility management network element 201 in the embodiment of the present application are generally located in the same network slice, and are not described herein.

Optionally, the target intermediate session management network element 204 and the target mobility management network element 202 in the embodiment of the present application are generally located in the same network slice, and are collectively described herein, and are not further described below.

Optionally, the target mobility management network element 202 and the target intermediate session management network element 204 in the embodiment of the present application may directly communicate with each other, and may also perform communication by forwarding of other devices, which is not specifically limited in this embodiment of the present application.

Optionally, the target intermediate session management network element 204 and the source intermediate session management network element 205 in the embodiment of the present application may directly communicate with each other, and may also perform communication by forwarding of other devices, which is not specifically limited in this embodiment of the present application. .

In the above switching system provided by the embodiment of the present application, after the terminal switches from the source network to the default intermediate session management network element in the target network, the terminal may be redirected to the target intermediate session management network element, and the target intermediate session management is performed. The network element may be a session management network element in the network slice corresponding to the session of the terminal in the target network. Therefore, based on the foregoing solution, after the terminal switches from the source network to the default intermediate session management network element in the target network, the network element may still be Switch to the appropriate network slice.

Optionally, the switching system 20 shown in FIG. 2 can be applied to the 5G network and other networks in the future, which is not specifically limited in this embodiment of the present invention.

Illustratively, if the switching system 20 shown in FIG. 2 can be applied to the current 5G network, as shown in FIG. 3, the network element or entity corresponding to the source mobility management network element may be the source AMF in the 5G network. The network element or the entity corresponding to the target mobility management network element may be the target AMF network element in the 5G network; the network element or entity corresponding to the source intermediate session management network element may be the source in the 5G network. The intermediate SMF (intermediate SMF) network element; the network element or entity corresponding to the target intermediate session management network element may be a target I-SMF network element in the 5G network.

In addition, as shown in FIG. 3, the 5G network may further include an access device, an intermediate intermediate UPF (I-UPF) network element, or a source I-UPF network element, which is not specifically limited in this embodiment. .

Although not shown, the 5G network may further include a policy control function (PCF) network element or an authentication server function (AUSF) network element, which is not specifically limited in this embodiment of the present application.

As shown in FIG. 3, in the embodiment of the present application, the terminal accesses the 5G core network through the access device, and the terminal passes through the Next Generation (N)1 interface (N1 for short) and the source AMF network element and the target respectively. AMF network element communication, the access device communicates with the source AMF network element and the target AMF network element through the N2 interface (N2 for short), and the access device communicates with the source I-UPF network element and the target I- through the N3 interface (N3 for short). In the UPF network element communication, the source AMF network element communicates with the source I-SMF network element through the N11 interface (N11 for short), and the source I-SMF network element communicates with the source I-UPF network element through the N4 interface (referred to as N4); the target AMF network The element communicates with the target I-SMF network element through N11, and the target I-SMF network element communicates with the target I-UPF network element through N4. In addition, the source AMF network element communicates with the target AMF network element through the N14 interface (N14 for short), and the source I-SMF network element communicates with the target I-SMF network element through the N16* interface (referred to as N16*), and the source I-UPF network element Communicate with the target I-SMF network element through the N9 interface (N9 for short).

It should be noted that the name of the interface between the network elements in FIG. 3 is only an example. In the specific implementation, the interface name may be other names, which is not specifically limited in this embodiment of the present application.

It should be noted that the terminal, the access device, the source AMF network element, the target AMF network element, the source I-SMF network element, the target I-SMF network element, the source I-UPF network element or the target I-UPF in FIG. The network element and so on are only one name, and the name does not limit the device itself. In the 5G network and other future networks, the terminal, the access device, the source AMF network element, the target AMF network element, the source I-SMF network element, the target I-SMF network element, the source I-UPF network element or the target I- The network element or entity corresponding to the UPF network element may also be other names, which is not specifically limited in this embodiment of the present application. For example, the source AMF network element may be replaced with a default AMF network element, and the source I-UPF network element may be replaced with a source I-UPF or a source I-UPF entity, etc. No longer.

Optionally, the terminal involved in the embodiment of the present application may include various handheld devices having wireless communication functions, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to the wireless modem; Including user unit (subscriber unit), cellular phone, smart phone, wireless data card, personal digital assistant (PDA) computer, tablet computer, wireless modem (modem), handheld device Handheld, laptop computer, cordless phone or wireless local loop (WLL) station, machine type communication (MTC) terminal, user equipment (user equipment) , UE), mobile station (MS), terminal device or relay user equipment. The relay user equipment may be, for example, a 5G residential gateway (RG). For convenience of description, in the present application, the above mentioned devices are collectively referred to as terminals.

Optionally, the access device involved in the embodiment of the present application refers to a device that accesses the core network, and may be, for example, a base station, a broadband network gateway (BNG), an aggregation switch, and a non-third-generation cooperation. 3rd generation partnership project (3GPP) access equipment, etc. The base station may include various forms of base stations, such as macro base stations, micro base stations (also referred to as small stations), relay stations, access points, and the like.

Optionally, the source mobility management network element, the target mobility management network element, the source intermediate session management network element, or the target intermediate session management network element in FIG. 2 of the embodiment of the present application may be implemented by one device, or may be shared by multiple devices. The implementation may be a function module in a device, which is not specifically limited in this embodiment. It can be understood that the above functions can be either a network component in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform).

For example, the source mobility management network element, the target mobility management network element, the source intermediate session management network element, or the target intermediate session management network element in FIG. 2 of the embodiment of the present application may be implemented by using the communication device in FIG. 4. FIG. 4 is a schematic structural diagram of hardware of a communication device according to an embodiment of the present application. The communication device 400 includes at least one processor 401, a communication line 402, a memory 403, and at least one communication interface 404.

The processor 401 can be a general central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more for controlling the execution of the program of the present application. integrated circuit.

Communication line 402 can include a path for communicating information between the components described above.

Communication interface 404, using any type of transceiver, for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .

The memory 403 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions. The dynamic storage device can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this. The memory may be stand-alone and connected to the processor via communication line 402. The memory can also be integrated with the processor.

The memory 403 is used to store computer execution instructions for executing the solution of the present application, and is controlled by the processor 401 for execution. The processor 401 is configured to execute computer execution instructions stored in the memory 403 to implement the switching method provided by the following embodiments of the present application.

Optionally, the computer-executed instructions in the embodiment of the present application may also be referred to as an application code, which is not specifically limited in this embodiment of the present application.

In a specific implementation, as an embodiment, the processor 401 may include one or more CPUs, such as CPU0 and CPU1 in FIG.

In a particular implementation, as an embodiment, communication device 400 can include multiple processors, such as processor 401 and processor 408 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.

In a particular implementation, as an embodiment, the communication device 400 can also include an output device 405 and an input device 406. Output device 405 is in communication with processor 401 and can display information in a variety of ways. For example, the output device 405 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait. Input device 406 is in communication with processor 401 and can receive user input in a variety of ways. For example, input device 406 can be a mouse, keyboard, touch screen device, or sensing device, and the like.

The communication device 400 described above may be a general purpose device or a dedicated device. In a specific implementation, the communication device 400 can be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, or the like in FIG. device. The embodiment of the present application does not limit the type of the communication device 400.

The switching method provided by the embodiment of the present application will be specifically described below with reference to FIG. 1 to FIG.

It should be noted that the name of the message or the name of each parameter in the message in the following embodiments of the present application is only an example, and may be other names in the specific implementation. limited.

The switching system shown in FIG. 2 is applied to the 5G network shown in FIG. 3 as an example. As shown in FIG. 5, the switching method provided by the embodiment of the present application includes the following steps:

S501: The source AMF network element obtains the S-NSSAI corresponding to the session of the terminal from the SMF network element + the PGW-C network element in the process of the terminal switching from the 4G network to the 5G network.

The specific implementation of the step S501 can refer to the existing implementation manner, and details are not described herein again.

At this point, as shown in Figure 5, the corresponding data transmission path is:

Terminal <-> access device <-> source I-UPF network element <-> UPF network element + PGW-U network element.

S502. After the terminal switches to the source AMF network element, the terminal sends a registration request 1 to the source AMF network element, so that the source AMF network element receives the registration request 1 from the terminal.

Optionally, the registration request 1 in the embodiment of the present application may carry the NSSAI requested by the terminal, which is not specifically limited in this embodiment of the present application.

S503. The source AMF network element selects a target AMF network element for the terminal according to the registration request 1.

Optionally, in the embodiment of the present application, after obtaining the registration request 1, the source AMF network element may select the target AMF network element for the terminal according to the NSSAI requested by the terminal. The NSSAI requested by the terminal may be the NSSAI requested by the terminal carried in the registration request 1 in step S502, or may be generated by the source AMF network element according to the S-NSSAI corresponding to the established session of the terminal obtained in step S501. The NSSAI requested by the terminal may also be a set of NSSAIs requested by the terminal that is requested by the terminal carried in the registration request 1 and the NSFAI generated by the source AMF network element according to the S-NSSAI corresponding to the session of the terminal obtained in step S501. The embodiment of the present application does not specifically limit this.

Optionally, the source AMF network element selects the target AMF network element for the terminal according to the NSSAI requested by the terminal, and the method includes: the source AMF network element acquires the NSSAI signed by the terminal from the UDM network element, and the NSSAI signed by the terminal and the NSSAI requested by the terminal. Sending to the NSSF network element, requesting the NSSF network element to select the target AMF network element for the terminal; further, the NSSF network element may select the target AMF network element or the target AMF network element set for the terminal according to the NSSAI subscribed by the terminal and the NSSAI requested by the terminal. And transmitting information of the target AMF network element or the set of the target AMF network element to the source AMF network element. If the source AMF network element receives the information of the set of the target AMF network element, the source AMF network element may select the target AMF network element from the set of the target AMF network element according to the information of the set of the target AMF network element. .

The above is merely an exemplary implementation of providing a source AMF network element to select a target AMF network element for the terminal according to the NSSAI requested by the terminal. Of course, the source AMF network element may select a target AMF network element for the terminal according to the NSSAI requested by the terminal, and may also refer to the existing implementation manner, and details are not described herein again.

Optionally, in the embodiment of the present application, the source AMF network element may also verify the registration request 1 to ensure that the registration request 1 is from the terminal and has not been tampered with. The specific implementation may refer to the existing implementation manner, and Let me repeat.

S504. The source AMF network element sends an N14 message to the target AMF network element, so that the target AMF network element receives the N14 message from the source AMF network element, where the N14 message carries the registration request 1, the first indication information, and the context of the terminal. .

The first indication information is used to indicate that the current registration process occurs in the connected state, so that the target AMF network element does not need to obtain the context of the terminal from the MME of the 4G network according to the GUTI of the terminal; or the first indication information. The context indicating that the terminal is stored in the source AMF network element, so that the target AMF network element does not need to obtain the context of the terminal from the MME of the 4G network according to the GUTI of the terminal; or the first indication information is used to indicate The context of the terminal is not required to be obtained from the MME of the 4G network according to the GUTI of the terminal; or the first indication information is used to indicate that the target AMF network element does not need to send the registration completion notification in the subsequent process.

Optionally, the foregoing first indication information may be explicit indication information, such as using a separate bit or field. The first indication information may also be implicit indication information, for example, the first indication information may include a source. The information of the AMF network element, the information of the source AMF network element may be used as an implicit indication, which is not specifically limited in this embodiment of the present application.

Optionally, in the embodiment of the present application, the information of the source AMF network element may include, for example, service address information corresponding to the source AMF network element, such as a universal resource identifier (URI) corresponding to the source AMF network element, or a source AMF. The internet protocol (IP) address of the network element, or the fully qualified domain name (FQDN) of the source AMF network element, or the identifier of the source AMF network element, or other information that can be used to identify the source AMF, The target AMF network element is caused to find the source AMF network element according to the information of the source AMF and send a corresponding message to the source AMF network element.

Optionally, in the embodiment of the present application, the context of the terminal may include: a permanent identifier of the terminal, a capability of the terminal, a temporary identifier of the terminal, or terminal location information, and the like, and a context related to access and mobility management. Optionally, the context of the terminal may further include: a session identifier corresponding to the session that the terminal has established, and information about the SMF network element corresponding to the session that the terminal has established (such as information of the source I-SMF network element or SMF network element + PGW) - at least one of the information of the C network element or the session context of the terminal such as the S-NSSAI corresponding to the session that the terminal has established. Optionally, the context of the terminal may further include: the transport layer information of the access device or the information used by the access device to identify the terminal on the N2 interface (that is, the NGAP terminal identifier allocated by the access device for the terminal), This embodiment of the present application does not specifically limit this.

Optionally, in the embodiment of the present application, the information of the source I-SMF network element may include, for example, service address information corresponding to the source I-SMF network element, such as a URI corresponding to the source I-SMF network element, or a source I-SMF network. The IP address of the element, or the FQDN of the source I-SMF network element, or the identity of the source I-SMF network element, or other information that can be used to identify the source I-SMF, so that other network elements are based on the source I-SMF network. The meta-information can find the source I-SMF network element and send a corresponding message to the source I-SMF network element.

Optionally, in the embodiment of the present application, the information of the source I-SMF network element may further include the service area information of the source I-SMF network element, which is not specifically limited in this embodiment of the present application.

Optionally, in the embodiment of the present application, the information about the SMF network element and the PGW-C network element may include the service address information corresponding to the SMF network element and the PGW-C network element, such as the SMF network element and the PGW-C network element. URI, or the IP address of the SMF network element + PGW-C network element, or the FQDN of the SMF network element + PGW-C network element, or the identifier of the SMF network element + PGW-C network element, or other may be used to identify the SMF network The information of the element + PGW-C network element, so that other network elements can find the SMF network element + PGW-C network element according to the information of the SMF network element + PGW-C network element and send a corresponding message to the SMF network. Yuan + PGW-C network element.

Optionally, in the embodiment of the present application, the information about the SMF network element and the PGW-C network element may further include the service area information of the SMF network element + the PGW-C network element and the publicity of the SMF network element + the PGW-C network element. At least one of the PLMN identifiers (IDs) of the public land mobile network (PLMN) is not specifically limited in this embodiment of the present application.

Optionally, the N14 message in the embodiment of the present application may further carry the information of the source AMF network element, and the related description of the information of the source AMF network element may be referred to the foregoing description, and details are not described herein again.

S505. The target AMF network element initiates the rest of the registration process.

For example, the target AMF network element can determine whether to authenticate the terminal, determine a new registration area (RA), reassign the GUTI, or obtain terminal subscription data from the UDM network element, as needed, and the specific implementation can refer to the existing implementation. The method will not be repeated here.

Optionally, after the registration is completed, the handover method provided by the embodiment of the present application may further include the following steps:

S506. Optionally, the target AMF network element sends a registration completion notification to the source AMF network element, so that the source AMF network element receives the registration completion notification from the target AMF network element.

The registration completion notification is used to notify the source AMF network element that the context of the terminal in the source AMF network element is no longer valid or the terminal has already registered to the target AMF network element, so that the source AMF network element can complete the notification according to the registration. Set the context of the terminal to be inactive.

Optionally, the registration completion notification may be used to notify the source AMF network element to delete the context of the terminal in the source AMF network element, so that the source AMF network element may delete the context of the terminal according to the registration completion notification. This is not specifically limited.

Optionally, in the embodiment of the present application, the source AMF network element may also set the context of the terminal to be inactive or delete the context of the terminal after sending the context of the terminal to the target AMF network element for a period of time. For example, a timer is set, and after the timer expires, the context of the terminal is set to be inactive or the context of the terminal is deleted, which is not specifically limited in this embodiment of the present application.

Optionally, if the first indication information in the step S504 is used to indicate that the target AMF network element does not need to send the registration completion notification in the subsequent process, the target AMF network element may determine, according to the first indication information, that the registration completion notification is not sent. That is, the step S506 is not performed. Optionally, the source AMF network element may set a timer, and after the timer expires, the context of the terminal is set to be inactive or the context of the terminal is deleted, which is not specifically limited in this embodiment of the present application.

Optionally, after the step S505, if the session switching is not required, the handover method provided by the embodiment of the present application may further include the following steps S507-S509:

S507. The target AMF network element sends an N2 message 1 to the access device, so that the access device receives the N2 message 1 from the target AMF network element.

The N2 message 1 carries a registration response, an NGAP terminal identifier and a GUAMI allocated by the target AMF network element to the terminal.

Optionally, the registration response in the embodiment of the present application may carry the GUTI allocated by the target AMF network element to the terminal, where the GUTI is allocated by the target AMF network element to the terminal and the target AMF network element is allocated to the terminal. Logo composition.

Optionally, the registration response may also carry the allowed NSSAI, which is not specifically limited in this embodiment of the present application.

Optionally, in the embodiment of the present application, the GUAMI allocated by the target AMF network element to the terminal may be identified by a public land mobile network (PLMN) identifier (ID) and an area where the target AMF network element is located ( The AMF region ID), the identifier (AMF Set ID) and the AMF pointer (AMF) of the AMF network element in which the target AMF network element is located are not specifically limited.

Optionally, in the embodiment of the present application, if the target AMF network element further updates the security context of the terminal, the N2 message 1 may further carry the security context of the updated terminal, which is not specifically limited in this embodiment of the present application.

Optionally, in a specific implementation, the NGAP terminal identifier and the GUAMI allocated by the target AMF network element for the terminal, and the security context of the updated terminal may be encapsulated in an N2 mobility management (MM) message. For example, the N2MM message may be a UE CONTEXT MODIFICATION REQUEST, and the terminal context modification request message is used to update the context of the terminal saved in the access device. The context of the terminal includes an NGAP terminal identifier and a GUAMI allocated by the target AMF network element for the terminal, and a security context corresponding to the terminal.

Optionally, there is no necessary sequence of execution between step S505 and step S507 in the embodiment of the present application. Step S505 may be performed first, and then step S507 may be performed. Step S507 may be performed first, and step S505 may be performed. Step S505 and step S507 may be performed at the same time, which is not specifically limited in this embodiment of the present application.

S508. The access device updates the context of the terminal according to the N2 message 1.

Illustratively, the access device may update the NGAP terminal identifier corresponding to the terminal on the access device according to the NGAP terminal identifier allocated by the target AMF network element to the terminal; and the access device may allocate the terminal according to the target AMF network element. GUAMI, update the GUAMI corresponding to the terminal on the access device.

Optionally, in the embodiment of the present application, if the N2 message 1 further carries the security context of the updated terminal, the access device may further update the security corresponding to the terminal on the access device according to the updated security context of the terminal. The context of the present application is not specifically limited thereto.

Optionally, in the embodiment of the present application, after the access device receives the N2 message 1 from the target AMF network element, the terminal may be bound to the link that receives the N2 message 1, and the subsequent access device goes to the target AMF. When the network element sends the uplink message related to the terminal, the network element can directly use the link to send the uplink message, which is not specifically limited in this embodiment.

S509. The access device sends a registration response to the terminal, so that the terminal receives the registration response from the access device.

For a description of the registration response, refer to step S507, and details are not described herein again.

Alternatively, in the embodiment of the present application, after the step S505, if the session switching is required, the handover method provided by the embodiment of the present application may further include the following steps S510-S528:

S510. The target AMF network element determines that a target I-SMF network element needs to be selected for the terminal.

Optionally, in a possible implementation manner, if the target AMF network element in the step S504 can obtain at least one of the information of the source I-SMF network element corresponding to the session or the information of the SMF network element + the PGW-C network element, The target AMF network element determines that the target I-SMF network element needs to be selected for the terminal. The specific AMF network element may include: at least one of the information of the source I-SMF network element or the information of the SMF network element + the PGW-C network element. It is determined that the target I-SMF network element needs to be selected for the terminal.

Exemplarily, for the roaming scenario, if the target AMF network element can obtain the information of the SMF network element + the PGW-C network element in step S504, the information of the SMF network element + the PGW-C network element includes the PLMN ID of the home location, The target AMF network element may determine that the SMF network element + the PGW-C network element is located at the home location according to the information of the SMF network element + the PGW-C network element corresponding to the session, that is, the session is the home route mode, and the target AMF network element may determine The target I-SMF network element needs to be selected for the terminal.

Or, exemplarily, if the target AMF network element can obtain the information of the SMF network element + the PGW-C network element in the step S504, the information of the SMF network element + the PGW-C network element includes the SMF network element + the PGW-C network element. The service area information, or the information of the SMF network element + PGW-C network element is the identification information of the SMF network element + the PGW-C network element, and the target AMF network element may be based on the identification information of the SMF network element + the PGW-C network element. Obtaining the service area information of the SMF network element + the PGW-C network element, and the target AMF network element determines that the service area of the SMF network element + the PGW-C network element cannot be covered according to the service area information of the SMF network element + the PGW-C network element For the current terminal, the target AMF network element can determine that the target I-SMF network element needs to be selected for the terminal.

Or, exemplarily, if the target AMF network element in step S504 can obtain the information of the source I-SMF network element corresponding to the session, the target AMF network element can determine the source I-SMF network according to the information of the source I-SMF network element. The element is a temporary SMF network element that is switched across systems, and the target AMF network element can determine that the target I-SMF network element needs to be selected for the terminal.

Or, exemplarily, if the target AMF network element in step S504 can obtain the information of the source I-SMF network element corresponding to the session and the information of the SMF network element + the PGW-C network element, the target AMF network element can adopt the foregoing session according to the session. The information of the corresponding source I-SMF network element determines the manner in which the target I-SMF network element needs to be selected for the terminal, or uses the information according to the SMF network element + the PGW-C network element to determine that the target I-SMF network element needs to be selected for the terminal. The method of determining the target I-SMF network element needs to be selected for the terminal, and details are not described herein again.

Optionally, in another possible implementation manner, the step S504 in the embodiment of the present application may further include third indication information, where the third indication information is used to indicate that the source I-SMF network element exists, or the third The indication information is used to indicate that the I-SMF network element needs to be reselected for the terminal. Further, the target AMF network element determining that the target I-SMF network element needs to be selected for the terminal may include: the target AMF network element determining, according to the third indication information, that the target I-SMF network element needs to be selected for the terminal.

Optionally, there is no necessary sequence of execution between step S505 and step S510 in the embodiment of the present application. Step S505 may be performed first, and then step S510 may be performed. Step S510 may be performed first, and step S505 may be performed. Step S505 and step S510 may be performed at the same time, which is not specifically limited in this embodiment of the present application.

S511. The target AMF network element selects a target I-SMF network element for the terminal.

The specific implementation of the target AMF network element for the terminal to select the target I-SMF network element may refer to the existing implementation manner, and details are not described herein again.

S512. The target AMF network element sends a session establishment request to the target I-SMF network element, so that the target I-SMF network element receives the session establishment request from the target AMF network element.

The session establishment request carries the second indication information, where the second indication information is used to indicate that the session establishment request is used to switch the session of the terminal, and the access device of the terminal does not change during the handover process (that is, the process occurs. In the registration process that is executed immediately after the switch).

S513. The target I-SMF network element sends a session context request to the source I-SMF network element according to the session establishment request, so that the source I-SMF network element receives the session context request from the target I-SMF network element.

The session context request is used to request the session context of the terminal.

Optionally, in the embodiment of the present application, the session context request may further carry the fourth indication information, where the session context of the terminal that includes the downlink path information of the access device is requested, which is not specifically limited in this embodiment of the present application.

Optionally, in the embodiment of the present application, the target I-SMF network element may send a session to the source I-SMF network element according to the session establishment request, combined with the information of the source I-SMF network element corresponding to the session acquired in step S504. The context request is not specifically limited in this embodiment of the present application.

S514. The source I-SMF network element sends a session context response to the target I-SMF network element, so that the target I-SMF network element receives the session context response from the source I-SMF network element.

The session context response may include the session context of the terminal, and the session context of the terminal includes the downlink path information of the access device and the uplink path information of the UPF network element + the PGW-U network element corresponding to the session of the terminal. The downlink path information of the access device is used to establish a downlink path from the target I-UPF network element to the access device; the uplink path information of the UPF network element + the PGW-U network element is used to establish the target I-UPF network element. The uplink path to the UPF network element + PGW-U network element.

Optionally, the path in the embodiment of the present application may also be referred to as a tunnel, which is not specifically limited in this embodiment of the present application.

Optionally, in the embodiment of the present application, the downlink path information of the access device may include, for example, a tunnel identifier of the N3 tunnel between the access device and the target I-UPF network element on the access device side; the UPF network element+PGW-U The uplink path information of the network element may include, for example, a tunnel identifier of the N9 tunnel between the target I-UPF network element and the UPF network element + the PGW-U network element on the UPF network element + the PGW-U network element side. The tunnel identifier may include, for example, an endpoint address or an endpoint identifier, and the endpoint identifier may be, for example, a tunnel endpoint identifier (TEID), which is not specifically limited in this embodiment of the present application.

S515. The target I-SMF network element selects a target I-UPF network element for the terminal.

The specific implementation of the target I-SMF network element for the terminal to select the target I-UPF network element may refer to the existing implementation manner, and details are not described herein.

S516. The target I-SMF network element sends an N4 session establishment request to the target I-UPF network element, so that the target I-UPF network element receives the N4 session establishment request from the target I-SMF network element.

The N4 session establishment request carries the downlink path information of the access device and the uplink path information of the UPF network element + PGW-U network element corresponding to the session of the terminal.

S517. The target I-UPF network element sends an N4 session establishment response to the target I-SMF network element, so that the target I-SMF network element receives the N4 session establishment response from the target I-UPF network element.

So far, the embodiment of the present application has established a downlink path from the target I-UPF network element to the access device and an uplink path from the target I-UPF network element to the UPF network element + the PGW-U network element. In this way, the target I-UPF network element can send the uplink data to the uplink path of the target I-UPF network element to the UPF network element+PGW-U network element when receiving the uplink data related to the terminal sent by the access device. Corresponding UPF network element + PGW-U network element; the target I-UPF network element can go through the downlink of the target I-UPF network element to the access device when receiving the downlink data related to the terminal to be sent to the access device The path sends the downlink data to the corresponding access device, so that data loss may be avoided in the process of switching the I-SMF network element.

S518. The target I-SMF network element sends an N2 session update request to the target AMF network element, so that the target AMF network element receives the N2 session update request from the target I-SMF network element.

The N2 session update request may carry a session management (SM) N2 message, where the SM N2 message may carry the uplink path information of the target I-UPF network element, and the uplink path information of the target I-UPF network element is used. The uplink path from the access device to the target I-UPF network element is established.

Optionally, in the embodiment of the present application, the uplink path information of the target I-UPF network element may include a tunnel identifier of the N3 tunnel between the access device and the target I-UPF network element on the target I-UPF network element side. For a description of the tunnel identifier, refer to step S514 above, and details are not described herein again.

Optionally, the SM N2 message in the embodiment of the present application is encapsulated in a container, and the target AMF network element is not parsed, and is uniformly described herein, and details are not described herein.

S519. The target AMF network element sends an N2 message 2 to the access device, so that the access device receives the N2 message 2 from the target AMF network element.

The N2 message 2 may carry the N2 session update request in step S518.

Optionally, the N2 message 2 may further carry the NGAP terminal identifier and the GUAMI allocated by the target AMF network element for the terminal. For related description, refer to step S507, and details are not described herein again.

Optionally, the N2 message 2 can also carry the security context of the updated terminal. For related description, refer to step S507, and details are not described herein again.

S520. The access device updates the context of the terminal according to the N2 message 2.

For the related description of the step S520, refer to the step S508, for example, the N2 message 1 in the step S508 is replaced with the N2 message 2 in the step S520, and details are not described herein again.

In addition, the N2 message 2 carries the N2 session update request message in step S518, and the N2 session update request message carries the uplink path information of the target I-UPF network element. Therefore, the access device can also perform the N2 session update request according to the N2 session update request message. The uplink path information of the target I-UPF in the message updates the N3 uplink tunnel corresponding to the session, thereby establishing an uplink path from the access device to the target I-UPF network element, that is, the access device switches the uplink path to the target I. - UPF network element. So far, as shown in Figure 5, the corresponding uplink data transmission path is:

Terminal->Access Device->Target I-UPF Network Element->UPF Network Element+PGW-U Network Element.

In addition, since the downlink path of the target I-UPF network element to the access device has been established in step S516, the bidirectional path between the access device and the target I-UPF network element has been established.

S521. The access device sends an N2 message 3 to the target AMF network element, so that the target AMF network element receives the N2 message 3 from the access device.

The N2 message 3 includes an N2 session update response to be sent to the target I-SMF network element, which is not specifically limited in this embodiment.

Optionally, in the embodiment of the present application, the N2 session update response may carry the downlink tunnel information of the access device, and may not be carried, and is not specifically limited in this embodiment.

S522. The target AMF network element sends an N2 session update response to the target I-SMF network element, so that the target I-SMF network element receives the N2 session update response from the target AMF network element.

S523. The target I-SMF network element sends a session modification request to the SMF network element + the PGW-C network element, so that the SMF network element + the PGW-C network element receives the session modification request from the target I-SMF network element.

Optionally, the session modification request in the embodiment of the present application may carry the downlink path information of the target I-UPF network element, where the downlink path information of the target I-UPF network element is used to establish the slave UPF network element and the PGW-U network. The downlink path from the element to the target I-UPF network element.

Optionally, in the embodiment of the present application, the downlink path information of the target I-UPF network element may include an N9 tunnel between the UPF network element + the PGW-U network element and the target I-UPF network element in the target I-UPF network element. The tunnel identification on the side. For a description of the tunnel identifier, refer to step S514 above, and details are not described herein again.

The S524, the SMF network element and the PGW-C network element send an N4 session modification request to the UPF network element + the PGW-U network element, so that the UPF network element + the PGW-U network element receives the network element from the SMF network element + the PGW-C network element. N4 session modification request.

Optionally, the N4 session modification request in the embodiment of the present application may carry the downlink path information of the target I-UPF network element in step S523. Therefore, the UPF network element+PGW-U network element may also be based on the target I- The downlink path information of the UPF updates the N9 downlink tunnel corresponding to the session, thereby establishing a downlink path from the UPF network element + the PGW-U network element to the target I-UPF network element, that is, the UPF network element + the PGW-U network element The downlink path is switched to the target I-UPF network element. So far, as shown in Figure 5, the corresponding downlink data transmission path is:

UPF network element + PGW-U network element -> target I-UPF -> access device -> terminal.

In addition, since the uplink path of the target I-UPF network element to the UPF network element + the PGW-U network element has been established in step S516, the UPF network element + the PGW-U network element and the target I-UPF network element are connected at this time. The two-way path has been established.

In other words, at this time, the corresponding data transmission path is:

Terminal <-> access device <-> target I-UPF network element <-> UPF network element + PGW-U network element.

S525: The UPF network element + the PGW-U network element sends an N4 session modification response to the SMF network element + the PGW-C network element, so that the SMF network element + the PGW-C network element receives the network element from the UPF network element + the PGW-U network element. The N4 session modifies the response.

S526. The SMF network element + the PGW-C network element sends a session modification response to the target I-SMF network element, so that the target I-SMF network element receives the session modification response from the SMF network element + the PGW-C network element.

S527. The target I-SMF network element sends a session establishment response to the target AMF network element, so that the target AMF network element receives the session establishment response from the target I-SMF network element.

The session establishment response is used to indicate that the terminal has switched from the source I-SMF network element to the target I-SMF network element.

S528. The target AMF network element sends a registration response to the terminal, so that the terminal receives the registration response from the target AMF network element.

The registration response may carry the GUTI allocated by the target AMF network element to the terminal, and the GUTI is composed of the GUAMI allocated by the target AMF network element for the terminal and the temporary identifier allocated by the target AMF network element to the terminal.

Optionally, in the embodiment of the present application, the target AMF network element may send the registration response to the terminal after receiving the session establishment response from the target I-SMF network element, or may send the registration response to the terminal after waiting for a period of time. This embodiment of the present application does not specifically limit this.

Optionally, in the embodiment of the present application, after the session of the terminal is switched to the target I-SMF network element, the target I-SMF network element may further notify the source I-SMF to delete the corresponding session; or, the target AMF network element may After the session is switched, the UDM network element is re-registered, and the source AMF network element notifies the source I-SMF network element corresponding to the session of the terminal to delete the corresponding session; or The target AMF network element may perform step S506 after the session switching is completed, and the source AMF network element notifies the source I-SMF network element to delete the corresponding session after receiving the registration completion notification from the target AMF network element. This is not specifically limited.

Optionally, in the embodiment of the present application, if the target AMF network element does not support some network slices on the source AMF network element, the session on the network slice cannot be switched to the target AMF network element, and the source AMF network element is further The source SMF network element corresponding to all the sessions of the network slice may be notified to delete or release the corresponding session, which is not specifically limited in this embodiment of the present application.

In addition, after the target I-SMF network element receives the session establishment request from the target AMF network element, the embodiment shown in FIG. 5 acquires the session context of the terminal from the source I-SMF network element according to the information of the source I-SMF network element. The downlink path information of the access device in the session context of the terminal is taken as an example for description. Optionally, in the embodiment shown in FIG. 5, after the target I-SMF network element receives the session establishment request from the target AMF network element, the target I-SMF network element may also be based on the information of the SMF network element + the PGW-C network element from the SMF network. The element + PGW-C network element obtains the session context of the terminal, and the session context of the terminal includes the uplink path information of the UPF network element + the PGW-U network element corresponding to the session of the terminal. In addition, the foregoing step S521 and step S522 may carry the downlink path information of the access device, and after the target I-SMF network obtains the downlink path information of the access device, the downlink path information of the access device may be sent to the target. The I-UPF network element can be used to establish a downlink path from the target I-UPF network element to the access device, which is not specifically limited in this embodiment of the present application. Alternatively, if the target AMF network element can obtain the information of the source I-SMF network element corresponding to the session in step S504, the target AMF network element can be based on the information of the source I-SMF network element after step S504. The session context of the terminal is obtained from the source I-SMF network element. The session context of the terminal may include the downlink path information of the access device and the uplink path information of the UPF network element + PGW-U network element corresponding to the session of the terminal. In addition, the session establishment request in the step S512 may carry the session context of the terminal, and the session context of the terminal is not required to be obtained through the step S513 and the step S514.

Based on the handover method provided by the embodiment of the present application, after the terminal switches from the 4G network to the default AMF network element in the 5G network, the corresponding network slice can still be switched.

The actions of the source AMF network element, the target AMF network element, the source I-SMF network element, or the target I-SMF network element in the foregoing steps S501 to S528 may be invoked by the processor 401 in the communication device 400 shown in FIG. The application code stored in the memory 403 is executed, and the embodiment does not impose any limitation.

As shown in FIG. 6 , the switching system shown in FIG. 2 is applied to the 5G network shown in FIG. 3 . As shown in FIG. 6 , the switching method includes the following steps:

S601-S603, the same as the steps S501-S503, the related description can refer to the embodiment shown in FIG. 5, and details are not described herein again.

S604. The source AMF network element sends a re-routing request to the access device, so that the access device receives the re-routing request from the source AMF network element.

The rerouting request carries the information of the target AMF network element, the information of the source AMF network element, and the registration request 1. The information of the source AMF network element may be encapsulated in a container, and the access device does not parse the content in the container. , hereby unified, the following will not repeat.

Optionally, in the embodiment of the present application, the information of the target AMF network element may include, for example, service address information corresponding to the target AMF network element, such as a URI corresponding to the target AMF network element, or an IP address of the target AMF network element, or a target AMF. The FQDN of the network element, or the identifier of the target AMF network element, or other information that can be used to identify the target AMF network element, so that other network elements can find the target AMF network element according to the information of the target AMF network element and corresponding The message is sent to the target AMF network element.

S605. The access device sends the N2 message 4 to the target AMF network element according to the information of the target AMF network element, so that the target AMF network element receives the N2 message 4 from the access device.

The N2 message 4 carries the information of the registration request 1 and the source AMF network element.

S606. The target AMF network element sends a context request to the source AMF network element according to the information of the source AMF network element, so that the source AMF network element receives the context request from the target AMF network element.

Wherein, the context request is used to request the context of the terminal.

Optionally, in the embodiment of the present application, the context request may carry the mapped 5G GUTI carried in the registration request 1, and the source AMF network element may find the context of the terminal according to the 5G GUTI. No specific limitation.

S607. The source AMF network element sends a context response to the target AMF network element, so that the target AMF network element receives the context response from the source AMF network element.

The context response carries the context of the terminal.

For the related description, refer to the embodiment shown in FIG. 5, and the details are not described herein again.

S609, similar to step S506, for example, in the embodiment of the present application, when the target AMF sends a registration completion notification to the source AMF network element, the destination AMF sends the registration to the source AMF network element according to the information of the source AMF network element carried in the N2 message 4. For the description of the remaining related description, refer to the embodiment shown in FIG. 5, and details are not described herein again.

The actions of the source AMF network element, the target AMF network element, the source I-SMF network element, or the target I-SMF network element in the foregoing steps S601 to S631 may be invoked by the processor 401 in the communication device 400 shown in FIG. The application code stored in the memory 403 is executed, and the embodiment does not impose any limitation.

As shown in FIG. 7 , the switching system shown in FIG. 2 is applied to the 5G network shown in FIG. 3 . As shown in FIG. 7 , the switching method includes the following steps:

For the related description, reference may be made to the embodiment shown in FIG. 5, and details are not described herein again.

Optionally, in the embodiment of the present application, after the terminal is switched from the 4G network to the 5G network, the handover method provided by the embodiment of the present application may further include the following steps:

S702. The source AMF network element selects a target AMF network element for the terminal.

The specific implementation of the source AMF network element for the terminal to select the target AMF network element may refer to the existing implementation manner, and details are not described herein.

S703. The source AMF network element sends a handover request to the target AMF network element, so that the target AMF network element receives the handover request from the source AMF network element.

The handover request carries the first indication information and the context of the terminal, where the first indication information is used to indicate that the access device of the terminal does not change in the current handover procedure.

Optionally, the handover request may further carry information about the access device of the terminal, and information used by the access device to identify the terminal on the N2 interface (that is, the NGAP terminal identifier allocated by the access device for the terminal), This embodiment of the present application does not specifically limit this.

Optionally, after the step S703, the handover method provided by the embodiment of the present application may further include the following steps S704-S708:

S704. The target AMF network element sends an N2 message 1 to the access device according to the first indication information, so that the access device receives the N2 message 1 from the target AMF network element.

The N2 message 1 carries the NGAP terminal identifier and GUAMI allocated by the target AMF network element to the terminal.

S705, the same as step S508, related description may refer to the embodiment shown in FIG. 5, and details are not described herein again.

S706. The target AMF network element sends a session update request to the SMF network element + PGW-C network element corresponding to the session of the terminal, so that the SMF network element + the PGW-C network element receives the session update request from the target AMF network element.

The session update request carries the information of the target AMF network element, and is used to update the AMF network element serving as the terminal service on the SMF network element + the PGW-C network element from the source AMF network element to the target AMF network element. In this way, the subsequent SMF network element + PGW-C network element can send the downlink message to the target AMF network element.

Optionally, the session update request may further carry the GUAMI allocated by the target AMF network element to the terminal, so that the SMF network element + the PGW-C network element can update the GUIM corresponding to the terminal on the SMF network element + the PGW-C network element. The embodiment of the present application does not specifically limit this.

Optionally, the target AMF network element may also send a registration request to the UDM network element, where the registration request is used to register the target AMF network element as the current serving AMF network element of the terminal, which is not specifically limited in this embodiment.

S707. The target AMF network element sends a configuration update message to the terminal, so that the terminal receives the configuration update message from the target AMF network element.

The configuration update message carries the GUTI allocated by the target AMF network element to the terminal.

Optionally, in the embodiment of the present application, if the allowed NSSAI is changed, the configuration update message may further carry the updated allowed NSSAI, which is not specifically limited in this embodiment of the present application.

Optionally, the configuration update message in the embodiment of the present application may also be carried in the N2 message 1 in step S704. After receiving the N2 message 1 from the target AMF network element, the access device may send the configuration update message to the The terminal is not specifically limited in this embodiment.

S708. The target AMF network element sends a handover completion notification to the source AMF network element, so that the source AMF network element receives the handover completion notification from the target AMF network element.

The handover completion notification is used to notify the source AMF network element that the handover from the source AMF network element to the target AMF network element has been completed. In addition, the source AMF network element may set the context of the terminal to be inactive or delete the context of the terminal, which is not specifically limited in this embodiment of the present application.

Optionally, there is no necessary sequence of execution between steps S704, S706, S707, and S708 in the embodiment of the present application, and any one of the steps may be performed first, and then the remaining steps may be performed; or any two of them may be executed first. The steps are performed, and the remaining steps are performed. The other steps are performed first, and the remaining steps are performed. The four steps are also performed at the same time, which is not specifically limited in the embodiment of the present application.

Or, optionally, after the step S703, the handover method provided by the embodiment of the present application may further include the following steps S709-S728:

S709-S726, the same as the steps S510-S527, the related description can refer to the embodiment shown in FIG. 5, and details are not described herein again.

S727-S728, the same step S707-S708, related description can refer to the above steps S707-S708, and details are not described herein again.

The actions of the source AMF network element, the target AMF network element, the source I-SMF network element, or the target I-SMF network element in the foregoing steps S701 to S728 may be invoked by the processor 401 in the communication device 400 shown in FIG. The application code stored in the memory 403 is executed, and the embodiment does not impose any limitation.

In summary, in the first aspect, the embodiment of the present application discloses a handover method, including: the target mobility management network element receives the first indication information from the source mobility management network element and the context of the terminal, where the first indication information is used. Instructing the current registration process to occur in the connected state; or the first indication information is used to indicate that the context of the terminal is stored in the source mobility management network element; or the first indication information is used to indicate that the location is not required to be acquired according to the GUTI of the terminal. Determining the context of the terminal; the target mobility management network element sends a registration completion notification to the source mobility management network element after the registration is completed according to the first indication information, where the registration completion notification is used to notify the source mobility management network element that the context of the terminal is no longer Valid or the terminal has been registered to the target mobility management network element.

As an implementation, the first indication information includes information of a source mobility management network element.

For the operation of the target mobility management network element, for example, the operation of the target mobile management network element may refer to the operation of the target AMF network element in FIG. 5 and the related text description, and details are not described herein again.

In addition, in a second aspect, the embodiment of the present application further discloses a handover method, including: a target mobility management network element receives a registration request of an access device from a terminal and information of a source mobility management network element; and the target mobility management network element is configured according to The source mobile management network element sends a context request to the source mobility management network element, the context request is used to request the context of the terminal; the target mobility management network element receives the context of the terminal from the source mobility management network element; target mobility management The network element sends a registration completion notification to the source mobility management network element after the registration is completed according to the information of the source mobility management network element, where the registration completion notification is used to notify the source mobility management network element that the context of the terminal is no longer valid or the terminal has Register to the target mobility management network element.

For the operation of the target mobility management network element, for example, the operation of the target mobile management network element may refer to the operation of the target AMF network element in FIG. 6 and the related text description, and details are not described herein again.

With reference to the foregoing first aspect or the second aspect, as an implementation, the handover method disclosed in the embodiment of the present application may further include: the target mobility management network element sends the target mobility management network element to the NGAP allocated by the terminal to the terminal access device. The terminal identifier and the GUAMI, wherein the NGAP terminal identifier is used to update the NGAP terminal identifier corresponding to the terminal on the access device, and the GUAMI is used to update the GUAMI corresponding to the terminal on the access device.

For the operation of the target mobility management network element, for example, the operation of the target AMF network element in FIG. 5 or FIG. 6 and the related text descriptions are not described herein.

In addition, in a third aspect, the embodiment of the present application further discloses a handover method, including: the target mobility management network element receives first indication information from a source mobility management network element and a context of the terminal, where the first indication information is used to indicate The access device of the terminal does not change in the current handover process; the target mobility management network element sends, according to the first indication information, the NGAP terminal identifier and the GUAMI allocated by the target mobility management network element to the terminal, where the NGAP is The terminal identifier is used to update the NGAP terminal identifier corresponding to the terminal on the access device, and the GUAMI is used to update the GUAMI corresponding to the terminal on the access device.

For the operation of the target mobility management network element, for example, the operation of the target mobility management network element may refer to the operation of the target AMF network element in FIG. 7 and the related text description, and details are not described herein again.

With reference to the foregoing first aspect or the second aspect or the third aspect, as a implementation, the handover method disclosed in the embodiment of the present application may further include: the target mobility management network element sends the updated security context of the terminal to the access device, where The security context of the updated terminal is used to update the security context of the terminal on the access device.

With reference to the foregoing first aspect or the second aspect or the third aspect, as an implementation, the handover method disclosed in the embodiment of the present application may further include: the target mobility management network element selects a target intermediate session management network element for the terminal; target mobility management The network element sends a session establishment request to the target intermediate session management network element, where the session establishment request carries the second indication information, where the second indication information is used to indicate that the session establishment request is used to switch the session of the terminal, and during the handover process, The access device of the terminal does not change.

With reference to the above first aspect or the second aspect or the third aspect, as an implementation, the context of the terminal from the source mobility management network element includes the session context of the terminal, wherein the session context of the terminal is the source mobile management network element from the source Obtained in the intermediate session management network element, where the session context of the terminal includes the downlink path information of the access device of the terminal and the uplink path information of the anchor user plane network element corresponding to the session of the terminal, and the anchor user plane network element The uplink path information is used to establish an uplink path from the target intermediate user plane network element to the anchor user plane function network element, and the downlink path information of the access device is used to establish a downlink path from the target intermediate user plane network element to the access device. Correspondingly, the session establishment request also carries the session context of the terminal.

With reference to the foregoing first aspect or the second aspect or the third aspect, as an implementation, the handover method disclosed in the embodiment of the present application may further include: the target mobility management network element determines that the target intermediate session management network element needs to be selected for the terminal.

As an implementation, the target mobility management network element determines that the target intermediate session management network element needs to be selected for the terminal, including: the target mobility management network element receives the anchor control plane network element corresponding to the session of the terminal from the source mobility management network element. At least one of the information or the information of the source intermediate session management network element; the target mobility management network element determines that the target needs to be selected for the terminal according to at least one of the information of the anchor control plane network element or the information of the source intermediate session management network element Intermediate session management network element.

As an implementation, the target mobility management network element determines that the target intermediate session management network element needs to be selected for the terminal, and the target mobility management network element receives the third indication information from the source mobility management network element, where the third indication information is used. Indicates that the source intermediate session management network element exists; or the third indication information is used to indicate that the intermediate session management network element needs to be reselected for the terminal; the target mobility management network element selects the target intermediate session management network element for the terminal according to the third indication information. .

For the operation of the target mobility management network element, for example, the operation of the target AMF network element in FIG. 5 to FIG. 7 and the related text descriptions are not described herein.

In addition, in a fourth aspect, the embodiment of the present application further discloses a handover method, including: a source mobility management network element receives a registration request from a terminal; and the source mobility management network element selects a target mobility management network element for the terminal according to the registration request. The source mobility management network element sends the first indication information and the context of the terminal to the target mobility management network element, where the first indication information is used to indicate that the current registration process occurs in the connected state; or the first indication information is used to indicate the terminal The context is stored in the source mobility management network element; or the first indication information is used to indicate that the context of the terminal is not required to be acquired according to the GUTI of the terminal; the source mobility management network element receives the registration completion notification from the target mobility management network element, The registration completion notification is used to notify the source mobility management network element that the context of the terminal is no longer valid or that the terminal has registered to the target mobility management network element.

For the operation of the source mobility management network element, for example, the operation of the source AMF network element in FIG. 5 and the related text descriptions are not described herein.

In addition, in a fifth aspect, the embodiment of the present application further discloses a handover method, including: a source mobility management network element receives a registration request from a terminal; and a source mobility management network element selects a target mobility management network element for the terminal according to the registration request; The source mobility management network element sends a rerouting request to the access device of the terminal, where the rerouting request carries the information of the source mobility management network element and the registration request, and the access device sends the registration request and the source to the target mobility management network element. The source management network element receives the context request sent by the target mobility management network element according to the information of the source mobility management network element, where the context request is used to request the context of the terminal; the source mobility management network element moves to the target The management network element sends the context of the terminal; after the registration is completed, the source mobility management network element receives a registration completion notification sent by the target mobility management network element according to the information of the source mobility management network element, and the registration completion notification is used to notify the source mobility management network. The context of the terminal is no longer valid or the terminal has already registered to the target mobility management network element.

For the operation of the source mobility management network element, for example, the operation of the source AMF network element in FIG. 6 and the related text descriptions are not described herein.

With reference to the foregoing fourth aspect or the fifth aspect, as an implementation, after the source mobility management network element receives the registration request from the terminal, the handover method disclosed in the embodiment of the present application may further include: the source mobility management network element to the source intermediate session The management network element sends a session context request for requesting the session context of the terminal; the source mobility management network element receives the session context of the terminal from the source intermediate session management network element; correspondingly, the terminal includes the terminal in the context The session context, where the session context of the terminal includes the downlink path information of the access device of the terminal and the uplink path information of the anchor user plane network element corresponding to the session of the terminal, and the uplink path information of the anchor user plane network element is used. The downlink path of the access device is used to establish a downlink path from the target intermediate user plane network element to the access device, in the uplink path from the target intermediate user plane network element to the anchor user plane function network element.

For the operation of the source mobility management network element, for example, the operation of the source AMF network element in FIG. 5 or FIG. 6 and the related text descriptions are not described herein.

In addition, the embodiment of the present application further discloses a handover method, including: a target intermediate session management network element receives a session establishment request from a target mobility management network element, where the session establishment request carries second indication information, and the second indication information is used. Instructing the session establishment request to switch the session of the terminal, and the access device of the terminal does not change during the handover process; the target intermediate session management network element obtains the source intermediate session management network element according to the second indication information. The session context of the terminal, where the session context of the terminal includes the downlink path information of the access device of the terminal and the uplink path information of the anchor user plane network element corresponding to the session of the terminal, and the uplink path of the anchor user plane network element The information is used to establish an uplink path from the target intermediate user plane network element to the anchor user plane function network element, and the downlink path information of the access device is used to establish a downlink path from the target intermediate user plane network element to the access device.

As an implementation, the target intermediate session management network element acquires the session context of the terminal from the source intermediate session management network element according to the second indication information, including: the target intermediate session management network element manages the source intermediate session according to the second indication information. The network element sends a session context request, where the session context request carries fourth indication information, which is used to request a session context of the terminal including the downlink path information of the access device; and the target intermediate session management network element receives the source from the source intermediate session management network element. The session context of the terminal.

As an implementation, the handover method disclosed in the embodiment of the present application may further include: the target intermediate session management network element sends the uplink path information of the target intermediate user plane network element to the access device, where the target intermediate user plane network element uplink path The information is used to establish an uplink path from the access device to the target intermediate user plane network element.

For the operation of the target intermediate session management network element, for example, the operation of the target intermediate session management network element may refer to the operation of the target I-SMF network element in FIG. 5 to FIG. 7 and the related text description, and details are not described herein again.

The solution provided by the embodiment of the present application is mainly introduced from the perspective of interaction between the network elements. It can be understood that, in order to implement the above functions, the source mobility management network element, the target mobility management network element or the target intermediate session management network element includes a hardware structure and/or a software module corresponding to each function. Those skilled in the art will readily appreciate that the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.

The embodiment of the present application may perform the function module division on the source mobility management network element, the target mobility management network element, or the target intermediate session management network element according to the foregoing method example. For example, each function module may be divided according to each function, or two functional modules may be divided. Or more than two functions are integrated in one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner.

For example, in the case of dividing each functional module in an integrated manner, FIG. 8 shows a schematic structural diagram of a target mobility management network element 80. The target mobility management network element 80 includes a receiving module 801 and a sending module 802.

In a possible implementation, the receiving module 801 is configured to receive first indication information from the source mobility management network element and a context of the terminal, where the first indication information is used to indicate that the current registration process occurs in a connected state; or The first indication information is used to indicate that the context of the terminal is stored in the source mobility management network element; or the first indication information is used to indicate that the context of the terminal is not required to be acquired according to the GUTI of the terminal. The sending module 802 is configured to send, according to the first indication information, a registration completion notification to the source mobility management network element after the registration is completed, where the registration completion notification is used to notify the source mobility management network element terminal that the context is no longer valid or the terminal has been registered. Go to the target mobility management network element.

In another possible implementation manner, the receiving module 801 is configured to receive a registration request of the access device from the terminal and information of the source mobility management network element. The sending module 802 is configured to send a context request to the source mobility management network element according to the information of the source mobility management network element, where the context request is used to request the context of the terminal. The receiving module 801 is further configured to receive a context of the terminal from the source mobility management network element. The sending module 802 is further configured to: after the registration is completed, send a registration completion notification to the source mobility management network element according to the information of the source mobility management network element, where the registration completion notification is used to notify the source mobility management network element terminal that the context is no longer valid. Or the terminal has already registered to the target mobility management network element.

In the above two possible implementation manners, the sending module 802 is further configured to send, to the access device of the terminal, the NGAP terminal identifier and the GUAMI that are allocated by the target mobility management network element to the terminal, where the NGAP terminal identifier is used. The NGAP terminal identifier corresponding to the terminal on the access device is updated, and the GUAMI is used to update the GUAMI corresponding to the terminal on the access device.

In a further possible implementation, the receiving module 801 is configured to receive the first indication information from the source mobility management network element and the context of the terminal, where the first indication information is used to indicate that the access device of the terminal does not occur in the current handover process. change. The sending module 802 is configured to send, according to the first indication information, the NGAP terminal identifier and the GUAMI allocated by the target mobility management network element to the terminal, where the NGAP terminal identifier is used to update the NGAP terminal corresponding to the terminal on the access device. The GUAM is used to update the GUAMI corresponding to the terminal on the access device.

In the foregoing three possible implementation manners, the sending module 802 is further configured to send, to the access device, the security context of the updated terminal, where the updated security context of the terminal is used to update the terminal on the access device. Security context.

In the foregoing three possible implementation manners, optionally, as shown in FIG. 8 , the target mobility management network element 80 further includes a processing module 803. The processing module 803 is configured to select a target intermediate session management network element for the terminal. The sending module 802 is further configured to send a session establishment request to the target intermediate session management network element, where the session establishment request carries the second indication information, where the second indication information is used to indicate that the session establishment request is used to switch the session of the terminal, and in the handover process The access device of the terminal does not change.

Optionally, the processing module 803 is further configured to determine that the target intermediate session management network element needs to be selected for the terminal.

As an implementation, the processing module 803 is configured to determine that the target intermediate session management network element needs to be selected for the terminal, including: information for receiving the anchor control plane network element corresponding to the session of the terminal from the source mobility management network element, or a source intermediate At least one of the information of the session management network element; determining, according to at least one of the information of the anchor control plane network element or the information of the source intermediate session management network element, that the target intermediate session management network element needs to be selected for the terminal;

As another implementation, the processing module 803 is configured to determine that the target intermediate session management network element needs to be selected for the terminal, including: for receiving third indication information from the source mobility management network element, where the third indication information is used to indicate that the source exists in the middle. The session management network element; or the third indication information is used to indicate that the intermediate session management network element needs to be reselected for the terminal; and the target intermediate session management network element is selected for the terminal according to the third indication information.

Optionally, in another possible implementation manner, in the embodiment of the present application, the receiving module 801 is configured to receive first indication information from the source mobility management network element and a context of the terminal, where the first indication information is used to indicate The target mobility management network element does not send a registration completion notification in the subsequent process; the processing module 802 is configured to determine not to send the registration completion notification according to the first indication information.

All the related content of the steps involved in the foregoing method embodiments may be referred to the functional descriptions of the corresponding functional modules, and details are not described herein again.

In the present embodiment, the target mobility management network element 80 is presented in a form that divides the various functional modules in an integrated manner. A "module" herein may refer to a particular ASIC, circuitry, processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other devices that provide the functionality described above. In a simple embodiment, those skilled in the art will appreciate that the target mobility management network element 80 can take the form shown in FIG.

For example, the processor 401 in FIG. 4 can execute the instruction by calling the computer stored in the memory 403, so that the target mobility management network element 80 performs the handover method in the foregoing method embodiment.

Specifically, the function/implementation process of the receiving module 801, the sending module 802, and the processing module 803 in FIG. 8 can be implemented by the processor 401 in FIG. 4 calling a computer executing instruction stored in the memory 403. Alternatively, the function/implementation process of the receiving module 801 and the sending module 802 in FIG. 8 may be implemented by the communication interface 404 in FIG. 4; the function/implementation process of the processing module 803 in FIG. 8 may pass through the processor 401 in FIG. This is accomplished by calling a computer execution instruction stored in the memory 403.

The target mobility management network element 80 provided in this embodiment can perform the foregoing switching method. Therefore, the technical effects of the foregoing method can be referred to the foregoing method embodiments, and details are not described herein again.

Optionally, the embodiment of the present application further provides a chip system, where the chip system includes a processor, and is configured to support the target mobility management network element 80 to implement the foregoing handover method, for example, assigning an NGAP terminal identifier and a GUAMI to the terminal. In one possible design, the chip system also includes a memory. The memory is used to store necessary program instructions and data of the target mobility management network element 80. Of course, the memory may not be in the chip system. The chip system may be composed of a chip, and may also include a chip and other discrete devices. This embodiment of the present application does not specifically limit this.

Or, for example, in the case of dividing each functional module in an integrated manner, FIG. 9 shows a schematic structural diagram of a source mobility management network element 90. The source mobility management network element 90 includes a transceiver module 901 and a processing module 902.

In a possible implementation, the transceiver module 901 is configured to receive a registration request from the terminal. The processing module 902 is configured to select a target mobility management network element for the terminal according to the registration request. The transceiver module 901 is further configured to send the first indication information and the context of the terminal to the target mobility management network element, where the first indication information is used to indicate that the current registration process occurs in the connected state; or the first indication information is used to indicate the context of the terminal. The information is stored in the source mobility management network element; or the first indication information is used to indicate that the context of the terminal does not need to be acquired according to the GUTI of the terminal. The transceiver module 901 is further configured to receive a registration completion notification from the target mobility management network element, where the registration completion notification is used to notify the source mobility management network element terminal that the context is no longer valid or the terminal has registered to the target mobility management network element.

In another possible implementation, the transceiver module 901 is configured to receive a registration request from the terminal. The processing module 902 is configured to select a target mobility management network element for the terminal according to the registration request. The transceiver module 901 is further configured to send a re-routing request to the access device of the terminal, where the re-routing request carries information and a registration request of the source mobility management network element, and the access device sends the registration request and the source mobile to the target mobility management network element. And the transceiver module 901 is further configured to receive a context request sent by the target mobility management network element according to information of the source mobility management network element, where the context request is used to request a context of the terminal. The transceiver module 901 is further configured to send a context of the terminal to the target mobility management network element. The transceiver module 901 is further configured to: after the registration is completed, receive a registration completion notification sent by the target mobility management network element according to the information of the source mobility management network element. The registration completion notification is used to notify the source mobility management network element terminal that the context is no longer valid or that the terminal has registered to the target mobility management network element.

In the above two possible implementation manners, the transceiver module 901 is further configured to send a session context request to the source intermediate session management network element, where the session context request is used to request the session context of the terminal, and the transceiver module 901 further a session context for receiving a terminal from the source intermediate session management network element; correspondingly, the context of the terminal includes a session context of the terminal, where the session context of the terminal includes downlink path information of the access device of the terminal and the session of the terminal The uplink path information of the corresponding anchor user plane network element, and the uplink path information of the anchor user plane network element is used to establish an uplink path from the target intermediate user plane network element to the anchor user plane function network element, and the access device downlink The path information is used to establish a downlink path from the target intermediate user plane network element to the access device.

In the present embodiment, the source mobility management network element 90 is presented in a form that divides the various functional modules in an integrated manner. A "module" herein may refer to a particular ASIC, circuitry, processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other devices that provide the functionality described above. In a simple embodiment, those skilled in the art will appreciate that the source mobility management network element 90 can take the form shown in FIG.

For example, the processor 401 in FIG. 4 can execute the instruction by calling the computer stored in the memory 403, so that the source mobility management network element 90 performs the handover method in the foregoing method embodiment.

Specifically, the function/implementation process of the transceiver module 901 and the processing module 902 in FIG. 9 can be implemented by the processor 401 in FIG. 4 calling a computer execution instruction stored in the memory 403. Alternatively, the function/implementation process of the transceiver module 901 in FIG. 9 can be implemented by the communication interface 404 in FIG. 4; the function/implementation process of the processing module 902 in FIG. 9 can be invoked in the memory 403 through the processor 401 in FIG. The stored computer executes instructions to implement.

The source mobility management network element 90 provided in this embodiment can perform the foregoing switching method. Therefore, the technical effects of the foregoing method can be referred to the foregoing method embodiments, and details are not described herein again.

Optionally, the embodiment of the present application further provides a chip system, where the chip system includes a processor, configured to support the source mobility management network element 90 to implement the foregoing handover method, for example, selecting a target mobility management network element for the terminal according to the registration request. . In one possible design, the chip system also includes a memory. The memory is used to store necessary program instructions and data of the source mobility management network element 90. Of course, the memory may not be in the chip system. The chip system may be composed of a chip, and may also include a chip and other discrete devices. This embodiment of the present application does not specifically limit this.

Or, for example, in the case of dividing each functional module in an integrated manner, FIG. 10 shows a schematic structural diagram of a target intermediate session management network element 100. The target intermediate session management network element 100 includes a transceiver module 1001 and a processing module 1002. The transceiver module 1001 is configured to receive a session establishment request from the target mobility management network element, where the session establishment request carries the second indication information, where the second indication information is used to indicate that the session establishment request is used to switch the session of the terminal, and During the handover process, the access device of the terminal does not change; the processing module 1002 is configured to obtain the session context of the terminal from the source intermediate session management network element according to the second indication information, where the session context of the terminal includes the connection of the terminal. The downlink path information of the device and the uplink path information of the anchor user plane network element corresponding to the session of the terminal, and the uplink path information of the anchor user plane network element is used to establish a function network from the target intermediate user plane network element to the anchor user plane The uplink path of the element, the downlink path information of the access device is used to establish a downlink path from the target intermediate user plane network element to the access device.

Optionally, the processing module 1002 is specifically configured to: send, according to the second indication information, a session context request to the source intermediate session management network element, where the session context request carries fourth indication information, and is used to request downlink path information including the access device. The session context of the terminal; the session context of the terminal from the source intermediate session management network element.

Optionally, the transceiver module 1001 is further configured to send uplink path information of the target intermediate user plane network element to the access device, where the uplink path information of the target intermediate user plane network element is used to establish the slave access device to the target intermediate user. The upstream path of the surface NE.

In this embodiment, the target intermediate session management network element 100 is presented in a form that divides each functional module in an integrated manner. A "module" herein may refer to a particular ASIC, circuitry, processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other devices that provide the functionality described above. In a simple embodiment, those skilled in the art will appreciate that the target intermediate session management network element 100 can take the form shown in FIG.

For example, the processor 401 in FIG. 4 can execute the instruction by calling the computer stored in the memory 403, so that the target intermediate session management network element 100 performs the switching method in the above method embodiment.

Specifically, the function/implementation process of the transceiver module 1001 and the processing module 1002 in FIG. 10 can be implemented by the processor 401 in FIG. 4 calling a computer execution instruction stored in the memory 403. Alternatively, the function/implementation process of the transceiver module 1001 in FIG. 10 can be implemented by the communication interface 404 in FIG. 4; the function/implementation process of the processing module 1002 in FIG. 10 can be invoked in the memory 403 through the processor 401 in FIG. The stored computer executes instructions to implement.

The target intermediate session management network element 100 provided in this embodiment can perform the foregoing switching method. Therefore, the technical effects of the foregoing method can be referred to the foregoing method embodiments, and details are not described herein.

Optionally, the embodiment of the present application further provides a chip system, where the chip system includes a processor, and is configured to support the target intermediate session management network element 100 to implement the foregoing switching method, for example, according to the second indication information, from the source intermediate session management. Obtain the session context of the terminal in the network element. In one possible design, the chip system also includes a memory. The memory is used to store necessary program instructions and data of the target intermediate session management network element 100. Of course, the memory may not be in the chip system. The chip system may be composed of a chip, and may also include a chip and other discrete devices. This embodiment of the present application does not specifically limit this.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using a software program, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server or data center via wired (eg coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.). The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device that includes one or more servers, data centers, etc. that can be integrated with the media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)) or the like.

Although the present application has been described herein in connection with the various embodiments, those skilled in the art can Other variations of the disclosed embodiments are achieved. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit may fulfill several of the functions recited in the claims. Certain measures are recited in mutually different dependent claims, but this does not mean that the measures are not combined to produce a good effect.

While the present invention has been described in connection with the specific embodiments and embodiments thereof, various modifications and combinations can be made without departing from the spirit and scope of the application. Accordingly, the description and drawings are to be regarded as It will be apparent to those skilled in the art that various modifications and changes can be made in the present application without departing from the spirit and scope of the application. Thus, it is intended that the present invention cover the modifications and variations of the present invention.

Claims

A switching method, the method comprising:

The target mobility management network element receives the first indication information from the source mobility management network element and the context of the terminal, where the first indication information is used to indicate that the current registration process occurs in the connected state; or the first indication information is used to indicate The context of the terminal is stored in the source mobility management network element; or the first indication information is used to indicate that the context of the terminal is not required to be acquired according to the global unique temporary identifier GUTI of the terminal;

The target mobility management network element sends a registration completion notification to the source mobility management network element after the registration is completed according to the first indication information, where the registration completion notification is used to notify the source mobility management network element The context of the terminal is no longer valid or the terminal has already registered to the target mobility management network element.
The method according to claim 1, wherein the first indication information comprises information of the source mobility management network element.
The method according to claim 1 or 2, wherein the method further comprises:

The target mobility management network element sends, to the access device of the terminal, a next generation application protocol NGAP terminal identifier and a global mobility management network element identifier GUAMI allocated by the target mobility management network element to the terminal, where the NGAP The terminal identifier is used to update the NGAP terminal identifier corresponding to the terminal on the access device, and the GUAMI is used to update the GUAMI corresponding to the terminal on the access device.
The method according to any one of claims 1 to 3, wherein the method further comprises:

Sending, by the target mobility management network element, the updated security context of the terminal to the access device of the terminal, where the updated security context of the terminal is used to update the terminal on the access device Security context.
The method according to any one of claims 1 to 4, wherein the method further comprises:

The target mobility management network element selects a target intermediate session management network element for the terminal;

The target mobility management network element sends a session establishment request to the target intermediate session management network element, where the session establishment request carries the second indication information, where the second indication information is used to indicate that the session establishment request is used for the handover The session of the terminal is described, and the access device of the terminal does not change during the handover process.
The method according to claim 5, wherein the context of the terminal from the source mobility management network element includes a session context of the terminal, wherein the session context of the terminal is the source mobility management network element Obtained from the source intermediate session management network element, where the session context of the terminal includes the downlink path information of the access device of the terminal and the uplink path information of the anchor user plane network element corresponding to the session of the terminal The uplink path information of the anchor user plane network element is used to establish an uplink path from the target intermediate user plane network element to the anchor user plane function network element, where the downlink path information of the access device is used. Establishing a downlink path from the target intermediate user plane network element to the access device;

Correspondingly, the session establishment request further carries a session context of the terminal.
The method of any of claims 1-6, wherein the method further comprises:

The target mobility management network element determines that a target intermediate session management network element needs to be selected for the terminal.
The method according to claim 7, wherein the target mobility management network element determines that the target intermediate session management network element needs to be selected for the terminal, including:

The target mobility management network element receives at least one of information of an anchor control plane network element corresponding to a session of the terminal from the source mobility management network element or information of a source intermediate session management network element;

Determining, by the target mobility management network element, that the target intermediate session management network element needs to be selected for the terminal, according to at least one of information of the anchor point control plane network element or information of the source intermediate session management network element;

Alternatively, the target mobility management network element determines that the target intermediate session management network element needs to be selected for the terminal, including:

The target mobility management network element receives the third indication information from the source mobility management network element, where the third indication information is used to indicate that the source intermediate session management network element exists; or the third indication information is used by And indicating that the intermediate session management network element needs to be reselected for the terminal; the target mobility management network element selects the target intermediate session management network element for the terminal according to the third indication information.
A switching method, the method comprising:

The source mobility management network element receives a registration request from the terminal;

The source mobility management network element selects a target mobility management network element for the terminal according to the registration request;

The source mobility management network element sends the first indication information and the context of the terminal to the target mobility management network element, where the first indication information is used to indicate that the current registration process occurs in a connected state; or the first indication information The first indication information is used to indicate that the context of the terminal is not required to be acquired according to the global unique temporary identifier GUTI of the terminal;

The source mobility management network element receives a registration completion notification from the target mobility management network element, where the registration completion notification is used to notify the source mobility management network element that the context of the terminal is no longer valid or the terminal has been registered. Go to the target mobility management network element.
The method according to claim 9, wherein the first indication information comprises information of the source mobility management network element.
The method according to claim 9 or 10, wherein after the source mobility management network element receives the registration request from the terminal, the method further includes:

The source mobility management network element sends a session context request to the source intermediate session management network element, where the session context request is used to request a session context of the terminal;

The source mobility management network element receives a session context of the terminal from the source intermediate session management network element;

Correspondingly, the context of the terminal includes a session context of the terminal, where the session context of the terminal includes downlink path information of the access device of the terminal and an anchor user plane corresponding to the session of the terminal. The uplink path information of the network element, the uplink path information of the anchor user plane network element is used to establish an uplink path from the target intermediate user plane network element to the anchor user plane function network element, and the access device downlink The path information is used to establish a downlink path from the target intermediate user plane network element to the access device.
A switching method, the method comprising:

The target intermediate session management network element receives a session establishment request from the target mobility management network element, where the session establishment request carries the second indication information, where the second indication information is used to indicate that the session establishment request is used to switch the session of the terminal. And the access device of the terminal does not change during the handover process;

Obtaining, by the target session management network element, the session context of the terminal from the source intermediate session management network element according to the second indication information, where the session context of the terminal includes the downlink of the access device of the terminal The path information and the uplink path information of the anchor user plane network element corresponding to the session of the terminal, where the uplink path information of the anchor user plane network element is used to establish the target intermediate user plane network element to the anchor point The uplink path of the user plane functions the network element, and the downlink path information of the access device is used to establish a downlink path from the target intermediate user plane network element to the access device.
The method according to claim 12, wherein the target intermediate session management network element acquires the session context of the terminal from the source intermediate session management network element according to the second indication information, including:

The target intermediate session management network element sends a session context request to the source intermediate session management network element according to the second indication information, where the session context request carries fourth indication information, and is used to request to include the access device. The context of the terminal of the downlink path information;

The target intermediate session management network element receives a context of the terminal from the source intermediate session management network element.
The method according to claim 12 or 13, wherein the method further comprises:

The target intermediate session management network element sends the uplink path information of the target intermediate user plane network element to the access device, where the uplink path information of the target intermediate user plane network element is used to establish from the access device to The uplink path of the target intermediate user plane network element.
A switching method, the method comprising:

The target mobility management network element receives the registration request of the access device from the terminal and the information of the source mobility management network element;

And the target mobility management network element sends a context request to the source mobility management network element according to the information of the source mobility management network element, where the context request is used to request a context of the terminal;

The target mobility management network element receives a context of the terminal from the source mobility management network element;

The target mobility management network element sends a registration completion notification to the source mobility management network element after the registration is completed according to the information of the source mobility management network element, where the registration completion notification is used to notify the source mobility management network. The context of the terminal is no longer valid or the terminal has already registered to the target mobility management network element.
A switching method, the method comprising:

The source mobility management network element receives a registration request from the terminal;

The source mobility management network element selects a target mobility management network element for the terminal according to the registration request;

The source mobility management network element sends a rerouting request to the access device of the terminal, where the rerouting request carries the information of the source mobility management network element and the registration request, and the access device sends the The target mobility management network element sends the registration request and the information of the source mobility management network element;

The source mobility management network element receives a context request sent by the target mobility management network element according to information of the source mobility management network element, where the context request is used to request a context of the terminal;

Transmitting, by the source mobility management network element, a context of the terminal to the target mobility management network element;

After the registration is completed, the source mobility management network element receives a registration completion notification sent by the target mobility management network element according to the information of the source mobility management network element, where the registration completion notification is used to notify the source mobility management network. The context of the terminal is no longer valid or the terminal has already registered to the target mobility management network element.
A switching method, the method comprising:

The target mobility management network element receives the first indication information from the source mobility management network element and the context of the terminal, where the first indication information is used to indicate that the access device of the terminal does not change in the current handover procedure;

Transmitting, by the target mobility management network element, the next generation application protocol NGAP terminal identifier and the global mobility management network element identifier GUAMI allocated by the target mobility management network element to the terminal according to the first indication information to the access device The NGAP terminal identifier is used to update an NGAP terminal identifier corresponding to the terminal on the access device, and the GUAMI is used to update a GUAMI corresponding to the terminal on the access device.
A target mobility management network element, wherein the target mobility management network element comprises a receiving module and a sending module;

The receiving module is configured to receive first indication information from the source mobility management network element and a context of the terminal, where the first indication information is used to indicate that the current registration process occurs in a connected state; or, the first indication information is used by The context indicating that the terminal is stored in the source mobility management network element; or the first indication information is used to indicate that the context of the terminal is not required to be acquired according to the global unique temporary identifier GUTI of the terminal;

The sending module is configured to send, according to the first indication information, a registration completion notification to the source mobility management network element after the registration is completed, where the registration completion notification is used to notify the source mobility management network element The context of the terminal is no longer valid or the terminal has already registered to the target mobility management network element.
The target mobility management network element of claim 18, wherein

The sending module is further configured to send, to the access device of the terminal, a next-generation application protocol NGAP terminal identifier and a global mobility management network element identifier GUAMI that are allocated by the target mobility management network element to the terminal, where The NGAP terminal identifier is used to update the NGAP terminal identifier corresponding to the terminal on the access device, and the GUAMI is used to update the GUAMI corresponding to the terminal on the access device.
A target mobility management network element according to claim 18 or 19, characterized in that

The sending module is further configured to send an updated security context of the terminal to an access device of the terminal, where the updated security context of the terminal is used to update the terminal on the access device Security context.
The target mobility management network element according to any one of claims 18 to 20, wherein the target mobility management network element further comprises a processing module;

The processing module is configured to select a target intermediate session management network element for the terminal;

The sending module is further configured to send a session establishment request to the target intermediate session management network element, where the session establishment request carries second indication information, where the second indication information is used to indicate the session establishment request is used for switching The session of the terminal, and the access device of the terminal does not change during the handover process.
The target mobility management network element according to claim 21, wherein

The processing module is further configured to determine that a target intermediate session management network element needs to be selected for the terminal.
The target mobility management network element according to claim 22, wherein the processing module is configured to determine that a target intermediate session management network element needs to be selected for the terminal, comprising: receiving the source mobility management network element from the source At least one of the information of the anchor control plane network element or the information of the source intermediate session management network element corresponding to the session of the terminal; the information of the anchor point control plane network element or the source intermediate session management network element At least one of the information determines that a target intermediate session management network element needs to be selected for the terminal;

Alternatively, the processing module is configured to determine that the target intermediate session management network element needs to be selected for the terminal, including: receiving third indication information from the source mobility management network element, where the third indication information is used to indicate The source intermediate session management network element exists; or the third indication information is used to indicate that the intermediate session management network element needs to be reselected for the terminal; and the target is selected for the terminal according to the third indication information. Intermediate session management network element.
A source mobility management network element, where the source mobility management network element includes: a transceiver module and a processing module;

The transceiver module is configured to receive a registration request from a terminal;

The processing module is configured to select a target mobility management network element for the terminal according to the registration request;

The transceiver module is further configured to send the first indication information and the context of the terminal to the target mobility management network element, where the first indication information is used to indicate that the current registration process occurs in a connected state; or the first indication The information is used to indicate that the context of the terminal is stored in the source mobility management network element; or the first indication information is used to indicate that the context of the terminal is not required to be acquired according to the global unique temporary identifier GUTI of the terminal;

The transceiver module is further configured to receive a registration completion notification from the target mobility management network element, where the registration completion notification is used to notify the source mobility management network element that the context of the terminal is no longer valid or the terminal has Register to the target mobility management network element.
The source mobility management network element of claim 24, wherein

The transceiver module is further configured to send a session context request to the source intermediate session management network element, where the session context request is used to request a session context of the terminal;

The transceiver module is further configured to receive a session context of the terminal from the source intermediate session management network element;

Correspondingly, the context of the terminal includes a session context of the terminal, where the session context of the terminal includes downlink path information of the access device of the terminal and an anchor user plane corresponding to the session of the terminal. The uplink path information of the network element, the uplink path information of the anchor user plane network element is used to establish an uplink path from the target intermediate user plane network element to the anchor user plane function network element, and the access device downlink The path information is used to establish a downlink path from the target intermediate user plane network element to the access device.
A target intermediate session management network element, wherein the target intermediate session management network element comprises: a transceiver module and a processing module;

The transceiver module is configured to receive a session establishment request from a target mobility management network element, where the session establishment request carries second indication information, where the second indication information is used to indicate that the session establishment request is used to switch a session of the terminal And the access device of the terminal does not change during the handover process;

The processing module is configured to obtain, according to the second indication information, a session context of the terminal from a source intermediate session management network element, where the session context of the terminal includes a downlink of the access device of the terminal The path information and the uplink path information of the anchor user plane network element corresponding to the session of the terminal, where the uplink path information of the anchor user plane network element is used to establish the target intermediate user plane network element to the anchor point The uplink path of the user plane functions the network element, and the downlink path information of the access device is used to establish a downlink path from the target intermediate user plane network element to the access device.
The target intermediate session management network element according to claim 26, wherein the processing module is specifically configured to:

Sending, according to the second indication information, a session context request to the source intermediate session management network element, where the session context request carries fourth indication information, and is used to request the terminal that includes the downlink path information of the access device. Session context; receiving a session context of the terminal from the source intermediate session management network element.
A target intermediate session management network element according to claim 26 or 27, wherein

The transceiver module is further configured to send uplink path information of the target intermediate user plane network element to the access device, where the uplink path information of the target intermediate user plane network element is used to establish from the access device to The uplink path of the target intermediate user plane network element.
A target mobility management network element, wherein the target mobility management network element comprises: a receiving module and a sending module;

The receiving module is configured to receive a registration request of the access device from the terminal and information of the source mobility management network element;

The sending module is configured to send a context request to the source mobility management network element according to the information of the source mobility management network element, where the context request is used to request a context of the terminal;

The receiving module is further configured to receive a context of the terminal from the source mobility management network element;

The sending module is further configured to: after the registration is completed, send a registration completion notification to the source mobility management network element according to the information of the source mobility management network element, where the registration completion notification is used to notify the source mobility management The context of the terminal of the network element is no longer valid or the terminal has already registered to the target mobility management network element.
A source mobility management network element, where the source mobility management network element includes: a transceiver module and a processing module;

The transceiver module is configured to receive a registration request from a terminal;

The processing module is configured to select a target mobility management network element for the terminal according to the registration request;

The transceiver module is further configured to send a rerouting request to the access device of the terminal, where the rerouting request carries the information of the source mobility management network element and the registration request, where the access device is located Transmitting, by the target mobility management network element, the registration request and the information of the source mobility management network element;

The transceiver module is further configured to receive a context request sent by the target mobility management network element according to the information of the source mobility management network element, where the context request is used to request a context of the terminal;

The transceiver module is further configured to send a context of the terminal to the target mobility management network element;

The transceiver module is further configured to: after the registration is completed, receive a registration completion notification sent by the target mobility management network element according to the information of the source mobility management network element, where the registration completion notification is used to notify the source mobility management The context of the terminal of the network element is no longer valid or the terminal has already registered to the target mobility management network element.
A target mobility management network element, wherein the target mobility management network element comprises: a receiving module and a sending module;

The receiving module is configured to receive the first indication information from the source mobility management network element and the context of the terminal, where the first indication information is used to indicate that the access device of the terminal does not change in the current handover procedure;

The sending module is configured to send, according to the first indication information, a next-generation application protocol NGAP terminal identifier and a global mobility management network element identifier GUAMI allocated by the target mobility management network element to the terminal to the access device. The NGAP terminal identifier is used to update an NGAP terminal identifier corresponding to the terminal on the access device, and the GUAMI is used to update a GUAMI corresponding to the terminal on the access device.
A switching system, comprising: the target mobility management network element according to any one of claims 18-23, and the source mobility management network element according to claim 24 or 25; or The switching system includes the target mobility management network element of claim 29, and the source mobility management network element of claim 30; or the switching system includes a source mobility management network element, and claim 31 The target mobility management network element, wherein the source mobility management network element is configured to select the target mobility management network element for the terminal, and send the first indication information to the target mobility management network element. And the context of the terminal.
The switching system of claim 32, wherein the switching system further comprises the target intermediate session management network element of any one of claims 26-28.
A target mobility management network element, comprising: a processor and a memory; the memory is configured to store a computer execution instruction, and when the target mobility management network element is running, the processor executes the memory storage The computer executes instructions to cause the target mobility management network element to perform the handover method of any of claims 1-8, or claim 15, or claim 17.
A source mobility management network element, comprising: a processor and a memory; the memory is configured to store a computer execution instruction, and when the source mobility management network element is running, the processor executes the memory storage The computer executes instructions to cause the source mobility management network element to perform the handover method of any one of claims 9-11, or claim 16.
A target intermediate session management network element, comprising: a processor and a memory; the memory is configured to store a computer execution instruction, and when the target intermediate session management network element is running, the processor executes the memory The stored computer executes instructions to cause the target intermediate session management network element to perform the handover method of any of claims 12-14.
A processor, for performing any one of claims 1-8, or any one of claims 9-11, or any one of claims 12-14, or claim 15, or claim 16. The switching method of claim 17.
A computer readable storage medium, wherein the computer readable storage medium stores instructions that, when run on a computer, cause the computer to perform any of claims 1-8, or claim 9. The switching method of any one of -11, or any one of claims 12-14, or claim 15, or claim 16, or claim 17.
A computer program product, wherein the computer program product stores instructions that, when run on a computer, cause the computer to perform any of claims 1-8, or any of claims 9-11 Item, or the switching method according to any one of claims 12-14, or claim 15, or claim 16, or claim 17.
A method for performing any one of claims 1-8, or any one of claims 9-11, or any one of claims 12-14, or claim 15, or claim 16, or claim 17. The device of the switching method.