WO2019015627A1 - 切换方法、设备及系统 - Google Patents

切换方法、设备及系统 Download PDF

Info

Publication number
WO2019015627A1
WO2019015627A1 PCT/CN2018/096203 CN2018096203W WO2019015627A1 WO 2019015627 A1 WO2019015627 A1 WO 2019015627A1 CN 2018096203 W CN2018096203 W CN 2018096203W WO 2019015627 A1 WO2019015627 A1 WO 2019015627A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
mobility management
management entity
terminal
target terminal
Prior art date
Application number
PCT/CN2018/096203
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 CN201710953564.0A external-priority patent/CN109429219B/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to BR112020000957-1A priority Critical patent/BR112020000957A2/pt
Priority to EP21184198.6A priority patent/EP3958601A3/en
Priority to EP18835449.2A priority patent/EP3629612B1/en
Priority to KR1020197038557A priority patent/KR102268412B1/ko
Priority to JP2020501165A priority patent/JP7145197B2/ja
Publication of WO2019015627A1 publication Critical patent/WO2019015627A1/zh
Priority to US16/709,362 priority patent/US11160004B2/en
Priority to US17/478,199 priority patent/US11716667B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a handover method, device, and system.
  • an access and mobility management function (AMF) entity determines that the terminal is no longer served
  • the AMF entity sends "not available” to the radio access network (RAN) device. "Indication, the AMF entity is marked as unavailable by the RAN device. In this way, the AMF entity is no longer considered when subsequently selecting an AMF entity.
  • the RAN device releases all next generation (N)2 interfaces (N2 for short) of the terminal served by the AMF entity.
  • the RAN device sends the message related to the terminal to the target AMF entity specified by the AMF entity or the target AMF selected by the RAN device for the terminal. entity.
  • the RAN device cannot send the related message of the terminal to the original AMF. Entity, which causes the current process of the terminal to be interrupted, thus affecting the user experience.
  • the embodiments of the present application provide a handover method, a device, and a system. After the AMF entity determines that the terminal does not provide services for some terminals, the current process of maintaining the progress of some processes in the terminals is not interrupted.
  • the embodiment of the present application provides the following technical solutions:
  • a handover method comprising: a target mobility management entity receiving a message related to a target terminal; the target mobility management entity transmitting a message related to the target terminal to a source mobility management entity currently providing a service for the target terminal .
  • the target terminal related message may be sent to the source mobility management entity, so that the source mobility management entity may continue to provide the terminal Service, so the current flow of the target terminal that keeps the process in progress after the source mobility management entity determines that it is no longer serving the target terminal is not interrupted.
  • the method further includes: the target mobility management entity receiving an identifier list from the source mobility management entity, where the identifier list is a to-be-switched terminal that provides service to the source mobility management entity, currently in progress The identifier of the terminal of the process; the target mobility management entity sends the message related to the target terminal to the source mobility management entity that is currently serving the target terminal, including: the target mobility management entity according to the identifier list The source mobile management entity that provides the service by the target terminal sends a message related to the target terminal.
  • the source mobility management entity sends, to the target to be switched terminal, the identifier list of the terminal that has the ongoing process to the target mobility management entity, and the target mobility management entity receives the target terminal.
  • the target terminal related message is sent to the source mobility management entity, so that the source mobility management entity can continue to provide the terminal with the service, so the source mobility management entity can determine that the target terminal is no longer the target terminal.
  • the service is provided, the current process of the target terminal that keeps the process in progress is not interrupted.
  • the target terminal related message carries an identifier of the target terminal
  • the target mobility management entity sends, according to the identifier list, a message related to the target terminal to a source mobility management entity that currently provides a service for the target terminal, including And if the identifier list includes the identifier of the target terminal, the target mobility management entity sends a message related to the target terminal to a source mobility management entity that currently provides a service for the target terminal.
  • the target terminal related message carries the identifier of the target terminal.
  • the method further includes: the target mobility management entity according to the identifier of the target terminal, and the identifier of the target terminal and the information of the source mobility management entity. Corresponding relationship, determining a source mobility management entity that provides services for the target terminal. Based on the scheme, a source mobility management entity that provides services to the target terminal can be determined.
  • the method further includes: after the target mobility management entity receives the context of the target terminal, the target mobility management deletes a correspondence between the identifier of the target terminal and the information of the source mobility management entity. Based on the scheme, after the target mobility management entity receives the target terminal related message, the target mobility management entity may serve the target terminal instead of transmitting the target terminal related message to the source mobility management entity.
  • the target terminal-related message carries the identifier of the target terminal; the target mobility management entity sends the target terminal-related message to the source mobility management entity that currently provides the service to the target terminal, including: The target mobility management entity searches for the context of the target terminal according to the identifier of the target terminal; if the target mobility management entity does not find the context of the target terminal, the target mobility management entity moves to the source that currently provides the service for the target terminal. The management entity sends a message related to the target terminal.
  • the target mobility management entity After receiving the message related to the target terminal, the target mobility management entity searches for the context of the target terminal according to the identifier of the target terminal carried in the message related to the target terminal; if the context of the target terminal is not found, the source mobility management is performed.
  • the entity sends the message related to the target terminal, so that the source mobility management entity can continue to provide services for the terminal, so the current process of the target terminal in which the process is in progress can be maintained after the source mobility management entity determines that the target terminal is no longer served. Not interrupted.
  • the target terminal related message carries the group identifier of the terminal group where the target terminal is located; the method further includes: the target mobility management entity receiving the context of the at least one terminal from the source mobility management entity, the at least one terminal Included in the context of the at least one terminal group group identifier, wherein the context of each terminal in the context of the at least one terminal includes a group identifier of the terminal group in which the terminal is located; if the target mobility management entity does not find the context of the target terminal And sending, by the target mobility management entity, the target terminal related message to the source mobility management entity that is currently serving the target terminal, including: if the target mobility management entity does not find the context of the target terminal, and the at least one terminal group
  • the group identifier includes a group identifier of a terminal group where the target terminal is located, and the target mobility management entity sends a message related to the target terminal to a source mobility management entity that currently provides a service for the target terminal. That is to say, the solution sends the message related to the target terminal to the
  • the target terminal related message carries the group identifier of the terminal group where the target terminal is located; the method further includes: the target mobility management entity according to the group identifier of the terminal group where the target terminal is located, and the group of the terminal group where the target terminal is located A correspondence between the identifier and the information of the source mobility management entity is determined, and a source mobility management entity that provides a service for the target terminal is determined. Based on the scheme, a source mobility management entity that provides services to the target terminal can be determined.
  • the method further includes: the target mobility management entity receiving information of the source mobility management entity from the source mobility management entity; or the target mobility management entity determining information of the source mobility management entity according to the configuration information. Based on the scheme, information of the mobility management entity can be obtained.
  • the target terminal related message is a downlink message; the target mobility management entity sends the target terminal related message to the source mobility management entity that currently provides the service to the target terminal, including: the target mobility management entity to the session management The entity sends a message related to the target terminal and information of a source mobility management entity currently serving the target terminal, the information of the source mobility management entity being used by the session management entity to send the target to the source mobility management entity Terminal related messages. That is, after the target mobility management entity determines the source mobility management entity that serves the terminal, the target terminal related message may be redirected to the source mobility management entity via the session management entity.
  • the method further includes: the target mobility management entity sends the indication information to the session management entity, where the indication information is used to indicate that the information of the source mobility management entity is used only for the current process initiated by the session management entity. That is to say, if the session management entity needs to initiate a new process after the end of the process, the session management entity needs to send the target terminal related message to the target mobility management entity or the session management entity to restart the target terminal.
  • the target mobility management entity sends the indication information to the session management entity, where the indication information is used to indicate that the information of the source mobility management entity is used only for the current process initiated by the session management entity. That is to say, if the session management entity needs to initiate a new process after the end of the process, the session management entity needs to send the target terminal related message to the target mobility management entity or the session management entity to restart the target terminal.
  • the selected mobile management entity is to send the target terminal related message to the target mobility management entity or the session management entity to restart the target terminal.
  • the second aspect provides a handover method, where the method includes: the source mobility management entity acquires, from the to-be-switched terminal that the source mobility management entity provides the service, an identifier list of the terminal that currently has an ongoing process; the source mobility management entity Sending the identifier list to the target mobility management entity; the target mobility management entity receives the identifier list from the source mobility management entity; after the target mobility management entity receives the target terminal related message, the target mobility management entity according to the identifier a list, sending a message related to the target terminal to the source mobility management entity.
  • the source mobility management entity sends the identifier list of the terminal that currently has the ongoing process to the target mobility management entity, and the target mobility management entity After receiving the message related to the target terminal, sending the message related to the target terminal to the source mobility management entity according to the identifier list, so that the source mobility management entity can continue to provide services for the terminal, and therefore the source mobility management entity can determine After servicing the target terminal, the current process of keeping the target terminal in progress is not interrupted.
  • a target mobility management entity having the functionality to implement the method described in the first aspect above.
  • 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 fourth aspect provides a target mobility management entity, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor is connected to the memory through the bus, when the target mobility management When the entity is running, the processor executes the computer-executed instructions stored by the memory to cause the target mobility management entity to perform the handover method as described in any of the first aspects above.
  • a computer readable storage medium having stored therein instructions that, when run on a computer, cause the computer to perform the switching method of any of the above first aspects.
  • 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 first aspects.
  • a chip system comprising a processor, configured to support a target mobility management entity to implement functions involved in the foregoing aspects, such as a target terminal related message, and send the target terminal to the source mobility management entity.
  • the chip system further includes a memory for storing necessary program instructions and data of the target mobility management entity.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • the eighth aspect provides a handover system, where the handover system includes: a source mobility management entity and a target mobility management entity, where the source mobility management entity is configured to acquire a to-be-switched terminal that provides service by the source mobility management entity, and currently An identifier list of the terminal of the performed process; the source mobility management entity is further configured to send the identifier list to the target mobility management entity; the target mobility management entity is configured to receive the identifier list from the source mobility management entity; the target The mobility management entity is further configured to: after receiving the message related to the target terminal, send the message related to the target terminal to the source mobility management entity according to the identifier list.
  • FIG. 1 is a schematic structural diagram of a handover system according to an embodiment of the present application
  • FIG. 2 is a schematic structural diagram of a 5G network according to an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of hardware of a communication device according to an embodiment of the present disclosure.
  • FIG. 4 is a schematic flowchart 1 of a handover method according to an embodiment of the present application.
  • FIG. 5 is a schematic flowchart 2 of a handover method according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic flowchart 3 of a handover method according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram 1 of a target mobility management entity according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram 2 of a target mobility management entity according to an embodiment of the present application.
  • 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.
  • FIG. 1 is a schematic structural diagram of a switching system 10 according to an embodiment of the present application.
  • the switching system includes a target mobility management entity 101 and a source mobility management entity 102.
  • the source mobility management entity 102 is a mobility management entity that provides services for the terminal before the terminal handover.
  • the target mobility management entity 101 is a mobility management entity that provides services for the terminal after the terminal is switched, and is not described here.
  • the message related to the target terminal may be an uplink message related to the target terminal, or may be a downlink message related to the target terminal.
  • the uplink message related to the target terminal may be an uplink message sent to the target mobility management entity 101, such as an uplink N2 message, when the access device needs to initiate an N2 message related to the target terminal, or may be sent by the target terminal to the target mobility management entity 101.
  • Uplink messages such as uplink non-access stratum (NAS) messages.
  • NAS uplink non-access stratum
  • the downlink message related to the target terminal may be a downlink message sent by the network side device to the access device, as follows: the N2 message; or the downlink message sent by the network device to the target terminal, as follows: the NAS message; or may be sent by the network device
  • the downlink message of the target mobility management entity 101 is not specifically limited in this embodiment of the present application.
  • the network device can be, for example, a session management function entity.
  • the target mobility management entity 101 is further configured to send a target terminal related message to the source mobility management entity 102 that currently provides a service to the target terminal.
  • the source mobility management entity 102 is configured to receive a message related to the target terminal from the target mobility management entity 101.
  • the source mobility management entity 102 and the target mobility management entity 101 in FIG. 1 may communicate directly, and may also perform communication through forwarding of other network devices, which is not specifically limited in this embodiment of the present application.
  • the target terminal related message may be sent to the source mobility management entity, so that the source mobility management entity may continue to provide the terminal Service, so the current flow of the target terminal that keeps the process in progress after the source mobility management entity determines that it is no longer serving the target terminal is not interrupted.
  • the foregoing switching system 10 can be applied to a 5th generation (5th generation, 5G) network, and other networks in the future, which are not specifically limited in this embodiment of the present application.
  • 5G 5th generation
  • the network element or entity corresponding to the target mobility management entity 101 may be an Access and Mobility Management Function (AMF) entity.
  • AMF Access and Mobility Management Function
  • the network element or entity corresponding to the source mobility management entity 102 may be a source AMF entity.
  • the 5G network may further include an access device, a user plane function (UPF) entity, a unified data management (UDM) entity, and an authentication server function (authentication server function).
  • UPF user plane function
  • UDM unified data management
  • authentication server function authentication server function
  • AUSF session management function
  • SMF session management function
  • PCF policy control function
  • UDSF unstructured data storage function
  • the target terminal accesses the network through the access device, and communicates with the source AMF entity and the target AMF entity through the next generation (N)1 interface (N1); the source AMF entity passes the N14.
  • the interface (referred to as N14) communicates with the target AMF entity; the source AMF entity and the target AMF entity both communicate with the access device through the N2 interface (N2); the source AMF entity and the target AMF entity both pass the N18 interface (referred to as N18) and the UDSF entity.
  • the source AMF entity and the target AMF entity both communicate with the AUSF entity through the N12 interface (N12 for short); the source AMF entity and the target AMF entity both communicate with the UDM entity through the N8 interface (referred to as N8); the source AMF entity and the target AMF entity both
  • the NMF interface (N11 for short) communicates with the SMF entity; the source AMF entity and the target AMF entity both communicate with the PCF entity through the N15 interface (N15 for short); the AUSF entity communicates with the UDM entity through the N13 interface (N13 for short); the SMF entity passes the N4
  • the interface (referred to as N4) communicates with the UPF entity; the UPF entity communicates through the N6 interface (N6) data network (DN).
  • interface name between the network elements in FIG. 2 is only an example.
  • the interface name may be referred to as another name in the specific implementation, which is not specifically limited in this embodiment of the present application.
  • the access device, the source AMF entity, the target AMF entity, the SMF entity, the UDSF entity, the AUSF entity, the UDM entity, the UPF entity, and the PCF entity of FIG. 2 are only one name, and the name does not limit the device itself. .
  • the network element or entity corresponding to the access device, the source AMF entity, the target AMF entity, the SMF entity, the UDSF entity, the AUSF entity, the UDM entity, the UPF entity, and the PCF entity may also be other
  • the name of the application is not specifically limited in this embodiment.
  • the UDM entity may be replaced by a home subscriber server (HSS) or a user subscription database (USD) or a database entity, etc., and is hereby described in a unified manner, and details are not described herein.
  • 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 , UE), mobile station (MS), terminal device, etc.
  • PDA personal digital assistant
  • WLL wireless local loop
  • MTC machine type communication
  • UE user equipment
  • MS mobile station
  • 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-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 function of the source AMF entity involved in the embodiment of the present application may refer to the function of the source mobility management entity in FIG. 1 .
  • the function of the target AMF entity involved in the embodiment of the present application may refer to FIG. 1 .
  • the function of the target mobile management entity is not described here.
  • the source AMF entity and the target AMF entity may also be responsible for the functions of registration management, mobility management, and lawful interception, which are not specifically limited in this embodiment.
  • the SMF entity involved in the embodiment of the present application is used for session management, including: session establishment, session modification, session release, and internet protocol (IP) address allocation between the terminals of the network.
  • IP internet protocol
  • the UPF entity involved in the embodiment of the present application may be responsible for processing, such as forwarding, statistics, and the like of the terminal.
  • the UPF entity may implement a user plane function of a serving gateway (SGW) and a packet data network gateway (PGW).
  • SGW serving gateway
  • PGW packet data network gateway
  • the UPF entity may also be a software-defined network (SDN) switch (Switch), which is not specifically limited in this embodiment.
  • SDN software-defined network
  • the AUSF entity involved in the embodiment of the present application is used to authenticate the terminal based on the subscription data of the terminal.
  • the UDM entity involved in the embodiment of the present application is used to store data for subscription.
  • the UDM entity further includes the functions of the authentication, the processing of the user identifier, the contract management, and the like, which are not specifically limited in this embodiment of the present application.
  • the PCF entity involved in the embodiment of the present application provides a policy rule, and supports a policy-related function such as a unified policy architecture management network behavior.
  • the UDSF entity provided in this embodiment is used to save unstructured data of the network entity.
  • the target mobility management entity 101 in FIG. 1 may be implemented by one physical device, or may be implemented by multiple physical devices, or may be a logical functional module in a physical device. No specific limitation.
  • FIG. 3 is a schematic diagram showing the hardware structure of a communication device according to an embodiment of the present application.
  • the communication device 300 includes at least one processor 301, a communication bus 302, a memory 303, and at least one communication interface 304.
  • the processor 301 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 bus 302 can include a path for communicating information between the components described above.
  • the communication interface 304 uses a device such as any transceiver for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .
  • a device such as any 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 303 can 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 can exist independently and be connected to the processor via a bus.
  • the memory can also be integrated with the processor.
  • the memory 303 is used to store application code for executing the solution of the present application, and is controlled by the processor 301 for execution.
  • the processor 301 is configured to execute the application code stored in the memory 303, thereby implementing the switching method provided by the following embodiments of the present application.
  • processor 301 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • communication device 300 can include multiple processors, such as processor 301 and processor 308 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 300 can also include an output device 305 and an input device 306.
  • Output device 305 is in communication with processor 301 and can display information in a variety of ways.
  • the output device 305 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 306 is in communication with processor 301 and can accept user input in a variety of ways.
  • input device 306 can be a mouse, keyboard, touch screen device, or sensing device, and the like.
  • the communication device 300 described above may be a general communication device or a dedicated communication device.
  • the communication device 300 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 300.
  • FIG. 4 is a schematic flowchart diagram of a handover method provided by an embodiment of the present application.
  • the source AMF entity sends the identifier list of the terminal currently having the ongoing process to the target AMF entity, and the target AMF entity receives the message related to the target terminal, according to the The identification list sends the target terminal related message to the source AMF entity.
  • the source AMF entity After the process of determining the target terminal by the source AMF entity ends, the source AMF entity sends the context of the target terminal to the target AMF entity through the N14 interface with the target AMF entity, so that the current process of the target terminal is maintained without interruption.
  • the handover of the target terminal from the source AMF entity to the target AMF entity is completed.
  • the switching method includes the following steps:
  • the source AMF entity determines the terminal to be handed over, and the source AMF entity determines a target AMF entity that provides a service for the terminal to be handed over.
  • the terminal to be switched may be all the terminals that the source AMF entity provides the service, or may be the terminal that provides the service by the source AMF entity, for example, a terminal group that includes the same group identifier. This is not specifically limited.
  • the source AMF entity may group all the terminals served by the source AMF entity according to a local policy or other factors, and configure corresponding group identifiers for each group of terminals, so as to facilitate management.
  • the group identifier here may be a globally unique AMF ID (GUMAI) of the source AMF entity, and is uniformly described herein, and details are not described herein.
  • GUII globally unique AMF ID
  • the source AMF entity sends, to the target AMF entity, the context of the terminal that is not currently in the process to be switched, so that the target AMF entity receives the context of the terminal that does not currently have an ongoing process.
  • the target AMF entity may store a context of the terminal that does not currently have an ongoing process.
  • the source AMF entity sends, to the target AMF entity, an identifier list of the terminal in the to-be-switched terminal that currently has an ongoing process, so that the target AMF entity receives the identifier list from the source AMF entity.
  • the source AMF entity may temporarily not send the context of these terminals to the target AMF, but send the identity of these terminals to the target AMF entity and inform the target AMF entity that these terminals are currently served by the source AMF entity.
  • the identifier of the terminal may include a global unique temporary identity (GUTI) of the terminal, a subscriber permanent identity (SUPI), and a terminal allocated by the source AMF entity to the terminal.
  • GUI global unique temporary identity
  • SUPI subscriber permanent identity
  • N2AP AMF N2 application layer protocol
  • N2AP AMF N2 application protocol
  • N2AP AMF N2 application protocol
  • N2AP AMF N2 application protocol
  • N2AP AMF N2 application protocol
  • the access device N2AP terminal identifier + access device identifier of the allocated terminal, or at least one of the other available identifiers, is not specifically limited in this embodiment.
  • the identifier of the terminal carried in the uplink message and the identifier of the terminal carried in the downlink message are one of the identifiers of the terminal, and the identifier of the terminal carried in the uplink message and the downlink message are carried in the downlink message.
  • the identifier of the terminal may be different.
  • the identifier of the terminal carried in the uplink message may include the GUTI, the AMF N2AP terminal identifier of the terminal allocated by the AMF entity to the terminal, the AMF N2AP terminal identifier of the terminal, and the group identifier of the terminal group where the terminal is located, and the terminal.
  • the access device N2AP terminal identifier + the access device identifier, or other available identifiers; the identifier of the terminal carried in the downlink message may include SUPI, GUTI, or other available identifiers, which are uniformly described herein, and are not described herein again.
  • the target AMF entity may store the identifier list.
  • the target AMF entity may store the correspondence between the information of the identifier list and the information of the source AMF entity, or store the identifier of the terminal in the identifier list and the source AMF entity.
  • the corresponding relationship of the information is not specifically limited in the embodiment of the present application.
  • the information of the identifier list may be, for example, the number of the identifier list.
  • the information of the source AMF entity may be, for example, the address of the source AMF entity or the name of the source AMF entity, which is not specifically limited in this embodiment of the present application.
  • the identifier list in step S403 and the context of the terminal in step S402 may be sent to the target AMF entity by using the same message, or may be sent to the target AMF entity by using different messages.
  • the application examples are not specifically limited thereto.
  • the information of the source AMF entity may be sent to the target AMF entity along with the identifier list in step S403 or the context of the terminal in step S402, for example, carried in the same message and sent to the target AMF.
  • the entity or the source address of the message is sent to the target AMF entity.
  • the information of the source AMF entity may also be configured in the target AMF entity, for example, the mapping between the IP address of the source AMF entity facing the target AMF entity and the information of the source AMF entity is configured in the target AMF entity, and further, the target AMF entity.
  • the information may be queried according to the received source IP address of the message in the step S403 or the source IP address of the message in the step S402, so as to obtain the information of the source AMF entity, which is not specifically limited in this embodiment of the present application.
  • the source AMF entity sends the indication information 1 to the access device, so that the access device receives the indication information 1 from the source AMF entity.
  • the indication information 1 is used to indicate that the source AMF entity is unavailable or that some group identifiers in the source AMF entity are unavailable. For example, if the terminal to be switched is a terminal that provides service to the source AMF entity, the indication information 1 is used to indicate that the source AMF entity is unavailable; or, for example, if the terminal to be switched is a terminal group that includes the same group identifier, The indication information 1 is used to indicate that the group identifier of the terminal group in the source AMF entity is unavailable.
  • the group identifier is not available, and the service is not provided for the terminal in the terminal group corresponding to the group identifier.
  • the source AMF entity sends the indication information 1 to the SMF entity, so that the AMF entity receives the indication information 1 from the source AMF entity.
  • step S404 For the related description of the indication information 1, refer to step S404, and details are not described herein again.
  • the exemplary AMF entity sends the indication information 1 to the SMF entity on the core network side as an example.
  • the SMF entity in the embodiment of the present application may also be replaced with other The core network device, for example, the source AMF entity may also send the indication information 1 to the UDM entity or the AUSF entity, which is not specifically limited in this embodiment of the present application.
  • the source AMF entity sends information of the target AMF entity serving the to-be-switched terminal to the access device, so that the access device receives information from the target AMF entity of the source AMF entity.
  • the information of the target AMF entity may be, for example, the address of the target AMF entity or the name of the target AMF entity, which is not specifically limited in this embodiment of the present application.
  • the information of the target AMF entity serving the terminal to be switched may also be sent by the target AMF entity to the access device, which is not specifically limited in this embodiment of the present application.
  • the source AMF entity sends information of the target AMF entity serving the terminal to be switched to the SMF entity, so that the SMF entity receives information from the target AMF entity of the source AMF entity.
  • step S406 For a description of the information of the target AMF entity, refer to step S406, and details are not described herein again.
  • the information of the target AMF entity serving the terminal to be switched may also be sent by the target AMF entity to the SMF entity, which is not specifically limited in this embodiment of the present application.
  • the information of the target AMF entity sent by the source AMF entity to the SMF entity on the core network side is exemplified as an example.
  • the source AMF entity may also be other than the SMF entity.
  • the other core network device sends the information of the target AMF entity, such as a UDM entity or an AUSF entity, which is not specifically limited in this embodiment.
  • the information of the indication information 1 in the step S404 and the target AMF entity in the step S406 may be sent to the access device by using the same message, or may be sent to the access by using different messages.
  • the device is not specifically limited in this embodiment.
  • the information of the indication information 1 in step S405 and the target AMF entity in step S407 may be sent to the SMF entity by using the same message, or may be sent to the SMF entity through different messages.
  • the application examples are not specifically limited thereto.
  • the access device releases the N2 interface of all connected terminals in the terminal to be switched, but retains the N3 interface.
  • the access device may determine, according to the indication information 1, the terminal to be switched. If the indication information 1 indicates that the source AMF entity is unavailable, then all terminals that the terminal to be switched are served for the source AMF entity are represented; or, for example, if the indication information 1 indicates that one of the source AMF entities is not available, then The terminal that represents the terminal to be switched to provide the service to the source AMF entity, the group identifies the terminal in the corresponding terminal group.
  • the SMF entity releases the N11 interface of all terminals in the connected terminal in the connected terminal.
  • the SMF entity may determine, according to the indication information 1, the terminal to be switched. If the indication information 1 indicates that the source AMF entity is unavailable, then all terminals that the terminal to be switched are served for the source AMF entity are represented; or, for example, if the indication information 1 indicates that one of the source AMF entities is not available, then The terminal that represents the terminal to be switched to provide the service to the source AMF entity, the group identifies the terminal in the corresponding terminal group.
  • the target AMF entity receives a message related to the target terminal.
  • the message related to the target terminal may be an uplink message related to the target terminal, or may be a downlink message related to the target terminal.
  • the message related to the target terminal may be an uplink message related to the target terminal, or may be a downlink message related to the target terminal.
  • the message related to the target terminal carries the identifier of the target terminal.
  • the identifier of the target terminal and the identifier of the target terminal that are carried in the downlink message related to the target terminal may not be the same. For details, refer to the description in step S403, and details are not described herein again.
  • the target AMF entity sends a message related to the target terminal to the source AMF entity according to the identifier list.
  • the target AMF entity sends the target terminal related message to the source AMF entity according to the identifier list, which may include: if the identifier list includes the identifier of the target terminal, the target AMF entity sends the target terminal related message to the source AMF entity. That is, if the target terminal has an ongoing process in the source AMF entity, the target AMF entity sends a message related to the target terminal to the source AMF entity, and the source AMF entity continues to provide services for the target terminal, thereby maintaining the target terminal. The current process is not interrupted.
  • the target AMF entity may determine, according to the identifier of the target terminal, and the correspondence between the identifier of the target terminal and the information of the source AMF entity, the source AMF entity that provides the service for the target terminal.
  • the source AMF entity may directly address the source AMF entity to the address of the target AMF entity or the source AMF entity according to the information of the source AMF entity.
  • the entity sends a message related to the target terminal.
  • the target terminal related message is an uplink message
  • the target AMF entity determines the source AMF entity serving the target mobility management entity
  • the source AMF entity may be oriented to the access device according to the information of the source AMF entity.
  • the address or the name of the source AMF entity is redirected to the source AMF entity by the access device;
  • the target terminal related message is a downlink message
  • the target AMF entity determines the source AMF entity serving the target terminal
  • the source may be based on the source
  • the information of the AMF entity in the source AMF entity facing the address of the SMF entity or the name of the source AMF entity is redirected to the source AMF entity by the SMF entity.
  • the target AMF entity sends the information of the source AMF entity to the SMF entity when redirected by the SMF entity.
  • the target AMF entity may further send, to the SMF entity, the indication information, where the information is used to indicate that the information of the source AMF entity is used only for the current process initiated by the SMF entity.
  • the "process" here may also be called a transaction.
  • the source AMF entity receives the message related to the target terminal, and processes the message related to the target terminal. If the downlink message needs to be sent to the access device or the target terminal, the source AMF needs to send the downlink message to the access device or the target terminal through the reestablished N2 interface after re-establishing the N2 interface between the access device and the source AMF entity. .
  • the source AMF entity receives the downlink message related to the target terminal, and processes the target terminal.
  • the source AMF entity may send the downlink message to the access device or the target terminal through the target AMF entity and the N2 interface between the target AMF entity and the access device.
  • the source AMF entity processes the target after receiving the message related to the target terminal.
  • the source AMF may send the N2 interface between the access device and the source AMF entity established in the redirection process to the access device or the target terminal. Downstream message.
  • the source AMF entity receives the message related to the target terminal, and processes the message related to the target terminal. If the NMF needs to be sent to the SMF, the source AMF needs to send the uplink message to the SMF entity through the reconstructed N11 interface after re-establishing the N11 interface between the SMF entity and the source AMF entity.
  • the target AMF entity directly sends the target terminal related message to the source AMF entity
  • the source AMF entity receives the message related to the target terminal
  • the message related to the target terminal is processed.
  • the source AMF entity may send the uplink message to the SMF entity through the target AMF entity and the N11 interface between the target AMF entity and the SMF entity.
  • the source AMF entity processes the target terminal after receiving the message related to the target terminal.
  • the source AMF may send the uplink message to the SMF entity through the N11 interface between the SMF entity and the source AMF entity established in the redirection process.
  • the source AMF entity determines that the process of the target terminal ends.
  • the end of the process of the target terminal may be the end of the process currently being performed by the target terminal, or may be the end of other processes after the end of the process currently being performed by the target terminal.
  • the source AMF entity determines that the target terminal handover process needs to be immediately re-registered to update the tracking area (TA) list and redistribute the GUTI, the source AMF entity should wait for the above re-registration process to end. Then switch the target terminal to the target AMF entity.
  • the re-registration here is equivalent to tracking area update (TAU).
  • the source AMF entity sends the context of the target terminal to the target AMF entity, so that the target terminal receives the context of the target terminal from the source AMF entity.
  • the target AMF entity After receiving the context of the target terminal, the target AMF entity deletes the correspondence between the identifier of the target terminal and the information of the source AMF entity.
  • the source AMF entity After the correspondence between the identifier of the target terminal and the information of the source AMF entity is deleted, the source AMF entity will no longer provide services for the target terminal. Further, after the target AMF entity receives the target terminal related message, the target AMF entity may serve the target terminal instead of transmitting the target terminal related message to the source AMF entity.
  • the correspondence between the identifier of the target terminal and the information of the source AMF entity is deleted, specifically, the identifier of the target terminal is Deleted from the list of identifiers.
  • the target AMF entity stores the identifier of the target terminal and the information of the source AMF entity
  • the corresponding relationship between the identifier of the target terminal and the information of the source AMF entity is deleted, specifically, deleting the identifier of the target terminal and The correspondence of the information of the source AMF entity is this record.
  • step S415. If the N2 interface of the access device and the source AMF entity is established in step S411, the target AMF entity sends an update N2 interface message to the access device, so that the access device receives the updated N2 interface message from the target AMF entity.
  • the update N2 interface message is used to instruct the access device to update the target terminal's N2 interface to the target AMF entity.
  • the update N2 interface message may be sent by the source AMF entity to the access device, and the access device updates the N2 interface of the target terminal to the target AMF entity according to the update N2 interface message.
  • the update N2 interface message may be sent by the source AMF entity to the access device, and the access device updates the N2 interface of the target terminal to the target AMF entity according to the update N2 interface message.
  • the access device updates the N2 interface of the target terminal to the target AMF entity according to the update N2 interface message.
  • step S416 If the N11 interface of the SMF entity and the source AMF entity is established in step S411, the target AMF entity sends an update N11 interface message to the SMF entity, so that the SMF entity receives the updated N11 interface message from the target AMF entity.
  • the update N11 interface message is used to instruct the SMF entity to update the N11 interface of the target terminal to the target AMF entity.
  • the update N11 interface message may also be sent by the source AMF entity to the SMF entity, and the SMF entity updates the N11 interface of the target terminal to the target AMF entity according to the update N11 interface message, which is not specifically limited in this embodiment. .
  • the source AMF entity sends the identifier list of the terminal that has the ongoing process to the target AMF entity, and the target AMF entity receives the message related to the target terminal. Then, according to the identifier list, the target terminal related message is sent to the source AMF entity. After the process of determining the target terminal by the source AMF entity ends, the source AMF entity sends the context of the target terminal to the target AMF entity through the N14 interface with the target AMF entity, so that the current process of the target terminal is maintained without interruption. The handover of the target terminal from the source AMF entity to the target AMF entity is completed.
  • the action of the target AMF entity in the foregoing steps S401 to S416 can be performed by the processor 301 in the communication device 300 shown in FIG. 3 to call the application code stored in the memory 303, which is not limited in this embodiment.
  • FIG. 5 is a schematic flowchart diagram of a handover method provided by an embodiment of the present application.
  • the target AMF entity after receiving the message related to the target terminal, the target AMF entity searches for the context of the target terminal according to the identifier of the target terminal carried in the message related to the target terminal; if the context of the target terminal is not found, the source AMF is The entity sends a message related to the target terminal.
  • the source AMF entity After the process of determining the target terminal by the source AMF entity ends, the source AMF entity sends the context of the target terminal to the target AMF entity through the N14 interface with the target AMF entity, so that the current process of the target terminal is maintained without interruption.
  • the handover of the target terminal from the source AMF entity to the target AMF entity is completed.
  • the switching method includes the following steps:
  • the source AMF entity sends, to the target AMF entity, the context of the terminal that is not currently in the process to be switched, so that the target AMF entity receives the context of the terminal that does not currently have an ongoing process.
  • the target AMF entity may store a context of the terminal that does not currently have an ongoing process.
  • the group identifier of the at least one terminal group is included in the context of the terminal that does not currently have an ongoing process.
  • the context of each terminal includes the group identifier of the terminal group where the terminal is located, so that the target AMF entity can store the group identifier and source of the at least one terminal group after receiving the context of the terminal that has no current process. Correspondence of information of AMF entities.
  • the information of the source AMF entity may be sent to the target AMF entity together with the context of the terminal, such as being carried in the same message and sent to the target AMF entity or sent as the source address of the message to the target AMF. entity.
  • the information of the source AMF entity may also be configured in the target AMF entity, for example, the mapping between the IP address of the source AMF entity facing the target AMF entity and the information of the source AMF entity is configured in the target AMF entity, and further, the target AMF entity.
  • the information may be queried according to the source IP address of the received message carrying the context of the terminal in the step S502, so that the information of the source AMF entity is obtained, which is not specifically limited in this embodiment of the present application.
  • the target AMF entity receives a message related to the target terminal.
  • step S410 For a description of the message related to the target terminal, refer to step S410, and details are not described herein again.
  • the message related to the target terminal carries the identifier of the target terminal.
  • the identifier of the target terminal and the identifier of the target terminal that are carried in the downlink message related to the target terminal may not be the same. For details, refer to the description in step S403, and details are not described herein again.
  • the message related to the target terminal carries the group identifier of the terminal group where the target terminal is located.
  • the target AMF entity searches for a context of the target terminal according to the identifier of the target terminal.
  • the target AMF entity sends a target terminal related message to the source AMF entity, so that the source AMF entity receives the target terminal related message from the target AMF entity.
  • the target AMF entity if the target AMF entity cannot find the context of the target terminal, and the group identifier of the at least one terminal group includes the group identifier of the terminal group where the target terminal is located, the target AMF entity is to the source AMF entity. Send a message related to the target terminal. That is, if the target terminal has an ongoing process in the source AMF entity, the target AMF entity sends a message related to the target terminal to the source AMF entity, and the source AMF entity continues to provide services for the target terminal, thereby maintaining the target terminal. The current process is not interrupted.
  • the target AMF entity may determine, after the context of the target terminal is not found, whether the group identifier of the at least one terminal group includes the group identifier of the terminal group where the target terminal is located; After determining the group identifier of the terminal group in which the target terminal is located, the context of the target terminal is not found in the embodiment of the present disclosure.
  • the target AMF entity may determine, according to the group identifier of the terminal group where the target terminal is located, and the correspondence between the group identifier of the terminal group where the target terminal is located and the information of the source AMF entity, the source AMF entity that provides the service to the target mobility management entity.
  • the specific implementation of the target AMF entity sending the target terminal-related message to the source AMF entity may refer to step S411, and details are not described herein again.
  • the target AMF entity after receiving the message related to the target terminal, the target AMF entity searches for the context of the target terminal according to the identifier of the target terminal carried in the message related to the target terminal; if the context of the target terminal is not found, Sending a message related to the target terminal to the source AMF entity.
  • the source AMF entity After the process of determining the target terminal by the source AMF entity ends, the source AMF entity sends the context of the target terminal to the target AMF entity through the N14 interface with the target AMF entity, so that the current process of the target terminal is maintained without interruption. The handover of the target terminal from the source AMF entity to the target AMF entity is completed.
  • the action of the target AMF entity in the foregoing steps S501 to S515 can be performed by the processor 301 in the communication device 300 shown in FIG. 3 to call the application code stored in the memory 303, which is not limited in this embodiment.
  • FIG. 6 is a schematic flowchart diagram of a handover method provided by an embodiment of the present application.
  • the target AMF entity After receiving the message related to the target terminal, the target AMF entity reads the context of the target terminal from the UDSF entity according to the identifier of the target terminal carried in the message related to the target terminal; if the target terminal is currently source AMF
  • the entity service that is, the target terminal currently has an ongoing process, the UDSF entity sends the information of the source AMF entity to the target AMF entity, and the target AMF entity can send the target terminal related to the source AMF entity according to the information of the source AMF entity.
  • the source AMF entity After the process of determining the target terminal by the source AMF entity ends, the source AMF entity sends the context of the target terminal to the target AMF entity through the N14 interface with the target AMF entity, or the source AMF entity saves the context of the target terminal to the UDSF entity. Therefore, the switching of the target terminal from the source AMF entity to the target AMF entity can be completed without interrupting the current process of the target terminal.
  • the switching method includes the following steps:
  • the target terminal is registered to the source AMF entity.
  • the specific process of registering the target terminal to the source AMF entity may refer to the existing implementation manner, and details are not described herein again.
  • the source AMF entity registers with the UDSF entity.
  • the source AMF entity registers with the UDSF entity. Specifically, the source AMF entity registers itself as the service AMF of the target terminal in the UDSF entity.
  • the specific process of registering the source AMF entity to the UDSF entity may refer to the existing implementation manner, and details are not described herein again.
  • the source AMF entity determines the terminal to be switched.
  • step S401 For a description of the terminal to be switched, refer to step S401, and details are not described herein again.
  • the related description of the terminal to be switched to the source AMF entity and the registration of the source AMF entity to the UDSF entity may refer to the terminal to be switched in step S601 to register with the source AMF entity, and the source AMF entity registered to the UDSF entity in step S602. Description, no longer repeat here.
  • the source AMF entity sends, to the UDSF entity, the context of the terminal that is not currently in the process to be switched, so that the UDSF entity receives the context of the terminal that does not currently have an ongoing process.
  • the UDSF entity may store a context of the terminal that does not currently have an ongoing process.
  • the context of the terminal that has no ongoing process may include only the latest context of the terminal, that is, relative to the terminal.
  • the context of the terminal sent to the UDSF entity has a changed context.
  • the source AMF entity does not need to resend the context of the terminal to the UDSF at this step. entity.
  • the source AMF entity sends the indication information 2 to the UDSF entity, so that the UDSF entity receives the indication information 2 from the source AMF entity.
  • the indication information 2 is used to instruct the UDSF entity to delete the information of the source AMF entity as the serving AMF entity of the terminal that does not currently have an ongoing procedure.
  • the UDSF entity deletes, according to the indication information 2, information of the source AMF entity as the service AMF of the terminal that does not currently have an ongoing process.
  • the context of the terminal in step S604 and the indication information 2 in step S605 may be sent to the UDSF entity by using the same message, or may be sent to the UDSF entity by using different messages. This example does not specifically limit this.
  • the source AMF entity determines the target AMF entity that provides the service for the terminal to be switched; In an example, the access device or the SMF entity first selects the target AMF entity for the target terminal before transmitting the target terminal related message to the target AMF entity.
  • the target AMF entity reads the context of the target terminal from the UDSF entity according to the identifier of the target terminal.
  • the UDSF entity sends the information of the source AMF entity to the target AMF entity, so that the target AMF entity receives the message from the source AMF of the UDSF entity.
  • the target AMF entity sends a target terminal related message to the source AMF entity according to the information of the source AMF entity, so that the source AMF entity receives the target terminal related message from the target AMF entity.
  • the specific implementation of the target AMF entity sending the target terminal-related message to the source AMF entity may refer to step S411, and details are not described herein again.
  • the target AMF entity sends the information of the source AMF entity to the SMF entity when redirected by the SMF entity.
  • the target AMF entity may further send the indication information to the SMF entity, where the indication information is used to indicate that the information of the source AMF entity is used only for the current process initiated by the SMF entity.
  • the SMF entity After the SMF entity needs to initiate a new process, the SMF entity re-selects the AMF entity for the target terminal, and then sends the message related to the target terminal to the AMF entity reselected for the target terminal.
  • steps S617 and S618 in the embodiment of the present application may be replaced by the following scheme:
  • the source AMF entity saves the context of the target terminal to the UDSF entity, and deletes the source AMF entity as the information of the service AMF of the target terminal; at the same time, the source AMF entity notifies the access device to release the N2 interface of the target terminal, and retains the N3 interface; And, the source AMF entity notifies the SMF entity to release the N11 interface of the target terminal.
  • the target AMF entity after receiving the message related to the target terminal, the target AMF entity reads the context of the target terminal from the UDSF entity according to the identifier of the target terminal carried in the message related to the target terminal;
  • the source AMF entity serves, that is, the target terminal currently has an ongoing process, and the UDSF entity sends the information of the source AMF entity to the target AMF entity, and the target AMF entity can send the source AMF entity to the source AMF entity according to the information of the source AMF entity.
  • the source AMF entity After the process of determining the target terminal by the source AMF entity ends, the source AMF entity sends the context of the target terminal to the target AMF entity through the N14 interface with the target AMF entity, or the source AMF entity saves the context of the target terminal to the UDSF entity. Therefore, the switching of the target terminal from the source AMF entity to the target AMF entity can be completed without interrupting the current process of the target terminal.
  • the action of the target AMF entity in the foregoing steps S601 to S617 can be performed by the processor 301 in the communication device 300 shown in FIG. 3 to call the application code stored in the memory 303, which is not limited in this embodiment.
  • the solution provided by the embodiment of the present application is mainly introduced from the perspective of interaction between the network elements. It can be understood that, in order to implement the above functions, the above-mentioned target mobility management entity includes corresponding hardware structures and/or software modules for performing respective functions.
  • 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 divide the function module of the target mobility management entity according to the foregoing method example.
  • each function module may be divided according to each function, or two or more functions may be integrated into 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. 7 shows a possible structural diagram of the target mobility management entity 70 involved in the above embodiment.
  • the target mobility management entity 70 includes a receiving module 701 and a transmitting module 702.
  • the receiving module 701 is configured to receive a message related to the target terminal.
  • the sending module 702 is configured to send a target terminal related message to a source mobility management entity that currently provides a service to the target terminal.
  • the receiving module 701 is further configured to receive an identifier list from the source mobility management entity, where the identifier list is a list of identifiers of the terminal that currently has an ongoing process in the to-be-switched terminal that provides the source mobility management entity.
  • the sending module 702 is specifically configured to: send, according to the identifier list, a message related to the target terminal to the source mobility management entity that currently provides the service to the target terminal.
  • the target terminal related message carries the identifier of the target terminal.
  • the sending module 702 is specifically configured to: if the identifier of the target terminal is included in the identifier list, send a message related to the target terminal to the source mobility management entity that currently provides the service to the target terminal.
  • the message related to the target terminal carries the identifier of the target terminal.
  • the target mobility management entity 70 further includes: a determining module 703.
  • the determining module 703 is configured to determine, according to the identifier of the target terminal, and the correspondence between the identifier of the target terminal and the information of the source mobility management entity, the source mobility management entity that provides the service for the target terminal.
  • the target mobility management entity 70 may further include: a deletion module 704.
  • the deleting module 704 is configured to delete the correspondence between the identifier of the target terminal and the information of the source mobility management entity after the receiving module 701 receives the context of the target terminal.
  • the target terminal related message carries the identifier of the target terminal.
  • the sending module 702 is specifically configured to: search for a context of the target terminal according to the identifier of the target terminal; if the context of the target terminal is not found, send a message related to the target terminal to the source mobility management entity that currently provides the service to the target terminal.
  • the message related to the target terminal carries the group identifier of the terminal group where the target terminal is located.
  • the receiving module 701 is further configured to receive a context of at least one terminal from the source mobility management entity, where the context of the at least one terminal includes a group identifier of the at least one terminal group, where the context of each terminal in the context of the at least one terminal includes the The group identifier of the terminal group where the terminal is located; the sending module 702 is specifically configured to: if the context of the target terminal is not found, and the group identifier of the at least one terminal group includes the group identifier of the terminal group where the target terminal is located, and provide services to the target terminal.
  • the source mobility management entity sends a message related to the target terminal.
  • the target terminal related message carries the group identifier of the terminal group where the target terminal is located.
  • the target mobility management entity 70 further includes: a determining module 703.
  • the determining module 703 is configured to determine, according to the group identifier of the terminal group where the target terminal is located, and the correspondence between the group identifier of the terminal group where the target terminal is located and the information of the source mobility management entity, the source mobility management entity that provides the service for the target terminal.
  • the receiving module 701 is further configured to receive information from a source mobility management entity of the source mobility management entity.
  • the determining module 703 is further configured to determine information about the source mobility management entity according to the configuration information.
  • the target terminal related message is a downlink message
  • the sending module 702 is specifically configured to: send, to the session management entity, a message related to the target terminal and information of the source mobile management entity that currently provides the service to the target terminal, where the source mobile management entity The information is used by the session management entity to send a target terminal related message to the source mobility management entity.
  • the sending module 702 is further configured to send the indication information to the session management entity, where the indication information is used to indicate that the information of the source mobility management entity is used only for the current process initiated by the session management entity.
  • FIG. 8 shows a possible structural diagram of the target mobility management entity 80 involved in the foregoing embodiment, and the target mobility management entity 80 includes a communication module 801.
  • the target mobility management entity 80 may further include a processing module 802.
  • the communication module 801 can be used to perform operations that can be performed by the receiving module 701 and the sending module 702 in FIG. 7; the processing module 802 can be used to perform operations performed by the determining module 703 and the deleting module 704 in FIG. Referring to the embodiment shown in FIG. 7, the embodiments of the present application are not described herein again.
  • the target mobility management entity is presented in the form of dividing each functional module corresponding to each function, or the target mobility management entity is presented in a form that divides each functional module in an integrated manner.
  • a “module” herein may refer to an Application-Specific Integrated Circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above. Device.
  • ASIC Application-Specific Integrated Circuit
  • the target mobility management entity 70 or the target mobility management entity 80 may take the form shown in FIG.
  • the receiving module 701, the transmitting module 702, the determining module 703, and the deleting module 704 in FIG. 7 can be implemented by the processor 301 and the memory 303 of FIG.
  • the receiving module 701, the sending module 702, the determining module 703, and the deleting module 704 can be executed by calling the application code stored in the memory 303 by the processor 301, which is not limited in this embodiment.
  • the processing module 802 and the communication module 801 in FIG. 8 may be implemented by the processor 301 and the memory 303 of FIG.
  • the processing module 802 and the communication module 801 can be executed by using the application code stored in the memory 303 by the processor 301, which is not limited in this embodiment.
  • the target mobility management entity provided by the embodiment of the present application can be used to perform the foregoing switching method. Therefore, the technical effects that can be obtained by reference to the foregoing method embodiments are not described herein.
  • the embodiment of the present application provides a chip system, where the chip system includes a processor, configured to support a target mobility management entity to implement functions involved in the foregoing aspects, for example, receiving a message related to a target terminal, and moving to a source.
  • the management entity sends a message related to the target terminal.
  • the chip system also includes a memory. This memory is used to save the necessary program instructions and data of the target mobility management entity.
  • 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 by wire (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)

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供切换方法、设备及系统，可以在AMF实体确定不再为某些终端提供服务之后，保持这些终端中某些流程正在进行的终端的当前流程不中断。方法包括：目标移动管理实体接收目标终端相关的消息；该目标移动管理实体向当前为该目标终端提供服务的源移动管理实体发送该目标终端相关的消息。

