CN112543468B - Disaster recovery method for gateway equipment and communication equipment - Google Patents

Disaster recovery method for gateway equipment and communication equipment Download PDF

Info

Publication number
CN112543468B
CN112543468B CN201910901318.XA CN201910901318A CN112543468B CN 112543468 B CN112543468 B CN 112543468B CN 201910901318 A CN201910901318 A CN 201910901318A CN 112543468 B CN112543468 B CN 112543468B
Authority
CN
China
Prior art keywords
access
gateway
gateway control
message
equipment
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201910901318.XA
Other languages
Chinese (zh)
Other versions
CN112543468A (en
Inventor
黄泽旭
周军平
林玮健
钱涛
徐日东
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201910901318.XA priority Critical patent/CN112543468B/en
Priority to PCT/CN2020/115066 priority patent/WO2021057526A1/en
Publication of CN112543468A publication Critical patent/CN112543468A/en
Application granted granted Critical
Publication of CN112543468B publication Critical patent/CN112543468B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition

Landscapes

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

Abstract

The embodiment of the application provides a method for disaster recovery of gateway equipment and communication equipment, wherein the method for disaster recovery of the gateway equipment comprises the following steps: the first access and mobile management equipment receives a service request of the terminal equipment; the first access and mobile management equipment responds to the service request, determines that the first gateway control panel equipment fails, and selects second gateway control panel equipment, wherein the first gateway control panel equipment is used for managing the session of the terminal equipment on gateway user panel equipment; the first access and mobile management device sends a first message to the second gateway control surface device, the first message includes first disaster tolerance data corresponding to the terminal device, and the first disaster tolerance data is used by the second gateway control surface device to recover the session of the terminal device on the gateway user surface device according to the first disaster tolerance data. By adopting the embodiment of the application, the complexity of the session recovery can be simplified, the reliability of the session recovery can be improved, the resource utilization rate can be improved, and the cost can be reduced.

Description

Disaster recovery method for gateway equipment and communication equipment
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method for disaster recovery of a gateway device and a communication device.
Background
In the prior art, based on the concept of separation of a control plane and a user plane, a network architecture includes a gateway control plane device and a gateway user plane device, and the gateway control plane device is usually used as a session management functional entity to implement access and management of a session and select a gateway user plane device for a terminal device. When the gateway control plane device selects the gateway user plane device for the terminal device, the gateway control plane device manages the session of the terminal device in the gateway user plane device, such as flow monitoring, charging, and the like.
In order to ensure that a system can still maintain a session when a gateway control surface device fails, at present, a gateway control surface device usually adopts a master-slave mode, that is, a spare gateway control surface device is deployed for a master gateway control surface device, the spare gateway control surface device does not issue a route of a service network Protocol (IP) address to the outside, only receives session information backed up by the master gateway control surface device, and switches all sessions of the master control surface device to the spare gateway control surface device through control of a certain centralized control node after the master gateway control surface device fails, so that the spare gateway control surface device provides services. In this way, the standby gateway control plane device does not participate in service processing, the resource utilization rate is low, and a centralized control node is also needed for fault monitoring and control switching operation, so that the cost is high. After the primary control plane device fails, a large number of sessions need to be recovered, the recovery process is complex, and the standby control plane device has a risk of session recovery failure.
Disclosure of Invention
The embodiment of the application provides a method for disaster recovery of gateway equipment and communication equipment, which can simplify the complexity of session recovery, improve the reliability of session recovery, improve the resource utilization rate and reduce the cost.
In a first aspect, an embodiment of the present application provides a method for disaster recovery of a gateway device, where the method is applied to a first access and mobile management device, and the method includes: the first access and mobile management equipment receives a service request of the terminal equipment.
The first access and mobility management device may be a source access and mobility management device associated with the terminal device, or may be a backup access and mobility management device that determines a failure of the source access and mobility management device and reselects when the terminal device sends a service request, or may be an access and mobility management device that is randomly selected when a third gateway control plane device determines a failure of the source access and mobility management device when downlink data of the terminal device exists, where the third gateway control plane device is a gateway control plane device that is selected when a gateway user plane device determines a failure of the first gateway control plane device associated with the terminal device. Optionally, the first disaster recovery data may also be backed up and stored in the backup mobile access and mobile management device, and for the definition of the source access and mobile management device and the backup access and mobile management device, reference is made to the description of the subsequent embodiment, which is not repeated herein.
Optionally, the service request may be triggered when the terminal device sends uplink data, or may also be triggered when downlink data of the terminal device exists, and the terminal device sends the service request by sending a paging message.
And the first access and mobile management equipment responds to the service request, determines that the first gateway control plane equipment for managing the session of the terminal equipment on the gateway user plane equipment has a fault, and selects the second gateway control plane equipment. The selection mode of the first access and mobility management device selecting the second gateway control plane device may be randomly selected or selected based on a specific protocol rule.
The first access and mobile management device sends a first message to the selected second gateway control surface device, wherein the first message comprises first disaster tolerance data corresponding to the terminal device, and the first disaster tolerance data is used for the second gateway control surface device to recover the session of the terminal device on the gateway user surface device according to the first disaster tolerance data.
Optionally, the first disaster recovery data may include, but is not limited to, an IP address of the terminal device, key data such as a gateway user plane device activated by the terminal device, and the like.
Correspondingly, the second gateway control plane device receives the first disaster recovery data, and recovers the session of the terminal device on the gateway user plane device according to the first disaster recovery data.
By implementing the embodiment, the first access and mobile management device stores the first disaster recovery data corresponding to the terminal device, and a control panel device is not required to be additionally arranged for backup storage of the first disaster recovery data, so that the cost is reduced, and the resource utilization rate is improved. In addition, the first access and mobile management equipment directly sends the first disaster recovery data to the newly selected second gateway control surface equipment to recover the session of the terminal equipment on the gateway user surface equipment, a control node is not required to be additionally configured to control the session recovery, the complexity of the session recovery is simplified, the session recovery is carried out when the terminal equipment has service requirements, the second control surface equipment is not required to simultaneously recover a large number of sessions, and the reliability of the session recovery is improved.
In a possible design, the first message may be a create session request or a service message, and if the first message is the create session request, the first access and mobility management device simulates a terminal device attach procedure, and sends the first disaster recovery data to the second gateway control plane device through the create session request. After the second gateway control surface device completes the session recovery of the terminal device on the gateway user surface device, the first access and mobile management device sends a service message to the second gateway control surface device so as to establish a bearer between the gateway user surface device and the access network device associated with the terminal device.
And if the first message is a service message, the first access and mobile management equipment and the second gateway control surface equipment realize the transmission of the first disaster tolerance data to the second gateway control surface equipment through service message interaction, and the service message is used for requesting the second gateway control surface equipment to establish the load between the gateway user surface equipment and the access network equipment associated with the terminal equipment. When detecting that there is no session context corresponding to the terminal device, the second gateway control plane device completes session recovery of the terminal device on the gateway user plane device through the first disaster recovery data, and then controls establishment of a bearer between the gateway user plane device and an access network device associated with the terminal device.
By implementing the embodiment, if the first message is the request for creating the session, the reliability of session recovery can be improved, and if the first message is the service message, the efficiency of service 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 a second message from the third gateway control plane device, where the second message is sent by triggering the third gateway control plane device when the gateway user plane device receives downlink data corresponding to the terminal device and determines that the first gateway control plane device fails, and the second message may include first indication information used for indicating 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 fails, 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 identifier of the source access and mobility management device to the third gateway control plane device. Optionally, the identifier of the source access and mobility management device may be sent by way of addressing information, where the addressing information may include, but is not limited to, the identifier of the source access and mobility management device, or index information used to indicate a backup storage path of the first disaster recovery data, and the like, for example, all backup storage paths of the disaster recovery data with an index of 1 are backed up from the access and mobility management device a to the access and mobility management device B, and the source access and mobility management device may also be determined by the index information.
When determining that the source access and mobility management device is available, the third gateway control surface device sends a second message (in the application scenario, the first access and mobility management device is the source access and mobility management device) to the source access and mobility management device, and if determining that the source access and mobility management device is failed, randomly selects one access and mobility management device, and sends the second message to the randomly selected access and mobility management device (in the application scenario, the first access and mobility management device is the randomly selected access and mobility management device).
The source access and mobility management device stores first disaster recovery data corresponding to the terminal device in a terminal attachment process.
And the first access and mobile management equipment (source access and mobile management equipment or randomly selected access and mobile management equipment) sends a paging message to the terminal equipment according to the first indication information, and the terminal equipment sends a service request to the first access and mobile management equipment after receiving the paging message.
In a possible design, if the 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 recovery data, and therefore, the second message sent by the third gateway control plane device to the first access and mobility management device further includes addressing information associated with the first disaster recovery data, and the backup storage location of the first disaster recovery data can be obtained through the addressing information.
And the first access and mobile management equipment acquires first disaster tolerance data corresponding to the terminal equipment according to the addressing information, wherein the first disaster tolerance data also comprises an identifier of access network equipment associated with the terminal equipment. 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 above embodiment, the addressing information associated with the first disaster recovery data is stored in the gateway user plane device in advance.
By implementing the 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 one possible design, before the first access and mobility management device receives the service request of the terminal device, the terminal device sends an attach request to the first access and mobility management device. The first access and mobile management device receives the attach request and sends a third message to the first gateway control surface device, where the third message may be a request for creating a session, and 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 gateway control surface device to send first disaster recovery data corresponding to the terminal device to the first access and mobile management device.
Correspondingly, the first gateway control surface device sends the first disaster recovery data corresponding to the terminal device to the first access and mobile management device, and the first access and mobile management device stores the first disaster recovery data.
By implementing the embodiment, the first disaster recovery data can be stored in the first access and mobile management device, and the gateway control panel device does not need to be additionally arranged to independently backup and store the first disaster recovery data, so that the cost can be saved, and the resource utilization rate can be improved.
In one possible design, the first access and mobility management device may also backup the first disaster recovery data to the second access and mobility management device.
By implementing the embodiment, the first disaster recovery data can be still addressed when the first access and mobile management equipment fails, and the session recovery is completed.
In a second aspect, a method for gateway device disaster recovery is provided in an embodiment of the present application, and is applied to a first gateway control plane device, where the first gateway control plane device receives a third message from a first access and mobility management device, where the third message includes second indication information and an identifier of a terminal device, the second indication information is used to indicate the first gateway control plane device to send first disaster recovery data corresponding to the terminal device to the first access and mobility management device, and the first disaster recovery data is used to recover a session of the terminal device at a gateway user plane device when it is determined that the first gateway control plane device fails.
The first gateway control surface device sends the first disaster recovery data to the first access and mobile management device. The first disaster recovery data includes, but is not limited to, an IP address of the terminal device and a gateway user plane device activated for the terminal device, where the activated gateway user plane device refers to the gateway user plane device and is used to forward uplink data or downlink data of the terminal device.
By implementing the embodiment, the first gateway control plane device sends the first disaster recovery data to the first access and mobile management device for storage, so that the cost can be saved and the resource utilization rate can be improved.
In a possible design, the third message may further include addressing information associated with the first disaster recovery data, where the addressing information includes, but is not limited to, an identifier of the first access and mobile management device, or index information used to indicate a backup storage path of the first disaster recovery data, for example, all backup storage paths of the disaster recovery data with index 1 are backed up from the access and mobile management device a to the access and mobile management device B, and the source access and mobile management device may also be determined by the index information. The addressing information can determine not only the first access and mobility management device, but also the location for backup storage of the first disaster recovery data.
The first gateway control surface device sends addressing information and an identifier of the terminal device to the gateway user surface device, and when the subsequent gateway user surface device receives downlink data corresponding to the terminal device and determines that the first gateway control surface device fails, the addressing information can be sent to a randomly selected third gateway control surface device so as to obtain the first disaster recovery data.
By implementing the 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 conveniently, and the first disaster recovery data can still be addressed when the first gateway control plane device is determined to be in failure.
In a third aspect, an embodiment of the present application provides a method for disaster recovery of a gateway device, where the method is applied to a second gateway control plane device, and the method includes: the second gateway control surface device receives a first message from the first access and mobile management device, the first message is triggered when the first access and mobile management device receives a service request of the terminal device and determines that the first gateway control surface device fails, the first message comprises first disaster tolerance data corresponding to the terminal device, and the first gateway control surface device is used for managing a session of the terminal device on a gateway user surface device.
And the second gateway control panel equipment recovers the session of the terminal equipment on the gateway user plane equipment according to the first disaster recovery data.
By implementing the embodiment, the second gateway control plane device can recover the session of the terminal device on the gateway user plane device through simple message interaction, and the recovery flow is simple.
In one possible design, the first message is a create session 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. Please refer to the description of the embodiment of the first aspect, which is not repeated herein.
In a fourth aspect, an embodiment of the present application provides an access and mobility management device, where the access and mobility management device is a first access and mobility management device, and the first access and mobility management device may include a plurality of functional modules or units, and is configured to correspondingly execute the method for disaster recovery of a gateway device provided in the first aspect.
In a fifth aspect, an embodiment of the present application provides a gateway control plane device, where the gateway control plane device is a first gateway control plane device, and the first gateway control plane device may include a plurality of functional modules or units, and is used to correspondingly execute the method for disaster recovery of the gateway device provided in the second aspect.
In a sixth aspect, an embodiment of the present application provides a gateway control plane device, where the gateway control plane device is a second gateway control plane device, and the second gateway control plane device may include a plurality of functional modules or units, and is configured to correspondingly execute the method for disaster recovery of the gateway device provided in the third aspect.
In a seventh aspect, an embodiment of the present application provides an access and mobility management device, where the access and mobility management device is a first access and mobility management device, and the first access and mobility management device is configured to execute the method for disaster recovery of a gateway device provided in the first aspect. The first access and mobility management device may include: memory, processor, transmitter, receiver, wherein: the transmitter and receiver are used to communicate with other communication devices. The memory is used for storing implementation codes of the method for disaster recovery of the gateway device provided by the first aspect, and the processor is used for executing the program codes stored in the memory, that is, executing the method for disaster recovery of the gateway device provided by the first aspect.
In an eighth aspect, an embodiment of the present application provides a gateway control plane device, where the gateway control plane device is a first gateway control plane device, and is configured to execute the method for disaster recovery of a gateway device provided in the second aspect. The first gateway control plane device may include: memory, processor, transmitter, receiver, wherein: the transmitter and receiver are used to communicate with other communication devices. The memory is used for storing the implementation code of the disaster recovery of the gateway device provided by the second aspect, and the processor is used for executing the program code stored in the memory, that is, executing the method of the disaster recovery of the gateway device provided by the second aspect.
In a ninth aspect, an embodiment of the present application provides a gateway control plane device, where the gateway control plane device is a second gateway control plane device, and is configured to execute the method for disaster recovery of a gateway device provided in the third aspect. The second gateway control plane device may comprise: memory, processor, transmitter, receiver, wherein: the transmitter and receiver are used to communicate with other communication devices. The memory is used for storing the implementation code of the disaster recovery of the gateway device provided by the third aspect, and the processor is used for executing the program code stored in the memory, that is, executing the method of the disaster recovery of the gateway device provided by the third aspect.
In a tenth aspect, an embodiment of the present application provides a communication system, including: the first gateway control plane device is connected with the first access and mobile management device. Wherein:
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 fifth aspect, or may be the gateway control plane device described in the eighth aspect.
The second gateway control plane device may be the gateway control plane device described in the above sixth aspect, or may be the gateway control plane device described in the above ninth aspect.
In an eleventh aspect, the present application provides a communication chip, which may include: a processor, and one or more interfaces coupled to the processor. The processor may be configured to call, from the memory, an implementation program of the method for disaster recovery of a gateway device provided in any one of the first aspect to the third aspect, and execute instructions included in the implementation program. The interface may be used to output a data processing result of the processor or to retrieve the implementation program from a memory.
In a twelfth aspect, an embodiment of the present application provides a computer-readable storage medium, which has instructions stored thereon, and when the computer-readable storage medium is executed on a processor, causes the processor to execute the method for disaster recovery of a gateway device described in any of the first to third aspects.
In a thirteenth aspect, an embodiment of the present application provides a computer program product including instructions, which when executed on a processor, causes the processor to perform the method for disaster recovery of a gateway device described in any of the first to third aspects.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments or the background art of the present application, the drawings required to be used in the embodiments or the background art of the present application will be described below.
Fig. 1 is a schematic architecture diagram of a wireless communication system according to an embodiment of the present application;
FIG. 2 is an alternative system architecture diagram provided by embodiments of the present application;
FIG. 3 is another alternative system architecture diagram provided in embodiments 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 recovery data collection process according to an embodiment of the present application;
fig. 6 is a flowchart of a downlink data transmission paging process according to an embodiment of the present application;
fig. 7 is an optional disaster recovery data collection scenario diagram according to an embodiment of the present application;
fig. 8 is a scenario diagram of a gateway device disaster tolerance provided in an embodiment of the present application;
fig. 9 is a diagram of a downlink data transmission paging scenario provided in an embodiment of the present application;
fig. 10 is a functional block diagram of an access and mobility management device according to an embodiment of the present application;
fig. 11 is a schematic hardware structure diagram of an access and mobility management device according to an embodiment of the present application;
fig. 12 is a functional block diagram of a gateway control plane device according to an embodiment of the present application;
fig. 13 is a schematic hardware structure diagram of a gateway control plane according to an embodiment of the present application;
fig. 14 is a functional block diagram of another gateway control plane device provided in an embodiment of the present application;
fig. 15 is a schematic hardware structure diagram of another gateway control plane provided in an embodiment of the present application;
fig. 16 is a schematic structural diagram of a communication chip according to an embodiment of the present application.
Detailed Description
The terminology used in the description of the embodiments section of the present application is for the purpose of describing particular embodiments of the present application only and is not intended to be limiting of the present 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 embodiment of the present application may include, but are not limited to, a Mobility Management Entity (MME), an access and Mobility Management Entity (AMF) in a 5G communication system, and the like. The entity in the embodiment of the present application may be understood as a hardware device.
The first Gateway Control surface device, the second Gateway Control surface device, and the third Gateway Control surface device in the embodiment of the present application include, but are not limited to, a Control surface PDN Gateway (PDN Gateway for Control plane, PGW-C), a Control surface Serving Gateway (SGW-C), and a session management function entity (SMF) in a 5G communication system, which is not limited in this application.
The Gateway User plane device in the embodiment of the present application includes, but is not limited to, a User plane PDN Gateway (PDN Gateway for User plane, PGW-U), a User plane Serving Gateway (SGW-U), and a (User plane function, UPF) User plane function entity in a 5G communication system, and the like.
The gateway control plane device of the embodiment of the present application may include one device or a set of multiple devices, for example, one gateway control plane device may include a PGW-C and an SGW-C, or one gateway control plane device may include an SMF, and the like.
The gateway user plane device of the embodiment of the present application may include one device or a set of multiple devices, for example, one gateway user plane device may include a PGW-U and an SGW-U, or one gateway user plane device may include a UPF, and the like.
The source access and mobility management device mentioned in the embodiment of the present application may refer to an access and mobility management device determined in a terminal attachment process, where the source access and mobility management device stores first disaster recovery data corresponding to the terminal device. The backup access and mobile management device in the embodiment of the present application may refer to an access and mobile management device for backing up and storing the first disaster recovery data. The source access and mobile management equipment and the backup access and mobile management equipment have a corresponding relation, and the backup access and mobile management equipment can be addressed through the identifier of the source access and mobile management equipment.
The first, second and third embodiments of the present application are to distinguish different objects in the same scene, and different objects in different scenes may have the same name, for example, in a first application scene, the source access and mobility management device is referred to as a first access and mobility management device, and in a second application scene, the backup access and mobility management device is referred to as a first access and mobility management device, and so on.
The first gateway control plane device associated with the terminal device in the embodiments of the present application may refer to a device for managing a session of the terminal device in a gateway user plane device.
The gateway user plane device associated with the terminal device 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 in the embodiment of the present application may refer to that the terminal device is in a cell under the access network device.
Fig. 1 is a schematic diagram of an architecture of a wireless communication system according to an embodiment of the present disclosure. The wireless communication system 100 includes, but is not limited to: terminal equipment 101, access Network (AN) equipment 102, gateway user plane equipment 103, gateway control plane equipment 104, access and mobility management equipment 105, and Data Network (DN) equipment 106. Wherein, the first and the second end of the pipe are connected with each other,
terminal equipment 101 can also be referred to as user equipment, mobile station, access terminal, subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user device, etc. The terminal device may be a handheld user equipment, a notebook computer, a subscriber unit (subscriber unit), a cellular phone (cellular phone), a smart phone (smart phone), a wireless data card, a Personal Digital Assistant (PDA), a handheld device with wireless communication function, a vehicle-mounted device, a wearable device, and a mobile station in a future 5G network or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, and the like. The terminal device 101 and the access network device 102 communicate with each other by using some air interface technology.
The access network device 102 is mainly responsible for functions of radio resource management, quality of service (QoS) management, data compression and encryption, etc. on the air interface side. The access network device 102 may include various forms of access network devices, such as: macro base stations, micro base stations (also referred to as small stations), relay stations, access points, etc. In systems employing different radio access technologies, the names of access network devices may differ, for example, in a 5G communication system, referred to as a next-generation Node B (gNB); in a Long Term Evolution (LTE) system, referred to as an evolved NodeB (eNB or eNodeB); in the third generation (3 rd generation,3 g) system, it is called Node B (Node B) or the like.
And the gateway user plane device 103 is configured to receive the data packet from the terminal device 101 and forward the data packet. Gateway User plane device 103 may include various forms of User plane devices including, but not limited to, a User plane PDN Gateway (PGW-U), a User plane Serving Gateway (SGW-U), and a User plane function entity (UPF) in a 5G communication system, among others.
The gateway control plane device 104 is configured to manage creation, deletion, and the like of a Packet Data Unit (PDU) session of a user, and maintain a PDU session context and user plane forwarding management channel information. The Gateway Control plane device may include various forms of Control plane devices, including, but not limited to, a Control plane PDN Gateway (PGW-C), a Control plane Serving Gateway (SGW-C), and a Session Management Function (SMF) in a 5G communication system.
The access and mobility management device 105 is configured 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. The access and Mobility Management device includes, but is not limited to, a Mobility Management Entity (MME) in the LTE system, an access and Mobility Management Entity in the 5G communication system, and the like.
The data network device 106 is used to provide various types of services (e.g., network access, operator services, etc.) to the user. For example, the data network device 106 may be a server.
Types of data networks include, but are not limited to: internet (Internet), internet protocol multimedia subsystem (IMS).
In the above-described wireless communication system 100, the terminal device 101 and the access network device 102 communicate with each other via a wireless interface, and the terminal device 101 and the access and mobility management device 105 may communicate with each other via a wireless interface.
Optionally, please refer to fig. 2 and fig. 3, which are two optional detailed network architecture diagrams proposed in the present application, as shown in fig. 2, the PGW-U and the SGW-U may correspond to the gateway user plane device in fig. 1, and the PGW-C and the SGW-C may correspond to the gateway control plane device in fig. 1. The MME may correspond to the access and mobility management device in fig. 1 and the E-UTRAN may correspond to the access network device in fig. 1.
As shown in fig. 3, the UPF may correspond to the gateway user plane device in fig. 1, the SMF may correspond to the gateway control plane device in fig. 1, the AMF may correspond to the access and mobility management device in fig. 1, and the RAN may correspond to the access network device in fig. 1.
It should be noted that fig. 1 to fig. 3 are only for illustrating the communication connection relationship between the devices, and the communication interfaces between the devices are respectively shown in fig. 2 to fig. 3. It is to be understood that, in an actual application scenario, the number of each device may include one or more devices, for example, one or more gateway control plane devices, one or more access and mobility management devices, one or more gateway user plane devices, and the like, and the embodiments of the present application are not limited thereto.
Based on the foregoing devices in the wireless communication system 100, the embodiment of the present application provides a method for disaster recovery of a gateway device. As shown in fig. 4, the method includes, but is not limited to, the following steps.
S301: the first access and mobile management equipment receives a service request of the terminal equipment;
in this embodiment, the first access and mobility management device may be a source access and mobility management device associated with the terminal device, or may also be a backup access and mobility management device that determines a failure of the source access and mobility management device and reselects the source access and mobility management device when the terminal device sends a service request. Or the first access and mobility management device may also be an access and mobility management device randomly selected when the third gateway control plane device determines that the source access and mobility management device is faulty when the downlink data of the terminal device exists. The third gateway control plane device is a gateway control plane device selected by the gateway user plane device when determining that the first gateway control plane device associated with the terminal device fails.
The first disaster recovery data corresponding to the terminal device is stored in the source access and mobile management device, and optionally, the first disaster recovery data may also be stored in the backup mobile access and mobile management device in a backup manner. For a specific processing procedure of storing the first disaster recovery data in the source access and mobility management device, please refer to the description of the embodiment in fig. 5, which is not repeated herein.
Generally, an interface between an access network device and a gateway user plane device is released, and if a terminal device sends uplink data or downlink data sent to the terminal device exists, the terminal device is configured to manage a gateway control plane device of a session of the terminal device at the gateway user plane device, and reestablish a bearer between the access network device and the gateway user plane device, where the terminal device sends a Service Request (SR) for triggering reestablishment of the bearer between the access network device and the gateway user plane device.
Specifically, optionally, two optional embodiments are respectively set forth below, and a specific processing flow for triggering the terminal device to send the service request is triggered in two cases, that is, in the case that the terminal device sends the uplink data and in the case that the downlink data sent to the terminal device exists:
in a first optional implementation manner, if the terminal device sends uplink data, a service request is sent to a source access and mobility management device associated with the terminal device, and accordingly, the source access and mobility management device (in the application scenario, the first access and mobility management device is 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, a backup access and mobility management device for backing up and storing the first disaster recovery data corresponding to the terminal device may be selected, and a service request is sent to the backup access and mobility management device (in the application scenario, the first access and mobility management device is the backup access and mobility management device), and accordingly, the backup access and mobility management device receives the service request of the terminal device and responds to the service request.
In a second optional implementation manner, if there is downlink data sent to the terminal device, for example, a message is sent to a wechat application of the terminal device, the message is first transmitted to a gateway user plane device associated with the terminal device, and because an interface between the gateway user plane device and an access network device is released, the gateway user plane device sends a service message to a gateway control plane device for managing a session of the terminal device at the gateway user plane device, so as to trigger the gateway control plane device to control establishment of a bearer between the gateway user plane device and the access network device. Specifically, referring to fig. 6, a flow chart of a downlink data transmission processing provided in the embodiment of the present application includes, but is not limited to, steps S51 to S53;
s51, the gateway user plane equipment receives downlink data of the terminal equipment, determines that the first control plane equipment fails, and sends addressing information associated with the first disaster recovery data to the third gateway control plane equipment;
the first control plane device is configured to manage a session of the terminal device in the gateway user plane device, and when the gateway user plane device determines that the first control plane device is faulty, one gateway control plane device, such as a third gateway control plane device, may be reselected, where a selection manner may be random selection or selection based on a specific protocol rule, and the like. Optionally, the gateway user plane device may determine that the first gateway control plane device fails, where the gateway user plane device sends a request message to the first gateway control plane device for multiple times, and if none of the first gateway control plane devices responds, the gateway user plane device determines that the first gateway control plane device fails.
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 address the first disaster recovery data corresponding to the terminal device to recover the session of the terminal device at the gateway user plane device when the source access and mobility management device fails, the gateway user plane device sends addressing information to the third gateway control plane device, where the addressing information includes, but is not limited to, an identifier of the source access and mobility management device or index information used to represent a backup storage path of the first disaster recovery data, for example, all backup storage paths of the disaster recovery data with an index of 1 are backed up from the access and mobility management device a to the access and mobility management device B, and the source access and mobility management device and the backup access and mobility management device can be determined through the index information. It should be noted that in this 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 mobile management device, wherein the second message comprises first indication information, and the first indication information is used for indicating the first access and mobile management device to send a paging message to the terminal device;
and S53, the first access and mobile 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, wherein the paging message is used for triggering the terminal device to send the service request.
Correspondingly, the third gateway control panel device receives the addressing information, and can acquire the source access and mobile management device corresponding to the terminal device through the addressing information, the third gateway control panel device first judges whether the source access and mobile management device is available, and if the source access and mobile management device is determined to be available, a second message is sent to the source access and mobile management device, the second message includes first indication information, and the first indication information is used for indicating the source access and mobile 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 a session context corresponding to the terminal device exists, so that the first access and mobility management device stores the identifier of the access network device associated with the terminal device in advance, and the first access and mobility management device can directly send the paging message to the terminal device through the stored access network device associated with the terminal device according to the first indication information. After receiving the paging message, the terminal device sends a service request to the source access and mobility management device (in the application scenario, the first access and mobility management device is the source access and mobility management device).
Optionally, if the third gateway control panel device determines that the source access and mobility management device is faulty, one access and mobility management device may be randomly selected, and the addressing information and the first indication information are sent to the randomly selected access and mobility management device, so that when the randomly selected access and mobility management device detects that there is no session context corresponding to the terminal device, the backup storage location of the first disaster recovery data is obtained through the addressing information, and the first disaster recovery data is obtained from the backup storage location. The first disaster recovery data further includes an identifier of an 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 the application scenario, the first access and mobility management device is the randomly selected access and mobility management device).
After receiving a service request of a terminal device, a first access and mobility management device (a source access and mobility management device or a randomly selected access and mobility management device) determines that a first gateway control surface device for managing a session of the terminal device on a gateway user surface device fails, selects a second gateway control surface device, and sends a first message to the second gateway control surface device, wherein the first message comprises first disaster tolerance data corresponding to the terminal device, and the second gateway control surface device recovers the session of the terminal device on the gateway user surface device according to the first disaster tolerance data. (refer to the description of S302-S304, which is not repeated here.)
After the second gateway control surface device recovers the session of the terminal device in the gateway user surface device, the second gateway control surface device controls and establishes the bearer between the access network device associated with the terminal device and the gateway user surface device, and the gateway user surface device can transmit the downlink data corresponding to the terminal device through the established bearer, so that the downlink data of the terminal device can be transmitted to the terminal device even in the fault scene of the first gateway control surface device.
Optionally, the first access and mobility management device of this embodiment may include an AMF, the first gateway control plane device may include an SMF, the gateway user plane device may include an UPF, or the first access and mobility management device may include an MME, the first gateway control plane device may include an SGW-C and a PGW-C, the gateway user plane device may include an SGW-U and a PGW-U, please refer to fig. 9, which illustrates an example in this application embodiment, a paging process in a downlink data transmission flow and a flow that triggers the terminal device to send a service request are described, devices such as the MME, the SGW-C, and the PGW-C are deployed in both the two data centers DC1 and DC2, and the user plane device SGW-U and the PGW-U are located close to a user (for example, the province of the user), and this embodiment includes the following steps:
1. the Downlink Data of the terminal equipment is transmitted to the PGW-U, the PGW-U forwards the Downlink Data to the SGW-U, and as an S1-U interface between the SGW-U and the access network equipment is released, a Downlink Data Notification (DDN) process is initiated. The DDN process comprises the following steps: the SGW-U informs the SGW-C associated with the terminal equipment to page the terminal equipment, the SGW-C informs the MME to initiate paging, the MME initiates a paging process to the terminal equipment through the access network equipment, the terminal is on-line after receiving the paging, reestablishes an S1-U bearer and sends downlink data to the terminal equipment.
In the embodiment of the application, in order to still send downlink data to the terminal device when a gateway control plane associated with the terminal device fails. In this embodiment of the present application, if the SGW-U determines that an SGW-C associated with the terminal device fails, the SGW-U randomly selects an available SGW-C (for example, the SGW-C4) to initiate a DDN procedure, that is, the SGW-U sends a DDN message to the SGW-C4, where the DDN message includes addressing information, where the addressing information may include, but is not limited to, an identifier of a source MME (for example, an S-MME) used for storing first disaster recovery data corresponding to the terminal device or index information used for indicating a backup storage path of the first disaster recovery data.
2. After the SGW-C4 receives the DDN message, the SGW-C4 detects that no context of a session corresponding to the terminal equipment exists, the DDN message contains an identification of an S-MME, if the SGW-C4 determines whether the S-MME is available, if the S-MME is available, the S-MME is selected, and the DDN message is sent to the S-MME; optionally, if the SGW-C4 determines that the S-MME fails, an available MME (e.g., MME 4) is randomly selected, and a DDN message is sent to the MME4, where the DDN message includes addressing information. The MME4 is a randomly selected MME, and therefore the MME4 may not be the MME corresponding to the S-MME for backing up the first disaster recovery data corresponding to the storage terminal device.
3. If the SGW-C4 is a DDN message sent to the S-MME, the S-MME stores all disaster recovery data corresponding to the terminal device, including the access network device associated with the terminal device, so that the S-MME can directly initiate a paging procedure to the terminal device through the access network device associated with the terminal device.
If the SGW-C4 is a DDN message sent to the MME4, and after the MME4 receives the DDN message, the MME4 detects that there is no session context corresponding to the terminal device locally, and acquires first disaster recovery data corresponding to the terminal device according to addressing information carried in the DDN message. For example, an MME (e.g., MME 2) for backing up and storing the first disaster recovery data is obtained according to the identifier of the S-MME, and then the first disaster recovery data is obtained from the MME 2. The identifier of the access network device associated with the terminal device can be obtained from the first disaster recovery data, and the MME4 initiates a paging procedure to the access network device.
After receiving the paging, the terminal device sends a service request to the MME 4.
S302: the first access and mobile management equipment responds to the service request, determines that first gateway control panel equipment fails, and selects second gateway control panel equipment, wherein the first gateway control panel equipment is used for managing the session of the terminal equipment on gateway user panel equipment;
s303: the first access and mobile 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 is used by the second gateway control plane device to recover the session of the terminal device at the gateway user plane device according to the first disaster tolerance data.
S304: and the second gateway control plane equipment recovers the session of the terminal equipment on the gateway user plane equipment according to the first disaster recovery data.
In one embodiment, the first access and mobility management device determines that a first gateway control plane device associated with the terminal device fails after receiving a service request from the terminal device. Optionally, after the first access and mobility management device sends a message to the first gateway control plane device associated with the terminal device for multiple times, and does not receive a response message of the first gateway control plane device, it determines that the first gateway control plane device fails, so as to select the second gateway control plane device.
Optionally, the first message may be a Create Session Request (e.g., create Session Request), that is, an attach procedure of the terminal device is simulated. And when the second gateway control panel equipment recovers the session of the terminal equipment in the gateway user panel equipment according to the first disaster recovery data in the session creation request, sending a response message of successful recovery to the first access and mobile management equipment.
After receiving the response message of successful recovery sent by the second gateway control surface device, the first access and mobility management device sends a service message to the second gateway control surface device according to the service request of the terminal device, where the service message is used to request the second gateway control surface device to establish a bearer between the gateway user surface device associated with the terminal device and the access network device associated with the terminal device, and when the bearer between the gateway user surface device and the access network device associated with the terminal device is successfully established, the terminal device can send uplink data by using the bearer or receive downlink data. If the service request is triggered by the existence of the uplink data sent by the terminal equipment, the terminal equipment can send the uplink data by using the bearer, and if the service request is triggered by the existence of the downlink data sent to the terminal equipment through the paging process, the terminal equipment can receive the downlink data by using the bearer.
Optionally, the first message may be a service message, that is, the first access and mobility management device sends the service message according to a service request of the terminal device, and this scenario is that session recovery of the terminal device on the gateway user plane device is completed in a normal service interaction flow. The service message includes first disaster recovery data corresponding to the terminal device, and after receiving the service message, the second gateway control panel device recovers the session of the terminal device at the gateway user plane device according to the first disaster recovery data when detecting that there is no session context corresponding to the terminal device locally, and then processes the service indicated by the service message, for example, controls to establish a bearer between the gateway user plane device associated with the terminal device and an access network device associated with the terminal device, so that the terminal device sends uplink data or receives downlink data. If the service request is triggered by the existence of the uplink data sent by the terminal equipment, the terminal equipment can send the uplink data by using the bearer, and if the service request is triggered by the existence of the downlink data sent to the terminal equipment through the paging process, the terminal equipment can receive the downlink data by using the bearer.
The recovering 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 sessions with peripheral entities, such as recovering a Charging session with an Online Charging System (OCS), recovering a session with a Policy and Charging Rules entity (PCRF), taking over a bearer of a terminal device at a gateway user equipment, and so on. Taking over the bearer of the terminal device at the gateway user plane device may include, but is not limited to: when uplink data or downlink data of the terminal device subsequently exist, and when a second gateway control plane device is available, a bearer between the access network device and the gateway user plane device may be established through the second gateway control plane device.
Optionally, the first access and mobility management device may include an AMF, the gateway control plane device may include an SMF, the gateway user plane device may include an UPF, or the access and mobility management device may include an MME, the gateway control plane device may include an SGW-C and a PGW-C, the gateway user plane device may include an SGW-U and a PGW-U, please refer to fig. 8, which illustrates an example in an embodiment of the present application, where a service request is initiated by a terminal and a session recovery procedure is described, an MME, an SGW-C, a PGW-C, an online charging system OCS and a policy control and rule function PCRF device are both deployed in two data centers DC1 and DC2, and the user plane device SGW-U and the PGW-U are located close to a user (for example, a province where the user is located), where the embodiment includes the following steps:
1. and the terminal equipment sends the SR request through the access network equipment, wherein the SR request is sent to the backup MME when the source MME fails, and the SR request is sent to the source MME when the source MME is available. The backup MME is illustrated.
2. And the backup MME determines that the SGW-C and the PGW-C associated with the terminal equipment are in failure, reselects the SGW-C and the PGW-C, can simulate a terminal attachment process, sends a Session creation Request (such as a Create Session Request) to the reselected SGW-C, and carries first disaster tolerance data corresponding to the terminal equipment in the Session creation Request.
3. And after receiving the session establishing request, the reselected SGW-C reestablishes the session with the peripheral entity according to the first disaster recovery data, and takes over the load of the terminal equipment in the SGW-U. And simultaneously sending a request message for disaster recovery to the reselected PGW-C, wherein the request message comprises the first disaster recovery data.
After receiving the request message, the reselected PGW-C reestablishes sessions with the peripheral entities, such as recovering a charging session with the OCS and recovering a session with the PCRF, according to the first disaster recovery data; and taking over the bearing of the terminal equipment in the PGW-U.
And the session between the reselected SGW-C and PGW-C and the peripheral entity is recovered, and the bearing of the terminal equipment in the SGW-U and the PGW-U is also recovered. The PGW-C replies a response message of successful restoration to the SGW-C, the SGW-C replies a response message of successful restoration to the MME, and the MME may perform a subsequent procedure, for example, send a service message to the reselected SGW-C, where the service message is used to request the SGW-C to establish a bearer between the access network device and the SGW-U, so as to transmit downlink data or uplink data of the terminal device.
Referring to fig. 5, a schematic diagram of a first disaster recovery data collection process proposed in the embodiment of the present application is shown, where the first disaster recovery data collection process includes, but is not limited to, steps S41 to S45, it should be noted that in the embodiment, the first access and mobile management device is a source access and mobile management device, and objects referred to by the first access and mobile management device in the embodiment may be different from those in the embodiment of fig. 4;
s41: the first access and mobile management equipment receives an attachment request of the terminal equipment.
When the terminal is powered on, or after the terminal switches a cell, and the like, the terminal device sends an attach request to the first access and mobility management device through the access network device associated with the terminal device, where the attach request may include an identifier of the terminal device, and the identifier of the terminal device may be a device code of the terminal device.
S42: and the first access and mobile management equipment sends a third message to first gateway control surface equipment according to the attachment request, wherein the third message comprises second indication information and the identifier of the terminal equipment, and the second indication information is used for indicating the first gateway control surface equipment to send the first disaster tolerance data corresponding to the terminal equipment to the first access and mobile management equipment.
S43: the first gateway control surface equipment sends the identification of the first access and mobile management equipment and the identification of the terminal equipment to the gateway user surface equipment; the identifier of the first access and mobility management device is used for acquiring the first disaster recovery data when the gateway user plane device receives downlink data corresponding to the terminal device and the first gateway control plane device fails.
S44: and the first gateway control surface equipment sends first disaster recovery data corresponding to the terminal equipment to the first access and mobile management equipment.
S45: the first access and mobility management device stores the first disaster recovery data.
The first access and mobility management device receives an attach Request of the terminal device from the access network device, and sends a third message to the first gateway control plane device, where the third message may be a Create Session Request (e.g., create Session Request), and 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 the second indication information.
Optionally, the second indication information is used to indicate that the first gateway control surface device sends, to the first access and mobility management device, first disaster recovery data corresponding to the identifier of the terminal device that is carried when supporting the method for disaster recovery of gateway devices in the embodiment of the present application, where the first disaster recovery data may be included in a response message that the first gateway control surface device sends to the first access and mobility management device, and the first access and mobility management device receives the response message that the first gateway control surface device sends, and stores, in the first access and mobility management device, the first disaster recovery data included in the response message. The response message may be an expanded message, for example, the response message may include a newly added private expansion field, and the private expansion field is used to carry the first disaster recovery data.
Optionally, the first access and mobility management device may further backup the first disaster recovery data corresponding to the terminal device to a third access and mobility management device, so that when the terminal device sends a service request, if the first access and mobility management device fails, the third access and mobility management device performs access management and responds to the service request.
Optionally, the first disaster recovery data may include, but is not limited to, an IP address of the terminal device, and key data such as a gateway user plane device activated by the terminal device, where the first disaster recovery data is used when the first gateway control plane device fails, and the second gateway control plane device recovers a session of the terminal device in the gateway user plane device, please refer to the description of the foregoing embodiment specifically, and no further description is given here. The gateway user plane device may include, but is not limited to, a PGW-U, a UPF, and the like. The gateway user plane device activated by the terminal device means that the uplink data and the downlink data corresponding to the terminal device are both forwarded through the gateway user plane device.
Optionally, the third message may further include addressing information, where the addressing information includes, but is not limited to, an identifier of the first access and mobile management device, or index information used to indicate a backup storage path of the first disaster recovery data, and the like, for example, all backup storage paths of the disaster recovery data with an index of 1 are backed up from the access and mobile management device a to the access and mobile management device B, and the like. When determining that the method for disaster recovery of the gateway device is supported, the first gateway control plane device sends the addressing information and the identifier of the terminal device to a gateway user plane device activated by the terminal device, where the gateway user plane device stores a corresponding relationship between the addressing information and the identifier of the terminal device. Therefore, subsequently, when the gateway user plane device receives downlink data corresponding to the terminal device and determines that a first gateway control plane for managing the terminal device in a gateway user plane device session has a fault, the first access and mobile management device may be determined according to the addressing information, or when the first access and mobile management device has a fault, the first disaster recovery data corresponding to the terminal device is obtained through the addressing information, which is specifically described with reference to fig. 6, and is not described herein again.
Optionally, the first access and mobility management device may include an AMF, the first gateway control plane device may include an SMF, and the gateway user plane device may include a UPF, or the first access and mobility management device may include an MME, the first gateway control plane device may include an SGW-C and a PGW-C, and the gateway user plane device may include an SGW-U and a PGW-U, referring to fig. 7, in this embodiment of the present application, an MME, an SGW-C, a PGW-C, an SGW-U, a PGW-U, an online charging system OCS, and a PCRF, are deployed in both data centers DC1 and DC2, a PCRF, a control plane device MME, an SGW-C, a PGW-C, an OCS, an MME, and a PCRF are located in the DC, and a SGW-U and a PGW-U are located close to a user (for example, a province where the user is located), and this embodiment includes the following steps:
1. the access network equipment sends an attachment request of the terminal equipment to a source MME;
2. the method includes that a source MME sends a Session creation Request (for example, create Session Request) to an SGW-C, the Session creation Request includes a private extension field, the private extension field includes indication information, and the indication information is used for inquiring whether the SGW-C supports the disaster recovery method provided by the embodiment of the application, and when the SGW-C supports the disaster recovery method provided by the embodiment of the application, disaster recovery data corresponding to a terminal device is sent to the MME.
3. A source SGW-C receives a session creation request, and if the SGW-C supports the disaster recovery method of the embodiment of the application, the SGW-U sends an identifier of a source MME to the SGW-U, and the SGW-U stores the identifier of the source MME; and the SGW-C sends a message to the PGW-C, where the message also includes a private extension field, where the private extension field includes indication information, where the indication information is used to inquire whether the PGW-C supports the disaster recovery method provided in the embodiment of the present application, and when the PGW-C supports the disaster recovery method provided in the embodiment of the present application, sends the disaster recovery data corresponding to the terminal device to the SGW-C.
4. The method includes the steps that a PGW-C receives a message sent by the SGW-C, if the PGW-C supports the disaster recovery method of the embodiment of the application, key data such as a PGW-U and an IP address activated by a terminal device are used as disaster recovery data, and the key data are sent to the SGW-C through a response message, wherein the response message also comprises a private extension field, and the private extension field comprises the disaster recovery data.
5. The SGW-C receives a response message sent by the PGW-C, and if the response message carries disaster tolerance data corresponding to the terminal device, it indicates that the PGW-C supports the disaster tolerance method provided in the embodiment of the present application, and the SGW-C sends a response message to the source MME, where the response message also includes a private extension field, and the private extension field includes the disaster tolerance data corresponding to the terminal device.
And the source MME receives a response message returned by the SGW-C, and stores the disaster tolerance data if the private extension field of the response message carries the disaster tolerance data corresponding to the terminal equipment.
Further optionally, if the source MME has a backup capability across regions, the source MME may further store the disaster recovery data across regions in another MME, that is, the backup MME.
Through the steps S41 to S45, the first disaster recovery data corresponding to the terminal device is stored in the first access and mobility management device, and the subsequent terminal device may perform data transmission through the gateway user plane device.
The following describes the configurations of the access and mobility management device and the gateway control plane device according to the embodiment of the present application with reference to fig. 10 to 15.
In this embodiment of the present invention, in a process of communication between a first access and mobility management device and a gateway control plane device (a first gateway control plane device, a second gateway control plane device, and a third gateway control plane device), a terminal device, and an access network device, an operation executed by the first access and mobility management device side may be executed by a processing unit, a receiving unit, and a sending unit in the first access and mobility management device, where the receiving unit is configured to execute an operation of receiving information (or a message) in the process, the sending unit is configured to execute an operation of sending information (or a message) in the process, and the processing unit is configured to execute other operations except for the operations executed by the receiving unit and the sending unit in the process. Alternatively, the sending unit and the receiving unit are controlled by the processing unit, that is, the processing unit may control the sending unit to perform sending operation and control the receiving unit to perform receiving operation, respectively. In addition, the processing unit, the receiving unit, and the sending unit in the first access and mobility management device may be logic modules divided according to functions, or may be corresponding hardware modules. When the processing unit, the receiving unit and the sending unit are all logic modules, the structure of the first access and mobility management device may be as shown in fig. 10.
The receiving unit 1101 is configured to receive a service request of a terminal device;
the processing unit 1102 is configured to respond to the service request, determine that a first gateway control plane device fails, and select a second gateway control plane device, where the first gateway control plane device is configured to manage a session of the terminal device in a gateway user plane device;
the sending unit 1103 is further configured to send a first message to the second gateway control surface device, where the first message includes first disaster tolerance data corresponding to the terminal device, and the first disaster tolerance data is used by the second gateway control surface device to recover, according to the first disaster tolerance data, the session of the terminal device on the gateway user surface 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, and at this time, the structure of the first access and mobility management device may be as shown in fig. 11.
Referring to fig. 11, fig. 11 shows an access and mobility management device according to an embodiment of the present application, where the access and mobility management device 120 may include: one or more processors 1201, memory 1202, transmitter 1203, receiver 1204. These components may be connected by a bus 1205 or otherwise, as illustrated by the bus connection in FIG. 11. Wherein:
the processor 1201 may be a general-purpose processor, such as a Central Processing Unit (CPU), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present 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 to the processor 1201 via the bus 1205 or an input/output port, or the memory 1202 may be integrated with the processor 1201. The memory 1202 is used to store various software programs and/or sets of instructions. In particular, the memory 1202 may include high-speed random access memory, and may also include 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 that may be used to communicate with one or more additional devices, one or more terminals, one or more network devices.
The transmitter 1203 may be configured to perform transmission processing on the signal output by the processor 1201. The receiver 1204 may be used for receive processing of received communication signals. In the access and mobility management device 120, the number of the transmitters 1203 and the receivers 1204 may be one or more.
The processor 1201 may be configured to read and execute computer readable instructions. Specifically, the processor 1201 may be configured to invoke a program stored in the memory 1202, for example, an implementation program of the method for disaster recovery of a gateway device provided in one or more embodiments of the present application on the first access and mobility management device side, and execute instructions included in the program to implement the method related to the subsequent embodiments. Optionally, when the processor 1201 sends any message or data, it does so, in particular by driving or controlling the transmitter 1203. Alternatively, when the processor 1201 receives any message or data, it does so by driving or controlling the receiver 1204, in particular. Thus, the processor 1201 can be considered as a control center that performs transmission or reception, and the transmitter 1203 and receiver 1204 are specific actors of the transmission and reception operations.
The receiver 1204 is configured to receive a service request of a terminal device;
a processor 1201, configured to respond to the service request, and select a second gateway control panel device if it is determined that a first gateway control panel device fails, where the first gateway control panel device is configured to manage a session of the terminal device in a gateway user plane device;
a transmitter 1203, 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 by the second gateway control plane device to recover, according to the first disaster tolerance data, the session of the terminal device on the gateway user plane device.
It should be noted that the access and mobility management device 120 shown in fig. 11 is only one implementation manner of the embodiment of the present application, and in practical applications, the access and mobility management device 120 may further include more or less components, which is not limited herein.
In this embodiment of the present invention, in a process that a first gateway control plane device communicates with other communication devices (e.g., a first access and mobility management device, a gateway user plane device, etc.), an operation performed by a first gateway control plane device side may be performed by a receiving unit, a processing unit, and a sending unit in the first gateway control plane device, where the receiving unit is configured to perform an operation of receiving information (or a message) in the process, and the sending unit is configured to perform an operation of sending information (or a message) in the process. Alternatively, the sending unit and the receiving unit may be controlled by the processing unit, that is, the processing unit may control the sending unit to perform sending operation and the receiving unit to perform receiving operation, respectively, or 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 logic 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.
The receiving unit 1301 is configured to receive a third message from a first access and mobility management device, where the third message includes second indication information and an identifier of a terminal device, the second indication information is used to indicate the first gateway control plane device to send first disaster recovery data corresponding to the terminal device to the first access and mobility management device, and the first disaster recovery data is used to recover a session of the terminal device on a gateway user plane device when it is determined that the first gateway control plane device fails;
the processing unit 1302 is configured to parse the third message to obtain second indication information and an identifier of the terminal device;
the sending unit 1303 is configured to send the first disaster recovery 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, where the structure of the first gateway control plane device may be as shown in fig. 13.
Referring to fig. 13, fig. 13 is a schematic diagram illustrating a hardware structure of a first gateway control plane device according to an embodiment of the present application, where the gateway control plane device 140 may include: one or more processors 1401, memory 1402, transmitter 1403, receiver 1404. These components may be connected by a bus 1405 or otherwise, as illustrated by the bus connection in FIG. 13. Wherein:
processor 1401 may be a general-purpose processor, such as a Central Processing Unit (CPU), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention. Processor 1401 can process data received via receiver 1404. Processor 1401 can also process data to be sent to transmitter 1403.
Memory 1402 may be coupled to processor 1401 via bus 1405 or an input-output port, and memory 1402 may be integrated with processor 1401. The memory 1402 is used to store various software programs and/or sets of instructions. In particular, memory 1402 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 1402 may also store a network communication program that can be utilized to communicate with one or more additional devices, one or more terminals, and one or more network devices.
Transmitter 1403 may be used for transmit processing of signals output by processor 1401. Receiver 1404 may be used for receive processing of received communication signals. In the gateway control plane device 140, the number of the transmitter 1403 and the receiver 1404 may be one or more.
Processor 1401 is operable to read and execute computer readable instructions. Specifically, the processor 1401 may be configured to invoke a program stored in the memory 1402, for example, an implementation program of the method for disaster recovery of a gateway device provided in one or more embodiments of the present application on the first gateway control plane device side, and execute instructions included in the program to implement the method according to the foregoing embodiments. Optionally, when processor 1401 sends any message or data, it does so, in particular by driving or controlling transmitter 1403. Optionally, when processor 1401 receives any message or data, it does so, in particular by driving or controlling receiver 1404. Thus, 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 transmission and reception operations.
The receiver 1404 is configured to receive a third message from a first access and mobility management device, where the third message includes second indication information and an identifier of a terminal device, the second indication information is used to indicate the first gateway control plane device to send first disaster recovery data corresponding to the terminal device to the first access and mobility management device, and the first disaster recovery data is used to recover a session of the terminal device on a gateway user plane device when it is determined that the first gateway control plane device fails;
a processor 1401, configured to parse the third message, to obtain second indication information and an identifier of the terminal device;
a transmitter 1403, configured to send the first disaster recovery data to the first access and mobile management device.
It should be noted that the gateway control plane apparatus shown in fig. 13 is only one implementation manner of the embodiment of the present application, and in practical applications, the gateway control plane apparatus 140 may also include more or less components, and is not limited herein.
In this embodiment of the present invention, in a process that the second gateway control plane device communicates with another communication device (such as the first access and mobility management device), an operation performed by the second gateway control plane device side may be performed by a receiving unit and a processing unit in the second gateway control plane device, where the receiving unit is configured to perform an operation of receiving information (or a message) in the process, and the processing unit is configured to process the received message. Alternatively, 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, or 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 logic modules divided according to functions, or may be corresponding hardware modules. When the processing unit and the receiving unit are both logic modules, the structure of the second gateway control plane device may be as shown in fig. 14.
The receiving unit 1501 is configured to receive a first message from a first access and mobility management device, where the first message is triggered when the first access and mobility management device receives a service request of a terminal device and determines that a first gateway control plane device fails, where the first message includes first disaster recovery data corresponding to the terminal device, and the first gateway control plane device is configured to manage a session of the terminal device on a gateway user plane device;
the processing unit 1502 is configured to recover, according to the first disaster recovery data, a session of the terminal device on the gateway user plane device.
Optionally, the second gateway control plane device may further include a sending unit, configured to send a message to other communication devices.
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, and at this time, the structure of the first access and mobility management device may be as shown in fig. 15.
Referring to fig. 15, fig. 15 shows a second gateway control plane device according to an embodiment of the present application, where the second gateway control plane device 160 may include: one or more processors 1601, memory 1602, transmitters 1603, receivers 1604. These components may be connected by a bus 1605 or otherwise, with fig. 15 exemplified as being connected by a bus. Wherein:
the processor 1601 may be a general purpose processor, such as a Central Processing Unit (CPU), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention. The processor 1601 may process data received by the receiver 1604. Processor 1601 may also process data to be sent to transmitter 1603.
The memory 1602 may be coupled to the processor 1601 by 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 sets of instructions. In particular, the memory 1602 may include high-speed random access memory, and may also include 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 that may be used to communicate with one or more additional devices, one or more terminals, and one or more network devices.
Transmitter 1603 may be used to transmit the signal output by processor 1601. The receiver 1604 may be configured to perform receive processing on received communication signals. The number of transmitters 1603 and receivers 1604 may each be one or more in the second gateway control plane device 160.
Processor 1601 is operable to read and execute computer readable instructions. Specifically, the processor 1601 is configured to invoke a program stored in the memory 1602, for example, an implementation program of the method for disaster recovery of the gateway device provided in one or more embodiments of the present application on the second gateway control plane device side, and execute instructions included in the program to implement the method according to the foregoing embodiments. Alternatively, when the processor 1601 sends any message or data, it does so by driving or controlling the transmitter 1603, among other things. Alternatively, when the processor 1601 receives any message or data, it does so, in particular by driving or controlling the receiver 1604. Thus, the processor 1601 may be considered a control center that performs transmission or reception, with the transmitter 1603 and the receiver 1604 being specific actors performing transmission and reception operations.
The receiver 1604 is configured to receive a first message from a first access and mobility management device, where the first message is triggered when the first access and mobility management device receives a service request of a terminal device and determines that a first gateway control plane device fails, where the first message includes first disaster recovery data corresponding to the terminal device, and the first gateway control plane device is used to manage a session of the terminal device on a gateway user plane device;
and a processor 1601, configured to recover, according to the first disaster recovery data, a session of the terminal device on the gateway user plane device.
It should be noted that the access and mobility management device 160 shown in fig. 15 is only one implementation manner of the embodiment of the present application, and in practical applications, the access and mobility management device 160 may further include more or less components, which is not limited herein.
Referring to fig. 16, fig. 16 shows a schematic structural diagram of a communication chip provided in 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. Wherein:
the processor 1701 may be used to read and execute computer readable instructions. In particular implementations, the processor 1701 may include primarily controllers, operators, and registers. The controller is mainly responsible for instruction decoding and sending out control signals for operations corresponding to the instructions. The arithmetic unit is mainly responsible for executing fixed-point or floating-point arithmetic operation, shift operation, logic operation and the like, and can also execute address operation and conversion. The register is mainly responsible for storing register operands, intermediate operation results and the like temporarily stored in the instruction execution process. In particular, the hardware architecture of the processor 1701 may be an Application Specific Integrated Circuit (ASIC) architecture, an MIPS architecture, an ARM architecture, an NP architecture, or the like. The processor 1701 may be single core or multi-core.
The interface 1702 is operable to input data to be processed to the processor 1701, and may output the processing result of the processor 1701 to the outside. For example, the interface 1702 may be a general purpose input/output (GPIO) interface, and may be connected to a plurality of peripheral devices (e.g., a display (LCD), a camera (camara), a Radio Frequency (RF) module, etc.). The interface 1702 is connected to the processor 1701 via a bus 1703.
The processor 1701 may be configured to invoke from the memory an implementation procedure of the method for disaster recovery of a gateway device according to one or more embodiments of the present application on the communication device side (the first access and mobility management device, the first gateway control plane device, or the second gateway control plane device), and execute the instructions contained in the procedure. The interface 1702 may be used to output the results of execution by the processor 1701. For the method for disaster recovery of gateway devices provided in one or more embodiments of the present application, reference may be made to the foregoing method embodiments, and details are not described here again.
It should be noted that the functions of the processor 1701 and the interface 1702 may be implemented by hardware design, software design, or a combination of hardware and software, which is not limited herein.
In another embodiment of the present application, a readable storage medium is further provided, where the readable storage medium stores computer execution instructions, and when one device (may be a single chip, a chip, or the like) or a processor invokes the computer execution instructions stored in the readable storage medium, 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 method for disaster recovery of gateway devices provided in fig. 4 to fig. 6 are implemented. The aforementioned readable storage medium may include: u disk, removable hard disk, read only memory, random access memory, magnetic or optical disk, etc. for storing program codes.
In another embodiment of the present application, there is also provided a computer program product comprising computer executable instructions stored in a computer readable storage medium; the at least one processor of the device may read the computer-executable instructions from the computer-readable storage medium 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 method for disaster recovery of a gateway device provided in fig. 4-6.
The terms "first," "second," "third," and "fourth," etc. in the description and claims of this application and in the accompanying drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a Solid State Disk (SSD)), among others.
Finally, it should be noted that: the above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (22)

