WO2019210779A1 - 切换方法、设备及*** - Google Patents

切换方法、设备及*** Download PDF

Info

Publication number
WO2019210779A1
WO2019210779A1 PCT/CN2019/083340 CN2019083340W WO2019210779A1 WO 2019210779 A1 WO2019210779 A1 WO 2019210779A1 CN 2019083340 W CN2019083340 W CN 2019083340W WO 2019210779 A1 WO2019210779 A1 WO 2019210779A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
terminal
management network
mobility management
target
Prior art date
Application number
PCT/CN2019/083340
Other languages
English (en)
French (fr)
Inventor
宗在峰
朱奋勤
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN201910121387.9A external-priority patent/CN110446233B/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2019210779A1 publication Critical patent/WO2019210779A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements

Definitions

  • the present application relates to the field of communications, and in particular, to a handover method, device, and system.
  • 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.
  • 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.
  • 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.
  • 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.
  • the first indication information includes information of the source mobility management network element.
  • a handover 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.
  • 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
  • the GUAMI is used to update the GUAMI corresponding to the terminal on the access device.
  • 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.
  • the security context of the terminal on the access device can be updated in time after the terminal switches to the corresponding network slice.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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. .
  • 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.
  • 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.
  • the first indication information includes information of the source mobility management network element.
  • 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.
  • 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.
  • the target 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 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
  • 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.
  • 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.
  • a handover 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.
  • 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
  • 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.
  • 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.
  • 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.
  • 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.
  • a 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.
  • a target mobility management network element 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.
  • 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.
  • 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 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.
  • 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.
  • a 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.
  • a source mobility management network element 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.
  • a source 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 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.
  • 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.
  • a 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.
  • 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.
  • a 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.
  • 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.
  • 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.
  • 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 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.
  • 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.
  • 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.
  • 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.
  • a 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.
  • 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.
  • 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.
  • FIG. 1 is a schematic diagram of an existing 4G network and 5G network interworking architecture
  • FIG. 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.
  • 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).
  • 3GPP 3rd generation partnership project
  • 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.
  • NSSAI Network slice selection assistance information
  • NSSAI includes multiple S-NSSAIs.
  • S-NSSAI consists of a service type (slice/service type, SST) and a slice differentiator (SD).
  • SST includes standardization and operator-defined types; SD is optional information supplementing SST to distinguish multiple network slices of the same SST.
  • 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.
  • 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.
  • SMF Management function
  • PGW-C PDN gateway control plane function
  • PCF policy control function
  • PCRF policy and charging rule function
  • HSS home subscriber server
  • UDM unified data management
  • 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
  • PGW-C is the corresponding to the SMF.
  • the PCF is the policy control function of the 5G network
  • the PCRF is the policy charging rule function of the 4G network corresponding to the PCF.
  • the UDM network element + HSS is referred to as a user data management network element
  • the SMF network element + PGW-C network element is referred to as an anchor control plane network element
  • 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.
  • 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.
  • 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.
  • 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.
  • the SGW communicates with the UPF network element + PGW-U network element through the S5-U interface
  • the SGW communicates with the SMF network element + PGW-C network element through the S5-C interface
  • the UPF network element + PGW-U passes
  • the N3 interface communicates with the NG-RAN device
  • the UPF network element + PGW-U network element communicates with the SMF network element + PGW-C network element through the N4 interface
  • the SMF network element + PGW-C network element passes the N7 interface and the PCF network element +
  • 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
  • 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
  • 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.
  • 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.
  • the 4G network may also include a general packet radio system (GPRS) service support node (SGSN), etc., 5G.
  • GPRS general packet radio system
  • SGSN general packet radio system
  • AUSF authentication service function
  • 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.
  • the handover system 20 includes a source mobility management network element 201 and a target mobility management network element 202.
  • 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 are 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.
  • GUI global unique temporary identity
  • 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.
  • 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.
  • 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.
  • NGAP next generation application protocol
  • GUI globally unique AMF identifier
  • 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.
  • 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.
  • 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.
  • 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.
  • the terminal 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.
  • the switching system 20 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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. .
  • the terminal 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.
  • 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.
  • 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.
  • 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. .
  • I-UPF intermediate intermediate UPF
  • source I-UPF network element which is not specifically limited in this embodiment.
  • 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.
  • PCF policy control function
  • AUSF authentication server function
  • 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.
  • N Next Generation
  • 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).
  • 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.
  • 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).
  • 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.
  • the network element and so on are only one name, and the name does not limit the device itself.
  • 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.
  • the source AMF network element may be replaced with a default AMF network element
  • the source I-UPF network element may be replaced with a source I-UPF or a source I-UPF entity, etc. No longer.
  • 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).
  • RG 5G residential gateway
  • 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.
  • 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).
  • 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.
  • CPU central processing unit
  • ASIC application-specific 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. .
  • RAN radio access network
  • WLAN wireless local area networks
  • 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.
  • 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.
  • the processor 401 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • 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.
  • processors herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • 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.
  • 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.
  • 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.
  • 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.
  • PDA personal digital assistant
  • the embodiment of the present application does not limit the type of the communication device 400.
  • the switching system shown in FIG. 2 is applied to the 5G network shown in FIG. 3 as an example.
  • the switching method provided by the embodiment of the present application includes the following steps:
  • 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.
  • step S501 can refer to the existing implementation manner, and details are not described herein again.
  • the terminal 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.
  • 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.
  • the source AMF network element selects a target AMF network element for the terminal according to 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • IP internet protocol
  • FQDN fully qualified domain name
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 meta-information can find the source I-SMF network element and send a corresponding message to the source I-SMF network element.
  • 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.
  • 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 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.
  • 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.
  • the target AMF network element initiates the rest of the registration process.
  • 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.
  • RA new registration area
  • 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.
  • the handover method provided by the embodiment of the present application may further include the following steps:
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the handover method may further include the following steps S507-S509:
  • 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.
  • 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 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.
  • the registration response may also carry the allowed NSSAI, which is not specifically limited in this 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.
  • PLMN public land mobile network
  • 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.
  • 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.
  • 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.
  • 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.
  • the access device updates the context of the terminal according to the N2 message 1.
  • 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.
  • 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.
  • the terminal may be bound to the link that receives the N2 message 1, and the subsequent access device goes to the target AMF.
  • 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.
  • the access device sends a registration response to the terminal, so that the terminal receives the registration response from the access device.
  • step S507 For a description of the registration response, refer to step S507, and details are not described herein again.
  • the handover method provided by the embodiment of the present application may further include the following steps S510-S528:
  • the target AMF network element determines that a target I-SMF network element needs to be selected for the terminal.
  • 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.
  • 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.
  • 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.
  • 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
  • the target AMF network element can determine that the target I-SMF network element needs to be selected for the terminal.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • 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.
  • 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.
  • 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.
  • 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 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • SM session management
  • 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.
  • 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.
  • 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.
  • 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.
  • the N2 message 2 may further carry the NGAP terminal identifier and the GUAMI allocated by the target AMF network element for the terminal.
  • the N2 message 2 may further carry the NGAP terminal identifier and the GUAMI allocated by the target AMF network element for the terminal.
  • the N2 message 2 can also carry the security context of the updated terminal.
  • the N2 message 2 can also carry the security context of the updated terminal.
  • the access device updates the context of the terminal according to the N2 message 2.
  • step S520 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.
  • 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:
  • step S516 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 may carry the downlink path information of the target I-UPF network element.
  • 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.
  • 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:
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the registration response may also carry the allowed NSSAI, which is not specifically limited in this 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the switching system shown in FIG. 2 is applied to the 5G network shown in FIG. 3 .
  • the switching method includes the following steps:
  • 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.
  • 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.
  • service address information corresponding to the target AMF network element
  • a URI corresponding to the target AMF network element
  • IP address of the target AMF network element
  • a target AMF a target AMF.
  • the message is sent to the target AMF network element.
  • 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.
  • 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.
  • the context request is used to request the context of the terminal.
  • 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.
  • the source AMF network element may find the context of the terminal according to the 5G GUTI.
  • 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.
  • step 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.
  • 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.
  • 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 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.
  • the switching system shown in FIG. 2 is applied to the 5G network shown in FIG. 3 .
  • the switching method includes the following steps:
  • the handover method provided by the embodiment of the present application may further include the following steps:
  • 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.
  • 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.
  • 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.
  • the handover method provided by the embodiment of the present application may further include the following steps S704-S708:
  • 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.
  • 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.
  • step S705 the same as step S508, related description may refer to the embodiment shown in FIG. 5, and details are not described herein again.
  • 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.
  • 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.
  • 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.
  • 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.
  • the configuration update message may further carry the updated allowed NSSAI, which is not specifically limited in this embodiment of the present application.
  • the configuration update message in the embodiment of the present application may also be carried in the N2 message 1 in step S704.
  • the access device may send the configuration update message to the The terminal is not specifically limited in this embodiment.
  • 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.
  • 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.
  • steps S704, S706, S707, and S708 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.
  • the handover method provided by the embodiment of the present application may further include the following steps S709-S728:
  • 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 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.
  • 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.
  • 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.
  • the first indication information includes information of a source mobility management network element.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • 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 session establishment request also carries the session context of the terminal.
  • 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.
  • 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.
  • 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. .
  • 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.
  • 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.
  • the first indication information includes information of a source mobility management network element.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 is a session context of the terminal.
  • 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.
  • 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 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • processing module 803 is further configured to determine that the target intermediate session management network element needs to be selected for the terminal.
  • 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;
  • 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.
  • 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.
  • 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.
  • the target mobility management network element 80 can take the form shown in FIG.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the source mobility management network element 90 can take the form shown in FIG.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 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 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 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.
  • the target intermediate session management network element 100 can take the form shown in FIG.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • 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.
  • the computer program 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.
  • a magnetic medium eg, a floppy disk, a hard disk, a magnetic tape
  • an optical medium eg, a DVD
  • a semiconductor medium such as a solid state disk (SSD)

Abstract

本申请实施例提供切换方法、设备及***，可以在终端从源网络切换到目标网络中的缺省移动管理网元之后，仍可以切换到相应的网络切片。方法包括：目标移动管理网元接收来自源移动管理网元的第一指示信息和终端的上下文，该第一指示信息用于指示当前注册流程发生在连接态；或者，该第一指示信息用于指示该终端的上下文存储在该源移动管理网元中；或者，该第一指示信息用于指示不需要根据该终端的全球唯一临时标识GUTI获取该终端的上下文；目标移动管理网元根据该第一指示信息，在注册完成之后，向源移动管理网元发送注册完成通知，该注册完成通知用于通知该源移动管理网元该终端的上下文不再有效或者终端已经注册到该目标移动管理网元。

Description

