WO2021057526A1

WO2021057526A1 - Disaster recovery method for gateway device, and communication device

Info

Publication number: WO2021057526A1
Application number: PCT/CN2020/115066
Authority: WO
Inventors: 黄泽旭; 周军平; 林玮健; 钱涛; 徐日东
Original assignee: 华为技术有限公司
Priority date: 2019-09-23
Filing date: 2020-09-14
Publication date: 2021-04-01
Also published as: CN112543468A; CN112543468B

Abstract

Provided in the embodiments of the present application are a disaster recovery method for a gateway device, and a communication device. The disaster recovery method for the gateway device comprises: a first access and mobile management device receiving a service request of a terminal device; in response to the service request, if a first gateway control plane device is determined to have failed, the first access and mobile management device selecting a second gateway control plane device, wherein the first gateway control plane device is used for managing a session of the terminal device at a gateway user plane device; and the first access and mobile management device sending a first message to the second gateway control plane device, wherein the first message comprises first disaster recovery data corresponding to the terminal device, and the first disaster recovery data is used by the second gateway control plane device to recover, according to the first disaster recovery data, the session of the terminal device at the gateway user plane device. According to the embodiments of the present application, complexity of session recovery can be simplified, reliability of session recovery can be improved, a resource utilization rate can be improved, and costs can be reduced.

Description

Method for disaster tolerance of gateway equipment and communication equipment

This application claims the priority of a Chinese patent application filed with the State Intellectual Property Office of China, the application number is 201910901318.X, and the invention title is "A method for disaster recovery of gateway equipment and communication equipment" on September 23, 2019, all of which The content is incorporated in this application by reference.

Technical field

The present invention relates to the field of communication technology, in particular to a method for disaster tolerance of a gateway device and a communication device.

Background technique

In the prior art, based on the concept of separation of the control plane and the user plane, the network architecture includes a gateway control plane device and a gateway user plane device. The gateway control plane device is usually used as a session management functional entity to implement session access and management, and to serve as a terminal The device selects the gateway user plane device. After the gateway control plane device selects the gateway user plane device for the terminal device, the gateway control plane device manages the terminal device's session with the gateway user plane device, such as traffic monitoring, billing, and so on.

In order to ensure that the system can still maintain the session when the gateway control plane device fails, currently, the gateway control plane device usually adopts the active/standby mode, that is, a backup gateway control plane device is deployed for the active gateway control plane device, and the backup gateway control plane device The plane device does not publish the route of the service network protocol (Internet Protocol, IP) address, but only receives the session information backed up by the master gateway control plane device. After the master gateway control plane device fails, the master will be controlled by a centralized control node. All sessions with the control plane device are switched to the backup gateway control plane device, and the backup gateway control plane device provides services. In this way, the standby gateway control plane device does not participate in service processing, the resource utilization is low, and a centralized control node is required to perform fault monitoring and control switching operations, which is costly. In addition, after the main control plane device fails, a large number of sessions need to be restored, the restoration process is complicated, and the backup control plane device has the risk of session restoration failure.

Summary of the invention

The embodiments of the present application provide a method for disaster recovery of a gateway device and a communication device, which can simplify the complexity of session recovery, improve the reliability of session recovery, and improve resource utilization and reduce costs.

In the first aspect, an embodiment of the present application provides a method for disaster recovery of a gateway device, which is applied to a first access and mobility management device, and the method includes: the first access and mobility management device receives a service request from a terminal device.

Among them, the first access and mobility management device can be the source access and mobility management device associated with the terminal device, or, when the terminal device sends a service request, it can be determined that the source access and mobility management device is faulty and reselect The backup access and mobility management device of the device, or, when there is downlink data from the terminal device, the third gateway control plane device is determining the source access and mobility management device failure, randomly selected access and mobility management devices, The third gateway control plane device is the gateway control plane device selected by the gateway user plane device when it determines that the first gateway control plane device associated with the terminal device is faulty. Wherein, the first disaster tolerance data corresponding to the terminal device is stored in the source access and mobility management device. Optionally, the first disaster tolerance data can also be backed up and stored in the backup mobile access and mobility management device. Please refer to the description of the subsequent embodiments for the definitions of the mobility management device and the backup access and mobility management device, and will not be repeated for the time being.

Optionally, the service request may be triggered when the terminal device sends uplink data, or it may also be the presence of downlink data of the terminal device, which triggers the terminal device to send the service request by sending a paging message.

In response to the service request, the first access and mobility management device determines that the first gateway control plane device used to manage the terminal device's session on the gateway user plane device is faulty, and then selects the second gateway control plane device. Wherein, the selection method for the first access and mobility management device to select the second gateway control plane device may be randomly selected or selected based on specific protocol rules.

The first access and mobility management device sends a first message to the selected second gateway control plane device, the first message includes the first disaster tolerance data corresponding to the terminal device, and the first disaster tolerance data is used for the second gateway control The plane device restores the session of the terminal device in the gateway user plane device according to the first disaster tolerance data.

Optionally, the first disaster tolerance data may include, but is not limited to, key data such as the IP address of the terminal device, the gateway user plane device activated by the terminal device, and so on.

Correspondingly, the second gateway control plane device receives the first disaster tolerance data, and restores the session of the terminal device on the gateway user plane device according to the first disaster tolerance data.

By implementing this embodiment, the first access and mobility management device stores the first disaster tolerance data corresponding to the terminal device, and there is no need to set up additional control plane devices for backup and storage of the first disaster tolerance data, reducing costs and improving resource utilization. . And this application is that the first access and mobility management device directly sends the first disaster tolerance data to the newly selected second gateway control plane device to restore the terminal device's session on the gateway user plane device, and no additional configuration of the control node to control the session is required. Recovery simplifies the complexity of session recovery. The session recovery is only performed when the terminal device has service requirements, and the second control plane device is not required to recover a large number of sessions at the same time, which improves the reliability of session recovery.

In a possible design, the first message may be a session creation request or a service message. If the first message is a session creation request, the first access and mobility management device simulates the terminal device attachment process, and the session creation request will The first disaster tolerance data is sent to the second gateway control plane device. After the second gateway control plane device completes the session recovery of the terminal device in the gateway user plane device, the first access and mobility management device sends a service message to the second gateway control plane device to establish the association between the gateway user plane device and the terminal device The bearer between the access network equipment.

If the first message is a business message, the first access and mobility management device and the second gateway control plane device realize the sending of the first disaster tolerance data to the second gateway control plane device through business message interaction, and the business message is used The second gateway control plane device is requested to establish a bearer between the gateway user plane device and the access network device associated with the terminal device. When the second gateway control plane device detects that there is no session context corresponding to the terminal device, it first completes the recovery of the terminal device's session on the gateway user plane device through the first disaster tolerance data, and then controls the establishment of the association between the gateway user plane device and the terminal device. The bearer between the access network equipment.

By implementing this embodiment, if the first message is a session creation request, the reliability of session recovery can be improved, and if the first message is a business message, the efficiency of business processing can be improved.

In a possible design, before the first access and mobility management device receives the service request of the terminal device, the method further includes: the first access and mobility management device receives the second message from the third gateway control plane device, and The second message is sent by the third gateway control plane device when the gateway user plane device receives the downlink data corresponding to the terminal device and determines that the first gateway control plane device is faulty. The second message may include the first indication information. An indication information is used to instruct the first access and mobility management device to send a paging message to the terminal device.

The third gateway control plane device may be a gateway control plane device randomly selected when the gateway user plane device determines that the first gateway control plane device is faulty, or a gateway control plane device selected based on a specific protocol rule.

It should be noted that, in order to facilitate the third gateway control plane device to determine the source access and mobility management device associated with the terminal device, the gateway user plane device sends the identification of the source access and mobility management device to the third gateway control plane device. Optionally, the identification of the source access and mobility management device may be sent by way of addressing information, and the addressing information may include but not limited to the identification of the source access and mobility management device, or used to indicate the first disaster tolerance data For example, the backup storage path of all disaster recovery data with index 1 is from the access and mobility management device A to the access and mobility management device B. The source can also be determined by the index information Access and mobile management equipment.

When the third gateway control plane device determines that the source access and mobility management device is available, it sends to the source access and mobility management device (in this application scenario, the first access and mobility management device is the source access and mobility management device). ) The second message, if it is determined that the source access and mobility management device is faulty, an access and mobility management device is randomly selected and sent to the randomly selected access and mobility management device (in this application scenario, the first access and mobility management device The mobility management device is a randomly selected access and mobility management device) sending the second message.

The aforementioned source access and mobility management device is an access and mobility management device that stores the first disaster tolerance data corresponding to the terminal device in the terminal attachment process.

The first access and mobility management device (the source access and mobility management device or the randomly selected access and mobility management device) sends a paging message to the terminal device according to the first indication information, and the terminal device receives the page After the message, the service request is sent to the first access and mobility management device.

In a possible design, if the above-mentioned first access and mobility management device is a randomly selected access and mobility management device, the first access and mobility management device does not store the first disaster tolerance data. Therefore, the first access and mobility management device does not store the first disaster tolerance data. The second message sent by the third gateway control plane device to the first access and mobility management device also includes addressing information associated with the first disaster tolerance data, and the backup of the first disaster tolerance data can be obtained through the address information storage location.

The first access and mobility management device obtains the first disaster tolerance data corresponding to the terminal device according to the addressing information, where the first disaster tolerance data further includes the identifier of the access network device associated with the terminal device. The first access and mobility management device may send a paging message to the terminal device through the access network device corresponding to the identifier according to the first indication information in the second message.