1. A method for disaster recovery of gateway equipment is characterized by comprising the following steps:
the first access and mobile management equipment receives a service request of the terminal equipment;
the first access and mobile management equipment responds to the service request, determines that first gateway control panel equipment fails, and selects second gateway control panel equipment, wherein the first gateway control panel equipment is used for managing the session of the terminal equipment on gateway user panel equipment;
the first access and mobile 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 includes a network protocol IP address of the terminal device and a gateway user plane device activated by the terminal device; and the first disaster tolerance data is used for the second gateway control surface equipment to recover the session of the terminal equipment on the gateway user surface equipment according to the first disaster tolerance data.
2. The method of claim 1, wherein the first message is a create session request or a service message; the service message is used for requesting 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.
3. The method of claim 1 or 2, wherein before the first access and mobility management device receives the service request of the terminal device, the method further comprises:
the first access and mobile management device receives a second message from a third gateway control plane device, where the second message is sent by triggering the third gateway control plane device when the gateway user plane device receives downlink data corresponding to the terminal device and determines that the first gateway control plane device fails, and the second message includes first indication information, where the first indication information is used to indicate the first access and mobile management device to send a paging message to the terminal device;
and the first access and mobile management equipment sends a paging message to the terminal equipment according to the first indication information, wherein the paging message is used for triggering the terminal equipment to send the service request.
4. The method of claim 3, wherein the second message further includes addressing information associated with the first disaster recovery data, the addressing information being used to obtain a backup storage location for the first disaster recovery data; the method further comprises the following steps:
the first access and mobile management equipment acquires first disaster tolerance data corresponding to the terminal equipment according to the addressing information, wherein the first disaster tolerance data also comprises an identifier of access network equipment associated with the terminal equipment;
the first access and mobility management device sends a paging message to the terminal device according to the first indication information, and the paging message includes:
and the first access and mobile management equipment sends a paging message to the terminal equipment through the access network equipment according to the first indication information.
5. The method of claim 1, wherein before the first access and mobility management device receives the service request from the terminal device, the method further comprises:
the first access and mobile management equipment receives an attachment request of the terminal equipment;
the first access and mobile management device sends a third message to the first gateway control plane device according to the attach request, where 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 gateway control plane device to send the first disaster recovery data corresponding to the terminal device to the first access and mobile management device;
the first access and mobile management device receives the first disaster recovery data from the first gateway control plane device;
and the first access and mobile management equipment stores the first disaster tolerance data.
6. The method of claim 5, wherein the method further comprises:
and the first access and mobile management equipment backs up the first disaster recovery data to second access and mobile management equipment.
7. A method for disaster recovery of gateway equipment is characterized by comprising the following steps:
the first gateway control surface device receives a third message from a first access and mobile management device, where the third message includes second indication information and an identifier of a terminal device, the second indication information is used to indicate the first gateway control surface device to send first disaster recovery data corresponding to the terminal device to the first access and mobile management device, and the first disaster recovery data includes a network protocol IP address of the terminal device and a gateway user plane device activated by the terminal device; the first disaster recovery data is used for recovering the session of the terminal equipment on the gateway user plane equipment when the first gateway control plane equipment is determined to be in fault;
and the first gateway control surface equipment sends the first disaster recovery data to the first access and mobile management equipment.
8. The method of claim 7, wherein the third message further includes addressing information associated with the first disaster recovery data; the method further comprises the following steps:
the first gateway control surface device sends the addressing information and the identifier of the terminal device to the gateway user surface device, wherein the addressing information is used for enabling the gateway user surface device to receive downlink data corresponding to the terminal device, and the first gateway control surface device acquires the first disaster recovery data when the first gateway control surface device fails.
9. A method for disaster recovery of gateway equipment is characterized by comprising the following steps:
the method comprises the steps that a second gateway control surface device receives a first message from a first access and mobile management device, wherein the first message is triggered when the first access and mobile management device receives a service request of a terminal device and determines that the first gateway control surface device fails, the first message comprises first disaster tolerance data corresponding to the terminal device, and the first disaster tolerance data comprises a network protocol IP address of the terminal device and gateway user surface devices activated by the terminal device; the first gateway control plane device is used for managing the session of the terminal device on the gateway user plane device;
and the second gateway control plane equipment recovers the session of the terminal equipment on the gateway user plane equipment according to the first disaster recovery data.
10. The method of claim 9, wherein the first message is a create session request or a service message; the service message is used for requesting 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.
11. 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 transmitting unit, wherein:
the receiving unit is used for receiving a service request of the terminal equipment;
the processing unit is configured to respond to the service request, determine that a first gateway control surface device fails, and select a second gateway control surface device, where the first gateway control surface device is configured to manage a session of the terminal device in a gateway user plane device;
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 includes a network protocol IP address of the terminal device and a gateway user plane device activated by the terminal device; the first disaster recovery data is used for the second gateway control plane device to recover the session of the terminal device on the gateway user plane device according to the first disaster recovery data.
12. The access and mobility management device of claim 11, wherein the first message is a create session request or a service message; the service message is used for requesting 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.
13. The access and mobility management device according to claim 11 or 12,
the receiving unit is further configured to receive a second message from a third gateway control plane device, where the second message is sent by triggering the third gateway control plane device when the gateway user plane device receives downlink data corresponding to the terminal device and determines that the first gateway control plane device fails, and the second message includes first indication information, where the first indication information is used to indicate the first access and mobility management device to send a paging message to the terminal device;
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.
14. The access and mobility management device of claim 13, wherein the second message further includes addressing information associated with the first disaster recovery data, the addressing information being used to obtain a backup storage location for the first disaster recovery data;
the processing unit is further configured to obtain first disaster recovery data corresponding to the terminal device according to the addressing information, where the first disaster recovery data further includes an identifier of an access network device associated with the terminal device;
the sending unit is further configured to send, according to the first indication information, a paging message to the terminal device through the access network device.
15. The access and mobility management device of claim 11,
the receiving unit is further configured to receive an attach request of the terminal device;
the sending unit is further configured to send a third message to the first gateway control surface device according to the attach request, where 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 gateway control surface device to send the first disaster recovery data corresponding to the terminal device to the first access and mobile management device;
the receiving unit is further configured to receive the first disaster recovery data from the first gateway control plane device;
the processing unit is further configured to store the first disaster recovery data.
16. The access and mobility management device of claim 15,
the sending unit is further configured to backup the first disaster recovery data to a second access and mobile management device.
17. The utility model provides a gateway control plane equipment, its characterized in that, gateway control plane equipment is first gateway control plane equipment, first gateway control plane equipment includes receiving element and transmitting element, wherein:
the receiving unit is configured to receive a third message from a first access and mobility management device, where the third message includes second indication information and an identifier of a terminal device, where the second indication information is used to indicate the first gateway control plane device to send first disaster recovery data corresponding to the terminal device to the first access and mobility management device, and the first disaster recovery data includes a network protocol IP address of the terminal device and a gateway user plane device activated by the terminal device; the first disaster recovery data is used for recovering the session of the terminal equipment on the gateway user plane equipment when the first gateway control plane equipment is determined to be in failure;
the sending unit sends the first disaster recovery data to the first access and mobile management device.
18. The gateway control plane apparatus of claim 17, wherein the third message further includes addressing information associated with the first disaster recovery data;
the sending unit is further configured to send the addressing information and the identifier of the terminal device to the gateway user plane device, where the addressing information is used to obtain the first disaster recovery data when the gateway user plane device receives downlink data corresponding to the terminal device and the first gateway control plane device fails.
19. The gateway control plane device is characterized in that the gateway control plane device is a second gateway control plane device, and the second gateway control plane device comprises 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 triggered when the first access and mobility management device receives a service request of a terminal device and determines that a first gateway control plane device fails, where the first message includes first disaster tolerance data corresponding to the terminal device, and the first disaster tolerance data includes a network protocol IP address of the terminal device and a gateway user plane device activated by the terminal device; the first gateway control plane device is used for managing the session of the terminal device on the gateway user plane device;
and the processing unit is configured to recover, according to the first disaster recovery data, a session of the terminal device on the gateway user plane device.
20. The gateway control plane apparatus of claim 19, wherein the first message is a create session request or a traffic message; the service message is used for requesting 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.
21. A communications system 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 the access and mobility management device of any of claims 11 to 16, the first gateway control plane device is the gateway control plane device of claim 17 or 18, and the second gateway control plane device is the gateway control plane device of claim 19 or 20.
22. A computer storage medium having stored thereon instructions that, when executed on a processor, cause the processor to perform the method of gateway device disaster recovery of any of claims 1 to 6 or claims 7 to 8 or claims 9 to 10.
CN201910901318.XA 2019-09-23 2019-09-23 Disaster recovery method for gateway equipment and communication equipment Active CN112543468B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201910901318.XA CN112543468B (en) 2019-09-23 2019-09-23 Disaster recovery method for gateway equipment and communication equipment
PCT/CN2020/115066 WO2021057526A1 (en) 2019-09-23 2020-09-14 Disaster recovery method for gateway device, and communication device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910901318.XA CN112543468B (en) 2019-09-23 2019-09-23 Disaster recovery method for gateway equipment and communication equipment