切换方法、设备及***
本申请要求了2018年5月4日提交的、申请号为201810422132.1、发明名称为“切换方法、设备及***”的中国申请的优先权，以及2019年2月13日提交的、申请号为201910121387.9、发明名称为“切换方法、设备及***”的中国申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及切换方法、设备及***。
背景技术
现有技术中，终端从***(4th generation，4G)网络切换到第五代(5th generation，5G)网络时，4G网络中的移动管理实体(mobility management entity，MME)在选择5G网络中的接入和移动性管理功能(access and mobility management function，AMF)网元时均会选择缺省AMF网元，并不考虑该终端的会话对应的单网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)，因此将导致终端从4G网络切换到5G网络时不能被切换到相应的网络切片，从而不利于网络切片的隔离。
因此，如何在终端从源网络切换到目标网络中的缺省移动管理网元之后，仍可以切换到相应的网络切片，是目前亟待解决的问题。
发明内容
本申请实施例提供切换方法、设备及***，可以在终端从源网络切换到目标网络中的缺省移动管理网元之后，仍可以切换到相应的网络切片。
为达到上述目的，本申请的实施例采用如下技术方案：
第一方面，提供了一种切换方法，该方法包括：目标移动管理网元接收来自源移动管理网元的第一指示信息和终端的上下文，该第一指示信息用于指示当前注册流程发生在连接态；或者，该第一指示信息用于指示该终端的上下文存储在该源移动管理网元中；或者，该第一指示信息用于指示不需要根据该终端的全球唯一临时标识GUTI获取该终端的上下文；目标移动管理网元根据该第一指示信息，在注册完成之后，向源移动管理网元发送注册完成通知，该注册完成通知用于通知该源移动管理网元该终端的上下文不再有效或者该终端已经注册到该目标移动管理网元。基于该方案，在终端从源网络切换到目标网络中的源移动管理网元之后，可以将终端重定向到目标移动管理网元，而该目标移动管理网元可以为目标网络中该终端的会话对应的网络切片中的移动管理网元，因此基于上述方案，可以在终端从源网络切换到目标网络中的源移动管理网元之后，仍可以切换到相应的网络切片。
在一种可能的设计中，该第一指示信息包括该源移动管理网元的信息。
第二方面，提供了一种切换方法，该方法包括：目标移动管理网元接收来自终端的接入设备的注册请求和源移动管理网元的信息；目标移动管理网元根据该源移动管理网元的信息，向源移动管理网元发送上下文请求，该上下文请求用于请求该终端的上下文；目标 移动管理网元接收来自源移动管理网元的该终端的上下文；目标移动管理网元根据该源移动管理网元的信息，在注册完成之后，向源移动管理网元发送注册完成通知，该注册完成通知用于通知该源移动管理网元该终端的上下文不再有效或者该终端已经注册到该目标移动管理网元。其中，第二方面的技术效果可参考上述第一方面技术效果的描述，在此不再赘述。
结合上述第一方面或第二方面，在一种可能的设计中，本申请实施例提供的切换方法还包括：目标移动管理网元向该终端的接入设备发送该目标移动管理网元为该终端分配的下一代应用协议NGAP终端标识和全球移动管理网元标识GUAMI，其中，该NGAP终端标识用于更新该接入设备上该终端对应的NGAP终端标识，该GUAMI用于更新该接入设备上该终端对应的GUAMI。基于该方案，可以在终端切换到相应的网络切片之后，及时更新接入设备上该终端对应的NGAP终端标识和GUAMI。
第三方面，提供了一种切换方法，该方法包括：目标移动管理网元接收来自源移动管理网元的第一指示信息和终端的上下文，该第一指示信息用于指示当前切换流程中该终端的接入设备不发生改变；目标移动管理网元根据该第一指示信息，向该接入设备发送该目标移动管理网元为该终端分配的下一代应用协议NGAP终端标识和全球移动管理网元标识GUAMI，其中，该NGAP终端标识用于更新该接入设备上该终端对应的NGAP终端标识，该GUAMI用于更新该接入设备上该终端对应的GUAMI。其中，第三方面的技术效果可参考上述第一方面技术效果的描述，在此不再赘述。
结合上述第一方面或第二方面或第三方面，在一种可能的设计中，本申请实施例提供的切换方法还包括：目标移动管理网元向该接入设备发送更新后的该终端的安全上下文，该更新后的该终端的安全上下文用于更新该接入设备上该终端的安全上下文。基于该方案，可以在终端切换到相应的网络切片之后，及时更新接入设备上终端的安全上下文。
结合上述第一方面或第二方面或第三方面，在一种可能的设计中，本申请实施例提供的切换方法还包括：目标移动管理网元为该终端选择目标中间会话管理网元；目标移动管理网元向该目标中间会话管理网元发送会话建立请求，该会话建立请求携带第二指示信息，该第二指示信息用于指示该会话建立请求用于切换该终端的会话，且在切换过程中，该终端的接入设备不发生改变。基于该方案，可以将终端的会话切换到相应的网络切片，且切换过程中，终端的接入设备不发生改变。
结合上述第一方面或第二方面或第三方面，在一种可能的设计中，该来自源移动管理网元的终端的上下文中包括该终端的会话上下文，其中，该终端的会话上下文是该源移动管理网元从源中间会话管理网元中获取的，其中，该终端的会话上下文中包括该终端的接入设备的下行路径信息以及该终端的会话对应的锚点用户面网元的上行路径信息，该锚点用户面网元的上行路径信息用于建立从该目标中间用户面网元到该锚点用户面功能网元的上行路径，该接入设备的下行路径信息用于建立从该目标中间用户面网元到该接入设备的下行路径；相应的，该会话建立请求中还携带该终端的会话上下文。基于该方案，目标移动管理网元在接收会话建立请求之后，不需要再获取该终端的会话上下文，而是可以直接根据会话建立请求中携带的会话上下文将终端的会话切换到相应的网络切片。
结合上述第一方面或第二方面或第三方面，在一种可能的设计中，本申请实施例提供 的切换方法还包括：目标移动管理网元确定需要为该终端选择目标中间会话管理网元。
在一种可能的设计中，目标移动管理网元确定需要为该终端选择目标中间会话管理网元，包括：目标移动管理网元接收来自该源移动管理网元的该终端的会话对应的锚点控制面网元的信息或源中间会话管理网元的信息中的至少一个；目标移动管理网元根据该锚点控制面网元的信息或该源中间会话管理网元的信息中的至少一个，确定需要为该终端选择目标中间会话管理网元。基于该方案，目标移动管理网元可以确定需要为该终端选择目标中间会话管理网元。
在一种可能的设计中，目标移动管理网元确定需要为该终端选择目标中间会话管理网元，包括：目标移动管理网元接收来自该源移动管理网元的第三指示信息，该第三指示信息用于指示存在该源中间会话管理网元；或者，该第三指示信息用于指示需要为该终端重新选择中间会话管理网元；目标移动管理网元根据该第三指示信息，为该终端选择目标中间会话管理网元。基于该方案，目标移动管理网元可以确定需要为该终端选择目标中间会话管理网元。
第四方面，提供了一种切换方法，该方法包括：源移动管理网元接收来自终端的注册请求；源移动管理网元根据该注册请求，为该终端选择目标移动管理网元；源移动管理网元向目标移动管理网元发送第一指示信息和终端的上下文，该第一指示信息用于指示当前注册流程发生在连接态；或者，该第一指示信息用于指示该终端的上下文存储在该源移动管理网元中；或者，该第一指示信息用于指示不需要根据该终端的全球唯一临时标识GUTI获取该终端的上下文；源移动管理网元接收来自该目标移动管理网元的注册完成通知，该注册完成通知用于通知该源移动管理网元该终端的上下文不再有效或者该终端已经注册到该目标移动管理网元。其中，第四方面的技术效果可参考上述第一方面技术效果的描述，在此不再赘述。
在一种可能的设计中，该第一指示信息包括该源移动管理网元的信息。
第五方面，提供了一种切换方法，该方法包括：源移动管理网元接收来自终端的注册请求；源移动管理网元根据该注册请求，为该终端选择目标移动管理网元；源移动管理网元向该终端的接入设备发送重路由请求，该重路由请求携带该源移动管理网元的信息和该注册请求，由该接入设备向该目标移动管理网元发送该注册请求和该源移动管理网元的信息；源移动管理网元接收目标移动管理网元根据该源移动管理网元的信息发送的上下文请求，该上下文请求用于请求该终端的上下文；源移动管理网元向该目标移动管理网元发送该终端的上下文；在注册完成之后，源移动管理网元接收目标移动管理网元根据该源移动管理网元的信息发送的注册完成通知，该注册完成通知用于通知该源移动管理网元该终端的上下文不再有效或者该终端已经注册到该目标移动管理网元。其中，第五方面的技术效果可参考上述第一方面技术效果的描述，在此不再赘述。
结合上述第四方面或第五方面，在一种可能的设计中，在源移动管理网元接收来自终端的注册请求之后，该方法还包括：源移动管理网元向源中间会话管理网元发送会话上下文请求，该会话上下文请求用于请求该终端的会话上下文；源移动管理网元接收来自该源中间会话管理网元的该终端的会话上下文；相应的，该终端的上下文中包括该终端的会话上下文，其中，该终端的会话上下文中包括该终端的接入设备的下行路径信息以及该终端 的会话对应的锚点用户面网元的上行路径信息，该锚点用户面网元的上行路径信息用于建立从目标中间用户面网元到该锚点用户面功能网元的上行路径，该接入设备的下行路径信息用于建立从该目标中间用户面网元到该接入设备的下行路径。基于该方案，目标移动管理网元在接收会话建立请求之后，不需要再获取该终端的会话上下文，而是可以直接根据会话建立请求中携带的终端的会话上下文将终端的会话切换到相应的网络切片。
第六方面，提供了一种切换方法，该方法包括：目标中间会话管理网元接收来自目标移动管理网元的会话建立请求，该会话建立请求携带第二指示信息，该第二指示信息用于指示该会话建立请求用于切换该终端的会话，且在切换过程中，该终端的接入设备不发生改变；目标中间会话管理网元根据该第二指示信息，从源中间会话管理网元中获取该终端的会话上下文，其中，该终端的会话上下文中包括该终端的接入设备的下行路径信息以及该终端的会话对应的锚点用户面网元的上行路径信息，该锚点用户面网元的上行路径信息用于建立从该目标中间用户面网元到该锚点用户面功能网元的上行路径，该接入设备的下行路径信息用于建立从该目标中间用户面网元到该接入设备的下行路径。基于该方案，目标移动管理网元可以根据终端的会话上下文将终端的会话切换到相应的网络切片。
在一种可能的设计中，目标中间会话管理网元根据该第二指示信息，从源中间会话管理网元中获取该终端的会话上下文，包括：目标中间会话管理网元根据该第二指示信息，向该源中间会话管理网元发送会话上下文请求，该会话上下文请求携带第四指示信息，用于请求包括该接入设备的下行路径信息的该终端的会话上下文；目标中间会话管理网元接收来自该源中间会话管理网元的该终端的会话上下文。基于该方案，目标中间会话管理网元可以从源中间会话管理网元中获取该终端的会话上下文。
在一种可能的设计中，该方法还包括：目标中间会话管理网元向该接入设备发送目标中间用户面网元的上行路径信息，其中，该目标中间用户面网元的上行路径信息用于建立从该接入设备到该目标中间用户面网元的上行路径。基于该方案，可以建立从接入设备到目标中间用户面网元的上行路径。
第七方面，提供了一种目标移动管理网元，该目标移动管理网元具有实现上述第一方面或第二方面或第三方面或第二十八方面任一项所述的方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第八方面，提供了一种目标移动管理网元，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该目标移动管理网元运行时，该处理器执行该存储器存储的该计算机执行指令，以使该目标移动管理网元执行如上述第一方面或第二方面或第三方面或第二十八方面任一项所述的切换方法。
第九方面，提供了一种目标移动管理网元，包括：处理器；所述处理器用于与存储器耦合，并读取存储器中的指令之后，根据所述指令执行如上述第一方面或第二方面或第三方面或第二十八方面中任一项所述的切换方法。
第十方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第一方面或第二方面或第三方面或第二十八方面中任一项所述的切换方法。
第十一方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第一方面或第二方面或第三方面或第二十八方面中任一项所述的切换方法。
第十二方面，提供了一种芯片***，该芯片***包括处理器，用于支持目标移动管理网元实现上述第一方面或第二方面或第三方面或第二十八方面中所涉及的功能，例如为终端分配NGAP终端标识和GUAMI。在一种可能的设计中，该芯片***还包括存储器，该存储器，用于保存目标移动管理网元必要的程序指令和数据。该芯片***，可以由芯片构成，也可以包含芯片和其他分立器件。
其中，第七方面至第十二方面中任一种设计方式所带来的技术效果可参见第一方面或第二方面或第三方面或第二十八方面中不同设计方式所带来的技术效果，此处不再赘述。
第十三方面，提供了一种源移动管理网元，该源移动管理网元具有实现上述第四方面或第五方面任一项所述的方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第十四方面，提供了一种源移动管理网元，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该源移动管理网元运行时，该处理器执行该存储器存储的该计算机执行指令，以使该源移动管理网元执行如上述第四方面或第五方面任一项所述的切换方法。
第十五方面，提供了一种源移动管理网元，包括：处理器；所述处理器用于与存储器耦合，并读取存储器中的指令之后，根据所述指令执行如上述第四方面或第五方面中任一项所述的切换方法。
第十六方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第四方面或第五方面中任一项所述的切换方法。
第十七方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第四方面或第五方面中任一项所述的切换方法。
第十八方面，提供了一种芯片***，该芯片***包括处理器，用于支持源移动管理网元实现上述第四方面或第五方面中所涉及的功能，例如根据注册请求，为终端选择目标移动管理网元。在一种可能的设计中，该芯片***还包括存储器，该存储器，用于保存源移动管理网元必要的程序指令和数据。该芯片***，可以由芯片构成，也可以包含芯片和其他分立器件。
其中，第十三方面至第十八方面中任一种设计方式所带来的技术效果可参见第四方面或第五方面中不同设计方式所带来的技术效果，此处不再赘述。
第十九方面，提供了一种目标中间会话管理网元，该目标中间会话管理网元具有实现上述第六方面任一项所述的方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第二十方面，提供了一种目标中间会话管理网元，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该目标中间会话管理网元运行时，该处理器执行该存储器存储的该计算机执行指令，以使该目标中间会话管理网元执行如上述第六方面任一项所述的切换方法。
第二十一方面，提供了一种目标中间会话管理网元，包括：处理器；所述处理器用于与存储器耦合，并读取存储器中的指令之后，根据所述指令执行如上述第六方面中任一项所述的切换方法。
第二十二方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第六方面中任一项所述的切换方法。
第二十三方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第六方面中任一项所述的切换方法。
第二十四方面，提供了一种芯片***，该芯片***包括处理器，用于支持目标中间会话管理网元实现上述第六方面中所涉及的功能，例如根据第二指示信息，从源中间会话管理网元中获取终端的会话上下文。在一种可能的设计中，该芯片***还包括存储器，该存储器，用于保存目标中间会话管理网元必要的程序指令和数据。该芯片***，可以由芯片构成，也可以包含芯片和其他分立器件。
其中，第十九方面至第二十四方面中任一种设计方式所带来的技术效果可参见第六方面中不同设计方式所带来的技术效果，此处不再赘述。
第二十五方面，提供了一种切换***，该切换***包括上述第七方面至第十二方面中任一项所述的可以执行上述第一方面所述的切换方法的目标移动管理网元，以及上述第十三方面至第十八方面中任一项所述的可以执行上述第四方面所述的切换方法的源移动管理网元。
第二十六方面，提供了一种切换***，该切换***包括上述第七方面至第十二方面中任一项所述的可以执行上述第二方面所述的切换方法的目标移动管理网元，以及上述第十三方面至第十八方面中任一项所述的可以执行上述第五方面所述的切换方法的源移动管理网元。
第二十七方面，提供了一种切换***，该切换***包括源移动管理网元，以及上述第七方面至第十二方面中任一项所述的可以执行上述第三方面所述的切换方法的目标移动管理网元；其中，该源移动管理网元，用于为该终端选择目标移动管理网元，并向目标移动管理网元发送该第一指示信息和该终端的上下文。
结合上述第二十五方面或第二十六方面或第二十七方面，在一种可能的设计中，该切换***还包括上述第十九方面至第二十四方面任一项所述的目标中间会话管理网元。
第二十八方面，提供了一种切换方法，包括：目标移动管理网元接收来自源移动管理网元的第一指示信息和终端的上下文，该第一指示信息用于指示目标移动管理网元在后续流程中不发送注册完成通知；目标移动管理网元根据该第一指示信息，确定不发送注册完成通知。基于该方案，在终端从源网络切换到目标网络中的源移动管理网元之后，可以将终端重定向到目标移动管理网元，而该目标移动管理网元可以为目标网络中该终端的会话对应的网络切片中的移动管理网元，因此基于上述方案，可以在终端从源网络切换到目标网络中的源移动管理网元之后，仍可以切换到相应的网络切片。
本申请的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
图1为现有的4G网络和5G网络互通架构的示意图；
图2为本申请实施例提供的一种切换***的结构示意图；
图3为本申请实施例提供的一种切换***在5G网络中的应用示意图；
图4为本申请实施例提供的一种通信设备的硬件结构示意图；
图5为本申请实施例提供的切换方法的流程示意图一；
图6为本申请实施例提供的切换方法的流程示意图二；
图7为本申请实施例提供的切换方法的流程示意图三；
图8为本申请实施例提供的目标移动管理网元的结构示意图；
图9为本申请实施例提供的源移动管理网元的结构示意图；
图10为本申请实施例提供的目标中间会话管理网元的结构示意图。
具体实施方式
为了方便理解本申请实施例的技术方案，首先给出本申请相关技术的简要介绍如下。
网络切片：
网络切片(network slice)是一个用于支持特定网络能力与网络特性的逻辑隔离的网络，可以端到端(end to end，E2E)的包括整个网络，也可以多个网络切共享多个网络功能，是满足第三代合作伙伴计划(3rd generation partnership project，3GPP)提出的5G移动通信技术关于网络差异化需求的关键技术。通常，不同网络切片的网络特征并不相同，且要求网络切片之间相互隔离，互不影响。如增强实现(augmented reality，AR)或虚拟实现(virtual reality，VR)业务的网络切片要求大带宽、低时延；物联网(internet of things，IOT)业务的网络切片要求支持海量终端接入，但带宽小，对时延没要求。
网络切片选择辅助信息(network slice selection assistance information，NSSAI)：
NSSAI中包括多个S-NSSAI。S-NSSAI由服务类型(slice/service type，SST)和切片区分器(slice differentiator，SD)组成。其中，SST包括标准化和运营商自定义的类型；SD是补充SST的可选信息，以区分相同SST的多个网络切片。23.501标准中定义的NSSAI的类型和作用如表一所示。
表一
Figure PCTCN2019083340-appb-000001
4G网络和5G网络互通架构：
如图1所示，为现有的4G网络和5G网络互通架构的示意图。其中，4G网络与5G网络共用用户面功能(user plane function，UPF)网元+分组数据网络(packet data network，PDN)网关用户面功能(PDN gateway user plane function，PGW-U)网元、会话管理功能 (session management function，SMF)网元+PDN网关控制面功能(PDN gateway control plane function，PGW-C)网元、策略控制功能(policy control function，PCF)网元+策略和计费规则功能(policy and charging rules function，PCRF)网元、归属签约用户服务器(home subscriber server，HSS)+统一数据管理(unified data management，UDM)网元。这里“+”表示合设，UPF为5G网络的用户面功能，PGW-U是与UPF对应的4G网络的网关用户面功能，SMF是5G网络的会话管理功能，PGW-C是与SMF对应的4G网络中的网关控制面功能，PCF是5G网络的策略控制功能、PCRF是与PCF对应的4G网络的策略计费规则功能。本申请实施例中，为方便表述，将UDM网元+HSS称之为用户数据管理网元，将SMF网元+PGW-C网元称之为锚点控制面网元，将UPF网元+PGW-U网元称之为锚点用户面网元，在此进行统一说明，以下不再赘述。当然，上述合设后的网络设备也可以用其他名称，本申请实施例对此不作具体限定。
此外，如图1所示，上述4G网络和5G网络互通架构中还可以包括4G网络中的MME和服务网关(Serving Gateway，SGW)，以及，5G网络中的AMF网元。可选的，该4G网络和5G网络互通架构中还可以包括网络切换选择功能(network slice selection function，NSSF)网元。其中，当AMF网元无法为该终端选择网络切片时，AMF网元可以请求该NSSF网元为该终端选择网络切片，本申请实施例对此不作具体限定。
其中，终端通过演进型通用陆地无线接入网(evolved universal terrestrial radio access network，E-UTRAN)设备接入4G网络，终端通过下一代无线接入网(next generation radio access network，NG-RAN)设备接入5G网络。E-UTRAN设备通过S1-MME接口与MME通信，E-UTRAN设备通过S1-U接口与SGW通信，MME通过S11接口与SGW通信，MME通过S6a接口与用户数据管理网元通信，MME通过N26接口与AMF网元通信，SGW通过S5-U接口与UPF网元+PGW-U网元通信，SGW通过S5-C接口与SMF网元+PGW-C网元通信，UPF网元+PGW-U通过N3接口与NG-RAN设备通信，UPF网元+PGW-U网元通过N4接口与SMF网元+PGW-C网元通信，SMF网元+PGW-C网元通过N7接口与PCF网元+PCRF网元通信，UDM网元+HSS通过N10接口与SMF网元+PGW-C网元通信，UDM网元+HSS通过N8接口与AMF网元通信，PCF网元+PCRF网元通过N15接口与AMF网元通信，SMF网元+PGW-C网元通过N11接口与AMF网元通信，AMF网元通过N2接口与NG-RAN设备通信，AMF网元通过N1接口与终端通信。
需要说明的是，图1中的各个网元之间的接口名字只是一个示例，具体实现中接口名字可能为其他名字，本申请实施例对此不作具体限定。
需要说明的是，5G网络中的NG-RAN设备也可以称之为接入设备，该接入设备指的是接入核心网的设备，例如可以是基站，宽带网络业务网关(broadband network gateway，BNG)，汇聚交换机，非3GPP接入设备等。基站可以包括各种形式的基站，例如：宏基站，微基站(也称为小站)，中继站，接入点等，本申请实施例对此不作具体限定。
当然，4G网络和5G网络中还可以有其它的网元，比如，4G网络中还可以包括通用分组无线***(general packet radio system，GPRS)业务支撑节点(serving GPRS support node，SGSN)等，5G网络中还可以包括鉴权服务功能(authentication server function，AUSF)网元等，本申请实施例对此不作具体限定。
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中， 在本申请的描述中，除非另有说明，“多个”是指两个或多于两个；“A/B”表示A或者B。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
如图2所示，为本申请实施例提供的一种切换***20，该切换***20包括源移动管理网元201和目标移动管理网元202。
一种可能的实现方式中，源移动管理网元201，用于接收来自终端的注册请求，并根据该注册请求，为该终端选择目标移动管理网元202之后，向目标移动管理网元202发送第一指示信息和终端的上下文。其中，该第一指示信息用于指示当前注册流程发生在连接态；或者，该第一指示信息用于指示终端的上下文存储在源移动管理网元201中；或者，该第一指示信息用于指示不需要根据终端的全球唯一临时标识(global unique temporary identity，GUTI)获取终端的上下文。
目标移动管理网元202，用于接收来自源移动管理网元201的第一指示信息和终端的上下文，并根据该第一指示信息，在注册完成之后，向源移动管理网元201发送注册完成通知，该注册完成通知用于通知源移动管理网元201终端的上下文不再有效或者该终端已经注册到目标移动管理网元202。
另一种可能的实现方式中，源移动管理网元201，用于接收来自终端的注册请求，并根据该注册请求，为终端选择目标移动管理网元202之后，向终端的接入设备发送重路由请求，该重路由请求携带源移动管理网元201的信息和该注册请求。
目标移动管理网元202，用于接收来自接入设备的注册请求和源移动管理网元的信息，并根据源移动管理网元201的信息，向源移动管理网元201发送上下文请求，该上下文请求用于请求终端的上下文。
源移动管理网元201，用于接收来自目标移动管理网元202的上下文请求，并根据上下文请求，向目标移动管理网元202发送终端的上下文。
目标移动管理网元202，用于接收来自源移动管理网元201的终端的上下文，并根据源移动管理网元201的信息，在注册完成之后，向源移动管理网元201发送注册完成通知，该注册完成通知用于通知源移动管理网元201终端的上下文不再有效或者该终端已经注册到目标移动管理网元202。
再一种可能的实现方式中，源移动管理网元201，用于为终端选择目标移动管理网元202，并向目标移动管理网元202发送第一指示信息和终端的上下文，该第一指示信息用于指示当前切换流程中终端的接入设备不发生改变。
目标移动管理网元202，用于接收来自源移动管理网元201的第一指示信息和终端的上下文，并根据第一指示信息，向接入设备发送目标移动管理网元202为终端分配的下一代 应用协议(next generation application protocol，NGAP)终端标识和全球移动管理网元标识(globally unique AMF identifier,GUAMI)，其中，NGAP终端标识用于更新接入设备上终端对应的NGAP终端标识，GUAMI用于更新接入设备上终端对应的GUAMI。
又一种可能的实现方式中，源移动管理网元201，用于为终端选择目标移动管理网元202，并向目标移动管理网元202发送第一指示信息和终端的上下文，该第一指示信息用于指示目标移动管理网元在后续流程中不发送注册完成通知(例如，不向源移动管理网元201发送注册完成通知，也不向MME发送注册完成通知)；目标移动管理网元202，用于接收来自源移动管理网元201的第一指示信息和终端的上下文，并根据该第一指示信息，确定不发送注册完成通知。
可选的，本申请实施例中的源移动管理网元201也可以称之为缺省移动管理网元，本申请实施例对此不作具体限定。
可选的，本申请实施例中的源移动管理网元201和目标移动管理网元202通常位于不同的网络切片中，在此统一说明，以下不再赘述。
可选的，本申请实施例中的源移动管理网元201和目标移动管理网元202之间可以直接通信，也可以通过其他设备的转发进行通信，本申请实施例对此不作具体限定。
本申请实施例提供的上述切换***中，在终端从源网络切换到目标网络中的缺省移动管理网元之后，可以将终端重定向到目标移动管理网元，而该目标移动管理网元可以为目标网络中该终端的会话对应的网络切片中的移动管理网元，因此基于上述方案，可以在终端从源网络切换到目标网络中的缺省移动管理网元之后，仍可以切换到相应的网络切片。
可选的，如图2所示，本申请实施例提供的切换***20还可以包括目标中间会话管理网元204和源中间会话管理网元205。
其中，目标移动管理网元202，用于为终端选择目标中间会话管理网元204，并向目标中间会话管理网元204发送会话建立请求。其中，该会话建立请求携带第二指示信息，该第二指示信息用于指示该会话建立请求用于切换终端的会话，且在切换过程中，终端的接入设备不发生改变。
目标中间会话管理网元204，用于接收来自目标移动管理网元202的会话建立请求，并根据第二指示信息，从源中间会话管理网元205中获取终端的会话上下文，其中，该终端的会话上下文中包括终端的接入设备的下行路径信息以及终端的会话对应的锚点用户面网元的上行路径信息，该锚点用户面网元的上行路径信息用于建立从目标中间用户面网元到锚点用户面功能网元的上行路径，该接入设备的下行路径信息用于建立从目标中间用户面网元到接入设备的下行路径。
可选的，本申请实施例中的源中间会话管理网元也可以称之为缺省中间会话管理网元，本申请实施例对此不作具体限定。
可选的，本申请实施例中的源中间会话管理网元205和上述源移动管理网元201通常位于同一个网络切片中，在此统一说明，以下不再赘述。
可选的，本申请实施例中的目标中间会话管理网元204和上述目标移动管理网元202通常位于同一个网络切片中，在此统一说明，以下不再赘述。
可选的，本申请实施例中的目标移动管理网元202和目标中间会话管理网元204之间 可以直接通信，也可以通过其他设备的转发进行通信，本申请实施例对此不作具体限定。
可选的，本申请实施例中的目标中间会话管理网元204和源中间会话管理网元205之间可以直接通信，也可以通过其他设备的转发进行通信，本申请实施例对此不作具体限定。
本申请实施例提供的上述切换***中，在终端从源网络切换到目标网络中的缺省中间会话管理网元之后，可以将终端重定向到目标中间会话管理网元，而该目标中间会话管理网元可以为目标网络中该终端的会话对应的网络切片中的会话管理网元，因此基于上述方案，可以在终端从源网络切换到目标网络中的缺省中间会话管理网元之后，仍可以切换到相应的网络切片。
可选的，图2所示的切换***20可以应用于5G网络以及未来其它的网络，本发明实施例对此不作具体限定。
示例性的，假设图2所示的切换***20可以应用于目前的5G网络，则如图3所示，上述的源移动管理网元所对应的网元或者实体可以为5G网络中的源AMF网元；上述的目标移动管理网元所对应的网元或者实体可以为5G网络中的目标AMF网元；上述的源中间会话管理网元所对应的网元或者实体可以为5G网络中的源中间SMF(intermediate SMF，I-SMF)网元；上述的目标中间会话管理网元所对应的网元或者实体可以为5G网络中的目标I-SMF网元。
此外，如图3所示，该5G网络还可以包括接入设备、目标中间UPF(intermediate UPF，I-UPF)网元、或源I-UPF网元等，本申请实施例对此不作具体限定。
虽然未示出，该5G网络还可以包括策略控制功能(policy control function，PCF)网元或鉴权服务器功能(authentication server function，AUSF)网元等，本申请实施例对此不做具体限定。
其中，如图3所示，本申请实施例中，终端通过接入设备接入5G核心网络，终端通过下一代网络(Next generation，N)1接口(简称N1)分别与源AMF网元和目标AMF网元通信，接入设备通过N2接口(简称N2)分别与源AMF网元和目标AMF网元通信，接入设备通过N3接口(简称N3)分别与源I-UPF网元和目标I-UPF网元通信，源AMF网元通过N11接口(简称N11)与源I-SMF网元通信，源I-SMF网元通过N4接口(简称N4)与源I-UPF网元通信；目标AMF网元通过N11与目标I-SMF网元通信，目标I-SMF网元通过N4与目标I-UPF网元通信。此外，源AMF网元通过N14接口(简称N14)与目标AMF网元通信，源I-SMF网元通过N16*接口(简称N16*)与目标I-SMF网元通信，源I-UPF网元通过N9接口(简称N9)与目标I-SMF网元通信。
需要说明的是，图3中的各个网元之间的接口名字只是一个示例，具体实现中接口名字可能为其他名字，本申请实施例对此不作具体限定。
需要说明的是，图3中的终端、接入设备、源AMF网元、目标AMF网元、源I-SMF网元、目标I-SMF网元、源I-UPF网元或目标I-UPF网元等仅是一个名字，名字对设备本身不构成限定。在5G网络以及未来其它的网络中，终端、接入设备、源AMF网元、目标AMF网元、源I-SMF网元、目标I-SMF网元、源I-UPF网元或目标I-UPF网元所对应的网元或实体也可以是其他的名字，本申请实施例对此不作具体限定。例如，源AMF网元还有可能被替换为缺省AMF网元，源I-UPF网元还有可能被替换为源I-UPF或者源I-UPF实体等等， 在此进行统一说明，以下不再赘述。
可选的，本申请实施例中所涉及到的终端(terminal)可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备；还可以包括用户单元(subscriber unit)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、膝上型电脑(laptop computer)、无绳电话(cordless phone)或者无线本地环路(wireless local loop，WLL)台、机器类型通信(machine type communication,MTC)终端、用户设备(user equipment，UE)，移动台(mobile station，MS)，终端设备(terminal device)或者中继用户设备等。其中，中继用户设备例如可以是5G家庭网关(residential gateway，RG)。为方便描述，本申请中，上面提到的设备统称为终端。
可选的，本申请实施例中所涉及的接入设备指的是接入核心网的设备，例如可以是基站，宽带网络业务网关(broadband network gateway，BNG)，汇聚交换机，非第三代合作伙伴计划(3rd generation partnership project，3GPP)接入设备等。基站可以包括各种形式的基站，例如：宏基站，微基站(也称为小站)，中继站，接入点等。
可选的，本申请实施例图2中的源移动管理网元、目标移动管理网元、源中间会话管理网元或者目标中间会话管理网元可以由一个设备实现，也可以由多个设备共同实现，还可以是一个设备内的一个功能模块，本申请实施例对此不作具体限定。可以理解的是，上述功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。
例如，本申请实施例图2中的源移动管理网元、目标移动管理网元、源中间会话管理网元或者目标中间会话管理网元可以通过图4中的通信设备来实现。图4所示为本申请实施例提供的通信设备的硬件结构示意图。该通信设备400包括至少一个处理器401，通信线路402，存储器403以及至少一个通信接口404。
处理器401可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信线路402可包括一通路，在上述组件之间传送信息。
通信接口404，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)等。
存储器403可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。 存储器可以是独立存在，通过通信线路402与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器403用于存储执行本申请方案的计算机执行指令，并由处理器401来控制执行。处理器401用于执行存储器403中存储的计算机执行指令，从而实现本申请下述实施例提供的切换方法。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器401可以包括一个或多个CPU，例如图4中的CPU0和CPU1。
在具体实现中，作为一种实施例，通信设备400可以包括多个处理器，例如图4中的处理器401和处理器408。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中，作为一种实施例，通信设备400还可以包括输出设备405和输入设备406。输出设备405和处理器401通信，可以以多种方式来显示信息。例如，输出设备405可以是液晶显示器(liquid crystal display，LCD)，发光二级管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备406和处理器401通信，可以以多种方式接收用户的输入。例如，输入设备406可以是鼠标、键盘、触摸屏设备或传感设备等。
上述的通信设备400可以是一个通用设备或者是一个专用设备。在具体实现中，通信设备400可以是台式机、便携式电脑、网络服务器、掌上电脑(personal digital assistant，PDA)、移动手机、平板电脑、无线终端设备、嵌入式设备或有图4中类似结构的设备。本申请实施例不限定通信设备400的类型。
下面将结合图1至图4对本申请实施例提供的切换方法进行具体阐述。
需要说明的是，本申请下述实施例中各个网元之间的消息名字或消息中各参数的名字等只是一个示例，具体实现中也可以是其他的名字，本申请实施例对此不作具体限定。
以图2所示的切换***应用于如图3所示的5G网络为例，如图5所示，为本申请实施例提供的一种切换方法，该切换方法包括如下步骤：
S501、终端从4G网络切换到5G网络的过程中，源AMF网元从SMF网元+PGW-C网元中获取该终端的会话对应的S-NSSAI。
其中，步骤S501的具体实现可参考现有的实现方式，在此不再赘述。
此时，如图5所示，相应的数据传输路径为：
终端<->接入设备<->源I-UPF网元<->UPF网元+PGW-U网元。
S502、在终端切换到源AMF网元之后，终端向源AMF网元发送注册请求1，以使得源AMF网元接收来自终端的注册请求1。
可选的，本申请实施例中的注册请求1中可以携带终端请求的NSSAI，本申请实施例对此不作具体限定。
S503、源AMF网元根据注册请求1，为终端选择目标AMF网元。
可选的，本申请实施例中，源AMF网元在获取注册请求1之后，可以根据终端请求的NSSAI为终端选择目标AMF网元。其中，该终端请求的NSSAI可以是步骤S502中的注册请求1中携带的终端请求的NSSAI；也可以是源AMF网元根据步骤S501中获得的该终端的已建立会话对应的S-NSSAI生成的终端请求的NSSAI，还可以是步骤S502中的注册请求1中携带的终端请求的NSSAI与源AMF网元根据步骤S501中获得的该终端的会话对应的S-NSSAI生成的终端请求的NSSAI的集合，本申请实施例对此不作具体限定。
可选的，源AMF网元根据终端请求的NSSAI为终端选择目标AMF网元，具体可以包括：源AMF网元从UDM网元获取终端签约的NSSAI，并将终端签约的NSSAI和终端请求的NSSAI发送给NSSF网元，请求NSSF网元为该终端选择目标AMF网元；进而，NSSF网元可以根据终端签约的NSSAI和终端请求的NSSAI，为终端选择目标AMF网元或者目标AMF网元的集合，并将目标AMF网元的信息或者目标AMF网元的集合的信息发送给源AMF网元。其中，若源AMF网元接收到的是目标AMF网元的集合的信息，则源AMF网元可以根据该目标AMF网元的集合的信息，从目标AMF网元的集合中选择目标AMF网元。
其中，上述仅是示例性的提供一种源AMF网元根据终端请求的NSSAI为终端选择目标AMF网元的具体实现。当然，源AMF网元根据终端请求的NSSAI为终端选择目标AMF网元还可能有其他的方式，具体可参考现有的实现方式，在此不再赘述。
可选的，本申请实施例中，源AMF网元还可以对注册请求1进行验证，以确保该注册请求1来自该终端并且未被篡改，具体实现可参考现有的实现方式，在此不再赘述。
S504、源AMF网元向目标AMF网元发送N14消息，以使得目标AMF网元接收来自源AMF网元的N14消息，其中，该N14消息携带注册请求1、第一指示信息和该终端的上下文。
其中，该第一指示信息用于指示当前注册流程发生在连接态，这样目标AMF网元就不需要根据该终端的GUTI从4G网络的MME中获取该终端的上下文；或者，该第一指示信息用于指示该终端的上下文存储在源AMF网元中，这样目标AMF网元就不需要根据该终端的GUTI从4G网络的MME中获取该终端的上下文；或者，该第一指示信息用于指示不需要根据该终端的GUTI从4G网络的MME中获取该终端的上下文；或者，该第一指示信息用于指示目标AMF网元在后续流程中不需要发送注册完成通知。
可选的，上述第一指示信息可以是显式的指示信息，比如使用单独的位或者字段来表示；该第一指示信息也可以是隐式的指示信息，比如该第一指示信息可以包括源AMF网元的信息，该源AMF网元的信息可以作为一种隐式指示，本申请实施例对此不作具体限定。
可选的，本申请实施例中，源AMF网元的信息例如可以包括源AMF网元对应的服务地址信息，如源AMF网元对应的通用资源标识(universal resource identifier，URI)，或者源AMF网元的互联网协议(internet protocol，IP)地址,或者源AMF网元的全量域名(fully qualified domain name，FQDN)，或者源AMF网元的标识、或者其他可以用于标识源AMF的信息，以使得目标AMF网元根据该源AMF的信息可以找到该源AMF网元并将相应的消息发送给该源AMF网元。
可选的，本申请实施例中，该终端的上下文可以包括：终端的永久标识、终端的能力、终端的临时标识或终端位置信息等与接入和移动性管理相关的上下文。可选的，该终端的上下文还可以包括：终端已经建立的会话对应的会话标识、终端已经建立的会话对应的SMF 网元的信息(如源I-SMF网元的信息或SMF网元+PGW-C网元的信息中的至少一个)或终端已经建立的会话对应的S-NSSAI等终端的会话上下文。可选的，该终端的上下文还可以包括：接入设备的传输层信息或者接入设备中用来在N2接口上标识终端的信息(即接入设备为该终端分配的NGAP终端标识)等，本申请实施例对此不作具体限定。
可选的，本申请实施例中，源I-SMF网元的信息例如可以包括源I-SMF网元对应的服务地址信息，如源I-SMF网元对应的URI，或者源I-SMF网元的IP地址，或者源I-SMF网元的FQDN，或者源I-SMF网元的标识，或者其他可以用于标识源I-SMF的信息，以使得其他网元根据该源I-SMF网元的信息可以找到该源I-SMF网元并将相应的消息发送给该源I-SMF网元。
可选的，本申请实施例中，该源I-SMF网元的信息还可以包括源I-SMF网元的服务区域信息，本申请实施例对此不作具体限定。
可选的，本申请实施例中，SMF网元+PGW-C网元的信息可以包括SMF网元+PGW-C网元对应的服务地址信息，如SMF网元+PGW-C网元对应的URI，或者SMF网元+PGW-C网元的IP地址，或者SMF网元+PGW-C网元的FQDN，或者SMF网元+PGW-C网元的标识，或者其他可以用于标识SMF网元+PGW-C网元的信息，以使得其他网元根据该SMF网元+PGW-C网元的信息可以找到该SMF网元+PGW-C网元并将相应的消息发送给该SMF网元+PGW-C网元。
可选的，本申请实施例中，SMF网元+PGW-C网元的信息还可以包括SMF网元+PGW-C网元的服务区域信息和SMF网元+PGW-C网元所在的公共陆地移动网络(public land mobile network，PLMN)的PLMN标识(identifier，ID)中的至少一个，本申请实施例对此不作具体限定。
可选的，本申请实施例中的N14消息中还可以携带源AMF网元的信息，该源AMF网元的信息的相关描述可参考上述描述，在此不再赘述。
S505、目标AMF网元发起完成其余注册流程。
比如，目标AMF网元可以根据需要可确定是否对终端进行认证、确定新注册区域(registration area，RA)、重新分配GUTI或者从UDM网元获取终端签约数据等，具体实现可参考现有的实现方式，在此不予赘述。
可选的，在注册完成之后，本申请实施例提供的切换方法还可以包括如下步骤：
S506、可选的，目标AMF网元向源AMF网元发送注册完成通知，以使得源AMF网元接收来自目标AMF网元的注册完成通知。
其中，该注册完成通知用于通知源AMF网元：该源AMF网元中该终端的上下文不再有效或者该终端已经注册到目标AMF网元，这样，源AMF网元可以根据该注册完成通知将该终端的上下文设置为不活跃。
可选的，该注册完成通知也可以用于通知源AMF网元删除该源AMF网元中终端的上下文，这样，源AMF网元可以根据该注册完成通知删除该终端的上下文，本申请实施例对此不作具体限定。
可选的，本申请实施例中，源AMF网元也可以在向目标AMF网元发送该终端的上下文一段时间之后，将该终端的上下文设置为不活跃或者删除该终端的上下文。比如，设置一个定时器，在定时器到期之后，将该终端的上下文设置为不活跃或者删除该终端的上下文， 本申请实施例对此不作具体限定。
可选的，若上述步骤S504中的第一指示信息用于指示目标AMF网元在后续流程中不需要发送注册完成通知，此时目标AMF网元可以根据第一指示信息确定不发送注册完成通知，即不执行该步骤S506。可选的，源AMF网元可以设置定时器，在定时器到期之后将终端的上下文设置为不活跃或者删除该终端的上下文，本申请实施例对此不作具体限定。
可选的，在步骤S505之后，若不需要进行会话切换，则本申请实施例提供的切换方法还可以包括如下步骤S507-S509：
S507、目标AMF网元向接入设备发送N2消息1，以使得接入设备接收来自目标AMF网元的N2消息1。
其中，该N2消息1携带注册响应、目标AMF网元为该终端分配的NGAP终端标识和GUAMI。
可选的，本申请实施例中的注册响应中可以携带目标AMF网元为该终端分配的GUTI，该GUTI由目标AMF网元为该终端分配的GUAMI以及目标AMF网元为该终端分配的临时标识构成。
可选的，该注册响应中还可以携带允许的NSSAI，本申请实施例对此不作具体限定。
可选的，本申请实施例中，目标AMF网元为该终端分配的GUAMI可以由公共陆地移动网络(public land mobile network，PLMN)标识(identifier，ID)、目标AMF网元所在区域的标识(AMF region ID)、目标AMF网元所在AMF网元组的标识(AMF Set ID)和AMF pointer(AMF标识)等构成，本申请实施例对此不作具体限定。
可选的，本申请实施例中，若目标AMF网元还更新终端的安全上下文，则该N2消息1还可以携带更新后的终端的安全上下文，本申请实施例对此不作具体限定。
可选的，在具体实现时，目标AMF网元为该终端分配的NGAP终端标识和GUAMI、以及更新后的终端的安全上下文可以封装在N2移动管理(mobility management，MM)消息中。比如，该N2MM消息可以为终端上下文修改请求消息(UE CONTEXT MODIFICATION REQUEST)，该终端上下文修改请求消息用于更新接入设备中保存的该终端的上下文。其中，该终端的上下文中包括目标AMF网元为该终端分配的NGAP终端标识和GUAMI、以及终端对应的安全上下文。
可选的，本申请实施例中的步骤S505与步骤S507之间没有必然的执行先后顺序，可以是先执行步骤S505，再执行步骤S507；也可以是先执行步骤S507，再执行步骤S505；还可以是同时执行步骤S505和步骤S507，本申请实施例对此不作具体限定。
S508、接入设备根据N2消息1，更新终端的上下文。
示例性的，接入设备可以根据目标AMF网元为该终端分配的NGAP终端标识，更新接入设备上该终端对应的NGAP终端标识；以及，接入设备可以根据目标AMF网元为该终端分配的GUAMI，更新接入设备上该终端对应的GUAMI。
可选的，本申请实施例中，若N2消息1还携带更新后的终端的安全上下文，则接入设备还可以根据该更新后的终端的安全上下文，更新接入设备上该终端对应的安全上下文，本申请实施例对此不作具体限定。
可选的，本申请实施例中，在接入设备接收来自目标AMF网元的N2消息1之后，可以将该终端与接收该N2消息1的链路进行绑定，后续接入设备向目标AMF网元发送该终端相 关的上行消息时，可以直接使用该链路进行发送，本申请实施例对此不作具体限定。
S509、接入设备向终端发送注册响应，以使得终端接收来自接入设备的注册响应。
其中，注册响应的相关描述可参考步骤S507，在此不再赘述。
或者，可选的，本申请实施例中，在步骤S505之后，若需要进行会话切换，则本申请实施例提供的切换方法还可以包括如下步骤S510-S528：
S510、目标AMF网元确定需要为该终端选择目标I-SMF网元。
可选的，一种可能的实现方式中，若步骤S504中目标AMF网元可以获取会话对应的源I-SMF网元的信息或SMF网元+PGW-C网元的信息中的至少一个，则目标AMF网元确定需要为终端选择目标I-SMF网元具体可以包括：目标AMF网元根据源I-SMF网元的信息或SMF网元+PGW-C网元的信息中的至少一个，确定需要为该终端选择目标I-SMF网元。
示例性的，针对漫游场景，若步骤S504中目标AMF网元可以获取SMF网元+PGW-C网元的信息，该SMF网元+PGW-C网元的信息包括归属地的PLMN ID，则目标AMF网元可以根据会话对应的SMF网元+PGW-C网元的信息确定SMF网元+PGW-C网元位于归属地，即该会话是归属地路由模式，则目标AMF网元可以确定需要为终端选择目标I-SMF网元。
或者，示例性的，若步骤S504中目标AMF网元可以获取SMF网元+PGW-C网元的信息，该SMF网元+PGW-C网元的信息包括SMF网元+PGW-C网元的服务区域信息，或者该SMF网元+PGW-C网元的信息为SMF网元+PGW-C网元的标识信息，目标AMF网元根据SMF网元+PGW-C网元的标识信息可获取该SMF网元+PGW-C网元的服务区域信息，并且目标AMF网元根据SMF网元+PGW-C网元的服务区域信息确定SMF网元+PGW-C网元的服务区域不能覆盖当前的终端，则目标AMF网元可以确定需要为该终端选择目标I-SMF网元。
或者，示例性的，若步骤S504中目标AMF网元可以获取会话对应的源I-SMF网元的信息，目标AMF网元根据该源I-SMF网元的信息可以确定该源I-SMF网元为跨***切换的临时SMF网元，则目标AMF网元可以确定需要为该终端选择目标I-SMF网元。
或者，示例性的，若步骤S504中目标AMF网元可以获取会话对应的源I-SMF网元的信息和SMF网元+PGW-C网元的信息，则目标AMF网元可以采用上述根据会话对应的源I-SMF网元的信息确定需要为终端选择目标I-SMF网元的方式，或者采用上述根据SMF网元+PGW-C网元的信息确定需要为终端选择目标I-SMF网元的方式，确定需要为该终端选择目标I-SMF网元，在此不再赘述。
可选的，另一种可能的实现方式中，本申请实施例中的步骤S504中还可以携带第三指示信息，该第三指示信息用于指示存在源I-SMF网元，或者该第三指示信息用于指示需要为该终端重新选择I-SMF网元。进而，目标AMF网元确定需要为终端选择目标I-SMF网元具体可以包括：目标AMF网元根据第三指示信息，确定需要为该终端选择目标I-SMF网元。
可选的，本申请实施例中的步骤S505与步骤S510之间没有必然的执行先后顺序，可以是先执行步骤S505，再执行步骤S510；也可以是先执行步骤S510，再执行步骤S505；还可以是同时执行步骤S505和步骤S510，本申请实施例对此不作具体限定。
S511、目标AMF网元为终端选择目标I-SMF网元。
其中，目标AMF网元为终端选择目标I-SMF网元的具体实现可参考现有的实现方式，在此不再赘述。
S512、目标AMF网元向目标I-SMF网元发送会话建立请求，以使得目标I-SMF网元接收来自目标AMF网元的会话建立请求。
其中，该会话建立请求携带第二指示信息，该第二指示信息用于指示该会话建立请求用于切换终端的会话，且在切换过程中，终端的接入设备不发生改变(即该流程发生在切换后立即执行的注册流程中)。
S513、目标I-SMF网元根据该会话建立请求，向源I-SMF网元发送会话上下文请求，以使得源I-SMF网元接收来自目标I-SMF网元的会话上下文请求。
其中，该会话上下文请求用于请求该终端的会话上下文。
可选的，本申请实施例中，该会话上下文请求还可以携带第四指示信息，用于请求包括接入设备的下行路径信息的终端的会话上下文，本申请实施例对此不作具体限定。
可选的，本申请实施例中，目标I-SMF网元可以根据该会话建立请求，结合步骤S504中获取的会话对应的源I-SMF网元的信息，向源I-SMF网元发送会话上下文请求，本申请实施例对此不作具体限定。
S514、源I-SMF网元向目标I-SMF网元发送会话上下文应答，以使得目标I-SMF网元接收来自源I-SMF网元的会话上下文应答。
其中，该会话上下文应答中可以携带该终端的会话上下文，该终端的会话上下文中包括接入设备的下行路径信息以及终端的会话对应的UPF网元+PGW-U网元的上行路径信息。该接入设备的下行路径信息用于建立从目标I-UPF网元到接入设备的下行路径；该UPF网元+PGW-U网元的上行路径信息用于建立从目标I-UPF网元到UPF网元+PGW-U网元的上行路径。
可选的，本申请实施例中的路径也可以称之为隧道，本申请实施例对此不作具体限定。
可选的，本申请实施例中，接入设备的下行路径信息例如可以包括接入设备与目标I-UPF网元之间N3隧道在接入设备侧的隧道标识；UPF网元+PGW-U网元的上行路径信息例如可以包括目标I-UPF网元与UPF网元+PGW-U网元之间的N9隧道在UPF网元+PGW-U网元侧的隧道标识。其中，该隧道标识例如可以包括端点地址或端点标识，该端点标识例如可以是隧道端点标识(tunnel endpoint identifier，TEID)等，本申请实施例对此不作具体限定。
S515、目标I-SMF网元为终端选择目标I-UPF网元。
其中，目标I-SMF网元为终端选择目标I-UPF网元的具体实现可参考现有的实现方式，在此不予赘述。
S516、目标I-SMF网元向目标I-UPF网元发送N4会话建立请求，以使得目标I-UPF网元接收来自目标I-SMF网元的N4会话建立请求。
其中，该N4会话建立请求携带接入设备的下行路径信息以及终端的会话对应的UPF网元+PGW-U网元的上行路径信息。
S517、目标I-UPF网元向目标I-SMF网元发送N4会话建立应答，以使得目标I-SMF网元接收来自目标I-UPF网元的N4会话建立应答。
至此，本申请实施例已经建立了从目标I-UPF网元到接入设备的下行路径以及从目标I-UPF网元到UPF网元+PGW-U网元的上行路径。这样，目标I-UPF网元在接收到接入设备 发送的该终端相关的上行数据时可以通过目标I-UPF网元到UPF网元+PGW-U网元的上行路径将该上行数据发送给对应的UPF网元+PGW-U网元；目标I-UPF网元在接收到待发送给该接入设备的该终端相关的下行数据时可以通过目标I-UPF网元到接入设备的下行路径将该下行数据发送给对应的接入设备，从而可以避免在切换I-SMF网元的过程中导致数据丢失。
S518、目标I-SMF网元向目标AMF网元发送N2会话更新请求，以使得目标AMF网元接收来自目标I-SMF网元的N2会话更新请求。
其中，该N2会话更新请求可以携带会话管理(session management，SM)N2消息，该SM N2消息中可以携带目标I-UPF网元的上行路径信息，该目标I-UPF网元的上行路径信息用于建立从接入设备到目标I-UPF网元的上行路径。
可选的，本申请实施例中，该目标I-UPF网元的上行路径信息可以包括接入设备与目标I-UPF网元之间N3隧道在目标I-UPF网元侧的隧道标识。该隧道标识的相关描述可参考上述步骤S514，在此不再赘述。
可选的，本申请实施例中的SM N2消息被封装在容器中，目标AMF网元不解析，在此统一说明，以下不再赘述。
S519、目标AMF网元向接入设备发送N2消息2，以使得接入设备接收来自目标AMF网元的N2消息2。
其中，该N2消息2可以携带步骤S518中的N2会话更新请求。
可选的，该N2消息2还可以携带目标AMF网元为该终端分配的NGAP终端标识和GUAMI，相关描述可参考步骤S507，在此不再赘述。
可选的，该N2消息2还可以携带更新后的终端的安全上下文，相关描述可参考步骤S507，在此不再赘述。
S520、接入设备根据N2消息2，更新终端的上下文。
其中，步骤S520的相关描述可参考步骤S508，区别比如在于将步骤S508中的N2消息1替换为步骤S520中的N2消息2，在此不再赘述。
此外，由于N2消息2中携带步骤S518中的N2会话更新请求消息，而该N2会话更新请求消息中携带目标I-UPF网元的上行路径信息，因此，接入设备还可以根据N2会话更新请求消息中的目标I-UPF的上行路径信息更新会话对应的N3上行隧道，从而建立从接入设备到目标I-UPF网元的上行路径，也就是说，接入设备将上行路径切换到了目标I-UPF网元，至此，如图5所示，相应的上行数据传输路径为：
终端->接入设备->目标I-UPF网元->UPF网元+PGW-U网元。
此外，由于步骤S516中已经建立目标I-UPF网元到接入设备的下行路径，因此，此时接入设备与目标I-UPF网元之间的双向路径已经建立完成。
S521、接入设备向目标AMF网元发送N2消息3，以使得目标AMF网元接收来自接入设备的N2消息3。
其中，该N2消息3中包括待发送给目标I-SMF网元的N2会话更新响应，本申请实施例对此不作具体限定。
可选的，本申请实施例中，该N2会话更新响应中可以携带接入设备的下行隧道信息，也可以不携带，本申请实施例对此不作具体限定。
S522、目标AMF网元向目标I-SMF网元发送N2会话更新响应，以使得目标I-SMF网元接收来自目标AMF网元的N2会话更新响应。
S523、目标I-SMF网元向SMF网元+PGW-C网元发送会话修改请求，以使得SMF网元+PGW-C网元接收来自目标I-SMF网元的会话修改请求。
可选的，本申请实施例中的会话修改请求中可以携带目标I-UPF网元的下行路径信息，该目标I-UPF网元的下行路径信息用于建立从UPF网元+PGW-U网元到目标I-UPF网元的下行路径。
可选的，本申请实施例中，该目标I-UPF网元的下行路径信息可以包括UPF网元+PGW-U网元与目标I-UPF网元之间N9隧道在目标I-UPF网元侧的隧道标识。该隧道标识的相关描述可参考上述步骤S514，在此不再赘述。
S524、SMF网元+PGW-C网元向UPF网元+PGW-U网元发送N4会话修改请求，以使得UPF网元+PGW-U网元接收来自SMF网元+PGW-C网元的N4会话修改请求。
可选的，本申请实施例中的N4会话修改请求中可以携带步骤S523中的目标I-UPF网元的下行路径信息，因此，UPF网元+PGW-U网元还可以根据该目标I-UPF的下行路径信息更新会话对应的N9下行隧道，从而建立从UPF网元+PGW-U网元到目标I-UPF网元的下行路径，也就是说，UPF网元+PGW-U网元将下行路径切换到了目标I-UPF网元，至此，如图5所示，相应的下行数据传输路径为：
UPF网元+PGW-U网元->目标I-UPF->接入设备->终端。
此外，由于步骤S516中已经建立目标I-UPF网元到UPF网元+PGW-U网元的上行路径，因此，此时UPF网元+PGW-U网元与目标I-UPF网元之间的双向路径已经建立完成。
也就是说，此时，相应的数据传输路径为：
终端<->接入设备<->目标I-UPF网元<->UPF网元+PGW-U网元。
S525、UPF网元+PGW-U网元向SMF网元+PGW-C网元发送N4会话修改应答，以使得SMF网元+PGW-C网元接收来自UPF网元+PGW-U网元的N4会话修改应答。
S526、SMF网元+PGW-C网元向目标I-SMF网元发送会话修改应答，以使得目标I-SMF网元接收来自SMF网元+PGW-C网元的会话修改应答。
S527、目标I-SMF网元向目标AMF网元发送会话建立应答，以使得目标AMF网元接收来自目标I-SMF网元的会话建立应答。
其中，该会话建立应答用于指示终端从源I-SMF网元已经切换到目标I-SMF网元。
S528、目标AMF网元向终端发送注册响应，以使得终端接收来自目标AMF网元的注册响应。
其中，该注册响应可以携带目标AMF网元为该终端分配的GUTI，该GUTI由目标AMF网元为该终端分配的GUAMI以及目标AMF网元为该终端分配的临时标识构成。
可选的，该注册响应中还可以携带允许的NSSAI，本申请实施例对此不作具体限定。
可选的，本申请实施例中，目标AMF网元可以在接收到来自目标I-SMF网元的会话建立应答之后向终端发送注册响应，也可以是等待一段时间之后向终端发送该注册响应，本申请实施例对此不作具体限定。
可选的，本申请实施例中，在将终端的会话切换到目标I-SMF网元之后，目标I-SMF 网元还可以通知源I-SMF删除相应的会话；或者，目标AMF网元可以在会话切换完成后再注册到UDM网元，由UDM网元通知源AMF网元取消注册，此时源AMF网元再通知各终端的会话对应的源I-SMF网元删除相应的会话；或者，目标AMF网元可以在会话切换完成后再执行步骤S506，源AMF网元在接收来自目标AMF网元的注册完成通知后再通知源I-SMF网元删除相应的会话，本申请实施例对此不作具体限定。
可选的，本申请实施例中，若目标AMF网元不支持源AMF网元上的某些网络切片，则这些网络切片上的会话将无法切换到目标AMF网元，则源AMF网元还可以通知该网络切片的所有会话对应的源SMF网元删除或释放相应的会话，本申请实施例对此不作具体限定。
此外，图5所示的实施例以目标I-SMF网元接收来自目标AMF网元的会话建立请求之后，根据源I-SMF网元的信息，从源I-SMF网元获取终端的会话上下文，且该终端的会话上下文中包括接入设备的下行路径信息为例进行说明。可选的，在图5所示的实施例中，目标I-SMF网元接收来自目标AMF网元的会话建立请求之后，也可以根据SMF网元+PGW-C网元的信息，从SMF网元+PGW-C网元获取终端的会话上下文，此时终端的会话上下文中包括终端的会话对应的UPF网元+PGW-U网元的上行路径信息。进而，上述的步骤S521和步骤S522中可以携带接入设备的下行路径信息，目标I-SMF网在元获取接入设备的下行路径信息之后，可以将该接入设备的下行路径信息发送给目标I-UPF网元，从而可以建立从目标I-UPF网元到接入设备的下行路径，本申请实施例对此不作具体限定。或者，可选的，若步骤S504中目标AMF网元可以获取会话对应的源I-SMF网元的信息，则在步骤S504之后，目标AMF网元即可根据该源I-SMF网元的信息，从源I-SMF网元获取该终端的会话上下文，该终端的会话上下文中可以包括接入设备的下行路径信息以及终端的会话对应的UPF网元+PGW-U网元的上行路径信息。进而，步骤S512中的会话建立请求中可以携带该终端的会话上下文，不需要再通过步骤S513和步骤S514获取该终端的会话上下文，本申请实施例对此不作具体限定。
基于本申请实施例提供的切换方法，可以在终端从4G网络切换到5G网络中的缺省AMF网元之后，仍可以切换到相应的网络切片。
其中，上述步骤S501至S528中的源AMF网元、目标AMF网元、源I-SMF网元或者目标I-SMF网元的动作可以由图4所示的通信设备400中的处理器401调用存储器403中存储的应用程序代码来执行，本实施例对此不作任何限制。
以图2所示的切换***应用于如图3所示的5G网络为例，如图6所示，为本申请实施例提供的另一种切换方法，该切换方法包括如下步骤：
S601-S603、同步骤S501-S503，相关描述可参考图5所示的实施例，在此不再赘述。
S604、源AMF网元向接入设备发送重路由请求，以使得接入设备接收来自源AMF网元的重路由请求。
其中，该重路由请求中携带目标AMF网元的信息、源AMF网元的信息和注册请求1，该源AMF网元的信息可以被封装在容器中，接入设备不解析该容器中的内容，在此统一说明，以下不再赘述。
可选的，本申请实施例中，目标AMF网元的信息例如可以包括目标AMF网元对应的服务地址信息，如目标AMF网元对应的URI，或者目标AMF网元的IP地址，或者目标AMF网 元的FQDN，或者目标AMF网元的标识，或者其他可以用于标识目标AMF网元的信息，以使得其他网元根据该目标AMF网元的信息可以找到该目标AMF网元并将相应的消息发送给该目标AMF网元。
S605、接入设备根据目标AMF网元的信息，向目标AMF网元发送N2消息4，以使得目标AMF网元接收来自接入设备的N2消息4。
其中，该N2消息4携带注册请求1以及源AMF网元的信息。
S606、目标AMF网元根据源AMF网元的信息，向源AMF网元发送上下文请求，以使得源AMF网元接收来自目标AMF网元的上下文请求。
其中，该上下文请求用于请求终端的上下文。
可选的，本申请实施例中，该上下文请求中可以携带注册请求1中携带的映射的5G GUTI，进而源AMF网元可以根据该5G GUTI查找到该终端的上下文，本申请实施例对此不作具体限定。
S607、源AMF网元向目标AMF网元发送上下文应答，以使得目标AMF网元接收来自源AMF网元的上下文应答。
其中，该上下文应答中携带该终端的上下文。
S608、同步骤S505，相关描述可参考图5所示的实施例，在此不再赘述。
S609、与步骤S506类似，区别比如在于，本申请实施例中，目标AMF向源AMF网元发送注册完成通知时，根据N2消息4中携带的源AMF网元的信息向源AMF网元发送注册完成通知，其余相关描述可参考图5所示的实施例，在此不再赘述。
S610-S631、同步骤S507-S528，相关描述可参考图5所示的实施例，在此不再赘述。
基于本申请实施例提供的切换方法，可以在终端从4G网络切换到5G网络中的缺省AMF网元之后，仍可以切换到相应的网络切片。
其中，上述步骤S601至S631中的源AMF网元、目标AMF网元、源I-SMF网元或者目标I-SMF网元的动作可以由图4所示的通信设备400中的处理器401调用存储器403中存储的应用程序代码来执行，本实施例对此不作任何限制。
以图2所示的切换***应用于如图3所示的5G网络为例，如图7所示，为本申请实施例提供的另一种切换方法，该切换方法包括如下步骤：
S701、同步骤S501，相关描述可参考图5所示的实施例，在此不再赘述。
可选的，本申请实施例中，在终端从4G网络切换到5G网络之后，本申请实施例提供的切换方法还可以包括如下步骤：
S702、源AMF网元为终端选择目标AMF网元。
其中，源AMF网元为终端选择目标AMF网元的具体实现可参考现有的实现方式，在此不予赘述。
S703、源AMF网元向目标AMF网元发送切换请求，以使得目标AMF网元接收来自源AMF网元的切换请求。
其中，该切换请求携带第一指示信息和终端的上下文，该第一指示信息用于指示当前切换流程中终端的接入设备不发生改变。
可选的，该切换请求中还可以携带终端的接入设备的信息，以及接入设备中用来在N2 接口上标识终端的信息(即接入设备为该终端分配的NGAP终端标识)等，本申请实施例对此不作具体限定。
可选的，在步骤S703之后，本申请实施例提供的切换方法还可以包括如下步骤S704-S708：
S704、目标AMF网元根据该第一指示信息，向接入设备发送N2消息1，以使得接入设备接收来自目标AMF网元的N2消息1。
其中，该N2消息1携带目标AMF网元为该终端分配的NGAP终端标识和GUAMI。
可选的，本申请实施例中，若目标AMF网元还更新终端的安全上下文，则该N2消息1还可以携带更新后的终端的安全上下文，本申请实施例对此不作具体限定。
S705、同步骤S508，相关描述可参考图5所示的实施例，在此不再赘述。
S706、目标AMF网元向该终端的会话对应的SMF网元+PGW-C网元发送会话更新请求，以使得SMF网元+PGW-C网元接收来自目标AMF网元的会话更新请求。
其中，该会话更新请求携带目标AMF网元的信息，用于将SMF网元+PGW-C网元上为终端服务的AMF网元从源AMF网元更新为目标AMF网元。这样，后续SMF网元+PGW-C网元可以将下行消息发送给该目标AMF网元。
可选的，该会话更新请求还可以携带目标AMF网元为该终端分配的GUAMI，以使得SMF网元+PGW-C网元可以更新SMF网元+PGW-C网元上该终端对应的GUAMI，本申请实施例对此不作具体限定。
可选的，目标AMF网元还可以向UDM网元发送注册请求，该注册请求用于将目标AMF网元注册为终端当前的服务AMF网元，本申请实施例对此不作具体限定。
S707、目标AMF网元向终端发送配置更新消息，以使得终端接收来自目标AMF网元的配置更新消息。
其中，该配置更新消息携带目标AMF网元为该终端分配的GUTI。
可选的，本申请实施例中，若允许的NSSAI发生了变更，则该配置更新消息中还可以携带更新后的允许的NSSAI，本申请实施例对此不作具体限定。
可选的，本申请实施例中的配置更新消息也可以携带在步骤S704中的N2消息1中，接入设备接收到来自目标AMF网元的N2消息1之后，可以将该配置更新消息发送给终端，本申请实施例对此不作具体限定。
S708、目标AMF网元向源AMF网元发送切换完成通知，以使得源AMF网元接收来自目标AMF网元的切换完成通知。
其中，该切换完成通知用于通知源AMF网元已经完成从源AMF网元到目标AMF网元的切换。进而，源AMF网元可以将该终端的上下文设置为不活跃或者删除该终端的上下文，本申请实施例对此不作具体限定。
可选的，本申请实施例步骤S704、S706、S707和S708之间没有必然的执行先后顺序，可以先执行其中的任意一个步骤，再执行其余的步骤；也可以是先执行其中的任意两个步骤，再执行其余的步骤；也可以是先执行其中的任意三个步骤，再执行其余的步骤；还可以是同时执行这四个步骤，本申请实施例对此不作具体限定。
或者，可选的，在步骤S703之后，本申请实施例提供的切换方法还可以包括如下步骤 S709-S728：
S709-S726、同步骤S510-S527，相关描述可参考图5所示的实施例，在此不再赘述。
S727-S728、同步骤S707-S708，相关描述可参考上述步骤S707-S708，在此不再赘述。
基于本申请实施例提供的切换方法，可以在终端从4G网络切换到5G网络中的缺省AMF网元之后，仍可以切换到相应的网络切片。
其中，上述步骤S701至S728中的源AMF网元、目标AMF网元、源I-SMF网元或者目标I-SMF网元的动作可以由图4所示的通信设备400中的处理器401调用存储器403中存储的应用程序代码来执行，本实施例对此不作任何限制。
综上，因此，第一方面，本申请实施例公开了一种切换方法，包括：目标移动管理网元接收来自源移动管理网元的第一指示信息和终端的上下文，该第一指示信息用于指示当前注册流程发生在连接态；或者，该第一指示信息用于指示终端的上下文存储在源移动管理网元中；或者，该第一指示信息用于指示不需要根据终端的GUTI获取所述终端的上下文；目标移动管理网元根据第一指示信息，在注册完成之后，向源移动管理网元发送注册完成通知，该注册完成通知用于通知源移动管理网元该终端的上下文不再有效或者终端已经注册到目标移动管理网元。
作为一种实现，该第一指示信息包括源移动管理网元的信息。
上述切换方法中，例如，目标移动管理网元的操作可参考图5中目标AMF网元的操作及上述相关文字说明，在此不再赘述。
此外，第二方面，本申请实施例还公开了一种切换方法，包括：目标移动管理网元接收来自终端的接入设备的注册请求和源移动管理网元的信息；目标移动管理网元根据源移动管理网元的信息，向源移动管理网元发送上下文请求，该上下文请求用于请求该终端的上下文；目标移动管理网元接收来自源移动管理网元的该终端的上下文；目标移动管理网元根据该源移动管理网元的信息，在注册完成之后，向源移动管理网元发送注册完成通知，该注册完成通知用于通知源移动管理网元该终端的上下文不再有效或者终端已经注册到目标移动管理网元。
上述切换方法中，例如，目标移动管理网元的操作可参考图6中目标AMF网元的操作及上述相关文字说明，在此不再赘述。
结合上述第一方面或第二方面，作为一种实现，本申请实施例公开的切换方法还可以包括：目标移动管理网元向终端的接入设备发送目标移动管理网元为该终端分配的NGAP终端标识和GUAMI，其中，该NGAP终端标识用于更新接入设备上该终端对应的NGAP终端标识，该GUAMI用于更新接入设备上该终端对应的GUAMI。
上述切换方法中，例如，目标移动管理网元的操作可参考图5或图6中目标AMF网元的操作及上述相关文字说明，在此不再赘述。
此外，第三方面，本申请实施例还公开了一种切换方法，包括：目标移动管理网元接收来自源移动管理网元的第一指示信息和终端的上下文，该第一指示信息用于指示当前切换流程中终端的接入设备不发生改变；目标移动管理网元根据第一指示信息，向接入设备发送目标移动管理网元为所述终端分配的NGAP终端标识和GUAMI，其中，该NGAP终端标识用于更新接入设备上该终端对应的NGAP终端标识，该GUAMI用于更新接入设备上该终端对 应的GUAMI。
上述切换方法中，例如，目标移动管理网元的操作可参考图7中目标AMF网元的操作及上述相关文字说明，在此不再赘述。
结合上述第一方面或第二方面或第三方面，作为一种实现，本申请实施例公开的切换方法还可以包括：目标移动管理网元向接入设备发送更新后的终端的安全上下文，该更新后的终端的安全上下文用于更新接入设备上该终端的安全上下文。
结合上述第一方面或第二方面或第三方面，作为一种实现，本申请实施例公开的切换方法还可以包括：目标移动管理网元为该终端选择目标中间会话管理网元；目标移动管理网元向目标中间会话管理网元发送会话建立请求，该会话建立请求携带第二指示信息，该第二指示信息用于指示该会话建立请求用于切换该终端的会话，且在切换过程中，终端的接入设备不发生改变。
结合上述第一方面或第二方面或第三方面，作为一种实现，来自源移动管理网元的终端的上下文中包括终端的会话上下文，其中，终端的会话上下文是源移动管理网元从源中间会话管理网元中获取的，其中，终端的会话上下文中包括终端的接入设备的下行路径信息以及终端的会话对应的锚点用户面网元的上行路径信息，锚点用户面网元的上行路径信息用于建立从目标中间用户面网元到锚点用户面功能网元的上行路径，接入设备的下行路径信息用于建立从目标中间用户面网元到接入设备的下行路径；相应的，该会话建立请求中还携带终端的会话上下文。
结合上述第一方面或第二方面或第三方面，作为一种实现，本申请实施例公开的切换方法还可以包括：目标移动管理网元确定需要为该终端选择目标中间会话管理网元。
作为一种实现，目标移动管理网元确定需要为该终端选择目标中间会话管理网元，包括：目标移动管理网元接收来自源移动管理网元的终端的会话对应的锚点控制面网元的信息或源中间会话管理网元的信息中的至少一个；目标移动管理网元根据锚点控制面网元的信息或源中间会话管理网元的信息中的至少一个，确定需要为该终端选择目标中间会话管理网元。
作为一种实现，目标移动管理网元确定需要为该终端选择目标中间会话管理网元，包括：目标移动管理网元接收来自源移动管理网元的第三指示信息，该第三指示信息用于指示存在源中间会话管理网元；或者，该第三指示信息用于指示需要为终端重新选择中间会话管理网元；目标移动管理网元根据第三指示信息，为终端选择目标中间会话管理网元。
上述切换方法中，例如，目标移动管理网元的操作可参考图5至图7中目标AMF网元的操作及上述相关文字说明，在此不再赘述。
此外，第四方面，本申请实施例还公开了一种切换方法，包括：源移动管理网元接收来自终端的注册请求；源移动管理网元根据该注册请求，为终端选择目标移动管理网元；源移动管理网元向目标移动管理网元发送第一指示信息和终端的上下文，该第一指示信息用于指示当前注册流程发生在连接态；或者，该第一指示信息用于指示该终端的上下文存储在源移动管理网元中；或者，该第一指示信息用于指示不需要根据终端的GUTI获取该终端的上下文；源移动管理网元接收来自目标移动管理网元的注册完成通知，该注册完成通知用于通知源移动管理网元该终端的上下文不再有效或者终端已经注册到目标移动管理网 元。
作为一种实现，该第一指示信息包括源移动管理网元的信息。
上述切换方法中，例如，源移动管理网元的操作可参考图5中源AMF网元的操作及上述相关文字说明，在此不再赘述。
此外，第五方面，本申请实施例还公开了一种切换方法，包括：源移动管理网元接收来自终端的注册请求；源移动管理网元根据注册请求，为终端选择目标移动管理网元；源移动管理网元向终端的接入设备发送重路由请求，该重路由请求携带源移动管理网元的信息和该注册请求，由接入设备向目标移动管理网元发送该注册请求和该源移动管理网元的信息；源移动管理网元接收目标移动管理网元根据源移动管理网元的信息发送的上下文请求，该上下文请求用于请求该终端的上下文；源移动管理网元向目标移动管理网元发送该终端的上下文；在注册完成之后，源移动管理网元接收目标移动管理网元根据源移动管理网元的信息发送的注册完成通知，该注册完成通知用于通知源移动管理网元该终端的上下文不再有效或者终端已经注册到目标移动管理网元。
上述切换方法中，例如，源移动管理网元的操作可参考图6中源AMF网元的操作及上述相关文字说明，在此不再赘述。
结合上述第四方面或第五方面，作为一种实现，在源移动管理网元接收来自终端的注册请求之后，本申请实施例公开的切换方法还可以包括：源移动管理网元向源中间会话管理网元发送会话上下文请求，该会话上下文请求用于请求该终端的会话上下文；源移动管理网元接收来自源中间会话管理网元的该终端的会话上下文；相应的，终端的上下文中包括终端的会话上下文，其中，该终端的会话上下文中包括终端的接入设备的下行路径信息以及终端的会话对应的锚点用户面网元的上行路径信息，锚点用户面网元的上行路径信息用于建立从目标中间用户面网元到锚点用户面功能网元的上行路径，接入设备的下行路径信息用于建立从目标中间用户面网元到接入设备的下行路径。
上述切换方法中，例如，源移动管理网元的操作可参考图5或图6中源AMF网元的操作及上述相关文字说明，在此不再赘述。
此外，本申请实施例还公开了一种切换方法，包括：目标中间会话管理网元接收来自目标移动管理网元的会话建立请求，该会话建立请求携带第二指示信息，第二指示信息用于指示该会话建立请求用于切换该终端的会话，且在切换过程中，该终端的接入设备不发生改变；目标中间会话管理网元根据第二指示信息，从源中间会话管理网元中获取该终端的会话上下文，其中，该终端的会话上下文中包括终端的接入设备的下行路径信息以及终端的会话对应的锚点用户面网元的上行路径信息，锚点用户面网元的上行路径信息用于建立从目标中间用户面网元到锚点用户面功能网元的上行路径，接入设备的下行路径信息用于建立从目标中间用户面网元到接入设备的下行路径。
作为一种实现，目标中间会话管理网元根据第二指示信息，从源中间会话管理网元中获取终端的会话上下文，包括：目标中间会话管理网元根据第二指示信息，向源中间会话管理网元发送会话上下文请求，该会话上下文请求携带第四指示信息，用于请求包括接入设备的下行路径信息的终端的会话上下文；目标中间会话管理网元接收来自源中间会话管理网元的所述终端的会话上下文。
作为一种实现，本申请实施例公开的切换方法还可以包括：目标中间会话管理网元向接入设备发送目标中间用户面网元的上行路径信息，其中，目标中间用户面网元的上行路径信息用于建立从接入设备到目标中间用户面网元的上行路径。
上述切换方法中，例如，目标中间会话管理网元的操作可参考图5至图7中目标I-SMF网元的操作及上述相关文字说明，在此不再赘述。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，上述源移动管理网元、目标移动管理网元或目标中间会话管理网元为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对源移动管理网元、目标移动管理网元或目标中间会话管理网元进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
比如，以采用集成的方式划分各个功能模块的情况下，图8示出了一种目标移动管理网元80的结构示意图。该目标移动管理网元80包括：接收模块801和发送模块802。
一种可能的实现方式中，接收模块801，用于接收来自源移动管理网元的第一指示信息和终端的上下文，该第一指示信息用于指示当前注册流程发生在连接态；或者，该第一指示信息用于指示终端的上下文存储在源移动管理网元中；或者，该第一指示信息用于指示不需要根据终端的GUTI获取终端的上下文。发送模块802，用于根据第一指示信息，在注册完成之后，向源移动管理网元发送注册完成通知，该注册完成通知用于通知源移动管理网元终端的上下文不再有效或者终端已经注册到目标移动管理网元。
另一种可能的实现方式中，接收模块801，用于接收来自终端的接入设备的注册请求和源移动管理网元的信息。发送模块802，用于根据源移动管理网元的信息，向源移动管理网元发送上下文请求，该上下文请求用于请求终端的上下文。接收模块801，还用于接收来自源移动管理网元的终端的上下文。发送模块802，还用于根据源移动管理网元的信息，在注册完成之后，向源移动管理网元发送注册完成通知，该注册完成通知用于通知源移动管理网元终端的上下文不再有效或者终端已经注册到目标移动管理网元。
在上述两种可能的实现方式中，可选的，发送模块802，还用于向终端的接入设备发送目标移动管理网元为终端分配的NGAP终端标识和GUAMI，其中，该NGAP终端标识用于更新接入设备上终端对应的NGAP终端标识，该GUAMI用于更新接入设备上终端对应的GUAMI。
再一种可能的实现方式中，接收模块801，用于接收来自源移动管理网元的第一指示信息和终端的上下文，第一指示信息用于指示当前切换流程中终端的接入设备不发生改变。发送模块802，用于根据第一指示信息，向接入设备发送目标移动管理网元为终端分配的NGAP终端标识和GUAMI，其中，该NGAP终端标识用于更新接入设备上终端对应的NGAP终 端标识，该GUAMI用于更新接入设备上终端对应的GUAMI。
在上述三种可能的实现方式中，可选的，发送模块802，还用于向接入设备发送更新后的终端的安全上下文，该更新后的终端的安全上下文用于更新接入设备上终端的安全上下文。
在上述三种可能的实现方式中，可选的，如图8所示，目标移动管理网元80还包括处理模块803。处理模块803，用于为终端选择目标中间会话管理网元。发送模块802，还用于向目标中间会话管理网元发送会话建立请求，该会话建立请求携带第二指示信息，第二指示信息用于指示会话建立请求用于切换终端的会话，且在切换过程中，终端的接入设备不发生改变。
可选的，处理模块803，还用于确定需要为终端选择目标中间会话管理网元。
作为一种实现，处理模块803用于确定需要为终端选择目标中间会话管理网元，包括：用于接收来自源移动管理网元的终端的会话对应的锚点控制面网元的信息或源中间会话管理网元的信息中的至少一个；根据锚点控制面网元的信息或源中间会话管理网元的信息中的至少一个，确定需要为终端选择目标中间会话管理网元；
作为另一种实现，处理模块803用于确定需要为终端选择目标中间会话管理网元，包括：用于接收来自源移动管理网元的第三指示信息，第三指示信息用于指示存在源中间会话管理网元；或者，第三指示信息用于指示需要为终端重新选择中间会话管理网元；根据第三指示信息，为终端选择目标中间会话管理网元。
可选的，又一种可能的实现方式中，本申请实施例中，接收模块801，用于接收来自源移动管理网元的第一指示信息和终端的上下文，该第一指示信息用于指示目标移动管理网元在后续流程中不发送注册完成通知；处理模块802，用于根据该第一指示信息，确定不发送注册完成通知。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该目标移动管理网元80以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到该目标移动管理网元80可以采用图4所示的形式。
比如，图4中的处理器401可以通过调用存储器403中存储的计算机执行指令，使得目标移动管理网元80执行上述方法实施例中的切换方法。
具体的，图8中的接收模块801、发送模块802和处理模块803的功能/实现过程可以通过图4中的处理器401调用存储器403中存储的计算机执行指令来实现。或者，图8中的接收模块801、发送模块802的功能/实现过程可以通过图4中的通信接口404来实现；图8中处理模块803的功能/实现过程可以通过图4中的处理器401调用存储器403中存储的计算机执行指令来实现。
由于本实施例提供的目标移动管理网元80可执行上述的切换方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
可选的，本申请实施例还提供了一种芯片***，该芯片***包括处理器，用于支持目 标移动管理网元80实现上述切换方法，例如为终端分配NGAP终端标识和GUAMI。在一种可能的设计中，该芯片***还包括存储器。该存储器，用于保存目标移动管理网元80必要的程序指令和数据。当然，存储器也可以不在芯片***中。该芯片***，可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
或者，比如，以采用集成的方式划分各个功能模块的情况下，图9示出了一种源移动管理网元90的结构示意图。该源移动管理网元90包括：收发模块901和处理模块902。
一种可能的实现方式中，收发模块901，用于接收来自终端的注册请求。处理模块902，用于根据注册请求，为终端选择目标移动管理网元。收发模块901，还用于向目标移动管理网元发送第一指示信息和终端的上下文，第一指示信息用于指示当前注册流程发生在连接态；或者，第一指示信息用于指示终端的上下文存储在源移动管理网元中；或者，第一指示信息用于指示不需要根据终端的GUTI获取终端的上下文。收发模块901，还用于接收来自目标移动管理网元的注册完成通知，注册完成通知用于通知源移动管理网元终端的上下文不再有效或者终端已经注册到目标移动管理网元。
另一种可能的实现方式中，收发模块901，用于接收来自终端的注册请求。处理模块902，用于根据注册请求，为终端选择目标移动管理网元。收发模块901，还用于向终端的接入设备发送重路由请求，该重路由请求携带源移动管理网元的信息和注册请求，由接入设备向目标移动管理网元发送注册请求和源移动管理网元的信息；收发模块901，还用于接收目标移动管理网元根据源移动管理网元的信息发送的上下文请求，该上下文请求用于请求终端的上下文。收发模块901，还用于向目标移动管理网元发送终端的上下文；收发模块901，还用于在注册完成之后，接收目标移动管理网元根据源移动管理网元的信息发送的注册完成通知，注册完成通知用于通知源移动管理网元终端的上下文不再有效或者终端已经注册到目标移动管理网元。
在上述两种可能的实现方式中，可选的，收发模块901，还用于向源中间会话管理网元发送会话上下文请求，该会话上下文请求用于请求终端的会话上下文；收发模块901，还用于接收来自源中间会话管理网元的终端的会话上下文；相应的，终端的上下文中包括终端的会话上下文，其中，终端的会话上下文中包括终端的接入设备的下行路径信息以及终端的会话对应的锚点用户面网元的上行路径信息，锚点用户面网元的上行路径信息用于建立从目标中间用户面网元到锚点用户面功能网元的上行路径，接入设备的下行路径信息用于建立从目标中间用户面网元到接入设备的下行路径。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该源移动管理网元90以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到该源移动管理网元90可以采用图4所示的形式。
比如，图4中的处理器401可以通过调用存储器403中存储的计算机执行指令，使得源移动管理网元90执行上述方法实施例中的切换方法。
具体的，图9中的收发模块901和处理模块902的功能/实现过程可以通过图4中的处 理器401调用存储器403中存储的计算机执行指令来实现。或者，图9中的收发模块901的功能/实现过程可以通过图4中的通信接口404来实现；图9中处理模块902的功能/实现过程可以通过图4中的处理器401调用存储器403中存储的计算机执行指令来实现。
由于本实施例提供的源移动管理网元90可执行上述的切换方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
可选的，本申请实施例还提供了一种芯片***，该芯片***包括处理器，用于支持源移动管理网元90实现上述切换方法，例如根据注册请求，为终端选择目标移动管理网元。在一种可能的设计中，该芯片***还包括存储器。该存储器，用于保存源移动管理网元90必要的程序指令和数据。当然，存储器也可以不在芯片***中。该芯片***，可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
或者，比如，以采用集成的方式划分各个功能模块的情况下，图10示出了一种目标中间会话管理网元100的结构示意图。该目标中间会话管理网元100包括：收发模块1001和处理模块1002。其中，收发模块1001，用于接收来自目标移动管理网元的会话建立请求，该会话建立请求携带第二指示信息，该第二指示信息用于指示会话建立请求用于切换终端的会话，且在切换过程中，终端的接入设备不发生改变；处理模块1002，用于根据第二指示信息，从源中间会话管理网元中获取终端的会话上下文，其中，终端的会话上下文中包括终端的接入设备的下行路径信息以及终端的会话对应的锚点用户面网元的上行路径信息，锚点用户面网元的上行路径信息用于建立从目标中间用户面网元到锚点用户面功能网元的上行路径，接入设备的下行路径信息用于建立从目标中间用户面网元到接入设备的下行路径。
可选的，处理模块1002具体用于：根据第二指示信息，向源中间会话管理网元发送会话上下文请求，该会话上下文请求携带第四指示信息，用于请求包括接入设备的下行路径信息的终端的会话上下文；接收来自源中间会话管理网元的终端的会话上下文。
可选的，收发模块1001，还用于向接入设备发送目标中间用户面网元的上行路径信息，其中，目标中间用户面网元的上行路径信息用于建立从接入设备到目标中间用户面网元的上行路径。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该目标中间会话管理网元100以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到该目标中间会话管理网元100可以采用图4所示的形式。
比如，图4中的处理器401可以通过调用存储器403中存储的计算机执行指令，使得目标中间会话管理网元100执行上述方法实施例中的切换方法。
具体的，图10中的收发模块1001和处理模块1002的功能/实现过程可以通过图4中的处理器401调用存储器403中存储的计算机执行指令来实现。或者，图10中的收发模块1001的功能/实现过程可以通过图4中的通信接口404来实现；图10中处理模块1002的功能/实现过程可以通过图4中的处理器401调用存储器403中存储的计算机执行指令来实现。
由于本实施例提供的目标中间会话管理网元100可执行上述的切换方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
可选的，本申请实施例还提供了一种芯片***，该芯片***包括处理器，用于支持目标中间会话管理网元100实现上述切换方法，例如根据第二指示信息，从源中间会话管理网元中获取终端的会话上下文。在一种可能的设计中，该芯片***还包括存储器。该存储器，用于保存目标中间会话管理网元100必要的程序指令和数据。当然，存储器也可以不在芯片***中。该芯片***，可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (40)

  1. 一种切换方法，其特征在于，所述方法包括：
    目标移动管理网元接收来自源移动管理网元的第一指示信息和终端的上下文，所述第一指示信息用于指示当前注册流程发生在连接态；或者，所述第一指示信息用于指示所述终端的上下文存储在所述源移动管理网元中；或者，所述第一指示信息用于指示不需要根据所述终端的全球唯一临时标识GUTI获取所述终端的上下文；
    所述目标移动管理网元根据所述第一指示信息，在注册完成之后，向所述源移动管理网元发送注册完成通知，所述注册完成通知用于通知所述源移动管理网元所述终端的上下文不再有效或者所述终端已经注册到所述目标移动管理网元。
  2. 根据权利要求1所述的方法，其特征在于，所述第一指示信息包括所述源移动管理网元的信息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述目标移动管理网元向所述终端的接入设备发送所述目标移动管理网元为所述终端分配的下一代应用协议NGAP终端标识和全球移动管理网元标识GUAMI，其中，所述NGAP终端标识用于更新所述接入设备上所述终端对应的NGAP终端标识，所述GUAMI用于更新所述接入设备上所述终端对应的GUAMI。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述方法还包括：
    所述目标移动管理网元向所述终端的接入设备发送更新后的所述终端的安全上下文，所述更新后的所述终端的安全上下文用于更新所述接入设备上所述终端的安全上下文。
  5. 根据权利要求1-4任一项所述的方法，其特征在于，所述方法还包括：
    所述目标移动管理网元为所述终端选择目标中间会话管理网元；
    所述目标移动管理网元向所述目标中间会话管理网元发送会话建立请求，所述会话建立请求携带第二指示信息，所述第二指示信息用于指示所述会话建立请求用于切换所述终端的会话，且在切换过程中，所述终端的接入设备不发生改变。
  6. 根据权利要求5所述的方法，其特征在于，所述来自源移动管理网元的终端的上下文中包括所述终端的会话上下文，其中，所述终端的会话上下文是所述源移动管理网元从源中间会话管理网元中获取的，其中，所述终端的会话上下文中包括所述终端的接入设备的下行路径信息以及所述终端的会话对应的锚点用户面网元的上行路径信息，所述锚点用户面网元的上行路径信息用于建立从所述目标中间用户面网元到所述锚点用户面功能网元的上行路径，所述接入设备的下行路径信息用于建立从所述目标中间用户面网元到所述接入设备的下行路径；
    相应的，所述会话建立请求中还携带所述终端的会话上下文。
  7. 根据权利要求1-6任意一项所述的方法，其特征在于，所述方法还包括：
    所述目标移动管理网元确定需要为所述终端选择目标中间会话管理网元。
  8. 根据权利要求7所述的方法，其特征在于，所述目标移动管理网元确定需要为所述终端选择目标中间会话管理网元，包括：
    所述目标移动管理网元接收来自所述源移动管理网元的所述终端的会话对应的锚点控制面网元的信息或源中间会话管理网元的信息中的至少一个；
    所述目标移动管理网元根据所述锚点控制面网元的信息或所述源中间会话管理网元的信息中的至少一个，确定需要为所述终端选择目标中间会话管理网元；
    或者，所述目标移动管理网元确定需要为所述终端选择目标中间会话管理网元，包括：
    所述目标移动管理网元接收来自所述源移动管理网元的第三指示信息，所述第三指示信息用于指示存在所述源中间会话管理网元；或者，所述第三指示信息用于指示需要为所述终端重新选择中间会话管理网元；所述目标移动管理网元根据所述第三指示信息，为所述终端选择所述目标中间会话管理网元。
  9. 一种切换方法，其特征在于，所述方法包括：
    源移动管理网元接收来自终端的注册请求；
    所述源移动管理网元根据所述注册请求，为所述终端选择目标移动管理网元；
    所述源移动管理网元向所述目标移动管理网元发送第一指示信息和终端的上下文，所述第一指示信息用于指示当前注册流程发生在连接态；或者，所述第一指示信息用于指示所述终端的上下文存储在所述源移动管理网元中；或者，所述第一指示信息用于指示不需要根据所述终端的全球唯一临时标识GUTI获取所述终端的上下文；
    所述源移动管理网元接收来自所述目标移动管理网元的注册完成通知，所述注册完成通知用于通知所述源移动管理网元所述终端的上下文不再有效或者所述终端已经注册到所述目标移动管理网元。
  10. 根据权利要求9所述的方法，其特征在于，所述第一指示信息包括所述源移动管理网元的信息。
  11. 根据权利要求9或10所述的方法，其特征在于，在所述源移动管理网元接收来自终端的注册请求之后，所述方法还包括：
    所述源移动管理网元向源中间会话管理网元发送会话上下文请求，所述会话上下文请求用于请求所述终端的会话上下文；
    所述源移动管理网元接收来自所述源中间会话管理网元的所述终端的会话上下文；
    相应的，所述终端的上下文中包括所述终端的会话上下文，其中，所述终端的会话上下文中包括所述终端的接入设备的下行路径信息以及所述终端的会话对应的锚点用户面网元的上行路径信息，所述锚点用户面网元的上行路径信息用于建立从目标中间用户面网元到所述锚点用户面功能网元的上行路径，所述接入设备的下行路径信息用于建立从所述目标中间用户面网元到所述接入设备的下行路径。
  12. 一种切换方法，其特征在于，所述方法包括：
    目标中间会话管理网元接收来自目标移动管理网元的会话建立请求，所述会话建立请求携带第二指示信息，所述第二指示信息用于指示所述会话建立请求用于切换终端的会话，且在切换过程中，所述终端的接入设备不发生改变；
    所述目标会话管理网元根据所述第二指示信息，从源中间会话管理网元中获取所述终端的会话上下文，其中，所述终端的会话上下文中包括所述终端的接入设备的下行路 径信息以及所述终端的会话对应的锚点用户面网元的上行路径信息，所述锚点用户面网元的上行路径信息用于建立从所述目标中间用户面网元到所述锚点用户面功能网元的上行路径，所述接入设备的下行路径信息用于建立从所述目标中间用户面网元到所述接入设备的下行路径。
  13. 根据权利要求12所述的方法，其特征在于，所述目标中间会话管理网元根据所述第二指示信息，从源中间会话管理网元中获取所述终端的会话上下文，包括：
    所述目标中间会话管理网元根据所述第二指示信息，向所述源中间会话管理网元发送会话上下文请求，所述会话上下文请求携带第四指示信息，用于请求包括所述接入设备的下行路径信息的所述终端的上下文；
    所述目标中间会话管理网元接收来自所述源中间会话管理网元的所述终端的上下文。
  14. 根据权利要求12或13所述的方法，其特征在于，所述方法还包括：
    所述目标中间会话管理网元向所述接入设备发送目标中间用户面网元的上行路径信息，其中，所述目标中间用户面网元的上行路径信息用于建立从所述接入设备到所述目标中间用户面网元的上行路径。
  15. 一种切换方法，其特征在于，所述方法包括：
    目标移动管理网元接收来自终端的接入设备的注册请求和源移动管理网元的信息；
    所述目标移动管理网元根据所述源移动管理网元的信息，向所述源移动管理网元发送上下文请求，所述上下文请求用于请求所述终端的上下文；
    所述目标移动管理网元接收来自所述源移动管理网元的所述终端的上下文；
    所述目标移动管理网元根据所述源移动管理网元的信息，在注册完成之后，向所述源移动管理网元发送注册完成通知，所述注册完成通知用于通知所述源移动管理网元所述终端的上下文不再有效或者所述终端已经注册到所述目标移动管理网元。
  16. 一种切换方法，其特征在于，所述方法包括：
    源移动管理网元接收来自终端的注册请求；
    所述源移动管理网元根据所述注册请求，为所述终端选择目标移动管理网元；
    所述源移动管理网元向所述终端的接入设备发送重路由请求，所述重路由请求携带所述源移动管理网元的信息和所述注册请求，由所述接入设备向所述目标移动管理网元发送所述注册请求和所述源移动管理网元的信息；
    所述源移动管理网元接收所述目标移动管理网元根据所述源移动管理网元的信息发送的上下文请求，所述上下文请求用于请求所述终端的上下文；
    所述源移动管理网元向所述目标移动管理网元发送所述终端的上下文；
    在注册完成之后，所述源移动管理网元接收所述目标移动管理网元根据所述源移动管理网元的信息发送的注册完成通知，所述注册完成通知用于通知所述源移动管理网元所述终端的上下文不再有效或者所述终端已经注册到所述目标移动管理网元。
  17. 一种切换方法，其特征在于，所述方法包括：
    目标移动管理网元接收来自源移动管理网元的第一指示信息和终端的上下文，所述第一指示信息用于指示当前切换流程中所述终端的接入设备不发生改变；
    所述目标移动管理网元根据所述第一指示信息，向所述接入设备发送所述目标移动管理网元为所述终端分配的下一代应用协议NGAP终端标识和全球移动管理网元标识GUAMI，其中，所述NGAP终端标识用于更新所述接入设备上所述终端对应的NGAP终端标识，所述GUAMI用于更新所述接入设备上所述终端对应的GUAMI。
  18. 一种目标移动管理网元，其特征在于，所述目标移动管理网元包括接收模块和发送模块；
    所述接收模块，用于接收来自源移动管理网元的第一指示信息和终端的上下文，所述第一指示信息用于指示当前注册流程发生在连接态；或者，所述第一指示信息用于指示所述终端的上下文存储在所述源移动管理网元中；或者，所述第一指示信息用于指示不需要根据所述终端的全球唯一临时标识GUTI获取所述终端的上下文；
    所述发送模块，用于根据所述第一指示信息，在注册完成之后，向所述源移动管理网元发送注册完成通知，所述注册完成通知用于通知所述源移动管理网元所述终端的上下文不再有效或者所述终端已经注册到所述目标移动管理网元。
  19. 根据权利要求18所述的目标移动管理网元，其特征在于，
    所述发送模块，还用于向所述终端的接入设备发送所述目标移动管理网元为所述终端分配的下一代应用协议NGAP终端标识和全球移动管理网元标识GUAMI，其中，所述NGAP终端标识用于更新所述接入设备上所述终端对应的NGAP终端标识，所述GUAMI用于更新所述接入设备上所述终端对应的GUAMI。
  20. 根据权利要求18或19所述的目标移动管理网元，其特征在于，
    所述发送模块，还用于向所述终端的接入设备发送更新后的所述终端的安全上下文，所述更新后的所述终端的安全上下文用于更新所述接入设备上所述终端的安全上下文。
  21. 根据权利要求18-20任一项所述的目标移动管理网元，其特征在于，所述目标移动管理网元还包括处理模块；
    所述处理模块，用于为所述终端选择目标中间会话管理网元；
    所述发送模块，还用于向所述目标中间会话管理网元发送会话建立请求，所述会话建立请求携带第二指示信息，所述第二指示信息用于指示所述会话建立请求用于切换所述终端的会话，且在切换过程中，所述终端的接入设备不发生改变。
  22. 根据权利要求21所述的目标移动管理网元，其特征在于，
    所述处理模块，还用于确定需要为所述终端选择目标中间会话管理网元。
  23. 根据权利要求22所述的目标移动管理网元，其特征在于，所述处理模块用于确定需要为所述终端选择目标中间会话管理网元，包括：用于接收来自所述源移动管理网元的所述终端的会话对应的锚点控制面网元的信息或源中间会话管理网元的信息中的至少一个；根据所述锚点控制面网元的信息或所述源中间会话管理网元的信息中的至少一个，确定需要为所述终端选择目标中间会话管理网元；
    或者，所述处理模块用于确定需要为所述终端选择目标中间会话管理网元，包括：用于接收来自所述源移动管理网元的第三指示信息，所述第三指示信息用于指示存在所述源中间会话管理网元；或者，所述第三指示信息用于指示需要为所述终端重新选择中间会话管理网元；根据所述第三指示信息，为所述终端选择所述目标中间会话管理网元。
  24. 一种源移动管理网元，其特征在于，所述源移动管理网元包括：收发模块和处理模块；
    所述收发模块，用于接收来自终端的注册请求；
    所述处理模块，用于根据所述注册请求，为所述终端选择目标移动管理网元；
    所述收发模块，还用于向所述目标移动管理网元发送第一指示信息和终端的上下文，所述第一指示信息用于指示当前注册流程发生在连接态；或者，所述第一指示信息用于指示所述终端的上下文存储在所述源移动管理网元中；或者，所述第一指示信息用于指示不需要根据所述终端的全球唯一临时标识GUTI获取所述终端的上下文；
    所述收发模块，还用于接收来自所述目标移动管理网元的注册完成通知，所述注册完成通知用于通知所述源移动管理网元所述终端的上下文不再有效或者所述终端已经注册到所述目标移动管理网元。
  25. 根据权利要求24所述的源移动管理网元，其特征在于，
    所述收发模块，还用于向源中间会话管理网元发送会话上下文请求，所述会话上下文请求用于请求所述终端的会话上下文；
    所述收发模块，还用于接收来自所述源中间会话管理网元的所述终端的会话上下文；
    相应的，所述终端的上下文中包括所述终端的会话上下文，其中，所述终端的会话上下文中包括所述终端的接入设备的下行路径信息以及所述终端的会话对应的锚点用户面网元的上行路径信息，所述锚点用户面网元的上行路径信息用于建立从目标中间用户面网元到所述锚点用户面功能网元的上行路径，所述接入设备的下行路径信息用于建立从所述目标中间用户面网元到所述接入设备的下行路径。
  26. 一种目标中间会话管理网元，其特征在于，所述目标中间会话管理网元包括：收发模块和处理模块；
    所述收发模块，用于接收来自目标移动管理网元的会话建立请求，所述会话建立请求携带第二指示信息，所述第二指示信息用于指示所述会话建立请求用于切换终端的会话，且在切换过程中，所述终端的接入设备不发生改变；
    所述处理模块，用于根据所述第二指示信息，从源中间会话管理网元中获取所述终端的会话上下文，其中，所述终端的会话上下文中包括所述终端的接入设备的下行路径信息以及所述终端的会话对应的锚点用户面网元的上行路径信息，所述锚点用户面网元的上行路径信息用于建立从所述目标中间用户面网元到所述锚点用户面功能网元的上行路径，所述接入设备的下行路径信息用于建立从所述目标中间用户面网元到所述接入设备的下行路径。
  27. 根据权利要求26所述的目标中间会话管理网元，其特征在于，所述处理模块具体用于：
    根据所述第二指示信息，向所述源中间会话管理网元发送会话上下文请求，所述会话上下文请求携带第四指示信息，用于请求包括所述接入设备的下行路径信息的所述终端的会话上下文；接收来自所述源中间会话管理网元的所述终端的会话上下文。
  28. 根据权利要求26或27所述的目标中间会话管理网元，其特征在于，
    所述收发模块，还用于向所述接入设备发送目标中间用户面网元的上行路径信息， 其中，所述目标中间用户面网元的上行路径信息用于建立从所述接入设备到所述目标中间用户面网元的上行路径。
  29. 一种目标移动管理网元，其特征在于，所述目标移动管理网元包括：接收模块和发送模块；
    所述接收模块，用于接收来自终端的接入设备的注册请求和源移动管理网元的信息；
    所述发送模块，用于根据所述源移动管理网元的信息，向所述源移动管理网元发送上下文请求，所述上下文请求用于请求所述终端的上下文；
    所述接收模块，还用于接收来自所述源移动管理网元的所述终端的上下文；
    所述发送模块，还用于根据所述源移动管理网元的信息，在注册完成之后，向所述源移动管理网元发送注册完成通知，所述注册完成通知用于通知所述源移动管理网元所述终端的上下文不再有效或者所述终端已经注册到所述目标移动管理网元。
  30. 一种源移动管理网元，其特征在于，所述源移动管理网元包括：收发模块和处理模块；
    所述收发模块，用于接收来自终端的注册请求；
    所述处理模块，用于根据所述注册请求，为所述终端选择目标移动管理网元；
    所述收发模块，还用于向所述终端的接入设备发送重路由请求，所述重路由请求携带所述源移动管理网元的信息和所述注册请求，由所述接入设备向所述目标移动管理网元发送所述注册请求和所述源移动管理网元的信息；
    所述收发模块，还用于接收所述目标移动管理网元根据所述源移动管理网元的信息发送的上下文请求，所述上下文请求用于请求所述终端的上下文；
    所述收发模块，还用于向所述目标移动管理网元发送所述终端的上下文；
    所述收发模块，还用于在注册完成之后，接收所述目标移动管理网元根据所述源移动管理网元的信息发送的注册完成通知，所述注册完成通知用于通知所述源移动管理网元所述终端的上下文不再有效或者所述终端已经注册到所述目标移动管理网元。
  31. 一种目标移动管理网元，其特征在于，所述目标移动管理网元包括：接收模块和发送模块；
    所述接收模块，用于接收来自源移动管理网元的第一指示信息和终端的上下文，所述第一指示信息用于指示当前切换流程中所述终端的接入设备不发生改变；
    所述发送模块，用于根据所述第一指示信息，向所述接入设备发送所述目标移动管理网元为所述终端分配的下一代应用协议NGAP终端标识和全球移动管理网元标识GUAMI，其中，所述NGAP终端标识用于更新所述接入设备上所述终端对应的NGAP终端标识，所述GUAMI用于更新所述接入设备上所述终端对应的GUAMI。
  32. 一种切换***，其特征在于，所述切换***包括如权利要求18-23任一项所述的目标移动管理网元，以及如权利要求24或25所述的源移动管理网元；或者，所述切换***包括如权利要求29所述的目标移动管理网元，以及如权利要求30所述的源移动管理网元；或者，所述切换***包括源移动管理网元，以及如权利要求31所述的目标移动管理网元，其中，所述源移动管理网元，用于为所述终端选择所述目标移动管理网元，并向所述目标移动管理网元发送所述第一指示信息和所述终端的上下文。
  33. 根据权利要求32所述的切换***，其特征在于，所述切换***还包括如权利要求26-28任一项所述的目标中间会话管理网元。
  34. 一种目标移动管理网元，其特征在于，包括：处理器和存储器；所述存储器用于存储计算机执行指令，当所述目标移动管理网元运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述目标移动管理网元执行如权利要求1-8任一项，或权利要求15，或权利要求17所述的切换方法。
  35. 一种源移动管理网元，其特征在于，包括：处理器和存储器；所述存储器用于存储计算机执行指令，当所述源移动管理网元运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述源移动管理网元执行如权利要求9-11任一项，或权利要求16所述的切换方法。
  36. 一种目标中间会话管理网元，其特征在于，包括：处理器和存储器；所述存储器用于存储计算机执行指令，当所述目标中间会话管理网元运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述目标中间会话管理网元执行如权利要求12-14任一所述的切换方法。
  37. 一种处理器，其特征在于，用于执行如权利要求1-8任一项，或权利要求9-11任一项，或权利要求12-14任一项，或权利要求15，或权利要求16，或权利要求17所述的切换方法。
  38. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行如权利要求1-8任一项，或权利要求9-11任一项，或权利要求12-14任一项，或权利要求15，或权利要求16，或权利要求17所述的切换方法。
  39. 一种计算机程序产品，其特征在于，所述计算机程序产品中存储有指令，当其在计算机上运行时，使得计算机可以执行如权利要求1-8任一项，或权利要求9-11任一项，或权利要求12-14任一项，或权利要求15，或权利要求16，或权利要求17所述的切换方法。
  40. 一种用来执行权利要求1-8任一项，或权利要求9-11任一项，或权利要求12-14任一项，或权利要求15，或权利要求16，或权利要求17所述的切换方法的装置。