It should be noted that, in the foregoing embodiment, the addressing information associated with the first disaster tolerance data is pre-stored in the gateway user plane device.

By implementing this embodiment, even when the first gateway control plane device fails, the downlink data corresponding to the terminal device can still be transmitted to the terminal device.

In a possible design, before the first access and mobility management device receives the service request of the terminal device, the terminal device sends an attachment request to the first access and mobility management device. The first access and mobility management device receives the attachment request, and sends a third message to the first gateway control plane device. The third message may be a session creation request, and the third message includes the second indication information and the identification of the terminal device, The second indication information is used to instruct the first gateway control plane device to send the first disaster tolerance data corresponding to the terminal device to the first access and mobility management device.

Correspondingly, the first gateway control plane device sends the first disaster tolerance data corresponding to the terminal device to the first access and mobility management device, and the first access and mobility management device stores the first disaster tolerance data.

By implementing this embodiment, the first disaster tolerance data can be stored in the first access and mobility management device, and there is no need to separately set up a gateway control plane device to backup and store the first disaster tolerance data separately, which can save costs and improve resource utilization.

In a possible design, the first access and mobility management device may also back up the first disaster tolerance data to the second access and mobility management device.

By implementing this embodiment, when the first access and mobility management device fails, the first disaster tolerance data can still be addressed and session recovery can be completed.

In a second aspect, an embodiment of the present application provides a method for disaster recovery of a gateway device, which is applied to a first gateway control plane device, and the method includes: the first gateway control plane device receives a third message from a first access and mobility management device , The third message includes second indication information and the identification of the terminal device, the second indication information is used to instruct the first gateway control plane device to send the first disaster tolerance data corresponding to the terminal device to the first access and mobility management Device, the first disaster tolerance data is used to restore the session of the terminal device on the gateway user plane device when it is determined that the first gateway control plane device is faulty.

The first gateway control plane device sends the first disaster tolerance data to the first access and mobility management device. The first disaster tolerance data includes, but is not limited to, the IP address of the terminal device, which is the gateway user plane device activated by the terminal device, where the activated gateway user plane device refers to the gateway user plane device used to forward the terminal device Upstream data or downstream data.

By implementing this embodiment, the first gateway control plane device sends the first disaster tolerance data to the first access and mobility management device for storage, which can save costs and improve resource utilization.

In a possible design, the third message may also include addressing information associated with the first disaster tolerance data. The addressing information includes, but is not limited to, the identification of the first access and mobility management device, or it is used to indicate the first access and mobility management device. Index information of a backup storage path of disaster tolerance data, etc., for example, the backup storage path of all disaster tolerance data with index 1 is from the access and mobility management device A backed up to the access and mobility management device B, through the index information It is also possible to determine the source access and mobile management equipment. The addressing information can not only determine the first access and mobility management device, but also determine the location for backing up and storing the first disaster recovery data.

The first gateway control plane device sends addressing information and the identification of the terminal device to the gateway user plane device. When the subsequent gateway user plane device receives downlink data corresponding to the terminal device and determines that the first gateway control plane device is faulty, it may Send the addressing information to a randomly selected third gateway control plane device, so as to obtain the first disaster tolerance data.

By implementing this embodiment, the addressing information is stored in the gateway user plane device in advance, so that the gateway user plane device can receive the downlink data of the terminal device, and when it is determined that the first gateway control plane device is faulty, it can still address the first content. Disaster data.

In a third aspect, an embodiment of the present application provides a method for disaster recovery of a gateway device, which is applied to a second gateway control plane device, and the method includes: the second gateway control plane device receives a first message from a first access and mobility management device The first message is triggered when the first access and mobility management device receives the service request of the terminal device and determines that the first gateway control plane device is faulty, and the first message includes the first content corresponding to the terminal device. For disaster data, the first gateway control plane device is used to manage the session of the terminal device on the gateway user plane device.

The second gateway control plane device restores the session of the terminal device in the gateway user plane device according to the first disaster tolerance data.

By implementing this embodiment, the second gateway control plane device can resume the session of the terminal device in the gateway user plane device through simple message interaction, and the recovery process is simple.

In a possible design, the first message is a session creation request or a service message; the service message is used to request the second gateway control plane device to establish a bearer between the gateway user plane device and the access network device associated with the terminal device. For details, please refer to the description of the embodiment of the first aspect, which will not be repeated here.

In a fourth aspect, the embodiments of the present application provide an access and mobility management device, the access and mobility management device is a first access and mobility management device, and the first access and mobility management device may include multiple functions The module or unit is used to correspondingly execute the method for disaster recovery of the gateway device provided in the first aspect.

In a fifth aspect, the embodiments of the present application provide a gateway control plane device. The gateway control plane device is a first gateway control plane device. The first gateway control plane device may include multiple functional modules or units for corresponding Implement the disaster recovery method for gateway equipment provided in the second aspect.

In a sixth aspect, embodiments of the present application provide a gateway control plane device. The gateway control plane device is a second gateway control plane device. The second gateway control plane device may include multiple functional modules or units for corresponding Implement the disaster recovery method for gateway equipment provided by the third aspect.

In a seventh aspect, the embodiments of the present application provide an access and mobility management device. The access and mobility management device is a first access and mobility management device, and the first access and mobility management device is used to execute the first access and mobility management device. Disaster recovery method for gateway equipment provided by the aspect. The first access and mobility management device may include: a memory, a processor, a transmitter, and a receiver, where the transmitter and the receiver are used to communicate with other communication devices. The memory is used to store the implementation code of the gateway device disaster tolerance method provided in the first aspect, and the processor is used to execute the program code stored in the memory, that is, to execute the gateway device disaster tolerance method provided in the first aspect.

In an eighth aspect, an embodiment of the present application provides a gateway control plane device, the gateway control plane device is a first gateway control plane device, and is used to execute the gateway device disaster recovery method provided in the second aspect. The first gateway control plane device may include: a memory, a processor, a transmitter, and a receiver, where the transmitter and the receiver are used to communicate with other communication devices. The memory is used to store the implementation code of the gateway device disaster tolerance provided in the second aspect, and the processor is used to execute the program code stored in the memory, that is, to execute the gateway device disaster tolerance method provided in the second aspect.

In a ninth aspect, an embodiment of the present application provides a gateway control plane device, the gateway control plane device is a second gateway control plane device, and is used to execute the gateway device disaster recovery method provided in the third aspect. The second gateway control plane device may include: a memory, a processor, a transmitter, and a receiver, where the transmitter and the receiver are used to communicate with other communication devices. The memory is used to store the implementation code of the gateway device disaster tolerance provided in the third aspect, and the processor is used to execute the program code stored in the memory, that is, to execute the gateway device disaster tolerance method provided in the third aspect.

In a tenth aspect, an embodiment of the present application provides a communication system. The communication system includes: a first access and mobility management device, a first gateway control plane device, and a second gateway control plane device. among them:

The first access and mobility management device may be the access and mobility management device described in the fourth aspect, or the access and mobility management device described in the seventh aspect.

The first gateway control plane device may be the gateway control plane device described in the foregoing fifth aspect, or may be the gateway control plane device described in the foregoing eighth aspect.

The second gateway control plane device may be the gateway control plane device described in the foregoing sixth aspect, or may be the gateway control plane device described in the foregoing ninth aspect.

In an eleventh aspect, the present application provides a communication chip. The communication chip may include a processor and one or more interfaces coupled to the processor. Wherein, the processor can be used to call the implementation program of the gateway device disaster tolerance method provided by any aspect of the first aspect to the third aspect from the memory, and execute the instructions contained in the program. The interface may be used to output the data processing result of the processor, or to obtain the implementation program from the memory.

In the twelfth aspect, the embodiments of the present application provide a computer-readable storage medium with instructions stored on the readable storage medium, which when run on a processor, cause the processor to execute any of the above-mentioned first to third aspects. On the one hand, a method for disaster recovery of a gateway device is described.

In a thirteenth aspect, the embodiments of the present application provide a computer program product containing instructions that, when run on a processor, cause the processor to execute the gateway device disaster recovery described in any one of the first to third aspects. Methods.

Description of the drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application or the background art, the following will describe the drawings that need to be used in the embodiments of the present application or the background art.

FIG. 1 is a schematic diagram of the architecture of a wireless communication system provided by an embodiment of the present application;

Figure 2 is an optional system architecture diagram provided by an embodiment of the present application;

Figure 3 is another optional system architecture diagram provided by an embodiment of the present application;

FIG. 4 is a schematic diagram of a method for disaster recovery of a gateway device according to an embodiment of the present application;

FIG. 5 is a schematic diagram of a disaster tolerance data collection process provided by an embodiment of the present application;

FIG. 6 is a flow chart of a downlink data transmission paging provided by an embodiment of the present application;

FIG. 7 is a diagram of an optional disaster recovery data collection scenario provided by an embodiment of the present application;

FIG. 8 is a scene diagram of a gateway device disaster tolerance provided by an embodiment of the present application;

FIG. 9 is a diagram of a paging scene for downlink data transmission provided by an embodiment of the present application;

FIG. 10 is a functional block diagram of an access and mobility management device provided by an embodiment of the present application;

FIG. 11 is a schematic diagram of the hardware structure of an access and mobility management device provided by an embodiment of the present application;

