WO2019024747A1 - 通信方法、设备及系统 - Google Patents

通信方法、设备及系统 Download PDF

Info

Publication number
WO2019024747A1
WO2019024747A1 PCT/CN2018/097138 CN2018097138W WO2019024747A1 WO 2019024747 A1 WO2019024747 A1 WO 2019024747A1 CN 2018097138 W CN2018097138 W CN 2018097138W WO 2019024747 A1 WO2019024747 A1 WO 2019024747A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
mobility management
management entity
entity
group
Prior art date
Application number
PCT/CN2018/097138
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
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP21194902.9A priority Critical patent/EP4007437B1/en
Priority to EP18840816.5A priority patent/EP3657869B1/en
Priority to BR112020002055-9A priority patent/BR112020002055A2/pt
Publication of WO2019024747A1 publication Critical patent/WO2019024747A1/zh
Priority to US16/748,340 priority patent/US11184757B2/en
Priority to US17/478,218 priority patent/US11968743B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/06—Registration at serving network Location Register, VLR or user mobility server
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/186—Processing of subscriber group data

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a communication method, device, and system.
  • an access and mobility management function (AMF) entity determines that the terminal is no longer served, the AMF entity provides a radio access network (RAN) device and other core networks.
  • a network functional entity such as a session management function (SMF) entity, sends an "unavailable" indication that the AMF entity is marked as invalid by the RAN device and other core network functional entities.
  • SMF session management function
  • the AMF entity is no longer considered when subsequently selecting an AMF entity.
  • the AMF fails and the context of the terminal being served by the failed AMF entity is not backed up, the network connection of these terminals will be lost, and the subsequent re-registration process needs to be initiated.
  • one method is to back up the context of the terminal to an unstructured data storage function (UDSF) entity, so that when the AMF entity fails, the RAN device or other core network function entity reselects one.
  • the non-failed target AMF entity continues to serve the terminal, and the target AMF entity reads the context of the terminal from the UDSF entity so that the terminal can continue to be served without requiring the terminal to initiate a re-registration procedure.
  • UDSF unstructured data storage function
  • the above solution relies on the UDSF entity, thus restricting a group of AMF entities that are mutually backup relationships from the same vendor.
  • the AMF entities that are in the backup relationship are from different vendors, the data format between the AMF entity and the UDSF entity of different vendors is not standardized, which may result in the loss of the context of the terminal being served by the failed AMF entity, thereby triggering the re-registration of the terminal. Process.
  • the embodiment of the present application provides a communication method, device, and system, which can prevent a re-registration process of a terminal from being triggered due to a context loss of a terminal being served when the mobility management entity fails.
  • the embodiment of the present application provides the following technical solutions:
  • the first aspect provides a communication method, where the method includes: acquiring, by the communication device, a first group identifier of a terminal group where the first terminal of the first mobility management entity service is located; and if the first mobility management entity is abnormal, The communication device sends the first terminal related message to the second mobility management entity according to the first group identity, where the second mobility management entity is a mobility management entity that has the context of the first terminal. Based on the solution, the first mobility management entity may synchronize the context of the first terminal of the service to the second mobility management entity, and in the case that the first mobility management entity is abnormal, may be based on the first group of the terminal group where the first terminal is located.
  • the group identifier sends a message related to the first terminal to the second mobility management entity, so that if the first mobility management entity is abnormal, the process of re-registering the terminal may be avoided due to the context loss of the terminal being served.
  • the current process of maintaining the terminal being served is not interrupted.
  • the first group identifier is a primary group identifier configured in the first mobility management entity, and a backup group identifier configured in the second mobility management entity.
  • the primary group identifier in the embodiment of the present application is used to indicate that, in the case that the mobility management entity that configures the primary group identifier is not abnormal, the group identifier of the terminal group where the terminal is located is the primary group identifier.
  • the identified mobility management entity provides the service; the backup group identifier in the embodiment of the present application is used to indicate that the group identity of the terminal group where the terminal is located is the abnormality when the mobility management entity configured with the backup group identifier is configured as the primary group identifier
  • the terminal identified by the backup group is served by the mobility management entity that configures the backup group identifier as the backup group identifier.
  • the method further includes: the communication device receiving the first indication message, where the first indication message is used to indicate that the terminal in the terminal group corresponding to the first group identifier is served by the second mobility management entity .
  • the receiving, by the communications device, the first indication message includes: the communications device receiving the first indication message from the second mobility management entity, wherein the first indication message is determined by the second mobility management entity A transmission management entity sends an exception to the communication device. That is to say, the second mobility management entity notifies the communication device that the terminal in the terminal group corresponding to the first group identifier is served by the second mobility management entity, if the first mobility management entity determines that the first mobility management entity is abnormal. In this way, the communications device can send the first terminal related message to the second mobility management entity according to the first indication message and the first group identifier.
  • the method further includes: the communication device receiving the first indication message, where the first indication message is used to indicate that the first group of identifiers corresponds to the first mobility management entity The terminal in the terminal group is served by the second mobility management entity.
  • the receiving, by the communications device, the first indication message includes: before the first mobility management entity generates an abnormality, the communications device receives the first indication message; if an abnormality occurs in the first mobility management entity, Sending, by the communication device, the message related to the first terminal to the second mobility management entity, according to the first group identifier, the communication device determining that the first mobility management entity is abnormal; the communication device according to the first group identifier
  • the second mobility management entity sends the message related to the first terminal. That is, before the first mobility management entity is abnormal, the communication device may know in advance that the terminal in the terminal group corresponding to the first group identifier is managed by the second mobility in the case that the first mobility management entity is abnormal. The entity provides the service. In this way, in the case that the first mobility management entity is abnormal, the communication device may send the first terminal related message to the second mobility management entity according to the first indication message and the first group identifier.
  • the first indication message may be notified by the second mobility management entity to the communication device, or may be notified by the first mobility management entity or the network management to the communication device, and the embodiment of the present application does not specifically limited.
  • the communication device acquires the first group identifier of the terminal group where the first terminal of the first mobility management entity service is located, where the communication device receives the message related to the first terminal, where the first terminal is related to the message.
  • the first group of identifiers of the terminal group in which the first terminal is located is carried; or the communication device determines, from the context of the first terminal, the first group of identifiers of the terminal group in which the first terminal is located.
  • the communication device can obtain the group identifier of the terminal group where the first terminal of the first mobility management entity service is located.
  • the method further includes: acquiring, by the communications device, a second group identifier of the terminal group where the second terminal of the first mobility management entity service is located; if the first mobility management entity is abnormal, the communication device is configured according to the The second group of identifiers sends a message related to the second terminal to the third mobility management entity, where the third mobility management entity is a mobility management entity that has a context of the second terminal.
  • the first mobility management entity may also synchronize the context of the second terminal of the service to the third mobility management entity, and in the case that the first mobility management entity is abnormal, may be based on the terminal where the second terminal is located.
  • the second group of identifiers of the group sends the second terminal related message to the third mobility management entity, so that if the first mobility management entity is abnormal, the terminal may be prevented from re-registering due to the context loss of the terminal being served.
  • the process that is, the current process of the terminal being served can be kept uninterrupted; on the other hand, since the first mobility management entity can group the terminals, the contexts of the terminals in different terminal groups can be separately backed up to multiple different mobility management entities. That is to say, one-to-many backup can be achieved.
  • the first mobility management entity is abnormal
  • one or more terminal groups of the first mobility management entity are respectively taken over by a plurality of different mobility management entities, thereby reducing the single node due to the abnormality of the first mobility management entity.
  • the impact of the mobile management entity saves resources compared to the traditional 1+1 backup, and at the same time compensates for the context loss problem in the traditional mobility management entity MME pool.
  • the communication device comprises an access device or a session management entity.
  • a communication method comprising: a second mobility management entity receiving a context of a first terminal of the first mobility management entity service from a first mobility management entity; the second mobility management entity determining the An abnormality occurs in a mobility management entity; the second mobility management entity sends a first indication message to the communication device, where the first indication message is used to indicate that the terminal in the terminal group corresponding to the first group identifier is served by the second mobility management entity
  • the first group identifier is a group identifier of the terminal group where the first terminal is located.
  • the terminal in the terminal group corresponding to the group identifier is served by the second mobility management entity, where the first group identifier is a group identifier of the terminal group where the first terminal is located. Therefore, the communication device may send, according to the first indication message and the first group identifier, a message related to the first terminal to the second mobility management entity, so that, in case the abnormality occurs in the first mobility management entity, the communication device may be avoided.
  • the context of the terminal is lost and the re-registration process of the terminal is triggered, that is, the current process of the terminal being served can be kept uninterrupted.
  • the method further includes: the second mobility management entity receiving the message related to the first terminal from the communications device. Based on the solution, the second mobility management entity may obtain the message related to the first terminal.
  • the method includes: the second mobility management entity receives a context of a second terminal served by the third mobility management entity of the third mobility management entity; the second mobility management entity determines that the third mobility management entity occurs The second mobility management entity sends a second indication message to the communication device, where the second indication message is used to indicate that the terminal in the terminal group corresponding to the second group identifier is served by the second mobility management entity, where The second group identifier is a group identifier of the terminal group where the second terminal is located.
  • the second mobility management entity can notify the communication if the third mobility management entity is abnormal.
  • the terminal in the terminal group corresponding to the second group identifier of the device is served by the second mobility management entity, where the second group identifier is the group identifier of the terminal group where the second terminal is located. Therefore, the communication device may send the second terminal related message to the second mobility management entity according to the second indication message and the second group identifier, so that, in case the abnormality occurs in the third mobility management entity, the The context of the terminal is lost and the re-registration process of the terminal is triggered, that is, the current process of the terminal being served can be kept uninterrupted.
  • the second mobility management entity can back up the first mobility management entity and the third mobility management entity respectively, one-to-many backup can be implemented, thereby saving resources compared to the conventional 1+1 backup.
  • a communication device having the functionality to implement the method of the first aspect described 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 communication device, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer to execute an instruction, and the processor is connected to the memory through the bus, when the communication device is running, The processor executes the computer-executable instructions stored by the memory to cause the communication device to perform the communication method of any of the first aspects above.
  • a fifth aspect a computer readable storage medium having stored therein instructions that, when run on a computer, cause the computer to perform the communication 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 communication method of any of the above first aspects.
  • a chip system comprising a processor for supporting a communication device to implement the functions involved in the foregoing aspects, for example, in case the abnormality occurs in the first mobility management entity, according to the first mobility management
  • the chip system further includes a memory for holding program instructions and data necessary for the communication device.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • a second mobility management entity having the functionality to implement the method of the second aspect described 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 ninth aspect provides a second 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, and the second When the mobility management entity is running, the processor executes the computer execution instructions stored by the memory to cause the second mobility management entity to perform the communication method as described in any of the above second aspects.
  • a computer readable storage medium having stored therein instructions that, when run on a computer, cause the computer to perform the business session establishing method of any of the above second aspects .
  • a computer program product comprising instructions which, when run on a computer, cause the computer to perform the communication method of any of the above second aspects.
  • a chip system comprising a processor for supporting a second mobility management entity to implement the functions involved in the above aspects, such as receiving a first mobility management entity from a first mobility management entity The context of the first terminal of the service.
  • the chip system further includes a memory for storing necessary program instructions and data of the second mobility management entity.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • a communications system comprising a first mobility management entity, a second mobility management entity, and a communication device; wherein the first mobility management entity is configured to send to the second mobility management entity a context of the first terminal served by the first mobility management entity; the second mobility management entity is configured to receive a context of the first terminal from the first mobility management entity; the communication device is configured to acquire the first terminal a first group identifier of the terminal group, and in the case that the first mobility management entity is abnormal, sending, according to the first group identifier, the first terminal related message to the second mobility management entity; the second mobile The management entity is further configured to receive a message related to the first terminal from the communication device.
  • the second mobility management entity is further configured to determine that the first mobility management entity is abnormal; the second mobility management entity is further configured to send a first indication message to the communications device, where the An indication message is used to indicate that the terminal in the terminal group corresponding to the first group identifier is served by the second mobility management entity; the communication device is further configured to receive the first indication message.
  • the communication device is further configured to: before the first mobility management entity generates an abnormality, receive a first indication message, where the first indication message is used to indicate that an abnormality occurs in the first mobility management entity.
  • the communication device is further configured to determine that the first mobility management entity is abnormal.
  • FIG. 1 is a schematic structural diagram of a communication 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 network device according to an embodiment of the present disclosure.
  • FIG. 4 is a schematic flowchart 1 of a communication method according to an embodiment of the present application.
  • FIG. 5 is a second schematic flowchart of a communication method according to an embodiment of the present disclosure.
  • FIG. 6 is a second schematic flowchart of a communication method according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram 1 of a communication device according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram 2 of a communication device according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram 1 of a second mobility management entity according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram 2 of a second mobility management entity according to an embodiment of the present application.
  • the words “first”, “second”, and the like are used to distinguish the same items or similar items whose functions and functions are substantially the same.
  • the words “first”, “second” and the like do not limit the number and execution order, and the words “first”, “second” and the like are not necessarily limited.
  • the second mobility management entity and the third mobility management entity in the embodiment of the present application may be the same mobility management entity, or may be different mobility management entities, which is not specifically limited in this 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 communication system 10 according to an embodiment of the present application.
  • the communication system 10 includes a communication device 101 and a mobility management entity group 102.
  • the mobility management entity group 102 includes at least two mobility management entities that are mutually backup relationships, such as the first mobility management entity 102a and the second mobility management entity 102b in FIG.
  • the mobility management entity group 102 in FIG. 1 may further include other mobility management entities, such as a third mobility management entity, which is not specifically limited in this embodiment of the present application.
  • the first mobility management entity 102a is configured to send the context of the first terminal served by the first mobility management entity 102a to the second mobility management entity 102b.
  • the communication device 101 is configured to acquire a first group identifier of the terminal group where the first terminal is located, and send an error to the second mobility management entity 102b according to the first group identity.
  • the first terminal related message is configured to acquire a first group identifier of the terminal group where the first terminal is located, and send an error to the second mobility management entity 102b according to the first group identity. The first terminal related message.
  • the second mobility management entity 102b is configured to receive a message related to the first terminal from the communication device 101.
  • the first mobility management entity 102a, the second mobility management entity 102b, and the communication device 101 in FIG. 1 may directly communicate with each other, and may also perform communication through forwarding of other devices, which is not specifically limited in this embodiment of the present application. .
  • the communication device 102 in FIG. 1 may include an access device or a session management function entity, etc., which is not specifically limited in this embodiment of the present application.
  • the message related to the first terminal is an uplink message related to the first terminal; if the communication device 102 is a session management function entity, the message related to the first terminal is related to the first terminal.
  • the downlink message is uniformly explained here, and will not be described below.
  • the abnormality of the mobility management entity in the embodiment of the present application includes a fault or an overload of the mobility management entity, and is uniformly described herein, and details are not described herein.
  • the first mobility management entity may synchronize the context of the first terminal of the service to the second mobility management entity, and may be based on the first terminal if the first mobility management entity is abnormal.
  • the first group identifier of the terminal group is sent to the second mobility management entity to send a message related to the first terminal, so that if the first mobility management entity is abnormal, the terminal may be prevented from being triggered due to the context loss of the terminal being served.
  • the current process of the terminal being served can be kept uninterrupted.
  • the synchronization of the context may be the synchronization of the context triggering context, or a timer may be set, and the synchronization of the context is triggered after the timer expires. Specifically limited.
  • the foregoing communication 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 communication device may be an access device or an SMF entity; the network element or entity corresponding to the mobility management entity may be connected.
  • Access and Mobility Management Function (AMF) entities For example, the network element or entity corresponding to the first mobility management entity 102a may be the first AMF entity; the network element or entity corresponding to the second mobility management entity 102b may be the second AMF entity.
  • AMF Access and Mobility Management Function
  • the 5G network may further include a user plane function (UPF) entity, a unified data management (UDM) entity, and an authentication server function (AUSF) entity. , policy control function (PCF) entity, etc.
  • the 5G network may further include a UDSF entity.
  • the terminal accesses the network through the access device, and communicates with the first AMF entity and the second AMF entity through a next generation (N)1 interface (N1); the first AMF entity Communicating with the second AMF entity through the N14 interface (N14 for short); the first AMF entity and the second AMF entity both communicate with the access device through the N2 interface (N2 for short); the first AMF entity and the second AMF entity both pass the N18 interface.
  • N next generation
  • N18 for short communicating with the UDSF entity; the first AMF entity and the second AMF entity both communicate with the AUSF entity through the N12 interface (N12 for short); the first AMF entity and the second AMF entity both pass the N8 interface (referred to as N8) and the UDM
  • the first AMF entity and the second AMF entity communicate with the SMF entity through the N11 interface (N11 for short); the first AMF entity and the second AMF entity communicate with the PCF entity through the N15 interface (N15 for short); the AUSF entity passes
  • the N13 interface (N13 for short) communicates with the UDM entity; the SMF entity communicates with the UPF entity through the N4 interface (N4 for short); the UPF entity communicates through the N6 interface (N6) data network (DN).
  • the name of the interface between the network elements in FIG. 2 is only an example. In the specific implementation, the interface name may be another name, which is not specifically limited in this embodiment of the present application.
  • the access device, the first AMF entity, the second 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 is not for the device itself.
  • the composition is limited.
  • the network element or entity corresponding to the access device, the first AMF entity, the second AMF entity, the SMF entity, the UDSF entity, the AUSF entity, the UDM entity, the UPF entity, and the PCF entity may also be used in the 5G network and other networks in the future.
  • Other names are not specifically limited in the embodiment of the present application.
  • 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 (user equipment) , UE), mobile station (MS), terminal device, etc.
  • PDA personal digital assistant
  • WLL wireless local loop
  • MTC machine type communication
  • user equipment user equipment
  • 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-third generation. 3rd generation partnership project (3GPP) access equipment, etc.
  • the base station may include various forms of base stations, such as macro base stations, micro base stations (also referred to as small stations), relay stations, access points, and the like.
  • the function of the first AMF entity involved in the embodiment of the present application may be referred to the function of the first mobility management entity in FIG. 1 .
  • the function of the second AMF entity involved in the embodiment of the present application may be referred to.
  • the functions of the second mobility management entity in FIG. 1 are not described herein again.
  • the first AMF entity and the second 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 of the present application.
  • 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 first mobility management entity or the communication device in FIG. 1 may be implemented by one physical device, or may be implemented by multiple physical devices, or may be a logical function module in a physical device. This is not specifically limited.
  • FIG. 3 is a schematic diagram showing the hardware structure of a network device according to an embodiment of the present application.
  • Network device 300 includes at least one processor 301, communication bus 302, 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 communication 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.
  • network 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.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • the network device 300 may further 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 network device 300 described above may be a general purpose device or a dedicated device.
  • the network 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 network device 300.
  • the communication system shown in FIG. 1 is applied to the 5G network shown in FIG. 2 as an example.
  • a group identity of the terminal group and an AMF entity group are first introduced as follows.
  • the AMF entity may group all the terminals served by the AMF entity according to a local policy or other factors, and configure corresponding group identifiers for each group of terminals to facilitate management.
  • an AMF entity may correspond to one or more globally unique AMF identifiers (GUAMIs), which are identified by a public land mobile network (PLMN) identifier (ID) and an AMF entity.
  • GUIs globally unique AMF identifiers
  • PLMN public land mobile network
  • ID an AMF entity.
  • AMF pointer multiple GUAMIs of one AMF entity can be distinguished by AMF pointer, that is, AMF pointers in different GUAMIs are different.
  • the group identifier of the terminal group in the embodiment of the present application may be an AMF pointer in GUAMI or GUAMI; when an AMF entity corresponds to a GUAMI, the terminal group in the embodiment of the present application
  • the group identifier may be the high N bit of the AMF pointer+ terminal temporary identifier, that is, the high N bits of the terminal temporary identifier may be used to identify different terminal groups. For example, taking the highest 2 bits for identifying the terminal group as an example, all terminals that provide services by one AMF entity can be divided into four groups, and the terminal temporary identifiers of the four groups of terminals start with 00, 01, 10, and 11, respectively.
  • the AMF entity needs to notify the access device and the core network device how to intercept the group identifier from the identifier of the terminal. For example, the AMF entity notifies the access device and the core network device of the length of the group identifier of the terminal group. Unified instructions, the details are not described below.
  • the following embodiment of the present application replaces the group identifier of the terminal group in which the terminal is located with the group identifier of the terminal, and is uniformly described herein, and details are not described herein again.
  • the AMF entity group includes multiple AMF entities that are mutually backup relationships. Each AMF entity can be configured with m primary group identifiers and n backup group identifiers.
  • the AMF entity provides a service for the terminal whose identity is the primary group identifier corresponding to the AMF entity, and the AMF entity saves the context of the terminal whose identity is the backup group identifier corresponding to the AMF entity.
  • the AMF entity takes over the terminals and provides services for the terminals.
  • the AMF entity is a 1+1 backup, that is, it is assumed that the AMF entity group includes two AMF entities, such as AMF entity 1 and AMF entity 2, respectively, and the two AMF entities are backup relationships with each other, and each AMF entity Configure three primary group IDs and three backup group IDs, as shown in Table 1:
  • AMF entity Primary group identification Backup group ID AMF entity 1 Logo 1, logo 2, logo 3 Mark 4, logo 5, logo 6 AMF entity 2 Mark 4, logo 5, logo 6 Logo 1, logo 2, logo 3
  • the AMF entity 1 when the AMF entity 1 does not have an abnormality, the AMF entity 1 provides services for the terminals whose group identifiers are the identifier 1, the identifier 2, and the identifier 3. At the same time, the AMF entity 1 stores the terminal whose group identifier is the identifier 4, the identifier 5, and the identifier 6. Context.
  • the AMF entity 1 takes over the terminal identified as the identifier 4, the identifier 5, and the identifier 6, and provides services for the terminals. .
  • the AMF entity 2 When the AMF entity 2 does not have an abnormality, the AMF entity 2 provides services for the terminals whose group identification is the identifier 4, the identifier 5, and the identifier 6; meanwhile, the AMF entity 2 stores the context of the terminal whose group identifier is the identifier 1, the identifier 2, and the identifier 3. .
  • the AMF entity 2 takes over the terminal whose identity is identified as the identifier 1, the identifier 2, and the identifier 3, and provides services for the terminals. .
  • the AMF entity is a 1+N backup, and N is an integer greater than 1, that is, it is assumed that the AMF entity group includes more than two AMF entities, including, for example, AMF entity 1, AMF entity 2, AMF entity 3, and AMF.
  • the entity 4 has a total of four AMF entities.
  • the four AMF entities are in a backup relationship.
  • Each AMF entity is configured with three primary group identifiers and three backup group identifiers, as shown in Table 2:
  • AMF entity Primary group identification Backup group ID AMF entity 1 Logo 1, logo 2, logo 3 Mark 4, logo 7, logo 10 AMF entity 2 Mark 4, logo 5, logo 6 Logo 1, logo 8, logo 11 AMF entity 3 Logo 7, logo 8, logo 9 Logo 2, logo 5, logo 12 AMF entity 4 Logo 10, logo 11, logo 12 Logo 3, logo 6, logo 9
  • the AMF entity 1 when the AMF entity 1 does not have an abnormality, the AMF entity 1 provides services for the terminals whose group identifiers are the identifier 1, the identifier 2, and the identifier 3; meanwhile, the AMF entity 1 stores the group identifiers as the identifiers of the identifier 4, the identifier 7, and the identifier 10. Context.
  • the AMF entity 1 takes over the terminal identified as the identifier 4 to provide services for the terminals; and provides services for the terminal whose group identifier is the identifier 7.
  • the AMF entity 1 takes over the terminal identified by the group as the identifier 7 to provide services for the terminals; and when the AMF entity 4 serving the terminal whose group identifier is the identifier 10 is abnormal, the AMF entity 1 Take over the group of terminals identified as ID 10 to provide services for these terminals.
  • the AMF entity 2 When the AMF entity 2 does not have an abnormality, the AMF entity 2 provides services for the terminals whose group identification is the identifier 4, the identifier 5, and the identifier 6; meanwhile, the AMF entity 2 stores the context of the terminal whose group identifier is the identifier 1, the identifier 8, and the identifier 11. .
  • the AMF entity 2 When an abnormality occurs in the AMF entity 1 that serves the terminal whose group ID is the identifier 1, the AMF entity 2 takes over the terminal whose identity is identified as the identifier 1, and provides services for the terminals; when the terminal is identified as the identifier of the group 8 When an abnormality occurs in the AMF entity 3, the AMF entity 2 takes over the terminal identified as the identifier 8 to provide services for the terminals; and when the AMF entity 4 serving the terminal whose group identifier is the identifier 11 is abnormal, the AMF entity 2 Take over the group of terminals identified as identifiers 11 to provide services for these terminals.
  • the AMF entity 3 When the AMF entity 3 does not have an abnormality, the AMF entity 3 provides services for the terminals whose group identification is the identifier 7, the identifier 8 and the identifier 9; meanwhile, the AMF entity 3 stores the context of the terminal whose group identifier is the identifier 2, the identifier 5, and the identifier 12. .
  • the AMF entity 3 takes over the terminal identified as the identifier 2 to provide services for the terminals; and provides services for the terminal whose group identifier is the identifier 5.
  • the AMF entity 3 takes over the terminal identified by the group as the identifier 5 to provide services for the terminals; and when the AMF entity 4 serving the terminal whose group identifier is the identifier 12 is abnormal, the AMF entity 3 Take over the group of terminals identified as identifiers 12 to provide services for these terminals.
  • the AMF entity 4 When the AMF entity 4 does not have an abnormality, the AMF entity 4 provides services for the terminals whose group identification is the identifier 10, the identifier 11 and the identifier 12; meanwhile, the AMF entity 4 stores the context of the terminal whose group identifier is the identifier 3, the identifier 6 and the identifier 9. .
  • the AMF entity 4 takes over the terminal identified as the identifier 3 to provide services for the terminals; and provides services for the terminal whose identifier is the identifier of the group 6.
  • the AMF entity 4 takes over the terminal identified as the identifier 6 to provide services for the terminals; and when the AMF entity 3 serving the terminal whose group identifier is the identifier 9 is abnormal, the AMF entity 4 Take over the group of terminals identified as identification 9 to provide services for these terminals.
  • the backup group identifier of an AMF entity is responsible for the average of other AMF entities in the AMF entity group.
  • the backup relationship may not be equal.
  • the configured backup relationship can be as shown in Table 3.
  • the AMF entity 1 when the AMF entity 1 does not have an abnormality, the AMF entity 1 provides services for the terminals whose group identifiers are the identifier 1, the identifier 2, and the identifier 3; meanwhile, the AMF entity 1 stores the group identifiers as the identifiers of the identifier 7, the identifier 8, and the identifier 9. Context.
  • the AMF entity 1 takes over the terminal identified as the identifier 7, the identifier 8 and the identifier 9 to provide services for the terminals. .
  • the AMF entity 2 When the AMF entity 2 does not have an abnormality, the AMF entity 2 provides services for the terminals whose group identification is the identifier 4, the identifier 5, and the identifier 6; meanwhile, the AMF entity 2 stores the context of the terminal whose group identifier is the identifier 10, the identifier 11, and the identifier 12. .
  • the AMF entity 2 takes over the terminal identified as the identifier 10, the identifier 11, and the identifier 12, and provides services for the terminals. .
  • the AMF entity 3 When the AMF entity 3 does not have an abnormality, the AMF entity 3 provides services for the terminal whose identity is the identifier of the group 7, the identifier 8, the identifier 9, the identifier 10, the identifier 11, and the identifier 12. At the same time, the AMF entity 3 saves the group identifier as the identifier 1. The context of the identity of the identity 2, the identity 3, the identity 4, the identity 5 and the identity 6.
  • the AMF entity 3 takes over the terminal whose identity is identified as the identifier 1, the identifier 2, and the identifier 3, and provides services for the terminals.
  • the AMF entity 3 takes over the terminal identified as the identifier 4, the identifier 5, and the identifier 6 to provide the terminals. service.
  • the embodiment of the present application does not specifically limit the backup relationship of each AMF entity in the AMF entity group, and can be flexibly configured according to actual requirements.
  • the primary group identifier and the backup group identifier may not be configured in the AMF entity, but only the group identifier of the terminal served when the primary AMF entity does not have an abnormality is configured in the primary AMF entity. And when the primary AMF entity is abnormal, the information of the backup AMF entity of the terminal identified by the group identity is respectively taken over.
  • the backup relationship between two AMF entities in an AMF entity group is as shown in Table 1, the backup relationship can also be represented by Table 4:
  • AMF entity 2 Mark 4, logo 5, logo 6 AMF entity 1
  • the backup relationship of four AMF entities in the AMF entity group is as shown in Table 2, the backup relationship may also be represented by Table 5:
  • the backup relationship of four AMF entities in the AMF entity group is as shown in Table 3, the backup relationship may also be represented by Table 6:
  • the characterization form of the backup relationship of each AMF entity in the AMF entity group is not specifically limited in this embodiment.
  • the communication system shown in FIG. 1 is applied to the 5G network shown in FIG. 2, and the configuration of the AMF entity group is as shown in Table 2, assuming that the AMF entity 1 is the first AMF entity and the AMF entity 2 is the second.
  • the AMF entity, the AMF entity 3 is the third AMF entity, and the AMF entity 4 is the fourth AMF entity.
  • the communication method provided by the embodiment of the present application may be as shown in FIG. 4, and includes the following steps:
  • the first AMF entity sends the primary group identifier configured in the first AMF entity to the access device, so that the access device receives the primary group identifier configured in the first AMF entity from the first AMF entity.
  • the primary group identifier configured in the first AMF entity includes the identifier 1, the identifier 2, and the identifier 3.
  • the primary group identifier is used to indicate that the terminal in the corresponding terminal group is served by the first AMF entity.
  • the mapping between the information of the first AMF entity and the primary group identifier configured in the first AMF entity may be saved.
  • the access device may select a corresponding AMF entity according to the corresponding relationship, which is not specifically limited in this embodiment.
  • the second AMF entity sends the primary group identifier configured in the second AMF entity to the access device, so that the access device receives the primary group identifier configured in the second AMF entity from the second AMF entity.
  • the primary group identifier configured in the second AMF entity includes the identifier 4, the identifier 5, and the identifier 6.
  • the primary group identifier is used to indicate that the terminal in the corresponding terminal group is served by the second AMF entity.
  • the mapping between the information of the second AMF entity and the primary group identifier configured in the second AMF entity may be saved.
  • the access device may select a corresponding AMF entity according to the corresponding relationship, which is not specifically limited in this embodiment.
  • the third AMF entity sends the primary group identifier configured in the third AMF entity to the access device, so that the access device receives the primary group identifier configured in the third AMF entity from the third AMF entity.
  • the primary group identifier configured in the third AMF entity includes the identifier 7, the identifier 8, and the identifier 9.
  • the primary group identifier is used to indicate that the terminal in the corresponding terminal group is served by the third mobility management entity.
  • the mapping between the information of the third AMF entity and the primary group identifier configured in the third AMF entity may be saved.
  • the access device may select a corresponding AMF entity according to the corresponding relationship, which is not specifically limited in this embodiment.
  • the fourth AMF entity sends the primary group identifier configured in the fourth AMF entity to the access device, so that the access device receives the primary group identifier configured in the fourth AMF entity from the fourth AMF entity.
  • the primary group identifier configured in the fourth AMF entity includes the identifier 10, the identifier 11, and the identifier 12.
  • the primary group identifier is used to indicate that the terminal in the corresponding terminal group is served by the fourth mobility management entity.
  • the mapping between the information of the fourth AMF entity and the primary group identifier configured in the fourth AMF entity may be saved.
  • the access device may select a corresponding AMF entity according to the corresponding relationship, which is not specifically limited in this embodiment.
  • each AMF entity needs to notify the access device of the length of the primary group identifier.
  • the length of the primary group identifier may be represented by a number of digits, or may be represented by a mask, which is not specifically limited in this embodiment of the present application.
  • the first AMF entity may further send the primary group identifier configured in the first AMF entity to the SMF entity; the second AMF entity may further send the primary group configured in the second AMF entity to the SMF entity.
  • the third AMF entity may also send the primary group identifier configured in the third AMF entity to the SMF entity; the fourth AMF entity may further send the primary group identifier configured in the fourth AMF entity to the SMF entity.
  • the SMF entity can store the correspondence between the information of each AMF entity and the primary group identifier configured in the corresponding AMF entity, and the SMF entity can subsequently select the corresponding AMF entity according to the corresponding relationship.
  • the group identifier of the terminal and the information of the AMF entity that it serves may be sent to the SMF entity when the packet data unit (PDU) session is established, which is not specifically limited in this embodiment of the present application.
  • the terminal registers with the network.
  • the access device selects an AMF entity for the terminal.
  • An embodiment of the present application is described by using the first AMF entity as an example.
  • the first AMF entity receives the registration request of the terminal, the first AMF entity randomly selects one of the primary group identifiers configured in the first AMF entity.
  • the primary group ID is used as the group ID of the terminal.
  • the first AMF entity selects the identifier 1 as the group identifier of the terminal, proceeding to step S403a;
  • step S403c is continued.
  • the first AMF entity sends the context of the terminal to the second AMF entity after the terminal completes registration or at other occasions, such as when the timer expires, so that the second AMF entity receives the terminal from the first AMF entity. Context.
  • the VRRP group identifier configured in the second AMF entity includes the identifier 1 in the second AMF entity. That is, when an abnormality occurs in the first AMF entity serving the terminal whose group identity is the identifier 1, the second AMF entity can take over the terminals, and provide services for the terminals whose identity is identified as the identifier 1, and thus the first AMF entity
  • the context of the terminal identified as the identity of the group 1 needs to be synchronized to the second AMF entity.
  • the first AMF entity sends the context of the terminal to the third AMF entity after the terminal completes registration or at other occasions, such as when the timer expires, so that the third AMF entity receives the terminal from the first AMF entity. Context.
  • the VRRP group identifier configured in the third AMF entity includes the identifier 2, as shown in Table 2. That is, when an abnormality occurs in the first AMF entity serving the terminal identified as the identity of the group 2, the third AMF entity can take over the terminals, and provide services for the terminals whose identity is identified as the identity 2, and thus the first AMF entity The context of the terminal identified as the identity of the group 2 needs to be synchronized to the third AMF entity.
  • the first AMF entity sends the context of the terminal to the fourth AMF entity after the terminal completes registration or at other occasions, such as when the timer expires, so that the fourth AMF entity receives the terminal from the first AMF entity. Context.
  • the VRRP group identifier configured in the fourth AMF entity includes the identifier 3, as shown in Table 2. That is, when an abnormality occurs in the first AMF entity serving the terminal identified as the identity of the group 3, the fourth AMF entity can take over the terminals, and provide services for the terminals whose identity is identified as the identifier 4, and thus the first AMF entity The context of the terminal identified as the identity of the group 3 needs to be synchronized to the fourth AMF entity.
  • S404 An abnormality occurs in the first AMF entity.
  • the access device performs steps S405a and S406a; the second AMF entity performs steps S405b-S407b; the third AMF entity performs steps S405c-S407c; and the fourth AMF entity performs steps S405d-S407d;
  • the SMF entity performs steps S405e and S406e, as described in the following steps.
  • the access device detects that the first AMF entity is abnormal.
  • the access device identifies the first AMF entity as unavailable, and the new AMF entity does not select the first AMF entity when accessing the new terminal.
  • S405b The second AMF entity detects that an abnormality occurs in the first AMF entity.
  • the second AMF entity sends an indication message 1 to the SMF entity, so that the SMF entity receives the indication message 1 from the second AMF entity.
  • the indication message 1 is used to indicate that the terminal in the terminal group corresponding to the identifier 1 is served by the second AMF entity.
  • the SMF entity may save the correspondence between the information of the second AMF entity and the identifier 1.
  • the SMF entity may release the SMF entity to the N11 interface of the first AMF entity.
  • the second AMF entity may be selected according to the corresponding relationship, and the SMF entity is sent to the N11 interface of the second AMF entity, and the downlink message is sent by the second AMF entity. This is not specifically limited.
  • the second AMF entity sends an indication message 1 to the access device, so that the access device receives the indication message 1 from the second AMF entity.
  • the indication message 1 is used to indicate that the terminal in the terminal group corresponding to the identifier 1 is served by the second AMF entity.
  • the access device may save the correspondence between the information of the second AMF entity and the identifier 1.
  • the access device may release the access device to the N2 interface of the first AMF entity.
  • the second AMF entity may be selected according to the corresponding relationship, and the N2 interface of the access device to the second AMF entity is established, and the second AMF entity sends an uplink message.
  • the embodiment does not specifically limit this.
  • S405c The third AMF entity detects that an abnormality occurs in the first AMF entity.
  • the third AMF entity sends an indication message 2 to the SMF entity, so that the SMF entity receives the indication message 2 from the third AMF entity.
  • the indication message 2 is used to indicate that the terminal in the terminal group corresponding to the identifier 2 is served by the third AMF entity.
  • the SMF entity may save the correspondence between the information of the third AMF entity and the identifier 2.
  • the SMF entity may release the SMF entity to the N11 interface of the first AMF entity.
  • the third AMF entity may be selected according to the corresponding relationship, and the NMF interface of the SMF entity to the third AMF entity is established, and the downlink message is sent by the third AMF entity. This is not specifically limited.
  • the third AMF entity sends an indication message 2 to the access device, so that the access device receives the indication message 2 from the third AMF entity.
  • the indication message 2 is used to indicate that the terminal in the terminal group corresponding to the identifier 2 is served by the third AMF entity.
  • the access device may save the correspondence between the information of the third AMF entity and the identifier 2.
  • the access device may release the access device to the N2 interface of the first AMF entity.
  • the third AMF entity may be selected according to the corresponding relationship, and the N2 interface of the access device to the third AMF entity is established, and the third AMF entity sends an uplink message.
  • the embodiment does not specifically limit this.
  • the fourth AMF entity detects that an abnormality occurs in the first AMF entity.
  • the fourth AMF entity sends an indication message 3 to the SMF entity, so that the SMF entity receives the indication message 3 from the fourth AMF entity.
  • the indication message 3 is used to indicate that the terminal in the terminal group corresponding to the identifier 3 is served by the fourth AMF entity.
  • the SMF entity may save the correspondence between the information of the fourth AMF entity and the identifier 3.
  • the SMF entity may release the SMF entity to the N11 interface of the first AMF entity.
  • the fourth AMF entity may be selected according to the corresponding relationship, and the NMF interface of the SMF entity to the fourth AMF entity is established, and the downlink message is sent by the fourth AMF entity. This is not specifically limited.
  • the fourth AMF entity sends an indication message 3 to the access device, so that the access device receives the indication message 3 from the fourth AMF entity.
  • the indication message 3 is used to indicate that the terminal in the terminal group corresponding to the identifier 3 is served by the fourth AMF entity.
  • the access device may save the correspondence between the information of the fourth AMF entity and the identifier 3.
  • the access device may release the access device to the N2 interface of the first AMF entity.
  • the fourth AMF entity may be selected according to the corresponding relationship, and the N2 interface of the access device to the fourth AMF entity is established, and the fourth AMF entity sends an uplink message.
  • the embodiment does not specifically limit this.
  • the SMF entity detects that an abnormality occurs in the first AMF entity.
  • the SMF entity identifies the first AMF entity as unavailable, and then does not send the downlink message to the first AMF entity.
  • the exemplary interaction between the AMF entity and the SMF entity on the core network side is taken as an example for description.
  • the SMF entity in the embodiment of the present application may be replaced with other core network devices.
  • each AMF entity performs the foregoing interaction with the UDM entity or the AUSF entity, which is not specifically limited in this embodiment.
  • the following descriptions are respectively taken from the access device to obtain the terminal-related uplink message and the SMF entity to obtain the terminal-related downlink message, which respectively include the following steps S408-S409 and steps S410-S411.
  • the access device acquires an uplink message related to the terminal.
  • the uplink message related to the terminal may be an uplink message sent to the target AMF entity, such as an uplink N2 message, when the access device needs to initiate an N2 message related to the terminal, or may be sent by the terminal to the terminal.
  • the uplink message of the target AMF entity such as the non-access stratum (NAS) message, is not specifically limited in this embodiment of the present application.
  • the access device may obtain the group identifier of the terminal from the uplink message related to the terminal that is sent by the terminal to the access device, or the access device may determine the group identifier of the terminal from the context of the terminal. This is not specifically limited.
  • the terminal related uplink message includes a system architecture evolution (SAE) temporary mobile subscriber identity (S-TMSI)
  • SAE system architecture evolution
  • S-TMSI temporary mobile subscriber identity
  • the S-TMSI is temporarily configured by the AMF pointer and the terminal.
  • the identifier component is configured. If the group identifier of the terminal group is the high N bit of the temporary identifier of the AMF pointer+ terminal, the access device can read the digits of the corresponding length from the upper digit of the S-TMSI according to the length of the group identifier, and obtain the corresponding group identifier.
  • SAE system architecture evolution
  • S-TMSI temporary mobile subscriber identity
  • the access device continues to perform step S409a;
  • the access device proceeds to step S409b;
  • the access device proceeds to step S409c.
  • the access device sends, according to the group identifier 1, a terminal-related uplink message to the second AMF entity, so that the second AMF entity receives the uplink message related to the terminal from the access device.
  • the access device may determine, according to the indication message 1 received in step S407b and the group identifier 1 obtained in step S408, that the AMF entity corresponding to the group identifier 1 is the second AMF entity, and further to the second AMF entity. Send the uplink message related to the terminal.
  • the access device sends, according to the group identifier 2, a terminal-related uplink message to the third AMF entity, so that the third AMF entity receives the uplink message related to the terminal from the access device.
  • the access device may determine, according to the indication message 2 received in step S407c and the group identifier 2 obtained in step S408, that the AMF entity corresponding to the group identifier 2 is the third AMF entity, and further to the third AMF entity. Send the uplink message related to the terminal.
  • S409c The access device sends, according to the group identifier 3, a terminal-related uplink message to the fourth AMF entity, so that the fourth AMF entity receives the uplink message related to the terminal from the access device.
  • the access device may determine, according to the indication message 3 received in step S407d and the group identifier 3 obtained in step S408, that the AMF entity corresponding to the group identifier 3 is the fourth AMF entity, and further to the fourth AMF entity. Send the uplink message related to the terminal.
  • the SMF entity acquires a downlink message related to the terminal.
  • the downlink message related to the terminal may be a downlink message sent by the SMF entity to the access device, and the following is an N2 message; or may be a downlink message sent by the SMF entity to the terminal, as follows: It may also be a downlink message sent by the SMF entity to the target AMF entity, which is not specifically limited in this embodiment of the present application.
  • the SMF entity may obtain the group identifier of the terminal from the downlink message related to the terminal sent by the other device to the SMF entity; or the SMF entity may determine the group identifier of the terminal from the context of the terminal. This is not specifically limited.
  • the S-TMSI is composed of the AMF pointer and the temporary identifier of the terminal, and if the group identifier of the terminal group is the high N-bit of the AMF pointer+ terminal temporary identifier, the SMF entity The value of the corresponding number of bits can be read from the upper part of the S-TMSI according to the length of the group identifier, and the corresponding group identifier is obtained, which is not specifically limited in this embodiment of the present application.
  • the SMF entity continues to perform step S411a;
  • the SMF entity continues to perform step S411b;
  • the SMF entity proceeds to step S411c.
  • the SMF entity sends a terminal-related downlink message to the second AMF entity according to the group identifier 1, so that the second AMF entity receives the downlink message related to the terminal from the SMF entity.
  • the SMF entity may determine, according to the indication message 1 received in step S406b and the group identifier 1 obtained in step S410, that the AMF entity corresponding to the group identifier 1 is the second AMF entity, and further to the second AMF entity. Send a downlink message related to the terminal.
  • the SMF entity sends a terminal-related downlink message to the third AMF entity according to the group identifier 2, so that the third AMF entity receives the terminal-related downlink message from the SMF entity.
  • the SMF entity may determine, according to the indication message 2 received in step S406c and the group identifier 2 obtained in step S410, that the AMF entity corresponding to the group identifier 2 is the third AMF entity, and then sends the third AMF entity to the third AMF entity. Terminal related downlink messages.
  • the SMF entity sends a terminal-related downlink message to the fourth AMF entity according to the group identifier 3, so that the fourth AMF entity receives the downlink message related to the terminal from the SMF entity.
  • the SMF entity may determine, according to the indication message 3 received in step S406d and the group identifier 3 obtained in step S410, that the AMF entity corresponding to the group identifier 3 is the fourth AMF entity, and further sends the fourth AMF entity to the fourth AMF entity. Terminal related downlink messages.
  • the first AMF entity can synchronize the context of the served terminal to another AMF entity that configures the group identifier of the terminal
  • the first AMF entity is abnormal
  • the terminal related message may be sent to other AMF entities configured with the group identifier according to the group identifier, so that if the first mobility management entity is abnormal, the terminal may be prevented from being restarted due to the context loss of the terminal being served.
  • the registration process that is, the current process of maintaining the terminal being served is not interrupted.
  • the contexts of the terminals in different terminal groups can be separately backed up to multiple different AMF entities, that is, one-to-many backup can be implemented.
  • one or more terminal groups of the first AMF entity are respectively taken over by a plurality of different AMF entities, thereby reducing the impact on the single AMF entity due to the abnormality of the first AMF entity.
  • the traditional 1+1 backup it saves resources and compensates for the problem of context loss in the traditional MME pool.
  • the operations of the access device, the SMF entity, and the respective AMF entities in the foregoing steps S401 to S411 can be performed by the processor 301 in the network device 300 shown in FIG. 3 by calling the application code stored in the memory 303.
  • the embodiment does not impose any limitation on this.
  • the communication system shown in FIG. 1 is applied to the 5G network shown in FIG. 2, and the configuration of the AMF entity group is as shown in Table 2.
  • AMF entity 1 is the first AMF entity
  • AMF entity 2 is The second AMF entity
  • the AMF entity 3 is the third AMF entity
  • the AMF entity 4 is the fourth AMF entity.
  • the communication method provided by the embodiment of the present application may also be as shown in FIG. 5, including the following steps:
  • S501a-S501d similar to S401a-S401d, except that the primary group identifier in the embodiment shown in FIG. 4 is used to indicate that the terminal in the corresponding terminal group is served by the AMF entity that sends the primary group identifier;
  • the primary group identifier in the illustrated embodiment is used to indicate that the terminal in the corresponding terminal group is served by the first AMF entity in the case that the AMF entity that sends the primary group identifier does not have an abnormality.
  • FIG. 4 The illustrated embodiment will not be described herein.
  • the first AMF entity sends the backup group identifier configured in the first AMF entity to the access device, so that the access device receives the backup group identifier configured in the first AMF entity from the first AMF entity.
  • the VRRP group identifier configured in the first AMF entity includes the identifier 4, the identifier 7, and the identifier 10.
  • the backup group identifier is used to indicate that the terminal in the corresponding terminal group is served by the first AMF entity if the AMF entity configured with the backup group identifier is configured as the primary group identifier. For example, in the case that an abnormality occurs in the second AMF entity that configures the identifier 4 as the primary group identifier, the terminal group whose group identifier is the identifier 4 is served by the first AMF entity.
  • the access device may save the correspondence between the information of the first AMF entity and the VRRP group identifier configured in the first AMF entity. In this way, the access device may select a corresponding AMF entity according to the corresponding relationship, which is not specifically limited in this embodiment.
  • the second AMF entity sends the backup group identifier configured in the second AMF entity to the access device, so that the access device receives the backup group identifier configured in the second AMF entity from the second AMF entity.
  • the VRRP group identifier configured in the second AMF entity includes the identifier 1, the identifier 8, and the identifier 11.
  • the backup group identifier is used to indicate that the terminal in the corresponding terminal group is served by the second AMF entity in the case that an abnormality occurs in the AMF entity configured with the backup group identifier as the primary group identifier. For example, in the case that an abnormality occurs in the first AMF entity that configures the identifier 1 as the primary group identifier, the terminal whose group identifier is the identifier of the terminal group is served by the second AMF entity.
  • the access device may select a corresponding AMF entity according to the corresponding relationship, which is not specifically limited in this embodiment.
  • the third AMF entity sends the backup group identifier configured in the third AMF entity to the access device, so that the access device receives the backup group identifier configured in the third AMF entity from the third AMF entity.
  • the VRRP group identifier configured in the third AMF entity includes the identifier 2, the identifier 5, and the identifier 12.
  • the backup group identifier is used to indicate that the terminal in the corresponding terminal group is served by the third AMF entity if the AMF entity configured with the backup group identifier is configured as the primary group identifier. For example, in the case that an abnormality occurs in the first AMF entity that configures the identifier 2 as the primary group identifier, the terminal group whose group identifier is the identifier 2 is served by the third AMF entity.
  • the access device may select a corresponding AMF entity according to the corresponding relationship, which is not specifically limited in this embodiment.
  • the fourth AMF entity sends the backup group identifier configured in the fourth AMF entity to the access device, so that the access device receives the backup group identifier configured in the fourth AMF entity from the fourth AMF entity.
  • the VRRP group identifier configured in the fourth AMF entity includes the identifier 3, the identifier 6, and the identifier 9.
  • the backup group identifier is used to indicate that the terminal in the corresponding terminal group is served by the fourth AMF entity if an abnormality occurs in the AMF entity configured with the backup group identifier as the primary group identifier. For example, in a case where an abnormality occurs in the first AMF entity that configures the identifier 3 as the primary group identifier, the terminal whose group identifier is the identifier of the terminal 3 is served by the fourth AMF entity.
  • the access device may select a corresponding AMF entity according to the corresponding relationship, which is not specifically limited in this embodiment.
  • each AMF entity also needs to notify the access device of the length of the primary group identifier and the length of the backup group identifier.
  • the length of the primary group identifier and the backup group identifier may be represented by a number of bits, or may be represented by a mask, which is not specifically limited in this embodiment of the present application.
  • the primary group identifier in step S501a and the backup group identifier in step S502a may be carried in a message together to be sent to the access device, or may be separately sent to the access device by two messages.
  • the embodiment of the present application does not specifically limit this.
  • the primary group identifier in step S501b and the backup group identifier in step S502b may be carried in a message together to be sent to the access device, or may be separately sent to the access device by two messages;
  • step S501c The primary group identifier in step S502c and the backup group identifier in step S502c may be carried in a message together to be sent to the access device, or may be separately sent to the access device through two messages;
  • the primary group identifier in step S501d The VRRP group in the step S502d may be sent to the access device in a message, or may be sent to the access device by using two messages, which is not specifically limited in this embodiment.
  • the first AMF entity may further send the primary group identifier and the backup group identifier configured in the first AMF entity to the SMF entity; the second AMF entity may also send the second AMF entity to the SMF entity.
  • the configured primary group ID and backup group ID may be used to the SMF entity.
  • the SMF entity can store the information of each AMF entity and the corresponding relationship between the primary group identifier and the backup group identifier configured in the corresponding AMF entity, and the SMF entity can subsequently select the corresponding AMF entity according to the corresponding relationship.
  • the group identifier of the terminal and the information of the AMF entity that it serves may be sent to the SMF entity when the PDU session is established, which is not specifically limited in this embodiment of the present application.
  • S505 An abnormality occurs in the first AMF entity.
  • the access device performs steps S506a and S507a; the second AMF entity performs steps S506b-S507b; the third AMF entity performs steps S506c-S507c; and the fourth AMF entity performs steps S506d-S507d;
  • the SMF entity performs steps S506e and S507e, as described in the following steps.
  • the access group identifier of the first AMF entity may be identified according to the correspondence between the VRRP group identifier and the AMF entity received by 502a-502d:
  • the service AMF entity of the terminal corresponding to the identifier 2 and the identifier 3 is configured as a second AMF entity, a third AMF entity, and a fourth AMF entity, which are not specifically limited in this embodiment.
  • each AMF entity separately sends the primary group identifier and the backup group identifier configured in the corresponding AMF entity to the SMF entity
  • the embodiment of the present application may not perform steps S506b-S507b, step S506c- S507c and steps S506d-S507d are collectively described herein, and are not described herein again.
  • the SMF entity may detect that the first AMF entity is abnormal.
  • the primary group identifier of the first AMF entity the service AMF entity of the terminal corresponding to the identifier 1, the identifier 2, and the identifier 3
  • the second AMF entity, the third AMF entity, and the fourth AMF entity are respectively set, which is not specifically limited in this embodiment.
  • the following descriptions are respectively taken from the access device acquiring the terminal-related uplink message and the SMF entity acquiring the terminal-related downlink message, which respectively include the following steps S508-S509 and steps S510-S511.
  • the access device acquires an uplink message related to the terminal.
  • step S508 For the related description of step S508, refer to step S408, and details are not described herein again.
  • the access device continues to perform step S509a;
  • the access device proceeds to step S509b;
  • the access device proceeds to step S509c.
  • the access device sends, according to the group identifier 1, a terminal-related uplink message to the second AMF entity, so that the second AMF entity receives the uplink message related to the terminal from the access device.
  • the access device may determine, according to the VRRP group identifier received in step S502b and the group identifier 1 obtained in step S508a, that the AMF entity corresponding to the group identifier 1 is the second AMF entity, and further to the second AMF entity. Send the uplink message related to the terminal.
  • S509b The access device sends, according to the group identifier 2, a terminal-related uplink message to the third AMF entity, so that the third AMF entity receives the uplink message related to the terminal from the access device.
  • the access device may determine, according to the VRRP group identifier received in step S502c and the group identifier 2 obtained in step S508b, that the AMF entity corresponding to the group identifier 2 is a third AMF entity, and further to the third AMF entity. Send the uplink message related to the terminal.
  • S509c The access device sends, according to the group identifier 3, a terminal-related uplink message to the fourth AMF entity, so that the fourth AMF entity receives the uplink message related to the terminal from the access device.
  • the access device may determine, according to the VRRP group identifier received in step S502d and the group identifier 3 obtained in step S508c, that the AMF entity corresponding to the group identifier 3 is the fourth AMF entity, and further to the fourth AMF entity. Send the uplink message related to the terminal.
  • the difference from the embodiment shown in FIG. 4 is that, in the embodiment shown in FIG. 4, when the first AMF entity is initially configured, the first AMF entity sends only the configured primary group identifier to the access device. When the other AMF entity detects that the first AMF entity is abnormal, the other AMF entity notifies the access device that the terminal corresponding to the primary group identifier is taken over by itself; and in the embodiment shown in FIG. 5, when the AMF entity is initially configured. The AMF entity can send the configured primary group identifier and backup group identifier to the access device.
  • the AMF entity can take over the terminals and provide services for the terminals.
  • the actions of the second AMF entity, the third AMF entity, and the fourth AMF entity are also similar to the first AMF entity, and details are not described herein again.
  • the first AMF entity can synchronize the context of the served terminal to another AMF entity that configures the group identifier of the terminal
  • the first AMF entity is abnormal
  • the terminal related message may be sent to other AMF entities configured with the group identifier according to the group identifier, so that if the first mobility management entity is abnormal, the terminal may be prevented from being restarted due to the context loss of the terminal being served.
  • the registration process that is, the current process of maintaining the terminal being served is not interrupted.
  • the contexts of the terminals in different terminal groups can be separately backed up to a plurality of different AMF entities, that is, one-to-many backup can be implemented.
  • one or more terminal groups of the first AMF entity are respectively taken over by a plurality of different AMF entities, thereby reducing the impact on the single AMF entity due to the abnormality of the first AMF entity.
  • the traditional 1+1 backup it saves resources and compensates for the problem of context loss in the traditional MME pool.
  • the operations of the access device, the SMF entity, and the respective AMF entities in the foregoing steps S501 to S511 can be performed by the processor 301 in the network device 300 shown in FIG. 3, by calling the application code stored in the memory 303.
  • the embodiment does not impose any limitation on this.
  • the communication system shown in FIG. 1 is applied to the 5G network shown in FIG. 2, and the configuration of the AMF entity group is as shown in Table 5.
  • AMF entity 1 is the first AMF entity
  • AMF entity 2 is The second AMF entity
  • the AMF entity 3 is the third AMF entity
  • the AMF entity 4 is the fourth AMF entity.
  • the communication method provided by the embodiment of the present application may also be as shown in FIG.
  • the S601a-S601d is similar to the S501a-S501d. The difference is that the primary group identifier in the embodiment shown in FIG. 5 is replaced by the group identifier in the embodiment shown in FIG. I will not repeat them here.
  • the first AMF entity sends an indication message 1 to the access device, so that the access device receives the indication message 1 from the first AMF entity.
  • the indication message 1 is used to indicate that in the case that an abnormality occurs in the first AMF entity, the terminal in the terminal group corresponding to the identifier 1 is served by the second AMF entity, and the terminal in the terminal group corresponding to the identifier 2 is provided by the third AMF entity.
  • the service, the terminal in the terminal group corresponding to the identifier 3 is served by the fourth AMF entity.
  • the access device may save the correspondence between the group identifier 1 and the first AMF entity and the second AMF entity, and the correspondence between the group identifier 2 and the first AMF entity and the third AMF entity.
  • the first AMF entity is the primary AMF entity of the group identifier 1, the group identifier 2, and the group identifier 3.
  • the second AMF entity is the backup AMF entity of the group identifier 1
  • the third AMF entity is the backup AMF entity of the group identifier 2.
  • the four AMF entities act as backup AMF entities for group identification 3. In this way, the access device may select the corresponding AMF entity according to the corresponding relationship, which is not specifically limited in this embodiment.
  • the second AMF entity sends an indication message 2 to the access device, so that the access device receives the indication message 2 from the second AMF entity.
  • the indication message 2 is used to indicate that, in the case that an abnormality occurs in the second AMF entity, the terminal in the terminal group corresponding to the identifier 4 is served by the first AMF entity, and the terminal in the terminal group corresponding to the identifier 5 is provided by the third AMF entity.
  • the service, the terminal in the terminal group corresponding to the identifier 6 is served by the fourth AMF entity.
  • the access device may save the correspondence between the group identifier 4 and the second AMF entity and the first AMF entity, and the correspondence between the group identifier 5 and the second AMF entity and the third AMF entity.
  • the second AMF entity is the primary AMF entity of the group identifier 4, the group identifier 5, and the group identifier 6.
  • the first AMF entity is the backup AMF entity of the group identifier 4
  • the third AMF entity is the backup AMF entity of the group identifier 5.
  • the four AMF entities act as backup AMF entities for group identification 6. In this way, the access device may select the corresponding AMF entity according to the corresponding relationship, which is not specifically limited in this embodiment.
  • the third AMF entity sends an indication message 3 to the access device, so that the access device receives the indication message 3 from the third AMF entity.
  • the indication message 3 is used to indicate that in the case that an abnormality occurs in the third AMF entity, the terminal in the terminal group corresponding to the identifier 7 is served by the first AMF entity, and the terminal in the terminal group corresponding to the identifier 8 is provided by the second AMF entity.
  • the service, the terminal in the terminal group corresponding to the identifier 9 is served by the fourth AMF entity.
  • the access device may save the correspondence between the group identifier 7 and the third AMF entity and the first AMF entity, and the correspondence between the group identifier 8 and the third AMF entity and the second AMF entity.
  • the third AMF entity is the primary AMF entity of the group identifier 7, the group identifier 8, and the group identifier 9, the second AMF entity is the backup AMF entity of the group identifier 8, the first AMF entity is the backup AMF entity of the group identifier 7, and the first The four AMF entities act as backup AMF entities for group identification 9.
  • the access device may select the corresponding AMF entity according to the corresponding relationship, which is not specifically limited in this embodiment.
  • the fourth AMF entity sends an indication message 4 to the access device, so that the access device receives the indication message 4 from the fourth AMF entity.
  • the indication message 4 is used to indicate that, in the case that an abnormality occurs in the fourth AMF entity, the terminal in the terminal group corresponding to the identifier 10 is served by the first AMF entity, and the terminal in the terminal group corresponding to the identifier 11 is provided by the second AMF entity.
  • the service, the terminal in the terminal group corresponding to the identifier 12 is served by the third AMF entity.
  • the access device may save the correspondence between the group identifier 10 and the fourth AMF entity and the first AMF entity, and the correspondence between the group identifier 11 and the fourth AMF entity and the second AMF entity.
  • the fourth AMF entity is the primary AMF entity of the group identifier 10, the group identifier 11 and the group identifier 12, the second AMF entity is the backup AMF entity of the group identifier 11, the third AMF entity is the backup AMF entity of the group identifier 12, and the third An AMF entity acts as a backup AMF entity for group identification 10.
  • the access device may select the corresponding AMF entity according to the corresponding relationship, which is not specifically limited in this embodiment.
  • the group identifier in step S601a and the indication message 1 in step S602a may be carried in a message and sent to the access device, or may be sent separately through two messages.
  • the embodiment of the present application does not specifically limit this.
  • the group identifier in step S601b and the indication message 2 in step S602b may be carried in a message together to be sent to the access device, or may be separately sent to the access device through two messages; in step S601c The group identifier and the indication message 3 in step S602c may be carried in a message together to be sent to the access device, or may be separately sent to the access device by two messages; the group identifier in step S601d and step S602d
  • the indication message 4 may be carried in a message and sent to the access device, or may be sent to the access device by using two messages, which is not specifically limited in this embodiment of the present application.
  • the first AMF entity may further send the group identifier and the indication message 1 configured in the first AMF entity to the SMF entity; the second AMF entity may further send the configuration in the second AMF entity to the SMF entity.
  • Group identification and indication message 2; the third AMF entity may also send the group identity and indication message 3 configured in the third AMF entity to the SMF entity; the fourth AMF entity may also send the group configured in the fourth AMF entity to the SMF entity Identify and indicate message 4.
  • the SMF entity can save the correspondence between each group identifier and the primary AMF entity and the backup AMF entity, and the SMF entity can subsequently select the corresponding AMF entity according to the corresponding relationship.
  • the group identifier of the terminal and the information of the AMF entity that it serves may be sent to the SMF entity when the PDU session is established, which is not specifically limited in this embodiment of the present application.
  • the S603a-S603d is similar to the S602a-S602d. The only difference is that the access device in the S602a-S602d is replaced by the SMF entity in the S603a-S603d. For details, refer to S602a-S602d, and details are not described herein.
  • S606 An abnormality occurs in the first AMF entity.
  • the access device performs steps S607a and S608a; the SMF entity performs steps S607e and S608e, as described in the following steps.
  • the access device may: according to the indication message received by 602a-602d, the group identifier of the first AMF entity: identifier 1, identifier 2, and identifier 3.
  • the service AMF entity of the terminal is configured as a second AMF entity, a third AMF entity, and a fourth AMF entity, which are not specifically limited in this embodiment.
  • the SMF entity may: according to the indication message received by the 603a-603d, the group identifier of the first AMF entity: the identifier corresponding to the identifier 1, the identifier 2, and the identifier 3.
  • the service AMF entity is configured as a second AMF entity, a third AMF entity, and a fourth AMF entity, which are not specifically limited in this embodiment of the present application.
  • FIG. 5 For example, the embodiment shown in FIG. 5 is omitted, and details are not described herein again.
  • the S610a-S610c is similar to the S509a-S509c. The difference is that the access device in the S509a-S509c determines the AMF entity corresponding to the group identifier according to the VRRP group identifier. In this embodiment, the AMF entity corresponding to the group identifier is determined according to the indication message. Reference may be made to the embodiment shown in FIG. 5, and details are not described herein again.
  • the access device may determine, according to the VRRP group identity, the AMF entity of the terminal that identifies the primary group identity managed by the AMF entity according to the VRRP identity; in the embodiment shown in FIG. 6, only in the primary AMF entity.
  • the group identifier of the terminal served when the primary AMF entity does not have an abnormality is configured, and when the primary AMF entity is abnormal, the information of the backup AMF entity of the terminal identified by the group identifier is taken over.
  • the access device may determine, according to the information of the backup AMF entity, the backup AMF entity that takes over the terminal identified by the group identity.
  • the first AMF entity can synchronize the context of the served terminal to another AMF entity that configures the group identifier of the terminal
  • the first AMF entity is abnormal
  • the terminal related message may be sent to other AMF entities configured with the group identifier according to the group identifier, so that if the first mobility management entity is abnormal, the terminal may be prevented from being restarted due to the context loss of the terminal being served.
  • the registration process that is, the current process of maintaining the terminal being served is not interrupted.
  • the contexts of the terminals in different terminal groups can be separately backed up to a plurality of different AMF entities, that is, one-to-many backup can be implemented.
  • one or more terminal groups of the first AMF entity are respectively taken over by a plurality of different AMF entities, thereby reducing the impact on the single AMF entity due to the abnormality of the first AMF entity.
  • the traditional 1+1 backup it saves resources and compensates for the problem of context loss in the traditional MME pool.
  • the operations of the access device, the SMF entity, and the respective AMF entities in the foregoing steps S601 to S612 can be performed by the processor 301 in the network device 300 shown in FIG. 3 calling the application code stored in the memory 303.
  • the embodiment does not impose any limitation on this.
  • the embodiment shown in FIG. 4 may be combined with the embodiment shown in FIG. 5, or the embodiment shown in FIG. 4 may be combined with the embodiment shown in FIG. 6.
  • This embodiment of the present application does not specifically limit this.
  • the solution provided by the embodiment of the present application is mainly introduced from the perspective of interaction between the network elements.
  • the foregoing communication device and the second mobility management entity include corresponding hardware structures and/or software modules for performing the respective functions in order to implement the above 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 perform the division of the function module on the communication device and the second 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 process.
  • 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 communication device 70 involved in the above embodiment.
  • the communication device 70 includes an acquisition module 701 and a transmission module 702.
  • the obtaining module 701 is configured to obtain a first group identifier of a terminal group where the first terminal of the first mobility management entity service is located.
  • the sending module 702 is configured to send, according to the first group identifier, a message related to the first terminal to the second mobility management entity, where the second mobility management entity is the first terminal.
  • the context of the mobile management entity is configured to send, according to the first group identifier, a message related to the first terminal to the second mobility management entity, where the second mobility management entity is the first terminal.
  • the first group identifier is a primary group identifier configured in the first mobility management entity, and a backup group identifier configured in the second mobility management entity.
  • the communication device 70 further includes: a receiving module 703.
  • the receiving module 703 is configured to receive a first indication message, where the first indication message is used to indicate that the terminal in the terminal group corresponding to the first group identifier is served by the second mobility management entity.
  • the receiving module 703 is specifically configured to: receive the first indication message from the second mobility management entity, where the first indication message is sent to the second mobility management entity to determine that the first mobility management entity is abnormal. Communication equipment.
  • the receiving module 703 is configured to receive a first indication message, where the first indication message is used to indicate that, in a case that an abnormality occurs in the first mobility management entity, the terminal group corresponding to the first group identifier is The terminal is served by the second mobility management entity.
  • the receiving module 703 is specifically configured to: before the first mobility management entity generates an abnormality, receive the first indication message.
  • the sending module 702 is specifically configured to: determine that an abnormality occurs in the first mobility management entity; and send, according to the first group identifier, a message related to the first terminal to the second mobility management entity.
  • the obtaining module 701 is specifically configured to: receive a message related to the first terminal, where the message related to the first terminal carries the first group identifier of the terminal group where the first terminal is located; or, in the context of the first terminal Determining a first group identifier of the terminal group where the first terminal is located.
  • the obtaining module 701 is further configured to obtain a second group identifier of the terminal group where the second terminal of the first mobility management entity service is located.
  • the sending module 702 is further configured to send, according to the second group of identifiers, a second terminal related message to the third mobility management entity, where the first mobility management entity is abnormal, where the third mobility management entity is the second The mobile management entity of the context of the terminal.
  • the communication device in the embodiment of the present application includes an access device or a session management entity.
  • FIG. 8 shows a possible structural diagram of the communication device 80 involved in the above embodiment, and the communication device 80 includes a processing module 801 and a communication module 802.
  • the processing module 801 can be used to perform operations that can be performed by the obtaining module 701 in FIG. 7, and the communications module 802 can be used to perform operations that can be performed by the sending module 702 in FIG.
  • the communication module 802 is further configured to perform the operations that can be performed by the receiving module 703 in FIG. 7.
  • the communication device is presented in the form of dividing each functional module corresponding to each function, or the communication device 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
  • communication device 70 or communication device 80 may take the form shown in FIG.
  • the obtaining module 701, the sending module 702, and the receiving module 703 in FIG. 7 can be implemented by the processor 401 and the memory 403 of FIG.
  • the obtaining module 701, the sending module 702, and the receiving module 703 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 processing module 801 and the communication module 802 in FIG. 8 may be implemented by the processor 301 and the memory 303 of FIG.
  • the processing module 801 and the communication module 802 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 communication device provided by the embodiment of the present application can be used to perform the foregoing communication method. Therefore, the technical effects that can be obtained by reference to the foregoing method embodiments are not described herein.
  • FIG. 9 shows a possible structural diagram of the second mobility management entity 90 involved in the above embodiment.
  • the second mobility management entity 90 includes a receiving module 901, a determining module 902, and a sending module 903.
  • the receiving module 901 is configured to receive a context of the first terminal that is served by the first mobility management entity of the first mobility management entity.
  • the determining module 902 is configured to determine that an abnormality occurs in the first mobility management entity.
  • the sending module 903 is configured to send a first indication message to the communications device, where the first indication message is used to indicate that the terminal in the terminal group corresponding to the first group identifier is served by the second mobility management entity, where the first group identifier is Group ID of the terminal group where the first terminal is located.
  • the receiving module 901 is further configured to receive a message related to the first terminal from the communications device.
  • the receiving module 901 is further configured to receive a context of the second terminal served by the third mobility management entity of the third mobility management entity.
  • the determining module 902 is further configured to determine that an abnormality occurs in the third mobility management entity.
  • the sending module 903 is further configured to send a second indication message to the communications device, where the second indication message is used to indicate that the terminal in the terminal group corresponding to the second group of identifiers is served by the second mobility management entity, where the second group identifier is The group ID of the terminal group where the second terminal is located.
  • FIG. 10 is a schematic diagram showing a possible structure of the second mobility management entity 100 involved in the foregoing embodiment, where the second mobility management entity 100 includes: a processing module. 1002 and a communication module 1001.
  • the processing module 1002 can be used to perform the operations that can be performed by the determining module 902 in FIG. 9.
  • the communications module 1001 can be used to perform operations performed by the receiving module 901 and the sending module 903 in FIG. The embodiments of the present application are not described herein again.
  • the second mobility management entity is presented in the form of dividing each function module corresponding to each function, or the second mobility management entity is presented in a form of dividing each function 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 second mobility management entity 90 or the second mobility management entity 100 may take the form shown in FIG.
  • the receiving module 901, the determining module 902, and the transmitting module 903 in FIG. 9 can be implemented by the processor 301 and the memory 303 of FIG.
  • the receiving module 901, the determining module 902, and the sending module 903 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 1002 and the communication module 1001 in FIG. 10 may be implemented by the processor 301 and the memory 303 of FIG.
  • the processing module 1002 and the communication module 1001 may be executed by calling the application code stored in the memory 303 by the processor 301, which is not limited in this embodiment.
  • the second mobility management entity provided by the embodiment of the present application can be used to perform the foregoing communication 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, and is configured to support a communication device to implement the functions involved in the foregoing aspects, for example, if an abnormality occurs in the first mobility management entity, The first group identifier of the terminal group where the first terminal of the first mobility management entity service is located, and the first terminal related message is sent to the second mobility management entity.
  • the chip system also includes a memory. The memory is used to store program instructions and data necessary for the communication device.
  • 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 embodiment of the present application provides a chip system, where the chip system includes a processor, configured to support a second mobility management entity to implement the functions involved in the foregoing aspects, for example, receiving a first from a first mobility management entity.
  • the chip system also includes a memory.
  • the memory is used to save necessary program instructions and data of the second 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)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephone Function (AREA)

Abstract

本申请实施例提供通信方法、设备及系统，可以在AMF实体失效时，避免由于正在服务的终端的上下文丢失而触发终端的重新注册流程。方法包括：通信设备获取第一移动管理实体服务的第一终端所在终端组的第一组标识；在该第一移动管理实体发生异常的情况下，该通信设备根据该第一组标识，向第二移动管理实体发送该第一终端相关的消息，其中，该第二移动管理实体为存在该第一终端的上下文的移动管理实体。

Description

通信方法、设备及系统
本申请要求于2017年7月31日提交中国专利局、申请号为201710640133.9、发明名称为“通信方法、设备及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及通信方法、设备及系统。
背景技术
现有技术中，当接入和移动性管理(access and mobility management function，AMF)实体确定不再为终端提供服务时，AMF实体给无线接入网(radio access network，RAN)设备和其他核心网网络功能实体，如会话管理功能(session management function，SMF)实体，发送“不可用”指示，由RAN设备和其他核心网网络功能实体将该AMF实体标注为失效。这样，在后续选择AMF实体时不再考虑该AMF实体。但是，若AMF失效且失效的AMF实体正在服务的终端的上下文没有备份，这些终端的网络连接将丢失，后续需要发起重新注册过程。
现有技术中，一种方法是将终端的上下文备份到非结构化数据存储功能(unstructured data storage function，UDSF)实体，这样当AMF实体失效时，RAN设备或其他核心网网络功能实体重新选择一个不失效的目标AMF实体为该终端继续服务，并且目标AMF实体从UDSF实体中读取终端的上下文，从而可以继续为该终端提供服务，无需该终端发起重新注册过程。
但是，上述方案依赖于UDSF实体，因此限制一组互为备份关系的AMF实体来自同一个厂家。当互为备份关系的AMF实体来自不同厂家时，由于不同厂家的AMF实体与UDSF实体间的数据格式不标准化，因此可能导致失效的AMF实体正在服务的终端的上下文丢失，从而触发终端的重新注册流程。
发明内容
本申请实施例提供通信方法、设备及系统，可以在移动管理实体失效时，避免由于正在服务的终端的上下文丢失而触发终端的重新注册流程。
为达到上述目的，本申请实施例提供如下技术方案：
第一方面，提供一种通信方法，该方法包括：通信设备获取第一移动管理实体服务的第一终端所在终端组的第一组标识；在该第一移动管理实体发生异常的情况下，该通信设备根据该第一组标识，向第二移动管理实体发送该第一终端相关的消息，其中，该第二移动管理实体为存在该第一终端的上下文的移动管理实体。基于该方案，由于第一移动管理实体可以将服务的第一终端的上下文同步至第二移动管理实体，在第一移动管理实体发生异常的情况下，可以根据第一终端所在终端组的第一组标识，向第二移动管理实体发送第一终端相关的消息，因此可以在第一移动管理实体发生异常的情况下，避免由于正在服务的终端的上下文丢失而触发终端的重新注册流程，即可以保持正在服务的终端的当前流程不中断。
可选的，该第一组标识为配置在该第一移动管理实体中的主组标识、配置在该第二移动 管理实体中的备份组标识。其中，本申请实施例中的主组标识用于指示在配置该主组标识的移动管理实体未发生异常的情况下，终端所在终端组的组标识为该主组标识的终端由配置该主组标识的移动管理实体提供服务；本申请实施例中的备份组标识用于指示在将该备份组标识配置为主组标识的移动管理实体发生异常的情况下，终端所在终端组的组标识为该备份组标识的终端由将该备份组标识配置为备份组标识的移动管理实体提供服务。
在一种可能的设计中，方法还包括：该通信设备接收第一指示消息，该第一指示消息用于指示该第一组标识对应的终端组中的终端由该第二移动管理实体提供服务。
可选的，该通信设备接收第一指示消息，包括：该通信设备接收来自该第二移动管理实体的该第一指示消息，其中，该第一指示消息为该第二移动管理实体确定该第一移动管理实体发生异常的情况下发送给该通信设备的。也就是说，第二移动管理实体在确定第一移动管理实体发生异常的情况下，才向通信设备通知该第一组标识对应的终端组中的终端由该第二移动管理实体提供服务。这样，通信设备可以根据该第一指示消息和第一组标识，向该第二移动管理实体发送该第一终端相关的消息。
在一种可能的设计中，该方法还包括：该通信设备接收第一指示消息，该第一指示消息用于指示在该第一移动管理实体发生异常的情况下，该第一组标识对应的终端组中的终端由该第二移动管理实体提供服务。
可选的，该通信设备接收第一指示消息，包括：在该第一移动管理实体发生异常之前，该通信设备接收该第一指示消息；在该第一移动管理实体发生异常的情况下，该通信设备根据该第一组标识，向第二移动管理实体发送该第一终端相关的消息，包括：该通信设备确定该第一移动管理实体发生异常；该通信设备根据该第一组标识，向该第二移动管理实体发送该第一终端相关的消息。也就是说，在第一移动管理实体发生异常之前，通信设备可以提前获知在该第一移动管理实体发生异常的情况下，该第一组标识对应的终端组中的终端由该第二移动管理实体提供服务。这样，在第一移动管理实体发生异常的情况下，通信设备可以根据该第一指示消息和第一组标识，向该第二移动管理实体发送该第一终端相关的消息。
其中，本申请实施例中，该第一指示消息可以是第二移动管理实体通知给通信设备的，也可以是第一移动管理实体或者网管通知给通信设备的，本申请实施例对此不作具体限定。
可选的，该通信设备获取第一移动管理实体服务的第一终端所在终端组的第一组标识，包括：该通信设备接收该第一终端相关的消息，其中，该第一终端相关的消息中携带该第一终端所在终端组的第一组标识；或者，该通信设备从该第一终端的上下文中确定该第一终端所在终端组的第一组标识。通过该方案，通信设备可以获取第一移动管理实体服务的第一终端所在终端组的组标识。
可选的，该方法还包括：该通信设备获取该第一移动管理实体服务的第二终端所在终端组的第二组标识；在该第一移动管理实体发生异常的情况下，该通信设备根据该第二组标识，向第三移动管理实体发送该第二终端相关的消息，其中，该第三移动管理实体为存在该第二终端的上下文的移动管理实体。基于该方案，一方面，由于第一移动管理实体还可以将服务的第二终端的上下文同步至第三移动管理实体，在第一移动管理实体发生异常的情况下，可以根据第二终端所在终端组的第二组标识，向第三移动管理实体发送第二终端相关的消息，因此可以在第一移动管理实体发生异常的情况下，避免由于正在服务的终端的上下文丢失而触发终端的重新注册流程，即可以保持正在服务的终端的当前流程不中断；另一方面，由于第一移动管理实体可以将终端进行分组，不同终端组内的终端的上下文可以分别备份到多个 不同的移动管理实体，也就是说可以实现一对多备份。这样，在该第一移动管理实体发生异常的情况下，由多个不同的移动管理实体分别接管第一移动管理实体的一个或多个终端组，因此减少了由于第一移动管理实体异常对单个移动管理实体的冲击，相对于传统的1+1备份节省资源，同时弥补了传统的移动性管理实体MME池中的上下文丢失问题。
可选的，该通信设备包括接入设备或者会话管理实体。
第二方面，提供一种通信方法，该方法包括：第二移动管理实体接收来自第一移动管理实体的该第一移动管理实体服务的第一终端的上下文；该第二移动管理实体确定该第一移动管理实体发生异常；该第二移动管理实体向通信设备发送第一指示消息，该第一指示消息用于指示第一组标识对应的终端组中的终端由该第二移动管理实体提供服务，其中，该第一组标识为该第一终端所在终端组的组标识。基于该方案，由于第一移动管理实体可以将服务的第一终端的上下文同步至第二移动管理实体，在第一移动管理实体发生异常的情况下，第二移动管理实体可以通知通信设备第一组标识对应的终端组中的终端由该第二移动管理实体提供服务，其中，该第一组标识为该第一终端所在终端组的组标识。因此，通信设备可以根据该第一指示消息和第一组标识，向第二移动管理实体发送第一终端相关的消息，从而可以在第一移动管理实体发生异常的情况下，避免由于正在服务的终端的上下文丢失而触发终端的重新注册流程，即可以保持正在服务的终端的当前流程不中断。
可选的，该方法还包括：该第二移动管理实体接收来自该通信设备的该第一终端相关的消息。基于该方案，第二移动管理实体可以获取该第一终端相关的消息。
可选的，该方法包括：该第二移动管理实体接收来自第三移动管理实体的该第三移动管理实体服务的第二终端的上下文；该第二移动管理实体确定该第三移动管理实体发生异常；该第二移动管理实体向该通信设备发送第二指示消息，该第二指示消息用于指示第二组标识对应的终端组中的终端由该第二移动管理实体提供服务，其中，该第二组标识为该第二终端所在终端组的组标识。基于该方案，一方面，由于第三移动管理实体可以将服务的第二终端的上下文同步至第二移动管理实体，在第三移动管理实体发生异常的情况下，第二移动管理实体可以通知通信设备第二组标识对应的终端组中的终端由该第二移动管理实体提供服务，其中，该第二组标识为该第二终端所在终端组的组标识。因此，通信设备可以根据该第二指示消息和第二组标识，向第二移动管理实体发送第二终端相关的消息，从而可以在第三移动管理实体发生异常的情况下，避免由于正在服务的终端的上下文丢失而触发终端的重新注册流程，即可以保持正在服务的终端的当前流程不中断。另一方面，由于第二移动管理实体可以分别为第一移动管理实体和第三移动管理实体备份，因此可以实现一对多备份，从而相对于传统的1+1备份节省资源。
第三方面，提供了一种通信设备，该通信设备具有实现上述第一方面所述的方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第四方面，提供了一种通信设备，包括：处理器、存储器、总线和通信接口；该存储器用于存储计算机执行指令，该处理器与该存储器通过该总线连接，当该通信设备运行时，该处理器执行该存储器存储的该计算机执行指令，以使该通信设备执行如上述第一方面中任一所述的通信方法。
第五方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第一方面中任意一项所述的通信方法。
第六方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第一方面中任意一项所述的通信方法。
第七方面，提供了一种芯片系统，该芯片系统包括处理器，用于支持通信设备实现上述方面中所涉及的功能，例如在第一移动管理实体发生异常的情况下，根据第一移动管理实体服务的第一终端所在终端组的第一组标识，向第二移动管理实体发送第一终端相关的消息。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存通信设备必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
其中，第三方面至第七方面中任一种设计方式所带来的技术效果可参见第一方面中不同设计方式所带来的技术效果，此处不再赘述。
第八方面，提供了一种第二移动管理实体，该第二移动管理实体具有实现上述第二方面所述的方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第九方面，提供了一种第二移动管理实体，包括：处理器、存储器、总线和通信接口；该存储器用于存储计算机执行指令，该处理器与该存储器通过该总线连接，当该第二移动管理实体运行时，该处理器执行该存储器存储的该计算机执行指令，以使该第二移动管理实体执行如上述第二方面中任一所述的通信方法。
第十方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第二方面中任意一项的业务会话建立方法。
第十一方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第二方面中任意一项所述的通信方法。
第十二方面，提供了一种芯片系统，该芯片系统包括处理器，用于支持第二移动管理实体实现上述方面中所涉及的功能，例如接收来自第一移动管理实体的第一移动管理实体服务的第一终端的上下文。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存第二移动管理实体必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
其中，第八方面至第十二方面中任一种设计方式所带来的技术效果可参见第二方面中不同设计方式所带来的技术效果，此处不再赘述。
第十三方面，提供了一种通信系统，该通信系统包括第一移动管理实体、第二移动管理实体以及通信设备；其中，该第一移动管理实体，用于向该第二移动管理实体发送该第一移动管理实体服务的第一终端的上下文；该第二移动管理实体，用于接收来自该第一移动管理实体的该第一终端的上下文；该通信设备，用于获取该第一终端所在终端组的第一组标识，并在该第一移动管理实体发生异常的情况下，根据该第一组标识，向该第二移动管理实体发送该第一终端相关的消息；该第二移动管理实体，还用于接收来自该通信设备的该第一终端相关的消息。
在一种可能的设计中，该第二移动管理实体，还用于确定该第一移动管理实体发生异常；该第二移动管理实体，还用于向该通信设备发送第一指示消息，该第一指示消息用于指示该第一组标识对应的终端组中的终端由该第二移动管理实体提供服务；该通信设备，还用于接收该第一指示消息。
在一种可能的设计中，该通信设备，还用于在该第一移动管理实体发生异常之前，接收第一指示消息，该第一指示消息用于指示在该第一移动管理实体发生异常的情况下，该第一 组标识对应的终端组中的终端由该第二移动管理实体提供服务；该通信设备，还用于确定该第一移动管理实体发生异常。
其中，第十三方面中任一种设计方式所带来的技术效果可参见上述第一方面中不同设计方式所带来的技术效果，此处不再赘述。
本申请的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
图1为本申请实施例提供的通信系统的架构示意图；
图2为本申请实施例提供的5G网络的架构示意图；
图3为本申请实施例提供的网络设备的硬件结构示意图；
图4为本申请实施例提供的通信方法的流程示意图一；
图5为本申请实施例提供的通信方法的流程示意图二；
图6为本申请实施例提供的通信方法的流程示意图二；
图7为本申请实施例提供的通信设备的结构示意图一；
图8为本申请实施例提供的通信设备的结构示意图二；
图9为本申请实施例提供的第二移动管理实体的结构示意图一；
图10为本申请实施例提供的第二移动管理实体的结构示意图二。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；本申请中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。比如，本申请实施例中的第二移动管理实体和第三移动管理实体可能是相同的移动管理实体，也可能是不同的移动管理实体，本申请实施例对此不作具体限定。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
如图1所示，为本申请实施例提供的通信系统10的架构示意图。该通信系统10包括通信设备101和移动管理实体组102。该移动管理实体组102中包括至少两个互为备份关系的移动管理实体，如图1中的第一移动管理实体102a和第二移动管理实体102b。当然，图1中的移动管理实体组102中还可以包括其它移动管理实体，比如第三移动管理实体等，本申请实施例对此不作具体限定。
其中，第一移动管理实体102a，用于向第二移动管理实体102b发送第一移动管理实体 102a服务的第一终端的上下文。
通信设备101，用于获取第一终端所在终端组的第一组标识，并在所述第一移动管理实体102a发生异常的情况下，根据该第一组标识，向第二移动管理实体102b发送第一终端相关的消息。
第二移动管理实体102b，用于接收来自通信设备101的第一终端相关的消息。
可选的，图1中的第一移动管理实体102a、第二移动管理实体102b和通信设备101之间可能直接通信，也可能通过其他设备的转发进行通信，本申请实施例对此不作具体限定。
可选的，图1中的通信设备102可以包括接入设备或者会话管理功能实体等，本申请实施例对此不做具体限定。其中，若通信设备102为接入设备，则第一终端相关的消息为第一终端相关的上行消息；若通信设备102为会话管理功能实体，则第一终端相关的消息为第一终端相关的下行消息，在此进行统一说明，以下不再赘述。
可选的，本申请实施例中移动管理实体发生异常包括移动管理实体发生故障或者过载等情况，在此进行统一说明，以下不再赘述。
基于本申请实施例提供的通信系统，由于第一移动管理实体可以将服务的第一终端的上下文同步至第二移动管理实体，在第一移动管理实体发生异常的情况下，可以根据第一终端所在终端组的第一组标识，向第二移动管理实体发送第一终端相关的消息，因此可以在第一移动管理实体发生异常的情况下，避免由于正在服务的终端的上下文丢失而触发终端的重新注册流程，即可以保持正在服务的终端的当前流程不中断。
需要说明的是，本申请实施例中上下文的同步可以是上下文发生变化触发上下文的同步，也可以是设置一个定时器，定时器到时后触发上下文的同步，本申请实施例对同步的时机不作具体限定。
可选的，上述通信系统10可以应用于第五代(5rd generation，5G)网络以及未来其它的网络，本申请实施例对此不作具体限定。
其中，若上述通信系统10应用于5G网络，则如图2所示，通信设备所对应的网元或者实体可以为接入设备或者SMF实体；移动管理实体所对应的网元或者实体可以为接入与移动管理功能(Access and Mobility Management Function，AMF)实体。比如，第一移动管理实体102a所对应的网元或者实体可以为第一AMF实体；第二移动管理实体102b所对应的网元或者实体可以为第二AMF实体。
需要说明的是，图2中仅是示例性的画了两个AMF实体。当然，在实际部署中AMF实体组中还可能会包括多于两个AMF实体，本实施例对此不作具体限定。
此外，如图2所示，该5G网络还可以包括用户面功能(user plane function，UPF)实体、统一数据管理(unified data management，UDM)实体、鉴权服务器功能(authentication server function，AUSF)实体、策略控制功能(policy control function，PCF)实体等。可选的，该5G网络还可以包括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)，汇聚交换机，非第三代合作伙伴计划(3rd generation partnership project，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中的第一移动管理实体或通信设备可以由一个实体设备实现，也可以由多个实体设备共同实现，还可以是一个实体设备内的一个逻辑功能模块，本申请实施例对此不作具体限定。
例如，图1中的第一移动管理实体、第二移动管理实体或通信设备可以通过图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实体可以对应一个或多个全球唯一AMF标识(globally unique AMF identifier，GUAMI)，该GUAMI由公共陆地移动网络(public land mobile network，PLMN)标识(identifier，ID)、AMF实体所在区域的标识(AMF region ID)、AMF实体所在AMF实体组的标识(AMF Set ID)和AMF pointer(AMF标识)构成。其中，一个AMF实体的多个GUAMI可以通过AMF pointer进行区分，也就是说，不同GUAMI中的AMF pointer不同。当一个AMF实体对应多个GUAMI时，本申请实施例中的终端组的组标识可以是GUAMI或者GUAMI中的AMF pointer；当一个AMF实体对应一个GUAMI时，则本申请实施例中的终端组的组标识可以是AMF pointer+终端临时标识的高N位，也就是说，可以将终端临时标识的高N位用于标识不同的终端组。比如，以最高2位用于标识终端组为例，一个AMF实体提供服务的所有终端可以分成4组，这4组终端的终端临时标识分别以00、01、10、11开头。这相当于把AMF pointer加长了两位。该情况下，AMF实体需要通知接入设备和核心网设备如何从终端的标识中截取组标识，比如，AMF实体将终端组的组标识的长度通知给接入设备和核心网设备，在此进行统一说明，以下不再赘述。
此外，为了简化描述，本申请下述实施例用终端的组标识替换终端所在终端组的组标识，在此进行统一说明，以下不再赘述。
第二，AMF实体组
AMF实体组中包括多个互为备份关系的AMF实体，每个AMF实体中可以配置m个主组标识和n个备份组标识。其中，当AMF实体不发生异常时，AMF实体为组标识为该AMF实体对应的主组标识的终端提供服务；同时，该AMF实体保存组标识为该AMF实体对应的备份组标识的终端的上下文。当为组标识为该AMF实体对应的备份组标识的终端提供服务的AMF实体发生异常时，该AMF实体接管这些终端，为这些终端提供服务。下面将结合一些示例进行详细说明。
示例性的，假设AMF实体为1+1备份，即假设AMF实体组中包括两个AMF实体，比如分别为AMF实体1和AMF实体2，这两个AMF实体互为备份关系，每个AMF实体配置3个主组标识和3个备份组标识，如表一所示：
表一
AMF实体的名称 主组标识 备份组标识
AMF实体1 标识1、标识2、标识3 标识4、标识5、标识6
AMF实体2 标识4、标识5、标识6 标识1、标识2、标识3
则，当AMF实体1未发生异常时，AMF实体1为组标识为标识1、标识2和标识3的终端提供服务；同时，AMF实体1保存组标识为标识4、标识5和标识6的终端的上下文。 当为组标识为标识4、标识5和标识6的终端提供服务的AMF实体2发生异常时，该AMF实体1接管该组标识为标识4、标识5和标识6的终端，为这些终端提供服务。
当AMF实体2未发生异常时，AMF实体2为组标识为标识4、标识5和标识6的终端提供服务；同时，AMF实体2保存组标识为标识1、标识2和标识3的终端的上下文。当为组标识为标识1、标识2和标识3的终端提供服务的AMF实体1发生异常时，该AMF实体2接管该组标识为标识1、标识2和标识3的终端，为这些终端提供服务。
或者，示例性的，假设AMF实体为1+N备份，N为大于1的整数，即假设AMF实体组中包括大于两个AMF实体，比如包括AMF实体1、AMF实体2、AMF实体3和AMF实体4共四个AMF实体，这四个AMF实体互为备份关系，每个AMF实体配置3个主组标识和3个备份组标识，如表二所示：
表二
AMF实体的名称 主组标识 备份组标识
AMF实体1 标识1、标识2、标识3 标识4、标识7、标识10
AMF实体2 标识4、标识5、标识6 标识1、标识8、标识11
AMF实体3 标识7、标识8、标识9 标识2、标识5、标识12
AMF实体4 标识10、标识11、标识12 标识3、标识6、标识9
则，当AMF实体1未发生异常时，AMF实体1为组标识为标识1、标识2和标识3的终端提供服务；同时，AMF实体1保存组标识为标识4、标识7和标识10的终端的上下文。当为组标识为标识4的终端提供服务的AMF实体2发生异常时，该AMF实体1接管该组标识为标识4的终端，为这些终端提供服务；当为组标识为标识7的终端提供服务的AMF实体3发生异常时，该AMF实体1接管该组标识为标识7的终端，为这些终端提供服务；当为组标识为标识10的终端提供服务的AMF实体4发生异常时，该AMF实体1接管该组标识为标识10的终端，为这些终端提供服务。
当AMF实体2未发生异常时，AMF实体2为组标识为标识4、标识5和标识6的终端提供服务；同时，AMF实体2保存组标识为标识1、标识8和标识11的终端的上下文。当为组标识为标识1的终端提供服务的AMF实体1发生异常时，该AMF实体2接管该组标识为标识1的终端，为这些终端提供服务；当为组标识为标识8的终端提供服务的AMF实体3发生异常时，该AMF实体2接管该组标识为标识8的终端，为这些终端提供服务；当为组标识为标识11的终端提供服务的AMF实体4发生异常时，该AMF实体2接管该组标识为标识11的终端，为这些终端提供服务。
当AMF实体3未发生异常时，AMF实体3为组标识为标识7、标识8和标识9的终端提供服务；同时，AMF实体3保存组标识为标识2、标识5和标识12的终端的上下文。当为组标识为标识2的终端提供服务的AMF实体1发生异常时，该AMF实体3接管该组标识为标识2的终端，为这些终端提供服务；当为组标识为标识5的终端提供服务的AMF实体2发生异常时，该AMF实体3接管该组标识为标识5的终端，为这些终端提供服务；当为组标识为标识12的终端提供服务的AMF实体4发生异常时，该AMF实体3接管该组标识为标识12的终端，为这些终端提供服务。
当AMF实体4不发生异常时，AMF实体4为组标识为标识10、标识11和标识12的终端提供服务；同时，AMF实体4保存组标识为标识3、标识6和标识9的终端的上下文。当为组标识为标识3的终端提供服务的AMF实体1发生异常时，该AMF实体4接管该组标识 为标识3的终端，为这些终端提供服务；当为组标识为标识6的终端提供服务的AMF实体2发生异常时，该AMF实体4接管该组标识为标识6的终端，为这些终端提供服务；当为组标识为标识9的终端提供服务的AMF实体3发生异常时，该AMF实体4接管该组标识为标识9的终端，为这些终端提供服务。
可选的，表一或表二所示的备份关系中，一个AMF实体的备份组标识由所在AMF实体组的其他AMF实体平均负责。在实际的组网中，备份关系可以不是均等的。比如，若AMF实体3的容量＝2倍AMF实体2容量＝2倍AMF实体1容量，则配置的备份关系可以如表三所示。
表三
Figure PCTCN2018097138-appb-000001
则，当AMF实体1未发生异常时，AMF实体1为组标识为标识1、标识2和标识3的终端提供服务；同时，AMF实体1保存组标识为标识7、标识8和标识9的终端的上下文。当为组标识为标识7、标识8和标识9的终端提供服务的AMF实体3发生异常时，该AMF实体1接管该组标识为标识7、标识8和标识9的终端，为这些终端提供服务。
当AMF实体2未发生异常时，AMF实体2为组标识为标识4、标识5和标识6的终端提供服务；同时，AMF实体2保存组标识为标识10、标识11和标识12的终端的上下文。当为组标识为标识10、标识11和标识12的终端提供服务的AMF实体3发生异常时，该AMF实体2接管该组标识为标识10、标识11和标识12的终端，为这些终端提供服务。
当AMF实体3未发生异常时，AMF实体3为组标识为标识7、标识8、标识9、标识10、标识11、标识12的终端提供服务；同时，AMF实体3保存组标识为标识1、标识2、标识3、标识4、标识5和标识6的终端的上下文。当为组标识为标识1、标识2和标识3的终端提供服务的AMF实体1发生异常时，该AMF实体3接管该组标识为标识1、标识2和标识3的终端，为这些终端提供服务；当为组标识为标识4、标识5和标识6的终端提供服务的AMF实体2发生异常时，该AMF实体3接管该组标识为标识4、标识5和标识6的终端，为这些终端提供服务。
本申请实施例对AMF实体组中各个AMF实体的备份关系不作具体限定，可以根据实际需求灵活配置。
可选的，本申请实施例中，也可以不在AMF实体中同时配置主组标识和备份组标识，而是仅在主AMF实体中配置该主AMF实体未发生异常时服务的终端的组标识，以及当该主AMF实体发生异常时，分别接管组标识为这些组标识的终端的备份AMF实体的信息。比如，假设AMF实体组中两个AMF实体的备份关系如表一所示，则该备份关系也可以通过表四表示：
表四
主AMF实体的名称 组标识 备份AMF实体的名称
AMF实体1 标识1、标识2、标识3 AMF实体2
AMF实体2 标识4、标识5、标识6 AMF实体1
或者，比如，假设AMF实体组中四个AMF实体的备份关系如表二所示，则该备份关系也可以通过表五表示：
表五
Figure PCTCN2018097138-appb-000002
或者，比如，假设AMF实体组中四个AMF实体的备份关系如表三所示，则该备份关系也可以通过表六表示：
表六
Figure PCTCN2018097138-appb-000003
本申请实施例对AMF实体组中各个AMF实体的备份关系的表征形式不作具体限定。
其次，以图1所示的通信系统应用于图2所示的5G网络，AMF实体组的配置情况如表二所示为例，假设AMF实体1为第一AMF实体，AMF实体2为第二AMF实体，AMF实体3为第三AMF实体，AMF实体4为第四AMF实体，则本申请实施例提供的通信方法可以如图4所示，包括如下步骤：
S401a、第一AMF实体向接入设备发送第一AMF实体中配置的主组标识，以使得接入 设备接收来自第一AMF实体的第一AMF实体中配置的主组标识。
其中，结合表二可知，第一AMF实体中配置的主组标识包括标识1、标识2和标识3。该主组标识用于指示对应的终端组中的终端由第一AMF实体提供服务。
可选的，接入设备接收到第一AMF实体中配置的主组标识之后，可以保存第一AMF实体的信息和第一AMF实体中配置的主组标识的对应关系。这样，接入设备后续可以根据该对应关系选择相应的AMF实体，本申请实施例对此不作具体限定。
S401b、第二AMF实体向接入设备发送第二AMF实体中配置的主组标识，以使得接入设备接收来自第二AMF实体的第二AMF实体中配置的主组标识。
其中，结合表二可知，第二AMF实体中配置的主组标识包括标识4、标识5和标识6。该主组标识用于指示对应的终端组中的终端由第二AMF实体提供服务。
可选的，接入设备接收到第二AMF实体中配置的主组标识之后，可以保存第二AMF实体的信息和第二AMF实体中配置的主组标识的对应关系。这样，接入设备后续可以根据该对应关系选择相应的AMF实体，本申请实施例对此不作具体限定。
S401c、第三AMF实体向接入设备发送第三AMF实体中配置的主组标识，以使得接入设备接收来自第三AMF实体的第三AMF实体中配置的主组标识。
其中，结合表二可知，第三AMF实体中配置的主组标识包括标识7、标识8和标识9。该主组标识用于指示对应的终端组中的终端由第三移动管理实体提供服务。
可选的，接入设备接收到第三AMF实体中配置的主组标识之后，可以保存第三AMF实体的信息和第三AMF实体中配置的主组标识的对应关系。这样，接入设备后续可以根据该对应关系选择相应的AMF实体，本申请实施例对此不作具体限定。
S401d、第四AMF实体向接入设备发送第四AMF实体中配置的主组标识，以使得接入设备接收来自第四AMF实体的第四AMF实体中配置的主组标识。
其中，结合表二可知，第四AMF实体中配置的主组标识包括标识10、标识11和标识12。该主组标识用于指示对应的终端组中的终端由第四移动管理实体提供服务。
可选的，接入设备接收到第四AMF实体中配置的主组标识之后，可以保存第四AMF实体的信息和第四AMF实体中配置的主组标识的对应关系。这样，接入设备后续可以根据该对应关系选择相应的AMF实体，本申请实施例对此不作具体限定。
可选的，在步骤S401a至S401d中，如上所述，若主组标识的长度不固定时，各个AMF实体还需要将主组标识的长度通知给接入设备。其中，该主组标识的长度可以用位数表示，也可以用掩码表示，本申请实施例对此不作具体限定。
可选的，本申请实施例中，第一AMF实体还可以向SMF实体发送第一AMF实体中配置的主组标识；第二AMF实体还可以向SMF实体发送第二AMF实体中配置的主组标识；第三AMF实体还可以向SMF实体发送第三AMF实体中配置的主组标识；第四AMF实体还可以向SMF实体发送第四AMF实体中配置的主组标识。这样，SMF实体可以保存各个AMF实体的信息和相应的AMF实体中配置的主组标识的对应关系，进而SMF实体后续可以根据该对应关系选择相应的AMF实体。当然，也可以在分组数据单元(packet data unit，PDU)会话建立时将终端的组标识和为其服务的AMF实体的信息发送给SMF实体，本申请实施例对此不作具体限定。
S402、终端注册到网络。
具体的，当终端初次接入到该AMF实体组时，该终端的全球唯一临时标识(global unique  temporary identity，GUTI)中不包括终端的组标识。此时，接入设备为终端选择一个AMF实体。本申请实施例以注册到第一AMF实体为例进行说明，则当第一AMF实体接收到终端的注册请求时，第一AMF实体会从第一AMF实体中配置的主组标识中随机选择一个主组标识作为该终端的组标识。
可选的，假设第一AMF实体选择了标识1作为终端的组标识，则继续执行步骤S403a；
或者，假设第一AMF实体选择了标识2作为终端的组标识，则继续执行步骤S403b；
或者，假设第一AMF实体选择了标识3作为终端的组标识，则继续执行步骤S403c。
S403a、第一AMF实体在终端完成注册后或者在其它时机，比如定时器到期时，向第二AMF实体发送该终端的上下文，以使得第二AMF实体接收来自第一AMF实体的该终端的上下文。
其中，结合表二可知，第二AMF实体中配置的备份组标识包括标识1。也就是说，当为组标识为标识1的终端提供服务的第一AMF实体发生异常时，第二AMF实体可以接管这些终端，为这些组标识为标识1的终端提供服务，因此第一AMF实体需要将组标识为标识1的终端的上下文同步至第二AMF实体。
S403b、第一AMF实体在终端完成注册后或者在其它时机，比如定时器到期时，向第三AMF实体发送该终端的上下文，以使得第三AMF实体接收来自第一AMF实体的该终端的上下文。
其中，结合表二可知，第三AMF实体中配置的备份组标识包括标识2。也就是说，当为组标识为标识2的终端提供服务的第一AMF实体发生异常时，第三AMF实体可以接管这些终端，为这些组标识为标识2的终端提供服务，因此第一AMF实体需要将组标识为标识2的终端的上下文同步至第三AMF实体。
S403c、第一AMF实体在终端完成注册后或者在其它时机，比如定时器到期时，向第四AMF实体发送该终端的上下文，以使得第四AMF实体接收来自第一AMF实体的该终端的上下文。
其中，结合表二可知，第四AMF实体中配置的备份组标识包括标识3。也就是说，当为组标识为标识3的终端提供服务的第一AMF实体发生异常时，第四AMF实体可以接管这些终端，为这些组标识为标识4的终端提供服务，因此第一AMF实体需要将组标识为标识3的终端的上下文同步至第四AMF实体。
S404、第一AMF实体发生异常。
在第一AMF实体发生异常的情况下，接入设备执行步骤S405a和S406a；第二AMF实体执行步骤S405b-S407b；第三AMF实体执行步骤S405c-S407c；第四AMF实体执行步骤S405d-S407d；SMF实体执行步骤S405e和S406e，详见以下步骤。
S405a、接入设备检测到第一AMF实体发生异常。
S406a、接入设备将第一AMF实体标识为不可用，后续有新的终端接入时不再选择该第一AMF实体。
S405b、第二AMF实体检测到第一AMF实体发生异常。
S406b、第二AMF实体向SMF实体发送指示消息1，以使得SMF实体接收来自第二AMF实体的指示消息1。该指示消息1用于指示标识1对应的终端组中的终端由第二AMF实体提供服务。
可选的，SMF实体接收到指示消息1之后，可以保存第二AMF实体的信息和标识1的 对应关系。另外，针对组标识为标识1的在该SMF实体建立了PDU会话的终端，SMF实体可以释放该SMF实体到第一AMF实体的N11接口。这样，SMF实体后续有下行消息需要发送时，可以根据该对应关系选择第二AMF实体，建立该SMF实体到第二AMF实体的N11接口，通过该第二AMF实体发送下行消息，本申请实施例对此不作具体限定。
S407b、第二AMF实体向接入设备发送指示消息1，以使得接入设备接收来自第二AMF实体的指示消息1。该指示消息1用于指示标识1对应的终端组中的终端由第二AMF实体提供服务。
可选的，接入设备接收到指示消息1之后，可以保存第二AMF实体的信息和标识1的对应关系。另外，针对组标识为标识1的处于连接态的终端，接入设备可以释放该接入设备到第一AMF实体的N2接口。这样，接入设备后续有上行消息需要发送时，可以根据该对应关系选择第二AMF实体，建立该接入设备到第二AMF实体的N2接口，通过该第二AMF实体发送上行消息，本申请实施例对此不作具体限定。
S405c、第三AMF实体检测到第一AMF实体发生异常。
S406c、第三AMF实体向SMF实体发送指示消息2，以使得SMF实体接收来自第三AMF实体的指示消息2。该指示消息2用于指示标识2对应的终端组中的终端由第三AMF实体提供服务。
可选的，SMF实体接收到指示消息2之后，可以保存第三AMF实体的信息和标识2的对应关系。另外，针对组标识为标识2的在该SMF实体建立了PDU会话的终端，SMF实体可以释放该SMF实体到第一AMF实体的N11接口。这样，SMF实体后续有下行消息需要发送时，可以根据该对应关系选择第三AMF实体，建立该SMF实体到第三AMF实体的N11接口，通过该第三AMF实体发送下行消息，本申请实施例对此不作具体限定。
S407c、第三AMF实体向接入设备发送指示消息2，以使得接入设备接收来自第三AMF实体的指示消息2。该指示消息2用于指示标识2对应的终端组中的终端由第三AMF实体提供服务。
可选的，接入设备接收到指示消息2之后，可以保存第三AMF实体的信息和标识2的对应关系。另外，针对组标识为标识2的处于连接态的终端，接入设备可以释放该接入设备到第一AMF实体的N2接口。这样，接入设备后续有上行消息需要发送时，可以根据该对应关系选择第三AMF实体，建立该接入设备到第三AMF实体的N2接口，通过该第三AMF实体发送上行消息，本申请实施例对此不作具体限定。
S405d、第四AMF实体检测到第一AMF实体发生异常。
S406d、第四AMF实体向SMF实体发送指示消息3，以使得SMF实体接收来自第四AMF实体的指示消息3。该指示消息3用于指示标识3对应的终端组中的终端由第四AMF实体提供服务。
可选的，SMF实体接收到指示消息3之后，可以保存第四AMF实体的信息和标识3的对应关系。另外，针对组标识为标识3的在该SMF实体建立了PDU会话的终端，SMF实体可以释放该SMF实体到第一AMF实体的N11接口。这样，SMF实体后续有下行消息需要发送时，可以根据该对应关系选择第四AMF实体，建立该SMF实体到第四AMF实体的N11接口，通过该第四AMF实体发送下行消息，本申请实施例对此不作具体限定。
S406d、第四AMF实体向接入设备发送指示消息3，以使得接入设备接收来自第四AMF实体的指示消息3。该指示消息3用于指示标识3对应的终端组中的终端由第四AMF实体提 供服务。
可选的，接入设备接收到指示消息3之后，可以保存第四AMF实体的信息和标识3的对应关系。另外，针对组标识为标识3的处于连接态的终端，接入设备可以释放该接入设备到第一AMF实体的N2接口。这样，接入设备后续有上行消息需要发送时，可以根据该对应关系选择第四AMF实体，建立该接入设备到第四AMF实体的N2接口，通过该第四AMF实体发送上行消息，本申请实施例对此不作具体限定。
S405e、SMF实体检测到第一AMF实体发生异常。
S406e、SMF实体将第一AMF实体标识为不可用，后续不再向第一AMF实体发送下行消息。
需要说明的是，本申请实施例中仅是示例性的以各个AMF实体与核心网侧的SMF实体交互为例进行说明。当然，本申请实施例中的SMF实体也可以替换为其他核心网设备，比如，各个AMF实体与UDM实体或者AUSF实体进行上述交互，本申请实施例对此不作具体限定。
下面分别从接入设备获取终端相关的上行消息和SMF实体获取终端相关的下行消息两方面分别进行说明，分别包括如下步骤S408-S409，以及步骤S410-S411。
S408、接入设备获取终端相关的上行消息。
可选的，本申请实施例中，终端相关的上行消息可以是接入设备需要发起与终端相关的N2消息时，发送给目标AMF实体的上行消息，如上行N2消息；也可以是终端发送给目标AMF实体的上行消息，如上行非接入层(non access stratum，NAS)消息，本申请实施例对此不作具体限定。
其中，接入设备可以从终端发送给接入设备的终端相关的上行消息中获取该终端的组标识；或者，接入设备可以从该终端的上下文中确定该终端的组标识，本申请实施例对此不作具体限定。
可选的，若终端相关的上行消息中包括系统架构演进(system architecture evolution，SAE)临时移动用户标识(SAE-temporary mobile subscriber identity，S-TMSI)，由于S-TMSI由AMF pointer和终端的临时标识组成，若终端组的组标识是AMF pointer+终端临时标识的高N位，则接入设备可以根据组标识的长度从S-TMSI的高位开始读取相应长度的位数，得到相应的组标识，本申请实施例对此不作具体限定。
可选的，假设终端的组标识为标识1，则接入设备继续执行步骤S409a；
或者，假设终端的组标识为标识2，则接入设备继续执行步骤S409b；
或者，假设终端的组标识为标识3，则接入设备继续执行步骤S409c。
S409a、接入设备根据组标识1，向第二AMF实体发送终端相关的上行消息，以使得第二AMF实体接收来自接入设备的终端相关的上行消息。
可选的，接入设备可以根据步骤S407b中接收到的指示消息1以及步骤S408中获取到的组标识1，确定该组标识1对应的AMF实体为第二AMF实体，进而向第二AMF实体发送终端相关的上行消息。
S409b、接入设备根据组标识2，向第三AMF实体发送终端相关的上行消息，以使得第三AMF实体接收来自接入设备的终端相关的上行消息。
可选的，接入设备可以根据步骤S407c中接收到的指示消息2以及步骤S408中获取到的组标识2，确定该组标识2对应的AMF实体为第三AMF实体，进而向第三AMF实体发送终端相关的上行消息。
S409c、接入设备根据组标识3，向第四AMF实体发送终端相关的上行消息，以使得第四AMF实体接收来自接入设备的终端相关的上行消息。
可选的，接入设备可以根据步骤S407d中接收到的指示消息3以及步骤S408中获取到的组标识3，确定该组标识3对应的AMF实体为第四AMF实体，进而向第四AMF实体发送终端相关的上行消息。
S410、SMF实体获取终端相关的下行消息。
可选的，本申请实施例中，终端相关的下行消息可以是SMF实体发送给接入设备的下行消息，如下行N2消息；也可以是SMF实体发送给终端的下行消息，如下行NAS消息；还可以是SMF实体发送给目标AMF实体的下行消息，本申请实施例对此不作具体限定。
可选的，SMF实体可以从其他设备发送给SMF实体的终端相关的下行消息中获取该终端的组标识；或者，SMF实体可以从该终端的上下文中确定该终端的组标识，本申请实施例对此不作具体限定。
可选的，若终端相关的下行消息中包括S-TMSI，由于S-TMSI由AMF pointer和终端的临时标识组成，若终端组的组标识是AMF pointer+终端临时标识的高N位，则SMF实体可以根据组标识的长度从S-TMSI的高位开始读取相应位数的值，得到相应的组标识，本申请实施例对此不作具体限定。
可选的，假设终端的组标识为标识1，则SMF实体继续执行步骤S411a；
或者，假设终端的组标识为标识2，则SMF实体继续执行步骤S411b；
或者，假设终端的组标识为标识3，则SMF实体继续执行步骤S411c。
S411a、SMF实体根据组标识1，向第二AMF实体发送终端相关的下行消息，以使得第二AMF实体接收来自SMF实体的终端相关的下行消息。
可选的，接SMF实体可以根据步骤S406b中接收到的指示消息1以及步骤S410中获取到的组标识1，确定该组标识1对应的AMF实体为第二AMF实体，进而向第二AMF实体发送终端相关的下行消息。
S411b、SMF实体根据组标识2，向第三AMF实体发送终端相关的下行消息，以使得第三AMF实体接收来自SMF实体的终端相关的下行消息。
可选的，SMF实体可以根据步骤S406c中接收到的指示消息2以及步骤S410中获取到的组标识2，确定该组标识2对应的AMF实体为第三AMF实体，进而向第三AMF实体发送终端相关的下行消息。
S411c、SMF实体根据组标识3，向第四AMF实体发送终端相关的下行消息，以使得第四AMF实体接收来自SMF实体的终端相关的下行消息。
可选的，SMF实体可以根据步骤S406d中接收到的指示消息3以及步骤S410中获取到的组标识3，确定该组标识3对应的AMF实体为第四AMF实体，进而向第四AMF实体发送终端相关的下行消息。
基于本申请实施例提供的通信方法，一方面，由于第一AMF实体可以将服务的终端的上下文同步至配置该终端的组标识的其他AMF实体，在该第一AMF实体发生异常的情况下，可以根据该组标识，向配置该组标识的其他AMF实体发送该终端相关的消息，因此可以在第一移动管理实体发生异常的情况下，避免由于正在服务的终端的上下文丢失而触发终端的重新注册流程，即可以保持正在服务的终端的当前流程不中断。另一方面，由于第一AMF实体可以将终端进行分组，不同终端组内的终端的上下文可以分别备份到多个不同的AMF 实体，也就是说可以实现一对多备份。这样，在该第一AMF实体发生异常的情况下，由多个不同的AMF实体分别接管第一AMF实体的一个或多个终端组，因此减少了由于第一AMF实体异常对单个AMF实体的冲击，相对于传统的1+1备份节省资源，同时弥补了传统的MME池中的上下文丢失问题。
其中，上述步骤S401至S411中接入设备、SMF实体以及各个AMF实体的动作均可以由图3所示的网络设备300中的处理器301调用存储器303中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
可选的，以图1所示的通信系统应用于图2所示的5G网络，AMF实体组的配置情况如表二所示为例，假设AMF实体1为第一AMF实体，AMF实体2为第二AMF实体，AMF实体3为第三AMF实体，AMF实体4为第四AMF实体，则本申请实施例提供的通信方法还可以如图5所示，包括如下步骤：
S501a-S501d、与S401a-S401d类似，区别仅在于图4所示的实施例中的主组标识用于指示对应的终端组中的终端由发送该主组标识的AMF实体提供服务；而图5所示的实施例中的主组标识用于指示在发送该主组标识的AMF实体未发生异常的情况下，对应的终端组中的终端由第一AMF实体提供服务，具体可参考图4所示的实施例，在此不再赘述。
S502a、第一AMF实体向接入设备发送第一AMF实体中配置的备份组标识，以使得接入设备接收来自第一AMF实体的第一AMF实体中配置的备份组标识。
其中，结合表二可知，第一AMF实体中配置的备份组标识包括标识4、标识7和标识10。该备份组标识用于指示在将该备份组标识配置为主组标识的AMF实体发生异常的情况下，对应的终端组中的终端由第一AMF实体提供服务。比如，在将标识4配置为主组标识的第二AMF实体发生异常的情况下，终端组的组标识为标识4的终端由第一AMF实体提供服务。
可选的，接入设备接收到第一AMF实体中配置的备份组标识之后，可以保存第一AMF实体的信息和第一AMF实体中配置的备份组标识的对应关系。这样，接入设备后续可以根据该对应关系选择相应的AMF实体，本申请实施例对此不作具体限定。
S502b、第二AMF实体向接入设备发送第二AMF实体中配置的备份组标识，以使得接入设备接收来自第二AMF实体的第二AMF实体中配置的备份组标识。
其中，结合表二可知，第二AMF实体中配置的备份组标识包括标识1、标识8和标识11。该备份组标识用于指示在将该备份组标识配置为主组标识的AMF实体发生异常的情况下，对应的终端组中的终端由第二AMF实体提供服务。比如，在将标识1配置为主组标识的第一AMF实体发生异常的情况下，终端组的组标识为标识1的终端由第二AMF实体提供服务。
可选的，接入设备接收到第二AMF实体中配置的备份组标识之后，可以保存第二AMF实体的信息和第二AMF实体中配置的备份组标识的对应关系。这样，接入设备后续可以根据该对应关系选择相应的AMF实体，本申请实施例对此不作具体限定。
S502c、第三AMF实体向接入设备发送第三AMF实体中配置的备份组标识，以使得接入设备接收来自第三AMF实体的第三AMF实体中配置的备份组标识。
其中，结合表二可知，第三AMF实体中配置的备份组标识包括标识2、标识5和标识12。该备份组标识用于指示在将该备份组标识配置为主组标识的AMF实体发生异常的情况下，对应的终端组中的终端由第三AMF实体提供服务。比如，在将标识2配置为主组标识的第一AMF实体发生异常的情况下，终端组的组标识为标识2的终端由第三AMF实体提供 服务。
可选的，接入设备接收到第三AMF实体中配置的备份组标识之后，可以保存第三AMF实体的信息和第三AMF实体中配置的备份组标识的对应关系。这样，接入设备后续可以根据该对应关系选择相应的AMF实体，本申请实施例对此不作具体限定。
S502d、第四AMF实体向接入设备发送第四AMF实体中配置的备份组标识，以使得接入设备接收来自第四AMF实体的第四AMF实体中配置的备份组标识。
其中，结合表二可知，第四AMF实体中配置的备份组标识包括标识3、标识6和标识9。该备份组标识用于指示在将该备份组标识配置为主组标识的AMF实体发生异常的情况下，对应的终端组中的终端由第四AMF实体提供服务。比如，在将标识3配置为主组标识的第一AMF实体发生异常的情况下，终端组的组标识为标识3的终端由第四AMF实体提供服务。
可选的，接入设备接收到第四AMF实体中配置的备份组标识之后，可以保存第四AMF实体的信息和第四AMF实体中配置的备份组标识的对应关系。这样，接入设备后续可以根据该对应关系选择相应的AMF实体，本申请实施例对此不作具体限定。
可选的，在步骤S501a至S502d中，如上所述，若组标识的长度不固定时，各个AMF实体还需要将主组标识的长度和备份组标识的长度通知给接入设备。其中，该主组标识和备份组标识的长度可以用位数表示，也可以用掩码表示，本申请实施例对此不作具体限定。
可选的，本申请实施例中，步骤S501a中的主组标识和步骤S502a中的备份组标识可以是携带在一条消息中一起发送给接入设备的，也可以是通过两条消息分别发送给接入设备的，本申请实施例对此不作具体限定。类似的，步骤S501b中的主组标识和步骤S502b中的备份组标识可以是携带在一条消息中一起发送给接入设备的，也可以是通过两条消息分别发送给接入设备的；步骤S501c中的主组标识和步骤S502c中的备份组标识可以是携带在一条消息中一起发送给接入设备的，也可以是通过两条消息分别发送给接入设备的；步骤S501d中的主组标识和步骤S502d中的备份组标识可以是携带在一条消息中一起发送给接入设备的，也可以是通过两条消息分别发送给接入设备的，本申请实施例对此不作具体限定。
可选的，本申请实施例中，第一AMF实体还可以向SMF实体发送第一AMF实体中配置的主组标识和备份组标识；第二AMF实体还可以向SMF实体发送第二AMF实体中配置的主组标识和备份组标识；第三AMF实体还可以向SMF实体发送第三AMF实体中配置的主组标识和备份组标识；第四AMF实体还可以向SMF实体发送第四AMF实体中配置的主组标识和备份组标识。这样，SMF实体可以保存各个AMF实体的信息和相应的AMF实体中配置的主组标识和备份组标识的对应关系，进而SMF实体后续可以根据该对应关系选择相应的AMF实体。当然，也可以在PDU会话建立时将终端的组标识和为其服务的AMF实体的信息发送给SMF实体，本申请实施例对此不作具体限定。
S503、同S402，具体可参考图4所示的实施例，在此不再赘述。
S504a-S504c、同S403a-S403c，具体可参考图4所示的实施例，在此不再赘述。
S505、第一AMF实体发生异常。
在第一AMF实体发生异常的情况下，接入设备执行步骤S506a和S507a；第二AMF实体执行步骤S506b-S507b；第三AMF实体执行步骤S506c-S507c；第四AMF实体执行步骤S506d-S507d；SMF实体执行步骤S506e和S507e，详见以下步骤。
S506a-S507a、同S405a-S406a，具体可参考图4所示的实施例，在此不再赘述。
可选的，接入设备在检测到第一AMF实体发生异常的情况下，可以根据502a-502d接收 到的备份组标识和AMF实体的对应关系，将第一AMF实体的主组标识：标识1、标识2和标识3对应的终端的服务AMF实体分别设置为第二AMF实体、第三AMF实体、第四AMF实体，本申请实施例对此不作具体限定。
S506b-S507b、同S405b-S406b，具体可参考图4所示的实施例，在此不再赘述。
S506c-S507c、同S405c-S406c，具体可参考图4所示的实施例，在此不再赘述。
S506d-S507d、同S405d-S406d，具体可参考图4所示的实施例，在此不再赘述。
S506e-S507e、同S405e-S406e，具体可参考图4所示的实施例，在此不再赘述。
需要说明的是，若在步骤S503之前，各个AMF实体分别向SMF实体发送了相应AMF实体中配置的主组标识和备份组标识，则本申请实施例可以不用执行步骤S506b-S507b、步骤S506c-S507c以及步骤S506d-S507d，在此进行统一说明，以下不再赘述。
可选的，若在步骤S503之前，各个AMF实体分别向SMF实体发送了相应AMF实体中配置的主组标识和备份组标识，则SMF实体在检测到第一AMF实体发生异常的情况下，可以根据接收到的主组标识与AMF实体的对应关系、以及备份组标识和AMF实体的对应关系，将第一AMF实体的主组标识：标识1、标识2和标识3对应的终端的服务AMF实体分别设置为第二AMF实体、第三AMF实体、第四AMF实体，本申请实施例对此不作具体限定。
下面分别从接入设备获取终端相关的上行消息和SMF实体获取终端相关的下行消息两方面分别进行说明，分别包括如下步骤S508-S509，以及步骤S510-S511。
S508、接入设备获取终端相关的上行消息。
其中，步骤S508的相关描述可参考步骤S408，在此不再赘述。
可选的，假设终端的组标识为标识1，则接入设备继续执行步骤S509a；
或者，假设终端的组标识为标识2，则接入设备继续执行步骤S509b；
或者，假设终端的组标识为标识3，则接入设备继续执行步骤S509c。
S509a、接入设备根据组标识1，向第二AMF实体发送终端相关的上行消息，以使得第二AMF实体接收来自接入设备的终端相关的上行消息。
可选的，接入设备可以根据步骤S502b中接收到的备份组标识以及步骤S508a中获取到的组标识1，确定该组标识1对应的AMF实体为第二AMF实体，进而向第二AMF实体发送终端相关的上行消息。
S509b、接入设备根据组标识2，向第三AMF实体发送终端相关的上行消息，以使得第三AMF实体接收来自接入设备的终端相关的上行消息。
可选的，接入设备可以根据步骤S502c中接收到的备份组标识以及步骤S508b中获取到的组标识2，确定该组标识2对应的AMF实体为第三AMF实体，进而向第三AMF实体发送终端相关的上行消息。
S509c、接入设备根据组标识3，向第四AMF实体发送终端相关的上行消息，以使得第四AMF实体接收来自接入设备的终端相关的上行消息。
可选的，接入设备可以根据步骤S502d中接收到的备份组标识以及步骤S508c中获取到的组标识3，确定该组标识3对应的AMF实体为第四AMF实体，进而向第四AMF实体发送终端相关的上行消息。
S510、同S410，具体可参考图4所示的实施例，在此不再赘述。
S511a-S511c、同S411a-S411c，具体可参考图4所示的实施例，在此不再赘述。
与图4所示的实施例的区别在于，图4所示的实施例中，在第一AMF实体初始配置时， 第一AMF实体仅将配置的主组标识发送给接入设备。当其他AMF实体检测到第一AMF实体发生异常时，其他AMF实体才通知接入设备相应的主组标识对应的终端由自己接管；而图5所示的实施例中，在AMF实体初始配置时，AMF实体可以将配置的主组标识和备份组标识均发送给接入设备。这样，当为组标识为该AMF实体对应的备份组标识的终端提供服务的第一AMF实体发生异常时，该AMF实体可以接管这些终端，为这些终端提供服务。另外，第二AMF实体、第三AMF实体和第四AMF实体的动作也与第一AMF实体类似，在此不再赘述。
基于本申请实施例提供的通信方法，一方面，由于第一AMF实体可以将服务的终端的上下文同步至配置该终端的组标识的其他AMF实体，在该第一AMF实体发生异常的情况下，可以根据该组标识，向配置该组标识的其他AMF实体发送该终端相关的消息，因此可以在第一移动管理实体发生异常的情况下，避免由于正在服务的终端的上下文丢失而触发终端的重新注册流程，即可以保持正在服务的终端的当前流程不中断。另一方面，由于第一AMF实体可以将终端进行分组，不同终端组内的终端的上下文可以分别备份到多个不同的AMF实体，也就是说可以实现一对多备份。这样，在该第一AMF实体发生异常的情况下，由多个不同的AMF实体分别接管第一AMF实体的一个或多个终端组，因此减少了由于第一AMF实体异常对单个AMF实体的冲击，相对于传统的1+1备份节省资源，同时弥补了传统的MME池中的上下文丢失问题。
其中，上述步骤S501至S511中接入设备、SMF实体以及各个AMF实体的动作均可以由图3所示的网络设备300中的处理器301调用存储器303中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
可选的，以图1所示的通信系统应用于图2所示的5G网络，AMF实体组的配置情况如表五所示为例，假设AMF实体1为第一AMF实体，AMF实体2为第二AMF实体，AMF实体3为第三AMF实体，AMF实体4为第四AMF实体，则本申请实施例提供的通信方法还可以如图6所示，包括如下步骤：
S601a-S601d、与S501a-S501d类似，区别仅在于，图6所示的实施例中用组标识替换图5所示的实施例中的主组标识，具体可参考图5所示的实施例，在此不再赘述。
S602a、第一AMF实体向接入设备发送指示消息1，以使得接入设备接收来自第一AMF实体的指示消息1。该指示消息1用于指示在第一AMF实体发生异常的情况下，标识1对应的终端组中的终端由第二AMF实体提供服务，标识2对应的终端组中的终端由第三AMF实体提供服务，标识3对应的终端组中的终端由第四AMF实体提供服务。
可选的，接入设备接收到指示消息1之后，可以保存组标识1与第一AMF实体和第二AMF实体的对应关系、组标识2与第一AMF实体和第三AMF实体的对应关系，组标识3与第一AMF实体和第四AMF实体的对应关系。其中，第一AMF实体作为组标识1、组标识2和组标识3的主AMF实体，第二AMF实体作为组标识1的备份AMF实体、第三AMF实体作为组标识2的备份AMF实体和第四AMF实体作为组标识3的备份AMF实体。这样，接入设备后续可以根据这些对应关系选择相应的AMF实体，本申请实施例对此不作具体限定。
S602b、第二AMF实体向接入设备发送指示消息2，以使得接入设备接收来自第二AMF实体的指示消息2。该指示消息2用于指示在第二AMF实体发生异常的情况下，标识4对应的终端组中的终端由第一AMF实体提供服务，标识5对应的终端组中的终端由第三AMF实 体提供服务，标识6对应的终端组中的终端由第四AMF实体提供服务。
可选的，接入设备接收到指示消息2之后，可以保存组标识4与第二AMF实体和第一AMF实体的对应关系、组标识5与第二AMF实体和第三AMF实体的对应关系，组标识6与第二AMF实体和第四AMF实体的对应关系。其中，第二AMF实体作为组标识4、组标识5和组标识6的主AMF实体，第一AMF实体作为组标识4的备份AMF实体、第三AMF实体作为组标识5的备份AMF实体和第四AMF实体作为组标识6的备份AMF实体。这样，接入设备后续可以根据这些对应关系选择相应的AMF实体，本申请实施例对此不作具体限定。
S602c、第三AMF实体向接入设备发送指示消息3，以使得接入设备接收来自第三AMF实体的指示消息3。该指示消息3用于指示在第三AMF实体发生异常的情况下，标识7对应的终端组中的终端由第一AMF实体提供服务，标识8对应的终端组中的终端由第二AMF实体提供服务，标识9对应的终端组中的终端由第四AMF实体提供服务。
可选的，接入设备接收到指示消息3之后，可以保存组标识7与第三AMF实体和第一AMF实体的对应关系、组标识8与第三AMF实体和第二AMF实体的对应关系，组标识9与第三AMF实体和第四AMF实体的对应关系。其中，第三AMF实体作为组标识7、组标识8和组标识9的主AMF实体，第二AMF实体作为组标识8的备份AMF实体、第一AMF实体作为组标识7的备份AMF实体和第四AMF实体作为组标识9的备份AMF实体。这样，接入设备后续可以根据这些对应关系选择相应的AMF实体，本申请实施例对此不作具体限定。
S602d、第四AMF实体向接入设备发送指示消息4，以使得接入设备接收来自第四AMF实体的指示消息4。该指示消息4用于指示在第四AMF实体发生异常的情况下，标识10对应的终端组中的终端由第一AMF实体提供服务，标识11对应的终端组中的终端由第二AMF实体提供服务，标识12对应的终端组中的终端由第三AMF实体提供服务。
可选的，接入设备接收到指示消息4之后，可以保存组标识10与第四AMF实体和第一AMF实体的对应关系、组标识11与第四AMF实体和第二AMF实体的对应关系，组标识12与第四AMF实体和第三AMF实体的对应关系。其中，第四AMF实体作为组标识10、组标识11和组标识12的主AMF实体，第二AMF实体作为组标识11的备份AMF实体、第三AMF实体作为组标识12的备份AMF实体和第一AMF实体作为组标识10的备份AMF实体。这样，接入设备后续可以根据这些对应关系选择相应的AMF实体，本申请实施例对此不作具体限定。
可选的，本申请实施例中，步骤S601a中的组标识和步骤S602a中的指示消息1可以是携带在一条消息中一起发送给接入设备的，也可以是通过两条消息分别发送给接入设备的，本申请实施例对此不作具体限定。类似的，步骤S601b中的组标识和步骤S602b中的指示消息2可以是携带在一条消息中一起发送给接入设备的，也可以是通过两条消息分别发送给接入设备的；步骤S601c中的组标识和步骤S602c中的指示消息3可以是携带在一条消息中一起发送给接入设备的，也可以是通过两条消息分别发送给接入设备的；步骤S601d中的组标识和步骤S602d中的指示消息4可以是携带在一条消息中一起发送给接入设备的，也可以是通过两条消息分别发送给接入设备的，本申请实施例对此不作具体限定。
可选的，本申请实施例中，第一AMF实体还可以向SMF实体发送第一AMF实体中配置的组标识和指示消息1；第二AMF实体还可以向SMF实体发送第二AMF实体中配置的组 标识和指示消息2；第三AMF实体还可以向SMF实体发送第三AMF实体中配置的组标识和指示消息3；第四AMF实体还可以向SMF实体发送第四AMF实体中配置的组标识和指示消息4。这样，SMF实体可以保存各个组标识和主AMF实体以及备份AMF实体的对应关系，进而SMF实体后续可以根据该对应关系选择相应的AMF实体。当然，也可以在PDU会话建立时将终端的组标识和为其服务的AMF实体的信息发送给SMF实体，本申请实施例对此不作具体限定。
S603a-S603d、与S602a-S602d类似，区别仅在于，S603a-S603d中用SMF实体替换S602a-S602d中的接入设备，具体可参考S602a-S602d，在此不再赘述。
S604、同S503，具体可参考图5所示的实施例，在此不再赘述。
S605a-S605c、同S504a-S504c，具体可参考图5所示的实施例，在此不再赘述。
S606、第一AMF实体发生异常。
在第一AMF实体发生异常的情况下，接入设备执行步骤S607a和S608a；SMF实体执行步骤S607e和S608e，详见以下步骤。
S607a-S608a、同S506a-S507a，具体可参考图5所示的实施例，在此不再赘述。
可选的，接入设备在检测到第一AMF实体发生异常的情况下，可以根据602a-602d接收到的指示消息，将第一AMF实体的组标识：标识1、标识2和标识3对应的终端的服务AMF实体分别设置为第二AMF实体、第三AMF实体、第四AMF实体，本申请实施例对此不作具体限定。
S607e-S608e、同S506e-S507e，具体可参考图5所示的实施例，在此不再赘述。
可选的，SMF实体在检测到第一AMF实体发生异常的情况下，可以根据603a-603d接收到的指示消息，将第一AMF实体的组标识：标识1、标识2和标识3对应的终端的服务AMF实体分别设置为第二AMF实体、第三AMF实体、第四AMF实体，本申请实施例对此不作具体限定。
S609、同S508，具体可参考图5所示的实施例，在此不再赘述。
S610a-S610c、与S509a-S509c类似，区别仅在于，S509a-S509c中接入设备根据备份组标识确定组标识对应的AMF实体，本申请实施例中根据指示消息确定组标识对应的AMF实体，具体可参考图5所示的实施例，在此不再赘述。
S611、同S510，具体可参考图5所示的实施例，在此不再赘述。
S612a-S612c、同S511a-S511c，具体可参考图5所示的实施例，在此不再赘述。
与图5所示的实施例的区别在于，图5所示的实施例中，在AMF实体中同时配置主组标识和备份组标识。在AMF实体发生故障时，接入设备可以根据备份组标识，确定接管组标识为该AMF实体管理的主组标识的终端的AMF实体；图6所示的实施例中，仅在主AMF实体中配置该主AMF实体未发生异常时服务的终端的组标识，以及当该主AMF实体发生异常时，分别接管组标识为这些组标识的终端的备份AMF实体的信息。在AMF实体发生故障时，接入设备可以根据备份AMF实体的信息，确定接管组标识为这些组标识的终端的备份AMF实体。
基于本申请实施例提供的通信方法，一方面，由于第一AMF实体可以将服务的终端的上下文同步至配置该终端的组标识的其他AMF实体，在该第一AMF实体发生异常的情况下，可以根据该组标识，向配置该组标识的其他AMF实体发送该终端相关的消息，因此可以在第一移动管理实体发生异常的情况下，避免由于正在服务的终端的上下文丢失而触发终端的 重新注册流程，即可以保持正在服务的终端的当前流程不中断。另一方面，由于第一AMF实体可以将终端进行分组，不同终端组内的终端的上下文可以分别备份到多个不同的AMF实体，也就是说可以实现一对多备份。这样，在该第一AMF实体发生异常的情况下，由多个不同的AMF实体分别接管第一AMF实体的一个或多个终端组，因此减少了由于第一AMF实体异常对单个AMF实体的冲击，相对于传统的1+1备份节省资源，同时弥补了传统的MME池中的上下文丢失问题。
其中，上述步骤S601至S612中接入设备、SMF实体以及各个AMF实体的动作均可以由图3所示的网络设备300中的处理器301调用存储器303中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
可选的，在实际部署时，还可以将图4所示的实施例和图5所示的实施例相结合，或者将图4所示的实施例和图6所示的实施例相结合，本申请实施例对此不作具体限定。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，上述通信设备和第二移动管理实体为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对通信设备和第二移动管理实体进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
比如，在采用对应各个功能划分各个功能模块的情况下，图7示出了上述实施例中所涉及的通信设备70的一种可能的结构示意图。该通信设备70包括获取模块701和发送模块702。获取模块701，用于获取第一移动管理实体服务的第一终端所在终端组的第一组标识。发送模块702，用于在第一移动管理实体发生异常的情况下，根据第一组标识，向第二移动管理实体发送第一终端相关的消息，其中，第二移动管理实体为存在第一终端的上下文的移动管理实体。
可选的，第一组标识为配置在第一移动管理实体中的主组标识、配置在第二移动管理实体中的备份组标识。
在一种可能的实现方式中，如图7所示，该通信设70备还包括：接收模块703。接收模块703，用于接收第一指示消息，该第一指示消息用于指示第一组标识对应的终端组中的终端由第二移动管理实体提供服务。
可选的，接收模块703具体用于：接收来自第二移动管理实体的第一指示消息，其中，该第一指示消息为第二移动管理实体确定第一移动管理实体发生异常的情况下发送给通信设备的。
在一种可能的实现方式中，接收模块703，用于接收第一指示消息，该第一指示消息用于指示在第一移动管理实体发生异常的情况下，第一组标识对应的终端组中的终端由第二移动管理实体提供服务。
可选的，接收模块703具体用于：在第一移动管理实体发生异常之前，接收第一指示消息。发送模块702具体用于：确定第一移动管理实体发生异常；根据第一组标识，向第二移动管理实体发送第一终端相关的消息。
可选的，获取模块701具体用于：接收第一终端相关的消息，其中，第一终端相关的消息中携带第一终端所在终端组的第一组标识；或者，从第一终端的上下文中确定第一终端所在终端组的第一组标识。
可选的，获取模块701，还用于获取第一移动管理实体服务的第二终端所在终端组的第二组标识。发送模块702，还用于在第一移动管理实体发生异常的情况下，根据第二组标识，向第三移动管理实体发送第二终端相关的消息，其中，第三移动管理实体为存在第二终端的上下文的移动管理实体。
可选的，本申请实施例中的通信设备包括接入设备或者会话管理实体。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
以采用集成的方式划分各个功能模块的情况下，图8示出了上述实施例中所涉及的通信设备80的一种可能的结构示意图，该通信设备80包括：处理模块801和通信模块802。其中，该处理模块801可用于执行图7中获取模块701所能执行的操作，该通信模块802可用于执行图7中发送模块702所能执行的操作。可选的，该通信模块802还可用于执行图7中接收模块703所能执行的操作，具体可参考图7所示的实施例，本申请实施例在此不再赘述。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该通信设备以对应各个功能划分各个功能模块的形式来呈现，或者，该通信设备以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定应用集成电路(Application-Specific Integrated Circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到通信设备70或者通信设备80可以采用图3所示的形式。比如，图7中的获取模块701、发送模块702和接收模块703可以通过图3的处理器401和存储器403来实现。具体的，获取模块701、发送模块702和接收模块703可以通过由处理器301来调用存储器303中存储的应用程序代码来执行，本申请实施例对此不作任何限制。或者，比如，图8中的处理模块801和通信模块802可以通过图3的处理器301和存储器303来实现。具体的，处理模块801和通信模块802可以通过由处理器301来调用存储器303中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
由于本申请实施例提供的通信设备可用于执行上述通信方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
或者，比如，在采用对应各个功能划分各个功能模块的情况下，图9示出了上述实施例中所涉及的第二移动管理实体90的一种可能的结构示意图。该第二移动管理实体90包括：接收模块901、确定模块902和发送模块903。接收模块901，用于接收来自第一移动管理实体的第一移动管理实体服务的第一终端的上下文。确定模块902，用于确定第一移动管理实体发生异常。发送模块903，用于向通信设备发送第一指示消息，该第一指示消息用于指示第一组标识对应的终端组中的终端由第二移动管理实体提供服务，其中，第一组标识为第一终端所在终端组的组标识。
可选的，接收模块901，还用于接收来自通信设备的第一终端相关的消息。
可选的，接收模块901，还用于接收来自第三移动管理实体的第三移动管理实体服务的第二终端的上下文。确定模块902，还用于确定第三移动管理实体发生异常。发送模块903，还用于向通信设备发送第二指示消息，第二指示消息用于指示第二组标识对应的终端组中的终端由第二移动管理实体提供服务，其中，第二组标识为第二终端所在终端组的组标识。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
以采用集成的方式划分各个功能模块的情况下，图10示出了上述实施例中所涉及的第二移动管理实体100的一种可能的结构示意图，该第二移动管理实体100包括：处理模块1002和通信模块1001。其中，该处理模块1002可用于执行图9中确定模块902所能执行的操作，该通信模块1001可用于执行图9中接收模块901和发送模块903所能执行的操作，具体可参考图9所示的实施例，本申请实施例在此不再赘述。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该第二移动管理实体以对应各个功能划分各个功能模块的形式来呈现，或者，该第二移动管理实体以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定应用集成电路(Application-Specific Integrated Circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到第二移动管理实体90或者第二移动管理实体100可以采用图3所示的形式。比如，图9中的接收模块901、确定模块902和发送模块903可以通过图3的处理器301和存储器303来实现。具体的，接收模块901、确定模块902和发送模块903可以通过由处理器301来调用存储器303中存储的应用程序代码来执行，本申请实施例对此不作任何限制。或者，比如，图10中的处理模块1002和通信模块1001可以通过图3的处理器301和存储器303来实现。具体的，处理模块1002和通信模块1001可以通过由处理器301来调用存储器303中存储的应用程序代码来执行，本申请实施例对此不作任何限制。
由于本申请实施例提供的第二移动管理实体可用于执行上述通信方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
可选的，本申请实施例提供了一种芯片系统，该芯片系统包括处理器，用于支持通信设备实现上述方面中所涉及的功能，例如在第一移动管理实体发生异常的情况下，根据第一移动管理实体服务的第一终端所在终端组的第一组标识，向第二移动管理实体发送第一终端相关的消息。在一种可能的设计中，该芯片系统还包括存储器。该存储器，用于保存通信设备必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
可选的，本申请实施例提供了一种芯片系统，该芯片系统包括处理器，用于支持第二移动管理实体实现上述方面中所涉及的功能，例如接收来自第一移动管理实体的第一移动管理实体服务的第一终端的上下文。在一种可能的设计中，该芯片系统还包括存储器。该存储器，用于保存第二移动管理实体必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当 使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (31)

  1. 一种通信方法，其特征在于，所述方法包括：
    通信设备获取第一移动管理实体服务的第一终端所在终端组的第一组标识；
    在所述第一移动管理实体发生异常的情况下，所述通信设备根据所述第一组标识，向第二移动管理实体发送所述第一终端相关的消息，其中，所述第二移动管理实体为存在所述第一终端的上下文的移动管理实体。
  2. 根据权利要求1所述的方法，其特征在于，所述第一组标识为配置在所述第一移动管理实体中的主组标识、配置在所述第二移动管理实体中的备份组标识。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述通信设备接收第一指示消息，所述第一指示消息用于指示所述第一组标识对应的终端组中的终端由所述第二移动管理实体提供服务。
  4. 根据权利要求3所述的方法，其特征在于，所述通信设备接收第一指示消息，包括：
    所述通信设备接收来自所述第二移动管理实体的所述第一指示消息，其中，所述第一指示消息为所述第二移动管理实体确定所述第一移动管理实体发生异常的情况下发送给所述通信设备的。
  5. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述通信设备接收第一指示消息，所述第一指示消息用于指示在所述第一移动管理实体发生异常的情况下，所述第一组标识对应的终端组中的终端由所述第二移动管理实体提供服务。
  6. 根据权利要求5所述的方法，其特征在于，所述通信设备接收第一指示消息，包括：
    在所述第一移动管理实体发生异常之前，所述通信设备接收所述第一指示消息；
    在所述第一移动管理实体发生异常的情况下，所述通信设备根据所述第一组标识，向第二移动管理实体发送所述第一终端相关的消息，包括：
    所述通信设备确定所述第一移动管理实体发生异常；
    所述通信设备根据所述第一组标识，向所述第二移动管理实体发送所述第一终端相关的消息。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，所述通信设备获取第一移动管理实体服务的第一终端所在终端组的第一组标识，包括：
    所述通信设备接收所述第一终端相关的消息，其中，所述第一终端相关的消息中携带所述第一终端所在终端组的第一组标识；
    或者，所述通信设备从所述第一终端的上下文中确定所述第一终端所在终端组的第一组标识。
  8. 根据权利要求1-7任一项所述的方法，其特征在于，所述方法还包括：
    所述通信设备获取所述第一移动管理实体服务的第二终端所在终端组的第二组标识；
    在所述第一移动管理实体发生异常的情况下，所述通信设备根据所述第二组标识，向第三移动管理实体发送所述第二终端相关的消息，其中，所述第三移动管理实体为存在所述第二终端的上下文的移动管理实体。
  9. 根据权利要求1-8任一项所述的方法，其特征在于，所述通信设备包括接入设备或者会话管理实体。
  10. 一种通信方法，其特征在于，所述方法包括：
    第二移动管理实体接收来自第一移动管理实体的所述第一移动管理实体服务的第一终端的上下文；
    所述第二移动管理实体确定所述第一移动管理实体发生异常；
    所述第二移动管理实体向通信设备发送第一指示消息，所述第一指示消息用于指示第一组标识对应的终端组中的终端由所述第二移动管理实体提供服务，其中，所述第一组标识为所述第一终端所在终端组的组标识。
  11. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    所述第二移动管理实体接收来自所述通信设备的所述第一终端相关的消息。
  12. 根据权利要求10或11所述的方法，其特征在于，所述方法包括：
    所述第二移动管理实体接收来自第三移动管理实体的所述第三移动管理实体服务的第二终端的上下文；
    所述第二移动管理实体确定所述第三移动管理实体发生异常；
    所述第二移动管理实体向所述通信设备发送第二指示消息，所述第二指示消息用于指示第二组标识对应的终端组中的终端由所述第二移动管理实体提供服务，其中，所述第二组标识为所述第二终端所在终端组的组标识。
  13. 一种通信设备，其特征在于，所述通信设备包括：获取模块和发送模块；
    所述获取模块，用于获取第一移动管理实体服务的第一终端所在终端组的第一组标识；
    所述发送模块，用于在所述第一移动管理实体发生异常的情况下，根据所述第一组标识，向第二移动管理实体发送所述第一终端相关的消息，其中，所述第二移动管理实体为存在所述第一终端的上下文的移动管理实体。
  14. 根据权利要求13所述的通信设备，其特征在于，所述第一组标识为配置在所述第一移动管理实体中的主组标识、配置在所述第二移动管理实体中的备份组标识。
  15. 根据权利要求13或14所述的通信设备，其特征在于，所述通信设备还包括：接收模块；
    所述接收模块，用于接收第一指示消息，所述第一指示消息用于指示所述第一组标识对应的终端组中的终端由所述第二移动管理实体提供服务。
  16. 根据权利要求15所述的通信设备，其特征在于，所述接收模块具体用于：
    接收来自所述第二移动管理实体的所述第一指示消息，其中，所述第一指示消息为所述第二移动管理实体确定所述第一移动管理实体发生异常的情况下发送给所述通信设备的。
  17. 根据权利要求13或14所述的通信设备，其特征在于，所述通信设备还包括：接收模块；
    所述接收模块，用于接收第一指示消息，所述第一指示消息用于指示在所述第一移动管理实体发生异常的情况下，所述第一组标识对应的终端组中的终端由所述第二移动管理实体提供服务。
  18. 根据权利要求17所述的通信设备，其特征在于，所述接收模块具体用于：
    在所述第一移动管理实体发生异常之前，接收所述第一指示消息；
    所述发送模块具体用于：
    确定所述第一移动管理实体发生异常；
    根据所述第一组标识，向所述第二移动管理实体发送所述第一终端相关的消息。
  19. 根据权利要求13-18任一项所述的通信设备，其特征在于，所述获取模块具体用于：
    接收所述第一终端相关的消息，其中，所述第一终端相关的消息中携带所述第一终端所在终端组的第一组标识；
    或者，从所述第一终端的上下文中确定所述第一终端所在终端组的第一组标识。
  20. 根据权利要求13-19任一项所述的通信设备，其特征在于，
    所述获取模块，还用于获取所述第一移动管理实体服务的第二终端所在终端组的第二组标识；
    所述发送模块，还用于在所述第一移动管理实体发生异常的情况下，根据所述第二组标识，向第三移动管理实体发送所述第二终端相关的消息，其中，所述第三移动管理实体为存在所述第二终端的上下文的移动管理实体。
  21. 根据权利要求13-20任一项所述的通信设备，其特征在于，所述通信设备包括接入设备或者会话管理实体。
  22. 一种第二移动管理实体，其特征在于，所述第二移动管理实体包括：接收模块、确定模块和发送模块；
    所述接收模块，用于接收来自第一移动管理实体的所述第一移动管理实体服务的第一终端的上下文；
    所述确定模块，用于确定所述第一移动管理实体发生异常；
    所述发送模块，用于向通信设备发送第一指示消息，所述第一指示消息用于指示第一组标识对应的终端组中的终端由所述第二移动管理实体提供服务，其中，所述第一组标识为所述第一终端所在终端组的组标识。
  23. 根据权利要求22所述的第二移动管理实体，其特征在于，
    所述接收模块，还用于接收来自所述通信设备的所述第一终端相关的消息。
  24. 根据权利要求22或23所述的第二移动管理实体，其特征在于，
    所述接收模块，还用于接收来自第三移动管理实体的所述第三移动管理实体服务的第二终端的上下文；
    所述确定模块，还用于确定所述第三移动管理实体发生异常；
    所述发送模块，还用于向所述通信设备发送第二指示消息，所述第二指示消息用于指示第二组标识对应的终端组中的终端由所述第二移动管理实体提供服务，其中，所述第二组标识为所述第二终端所在终端组的组标识。
  25. 一种通信设备，其特征在于，包括：处理器、存储器；
    所述存储器用于存储计算机执行指令，当所述通信设备运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述通信设备执行如权利要求1-9中任意一项所述的通信方法。
  26. 一种第二移动管理实体，其特征在于，包括：处理器、存储器；
    所述存储器用于存储计算机执行指令，当所述第二移动管理实体运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述第二移动管理实体执行如权利要求10-12中任意一项所述的通信方法。
  27. 一种通信系统，其特征在于，所述通信系统包括第一移动管理实体、第二移动管理实体以及通信设备；
    其中，所述第一移动管理实体，用于向所述第二移动管理实体发送所述第一移动管理实体服务的第一终端的上下文；
    所述第二移动管理实体，用于接收来自所述第一移动管理实体的所述第一终端的上下文；
    所述通信设备，用于获取所述第一终端所在终端组的第一组标识，并在所述第一移动管理实体发生异常的情况下，根据所述第一组标识，向所述第二移动管理实体发送所述第一终端相关的消息；
    所述第二移动管理实体，还用于接收来自所述通信设备的所述第一终端相关的消息。
  28. 根据权利要求27所述的通信系统，其特征在于，
    所述第二移动管理实体，还用于确定所述第一移动管理实体发生异常；
    所述第二移动管理实体，还用于向所述通信设备发送第一指示消息，所述第一指示消息用于指示所述第一组标识对应的终端组中的终端由所述第二移动管理实体提供服务；
    所述通信设备，还用于接收所述第一指示消息。
  29. 根据权利要求27所述的通信系统，其特征在于，
    所述通信设备，还用于在所述第一移动管理实体发生异常之前，接收第一指示消息，所述第一指示消息用于指示在所述第一移动管理实体发生异常的情况下，所述第一组标识对应的终端组中的终端由所述第二移动管理实体提供服务；
    所述通信设备，还用于确定所述第一移动管理实体发生异常。
  30. 一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行如权利要求1-9中任意一项所述的通信方法。
  31. 一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行如权利要求10-12中任意一项所述的通信方法。
PCT/CN2018/097138 2017-07-31 2018-07-26 通信方法、设备及系统 WO2019024747A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP21194902.9A EP4007437B1 (en) 2017-07-31 2018-07-26 Communication methods and access device
EP18840816.5A EP3657869B1 (en) 2017-07-31 2018-07-26 Communication method, device and system
BR112020002055-9A BR112020002055A2 (pt) 2017-07-31 2018-07-26 método de comunicação, dispositivo de comunicações e sistema de comunicações
US16/748,340 US11184757B2 (en) 2017-07-31 2020-01-21 Communication method, communications device, and communications system
US17/478,218 US11968743B2 (en) 2017-07-31 2021-09-17 Communication method, communications device, and communications system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710640133.9A CN109327849B (zh) 2017-07-31 2017-07-31 通信方法、设备及系统
CN201710640133.9 2017-07-31

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/748,340 Continuation US11184757B2 (en) 2017-07-31 2020-01-21 Communication method, communications device, and communications system

Publications (1)

Publication Number Publication Date
WO2019024747A1 true WO2019024747A1 (zh) 2019-02-07

Family

ID=65233507

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/097138 WO2019024747A1 (zh) 2017-07-31 2018-07-26 通信方法、设备及系统

Country Status (6)

Country Link
US (2) US11184757B2 (zh)
EP (2) EP4007437B1 (zh)
CN (2) CN109327849B (zh)
BR (1) BR112020002055A2 (zh)
ES (1) ES2944910T3 (zh)
WO (1) WO2019024747A1 (zh)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3603214A1 (en) * 2017-03-20 2020-02-05 Telefonaktiebolaget LM Ericsson (PUBL) Methods and arrangements for transferring management of wireless devices between core network nodes of a wireless communication network
FR3072537A1 (fr) * 2017-10-17 2019-04-19 Orange Procede de basculement d'un equipement de gestion dans un reseau de telecommunications
US11310662B2 (en) * 2018-12-12 2022-04-19 Bank Of America Corporation System for 5G enabled rapid bandwidth deployment
CN111770123B (zh) * 2019-04-02 2022-01-11 华为技术有限公司 通信方法、设备及存储介质
CN110167052B (zh) * 2019-04-04 2022-05-10 南京邮电大学 一种基于池技术的amf网元部署系统及运行方法
CN110366276B (zh) * 2019-07-03 2022-04-12 中国联合网络通信集团有限公司 服务化架构基站
CN112203265B (zh) * 2020-11-02 2022-08-02 中国联合网络通信集团有限公司 上下文信息重建方法、mme、msc/vlr及hss
CN114945002B (zh) * 2021-02-09 2023-07-25 大唐移动通信设备有限公司 Amf选择方法、装置、网络设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101247255A (zh) * 2007-02-13 2008-08-20 华为技术有限公司 一种处理故障的方法及系统
CN102740266A (zh) * 2011-04-12 2012-10-17 中兴通讯股份有限公司 一种上下文的同步方法及系统
US20140219178A1 (en) * 2012-01-20 2014-08-07 Verizon Patent And Licensing Inc. Optimizing user device context for mobility management entity (mme) resiliency

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7099477B2 (en) * 2004-10-21 2006-08-29 International Business Machines Corporation Method and system for backup and restore of a context encryption key for a trusted device within a secured processing system
US20080065637A1 (en) * 2005-04-14 2008-03-13 Emc Corporation Locating last processed data
CN101043712B (zh) * 2006-03-22 2010-05-12 华为技术有限公司 在无线通信系统中实现切换的方法及系统
CN101730124A (zh) * 2008-10-29 2010-06-09 华为技术有限公司 恢复业务的方法、装置和系统
US20110235505A1 (en) * 2010-03-29 2011-09-29 Hitachi, Ltd. Efficient deployment of mobility management entity (MME) with stateful geo-redundancy
ES2540991T3 (es) * 2010-05-11 2015-07-15 Nec Europe Ltd. Método para manejar el fallo de una MME en un sistema de paquetes evolucionado
JP5664988B2 (ja) * 2010-09-08 2015-02-04 ▲ホア▼▲ウェイ▼技術有限公司 ページング処理方法およびシステム、サービングゲートウェイ
CN102520916B (zh) 2011-11-28 2015-02-11 深圳中微电科技有限公司 在mvp处理器中消除纹理延迟和寄存器管理的方法
US8908603B2 (en) * 2012-01-24 2014-12-09 Telefonaktiebolaget L M Ericsson (Publ) MME restoration
BR112014017934A8 (pt) * 2012-01-24 2017-07-11 Ericsson Telefon Ab L M Recuperação de mme
US9185584B1 (en) * 2013-06-06 2015-11-10 Sprint Spectrum L.P. Dual controller functionality in a wireless communication system
WO2016144245A1 (en) * 2015-03-09 2016-09-15 Telefonaktiebolaget Lm Ericsson (Publ) User equipment registration recovery upon core node failure
US10582522B2 (en) * 2015-09-04 2020-03-03 Lg Electronics Inc. Data transmission and reception method and device of terminal in wireless communication system
US9608860B1 (en) * 2016-03-28 2017-03-28 Affirmed Networks Communications Technologies, Inc. Synchronized MME pool
WO2017175715A1 (ja) * 2016-04-05 2017-10-12 シャープ株式会社 端末装置、基地局装置、ＭＭＥ（Ｍｏｂｉｌｉｔｙ Ｍａｎａｇｅｍｅｎｔ Ｅｎｔｉｔｙ）及び通信制御方法
EP3432641B1 (en) * 2017-01-09 2022-10-05 LG Electronics Inc. Method for interworking between networks in wireless communication system and apparatus therefor

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101247255A (zh) * 2007-02-13 2008-08-20 华为技术有限公司 一种处理故障的方法及系统
CN102740266A (zh) * 2011-04-12 2012-10-17 中兴通讯股份有限公司 一种上下文的同步方法及系统
US20140219178A1 (en) * 2012-01-20 2014-08-07 Verizon Patent And Licensing Inc. Optimizing user device context for mobility management entity (mme) resiliency

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
BR112020002055A2 (pt) 2020-09-08
CN114339910A (zh) 2022-04-12
CN109327849A (zh) 2019-02-12
US11968743B2 (en) 2024-04-23
EP4007437B1 (en) 2023-03-29
EP3657869A1 (en) 2020-05-27
EP4007437A1 (en) 2022-06-01
US11184757B2 (en) 2021-11-23
US20220007167A1 (en) 2022-01-06
ES2944910T3 (es) 2023-06-27
US20200162888A1 (en) 2020-05-21
EP3657869A4 (en) 2020-08-26
EP3657869B1 (en) 2021-11-17
CN109327849B (zh) 2021-12-03

Similar Documents

Publication Publication Date Title
US11612013B2 (en) Data transmission method, device, and system
US11812484B2 (en) Data transmission method, device, and data transmission system
WO2019024747A1 (zh) 通信方法、设备及系统
CN110049485B (zh) 一种配置ue的策略的方法、装置和系统
WO2018214597A1 (zh) 接入网类型选择方法、设备及系统
US11716667B2 (en) Handover method, device, and system
WO2019120073A1 (zh) 数据传输方法、设备及系统
US10897699B2 (en) Subscription update method, device, and system
WO2019223702A1 (zh) 管理pdu会话的方法、装置和系统
WO2019174437A1 (zh) 地址管理方法、设备及系统
WO2018191867A1 (zh) 终端监控信息的同步方法、设备及系统
WO2019015627A1 (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: 18840816

Country of ref document: EP

Kind code of ref document: A1

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: 112020002055

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 2018840816

Country of ref document: EP

Effective date: 20200219

ENP Entry into the national phase

Ref document number: 112020002055

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20200130