PCT/CN2019/083340 2018-05-04 2019-04-19 切换方法、设备及*** WO2019210779A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201810422132 2018-05-04
CN201810422132.1 2018-05-04
CN201910121387.9 2019-02-13
CN201910121387.9A CN110446233B (zh) 2018-05-04 2019-02-13 切换方法、设备及***

Publications (1)

Publication Number Publication Date
WO2019210779A1 true WO2019210779A1 (zh) 2019-11-07

Family

ID=68386966

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/083340 WO2019210779A1 (zh) 2018-05-04 2019-04-19 切换方法、设备及***

Country Status (1)

Country Link
WO (1) WO2019210779A1 (zh)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107277883A (zh) * 2016-04-08 2017-10-20 电信科学技术研究院 在多网络切片的网络中路由消息的方法、设备及***

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107277883A (zh) * 2016-04-08 2017-10-20 电信科学技术研究院 在多网络切片的网络中路由消息的方法、设备及***

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3GPP TS 23.502 V15.1.0", 3RD GENERATION PARTNERSHIP PROJECT; TECHNICAL SPECIFICATION GROUP SERVICES AND SYSTEM ASPECTS, 27 March 2018 (2018-03-27), XP055098453 *
HUAWEI ET AL.: "Inter I-SMF Mobility", SA WG2 MEETING #127, 10 April 2018 (2018-04-10), pages - S2-183455, XP051437773 *

Similar Documents

Publication Publication Date Title
US11870856B2 (en) Session establishment method and apparatus
CN110248352B (zh) 会话管理方法、设备及计算机可读存储介质
CN110049072B (zh) 会话建立方法及设备
CN113286342B (zh) 切换方法、设备及***
KR102313165B1 (ko) 데이터 송신 방법, 디바이스 및 시스템
JP2022177216A (ja) 通信システム間移動方法、デバイス及びシステム
CN110049485B (zh) 一种配置ue的策略的方法、装置和***
CN110035423B (zh) 会话管理方法、设备及***
WO2019137125A1 (zh) 会话管理方法、设备及***
WO2019120073A1 (zh) 数据传输方法、设备及***
WO2019223702A1 (zh) 管理pdu会话的方法、装置和***
WO2019184723A1 (zh) 策略和计费控制规则获取方法、装置及***
WO2020249032A1 (zh) 通信方法及装置
CN110266826B (zh) 地址管理方法、设备及***
US11160004B2 (en) Handover method, device, and system
WO2019137521A1 (zh) 会话管理方法、设备及***
WO2019210779A1 (zh) 切换方法、设备及***
CN110856273B (zh) 会话管理方法、设备及***

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19796799

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19796799

Country of ref document: EP

Kind code of ref document: A1