FIG. 12 is a functional block diagram of a gateway control plane device provided by an embodiment of the present application;

FIG. 13 is a schematic diagram of the hardware structure of a gateway control plane provided by an embodiment of the present application;

FIG. 14 is a functional block diagram of another gateway control plane device provided by an embodiment of the present application;

15 is a schematic diagram of the hardware structure of another gateway control plane provided by an embodiment of the present application;

FIG. 16 is a schematic structural diagram of a communication chip provided by an embodiment of the present application.

detailed description

The terminology used in the implementation mode part of this application is only used to explain the specific embodiments of this application, and is not intended to limit this application.

The first access and mobility management device, the second access and mobility management device, and the third access and mobility management device in the embodiments of this application may include, but are not limited to, a mobility management entity (MME), and 5G Access and mobility management function (AMF) in the communication system and so on. The entities in the embodiments of the present application may be understood as hardware devices.

The first gateway control plane device, the second gateway control plane device, and the third gateway control plane device in the embodiments of this application include but are not limited to the control plane PDN gateway (PDN Gateway for Control plane, PGW-C), the control plane service gateway ( Serving Gateway for Control plane, SGW-C), and session management function entities (session management function, SMF, etc.) in the 5G communication system, which are not limited in this embodiment of the application.

The gateway user plane equipment in the embodiments of this application includes but is not limited to user plane PDN gateway (PDN Gateway for User plane, PGW-U), user plane service gateway (Serving Gateway for User plane, SGW-U), and 5G communication systems (User plane function, UPF) user plane function entities and so on.

The gateway control plane device in the embodiment of the present application may include one device or a collection of multiple devices. For example, one gateway control plane device may include PGW-C and SGW-C, or one gateway control plane device may include SMF and so on.

The gateway user plane device in the embodiment of the present application may include one device or a collection of multiple devices. For example, one gateway user plane device may include PGW-U and SGW-U, or one gateway user plane device may include UPF and so on.

The source access and mobility management device mentioned in the embodiment of this application may refer to the determined access and mobility management device in the terminal attachment process, and the source access and mobility management device stores the first access and mobility management device corresponding to the terminal device. 1. Disaster recovery data. The backup access and mobility management device in the embodiment of the present application may refer to an access and mobility management device used to backup and store the first disaster tolerance data. There is a corresponding relationship between the source access and mobility management device and the backup access and mobility management device, and the backup access and mobility management device can be addressed through the identification of the source access and mobility management device.

The first, second, and third embodiments of this application are to distinguish different objects in the same scene. Different objects in different scenes may have the same name. For example, in application scenario 1, source access and mobile management equipment It is called the first access and mobility management device. In the second application scenario, the backup access and mobility management device is called the first access and mobility management device and so on.

The first gateway control plane device associated with the terminal device mentioned in the embodiment of the present application may refer to a device used to manage the terminal device's session on the gateway user plane device.

The gateway user plane device associated with the terminal device mentioned in the embodiment of the present application may refer to a device for forwarding uplink data or downlink data corresponding to the terminal device.

The access network device associated with the terminal device mentioned in the embodiment of the present application may refer to the terminal device in a cell under the access network device.

Refer to FIG. 1, which is a schematic diagram of the architecture of a wireless communication system provided by an embodiment of the present application. The wireless communication system 100 includes, but is not limited to: terminal equipment 101, access network (access network, AN) equipment 102, gateway user plane equipment 103, gateway control plane equipment 104, access and mobility management equipment 105, and data network (data network, DN) device 106. among them,

The terminal device 101 may also be referred to as user equipment, mobile station, access terminal, user unit, user station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device, etc. . The terminal device can be a handheld user equipment, a notebook computer, a subscriber unit, a cellular phone, a smart phone, a wireless data card, a personal digital assistant (PDA), and wireless communication. Functional handheld devices, in-vehicle devices, wearable devices, mobile stations in the future 5G network or terminal devices in the future evolved public land mobile network (PLMN) network, etc. The terminal device 101 and the access network device 102 communicate with each other using a certain air interface technology.

The access network device 102 is mainly responsible for functions such as radio resource management, quality of service (QoS) management, data compression, and encryption on the air interface side. The access network equipment 102 may include various forms of access network equipment, such as: a macro base station, a micro base station (also referred to as a small station), a relay station, and an access point. In systems using different wireless access technologies, the names of access network devices may be different. For example, in 5G communication systems, they are called next-generation Node B (gNB); in the long-term evolution In a long term evolution (LTE) system, it is called an evolved NodeB (evolved NodeB, eNB or eNodeB); in a third generation (3rd Generation, 3G) system, it is called a Node B (Node B), etc.

The gateway user plane device 103 is used for receiving data packets from the terminal device 101 and forwarding the data packets. The gateway user plane device 103 may include various forms of user plane devices, including but not limited to user plane PDN gateway (PDN Gateway for User plane, PGW-U), user plane service gateway (Serving Gateway for User plane, SGW-U) , And the (user plane function, UPF) user plane function entity in the 5G communication system, etc.

The gateway control plane device 104 is used to manage the creation and deletion of a packet data unit (PDU) session of the user, and maintain the PDU session context and user plane forwarding management channel information. Gateway control plane devices may include various forms of control plane devices, including but not limited to PDN Gateway for Control plane (PGW-C) and Serving Gateway for Control plane (SGW-C), And the session management function entity (session management function, SMF) in the 5G communication system.

The access and mobility management device 105 is used to perform access and mobility management, interact with network elements such as the access network device 102 and the gateway control plane device 104, and forward signaling. Access and mobility management equipment includes, but is not limited to, the mobility management entity (MME) in the LTE system, and the access and mobility management entity in the 5G communication system.

The data network equipment 106 is used to provide users with various services (for example, network access, operator services, etc.). For example, the data network device 106 may be a server.

Types of data networks include, but are not limited to: Internet, Internet protocol multimedia subsystem (IMS).

In the above-mentioned wireless communication system 100, the terminal device 101 and the access network device 102 communicate through a wireless interface, and the terminal device 101 and the access and mobility management device 105 may also communicate through a wireless interface.

Optionally, please refer to Figure 2 and Figure 3 for the two optional detailed network architecture diagrams proposed for this application. As shown in Figure 2, PGW-U and SGW-U can correspond to the gateway in Figure 1 The user plane equipment, PGW-C and SGW-C may correspond to the gateway control plane equipment in FIG. 1. The MME may correspond to the access and mobility management equipment in FIG. 1, and the E-UTRAN may correspond to the access network equipment in FIG. 1.

As shown in Figure 3, UPF can correspond to the gateway user plane device in Figure 1, SMF can correspond to the gateway control plane device in Figure 1, AMF can correspond to the access and mobility management device in Figure 1, RAN can correspond to Access network equipment in Figure 1.

It should be noted that FIGS. 1 to 3 are only to illustrate the communication connection relationship between the devices, and the communication interfaces between the devices are as shown in FIGS. 2 to 3 respectively. It is understandable that in actual application scenarios, the number of each device may include one or more, for example, it may include one or more gateway control plane devices, one or more access and mobility management devices, one or more Gateway user plane devices, etc., are not limited in the embodiment of the present application.

Based on each device in the aforementioned wireless communication system 100, an embodiment of the present application provides a method for disaster recovery of a gateway device. As shown in Figure 4, the method includes but is not limited to the following steps.

S301: The first access and mobility management device receives the service request of the terminal device;

In the embodiment of the present application, the first access and mobility management device may be the source access and mobility management device associated with the terminal device, or it may be the source access and mobility management device that is determined when the terminal device sends a service request Failure, re-selected backup access and mobile management equipment. Or the first access and mobility management device may also be a randomly selected access and mobility management device when the third gateway control plane device determines that the source access and mobility management device is faulty when there is downlink data from the terminal device. The third gateway control plane device is the gateway control plane device selected by the gateway user plane device when it determines that the first gateway control plane device associated with the terminal device is faulty.

The first disaster tolerance data corresponding to the terminal device is stored in the source access and mobility management device. Optionally, the first disaster tolerance data may also be backed up and stored in the backup mobile access and mobility management device. For the specific processing process of storing the first disaster tolerance data in the source access and mobility management device, please refer to the description of the embodiment in FIG. 5, which will not be repeated here.

Generally, the interface between the access network device and the gateway user plane device is released. If the terminal device sends uplink data, or there is downlink data sent to the terminal device, it is used to manage the gateway control of the terminal device’s session on the gateway user plane device. Re-establish the bearer between the access network device and the gateway user plane device, where the terminal device sends a Service Request (SR), which is used to trigger the re-establishment of the access network device and the gateway user plane device Bearer between.

Specifically optional, the following two optional implementation manners are separately described. The specific processing flow of triggering the terminal device to send the service request in the presence of uplink data sent by the terminal device and downlink data sent to the terminal device:

In the first optional implementation manner, if a terminal device sends uplink data, it sends a service request to the source access and mobility management device associated with the terminal device. Correspondingly, the source access and mobility management device (in this application scenario) Next, the first access and mobility management device (the source access and mobility management device) receives the service request of the terminal device and responds to the service request. Optionally, if the source access and mobility management device associated with the terminal device fails, you can select the backup access and mobility management device for backing up and storing the first disaster tolerance data corresponding to the terminal device, and connect to the backup The access and mobility management device (in this application scenario, the first access and mobility management device is the backup access and mobility management device) sends a service request, and correspondingly, the backup access and mobility management device receives the service request of the terminal device, And respond to the business request.