Publications (2)

Publication Number Publication Date
CN112543468A CN112543468A (en) 2021-03-23
CN112543468B true CN112543468B (en) 2022-11-18

Family

ID=75013047

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910901318.XA Active CN112543468B (en) 2019-09-23 2019-09-23 Disaster recovery method for gateway equipment and communication equipment

Country Status (2)

Country Link
CN (1) CN112543468B (en)
WO (1) WO2021057526A1 (en)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115150857A (en) * 2021-03-31 2022-10-04 华为技术有限公司 Gateway fault recovery method, system and device
CN115529220A (en) * 2021-06-08 2022-12-27 中国移动通信集团重庆有限公司 Communication gateway disaster tolerance system and method
CN117014297A (en) * 2022-04-28 2023-11-07 华为技术有限公司 User plane management method, control plane device and user plane device
CN115297569B (en) * 2022-10-08 2023-06-02 北京云智软通信息技术有限公司 Communication method, node, device and storage medium
CN115623009B (en) * 2022-12-19 2023-03-28 南京赛宁信息技术有限公司 Active defense gateway visitor data backup and node online capacity expansion method and system

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101170553B (en) * 2006-10-24 2011-07-20 华为技术有限公司 Method and device for realizing Internet protocol multi-media sub-system disaster tolerance
CN104284359B (en) * 2014-06-17 2018-10-02 南京邮电大学 Trans-regional disaster tolerance system and control method under a kind of EPC networks
CN105338560B (en) * 2014-08-07 2019-02-26 中国电信股份有限公司 Gateway disaster recovery method, equipment and system
CN105357701B (en) * 2014-08-20 2018-10-19 中国电信股份有限公司 A kind of LTE network gateway pond group disaster recovery method, equipment and system
CN112866004B (en) * 2018-08-23 2024-04-12 华为技术有限公司 Control plane equipment switching method and device and transfer control separation system