Description

切换方法、设备及系统
本申请要求了2017年7月20日提交的、申请号为201710597349.1、发明名称为“切换方法、设备及系统”的中国申请的优先权，以及2017年10月13日提交的、申请号为201710953564.0、发明名称为“切换方法、设备及系统”的中国申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及切换方法、设备及系统。
背景技术
现有技术中，当接入和移动性管理(access and mobility management function，AMF)实体确定不再为终端提供服务时，AMF实体给无线接入网(radio access network，RAN)设备发送“不可用”指示，由RAN设备将该AMF实体标注为不可用。这样，在后续选择AMF实体时不再考虑该AMF实体。并且，RAN设备在收到上述“不可用”指示后释放所有由该AMF实体服务的终端的下一代网络(next generation，N)2接口(简称N2)。后续，若RAN设备需要发送原来由该AMF实体服务的某个终端相关的消息时，RAN设备将该终端相关的消息发送给该AMF实体指定的目标AMF实体或者RAN设备为该终端选择的目标AMF实体。
但是，如果原来由该AMF实体服务的终端有正在进行的流程，由于RAN设备已经释放了由该AMF实体服务的该终端的N2接口，因此RAN设备无法将该终端的相关消息发送给原来的AMF实体，这会导致该终端的当前流程中断，从而影响用户体验。
发明内容
本申请实施例提供切换方法、设备及系统，可以在AMF实体确定不再为某些终端提供服务之后，保持这些终端中某些流程正在进行的终端的当前流程不中断。
为达到上述目的，本申请实施例提供如下技术方案：
第一方面，提供一种切换方法，该方法包括：目标移动管理实体接收目标终端相关的消息；该目标移动管理实体向当前为该目标终端提供服务的源移动管理实体发送该目标终端相关的消息。基于本申请实施例提供的切换方法，由于目标移动管理实体在接收目标终端相关的消息之后，可以将该目标终端相关的消息发送给源移动管理实体，使得源移动管理实体可以继续为该终端提供服务，因此可以在源移动管理实体确定不再为该目标终端提供服务之后，保持流程正在进行的目标终端的当前流程不中断。
在一种可能的设计中，该方法还包括：该目标移动管理实体接收来自该源移动管理实体的标识列表，该标识列表为该源移动管理实体提供服务的待切换终端中，当前有正在进行的流程的终端的标识列表；该目标移动管理实体向当前为该目标终端提供服务的源移动管理实体发送该目标终端相关的消息，包括：该目标移动管理实体根据该标识列表，向当前为该目标终端提供服务的源移动管理实体发送该目标终端相关的消息。本申请实施例提供的切换方法中，源移动管理实体将提供服务的待切换终端中，当前有正在进行的流程的终端的标识列表发送给目标移动管理实体，由目标移动管理实体在接收目标终端相关的消息之后，根据该 标识列表，向源移动管理实体发送该目标终端相关的消息，使得源移动管理实体可以继续为该终端提供服务，因此可以在源移动管理实体确定不再为该目标终端提供服务之后，保持流程正在进行的目标终端的当前流程不中断。
可选的，该目标终端相关的消息中携带该目标终端的标识；该目标移动管理实体根据该标识列表，向当前为该目标终端提供服务的源移动管理实体发送该目标终端相关的消息，包括：若该标识列表中包括该目标终端的标识，该目标移动管理实体向当前为该目标终端提供服务的源移动管理实体发送该目标终端相关的消息。
可选的，该目标终端相关的消息中携带该目标终端的标识；该方法还包括：该目标移动管理实体根据该目标终端的标识，以及该目标终端的标识和该源移动管理实体的信息的对应关系，确定为该目标终端提供服务的源移动管理实体。基于该方案，可以确定为目标终端提供服务的源移动管理实体。
可选的，该方法还包括：在该目标移动管理实体接收到该目标终端的上下文之后，该目标移动管理删除该目标终端的标识和该源移动管理实体的信息的对应关系。基于该方案，在目标移动管理实体接收目标终端相关的消息之后，可以由目标移动管理实体为该目标终端服务，而不是将目标终端相关的消息发送给源移动管理实体。
在一种可能的设计中，该目标终端相关的消息中携带该目标终端的标识；该目标移动管理实体向当前为该目标终端提供服务的源移动管理实体发送该目标终端相关的消息，包括：该目标移动管理实体根据该目标终端的标识，查找该目标终端的上下文；若该目标移动管理实体未查找到该目标终端的上下文，该目标移动管理实体向当前为该目标终端提供服务的源移动管理实体发送该目标终端相关的消息。基于该方案，目标移动管理实体在接收目标终端相关的消息之后，根据目标终端相关的消息中携带的目标终端的标识，查找目标终端的上下文；若查找不到目标终端的上下文，向源移动管理实体发送该目标终端相关的消息，使得源移动管理实体可以继续为该终端提供服务，因此可以在源移动管理实体确定不再为该目标终端提供服务之后，保持流程正在进行的目标终端的当前流程不中断。
可选的，该目标终端相关的消息中携带该目标终端所在终端组的组标识；该方法还包括：该目标移动管理实体接收来自该源移动管理实体的至少一个终端的上下文，该至少一个终端的上下文中包括至少一个终端组的组标识，其中，该至少一个终端的上下文中每个终端的上下文包括该终端所在终端组的组标识；若该目标移动管理实体未查找到该目标终端的上下文，该目标移动管理实体向当前为该目标终端提供服务的源移动管理实体发送该目标终端相关的消息，包括：若该目标移动管理实体未查找到该目标终端的上下文，且该至少一个终端组的组标识中包括该目标终端所在终端组的组标识，该目标移动管理实体向当前为该目标终端提供服务的源移动管理实体发送该目标终端相关的消息。也就是说，该方案在确定目标终端为源移动管理实体提供服务的终端之后，才向源移动管理实体发送该目标终端相关的消息，从而可以保证流程的准确性。
可选的，该目标终端相关的消息携带该目标终端所在终端组的组标识；该方法还包括：该目标移动管理实体根据该目标终端所在终端组的组标识以及该目标终端所在终端组的组标识和该源移动管理实体的信息的对应关系，确定为该目标终端提供服务的源移动管理实体。基于该方案，可以确定为目标终端提供服务的源移动管理实体。
可选的，该方法还包括：该目标移动管理实体接收来自该源移动管理实体的该源移动管理实体的信息；或者，该目标移动管理实体根据配置信息确定该源移动管理实体的信息。基于该方案，可以获取移动管理实体的信息。
可选的，该目标终端相关的消息为下行消息；该目标移动管理实体向当前为该目标终端提供服务的源移动管理实体发送该目标终端相关的消息，包括：该目标移动管理实体向会话管理实体发送该目标终端相关的消息以及当前为该目标终端提供服务的源移动管理实体的信息，所述源移动管理实体的信息用于所述会话管理实体向所述源移动管理实体发送所述目标终端相关的消息。也就是说，在目标移动管理实体确定为终端提供服务的源移动管理实体之后，可以将目标终端相关的消息经过会话管理实体重定向给源移动管理实体。
可选的，该方法还包括：该目标移动管理实体向该会话管理实体发送指示信息，该指示信息用于指示该源移动管理实体的信息只用于该会话管理实体发起的本次流程。也就是说，当本次流程结束后若该会话管理实体需要发起新的流程，该会话管理实体需要将该目标终端相关的消息发送给该目标移动管理实体或该会话管理实体为该目标终端重新选择的移动管理实体。
第二方面，提供了一种切换方法，该方法包括：源移动管理实体获取该源移动管理实体提供服务的待切换终端中，当前有正在进行的流程的终端的标识列表；该源移动管理实体向目标移动管理实体发送该标识列表；该目标移动管理实体接收来自该源移动管理实体的该标识列表；在该目标移动管理实体接收到目标终端相关的消息之后，该目标移动管理实体根据该标识列表，向该源移动管理实体发送该目标终端相关的消息。也就是说，本申请实施例提供的切换方法中，源移动管理实体将提供服务的待切换终端中，当前有正在进行的流程的终端的标识列表发送给目标移动管理实体，由目标移动管理实体在接收目标终端相关的消息之后，根据该标识列表，向源移动管理实体发送该目标终端相关的消息，使得源移动管理实体可以继续为该终端提供服务，因此可以在源移动管理实体确定不再为该目标终端提供服务之后，保持流程正在进行的目标终端的当前流程不中断。
第三方面，提供了一种目标移动管理实体，该目标移动管理实体具有实现上述第一方面所述的方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第四方面，提供了一种目标移动管理实体，包括：处理器、存储器、总线和通信接口；该存储器用于存储计算机执行指令，该处理器与该存储器通过该总线连接，当该目标移动管理实体运行时，该处理器执行该存储器存储的该计算机执行指令，以使该目标移动管理实体执行如上述第一方面中任一所述的切换方法。
第五方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第一方面中任意一项的切换方法。
第六方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第一方面中任意一项的切换方法。
第七方面，提供了一种芯片系统，该芯片系统包括处理器，用于支持目标移动管理实体实现上述方面中所涉及的功能，例如目标终端相关的消息，并向源移动管理实体发送目标终端相关的消息。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存该目标移动管理实体必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
其中，第三方面至第七方面中任一种设计方式所带来的技术效果可参见第一方面中不同设计方式所带来的技术效果，此处不再赘述。
第八方面，提供一种切换系统，该切换系统包括：源移动管理实体和目标移动管理实体；该源移动管理实体，用于获取该源移动管理实体提供服务的待切换终端中，当前有正在进行 的流程的终端的标识列表；该源移动管理实体，还用于向目标移动管理实体发送该标识列表；该目标移动管理实体，用于接收来自该源移动管理实体的该标识列表；该目标移动管理实体，还用于在接收到目标终端相关的消息之后，根据该标识列表，向该源移动管理实体发送该目标终端相关的消息。
其中，第八方面所带来的技术效果可参见第二方面所带来的技术效果，此处不再赘述。
本申请的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
图1为本申请实施例提供的切换系统的架构示意图；
图2为本申请实施例提供的5G网络的架构示意图；
图3为本申请实施例提供的通信设备的硬件结构示意图；
图4为本申请实施例提供的切换方法的流程示意图一；
图5为本申请实施例提供的切换方法的流程示意图二；
图6为本申请实施例提供的切换方法的流程示意图三；
图7为本申请实施例提供的目标移动管理实体的结构示意图一；
图8为本申请实施例提供的目标移动管理实体的结构示意图二。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
如图1所示，为本申请实施例提供的切换系统10的架构示意图。该切换系统包括目标移动管理实体101和源移动管理实体102。其中，源移动管理实体102为终端切换之前为该终端提供服务的移动管理实体；目标移动管理实体101为终端切换之后为该终端提供服务的移动管理实体，在此统一说明，以下不再赘述。
其中，该目标终端相关的消息可以是目标终端相关的上行消息，也可以是目标终端相关的下行消息。目标终端相关的上行消息可以是接入设备需要发起与目标终端相关的N2消息时，发送给目标移动管理实体101的上行消息，如上行N2消息；也可以是目标终端发送给目标移动管理实体101的上行消息，如上行非接入层(non access stratum，NAS)消息。目标终端相关的下行消息可以是网络侧设备发送给接入设备的下行消息，如下行N2消息；也可以是网络设备发送给目标终端的下行消息，如下行NAS消息；还可以是网络设备发送给目标移动管理实体101的下行消息，本申请实施例对此不作具体限定。该网络设备例如可以是会话管理功能实体。
目标移动管理实体101，还用于向当前为目标终端提供服务的源移动管理实体102发送目标终端相关的消息。
源移动管理实体102，用于接收来自目标移动管理实体101的目标终端相关的消息。
其中，图1中的源移动管理实体102和目标移动管理实体101可能直接通信，也可能通过其他网络设备的转发进行通信，本申请实施例对此不作具体限定。
基于本申请实施例提供的切换系统，由于目标移动管理实体在接收目标终端相关的消息之后，可以将该目标终端相关的消息发送给源移动管理实体，使得源移动管理实体可以继续为该终端提供服务，因此可以在源移动管理实体确定不再为该目标终端提供服务之后，保持流程正在进行的目标终端的当前流程不中断。
可选的，上述切换系统10可以应用于第五代(5rd generation，5G)网络以及未来其它的网络，本申请实施例对此不作具体限定。
其中，若上述切换系统10应用于5G网络，则如图2所示，目标移动管理实体101所对应的网元或者实体可以为目标接入与移动管理功能(Access and Mobility Management Function，AMF)实体；源移动管理实体102所对应的网元或者实体可能为源AMF实体。
此外，如图2所示，该5G网络还可以包括接入设备、用户面功能(user plane function，UPF)实体、统一数据管理(unified data management，UDM)实体、鉴权服务器功能(authentication server function，AUSF)实体、会话管理功能(session management function，SMF)实体、策略控制功能(policy control function，PCF)实体等。可选的，该5G网络还可以包括非结构化数据存储功能(unstructured data storage function，UDSF)实体。
其中，本申请实施例中，目标终端通过接入设备接入网络，并通过下一代网络(next generation，N)1接口(简称N1)与源AMF实体和目标AMF实体通信；源AMF实体通过N14接口(简称N14)与目标AMF实体通信；源AMF实体和目标AMF实体均通过N2接口(简称N2)与接入设备通信；源AMF实体和目标AMF实体均通过N18接口(简称N18)与UDSF实体通信；源AMF实体和目标AMF实体均通过N12接口(简称N12)与AUSF实体通信；源AMF实体和目标AMF实体均通过N8接口(简称N8)与UDM实体通信；源AMF实体和目标AMF实体均通过N11接口(简称N11)与SMF实体通信；源AMF实体和目标AMF实体均通过N15接口(简称N15)与PCF实体通信；AUSF实体通过N13接口(简称N13)与UDM实体通信；SMF实体通过N4接口(简称N4)与UPF实体通信；UPF实体通过N6接口(简称N6)数据网络(data network，DN)通信。
需要说明的是，图2中的各个网元之间的接口名字只是一个示例，具体实现中接口名字可能称为其他名字，本申请实施例对此不作具体限定。
需要说明的是，图2的接入设备、源AMF实体、目标AMF实体、SMF实体、UDSF实体、AUSF实体、UDM实体、UPF实体和PCF实体等仅是一个名字，名字对设备本身不构成限定。在5G网络以及未来其它的网络中，接入设备、源AMF实体、目标AMF实体、SMF实体、UDSF实体、AUSF实体、UDM实体、UPF实体和PCF实体所对应的网元或实体也可以是其他的名字，本申请实施例对此不作具体限定。例如，该UDM实体还有可能被替换为用户归属服务器(home subscriber server，HSS)或者用户签约数据库(user subscription database，USD)或者数据库实体，等等，在此进行统一说明，以下不再赘述。
可选的，本申请实施例中所涉及到的终端(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)等。为方便描述，本申请中，上面提到的设备统称为终端。
可选的，本申请实施例中所涉及到的接入设备指的是接入核心网的设备，例如可以是基站，宽带网络业务网关(broadband network gateway，BNG)，汇聚交换机，非3GPP接入设备等。基站可以包括各种形式的基站，例如：宏基站，微基站(也称为小站)，中继站，接入点等。
可选的，本申请实施例中所涉及到的源AMF实体的功能可参考图1中的源移动管理实体的功能；本申请实施例中所涉及到的目标AMF实体的功能可参考图1中的目标移动管理实体的功能，在此不再赘述。此外，源AMF实体和目标AMF实体还可以负责注册管理，移动性管理，合法监听等功能，本申请实施例对此不作具体限定。
可选的，本申请实施例中所涉及到的SMF实体用于进行会话管理，包括：会话建立，会话修改，会话释放，终端的网络之间互连的协议(internet protocol，IP)地址分配和管理，UPF实体的选择和控制，合法监听等与会话相关的控制功能。
可选的，本申请实施例中所涉及到的UPF实体可负责终端报文的转发、统计等处理功能。例如，UPF实体可实现服务网关(serving gateway，SGW)和分组数据网络网关(packet data network gateway，PGW)的用户面功能。UPF实体还可以是软件定义网络(software defined network，SDN)交换机(Switch)，本申请实施例对此不作具体限定。
可选的，本申请实施例中所涉及到的AUSF实体用于基于终端的签约数据对终端进行鉴权认证。
可选的，本申请实施例中所涉及到的UDM实体用于储存用于签约数据。此外，UDM实体还包括鉴权认证，处理用户标识，签约管理等功能，本申请实施例对此不作具体限定。
可选的，本申请实施例中所涉及到的PCF实体提供策略规则，支持统一的策略架构管理网络行为等与策略相关的功能。
可选的，本申请实施例中所提供的UDSF实体用于保存网络实体的非结构化数据。
可选的，图1中的目标移动管理实体101，可以由一个实体设备实现，也可以由多个实体设备共同实现，还可以是一个实体设备内的一个逻辑功能模块，本申请实施例对此不作具体限定。
例如，图1中的目标移动管理实体101可以通过图3中的通信设备来实现。图3所示为本申请实施例提供的通信设备的硬件结构示意图。通信设备300包括至少一个处理器301，通信总线302，存储器303以及至少一个通信接口304。
处理器301可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信总线302可包括一通路，在上述组件之间传送信息。
通信接口304，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)等。
存储器303可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable  programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过总线与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器303用于存储执行本申请方案的应用程序代码，并由处理器301来控制执行。处理器301用于执行存储器303中存储的应用程序代码，从而实现本申请下述实施例提供的切换方法。
在具体实现中，作为一种实施例，处理器301可以包括一个或多个CPU，例如图3中的CPU0和CPU1。
在具体实现中，作为一种实施例，通信设备300可以包括多个处理器，例如图3中的处理器301和处理器308。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中，作为一种实施例，通信设备300还可以包括输出设备305和输入设备306。输出设备305和处理器301通信，可以以多种方式来显示信息。例如，输出设备305可以是液晶显示器(liquid crystal display，LCD),发光二级管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备306和处理器301通信，可以以多种方式接受用户的输入。例如，输入设备306可以是鼠标、键盘、触摸屏设备或传感设备等。
上述的通信设备300可以是一个通用通信设备或者是一个专用通信设备。在具体实现中，通信设备300可以是台式机、便携式电脑、网络服务器、掌上电脑(personal digital assistant，PDA)、移动手机、平板电脑、无线终端设备、嵌入式设备或有图3中类似结构的设备。本申请实施例不限定通信设备300的类型。
下面将结合图1至图3对本申请实施例提供的切换方法进行具体阐述。
以图1所示的切换系统应用于图2所示的5G网络为例，假设源AMF实体由于即将关机或者由于缩容等其他原因确定将该源AMF实体提供服务的全部或部分终端迁移到目标AMF，由目标AMF为这些终端提供服务。则如图4所示，为本申请实施例提供的一种切换方法的流程示意图。在该切换方法中，源AMF实体将提供服务的待切换终端中，当前有正在进行的流程的终端的标识列表发送给目标AMF实体，由目标AMF实体在接收目标终端相关的消息之后，根据该标识列表，向源AMF实体发送该目标终端相关的消息。在源AMF实体确定目标终端的流程结束后，源AMF实体通过与目标AMF实体之间的N14接口将目标终端的上下文发送给目标AMF实体，从而可以在保持目标终端的当前流程不中断的前提下，完成目标终端从源AMF实体到目标AMF实体的切换。具体的，该切换方法包括如下步骤：
S401、源AMF实体确定待切换的终端，并且源AMF实体确定为待切换的终端提供服务的目标AMF实体。
其中，本申请实施例中，待切换的终端可能是源AMF实体提供服务的全部终端，也可能是源AMF实体提供服务的部分终端，比如包含相同组标识的一个终端组，本申请实施例对此不作具体限定。
需要说明的是，本申请实施例中，源AMF实体可以基于本地策略或者其他因素将该源AMF实体提供服务的所有终端进行分组，并为每组终端都配置相应的组标识，以便于管理， 这里的组标识可以是源AMF实体的全球唯一AMF标识(globally unique AMF ID，GUMAI)，在此进行统一说明，以下不再赘述。
S402、源AMF实体向目标AMF实体发送待切换的终端中，当前没有正在进行的流程的终端的上下文，以使得目标AMF实体接收该当前没有正在进行的流程的终端的上下文。
可选的，本申请实施例中，目标AMF实体在接收到该当前没有正在进行的流程的终端的上下文之后，可以存储该当前没有正在进行的流程的终端的上下文。
S403、源AMF实体向目标AMF实体发送待切换终端中，当前有正在进行的流程的终端的标识列表，以使得目标AMF实体接收来自源AMF实体的标识列表。
也就是说，在源AMF实体确定的待切换终端中，若某些终端有正在进行的流程，比如，某些终端正在进行重注册流程或者切换流程，则针对这些有流程正在进行的终端，源AMF可以暂时不将这些终端的上下文发送给目标AMF，而是将这些终端的标识发送给目标AMF实体，并通知目标AMF实体这些终端当前由源AMF实体继续为之提供服务。
其中，本申请实施例中，终端的标识可以包括终端的全局唯一临时标识(global unique temporary identity，GUTI)，终端的签约永久标识(subscriber permanent identity，SUPI)，源AMF实体给终端分配的终端的AMF N2应用层协议(N2application protocol，N2AP)终端标识，源AMF实体给终端分配的终端的AMF N2应用层协议(N2application protocol，N2AP)终端标识+终端所在终端组的组标识，接入设备给终端分配的终端的接入设备N2AP终端标识+接入设备标识，或者其他可用标识中的至少一个，本申请实施例对此不作具体限定。
其中，本申请实施例中，上行消息中携带的终端的标识和下行消息中携带的终端的标识为上述终端的标识中的其中一个标识，并且上行消息中携带的终端的标识和下行消息中携带的终端的标识可能不同，比如，上行消息中携带的终端的标识可以包括GUTI，AMF实体给终端分配的终端的AMF N2AP终端标识，终端的AMF N2AP终端标识+终端所在终端组的组标识，终端的接入设备N2AP终端标识+接入设备标识，或者其他可用标识；下行消息中携带的终端的标识可以包括SUPI，GUTI，或者其他可用标识，在此进行统一说明，以下不再赘述。
可选的，本申请实施例中，目标AMF实体接收到标识列表之后，可以存储该标识列表。
可选的，本申请实施例中，目标AMF实体接收到标识列表之后，可以存储标识列表的信息和源AMF实体的信息的对应关系，或者，存储标识列表中的终端的标识和源AMF实体的信息的对应关系，本申请实施例对此不作具体限定。
其中，标识列表的信息例如可以是标识列表的编号；源AMF实体的信息例如可以是源AMF实体的地址或者源AMF实体的名字等，本申请实施例对此不作具体限定。
可选的，本申请实施例中，步骤S403中的标识列表和步骤S402中的终端的上下文可以是通过同一条消息发送给目标AMF实体，也可以是通过不同的消息发送给目标AMF实体，本申请实施例对此不作具体限定。
可选的，本申请实施例中，源AMF实体的信息可以是和步骤S403中的标识列表或者步骤S402中的终端的上下文一起发送给目标AMF实体，比如携带在同一条消息中发送给目标AMF实体或者作为消息的源地址发送给目标AMF实体。当然，源AMF实体的信息也可以是在目标AMF实体中配置，比如在目标AMF实体中配置源AMF实体面向目标AMF实体的IP地址与源AMF实体的信息间的对应关系，进而，目标AMF实体可以根据接收到的携带步骤S403中的标识列表或者步骤S402中的终端的上下文的消息的源IP地址查询上述对应关系，从而获得源AMF实体的信息，本申请实施例对此不作具体限定。
S404、源AMF实体向接入设备发送指示信息1，以使得接入设备接收来自源AMF实体的指示信息1。
其中，该指示信息1用于指示该源AMF实体不可用或者该源AMF实体中的某些组标识不可用。比如，若待切换终端为源AMF实体提供服务的全部终端，则该指示信息1用于指示该源AMF实体不可用；或者，比如，若待切换终端为包含相同组标识的一个终端组，则该指示信息1用于指示该源AMF实体中该终端组的组标识不可用。
需要说明的是，本申请实施例中，组标识不可用具体是指，不再为给组标识对应的终端组中的终端提供服务，在此进行统一说明，以下不再赘述。
S405、源AMF实体向SMF实体发送指示信息1，以使得AMF实体接收来自源AMF实体的指示信息1。
其中，指示信息1的相关描述可参考步骤S404，在此不再赘述。
需要说明的是，本申请实施例中仅是示例性的以源AMF实体向核心网侧的SMF实体发送指示信息1为例进行说明，当然，本申请实施例中的SMF实体也可以替换为其他核心网设备，比如，源AMF实体还可以向UDM实体或者AUSF实体发送该指示信息1，本申请实施例对此不作具体限定。
S406、源AMF实体向接入设备发送为待切换终端服务的目标AMF实体的信息，以使得接入设备接收来自源AMF实体的目标AMF实体的信息。
其中，本申请实施例中，目标AMF实体的信息例如可以是目标AMF实体的地址或者目标AMF实体的名字等，本申请实施例对此不作具体限定。
可选的，为待切换终端服务的目标AMF实体的信息也可以是由目标AMF实体发送给接入设备，本申请实施例对此不作具体限定。
S407、源AMF实体向SMF实体发送为待切换终端服务的目标AMF实体的信息，以使得SMF实体接收来自源AMF实体的目标AMF实体的信息。
其中，目标AMF实体的信息的相关描述可参考步骤S406，在此不再赘述。
可选的，为待切换终端服务的目标AMF实体的信息也可能是由目标AMF实体发送给SMF实体，本申请实施例对此不作具体限定。
需要说明的是，本申请实施例中仅是示例性的以源AMF实体向核心网侧的SMF实体发送目标AMF实体的信息为例进行说明，当然，源AMF实体还可以向除SMF实体之外的其它核心网设备发送该目标AMF实体的信息，比如UDM实体或者AUSF实体等，本申请实施例对此不作具体限定。
可选的，本申请实施例中，步骤S404中的指示信息1和步骤S406中的目标AMF实体的信息可以是通过同一条消息发送给接入设备，也可以是通过不同的消息发送给接入设备，本申请实施例对此不作具体限定。
类似的，本申请实施例中，步骤S405中的指示信息1和步骤S407中的目标AMF实体的信息可以是通过同一条消息发送给SMF实体，也可以是通过不同的消息发送给SMF实体，本申请实施例对此不作具体限定。
S408、接入设备将待切换终端中所有处于连接态的终端的N2接口释放，但保留N3接口。
具体的，接入设备可以根据指示信息1，确定待切换的终端。若指示信息1指示源AMF实体不可用，则表征待切换的终端为该源AMF实体提供服务的所有终端；或者，比如，若指示信息1指示源AMF实体中的某一个组标识不可用，则表征待切换的终端为该源AMF实体提供服务的终端中，该组标识对应的终端组中的终端。
S409、SMF实体将待切换终端中所有处于连接态的终端的N11接口释放。
具体的，SMF实体可以根据指示信息1，确定待切换的终端。若指示信息1指示源AMF实体不可用，则表征待切换的终端为该源AMF实体提供服务的所有终端；或者，比如，若指示信息1指示源AMF实体中的某一个组标识不可用，则表征待切换的终端为该源AMF实体提供服务的终端中，该组标识对应的终端组中的终端。
S410、目标AMF实体接收目标终端相关的消息。
其中，该目标终端相关的消息可以是目标终端相关的上行消息，也可以是目标终端相关的下行消息，具体可参考图1所示的实施例的描述，在此不再赘述。
可选的，本申请实施例中，目标终端相关的消息中携带目标终端的标识。本申请实施例中，目标终端相关的上行消息和目标终端相关的下行消息中携带的目标终端的标识可能并不相同，具体可参考步骤S403中的描述，在此不再赘述。
S411、目标AMF实体根据标识列表，向源AMF实体发送目标终端相关的消息。
可选的，目标AMF实体根据标识列表，向源AMF实体发送目标终端相关的消息，具体可以包括：若标识列表中包括目标终端的标识，目标AMF实体向源AMF实体发送目标终端相关的消息。也就是说，若目标终端在源AMF实体中有正在进行的流程，目标AMF实体会向源AMF实体发送目标终端相关的消息，由源AMF实体继续为该目标终端提供服务，从而可以保持目标终端的当前流程不中断。
可选的，目标AMF实体可以根据目标终端的标识，以及目标终端的标识和源AMF实体的信息的对应关系，确定为目标终端提供服务的源AMF实体。
可选的，在目标AMF实体确定为目标移动管理实体提供服务的源AMF实体之后，可以根据源AMF实体的信息中源AMF实体面向目标AMF实体的地址或者源AMF实体的名称，直接向源AMF实体发送目标终端相关的消息。
或者，可选的，在目标终端相关的消息为上行消息时，在目标AMF实体确定为目标移动管理实体提供服务的源AMF实体之后，可以根据源AMF实体的信息中源AMF实体面向接入设备的地址或者源AMF实体的名称，经过接入设备重定向给源AMF实体；在目标终端相关的消息为下行消息时，在目标AMF实体确定为目标终端提供服务的源AMF实体之后，可以根据源AMF实体的信息中源AMF实体面向SMF实体的地址或者源AMF实体的名称，经过SMF实体重定向给源AMF实体。其中，当经过SMF实体重定向时，目标AMF实体向SMF实体发送源AMF实体的信息。可选的，当经过SMF实体重定向时，目标AMF实体还可以向SMF实体发送指示信息，该指示信息用于指示该源AMF实体的信息只用于该SMF实体发起的本次流程(其中，这里的“流程”也可以叫做事务(transaction))，当本次流程结束后若该SMF实体需要发起新的流程时，该SMF实体仍然将目标终端相关的消息发送给目标AMF实体。
可选的，本申请实施例中，若目标AMF实体直接向源AMF实体发送目标终端相关的消息，则源AMF实体接收到目标终端相关的消息之后，在处理该目标终端相关的消息的过程中，若需要给接入设备或目标终端发送下行消息，源AMF需要在重新建立接入设备与源AMF实体之间的N2接口后，通过重建的N2接口向接入设备或目标终端发送该下行消息。
或者，可选的，本申请实施例中，若目标AMF实体直接向源AMF实体发送目标终端相关的下行消息，则源AMF实体接收到目标终端相关的下行消息之后，在处理该目标终端相关的消息的过程中，若需要给接入设备或目标终端发送下行消息，源AMF实体可以通过目标AMF实体，以及目标AMF实体与接入设备间的N2接口向接入设备或目标终端发送该下 行消息。
或者，可选的，本申请实施例中，若目标AMF实体将目标终端相关的消息经过接入设备重定向给源AMF实体，则源AMF实体接收到目标终端相关的消息之后，在处理该目标终端相关的消息的过程中，若需要给接入设备或目标终端发送下行消息，源AMF可以通过重定向过程中建立的接入设备与源AMF实体间的N2接口向接入设备或目标终端发送下行消息。
可选的，本申请实施例中，若目标AMF实体直接向源AMF实体发送目标终端相关的消息，则源AMF实体接收到目标终端相关的消息之后，在处理该目标终端相关的消息的过程中，若需要给SMF发送上行消息，源AMF需要在重新建立SMF实体与源AMF实体之间的N11接口后，通过重建的N11接口向SMF实体发送该上行消息。
或者，可选的，本申请实施例中，若目标AMF实体直接向源AMF实体发送目标终端相关的消息，则源AMF实体接收到目标终端相关的消息之后，在处理该目标终端相关的消息的过程中，若需要给SMF实体发送上行消息，源AMF实体可以通过目标AMF实体，以及目标AMF实体与SMF实体间的N11接口向SMF实体发送该上行消息。
或者，可选的，本申请实施例中，若目标AMF实体将目标终端相关的消息经过SMF实体重定向给源AMF实体，则源AMF实体接收到目标终端相关的消息之后，在处理该目标终端相关的消息的过程中，若需要给SMF实体发送上行消息，源AMF可以通过重定向过程中建立的SMF实体与源AMF实体间的N11接口向SMF实体发送该上行消息。
S412、源AMF实体确定目标终端的流程结束。
可选的，目标终端的流程结束可以是目标终端当前正在进行的流程结束；也可以是目标终端当前正在进行的流程结束之后的其它流程结束。比如，针对切换流程，若源AMF实体判断目标终端的切换流程结束后需要立即进行重注册以便更新跟踪区(tracking area，TA)列表以及重分配GUTI，则源AMF实体应等待上述重注册流程结束后再将目标终端切换至目标AMF实体。其中，这里的重注册相当于跟踪区更新(tracking area update，TAU)。
S413、源AMF实体向目标AMF实体发送目标终端的上下文，以使得目标终端接收来自源AMF实体的目标终端的上下文。
S414、目标AMF实体接收到目标终端的上下文之后，删除目标终端的标识和源AMF实体的信息的对应关系。
其中，删除目标终端的标识和源AMF实体的信息的对应关系之后，源AMF实体将不再为目标终端提供服务。进而，在目标AMF实体接收目标终端相关的消息之后，可以由目标AMF实体为该目标终端服务，而不是将目标终端相关的消息发送给源AMF实体。
可选的，若目标AMF实体中存储的是标识列表的信息和源AMF实体的信息，此时删除目标终端的标识和源AMF实体的信息的对应关系，具体是指，将目标终端的标识从标识列表中删除。
可选的，若目标AMF实体中存储的是目标终端的标识和源AMF实体的信息，此时删除目标终端的标识和源AMF实体的信息的对应关系，具体是指，删除目标终端的标识和源AMF实体的信息的对应关系这条记录。
S415、若在步骤S411建立了接入设备与源AMF实体的N2接口，目标AMF实体向接入设备发送更新N2接口消息，以使得接入设备接收来自目标AMF实体的更新N2接口消息。该更新N2接口消息用于指示接入设备将目标终端的N2接口更新到目标AMF实体。
可选的，该更新N2接口消息也可能是源AMF实体发送给接入设备，由接入设备根据该更新N2接口消息将目标终端的N2接口更新到目标AMF实体，本申请实施例对此不作具体 限定。
S416、若在步骤S411建立了SMF实体与源AMF实体的N11接口，目标AMF实体向SMF实体发送更新N11接口消息，以使得SMF实体接收来自目标AMF实体的更新N11接口消息。该更新N11接口消息用于指示SMF实体将目标终端的N11接口更新到目标AMF实体。
可选的，该更新N11接口消息也可能是源AMF实体发送给SMF实体，由SMF实体根据该更新N11接口消息将目标终端的N11接口更新到目标AMF实体，本申请实施例对此不作具体限定。
本申请实施例提供的切换方法中，源AMF实体将提供服务的待切换终端中，当前有正在进行的流程的终端的标识列表发送给目标AMF实体，由目标AMF实体在接收目标终端相关的消息之后，根据该标识列表，向源AMF实体发送该目标终端相关的消息。在源AMF实体确定目标终端的流程结束后，源AMF实体通过与目标AMF实体之间的N14接口将目标终端的上下文发送给目标AMF实体，从而可以在保持目标终端的当前流程不中断的前提下，完成目标终端从源AMF实体到目标AMF实体的切换。
其中，上述步骤S401至S416中目标AMF实体的动作可以由图3所示的通信设备300中的处理器301调用存储器303中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
可选的，以图1所示的切换系统应用于图2所示的5G网络为例，假设源AMF实体由于即将关机或者由于缩容等其他原因确定将该源AMF实体提供服务的全部或部分终端迁移到目标AMF，由目标AMF为这些终端提供服务。则如图5所示，为本申请实施例提供的一种切换方法的流程示意图。在该切换方法中，目标AMF实体在接收目标终端相关的消息之后，根据目标终端相关的消息中携带的目标终端的标识，查找目标终端的上下文；若查找不到目标终端的上下文，向源AMF实体发送该目标终端相关的消息。在源AMF实体确定目标终端的流程结束后，源AMF实体通过与目标AMF实体之间的N14接口将目标终端的上下文发送给目标AMF实体，从而可以在保持目标终端的当前流程不中断的前提下，完成目标终端从源AMF实体到目标AMF实体的切换。具体的，该切换方法包括如下步骤：
S501、同步骤S401，具体可参考图4所示的实施例，在此不再赘述。
S502、源AMF实体向目标AMF实体发送待切换的终端中，当前没有正在进行的流程的终端的上下文，以使得目标AMF实体接收该当前没有正在进行的流程的终端的上下文。
可选的，本申请实施例中，目标AMF实体在接收到该当前没有正在进行的流程的终端的上下文之后，可以存储该当前没有正在进行的流程的终端的上下文。
可选的，本申请实施例中，当前没有正在进行的流程的终端的上下文中包括至少一个终端组的组标识。其中，每个终端的上下文中包括该终端所在终端组的组标识，这样，目标AMF实体在接收到该当前没有正在进行的流程的终端的上下文之后，可以存储至少一个终端组的组标识和源AMF实体的信息的对应关系。
可选的，本申请实施例中，源AMF实体的信息可以是和终端的上下文一起发送给目标AMF实体，比如携带在同一条消息中发送给目标AMF实体或者作为消息的源地址发送给目标AMF实体。当然，源AMF实体的信息也可以是在目标AMF实体中配置，比如在目标AMF实体中配置源AMF实体面向目标AMF实体的IP地址与源AMF实体的信息间的对应关系，进而，目标AMF实体可以根据接收到的携带步骤S502中的终端的上下文的消息的源IP地址查询上述对应关系，从而获得源AMF实体的信息，本申请实施例对此不作具体限定。
S503-S508、同S404-S409，具体可参考图4所示的实施例，在此不再赘述。
S509、目标AMF实体接收目标终端相关的消息。
其中，该目标终端相关的消息的描述可参考步骤S410，在此不再赘述。
可选的，本申请实施例中，目标终端相关的消息中携带目标终端的标识。本申请实施例中，目标终端相关的上行消息和目标终端相关的下行消息中携带的目标终端的标识可能并不相同，具体可参考步骤S403中的描述，在此不再赘述。
可选的，本申请实施例中，目标终端相关的消息中携带目标终端所在终端组的组标识。
S510、目标AMF实体根据目标终端的标识，查找目标终端的上下文。
S511、若查找不到，目标AMF实体向源AMF实体发送目标终端相关的消息，以使得源AMF实体接收来自目标AMF实体的目标终端相关的消息。
或者，可选的，本申请实施例中，若目标AMF实体查找不到目标终端的上下文，且至少一个终端组的组标识中包括目标终端所在终端组的组标识，目标AMF实体向源AMF实体发送目标终端相关的消息。也就是说，若目标终端在源AMF实体中有正在进行的流程，目标AMF实体会向源AMF实体发送目标终端相关的消息，由源AMF实体继续为该目标终端提供服务，从而可以保持目标终端的当前流程不中断。
需要说明的是，本申请实施例中，目标AMF实体可以是在查找不到目标终端的上下文之后，才确定至少一个终端组的组标识中是否包括目标终端所在终端组的组标识；也可以是在确定至少一个终端组的组标识中包括目标终端所在终端组的组标识之后，才查找目标终端的上下文，本申请实施例对此不作具体限定。
可选的，目标AMF实体可以根据目标终端所在终端组的组标识，以及目标终端所在终端组的组标识和源AMF实体的信息的对应关系，确定为目标移动管理实体提供服务的源AMF实体。
可选的，目标AMF实体向源AMF实体发送目标终端相关的消息的具体实现可参考步骤S411，在此不再赘述。
S512-S513、同S412-S413，具体可参考图4所示的实施例，在此不再赘述。
S514-S515、同S415-S416，具体可参考图4所示的实施例，在此不再赘述。
本申请实施例提供的切换方法中，目标AMF实体在接收目标终端相关的消息之后，根据目标终端相关的消息中携带的目标终端的标识，查找目标终端的上下文；若查找不到目标终端的上下文，向源AMF实体发送该目标终端相关的消息。在源AMF实体确定目标终端的流程结束后，源AMF实体通过与目标AMF实体之间的N14接口将目标终端的上下文发送给目标AMF实体，从而可以在保持目标终端的当前流程不中断的前提下，完成目标终端从源AMF实体到目标AMF实体的切换。
其中，上述步骤S501至S515中目标AMF实体的动作可以由图3所示的通信设备300中的处理器301调用存储器303中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
可选的，以图1所示的切换系统应用于图2所示的5G网络为例，假设源AMF实体由于即将关机或者由于缩容等其他原因确定将该源AMF实体提供服务的全部或部分终端迁移到目标AMF，由目标AMF为这些终端提供服务。则如图6所示，为本申请实施例提供的一种切换方法的流程示意图。在该切换方法中，目标AMF实体在接收目标终端相关的消息之后，根据目标终端相关的消息中携带的目标终端的标识，从UDSF实体中读取目标终端的上下文；若目标终端当前由源AMF实体服务，也就是说目标终端当前有正在进行的流程，则UDSF 实体向目标AMF实体发送源AMF实体的信息，进而目标AMF实体可以根据源AMF实体的信息，向源AMF实体发送该目标终端相关的消息。在源AMF实体确定目标终端的流程结束后，源AMF实体通过与目标AMF实体之间的N14接口将目标终端的上下文发送给目标AMF实体，或者源AMF实体将目标终端的上下文保存到UDSF实体，从而可以在保持目标终端的当前流程不中断的前提下，完成目标终端从源AMF实体到目标AMF实体的切换。具体的，该切换方法包括如下步骤：
S601、目标终端注册到源AMF实体。
其中，目标终端注册到源AMF实体的具体流程可参考现有的实现方式，在此不再赘述。
S602、源AMF实体注册到UDSF实体。
其中，源AMF实体注册到UDSF实体，具体是指，源AMF实体在UDSF实体中将自己注册为目标终端的服务AMF。
其中，源AMF实体注册到UDSF实体的具体流程可参考现有的实现方式，在此不再赘述。
S603、源AMF实体确定待切换的终端。
其中，待切换的终端的相关描述可参考步骤S401，在此不再赘述。
其中，待切换的终端注册到源AMF实体，以及源AMF实体注册到UDSF实体的相关描述可参考步骤S601中待切换的终端注册到源AMF实体，以及步骤S602中源AMF实体注册到UDSF实体的描述，在此不再赘述。
S604、源AMF实体向UDSF实体发送待切换的终端中，当前没有正在进行的流程的终端的上下文，以使得UDSF实体接收该当前没有正在进行的流程的终端的上下文。
可选的，本申请实施例中，UDSF实体在接收到该当前没有正在进行的流程的终端的上下文之后，可以存储该当前没有正在进行的流程的终端的上下文。
可选的，本申请实施例中，源AMF实体向UDSF实体发送的待切换的终端中，当前没有正在进行的流程的终端的上下文中可以仅包括该终端最新的上下文，即相对于该终端上次发送给UDSF实体的该终端的上下文有变化的上下文。当前，若源AMF实体在之前已经将待切换的终端中，当前没有正在进行的流程的终端的最新上下文发送给UDSF实体，则源AMF实体在这一步不需要将该终端的上下文再发送给UDSF实体。
S605、源AMF实体向UDSF实体发送指示信息2，以使得UDSF实体接收来自源AMF实体的指示信息2。该指示信息2用于指示UDSF实体删除源AMF实体作为当前没有正在进行的流程的终端的服务AMF实体的信息。
S606、UDSF实体根据指示信息2，删除源AMF实体作为该当前没有正在进行的流程的终端的服务AMF的信息。
可选的，本申请实施例中，步骤S604中终端的上下文和步骤S605中的指示信息2可以是通过同一条消息发送给UDSF实体，也可以是通过不同的消息发送给UDSF实体，本申请实施例对此不作具体限定。
S607-S608、同S404-S405，具体可参考图4所示的实施例，在此不再赘述。
S609-S610、同S408-S409，具体可参考图4所示的实施例，在此不再赘述。
S611、同S410，具体可参考图4所示的实施例，在此不再赘述。
其中，与图4和图5所示的实施例的区别在于，图4和图5所示的实施例中，由源AMF实体确定为待切换的终端提供服务的目标AMF实体；而本申请实施例中，接入设备或者SMF实体在向目标AMF实体发送目标终端相关的消息之前，首先为目标终端选择目标AMF实体。
S612、目标AMF实体根据目标终端的标识，从UDSF实体中读取目标终端的上下文。
S613、若目标终端当前由源AMF继续服务，UDSF实体向目标AMF实体发送源AMF实体的信息，以使得目标AMF实体接收来自UDSF实体的源AMF的消息。
S614、目标AMF实体根据源AMF实体的信息，向源AMF实体发送目标终端相关的消息，以使得源AMF实体接收来自目标AMF实体的目标终端相关的消息。
可选的，目标AMF实体向源AMF实体发送目标终端相关的消息的具体实现可参考步骤S411，在此不再赘述。
其中，当经过SMF实体重定向时，目标AMF实体向SMF实体发送源AMF实体的信息。可选的，当经过SMF实体重定向时，目标AMF实体还可以向SMF实体发送指示信息，该指示信息用于指示该源AMF实体的信息只用于该SMF实体发起的本次流程，当本次流程结束后若该SMF实体需要发起新的流程时，该SMF实体为目标终端重新选择AMF实体后，将目标终端相关的消息发送给为该目标终端重新选择的AMF实体。
S615-S616、同S412-S413，具体可参考图4所示的实施例，在此不再赘述。
S617-S618、同S415-S416，具体可参考图4所示的实施例，在此不再赘述。
可选的，本申请实施例中的步骤S617和S618可以用如下方案替换：
源AMF实体将目标终端的上下文保存到UDSF实体中，并且删除源AMF实体作为该目标终端的服务AMF的信息；同时，源AMF实体通知接入设备释放该目标终端的N2接口，保留N3接口；以及，源AMF实体通知SMF实体释放该目标终端的N11接口。
本申请实施例提供的切换方法中，目标AMF实体在接收目标终端相关的消息之后，根据目标终端相关的消息中携带的目标终端的标识，从UDSF实体中读取目标终端的上下文；若目标终端当前由源AMF实体服务，也就是说目标终端当前有正在进行的流程，则UDSF实体向目标AMF实体发送源AMF实体的信息，进而目标AMF实体可以根据源AMF实体的信息，向源AMF实体发送该目标终端相关的消息。在源AMF实体确定目标终端的流程结束后，源AMF实体通过与目标AMF实体之间的N14接口将目标终端的上下文发送给目标AMF实体，或者源AMF实体将目标终端的上下文保存到UDSF实体，从而可以在保持目标终端的当前流程不中断的前提下，完成目标终端从源AMF实体到目标AMF实体的切换。
其中，上述步骤S601至S617中目标AMF实体的动作可以由图3所示的通信设备300中的处理器301调用存储器303中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，上述目标移动管理实体为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对目标移动管理实体进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
比如，在采用对应各个功能划分各个功能模块的情况下，图7示出了上述实施例中所涉及的目标移动管理实体70的一种可能的结构示意图。该目标移动管理实体70包括接收模块701和发送模块702。接收模块701，用于接收目标终端相关的消息。发送模块702，用于向当前为目标终端提供服务的源移动管理实体发送目标终端相关的消息。
可选的，接收模块701，还用于接收来自源移动管理实体的标识列表，该标识列表为源移动管理实体提供服务的待切换终端中，当前有正在进行的流程的终端的标识列表。发送模块702具体用于：根据标识列表，向当前为目标终端提供服务的源移动管理实体发送目标终端相关的消息。
可选的，目标终端相关的消息中携带目标终端的标识。相应的，发送模块702具体用于：若标识列表中包括目标终端的标识，向当前为目标终端提供服务的源移动管理实体发送目标终端相关的消息。
可选的，如图7所示，目标终端相关的消息中携带目标终端的标识。相应的，目标移动管理实体70还包括：确定模块703。确定模块703，用于根据目标终端的标识，以及目标终端的标识和源移动管理实体的信息的对应关系，确定为目标终端提供服务的源移动管理实体。
可选的，如图7所示，目标移动管理实体70还可以包括：删除模块704。删除模块704，用于在接收模块701接收到目标终端的上下文之后，删除目标终端的标识和源移动管理实体的信息的对应关系。
可选的，目标终端相关的消息中携带目标终端的标识。相应的，发送模块702具体用于：根据目标终端的标识，查找目标终端的上下文；若未查找到目标终端的上下文，向当前为目标终端提供服务的源移动管理实体发送目标终端相关的消息。
可选的，目标终端相关的消息中携带目标终端所在终端组的组标识。接收模块701，还用于接收来自源移动管理实体的至少一个终端的上下文，至少一个终端的上下文中包括至少一个终端组的组标识，其中，至少一个终端的上下文中每个终端的上下文包括该终端所在终端组的组标识；发送模块702具体用于：若未查找到目标终端的上下文，且至少一个终端组的组标识中包括目标终端所在终端组的组标识，向当前为目标终端提供服务的源移动管理实体发送目标终端相关的消息。
可选的，目标终端相关的消息携带目标终端所在终端组的组标识。相应的，如图7所示，目标移动管理实体70还包括：确定模块703。确定模块703，用于根据目标终端所在终端组的组标识以及目标终端所在终端组的组标识和源移动管理实体的信息的对应关系，确定为目标终端提供服务的源移动管理实体。
可选的，接收模块701，还用于接收来自源移动管理实体的源移动管理实体的信息。
可选的，确定模块703，还用于根据配置信息确定源移动管理实体的信息。
可选的，目标终端相关的消息为下行消息；发送模块702具体用于：向会话管理实体发送目标终端相关的消息以及当前为目标终端提供服务的源移动管理实体的信息，源移动管理实体的信息用于会话管理实体向源移动管理实体发送目标终端相关的消息。
可选的，发送模块702，还用于向会话管理实体发送指示信息，该指示信息用于指示源移动管理实体的信息只用于会话管理实体发起的本次流程。
以采用集成的方式划分各个功能模块的情况下，图8示出了上述实施例中所涉及的目标移动管理实体80的一种可能的结构示意图，该目标移动管理实体80包括：通信模块801。可选的，该目标移动管理实体80还可以包括处理模块802。其中，该通信模块801可用于执行图7中接收模块701和发送模块702所能执行的操作；该处理模块802可用于执行图7中 确定模块703、删除模块704所能执行的操作，具体可参考图7所示的实施例，本申请实施例在此不再赘述。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该目标移动管理实体以对应各个功能划分各个功能模块的形式来呈现，或者，该目标移动管理实体以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定应用集成电路(Application-Specific Integrated Circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到目标移动管理实体70或者目标移动管理实体80可以采用图3所示的形式。比如，图7中的接收模块701、发送模块702、确定模块703和删除模块704可以通过图3的处理器301和存储器303来实现。具体的，接收模块701、发送模块702、确定模块703和删除模块704可以通过由处理器301来调用存储器303中存储的应用程序代码来执行，本申请实施例对此不作任何限制。或者，比如，图8中的处理模块802和通信模块801可以通过图3的处理器301和存储器303来实现。具体的，处理模块802和通信模块801可以通过由处理器301来调用存储器303中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
由于本申请实施例提供的目标移动管理实体可用于执行上述切换方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
可选的，本申请实施例提供了一种芯片系统，该芯片系统包括处理器，用于支持目标移动管理实体实现上述方面中所涉及的功能，例如接收目标终端相关的消息，并向源移动管理实体发送目标终端相关的消息。在一种可能的设计中，该芯片系统还包括存储器。该存储器，用于保存目标移动管理实体必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (29)

  1. 一种切换方法，其特征在于，所述方法包括：
    目标移动管理实体接收目标终端相关的消息；
    所述目标移动管理实体向当前为所述目标终端提供服务的源移动管理实体发送目标终端相关的消息。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述目标移动管理实体接收来自所述源移动管理实体的标识列表，所述标识列表为所述源移动管理实体提供服务的待切换终端中，当前有正在进行的流程的终端的标识列表；
    所述目标移动管理实体向当前为所述目标终端提供服务的源移动管理实体发送所述目标终端相关的消息，包括：
    所述目标移动管理实体根据所述标识列表，向当前为所述目标终端提供服务的源移动管理实体发送所述目标终端相关的消息。
  3. 根据权利要求2所述的方法，其特征在于，所述目标终端相关的消息中携带所述目标终端的标识；
    所述目标移动管理实体根据所述标识列表，向当前为所述目标终端提供服务的源移动管理实体发送所述目标终端相关的消息，包括：
    若所述标识列表中包括所述目标终端的标识，所述目标移动管理实体向当前为所述目标终端提供服务的源移动管理实体发送所述目标终端相关的消息。
  4. 根据权利要求2或3所述的方法，其特征在于，所述目标终端相关的消息中携带所述目标终端的标识；所述方法还包括：
    所述目标移动管理实体根据所述目标终端的标识，以及所述目标终端的标识和所述源移动管理实体的信息的对应关系，确定为所述目标终端提供服务的所述源移动管理实体。
  5. 根据权利要求2-4任一项所述的方法，其特征在于，所述方法还包括：
    在所述目标移动管理实体接收到所述目标终端的上下文之后，所述目标移动管理删除所述目标终端的标识和所述源移动管理实体的信息的对应关系。
  6. 根据权利要求1所述的方法，其特征在于，所述目标终端相关的消息中携带所述目标终端的标识；
    所述目标移动管理实体向当前为所述目标终端提供服务的源移动管理实体发送所述目标终端相关的消息，包括：
    所述目标移动管理实体根据所述目标终端的标识，查找所述目标终端的上下文；
    若所述目标移动管理实体未查找到所述目标终端的上下文，所述目标移动管理实体向当前为所述目标终端提供服务的源移动管理实体发送所述目标终端相关的消息。
  7. 根据权利要求6所述的方法，其特征在于，所述目标终端相关的消息中携带所述目标终端所在终端组的组标识；所述方法还包括：
    所述目标移动管理实体接收来自所述源移动管理实体的至少一个终端的上下文，所述至少一个终端的上下文中包括至少一个终端组的组标识，其中，所述至少一个终端的上下文中每个终端的上下文包括该终端所在终端组的组标识；
    若所述目标移动管理实体未查找到所述目标终端的上下文，所述目标移动管理实体向当前为所述目标终端提供服务的源移动管理实体发送所述目标终端相关的消息，包括：
    若所述目标移动管理实体未查找到所述目标终端的上下文，且所述至少一个终端组的组标识中包括所述目标终端所在终端组的组标识，所述目标移动管理实体向当前为所述目标终端提供服务的源移动管理实体发送所述目标终端相关的消息。
  8. 根据权利要求6或7所述的方法，其特征在于，所述目标终端相关的消息携带所述目标终端所在终端组的组标识；所述方法还包括：
    所述目标移动管理实体根据所述目标终端所在终端组的组标识以及所述目标终端所在终端组的组标识和所述源移动管理实体的信息的对应关系，确定为所述目标终端提供服务的所述源移动管理实体。
  9. 根据权利要求1-8任一项所述的方法，其特征在于，所述方法还包括：
    所述目标移动管理实体接收来自所述源移动管理实体的所述源移动管理实体的信息；或者，所述目标移动管理实体根据配置信息确定所述源移动管理实体的信息。
  10. 根据权利要求1-9任一项所述的方法，其特征在于，所述目标终端相关的消息为下行消息；所述目标移动管理实体向当前为所述目标终端提供服务的源移动管理实体发送目标终端相关的消息，包括：
    所述目标移动管理实体经过核心网设备重定向目标终端相关的消息给所述源移动管理实体。
  11. 根据权利要求10所述的方法，其特征在于，所述目标移动管理实体经过会话管理实体重定向目标终端相关的消息给所述源移动管理实体包括：
    所述目标移动管理实体向所述核心网设备发送当前为所述目标终端提供服务的源移动管理实体的信息，其中，所述源移动管理实体的信息用于使所述核心网设备向所述源移动管理实体发送目标终端相关的消息。
  12. 根据权利要求10或11所述的方法，其特征在于，所述方法还包括：
    所述目标移动管理实体向所述核心网设备发送指示信息，所述指示信息用于指示所述源移动管理实体的信息只用于所述核心网设备发起的本次流程。
  13. 根据权利要求10-12任一所述的方法，其特征在于，所述核心网设备为会话管理实体；或，统一数据管理实体；或，鉴权服务器功能实体。
  14. 一种切换方法，其特征在于，所述方法包括：
    源移动管理实体获取所述源移动管理实体提供服务的待切换终端中，当前有正在进行的流程的终端的标识列表；
    所述源移动管理实体向目标移动管理实体发送所述标识列表；
    所述目标移动管理实体接收来自所述源移动管理实体的所述标识列表；
    在所述目标移动管理实体接收到目标终端相关的消息之后，所述目标移动管理实体根据所述标识列表，向所述源移动管理实体发送所述目标终端相关的消息。
  15. 一种目标移动管理实体，其特征在于，所述目标移动管理实体包括：接收模块和发送模块；
    所述接收模块，用于接收目标终端相关的消息；
    所述发送模块，用于向当前为所述目标终端提供服务的源移动管理实体发送目标终端相关的消息。
  16. 根据权利要求15所述的目标移动管理实体，其特征在于，
    所述接收模块，还用于接收来自所述源移动管理实体的标识列表，所述标识列表为所述源移动管理实体提供服务的待切换终端中，当前有正在进行的流程的终端的标识列表；
    所述发送模块具体用于：
    根据所述标识列表，向当前为所述目标终端提供服务的源移动管理实体发送所述目标终端相关的消息。
  17. 根据权利要求16所述的目标移动管理实体，其特征在于，所述目标终端相关的消息中携带所述目标终端的标识；
    所述发送模块具体用于：
    若所述标识列表中包括所述目标终端的标识，向当前为所述目标终端提供服务的源移动管理实体发送所述目标终端相关的消息。
  18. 根据权利要求16或17所述的目标移动管理实体，其特征在于，所述目标终端相关的消息中携带所述目标终端的标识；所述目标移动管理实体还包括：确定模块；
    所述确定模块，用于根据所述目标终端的标识，以及所述目标终端的标识和所述源移动管理实体的信息的对应关系，确定为所述目标终端提供服务的所述源移动管理实体。
  19. 根据权利要求16-18任一项所述的目标移动管理实体，其特征在于，所述目标移动管理实体还包括：删除模块；
    所述删除模块，用于在所述接收模块接收到所述目标终端的上下文之后，删除所述目标终端的标识和所述源移动管理实体的信息的对应关系。
  20. 根据权利要求15所述的目标移动管理实体，其特征在于，所述目标终端相关的消息中携带所述目标终端的标识；
    所述发送模块具体用于：
    根据所述目标终端的标识，查找所述目标终端的上下文；
    若未查找到所述目标终端的上下文，向当前为所述目标终端提供服务的源移动管理实体发送所述目标终端相关的消息。
  21. 根据权利要求20所述的目标移动管理实体，其特征在于，所述目标终端相关的消息中携带所述目标终端所在终端组的组标识；
    所述接收模块，还用于接收来自所述源移动管理实体的至少一个终端的上下文，所述至少一个终端的上下文中包括至少一个终端组的组标识，其中，所述至少一个终端的上下文中每个终端的上下文包括该终端所在终端组的组标识；
    所述发送模块具体用于：
    若未查找到所述目标终端的上下文，且所述至少一个终端组的组标识中包括所述目标终端所在终端组的组标识，向当前为所述目标终端提供服务的源移动管理实体发送所述目标终端相关的消息。
  22. 根据权利要求20或21所述的目标移动管理实体，其特征在于，所述目标终端相关的消息携带所述目标终端所在终端组的组标识；所述目标移动管理实体还包括：确定模块；
    所述确定模块，用于根据所述目标终端所在终端组的组标识以及所述目标终端所在终端组的组标识和所述源移动管理实体的信息的对应关系，确定为所述目标终端提供服务的所述源移动管理实体。
  23. 根据权利要求15-22任一项所述的目标移动管理实体，其特征在于，
    所述接收模块，还用于接收来自所述源移动管理实体的所述源移动管理实体的信息；
    或者，所述目标移动管理实体还包括确定模块；
    所述确定模块，用于根据配置信息确定所述源移动管理实体的信息。
  24. 根据权利要求15-23任一项所述的目标移动管理实体，其特征在于，所述目标终端 相关的消息为下行消息；所述发送模块用于向当前为所述目标终端提供服务的源移动管理实体发送目标终端相关的消息具体包括：经过核心网设备重定向目标终端相关的消息给所述源移动管理实体。
  25. 根据权利要求24所述的目标移动管理实体，其特征在于，所述发送模块用于经过核心网设备重定向目标终端相关的消息给所述源移动管理实体具体包括：所述目标移动管理实体向所述核心网设备发送当前为所述目标终端提供服务的源移动管理实体的信息，其中，所述源移动管理实体的信息用于使所述核心网设备向所述源移动管理实体发送目标终端相关的消息。
  26. 根据权利要求24或25所述的目标移动管理实体，其特征在于，
    所述发送模块，还用于向所述会话管理实体发送指示信息，所述指示信息用于指示所述源移动管理实体的信息只用于所述会话管理实体发起的本次流程。
  27. 一种目标移动管理实体，其特征在于，包括：处理器、存储器；
    所述存储器用于存储计算机执行指令，当所述目标移动管理实体运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述目标移动管理实体执行如权利要求1-13中任意一项所述的切换方法。
  28. 一种切换系统，其特征在于，所述切换系统包括：源移动管理实体和目标移动管理实体；
    所述源移动管理实体，用于获取所述源移动管理实体提供服务的待切换终端中，当前有正在进行的流程的终端的标识列表；
    所述源移动管理实体，还用于向目标移动管理实体发送所述标识列表；
    所述目标移动管理实体，用于接收来自所述源移动管理实体的所述标识列表；
    所述目标移动管理实体，还用于在接收到目标终端相关的消息之后，根据所述标识列表，向所述源移动管理实体发送所述目标终端相关的消息。
  29. 一种计算机可读存储介质，其特征在于，包括：该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行如权利要求1-13中任意一项所述的切换方法。
PCT/CN2018/096203 2017-07-20 2018-07-19 切换方法、设备及系统 WO2019015627A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
BR112020000957-1A BR112020000957A2 (pt) 2017-07-20 2018-07-19 método, dispositivo e sistema de transferência
EP21184198.6A EP3958601A3 (en) 2017-07-20 2018-07-19 Handover method, device, and system
EP18835449.2A EP3629612B1 (en) 2017-07-20 2018-07-19 Handover method, apparatus and system
KR1020197038557A KR102268412B1 (ko) 2017-07-20 2018-07-19 핸드오버 방법, 디바이스 및 시스템
JP2020501165A JP7145197B2 (ja) 2017-07-20 2018-07-19 ハンドオーバ方法、デバイス及びシステム
US16/709,362 US11160004B2 (en) 2017-07-20 2019-12-10 Handover method, device, and system
US17/478,199 US11716667B2 (en) 2017-07-20 2021-09-17 Handover method, device, and system

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201710597349.1 2017-07-20
CN201710597349 2017-07-20
CN201710953564.0 2017-10-13
CN201710953564.0A CN109429219B (zh) 2017-07-20 2017-10-13 切换方法、设备及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/709,362 Continuation US11160004B2 (en) 2017-07-20 2019-12-10 Handover method, device, and system

Publications (1)

Publication Number Publication Date
WO2019015627A1 true WO2019015627A1 (zh) 2019-01-24

Family

ID=65015031

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/096203 WO2019015627A1 (zh) 2017-07-20 2018-07-19 切换方法、设备及系统

Country Status (1)

Country Link
WO (1) WO2019015627A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100311419A1 (en) * 2009-06-04 2010-12-09 Motorola, Inc. Mobility Management Entity Tracking for Group Mobility in Wireless Communication Network
CN103002530A (zh) * 2011-09-08 2013-03-27 华为技术有限公司 用于切换到服务网络的方法和设备
CN102714838B (zh) * 2010-01-08 2014-06-25 上海贝尔股份有限公司 机器型通信中基于组的移动性优化方法和设备
WO2016114611A1 (ko) * 2015-01-14 2016-07-21 엘지전자(주) 무선 통신 시스템에서 영역 업데이트 방법 및 이를 위한 장치
CN106211244A (zh) * 2015-05-07 2016-12-07 中兴通讯股份有限公司 一种实现蜂窝网络重定位的方法和基站
WO2017190296A1 (zh) * 2016-05-04 2017-11-09 华为技术有限公司 切换用户设备方法及设备

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100311419A1 (en) * 2009-06-04 2010-12-09 Motorola, Inc. Mobility Management Entity Tracking for Group Mobility in Wireless Communication Network
CN102714838B (zh) * 2010-01-08 2014-06-25 上海贝尔股份有限公司 机器型通信中基于组的移动性优化方法和设备
CN103002530A (zh) * 2011-09-08 2013-03-27 华为技术有限公司 用于切换到服务网络的方法和设备
WO2016114611A1 (ko) * 2015-01-14 2016-07-21 엘지전자(주) 무선 통신 시스템에서 영역 업데이트 방법 및 이를 위한 장치
CN106211244A (zh) * 2015-05-07 2016-12-07 中兴通讯股份有限公司 一种实现蜂窝网络重定位的方法和基站
WO2017190296A1 (zh) * 2016-05-04 2017-11-09 华为技术有限公司 切换用户设备方法及设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3629612A4 *

Similar Documents

Publication Publication Date Title
KR102138002B1 (ko) 세션 관리 기능 엔티티 선택 방법, 장치, 및 시스템
CN110035423B (zh) 会话管理方法、设备及系统
EP4297499A2 (en) Session establishment method and apparatus
JP6855575B2 (ja) ネットワーク間変更方法および装置、ならびに関連デバイス
KR102313165B1 (ko) 데이터 송신 방법, 디바이스 및 시스템
WO2019001204A1 (zh) 切片选择方法和装置
JP2021108500A (ja) 負荷再配置方法、装置、およびシステム
WO2019137553A1 (zh) 一种配置ue的策略的方法、装置和系统
JP2020537466A (ja) セッション確立方法およびシステム、ならびにデバイス
US20230072956A1 (en) Slice access method, apparatus, and system
US11716667B2 (en) Handover method, device, and system
WO2019137125A1 (zh) 会话管理方法、设备及系统
WO2018214597A1 (zh) 接入网类型选择方法、设备及系统
WO2018161281A1 (zh) 通信方法及装置
WO2019024747A1 (zh) 通信方法、设备及系统
WO2019184723A1 (zh) 策略和计费控制规则获取方法、装置及系统
WO2019223702A1 (zh) 管理pdu会话的方法、装置和系统
US20230188965A1 (en) Application Relocation Method and Apparatus
WO2019137521A1 (zh) 会话管理方法、设备及系统
WO2019015627A1 (zh) 切换方法、设备及系统
CN110708727B (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: 18835449

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20197038557

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2020501165

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018835449

Country of ref document: EP

Effective date: 20191227

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112020000957

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112020000957

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20200116