In the second optional implementation manner, if there is downlink data sent to the terminal device, such as sending a message to the WeChat application of the terminal device, the message is first transmitted to the gateway user plane device associated with the terminal device. The interface between the device and the access network device is released. Therefore, the gateway user plane device sends a service message to the gateway control plane device used to manage the terminal device’s session on the gateway user plane device to trigger the gateway control plane device to control the establishment of the The bearer between the gateway user plane device and the access network device. For specific options, please refer to FIG. 6, which is a flow chart of downlink data transmission processing provided in this embodiment of the application, including but not limited to steps S51-S53;

S51: The gateway user plane device receives the downlink data of the terminal device, determines that the first control plane device is faulty, and sends addressing information associated with the first disaster tolerance data to the third gateway control plane device;

The first control plane device is used to manage the session of the terminal device on the gateway user plane device. When the gateway user plane device determines that the first control plane device is faulty, it can reselect a gateway control plane device, such as the third gateway control plane device The selection method may be random selection, or selection based on specific protocol rules, etc., which is not limited in the embodiment of the present application. Optionally, the way for the gateway user plane device to determine that the first gateway control plane device is faulty may be that the gateway user plane device sends multiple request messages to the first gateway control plane device, and none of the first gateway control plane device responds. , It is determined that the control plane device of the first gateway is faulty.

In order to facilitate the third gateway control plane device to determine the source access and mobility management device associated with the terminal device, or when the source access and mobility management device fails, address the first disaster tolerance data corresponding to the terminal device to recover For the session of the terminal device on the gateway user plane device, the gateway user plane device will send addressing information to the third gateway control plane device. The addressing information includes but not limited to the identity of the source access and mobility management device or is used to indicate the first The index information of the backup storage path of disaster tolerance data. For example, the backup storage path of all disaster tolerance data with index 1 is from the backup of the access and mobility management device A to the access and mobility management device B, etc., through the index information not only The source access and mobile management equipment can be determined, and the backup access and mobile management equipment can also be determined. It should be noted that, in the embodiment of the present application, the addressing information may be stored in the gateway user plane device in advance through step S43 in the embodiment of FIG. 5.

S52. The third gateway control plane device sends a second message to the first access and mobility management device, where the second message includes first indication information, and the first indication information is used to indicate the first access and mobility The management device sends a paging message to the terminal device;

S53. The first access and mobility management device receives a second message from a third gateway control plane device, and sends a paging message to the terminal device according to the first indication information, where the paging message is used to trigger The terminal device sends the service request.

Correspondingly, the third gateway control plane device receives the addressing information, and can learn the source access and mobility management equipment corresponding to the terminal device through the addressing information, and the third gateway control plane device first determines the source access and mobility management equipment Whether it is available, if it is determined that the source access and mobility management device is available, a second message is sent to the source access and mobility management device. The second message contains the first indication information, and the first indication information is used for Instruct the source access and mobility management device to send a paging message to the terminal device. Correspondingly, the source access and mobility management device receives the second message, and further, the source access and mobility management device detects that there is a session context corresponding to the terminal device, so the first access and mobility management device pre-stores With the identification of the access network device associated with the terminal device, the first access and mobility management device can directly send a page to the terminal device through the stored access network device associated with the terminal device according to the first indication information news. After receiving the paging message, the terminal device sends a service request to the source access and mobility management device (in this application scenario, the first access and mobility management device is the source access and mobility management device).

Optionally, if the third gateway control plane device determines that the source access and mobility management device is faulty, it can randomly select an access and mobility management device, and send the addressing information and the first indication information to the randomly selected access device. Access and mobility management equipment, so that when the randomly selected access and mobility management device detects that there is no session context corresponding to the terminal device, it can obtain the backup storage location of the first disaster tolerance data through the addressing information, and obtain the backup storage location from the backup The storage location obtains the first disaster recovery data. The first disaster tolerance data also includes the identifier of the access network device associated with the terminal device, and the randomly selected access and mobility management device sends a paging message to the terminal device through the access network device.

After receiving the paging message, the terminal device sends a service request to the randomly selected access and mobility management device (in this application scenario, the first access and mobility management device is the randomly selected access and mobility management device).

After the first access and mobility management device (the source access and mobility management device or the randomly selected access and mobility management device) receives the service request of the terminal device, it is determined to be used for managing the terminal device in the gateway user plane device If the first gateway control plane device of the conversation fails, the second gateway control plane device is selected, and a first message is sent to the second gateway control plane device. The first message includes the first disaster tolerance data corresponding to the terminal device, and the second The gateway control plane device restores the session of the terminal device on the gateway user plane device according to the first disaster tolerance data. (For details, please refer to the description of S302-S304, which will not be repeated here)

When the second gateway control plane device resumes the session of the terminal device with the gateway user plane device, the second gateway control plane device controls the bearer between the access network device associated with the terminal device and the gateway user plane device, and the gateway user plane device That is, the aforementioned downlink data corresponding to the terminal device can be transmitted to the terminal device through the established bearer, so that the downlink data of the terminal device can still be transmitted to the terminal device even in a scenario where the first gateway control plane device fails.

Optionally, the first access and mobility management device of this embodiment may include AMF, the first gateway control plane device may include SMF, and the gateway user plane device may include UPF, or the first access and mobility management device may include MME, the first gateway control plane device may include SGW-C and PGW-C, and the gateway user plane device may include SGW-U and PGW-U. Please refer to FIG. The paging process and the process of triggering the terminal equipment to send the service request are explained. The two data centers DC1 and DC2 are equipped with equipment such as MME, SGW-C, PGW-C, and the user plane equipment SGW-U and PGW-U are located in Close to the location of the user (for example, the province where the user is located), this embodiment includes the following steps:

1. The downlink data of the terminal device is transmitted to the PGW-U, and the PGW-U forwards the downlink data to the SGW-U. Since the S1-U interface between the SGW-U and the access network device is released, the downlink data is initiated Notification (Downlink Data Notification, DDN) process. The DDN process includes: SGW-U notifies the SGW-C associated with the terminal equipment to page the terminal equipment, SGW-C notifies the MME to initiate paging, the MME initiates a paging process to the terminal equipment through the access network equipment, and the terminal receives the page. Go online after the call, re-establish the S1-U bearer, and then send the downlink data to the terminal device.

In the embodiment of the present application, in order to be able to still send downlink data to the terminal device when the control plane of the gateway associated with the terminal device fails. In the embodiment of this application, if the SGW-U determines that the SGW-C associated with the terminal device is faulty, the SGW-U randomly selects an available SGW-C (such as SGW-C4) to initiate the DDN process, that is, the SGW-U sends the SGW-C4 to the SGW-C4. Send a DDN message. The DDN message includes addressing information. The addressing information may include, but is not limited to, the identification of the source MME (for example: S-MME) used to store the first disaster tolerance data corresponding to the terminal device or for indicating Index information of the backup storage path of the first disaster tolerance data.

2. After SGW-C4 receives the DDN message, SGW-C4 detects that there is no context for the session corresponding to the terminal device. The DDN message contains the S-MME identifier. If SGW-C4 determines whether the S-MME is available, if the S-MME is available, -If the MME is available, select the S-MME and send a DDN message to the S-MME; optionally, if SGW-C4 determines that the S-MME is faulty, it randomly selects an available MME (such as MME4) and sends it to MME4 Send a DDN message, which includes addressing information. Wherein, MME4 is an MME selected at random, so MME4 may not be the MME corresponding to the S-MME for backing up and storing the first disaster tolerance data corresponding to the terminal device.

3. If SGW-C4 is a DDN message sent to S-MME, the S-MME stores all disaster tolerance data corresponding to the terminal equipment, including the access network equipment associated with the terminal equipment, so the S-MME can directly pass The access network device associated with the terminal device initiates a paging process to the terminal device.

If SGW-C4 is a DDN message sent to MME4, after MME4 receives the DDN message, MME4 detects that there is no session context corresponding to the terminal device locally, and then obtains the first corresponding terminal device according to the addressing information carried in the DDN message. 1. Disaster recovery data. For example, if an MME (such as MME2) used for backing up and storing the first disaster tolerance data is acquired according to the S-MME identifier, the first disaster tolerance data is acquired from MME2. The identification of the access network device associated with the terminal device can be obtained from the first disaster tolerance data, and the MME 4 initiates a paging process for the access network device.

After receiving the page, the terminal device sends a service request to MME4.

S302: In response to the service request, the first access and mobility management device determines that the first gateway control plane device is faulty, and then selects a second gateway control plane device, and the first gateway control plane device is used to manage the terminal The device's session on the gateway user plane device;

S303: The first access and mobility management device sends a first message to the second gateway control plane device, where the first message includes first disaster tolerance data corresponding to the terminal device, and the first tolerance The disaster data is used by the second gateway control plane device to restore the session of the terminal device in the gateway user plane device according to the first disaster tolerance data.

S304: The second gateway control plane device restores the session of the terminal device with the gateway user plane device according to the first disaster tolerance data.

In one embodiment, after receiving the service request of the terminal device, the first access and mobility management device determines that the first gateway control plane device associated with the terminal device is faulty. Optionally, it may be that the first access and mobility management device does not receive a response message from the first gateway control plane device after sending multiple messages to the first gateway control plane device associated with the terminal device, and then determines the first gateway control plane device. A gateway control plane device is faulty, and a second gateway control plane device is selected. Optionally, the selection method may be random selection or selection based on specific protocol rules, which is not limited in the embodiment of the present application.

Optionally, the first message may be a session creation request (for example: Create Session Request), which simulates the attachment process of the terminal device. When the second gateway control plane device restores the session of the terminal device in the gateway user plane device according to the first disaster tolerance data in the session creation request, it sends a response message of successful restoration to the first access and mobility management device.

After the first access and mobility management device receives the successful recovery response message sent by the second gateway control plane device, it sends a service message to the second gateway control plane device according to the service request of the terminal device. The service message is used for Request the second gateway control plane device to establish a bearer between the gateway user plane device associated with the terminal device and the access network device associated with the terminal device, when the bearer between the gateway user plane device and the access network device associated with the terminal device is established After success, the terminal device can use the bearer to send uplink data or receive downlink data. Among them, if the above service request is triggered by the presence of uplink data sent by the terminal device, the terminal device can use the bearer to send uplink data. If the above service request is the presence of downlink data sent to the terminal device, the terminal device is triggered through the paging process If it is sent, the terminal device can use the bearer to receive downlink data.

Optionally, the first message may be a service message, that is, the first access and mobility management device sends a service message according to the service request of the terminal device. In this scenario, the terminal device is in the gateway user plane in the normal service interaction process. The session of the device is resumed. The service message includes the first disaster tolerance data corresponding to the terminal device. After receiving the service message, the second gateway control plane device detects that the session context corresponding to the terminal device does not exist locally, and then restores according to the first disaster tolerance data The terminal device has a session with the gateway user plane device, and then processes the service indicated by the service message, such as controlling the establishment of a bearer between the gateway user plane device associated with the terminal device and the access network device associated with the terminal device, so as to facilitate The terminal device sends uplink data or receives downlink data. Among them, if the above service request is triggered by the presence of uplink data sent by the terminal device, the terminal device can use the bearer to send uplink data. If the above service request is the presence of downlink data sent to the terminal device, the terminal device is triggered through the paging process If it is sent, the terminal device can use the bearer to receive downlink data.

Wherein, resuming the session of the terminal device on the gateway user plane device includes but is not limited to: the second gateway control plane device reestablishes the session with the surrounding entities, such as resuming the charging session with the online charging system (Online Charging System, OCS), Resume the session with the Policy and Charging Rules Function (PCRF), take over the bearer of the terminal equipment on the gateway user equipment, and so on. Taking over the bearer of the terminal device on the gateway user plane device may include but is not limited to: when there is subsequent uplink data or downlink data of the terminal device, when the second gateway control plane device is available, the connection can be established through the second gateway control plane device. The bearer between the network access device and the gateway user plane device.

Optionally, the first access and mobility management device may include AMF, the gateway control plane device may include SMF, the gateway user plane device may include UPF, or the access and mobility management device may include MME, and the gateway control plane device may include SGW-C and PGW-C, the gateway user plane equipment may include SGW-U and PGW-U. Please refer to Figure 8. The embodiment of this application illustrates the process of initiating a service request by the terminal and performing session recovery. Both Both data centers DC1 and DC2 are deployed with MME, SGW-C, PGW-C, online charging system OCS, and policy control and rule function PCRF equipment. User plane equipment SGW-U and PGW-U are located close to users ( For example, the province where the user is located), this embodiment includes the following steps:

1. The terminal device sends an SR request through the access network device. When the source MME fails, it sends an SR request to the backup MME, and when the source MME is available, it sends an SR request to the source MME. In the figure, the backup MME is taken as an example for illustration.

2. The backup MME determines that the SGW-C and PGW-C associated with the terminal device are faulty, and then reselects SGW-C and PGW-C, which can simulate the terminal attachment process and send a session creation request to the newly selected SGW-C (for example: Create Session Request), the session creation request carries the first disaster tolerance data corresponding to the terminal device.

3. After receiving the session creation request, the newly selected SGW-C rebuilds the session with the surrounding entities according to the first disaster tolerance data, and takes over the bearer of the terminal device in the SGW-U. At the same time, a disaster recovery recovery request message is sent to the newly selected PGW-C, and the request message includes the first disaster recovery data.

After the newly selected PGW-C receives the request message, it rebuilds the session with the surrounding entities according to the first disaster recovery data, such as restoring the charging session with OCS, restoring the session with PCRF; take over the terminal equipment in PGW-U Of the bearer.

The sessions between the newly selected SGW-C and PGW-C and surrounding entities have been restored, and the bearer of the terminal equipment in the SGW-U and PGW-U has also been restored. PGW-C replies to SGW-C with a response message of successful recovery, and SGW-C replies with a response message of successful recovery to MME. MME can proceed with subsequent procedures, such as sending a service message to the newly selected SGW-C. The service message is used for The SGW-C is requested to establish a bearer between the access network device and the SGW-U to facilitate the transmission of downlink data or uplink data of the terminal device.

Please refer to FIG. 5, which is a schematic diagram of a first disaster tolerance data collection process proposed in an embodiment of this application. As shown in the figure, the first disaster tolerance data collection process includes but is not limited to steps S41-S45, which need to be explained Yes, in this embodiment, the first access and mobility management device is the source access and mobility management device. The first access and mobility management device in this embodiment is the same as the first access and mobility management device in the embodiment of FIG. 4 The objects referred to by the mobile management device may be different;

S41: The first access and mobility management device receives the attachment request of the terminal device.

Wherein, when the terminal is turned on, or after the terminal switches cells, the terminal device sends an attachment request to the first access and mobility management device through the access network device associated with the terminal device, and the attachment request may include the terminal The identification of the device, the identification of the terminal device may be the device code of the terminal device.

S42: The first access and mobility management device sends a third message to the first gateway control plane device according to the attachment request, where the third message includes second indication information and the terminal device identifier, and The second indication information is used to instruct the first gateway control plane device to send the first disaster tolerance data corresponding to the terminal device to the first access and mobility management device.

S43: The first gateway control plane device sends the identity of the first access and mobility management device and the identity of the terminal device to the gateway user plane device; the identity of the first access and mobility management device is used for the user plane of the gateway The device receives the downlink data corresponding to the terminal device, and acquires the first disaster tolerance data when the first gateway control plane device fails.

S44: The first gateway control plane device sends the first disaster tolerance data corresponding to the terminal device to the first access and mobility management device.

S45: The first access and mobility management device stores the first disaster tolerance data.

Among them, the first access and mobility management device receives the attachment request of the terminal device from the access network device, and sends a third message to the first gateway control plane device. The third message may be a session creation request (for example: Create Session Request) The third message may be an extended message. For example, the third message includes a newly-added private extension field, and the private extension field carries second indication information.

Optionally, the second indication information is used to instruct the first gateway control plane device to set the first disaster tolerance corresponding to the carried terminal device identifier when supporting the gateway device disaster tolerance method mentioned in the embodiment of this application. The data is sent to the first access and mobility management device, where the first disaster tolerance data may be included in the response message sent by the first gateway control plane device to the first access and mobility management device. The first access and mobility management device The device receives the response message sent by the first gateway control plane device, and stores the first disaster tolerance data included in the response message in the first access and mobility management device. The response message may be an extended message. For example, the response message may include a newly-added private extension field, and the private extension field is used to carry the first disaster tolerance data.

Further optionally, the first access and mobility management device may also back up the first disaster tolerance data corresponding to the terminal device to the third access and mobility management device, so that when the terminal device sends a service request, the first access If the access and mobility management device fails, the third access and mobility management device will perform access management and respond to the service request.

Optionally, the first disaster tolerance data may include, but is not limited to, key data such as the IP address of the terminal device, the gateway user plane device activated by the terminal device, and the like. The first disaster tolerance data is used when the first gateway control plane device fails. At this time, the second gateway control plane device resumes the session of the terminal device on the gateway user plane device. For details, please refer to the description of the foregoing embodiment, which will not be repeated here. Among them, the gateway user plane device may include, but is not limited to, PGW-U, UPF, and so on. The above-mentioned gateway user plane device activated by the terminal device means that the uplink data and downlink data corresponding to the terminal device are forwarded through the gateway user plane device.

Optionally, the third message may also include addressing information, which includes, but is not limited to, the identification of the first access and mobility management device or index information used to indicate the backup storage path of the first disaster tolerance data, etc. For example, the backup storage path of all disaster tolerance data whose index is 1 is from the access and mobility management device A to the access and mobility management device B and so on. When the first gateway control plane device determines to support the disaster recovery method of the gateway device mentioned in the embodiment of this application, it sends the addressing information and the identification of the terminal device to the gateway user plane device activated by the terminal device, and the gateway user The surface device stores the correspondence between the addressing information and the identification of the terminal device. In order to facilitate subsequent, when the gateway user plane device receives the downlink data corresponding to the terminal device, it can be determined according to the addressing information when it is determined that the first gateway control plane used to manage the terminal device’s session on the gateway user plane device is faulty. The first access and mobility management device, or when the first access and mobility management device fails, obtain the first disaster tolerance data corresponding to the terminal device through the addressing information. Please refer to the description of the embodiment in FIG. 6 for details. This will not be repeated here.

Optionally, the first access and mobility management device may include AMF, the first gateway control plane device may include SMF, and the gateway user plane device may include UPF, or the first access and mobility management device may include MME. The gateway control plane device may include SGW-C and PGW-C, and the gateway user plane device may include SGW-U and PGW-U. Please refer to Figure 7. The embodiment of this application illustrates as an example, both data centers DC1 and DC2 are deployed MME, SGW-C, PGW-C, SGW-U, PGW-U, online charging system OCS and policy control and rule function PCRF equipment, control plane equipment MME, SGW-C, PGW-C, OCS, MME and The PCRF is located in the DC, and the user plane devices SGW-U and PGW-U are located close to the user (for example, the province where the user is located). This embodiment includes the following steps:

1. The access network device sends an attachment request of the terminal device to the source MME;

2. The source MME sends a session creation request (for example: Create Session Request) to the SGW-C. The session creation request includes a private extension field, and the private extension field includes indication information. The indication information is used to inquire whether the SGW-C supports this application The disaster tolerance method provided in the embodiment, and when the disaster tolerance method provided in the embodiment of the present application is supported, the disaster tolerance data corresponding to the terminal device is sent to the MME.

3. The source SGW-C receives the session creation request, and if the SGW-C supports the disaster tolerance method of the embodiment of this application, it sends the source MME identification to the SGW-U, and the SGW-U saves the source MME identification; and the SGW-C Send a message to PGW-C. The message also contains a private extension field. The private extension field contains indication information. The indication information is used to inquire whether PGW-C supports the disaster tolerance method provided in the embodiments of this application and is supporting the implementation of this application. In the disaster recovery method provided in the example, the disaster recovery data corresponding to the terminal device is sent to the SGW-C.

4. The PGW-C receives the message sent by the SGW-C. If the PGW-C supports the disaster recovery method of the embodiment of this application, it will use the key data such as the PGW-U and IP address activated by the terminal device as the disaster recovery data, and pass the response message Sent to SGW-C, the response message also contains a private extension field, and the private extension field contains disaster tolerance data.

5. SGW-C receives the response message sent by PGW-C. If the response message carries disaster tolerance data corresponding to the terminal device, it means that PGW-C supports the disaster tolerance method provided in the embodiments of this application, and SGW-C sends The source MME sends a response message, and the response message also includes a private extension field, and the private extension field includes disaster tolerance data corresponding to the terminal device.

The source MME receives the response message returned by the SGW-C, and if the private extension field of the response message carries the disaster tolerance data corresponding to the terminal device, the disaster tolerance data is stored.

Further optionally, if the source MME has a cross-regional backup capability, the source MME may also store the disaster tolerance data across regions in another MME, that is, the backup MME.

Through the above steps S41-S45, the first disaster tolerance data corresponding to the terminal device is stored in the first access and mobility management device, and the subsequent terminal device can perform data transmission through the gateway user plane device.

The structure of the access and mobility management device and the gateway control plane device involved in the embodiment of the present application will be described below with reference to FIG. 10-15.

In the embodiment of the present invention, the first access and mobility management device communicates with the gateway control plane device (the first gateway control plane device, the second gateway control plane device, and the third gateway control plane device), the terminal device, and the access network device During the process, the operations performed by the first access and mobility management device side can be performed by the processing unit, the receiving unit, and the sending unit in the first access and mobility management device, where the receiving unit is used to perform the receiving in the process. Information (or message) operation, the sending unit is used to perform the operation of sending information (or message) in the process, and the processing unit is used to perform other operations in the process except the operations performed by the receiving unit and the sending unit . Optionally, the sending unit and the receiving unit are controlled by the processing unit, that is, the processing unit can respectively control the sending unit to perform the sending operation and the receiving unit to perform the receiving operation. In addition, the processing unit, the receiving unit, and the sending unit in the first access and mobility management device may be logical modules divided according to functions, or may be corresponding hardware modules. When the processing unit, the receiving unit, and the sending unit are all logical modules, the structure of the first access and mobility management device may be as shown in FIG. 10.

Among them, the receiving unit 1101 is configured to receive a service request from a terminal device;

The processing unit 1102 is configured to respond to the service request and determine that the first gateway control plane device is faulty, and then select a second gateway control plane device. The first gateway control plane device is used to manage the terminal device in the gateway user Face device session;

The sending unit 1103 is further configured to send a first message to the second gateway control plane device, where the first message includes first disaster tolerance data corresponding to the terminal device, and the first disaster tolerance data is used for Recovering the session of the terminal device in the gateway user plane device according to the first disaster tolerance data at the second gateway control plane device.

When the processing unit, receiving unit, and sending unit are all hardware modules, the processing unit can be specifically a processor, the receiving unit can be specifically a receiver, and the sending unit can be specifically a transmitter. The structure can be as shown in Figure 11.

Please refer to FIG. 11. FIG. 11 shows an access and mobility management device provided by an embodiment of the present application. The access and mobility management device 120 may include: one or more processors 1201, a memory 1202, and a transmitter 1203 , Receiver 1204. These components can be connected through a bus 1205 or other methods. FIG. 11 uses a bus connection as an example. among them:

The processor 1201 may be a general-purpose processor, such as a central processing unit (CPU), a digital signal processor (digital signal processing, DSP), an application specific integrated circuit (ASIC), or One or more integrated circuits configured to implement embodiments of the invention. The processor 1201 may process data received through the receiver 1204. The processor 1201 may also process data to be sent to the transmitter 1203.

The memory 1202 may be coupled with the processor 1201 through a bus 1205 or an input/output port, and the memory 1202 may also be integrated with the processor 1201. The memory 1202 is used to store various software programs and/or multiple sets of instructions. Specifically, the memory 1202 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory 1202 may also store a network communication program, which may be used to communicate with one or more additional devices, one or more terminals, and one or more network devices.

The transmitter 1203 may be used to transmit and process the signal output by the processor 1201. The receiver 1204 may be used for receiving and processing the received communication signal. In the access and mobility management device 120, the number of the transmitter 1203 and the receiver 1204 may each be one or more.

The processor 1201 can be used to read and execute computer readable instructions. Specifically, the processor 1201 may be used to call a program stored in the memory 1202, such as the implementation program of the gateway device disaster recovery method provided by one or more embodiments of the present application on the side of the first access and mobility management device, and The instructions contained in the program are executed to implement the methods involved in the subsequent embodiments. Optionally, when the processor 1201 sends any message or data, it specifically drives or controls the transmitter 1203 to send it. Optionally, when the processor 1201 receives any message or data, it specifically drives or controls the receiver 1204 to do the reception. Therefore, the processor 1201 can be regarded as a control center that performs transmission or reception, and the transmitter 1203 and the receiver 1204 are specific performers of the transmission and reception operations.

Among them, the receiver 1204 is used to receive a service request from a terminal device;

The processor 1201 is configured to respond to the service request and determine that the first gateway control plane device is faulty, and then select a second gateway control plane device. The first gateway control plane device is used to manage the terminal device in the gateway user plane device. Conversation

The transmitter 1203 is configured to send a first message to the second gateway control plane device, where the first message includes first disaster tolerance data corresponding to the terminal device, and the first disaster tolerance data is used for the The second gateway control plane device restores the session of the terminal device in the gateway user plane device according to the first disaster tolerance data.

It should be noted that the access and mobility management device 120 shown in FIG. 11 is only an implementation of the embodiment of the present application. In actual applications, the access and mobility management device 120 may also include more or fewer components. There is no restriction here.

In the embodiment of the present invention, during the communication process between the first gateway control plane device and other communication devices (such as the first access and mobility management device, the gateway user plane device, etc.), the operations performed on the first gateway control plane device side can be performed by The receiving unit, the processing unit, and the sending unit in the first gateway control plane device are executed, wherein the receiving unit is used to perform the operation of receiving information (or message) in the process, and the sending unit is used to perform the sending information in the process ( Or message) operation. Optionally, the sending unit and the receiving unit may be controlled by the processing unit, that is, the processing unit may respectively control the sending unit to perform the sending operation and the receiving unit to perform the receiving operation, and the sending unit and the receiving unit may not be controlled by the processing unit. In addition, the processing unit, the receiving unit, and the sending unit in the first gateway control plane device may be logical modules divided according to functions, or may be corresponding hardware modules. When the processing unit, the receiving unit, and the sending unit are all logical modules, the structure of the first gateway control plane device may be as shown in FIG. 12.

Wherein, the receiving unit 1301 is configured to receive a third message from the first access and mobility management device, the third message includes second indication information and an identifier of the terminal device, and the second indication information is used to indicate the second indication information. A gateway control plane device sends first disaster tolerance data corresponding to the terminal device to the first access and mobility management device, and the first disaster tolerance data is used to determine the first gateway control plane device Restore the session of the terminal device on the gateway user plane device in the event of a failure;

The processing unit 1302 is configured to parse the third message to obtain the second indication information and the identification of the terminal device;

The sending unit 1303 is configured to send the first disaster tolerance data to the first access and mobility management device.

When the processing unit, the receiving unit, and the sending unit are all hardware modules, the processing unit may be specifically a processor, the receiving unit may be specifically a receiver, and the sending unit may be specifically a transmitter. In this case, the structure of the first gateway control plane device may be As shown in Figure 13.

Please refer to FIG. 13, which shows a schematic diagram of the hardware structure of a first gateway control plane device provided by an embodiment of the present application. The gateway control plane device 140 may include: one or more processors 1401, a memory 1402, and a transmitting device. The receiver 1403 and the receiver 1404. These components can be connected through a bus 1405 or in other ways. FIG. 13 uses a bus connection as an example. among them:

The processor 1401 may be a general-purpose processor, such as a central processing unit (CPU), a digital signal processing (DSP), an application specific integrated circuit (ASIC), or One or more integrated circuits configured to implement embodiments of the invention. The processor 1401 may process data received through the receiver 1404. The processor 1401 may also process data to be sent to the transmitter 1403.

The memory 1402 may be coupled with the processor 1401 through a bus 1405 or an input/output port, and the memory 1402 may also be integrated with the processor 1401. The memory 1402 is used to store various software programs and/or multiple sets of instructions. Specifically, the memory 1402 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory 1402 may also store a network communication program, which may be used to communicate with one or more additional devices, one or more terminals, and one or more network devices.

The transmitter 1403 may be used to transmit and process the signal output by the processor 1401. The receiver 1404 may be used for receiving and processing the received communication signal. In the gateway control plane device 140, the number of the transmitter 1403 and the receiver 1404 may both be one or more.

The processor 1401 may be used to read and execute computer-readable instructions. Specifically, the processor 1401 may be used to call a program stored in the memory 1402, for example, the implementation program of the gateway device disaster recovery method provided by one or more embodiments of the present application on the first gateway control plane device side, and execute the program. The instructions contained in the program are used to implement the methods involved in the foregoing embodiments. Optionally, when the processor 1401 sends any message or data, it specifically drives or controls the transmitter 1403 to do the sending. Optionally, when the processor 1401 receives any message or data, it specifically drives or controls the receiver 1404 to do the reception. Therefore, the processor 1401 can be regarded as a control center that performs transmission or reception, and the transmitter 1403 and the receiver 1404 are specific performers of the transmission and reception operations.

Wherein, the receiver 1404 is configured to receive a third message from the first access and mobility management device, the third message includes second indication information and an identifier of the terminal device, and the second indication information is used to indicate the second indication information. A gateway control plane device sends first disaster tolerance data corresponding to the terminal device to the first access and mobility management device, and the first disaster tolerance data is used to determine the first gateway control plane device Restore the session of the terminal device on the gateway user plane device in the event of a failure;

The processor 1401 is configured to parse the third message to obtain the second indication information and the identification of the terminal device;

The transmitter 1403 is configured to send the first disaster tolerance data to the first access and mobility management device.

It should be noted that the gateway control plane device shown in FIG. 13 is only an implementation of the embodiment of the present application. In practical applications, the gateway control plane device 140 may also include more or fewer components, which is not limited here.

In the embodiment of the present invention, during the communication process between the second gateway control plane device and other communication devices (such as the first access and mobility management device), the operations performed by the second gateway control plane device side can be performed by the second gateway control plane device The receiving unit and the processing unit are used to perform the operation of receiving information (or message) in the process, and the processing unit is used to process the received message. Optionally, the receiving unit may be controlled by the processing unit, that is, the processing unit may control the receiving unit to perform the receiving operation, and the receiving unit may not be controlled by the processing unit. In addition, the processing unit and the receiving unit in the second gateway control plane device may be logical modules divided according to functions, or may be corresponding hardware modules. When the processing unit and the receiving unit are both logical modules, the structure of the second gateway control plane device may be as shown in FIG. 14.

Wherein, the receiving unit 1501 is configured to receive a first message from a first access and mobility management device, where the first message is when the first access and mobility management device receives a service request from a terminal device, and determines the first message Triggered when a gateway control plane device fails, the first message includes the first disaster tolerance data corresponding to the terminal device, and the first gateway control plane device is used to manage the terminal device in the gateway user plane device Conversation

The processing unit 1502 is configured to restore the session of the terminal device on the gateway user plane device according to the first disaster tolerance data.

Optionally, the second gateway control plane device may further include a sending unit for sending messages to other communication devices.

When the processing unit, receiving unit, and sending unit are all hardware modules, the processing unit can be specifically a processor, the receiving unit can be specifically a receiver, and the sending unit can be specifically a transmitter. The structure can be as shown in Figure 15.

Please refer to FIG. 15. FIG. 15 shows a second gateway control plane device provided by an embodiment of the present application. The second gateway control plane device 160 may include: one or more processors 1601, a memory 1602, and a transmitter 1603. , Receiver 1604. These components can be connected through a bus 1605 or in other ways. FIG. 15 uses a bus connection as an example. among them:

The processor 1601 may be a general-purpose processor, such as a central processing unit (CPU), a digital signal processing (DSP), an application specific integrated circuit (ASIC), or One or more integrated circuits configured to implement embodiments of the invention. The processor 1601 may process data received through the receiver 1604. The processor 1601 may also process data to be sent to the transmitter 1603.

The memory 1602 may be coupled with the processor 1601 through a bus 1605 or an input/output port, and the memory 1602 may also be integrated with the processor 1601. The memory 1602 is used to store various software programs and/or multiple sets of instructions. Specifically, the memory 1602 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory 1602 may also store a network communication program, which may be used to communicate with one or more additional devices, one or more terminals, and one or more network devices.

The transmitter 1603 may be used to transmit and process the signal output by the processor 1601. The receiver 1604 may be used for receiving and processing the received communication signal. In the second gateway control plane device 160, the number of transmitters 1603 and receivers 1604 may each be one or more.

The processor 1601 can be used to read and execute computer readable instructions. Specifically, the processor 1601 may be used to call a program stored in the memory 1602, such as the implementation program on the second gateway control plane device side of the gateway device disaster recovery method provided in one or more embodiments of the present application, and execute the program. The instructions contained in the program are used to implement the methods involved in the foregoing embodiments. Optionally, when the processor 1601 sends any message or data, it specifically drives or controls the transmitter 1603 to do the sending. Optionally, when the processor 1601 receives any message or data, it specifically drives or controls the receiver 1604 to do the reception. Therefore, the processor 1601 can be regarded as a control center that performs transmission or reception, and the transmitter 1603 and the receiver 1604 are specific performers of the transmission and reception operations.

Wherein, the receiver 1604 is configured to receive a first message from a first access and mobility management device, where the first message is when the first access and mobility management device receives a service request from a terminal device, and determines the first message Triggered when a gateway control plane device fails, the first message includes the first disaster tolerance data corresponding to the terminal device, and the first gateway control plane device is used to manage the terminal device in the gateway user plane device Conversation

The processor 1601 is configured to restore the session of the terminal device on the gateway user plane device according to the first disaster tolerance data.

It should be noted that the access and mobility management device 160 shown in FIG. 15 is only an implementation of the embodiment of the present application. In actual applications, the access and mobility management device 160 may also include more or fewer components. There is no restriction here.

Referring to FIG. 16, FIG. 16 shows a schematic structural diagram of a communication chip provided by the present application. As shown in FIG. 16, the communication chip 170 may include a processor 1701, and one or more interfaces 1702 coupled to the processor 1701. among them:

The processor 171 can be used to read and execute computer-readable instructions. In specific implementation, the processor 1701 may mainly include a controller, an arithmetic unit, and a register. Among them, the controller is mainly responsible for the instruction decoding, and sends out control signals for the operation corresponding to the instruction. The arithmetic unit is mainly responsible for performing fixed-point or floating-point arithmetic operations, shift operations and logic operations, etc., and can also perform address operations and conversions. The register is mainly responsible for storing the register operands and intermediate operation results temporarily stored during the execution of the instruction. In specific implementation, the hardware architecture of the processor 1701 may be an application specific integrated circuit (ASIC) architecture, MIPS architecture, ARM architecture, or NP architecture, etc. The processor 1701 may be single-core or multi-core.

The interface 1702 can be used to input data to be processed to the processor 1701, and can output the processing result of the processor 1501 to the outside. For example, the interface 1702 may be a general purpose input output (GPIO) interface, and may be connected to multiple peripheral devices (such as a display (LCD), a camera (camara), a radio frequency (RF) module, etc.). The interface 172 is connected to the processor 1701 through the bus 1703.

In this application, the processor 1701 may be used to call the method for disaster recovery of a gateway device provided by one or more embodiments of this application from a memory on the side of the communication device (the first access and mobility management device, the first gateway control plane device) Or the implementation program of the second gateway control plane device), and execute the instructions contained in the program. The interface 1702 may be used to output the execution result of the processor 1701. For the method for disaster recovery of the gateway device provided by one or more embodiments of the present application, reference may be made to the foregoing method embodiment, which will not be repeated here.

It should be noted that the respective functions of the processor 1701 and the interface 1702 may be implemented through hardware design, or through software design, or through a combination of software and hardware, which is not limited here.

In another embodiment of the present application, a readable storage medium is also provided. The readable storage medium stores computer execution instructions. When a device (may be a single-chip microcomputer, a chip, etc.) or a processor calls the readable storage medium The stored computer executes instructions to implement the steps performed by the first access and mobility management device, the first gateway control plane device, or the second gateway control plane device in the gateway device disaster recovery method provided in FIGS. 4-6. The aforementioned readable storage medium may include: U disk, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk, and other media that can store program codes.

In another embodiment of the present application, a computer program product is also provided. The computer program product includes computer-executable instructions, and the computer-executable instructions are stored in a computer-readable storage medium; at least one processor of the device can be accessed from a computer. Read the storage medium to read the computer execution instructions, and implement the first access and mobility management device, the first gateway control plane device, or the second gateway control plane device in the gateway device disaster recovery method provided in Figures 4-6. A step of.

The terms "first", "second", "third" and "fourth" in the specification and claims of the application and the drawings are used to distinguish different objects, rather than describing a specific order . In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units not listed, or optionally includes Other steps or units inherent in these processes, methods, products or equipment.

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

Finally, it should be noted that the above are only specific implementations of this application, but the scope of protection of this application is not limited to this. Any changes or substitutions within the technical scope disclosed in this application shall be covered by this application. Within the scope of protection applied for. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

A method for disaster recovery of gateway equipment, characterized in that it comprises:

The first access and mobility management device receives the service request of the terminal device;

In response to the service request, the first access and mobility management device determines that the first gateway control plane device is faulty, and then selects the second gateway control plane device. The first gateway control plane device is used to manage the terminal device The session of the gateway user plane device;

The first access and mobility management device sends a first message to the second gateway control plane device, where the first message includes first disaster tolerance data corresponding to the terminal device, and the first disaster tolerance data The second gateway control plane device is used for restoring the session of the terminal device in the gateway user plane device according to the first disaster tolerance data.
The method according to claim 1, wherein the first message is a session creation request or a service message; the service message is used to request the second gateway control plane device to establish the connection between the gateway user plane device and the gateway user plane device. The bearer between the access network equipment associated with the terminal equipment.
The method according to claim 1 or 2, wherein before the first access and mobility management device receives a service request from a terminal device, the method further comprises:

The first access and mobility management device receives a second message from a third gateway control plane device, where the second message is that the gateway user plane device receives downlink data corresponding to the terminal device, and determines the When the first gateway control plane device fails, the third gateway control plane device is triggered to send, the second message includes first indication information, and the first indication information is used to indicate the first access and mobility management The device sends a paging message to the terminal device;

The first access and mobility management device sends a paging message to the terminal device according to the first indication information, where the paging message is used to trigger the terminal device to send the service request.
The method of claim 3, wherein the second message further includes addressing information associated with the first disaster tolerance data, and the addressing information is used to obtain information about the first disaster tolerance data. Backup storage location; the method further includes:

The first access and mobility management device obtains first disaster tolerance data corresponding to the terminal device according to the addressing information, and the first disaster tolerance data further includes the identification of the access network device associated with the terminal device ；

The first access and mobility management device sending a paging message to the terminal device according to the first indication information includes:

The first access and mobility management device sends a paging message to the terminal device through the access network device according to the first indication information.
The method according to claim 1, wherein before the first access and mobility management device receives a service request from a terminal device, the method further comprises:

Receiving, by the first access and mobility management device, the attachment request of the terminal device;

The first access and mobility management device sends a third message to the first gateway control plane device according to the attachment request, and the third message includes second indication information and the identification of the terminal device. The second indication information is used to instruct the first gateway control plane device to send the first disaster tolerance data corresponding to the terminal device to the first access and mobility management device;

Receiving, by the first access and mobility management device, the first disaster tolerance data from the first gateway control plane device;

The first access and mobility management device stores the first disaster tolerance data.
The method of claim 5, wherein the method further comprises:

The first access and mobility management device backs up the first disaster tolerance data to the second access and mobility management device.
A method for disaster recovery of gateway equipment, characterized in that it comprises:

The first gateway control plane device receives a third message from the first access and mobility management device. The third message includes second indication information and an identifier of the terminal device. The second indication information is used to indicate the first gateway The control plane device sends the first disaster tolerance data corresponding to the terminal device to the first access and mobility management device, where the first disaster tolerance data is used when determining that the first gateway control plane device is faulty Resume the session of the terminal device on the gateway user plane device;

The first gateway control plane device sends the first disaster tolerance data to the first access and mobility management device.
8. The method of claim 7, wherein the third message further includes addressing information associated with the first disaster tolerance data; the method further includes:

The first gateway control plane device sends the addressing information and the identification of the terminal device to the gateway user plane device, and the addressing information is used to communicate with the terminal device when the gateway user plane device receives Corresponding downlink data, and the first disaster tolerance data is acquired when the first gateway control plane device fails.
A method for disaster recovery of gateway equipment, characterized in that it comprises:

The second gateway control plane device receives the first message from the first access and mobility management device, the first message is when the first access and mobility management device receives the service request of the terminal device, and determines the first gateway Triggered when a control plane device fails, the first message includes first disaster tolerance data corresponding to the terminal device, and the first gateway control plane device is used to manage the terminal device's session on the gateway user plane device ；

The second gateway control plane device restores the session of the terminal device in the gateway user plane device according to the first disaster tolerance data.
The method according to claim 9, wherein the first message is a session creation request or a service message; the service message is used to request the second gateway control plane device to establish a connection between the gateway user plane device and the gateway user plane device. The bearer between the access network equipment associated with the terminal equipment.
An access and mobility management device, wherein the access and mobility management device is a first access and mobility management device, and the first access and mobility management device includes a receiving unit, a processing unit, and a sending unit ,among them:

The receiving unit is configured to receive a service request from a terminal device;

The processing unit is configured to respond to the service request and determine that the first gateway control plane device is faulty, and then select a second gateway control plane device. The first gateway control plane device is used to manage the terminal device in the gateway user plane. Device session;

The sending unit is further configured to send a first message to the second gateway control plane device, where the first message includes first disaster tolerance data corresponding to the terminal device, and the first disaster tolerance data is used for The second gateway control plane device restores the session of the terminal device in the gateway user plane device according to the first disaster tolerance data.
The access and mobility management device according to claim 11, wherein the first message is a session creation request or a service message; the service message is used to request the second gateway control plane device to establish the gateway The bearer between the user plane device and the access network device associated with the terminal device.
The access and mobility management device according to claim 11 or 12, wherein:

The receiving unit is further configured to receive a second message from a third gateway control plane device, where the second message is that the gateway user plane device receives downlink data corresponding to the terminal device, and determines the first gateway When the control plane device fails, the third gateway control plane device is triggered to send, the second message includes first indication information, and the first indication information is used to instruct the first access and mobility management device to send the The terminal device sends a paging message;

The sending unit is further configured to send a paging message to the terminal device according to the first indication information, where the paging message is used to trigger the terminal device to send the service request.
The access and mobility management device according to claim 13, wherein the second message further includes addressing information associated with the first disaster tolerance data, and the addressing information is used to obtain the second 1. Backup storage location of disaster recovery data;

The processing unit is further configured to obtain first disaster tolerance data corresponding to the terminal device according to the addressing information, and the first disaster tolerance data further includes the identifier of the access network device associated with the terminal device;

The sending unit is further configured to send a paging message to the terminal device through the access network device according to the first indication information.
The access and mobility management device according to claim 11, wherein:

The receiving unit is further configured to receive an attachment request of the terminal device;

The sending unit is further configured to send a third message to the first gateway control plane device according to the attachment request, where the third message includes second indication information and the identification of the terminal device, and the second indication Information used to instruct the first gateway control plane device to send the first disaster tolerance data corresponding to the terminal device to the first access and mobility management device;

The receiving unit is further configured to receive the first disaster tolerance data from the first gateway control plane device;

The processing unit is also used to store the first disaster tolerance data.
The access and mobility management device according to claim 15, wherein:

The sending unit is also used to back up the first disaster tolerance data to a second access and mobility management device.
A gateway control plane device, wherein the gateway control plane device is a first gateway control plane device, and the first gateway control plane device includes a receiving unit and a sending unit, wherein:

The receiving unit is configured to receive a third message from a first access and mobility management device, the third message includes second indication information and an identifier of the terminal device, and the second indication information is used to indicate the first The gateway control plane device sends the first disaster tolerance data corresponding to the terminal device to the first access and mobility management device, and the first disaster tolerance data is used to determine the failure of the first gateway control plane device. Resume the session of the terminal device on the gateway user plane device at the time;

The sending unit sends the first disaster tolerance data to the first access and mobility management device.
The gateway control plane device of claim 17, wherein the third message further includes addressing information associated with the first disaster tolerance data;

The sending unit is further configured to send the addressing information and the identification of the terminal device to the gateway user plane device, and the addressing information is used to receive the address information corresponding to the terminal device on the gateway user plane device. And obtain the first disaster tolerance data when the first gateway control plane device fails.
A gateway control plane device, wherein the gateway control plane device is a second gateway control plane device, and the second gateway control plane device includes a receiving unit and a processing unit, wherein:

The receiving unit is configured to receive a first message from a first access and mobility management device, where the first message is when the first access and mobility management device receives a service request from a terminal device, and determines the first Triggered when the gateway control plane device fails, the first message includes the first disaster tolerance data corresponding to the terminal device, and the first gateway control plane device is used to manage the terminal device's access to the gateway user plane device. Conversation

The processing unit is configured to restore the session of the terminal device on the gateway user plane device according to the first disaster tolerance data.
The gateway control plane device according to claim 19, wherein the first message is a session creation request or a service message; the service message is used to request the second gateway control plane device to establish the gateway user plane The bearer between the device and the access network device associated with the terminal device.
A communication system, characterized by comprising a first access and mobility management device, a first gateway control plane device, and a second gateway control plane device, wherein the first access and mobility management device is according to claim 11- The access and mobility management device according to any one of 16, the first gateway control plane device is the gateway control plane device according to claim 17 or 18, and the second gateway control plane device is claim 19 or 20 The gateway control plane device.
A computer storage medium, characterized in that instructions are stored on the computer storage medium, and when the instructions run on a processor, the processor executes claims 1 to 6 or claims 7 to 8 or rights. The method for disaster recovery of gateway equipment described in any one of claims 9 to 10.