Also Published As

Publication number Publication date
WO2021057526A1 (en) 2021-04-01
CN112543468A (en) 2021-03-23

Similar Documents

Publication Publication Date Title
CN112543468B (en) Disaster recovery method for gateway equipment and communication equipment
CN109246770B (en) Switching method, terminal equipment and network equipment
EP3755112B1 (en) Session management method and system
CN107959918B (en) Session management method, mobility management function and session management function
US9282476B2 (en) Communication control system, communication control device, and communication control method
CN102355743B (en) Management method and management device for UE (User Equipment) context information
WO2018166328A1 (en) Information processing method, apparatus, computer readable storage medium and electronic device
US11057813B2 (en) Method and apparatus for transmitting downlink data
WO2019223478A1 (en) Information processing method and apparatus, network element and storage medium
JP6128221B2 (en) COMMUNICATION PROCESSING SYSTEM, COMMUNICATION PROCESSING METHOD, COMMUNICATION CONTROL DEVICE, AND THEIR CONTROL METHOD AND CONTROL PROGRAM
KR102316348B1 (en) Communication method, network device and terminal device
WO2020164470A1 (en) Communication method, apparatus, and system
CN110856213B (en) Method and device for switching data transmission modes, storage medium and electronic equipment
CN103051484B (en) Session service processing method, system and Session Border Controll
CN112291803A (en) Communication method, terminal equipment and computer readable storage medium
CN104883706A (en) Method and device for processing paging failure
CN114125963A (en) Radio Resource Control (RRC) connection reestablishment method and device
CN111757555B (en) Connection processing method and device
CN114727324B (en) Network disaster recovery processing method and device, storage medium and electronic equipment
CN114071589B (en) Link switching indication method, device, apparatus and storage medium
US20220182907A1 (en) Base station, control method, and storage medium
EP4254996A1 (en) Shared cu up address management
WO2018186270A1 (en) Communication system
CN117255131A (en) Method, device, equipment and readable medium for carrying out service request based on slice
CN118075095A (en) Data transmission method and related device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant