Nothing Special   »   [go: up one dir, main page]

WO2019184923A1 - 一种信息备份方法及相关设备 - Google Patents

一种信息备份方法及相关设备 Download PDF

Info

Publication number
WO2019184923A1
WO2019184923A1 PCT/CN2019/079782 CN2019079782W WO2019184923A1 WO 2019184923 A1 WO2019184923 A1 WO 2019184923A1 CN 2019079782 W CN2019079782 W CN 2019079782W WO 2019184923 A1 WO2019184923 A1 WO 2019184923A1
Authority
WO
WIPO (PCT)
Prior art keywords
cloud
standby
master
master device
cloud device
Prior art date
Application number
PCT/CN2019/079782
Other languages
English (en)
French (fr)
Inventor
张小平
张耀坤
赵全喜
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP19774599.5A priority Critical patent/EP3764619B1/en
Publication of WO2019184923A1 publication Critical patent/WO2019184923A1/zh
Priority to US17/036,705 priority patent/US11989100B2/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G06F11/1464—Management of the backup or restore process for networked environments
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/16—Threshold monitoring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/101—Server selection for load balancing based on network conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection

Definitions

  • the present application relates to the field of communications technologies, and in particular, to an information backup method and related devices.
  • RUI multi-machine backup technology has appeared.
  • RUI multi-machine backup technology has been implemented on the existing network in large-scale applications, such as RUI backup in the field of Broadband Remote Access Server (BRAS) and IP Radio Access Network (IPRAN). Address Resolution Protocol (ARP) RUI backup, etc.
  • BRAS Broadband Remote Access Server
  • IPRAN IP Radio Access Network
  • ARP Address Resolution Protocol
  • the Virtual Router Redundancy Protocol (VRRP) is used to negotiate which router is the master device and which router is the standby device.
  • the master device is configured to implement traffic forwarding between the user side and the network side, and the standby device is configured to back up user information.
  • the master device sends the user information of the user device to the standby device through the Remote Backup Service (RBS) channel.
  • RBS Remote Backup Service
  • the backup is performed.
  • FIG. 1-b when the communication failure between the user equipment and the master device is detected by the Bidirectional Forwarding Detection (BFD) technology, the backup user information may be used.
  • BFD Bidirectional Forwarding Detection
  • the user equipment is quickly switched to the standby device.
  • the standby device takes over the traffic from the primary device to forward traffic to the user device. This ensures that the user service is uninterrupted.
  • the continuity of the user service will be affected. For example, for Router 1 and Router 2, when Router 1 fails to recover and meets the WTR setting value, Router 1 will be restored to the primary device by the standby device, and Router 2 will be restored to the standby device by the primary device. Before the WTR setting value is reached, the router 2 is still the master device, it will back up the user information to the router 1. If the backup speed between the router 1 and the router 2 is slow or the RBS channel between the two is delayed, the router 2 cannot complete the user before the WTR. Information is backed up, which affects the continuity of these user services.
  • the embodiment of the present application provides an information backup method and related equipment, which can ensure continuity of user services.
  • the embodiment of the present application provides the following technical solutions:
  • an embodiment of the present application provides an information backup method, where the method is applied to a communication system, where the communication system includes a master device, a standby device, and a cloud device, where the method is performed by the master device;
  • the method includes: the primary device sends a first identity notification to the cloud device, where the first identity notification is that the primary device has a notification of a primary device identity; and the primary device determines a communication state of the cloud device; Uploading, by the master device, the acquired first user information to the cloud device, where the communication status of the cloud device is normal; wherein the first user information is stored by the cloud device and provided to the And the first user information is information to be backed up of the user equipment that is online from the master device when the communication state of the cloud device is normal.
  • the master device when the communication status of the cloud device is normal, if the user device is online from the master device, the master device generates the information to be backed up of the user device and uploads the information to the cloud device, so that the standby device can be from the cloud.
  • the device obtains the information to be backed up for backup. It can be seen that, because the master device backs up information to the standby device through the cloud device, the device can prevent the master device from directly backing up information to the standby device. In some scenarios, for example, the master device and the standby device. The relationship is confusing, resulting in a problem of discontinuity in user business.
  • the method further includes: when the master device determines that the communication state of the cloud device is abnormal, and the master device and the standby device can communicate normally, The obtained second user information is sent to the standby device for backup; wherein the second user information is information to be backed up of the user equipment that is online from the master device when the communication state of the cloud device is abnormal.
  • the master device when the communication status of the cloud device is abnormal, that is, the data backup cannot be implemented by the cloud device, if the master device and the standby device can communicate normally, the master device can directly back up the information to the standby device. To achieve local backup, which improves the reliability of backup work.
  • the determining, by the master device, the communication status of the cloud device includes: sending, by the master device, a disconnection timeout between the cloud device and the cloud device An inquiry message, wherein the first inquiry message is used to query whether a disconnection timeout occurs between the standby device and the cloud device; and the primary device determines, according to the response message received from the standby device, The communication status of the cloud device.
  • the master device may determine whether the backup device has a timeout timeout with the cloud device, so that the master device can determine the cloud according to the response message of the standby device. Whether the communication status of the device is abnormal.
  • the determining, by the master device, the communication status of the cloud device according to the response message received from the standby device includes: receiving, by the master device, the first returned by the standby device Responding to the message, determining that the communication status of the cloud device is abnormal, wherein the first response message is used to notify a disconnection timeout between the standby device and the cloud device; and sending the acquired second user information to Before the backup device performs the backup, the method further includes: the master device starts a local backup mechanism between the master device and the standby device.
  • the master device can determine that the communication state of the cloud device is abnormal.
  • the primary device can initiate a local backup mechanism and perform a local backup.
  • the determining, by the master device, the communication status of the cloud device according to the response message received from the standby device includes: receiving, by the master device, the second returned by the standby device Responding to the message, determining that the communication status of the cloud device is normal; wherein the second response message is used to notify that the backup device does not have a link timeout between the standby device and the cloud device; Performing a link-breaking between the device and the cloud device; the master device sends the obtained third user information to the cloud device in batches after the link-breaking is successfully performed, where the third user information is The cloud device is stored and provided to the standby device, and the third user information is online from the master device after the master device is disconnected from the cloud device and before the broken link is successfully reestablished.
  • the master device can determine that the communication state of the cloud device is normal.
  • the main device can complete the broken link reconstruction with the cloud device, and realize the cloud backup after the broken link is successfully reconstructed.
  • the determining, by the master device, the communication status of the cloud device includes: receiving, by the master device, a first notification message sent by the standby device, where the first notification message is used Notifying that the link timeout occurs between the backup device and the cloud device; after receiving the first notification message, the master device determines the cloud device according to the link situation between the master device and the cloud device Communication status.
  • the master device may notify the master device of the situation, so that after receiving the notification, the master device may determine according to the link between the user and the cloud device. Whether the communication status of the cloud device is abnormal.
  • the master device determines a communication status of the cloud device according to a link situation between the master device and the cloud device, including: if the master device determines the master device and the If the link timeout occurs between the cloud devices, the communication status of the cloud device is abnormal.
  • the method further includes: after the second user information is sent to the backup device for backup, the method further includes: A local backup mechanism between the master device and the standby device.
  • the master device can determine that the communication state of the cloud device is abnormal.
  • the primary device can initiate a local backup mechanism and perform a local backup.
  • the master device determines the communication status of the cloud device according to the link status of the master device and the cloud device, including: if the master device determines that the cloud device is If the link timeout occurs, the communication state of the cloud device is determined to be normal.
  • the method further includes: the master device notifying the standby device to wait for completion of the broken link reestablishment with the cloud device.
  • the master device can determine that the communication state of the cloud device is normal.
  • the master device can notify the backup device and the cloud device to complete the broken link re-establishment, so that the standby device can back up data from the cloud device after the broken link is successfully reconstructed.
  • the master device determines the communication status of the cloud device, including: the master device receives a second query message sent by the standby device, and the second query message is the standby device The device determines that a chain break timeout occurs between the cloud device and the second query message is used to query whether a link timeout occurs between the master device and the cloud device; the master device is receiving After the second query message, the communication status of the cloud device is determined according to the link status of the master device and the cloud device.
  • the standby device if the standby device first detects that a broken link timeout occurs with the cloud device, it queries whether the primary device also has a broken link timeout with the cloud device, so that the primary device can be based on the link between the primary device and the cloud device. Determine whether the communication status of the cloud device is abnormal.
  • the master device determines the communication status of the cloud device according to the link status of the master device and the cloud device, including: if the master device determines that the cloud device is If the link timeout occurs, the communication status of the cloud device is abnormal.
  • the method further includes: sending, by the master device, the standby device a third response message, so that the standby device initiates a local backup mechanism between the primary device and the standby device after receiving the third response message, where the third response message is the primary device and A link timeout occurs between the cloud devices.
  • the master device can determine that the communication state of the cloud device is abnormal.
  • the master device can notify the standby device of this situation. After receiving the notification, the standby device can start the local backup mechanism and perform local backup.
  • the master device determines the communication status of the cloud device according to the link status of the master device and the cloud device, including: if the master device determines that the cloud device is If the link timeout occurs, the communication status of the cloud device is determined to be normal.
  • the method further includes: the master device sending a fourth response message to the standby device, so that the standby device receives the fourth response.
  • the network device is configured to complete the broken link reestablishment with the cloud device, where the fourth response message is that no broken link timeout occurs between the primary device and the cloud device.
  • the master device can determine that the communication state of the cloud device is normal.
  • the master device can notify the backup device and the cloud device to complete the broken link re-establishment, so that the standby device can back up data from the cloud device after the broken link is successfully reconstructed.
  • the determining, by the master device, the communication status of the cloud device includes: sending, by the master device, the device to the standby device after detecting a timeout delay between the cloud device and the cloud device a second notification message, wherein the second notification message is used to notify the backup device that a broken link timeout occurs between the primary device and the cloud device; and the primary device is configured to target the second notification according to the standby device The response of the message determines the communication status of the cloud device.
  • the master device may notify the standby device of the situation, and the master device may determine the communication state of the cloud device according to the response result of the standby device to the notification. Is it abnormal?
  • the determining, by the master device, the communication status of the cloud device according to the response of the standby device to the second notification message includes: if the master device determines that the standby device is started A local backup mechanism between the master device and the standby device determines that the communication state of the cloud device is abnormal.
  • the standby device starts a local backup mechanism, so that the master device can determine The communication status of the cloud device is abnormal, so that local backup can be performed.
  • the determining, by the master device, the communication status of the cloud device according to the response of the standby device to the second notification message includes: receiving, by the master device, the standby device And the notification response message is used to determine that the communication status of the cloud device is normal; wherein the notification response message is used to notify the master device to wait for completion of a broken link reestablishment with the cloud device; the method further includes: Performing a broken link between the master device and the cloud device; the master device sends the obtained third user information to the cloud device in batches after the link chain is successfully reestablished, where the third user information is The cloud device is stored and provided to the standby device, and the third user information is online from the master device after the master device is disconnected from the cloud device and before the broken link is successfully reestablished.
  • the primary device can complete the broken link reconstruction with the cloud device, and is broken. Cloud backup is implemented after successful chain reconstruction.
  • the determining, by the master device, that the communication status of the cloud device is abnormal includes: if the master device determines that the link quality between the master device and the cloud device is lower than a pre- If the quality threshold is set, and/or the link quality between the standby device and the cloud device is lower than a preset quality threshold, the communication state of the cloud device is determined to be abnormal.
  • the master device determines that one of the self and/or the standby device has poor link quality, it can determine that the communication state of the cloud device is abnormal. In this case, the local backup mechanism can be started and localized. Backup.
  • the method further includes: the master device determines that the master device and the cloud device cannot communicate normally, and the master device and the standby device cannot be normal. In the case of communication, the identity of the master device of the master device is switched to the identity of the standby device. In the embodiment of the present application, if the master device cannot communicate with the cloud device and the standby device at the same time, the master device can perform neither the cloud backup nor the local backup. In this case, the master device can perform the master/slave identity switch, thereby enabling The backup device that implements the cloud backup function is used as the master device to perform cloud backup, thereby ensuring the reliability of the backup work.
  • the master device and the cloud device cannot communicate normally, including: a link timeout occurs between the master device and the cloud device, or the master device and the device
  • the link quality between the cloud devices is lower than the preset quality threshold.
  • the master device and the cloud device cannot communicate normally, and may be represented as a broken link timeout, and may also be characterized by poor link quality.
  • the master device and the standby device cannot communicate normally, including: a link timeout occurs between the master device and the standby device, or the master device and the device
  • the link quality between the devices is lower than the preset quality threshold.
  • the primary device and the standby device cannot communicate normally, and may be represented as a broken link timeout, and may also be characterized by poor link quality.
  • the embodiment of the present application provides an information backup method, where the method is applied to a communication system, where the communication system includes a master device, a standby device, and a cloud device, where the method is performed by the cloud device;
  • the method includes: the cloud device receiving a first identity notification sent by the master device, and a second identity notification sent by the standby device, where the first identity notification is a notification that the master device has a master device identity, The second identity notification is that the standby device has a notification of the device identity;
  • the cloud device receives and stores the first user information uploaded by the master device, and provides the first user information to the standby device;
  • the first user information is uploaded when the master device determines that the communication state of the cloud device is normal, and the first user information is from the case when the communication state of the cloud device is normal.
  • Information to be backed up by the user equipment that is online.
  • the master device when the communication status of the cloud device is normal, if the user device is online from the master device, the master device generates the information to be backed up of the user device and uploads the information to the cloud device, so that the standby device can be from the cloud.
  • the device obtains the information to be backed up for backup. It can be seen that the backup device backs up information to the standby device through the cloud device, which avoids the problem that the user service is discontinuous caused by the backup device directly backing up information to the standby device.
  • an embodiment of the present application provides an information backup method, where the method is applied to a communication system, where the communication system includes a master device, a backup device, and a cloud device, where the method is performed by the standby device;
  • the method includes: the standby device sends a second identity notification to the cloud device, where the second identity notification is that the standby device has a notification of the standby device identity; and the standby device obtains the first user information from the cloud device Performing a backup; wherein, the first user information is that the primary device determines that the communication state of the cloud device is normal, and is uploaded to the cloud device, and the first user information is when the cloud device is The information to be backed up of the user equipment that is online from the master device in the case where the communication state is normal.
  • the master device when the communication status of the cloud device is normal, if the user device is online from the master device, the master device generates the information to be backed up of the user device and uploads the information to the cloud device, so that the standby device can be from the cloud.
  • the device obtains the information to be backed up for backup. It can be seen that the backup device backs up information to the standby device through the cloud device, which avoids the problem that the user service is discontinuous caused by the backup device directly backing up information to the standby device.
  • the method further includes: when the communication status of the cloud device is abnormal, the standby device receives the second user information sent by the primary device for backup; wherein The second user information is information to be backed up by the user equipment that is online from the master device when the communication state of the cloud device is abnormal; the second user information is that the master device determines the communication of the cloud device The status is abnormal and is sent if the master device and the standby device can communicate normally.
  • the communication status of the cloud device is abnormal, that is, the data backup cannot be implemented by the cloud device, if the master device and the standby device can communicate normally, the master device can directly back up the information to the standby device. To achieve local backup, which improves the reliability of backup work.
  • the method further includes: if the standby device receives the first query message sent by the master device, returning a response message to the master device; wherein the first query The message is sent by the master device after detecting a broken link timeout with the cloud device, and the first query message is used to query whether a link timeout occurs between the standby device and the cloud device.
  • the response message returned by the standby device is used to enable the master device to determine the communication status of the cloud device.
  • the master device may determine whether the backup device has a timeout timeout with the cloud device, so that the master device can determine the cloud according to the response message of the standby device. Whether the communication status of the device is abnormal.
  • the standby device returns a response message to the primary device, including: the standby device returns a first response message to the primary device; wherein the first response message is used to notify A link timeout occurs between the standby device and the cloud device, so that the master device determines that the communication state of the cloud device is abnormal after a link timeout occurs between the standby device and the cloud device, and After the communication status of the cloud device is abnormal, the local backup mechanism between the primary device and the standby device is started; the standby device receives the second user information sent by the primary device for backup, including: The standby device receives the second user information sent by the primary device after starting the local backup mechanism for backup.
  • the master device can determine that the communication state of the cloud device is abnormal.
  • the device can initiate a local backup mechanism and perform a local backup.
  • the standby device returns a response message to the primary device, including: the standby device returns a second response message to the primary device; wherein the second response message is used to notify A link-timeout has not occurred between the standby device and the cloud device, so that the master device determines that the communication state of the cloud device is normal after the link-timeout has not occurred between the standby device and the cloud device. And performing a broken link re-establishment between the main device and the cloud device after determining that the communication state of the cloud device is normal, and causing the third device to be acquired after the main device is successfully reconfigured.
  • the third user information is stored by the cloud device and provided to the standby device, and the third user information is generated by the master device and the cloud device Information to be backed up by the user equipment that is online from the master device after the chain is broken and before the broken link is successfully reconstructed.
  • the master device can determine that the communication state of the cloud device is normal. The main device can complete the broken link reconstruction with the cloud device, and realize the cloud backup after the broken link is successfully reconstructed.
  • the method further includes: the standby device sending a first notification message to the primary device, where the first notification message is used to notify the standby device and the cloud device A link timeout occurs between the master device to determine that the communication state of the cloud device is abnormal after a link timeout occurs between the master device and the cloud device.
  • the master device may notify the master device of the situation, so that after receiving the notification, the master device may determine according to the link between the user and the cloud device. Whether the communication status of the cloud device is abnormal.
  • the method further includes: the standby device receiving a reconfiguration waiting notification sent by the primary device, where the reconfiguration waiting notification is used to notify the standby device to wait with the cloud device Performing a broken link re-establishment, the re-establishment waiting notification is sent after the main device determines that the communication state of the cloud device is normal, and the communication state is normal, the main device determines that the non-occurrence occurs with the cloud device Determined after the chain break timeout.
  • the master device can determine that the communication state of the cloud device is normal. The master device can notify the backup device and the cloud device to complete the broken link re-establishment, so that the standby device can back up data from the cloud device after the broken link is successfully reconstructed.
  • the method further includes: after the standby device determines that a broken link timeout occurs with the cloud device, sending a second query message to the primary device, where the second The query message is used to query whether a link timeout occurs between the master device and the cloud device; if the standby device receives the third response message returned by the master device, the device learns according to the third response message.
  • the communication status of the cloud device is abnormal, and the local backup mechanism between the master device and the standby device is started, where the third response message is used to notify that the master device and the cloud device are disconnected.
  • the backup device receives the second user information sent by the master device for backup, the backup device receives the second user information sent by the master device for backup after successfully starting the local backup mechanism.
  • the backup device if the backup device first detects that a broken link timeout occurs with the cloud device, it queries whether the primary device also has a broken link timeout with the cloud device; if a link timeout occurs between the primary device and the cloud device, The backup device has a timeout between the backup device and the cloud device.
  • the master device can determine that the communication status of the cloud device is abnormal. In this case, the master device can notify the standby device of the situation. After receiving the notification, the standby device can Start the local backup mechanism and perform a local backup.
  • the method further includes: if the standby device receives the fourth response message returned by the primary device, waiting for completion of the broken link reconstruction with the cloud device, where the The four response message is used to notify that the link timeout has not occurred between the master device and the cloud device.
  • the master device can determine that the communication state of the cloud device is normal. The master device can notify the backup device and the cloud device to complete the broken link re-establishment, so that the standby device can back up data from the cloud device after the broken link is successfully reconstructed.
  • the method further includes: if the standby device receives the second notification message sent by the primary device, responding to the second notification message; wherein, the second device The notification message is sent by the master device after detecting a disconnection timeout with the cloud device, and the second notification message is used to notify the standby device between the master device and the cloud device. A link timeout occurs; the response of the standby device to the second notification message causes the master device to determine a communication state of the cloud device.
  • the master device may notify the standby device of the situation, and the master device may determine the communication state of the cloud device according to the response result of the standby device to the notification. Is it abnormal?
  • the standby device responds to the second notification message, including: the standby device starts a local backup mechanism between the primary device and the standby device, so that the primary device After the local backup mechanism is started, the device determines that the communication status of the cloud device is abnormal.
  • the standby device receives the second user information sent by the primary device for backup, including: the standby device successfully starts the local device. After the backup mechanism, the second user information sent by the primary device is received for backup.
  • the standby device starts a local backup mechanism, so that the master device can determine The communication status of the cloud device is abnormal, so that local backup can be performed.
  • the standby device responds to the second notification message, including: the standby device returns a notification response message to the primary device; wherein the notification response message is used to notify the
  • the master device waits to complete the link-breaking reestablishment with the cloud device, so that the master device sends the acquired third user information to the cloud device in batches after the link-synchronization is successfully performed;
  • the information is stored by the cloud device and provided to the standby device, and the third user information is from the master after the master device is disconnected from the cloud device and before the broken link is successfully reestablished.
  • the primary device can complete the broken link reconstruction with the cloud device, and is broken. Cloud backup is implemented after successful chain reconstruction.
  • the method further includes: if the standby device determines that a link quality between the standby device and the cloud device is lower than a preset quality threshold, and/or determines the primary The link quality between the device and the cloud device is lower than a preset quality threshold, and a local backup mechanism between the master device and the standby device is started, so that the master device is started in the local backup mechanism. Then, it is determined that the communication state of the cloud device is abnormal.
  • the standby device determines that one of the user and/or the master device has poor link quality
  • the local backup mechanism can be started. After the local backup mechanism is started, the primary device can determine the cloud device. The communication status is abnormal, and at this time, a local backup can be performed.
  • the method further includes: the standby device determines that the standby device and the cloud device can communicate normally, and the standby device cannot communicate with the master device.
  • the device identity of the standby device is switched to the identity of the master device.
  • the standby device in the case that the primary device cannot communicate with the cloud device and the standby device at the same time, if the standby device can communicate with the cloud device, the standby device can perform cloud backup.
  • the backup function is used to make the cloud backup as the master device, thus ensuring the reliability of the backup work.
  • the standby device and the master device cannot communicate normally, including: a link-timeout occurs between the standby device and the master device, or the standby device and the master device
  • the link quality between devices is lower than the preset quality threshold.
  • the backup device and the master device cannot communicate normally, and may be represented as a broken link timeout, and may also be characterized by poor link quality.
  • the embodiment of the present application provides a master device, where the master device includes: a notification sending module, configured to send a first identity notification to a cloud device, where the first identity notification is a notification that the primary device has a primary device identity a state determining module, configured to determine a communication state of the cloud device; and a cloud backup module, configured to: upload the obtained first user information to the cloud device, if the communication state of the cloud device is normal;
  • the first user information is stored by the cloud device and provided to the standby device, and the first user information is a user device that is online from the master device when the communication state of the cloud device is normal.
  • the information to be backed up where the master device includes: a notification sending module, configured to send a first identity notification to a cloud device, where the first identity notification is a notification that the primary device has a primary device identity a state determining module, configured to determine a communication state of the cloud device; and a cloud backup module, configured to: upload the obtained first user information to the cloud device, if the
  • the master device further includes: a local backup module, configured to determine that a communication state of the cloud device is abnormal, and that the master device and the standby device can communicate normally
  • the second user information is sent to the standby device for backup; wherein the second user information is a user equipment that is online from the master device when the communication state of the cloud device is abnormal. Back up information.
  • the status determining module includes: a query sending submodule, configured to send a first query message to the standby device after detecting a broken link timeout with the cloud device, The first query message is used to query whether a link timeout occurs between the standby device and the cloud device, and the first determining submodule is configured to determine, according to the response message received from the standby device, The communication status of the cloud device.
  • the first determining sub-module is specifically configured to: if the first response message returned by the standby device is received, determining that the communication status of the cloud device is abnormal, where the first The response message is used to notify a disconnection timeout between the standby device and the cloud device; the local backup module is further configured to: before sending the acquired second user information to the standby device for backup, starting the location A local backup mechanism between the master device and the standby device.
  • the first determining submodule is specifically configured to: if the second response message returned by the standby device is received, determining that the communication state of the cloud device is normal; wherein the second The response message is used to notify that there is no link timeout between the standby device and the cloud device; the master device further includes: a first link-breaking reconstruction module, configured to perform link-breaking reconstruction with the cloud device; a first batch backup module, configured to send the obtained third user information to the cloud device in batches, where the third user information is stored by the cloud device and provided to the The device is described, and the third user information is information to be backed up by the user equipment that is online from the master device after the master device and the cloud device are disconnected.
  • the status determining module includes: a notification receiving submodule, configured to receive a first notification message sent by the standby device, where the first notification message is used to notify the standby device And the second determining submodule is configured to determine, according to the link situation between the primary device and the cloud device, the cloud device after the receiving the first notification message Communication status.
  • the second determining sub-module is specifically configured to determine that the communication status of the cloud device is abnormal if a link timeout occurs between the primary device and the cloud device;
  • the local backup module is further configured to start a local backup mechanism between the master device and the standby device before sending the obtained second user information to the backup device for backup.
  • the second determining sub-module is specifically configured to determine that the communication state of the cloud device is normal if the disconnection timeout does not occur between the cloud device and the cloud device;
  • the method further includes: a re-establishment notification module, configured to notify the standby device to wait for completion of a broken link reestablishment with the cloud device.
  • the status determining module includes: a query receiving submodule, configured to receive a second query message sent by the standby device, where the second query message is determined by the standby device And sending, by the cloud device, a disconnection timeout, and the second query message is used to query whether a link timeout occurs between the master device and the cloud device; and the third determining submodule is configured to receive After the second query message, the communication status of the cloud device is determined according to the link status of the primary device and the cloud device.
  • the third determining sub-module is specifically configured to determine that the communication status of the cloud device is abnormal if a disconnection timeout occurs between the cloud device and the cloud device;
  • the first response sending module is configured to: before the cloud backup module sends the acquired second user information to the standby device for backup, send a third response message to the standby device, so that the standby device receives After the third response message is sent, the local backup mechanism between the master device and the standby device is started, where the third response message is a link timeout between the master device and the cloud device.
  • the third determining sub-module is specifically configured to determine that a communication state of the cloud device is normal if a disconnection timeout occurs between the cloud device and the cloud device;
  • the second response sending module is configured to send a fourth response message to the standby device, so that the standby device waits to complete the broken link reconstruction with the cloud device after receiving the fourth response message, where The fourth response message is that no link timeout occurs between the primary device and the cloud device.
  • the state determining module includes: a notification sending submodule, configured to send a second notification message to the standby device after detecting a broken link timeout with the cloud device, The second notification message is used to notify the backup device that a broken link timeout occurs between the primary device and the cloud device, and the fourth determining submodule is configured to use the standby device for the second notification.
  • the response of the message determines the communication status of the cloud device.
  • the fourth determining submodule is specifically configured to determine the cloud device if it is determined that the standby device has started a local backup mechanism between the primary device and the standby device.
  • the communication status is abnormal.
  • the fourth determining sub-module is specifically configured to: if the notification response message returned by the standby device is received, determining that the communication state of the cloud device is normal; wherein the notification response is The message is used to notify the master device to wait for the broken link to be reestablished with the cloud device; the master device further includes: a second link-breaking reconstruction module, configured to perform link-breaking reconstruction with the cloud device; The second batch backup module is configured to send the obtained third user information to the cloud device in batches, where the third user information is stored by the cloud device and provided to the standby device. And the third user information is information to be backed up by the user equipment that is online from the master device after the master device and the cloud device are disconnected.
  • the status determining module is specifically configured to: if it is determined that a link quality between the primary device and the cloud device is lower than a preset quality threshold, and/or determine the standby device If the link quality between the cloud device and the cloud device is lower than a preset quality threshold, determining that the communication state of the cloud device is abnormal.
  • the master device further includes: an identity switching module, configured to determine that the master device and the cloud device cannot communicate normally, and the master device and the standby device If the communication cannot be performed normally, the identity of the master device of the master device is switched to the identity of the standby device.
  • an identity switching module configured to determine that the master device and the cloud device cannot communicate normally, and the master device and the standby device If the communication cannot be performed normally, the identity of the master device of the master device is switched to the identity of the standby device.
  • the master device and the cloud device cannot communicate normally, including: a link timeout occurs between the master device and the cloud device, or the master device and the device The link quality between the cloud devices is lower than the preset quality threshold.
  • the master device and the standby device cannot communicate normally, including: a link timeout occurs between the master device and the standby device, or the master device and the device The link quality between the devices is lower than the preset quality threshold.
  • the embodiment of the present application provides a cloud device, where the cloud device includes: a notification receiving module, configured to receive a first identity notification sent by the master device, and a second identity notification sent by the standby device, where the first identity is The notification is that the primary device has a notification of the identity of the primary device, the second identity notification is that the standby device has a notification of the identity of the standby device, and the cloud backup module is configured to receive and store the first user information uploaded by the primary device.
  • the first user information is uploaded when the master device determines that the communication state of the cloud device is normal, and the first user is The information is information to be backed up of the user equipment that is online from the master device when the communication state of the cloud device is normal.
  • the embodiment of the present application provides a standby device, where the standby device includes: a notification sending module, configured to send a second identity notification to a cloud device, where the second identity notification is that the standby device has a standby device identity
  • the cloud backup module is configured to obtain the first user information from the cloud device for backup; wherein the first user information is that the master device determines that the communication state of the cloud device is normal, and uploads to the cloud device.
  • the information stored in the cloud device is the information to be backed up by the user equipment that is online from the master device when the communication state of the cloud device is normal.
  • the standby device further includes: a local backup module, configured to receive the second user information sent by the primary device for backup if the communication status of the cloud device is abnormal;
  • the second user information is information to be backed up by the user equipment that is online from the master device when the communication state of the cloud device is abnormal; the second user information is that the master device determines the cloud
  • the communication status of the device is abnormal and is transmitted if the master device and the standby device can communicate normally.
  • the standby device further includes: a message returning module, configured to return a response message to the primary device if receiving the first query message sent by the primary device;
  • the first query message is sent after the master device detects that a link timeout occurs with the cloud device, and the first query message is used to query whether the standby device and the cloud device are generated.
  • the link-breaking timeout is sent; the response message returned by the standby device is used to enable the master device to determine the communication state of the cloud device.
  • the message returning module is specifically configured to return a first response message to the primary device, where the first response message is used to notify the standby device and the cloud device A link timeout occurs between the master device, and the master device determines that the communication state of the cloud device is abnormal after the link timeout occurs between the standby device and the cloud device, and determines that the communication state of the cloud device is abnormal. Then, the local backup mechanism is started between the master device and the standby device. The local backup module is configured to receive the second user information sent by the master device after the local backup mechanism is started to perform backup.
  • the message returning module is specifically configured to return a second response message to the primary device, where the second response message is used to notify the standby device and the cloud device.
  • the link timeout has not occurred, so that the master device determines that the communication state of the cloud device is normal after the link timeout has not occurred between the standby device and the cloud device, and determines the communication of the cloud device.
  • the master device and the cloud device are disconnected, and the third device is sent to the cloud device in batches after the link is successfully reestablished.
  • the third user information is stored by the cloud device and provided to the standby device, and the third user information is after the main device is disconnected from the cloud device and is in the broken link reconstruction. The information to be backed up of the user equipment that is online from the master device before the success.
  • the standby device further includes: a notification sending module, configured to send a first notification message to the primary device, where the first notification message is used to notify the standby device and the device A link timeout occurs between the cloud devices, so that the master device determines that the communication state of the cloud device is abnormal after a link timeout occurs between the master device and the cloud device.
  • a notification sending module configured to send a first notification message to the primary device, where the first notification message is used to notify the standby device and the device A link timeout occurs between the cloud devices, so that the master device determines that the communication state of the cloud device is abnormal after a link timeout occurs between the master device and the cloud device.
  • the standby device further includes: a notification receiving module, configured to receive a reconfiguration waiting notification sent by the main device, where the reconfiguration waiting notification is used to notify the standby device to wait for Performing a link-breaking re-establishment between the cloud devices, where the re-establishment wait notification is sent after the master device determines that the communication state of the cloud device is normal, and the communication state is normal, the master device determines that the cloud device is Determined after the timeout has not occurred.
  • a notification receiving module configured to receive a reconfiguration waiting notification sent by the main device, where the reconfiguration waiting notification is used to notify the standby device to wait for Performing a link-breaking re-establishment between the cloud devices, where the re-establishment wait notification is sent after the master device determines that the communication state of the cloud device is normal, and the communication state is normal, the master device determines that the cloud device is Determined after the timeout has not occurred.
  • the standby device further includes: a query sending module, configured to send a second query message to the master device after determining that a broken link timeout occurs with the cloud device, where The second query message is used to query whether a link timeout occurs between the master device and the cloud device.
  • the local backup module is specifically configured to: if receiving a third response message returned by the master device, according to The third response message is used to learn that the communication status of the cloud device is abnormal, and the local backup mechanism between the master device and the standby device is started. After the local backup mechanism is successfully started, the host device sends the The second user information is backed up, wherein the third response message is used to notify that a broken link timeout occurs between the primary device and the cloud device.
  • the standby device further includes: a link-breaking reconstruction module, configured to wait for completion of a broken link with the cloud device if receiving the fourth response message returned by the primary device, where The fourth response message is used to notify that the link timeout has not occurred between the master device and the cloud device.
  • a link-breaking reconstruction module configured to wait for completion of a broken link with the cloud device if receiving the fourth response message returned by the primary device, where The fourth response message is used to notify that the link timeout has not occurred between the master device and the cloud device.
  • the standby device further includes: a notification response module, configured to respond to the second notification message if receiving the second notification message sent by the primary device;
  • the second notification message is sent by the master device after detecting a disconnection timeout between the cloud device, and the second notification message is used to notify the standby device of the standby device and the cloud device.
  • a link timeout occurs between the devices; the response of the standby device to the second notification message causes the master device to determine a communication state of the cloud device.
  • the notification response module is specifically configured to start a local backup mechanism between the primary device and the standby device, so that the primary device determines after the local backup mechanism is started.
  • the communication status of the cloud device is abnormal.
  • the local backup module is configured to receive the second user information sent by the primary device for backup after the local backup mechanism is successfully started.
  • the notification response module is specifically configured to return a notification response message to the primary device, where the notification response message is used to notify the primary device to wait with the cloud device Performing the link-breaking reconstruction, so that the master device sends the acquired third user information to the cloud device in batches after the link-breaking is successfully performed; the third user information is stored by the cloud device and provided to the The device is described, and the third user information is information to be backed up by the user equipment that is online from the master device after the master device and the cloud device are disconnected.
  • the standby device further includes: the local backup module, configured to: if it is determined that a link quality between the standby device and the cloud device is lower than a preset quality threshold, and And determining that the link quality between the master device and the cloud device is lower than a preset quality threshold, starting a local backup mechanism between the master device and the standby device, so that the master device is in the After the local backup mechanism is started, it is determined that the communication status of the cloud device is abnormal.
  • the local backup module configured to: if it is determined that a link quality between the standby device and the cloud device is lower than a preset quality threshold, and And determining that the link quality between the master device and the cloud device is lower than a preset quality threshold, starting a local backup mechanism between the master device and the standby device, so that the master device is in the After the local backup mechanism is started, it is determined that the communication status of the cloud device is abnormal.
  • the standby device further includes: an identity switching module, configured to determine that the standby device and the cloud device can communicate normally, and between the standby device and the master device If the device does not communicate normally, the device identity of the standby device is switched to the identity of the master device.
  • an identity switching module configured to determine that the standby device and the cloud device can communicate normally, and between the standby device and the master device If the device does not communicate normally, the device identity of the standby device is switched to the identity of the master device.
  • the standby device and the master device cannot communicate normally, including: a link-timeout occurs between the standby device and the master device, or the standby device and the master device The link quality between devices is lower than the preset quality threshold.
  • the embodiment of the present application provides a master device, where the master device includes: a processor, a memory, a communication interface, and a bus; the processor, the communication interface, and the memory communicate with each other through the bus; the communication An interface for receiving and transmitting data; the memory for storing instructions; the processor for executing the instructions in the memory, performing the method of any of the preceding first aspects.
  • the embodiment of the present application provides a cloud device, where the cloud device includes: a processor, a memory, a communication interface, and a bus; the processor, the communication interface, and the memory communicate with each other through the bus; the communication An interface for receiving and transmitting data; the memory for storing instructions; the processor for executing the instructions in the memory, performing the method of any of the preceding second aspects.
  • the embodiment of the present application provides a standby device, where the master device includes: a processor, a memory, a communication interface, and a bus; the processor, the communication interface, and the memory communicate with each other through the bus; the communication An interface for receiving and transmitting data; the memory for storing instructions; the processor for executing the instructions in the memory, performing the method of any of the preceding third aspects.
  • the embodiment of the present application provides a communication system, where the communication system includes the master device of the fourth aspect, the cloud device of the fifth aspect, and the standby device of the sixth aspect, or the communication system includes the foregoing
  • an embodiment of the present application provides a computer readable storage medium, wherein the computer readable storage medium stores instructions that, when run on a computer, cause the computer to perform the methods described in the above aspects.
  • an embodiment of the present application provides a computer program product comprising instructions that, when run on a computer, cause the computer to perform the method described in the above aspects.
  • Figure 1-a is a schematic diagram of data flow direction of the existing communication system
  • Figure 1-b is a second schematic diagram of data flow of the existing communication system
  • FIG. 2 is a schematic structural diagram of an existing communication system
  • FIG. 3 is a schematic structural diagram of a communication system provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a data preparation process provided by an embodiment of the present application.
  • FIG. 5 is a schematic diagram of interaction of a normal information backup method according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of interaction of a local information backup method according to an embodiment of the present application.
  • 6-b is a second schematic diagram of interaction of a local information backup method according to an embodiment of the present application.
  • FIG. 7 is a third schematic diagram of interaction of a local information backup method according to an embodiment of the present application.
  • 7-b is a fourth interaction diagram of the local information backup method provided by the embodiment of the present application.
  • FIG. 8 is a fifth schematic diagram of interaction of a local information backup method according to an embodiment of the present application.
  • FIG. 8-b is a sixth schematic diagram of interaction of a local information backup method according to an embodiment of the present application.
  • 9-a is a seventh schematic diagram of interaction of a local information backup method according to an embodiment of the present application.
  • 9-b is a schematic diagram of an interaction diagram of a local information backup method according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a main device according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of a cloud device according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic structural diagram of a standby device according to an embodiment of the present disclosure.
  • FIG. 13 is a second schematic diagram of a composition of a master device according to an embodiment of the present disclosure.
  • FIG. 14 is a second schematic diagram of a composition of a cloud device according to an embodiment of the present disclosure.
  • FIG. 15 is a second schematic structural diagram of a standby device according to an embodiment of the present disclosure.
  • the embodiment of the present application provides an information backup method and related equipment, which can ensure continuity of user services.
  • FIG. 2 is a schematic structural diagram of an RUI multi-machine backup communication system provided by an embodiment of the present application.
  • Router-A and Router-B can be routers, and other devices that can back up user information, such as switches.
  • Router-A is the master device and Router-B is the standby device, the upstream and downstream traffic of the user device is forwarded through Router-A.
  • Router-A can back up the user to Router-B through the RBS channel.
  • Device information can be routers, and other devices that can back up user information, such as switches.
  • the RUI logical model is:
  • the master/slave protocol for example, VRRP, negotiates the master/slave relationship between the routers.
  • the same user service corresponds to one master device and one standby device. Backing up user information from the master device to the standby device for the user service;
  • the active/standby protocol is associated with the BFD deployment. It is used to quickly detect communication faults between the user equipment and the master device, and notify the upper-layer application when a fault occurs.
  • the master device advertises the address pool route to the network. After the user device goes online, the device can obtain the address from the address pool. The standby device revokes the corresponding address pool route. The traffic between the network and the user is forwarded through the master device.
  • the master device In the fault scenario, for example, when the interface 1 of the primary device fails, only the user service corresponding to the faulty interface 1 is switched to the standby device, but the master device also has other normal interfaces, such as interface 2, because interface 2 and faulty interface 1 Users share the same address pool. Therefore, the route of the address pool that has been advertised by the master device before the fault is not revoked.
  • the traffic of the user traffic corresponding to faulty interface 1 that is, the traffic between the network and the user, will arrive first.
  • the master device forwards traffic through the RBS channel to the standby device.
  • FIG. 3 is a schematic structural diagram of a communication system provided by an embodiment of the present application.
  • the communication system provided by the embodiment of the present application is a cloud device that is added to the communication system shown in FIG. 2.
  • the embodiment of the present application does not limit the type of the cloud device.
  • the cloud device may be a standardized network component. SNC) controller, server or network management device, etc.
  • Router-A and Router-B are the local branch devices of the cloud backup system.
  • the cloud device serves as the centralized storage device of the cloud backup system. When Router-A functions as the master device, it is used to upload user information to the cloud device. Router-B When the device is used as the backup device, it is used to obtain the user information from the cloud device for backup.
  • Router-A does not back up user information to Router-B. Only Router-A and/or Router-B communicate with the cloud device. When abnormal, Router-A may back up user information to Router-B. On Router-A and Router-B, Router-A is responsible for traffic forwarding, and Router-B is not responsible for traffic forwarding. That is to say, when Router-A is the master device, the user device will be forwarded. The device is connected to Router A. The traffic between the user equipment and the network is forwarded by Router-A. For details about the traffic forwarding mode, refer to the related information. It is not responsible for traffic forwarding of the user equipment, but needs to back up the user information of the user equipment.
  • preparation work 1 and preparation work 2 need to be completed in sequence.
  • Preparation 1 The master device and the standby device are negotiated through the master/slave protocol.
  • the negotiation object of the active/standby relationship is taken as an example for the router.
  • the communication system shown in Figure 3 includes multiple routers, it is necessary to negotiate which router is the master device and which router is the standby device through the master/slave protocol, such as VRRP. .
  • VRRP defines three states of the router, namely Initialize, Active, and Backup.
  • VRRP determines the role of each router based on the priority, that is, determines the primary device. And the standby device, the higher the priority, the more likely it becomes the master device.
  • each router in the initial creation of VRRP works in the Initialize state. If the priority of the router is less than 255, it will be switched from the Initialize state to the Backup state. After the timer expires, it will switch to the Master state.
  • the routers that switch to the master state first exchange the VRRP advertisement packets to learn the priorities of other routers.
  • the router in the backup state maintains the backup state if the priority of the master device in the VRRP advertisement packet is higher than or equal to the priority of the master device.
  • the priority of the master device is lower than its own priority.
  • the preemption mode is adopted, the master device is switched to the master state and becomes the master device.
  • the non-preemptive mode is adopted, the master device remains in the backup state.
  • Preparation 2 Make the cloud device aware that the primary device has the identity of the primary device and the standby device has the identity of the standby device.
  • S401 The primary device establishes a connection with the cloud device, and the standby device establishes a connection with the cloud device.
  • the master device and the standby device can communicate with the cloud through the Network Configuration Protocol (NETCONF) or the Simple Network Management Protocol (SNMP).
  • NETCONF Network Configuration Protocol
  • SNMP Simple Network Management Protocol
  • the primary device sends a first identity notification to the cloud device, where the first identity notification is that the primary device has the identity of the primary device identity, and the standby device sends the second identity notification to the cloud device, where the second identity notification is the standby device. Notification of the identity of the standby device.
  • the first identity notification may include the unique identifier of the master device and the identifier of the master device, such as the IP address of the master device and the “master”.
  • the first identity notification may include the unique identifier of the standby device and ID of the standby device, such as the IP address of the standby device and "standby”.
  • S403 The cloud device establishes a storage entry.
  • the cloud device After receiving the first identity notification, the cloud device establishes a storage entry for the primary device, such as the IP address of the primary device: the primary device. Similarly, after receiving the second identity notification, the cloud device establishes a storage entry for the standby device, for example, IP address of the device: standby.
  • S404 The master device and the standby device establish an RBS channel by using a three-way handshake.
  • the RBS channel is established between the master device and the standby device through the three-way handshake.
  • the local backup mechanism between the master device and the standby device is started, the information of the master device to the standby device is backed up through the RBS channel.
  • the three-way handshake process is specifically:
  • the master device sends a SYN packet to the standby device, and then waits for the standby device to confirm.
  • SYN (synchronous) is the handshake signal used when TCP/IP establishes a connection
  • the standby device is used.
  • the standby device After receiving the SYN packet sent by the master device, the standby device sends a SYN+ACK packet to the master device, where ACK (Acknowledgement) is an acknowledgement character;
  • the master device receives the SYN+ACK packet sent by the standby device. After that, the master device sends an acknowledgement packet ACK to the standby device. After the packet is sent, the master device and the standby device enter the TCP connection success state and complete the three-way handshake.
  • the user information backup can be implemented in accordance with the following embodiments of the present application.
  • FIG. 5 is a schematic diagram of interaction of an information backup method provided by an embodiment of the present application.
  • the information backup method may include the following steps:
  • the master device acquires the first user information, where the first user information is information to be backed up of the user equipment that is online from the master device when the communication state of the cloud device is normal.
  • the master device can communicate with the cloud device and the device can communicate with the cloud device. If the user device successfully goes online through the master device, the master device obtains the information about the user device to be backed up.
  • the information to be backed up may include a Media Access Control (MAC) address of the user equipment, an Internet Protocol (IP) address, and a Dynamic Host Configuration Protocol (Dynamic Host Configuration Protocol). Referred to as DHCP) lease, DHCP option82, etc.
  • MAC Media Access Control
  • IP Internet Protocol
  • DHCP Dynamic Host Configuration Protocol
  • DHCP Dynamic Host Configuration Protocol
  • the user equipment sends a discovery packet to the master device, and the discovery device carries the MAC address of the user device, so that the master device obtains the MAC address of the user device.
  • the server assigns an IP address to the user device through the master device, so that the master device obtains the IP address of the user device; the server allocates an IP address for the user device.
  • the DHCP lease is also set on the address, so that the master device obtains the DHCP lease of the user device.
  • the user device dials the DHCP option 82.
  • the master device can also regenerate the DHCP option82 according to its own principles. So that the master device obtains the DHCP option82 of the user device.
  • the primary device determines that the acquired first user information is uploaded to the cloud device, if the communication status of the cloud device is normal.
  • the primary device After the primary device generates the first user information, the first user information is backed up to the cloud device.
  • the primary device may upload the first user information to the cloud device according to the real-time upload mode or the batch upload mode. Specifically, when the real-time uploading mode is adopted, the primary device uploads the first user information to the cloud device immediately after generating the first user information, and when the batch uploading mode is adopted, according to the predicted time interval, for example, every 1 second. Bulk upload all first user information that has not been uploaded.
  • the main device also backs up user information to the cloud device in batches. For details, refer to step S605a in Figure 6-a and step S707b in Figure 7-b.
  • the bulk uploading is also required.
  • the active/standby protocol is active, that is, the communication link 1 should be switched from the primary device identity to the standby device identity, and the communication link 2 corresponding to the communication link 1 in Router-B should be switched to be the primary device by the standby device identity.
  • Router-A is using the interface corresponding to communication link 1 to upload data to the cloud device in batches, the backup data will not be lost.
  • S503 The cloud device receives and stores the first user information.
  • the cloud device Since the cloud device records the identity information of the master device (for example, the IP address of the master device), after the cloud device receives the first user information, it may be determined that the first user information is uploaded by the master device according to the identity information of the master device, thereby Store the first user information.
  • the identity information of the master device for example, the IP address of the master device
  • the standby device acquires the first user information from the cloud device for backup.
  • the cloud device notifies the backup device to download the first user information, or the cloud device directly delivers the first user information to the standby device, thereby implementing backup of the user information by the standby device.
  • the standby device does not actively back up data to the cloud device. If the standby device backs up data to the cloud device, the cloud device can discard the data according to the recorded standby device identity.
  • the communication link 1 between the user equipment and the master device fails, the user equipment cannot forward traffic to the network side through the master device.
  • the corresponding communication chain in the standby device The second device is upgraded to the master device, so that the new master device can continue the user service of the user device through the link 2 based on the backup information of the user device, thereby ensuring uninterrupted user service.
  • the master device when the communication status of the cloud device is normal, if the user device is online from the master device, the master device generates the information to be backed up of the user device, and uploads the information to be backed up to the cloud device, so that The standby device can obtain the information to be backed up from the cloud device for backup. It can be seen that the master device in the embodiment of the present application backs up information to the standby device through the cloud device, and avoids the problem that the user service is discontinuous caused by the backup device directly backing up information to the standby device.
  • the above describes how to implement data backup through the cloud device when the communication status of the cloud device is normal.
  • the master device cannot back up data to the cloud device and/or the backup device cannot obtain backup data from the cloud device.
  • the master device and the standby device can be normal.
  • the information backup method provided by the embodiment of the present application may further include the step S505: the master device determines the communication state of the cloud device, and the master device determines that the communication state of the cloud device is abnormal, and the master device and the standby device
  • the second user information is sent to the standby device for backup in the case of normal communication; wherein the second user information is to be backed up by the user equipment that is online from the primary device when the communication state of the cloud device is abnormal. information.
  • a local backup mechanism between the master device and the standby device is started.
  • the master device acquires the The information to be backed up by the user equipment is the second user information, and the second user information is sent to the standby device for backup through the RBS channel. It can be seen that when the data backup cannot be implemented through the cloud device, the existing local backup mechanism can improve the reliability of the backup work.
  • the local backup is implemented according to the process shown in Figure 6-a below.
  • the master/slave protocol can pre-define the router device that initiates the local backup mechanism.
  • the master/slave protocol stipulates that the master device is responsible for initiating the local backup mechanism, if the master device detects that a link timeout occurs between itself and the cloud device, The process shown in Figure 6-a is used to implement local backup. Otherwise, if the standby device detects the link timeout between itself and the cloud device, the local backup is performed according to the process shown in Figure 6-b below.
  • the local backup method may include the following steps:
  • S601a If the master device detects that a link timeout occurs with the cloud device, and determines that the master device and the backup device can communicate normally, send a first query message to the standby device, where the first query message is used to query Whether a link timeout occurs between the standby device and the cloud device.
  • the primary device Compared with the standby device, if the primary device first detects a broken link timeout between the device and the cloud device, it asks whether the standby device also has a broken link timeout with the cloud device.
  • the master device can determine the communication status of the cloud device according to the response message received by the slave device, that is, determine whether the communication state of the cloud device is normal or abnormal, and specifically, the following steps can be used to determine.
  • the standby device After receiving the first query message, the standby device detects whether a link timeout occurs between the standby device and the cloud device; if yes, returns a first response message to the primary device, where the first response message notifies the standby device and the cloud device A link-timeout occurs between the device and the cloud device.
  • the second response message is used to notify the device that the link-timeout has not occurred.
  • S603a If the primary device receives the first response message returned by the standby device, the primary device determines that the communication state of the cloud device is abnormal and starts a local backup mechanism between the primary device and the standby device, and after the local backup mechanism is successfully started, The two user information is sent to the standby device for backup.
  • the master device After receiving the first response message, the master device determines that the master device and the backup device both have a broken link timeout with the cloud device, and the master device determines that the cloud device is faulty. In this case, the master device cannot back up data to the cloud device but prepare the device. It is also not possible to get backup data from a cloud device.
  • the master device initiates a three-way handshake with the standby device to initiate a local backup mechanism between the master device and the standby device. After the local backup mechanism is successfully started, the master device directly backs up the second user information to the standby device. At the same time, the master device no longer sends backup data to the cloud device, and the standby device no longer obtains backup data from the cloud device.
  • the three-way handshake refer to the related introduction in S404, and no further details are provided here.
  • S604a If the primary device receives the second response message returned by the standby device, it determines that the communication state of the cloud device is normal, and performs a broken link reestablishment with the cloud device.
  • the master device After receiving the second response message, the master device determines that only the user and the cloud device are temporarily broken. In this case, the master device can perform the link-breaking reconstruction with the cloud device to restore the connection with the cloud device.
  • one or more user devices may be online from the master device.
  • the information to be backed up for each user device is defined as the third user information. Therefore, after the link re-establishment is successful, the master device can upload the third user information to the cloud device in batches to ensure that the backup device can back up the third user information from the cloud device in time.
  • S606a The cloud device receives and stores the third user information.
  • the cloud device records the identity information of the master device (such as the IP address of the master device). Therefore, after receiving the third user information, the cloud device may determine that the third user information is uploaded by the master device according to the identity information of the master device, thereby Store third user information.
  • the standby device acquires third user information from the cloud device for backup.
  • the cloud device notifies the backup device to download the third user information, or the cloud device directly delivers the third user information to the standby device, thereby implementing backup of the user information.
  • the local backup method may include the following steps:
  • the standby device sends a first notification message to the master device, where the backup device detects that a link timeout occurs with the cloud device, and determines that the backup device can communicate with the master device, where the first notification message is used to notify the device. A link timeout occurred between the device and the cloud device.
  • the master device notifies the master device that the slave device detects the link timeout between the cloud device and the cloud device. After receiving the first notification message, the master device can determine the link between the master device and the cloud device.
  • the communication status of the cloud device that is, whether the communication status of the cloud device is normal or abnormal, may be determined by the following steps.
  • S602b After receiving the first notification message, the master device determines whether a link timeout occurs between the master device and the cloud device; if yes, determining that the communication state of the cloud device is abnormal, and executing S603b; if not, determining the communication of the cloud device The status is normal, and S604b is executed.
  • the master device determines that the cloud device is faulty.
  • S603b The master device starts the local backup mechanism between the master device and the standby device, and sends the second user information to the standby device for backup after the local backup mechanism is successfully started.
  • the master device After the master device determines that the cloud device is faulty, the master device initiates a three-way handshake with the standby device to initiate a local backup mechanism between the master device and the standby device. After the local backup mechanism is successfully started, the master device uses the second user information. The backup device directly sends backup data to the cloud device, and the backup device does not obtain backup data from the cloud device.
  • the three-way handshake For the specific process of the three-way handshake, refer to the related introduction in S404, and no further details are provided here.
  • S604b The master device sends a re-establishment waiting notification to the standby device, where the re-establishment waiting notification is used to notify the standby device to wait for the broken link reestablishment with the cloud device.
  • the master device notifies the standby device to complete the link-breaking reestablishment with the cloud device. Temporarily not obtaining backup data from the cloud device, but waiting to restore the connection with the cloud device and then obtaining backup data from the cloud device.
  • the link-breaking party can wait for the connection to be restored before performing data backup through the cloud device. .
  • the master device and the standby device can communicate normally.
  • the master device directly initiates a local backup mechanism and sends the information to be backed up to the standby device for backup after the local backup mechanism is successfully initiated. That is, as shown in FIG. 6-a, when the primary device and the cloud device have a link timeout, the S603a is directly executed, and no other steps are performed; as shown in FIG. 6-b, when the standby device and the cloud device are broken. When timeout occurs, S601b and S603b are executed in sequence, and no other steps are performed.
  • the local backup mechanism is initiated by the master device, and in the embodiment shown in Figures 7-a and 7-b below, The local backup mechanism is initiated by the standby device.
  • the embodiments shown in Figures 7-a and 7-b will be specifically described below.
  • the local backup is implemented according to the process shown in Figure 7-a below.
  • the active/standby protocol stipulates that the standby device is responsible for initiating the local backup mechanism
  • the standby device if the standby device first detects the link timeout between itself and the cloud device, the local backup is implemented according to the process shown in Figure 7-a below. If the master device detects the link timeout between itself and the cloud device, perform the local backup according to the process shown in Figure 7-b below, as follows.
  • the local backup method may include the following steps:
  • S701a The standby device sends a second query message to the master device, if the slave device detects that a link timeout occurs with the cloud device, and the device can communicate normally with the master device, where the second query message is used to query the master. Whether a link timeout occurs between the device and the cloud device.
  • the standby device Relative to the master device, if the standby device first detects a broken link timeout between the device and the cloud device, it queries whether the master device also has a link timeout with the cloud device.
  • the master device may determine the communication state of the cloud device according to the link status between the master device and the cloud device, that is, determine whether the communication state of the cloud device is normal or abnormal, and may be determined by the following steps.
  • the master device After receiving the second query message, the master device detects whether a link timeout occurs between the master device and the cloud device; if yes, determines that the communication state of the cloud device is abnormal, and returns a third response message to the standby device, where the The third response message is used to notify the master device that the link timeout occurs between the cloud device and the cloud device; if not, the communication state of the cloud device is normal, and the fourth response message is returned to the standby device, and the fourth response message is used to notify the master device. No broken link timeout occurred with the cloud device.
  • the standby device After receiving the third response message, the standby device determines that the master device and the backup device both have a link timeout with the cloud device. In this case, the standby device determines that the cloud device is faulty. At this time, the master device cannot back up data to the cloud device. The backup device cannot obtain backup data from the cloud device. At this time, the standby device initiates a three-way handshake with the master device to initiate a local backup mechanism between the master device and the standby device. For the specific process of the three-way handshake, refer to the related introduction in S404, and no further details are provided here.
  • the primary device After the local backup mechanism is successfully started, the primary device directly backs up the second user information to the standby device. At the same time, the primary device does not send backup data to the cloud device, and the standby device does not obtain backup data from the cloud device.
  • the standby device After receiving the fourth response message, the standby device determines that only the network device is disconnected from the cloud device. In this case, the standby device can be re-established with the cloud device to restore the connection with the cloud device.
  • one or more user devices Before the device is disconnected from the cloud device, one or more user devices may be online from the master device, and the master device has generated the information to be backed up by the user device and backs up to the cloud device. Therefore, after the link-breaking is completed, the standby device can obtain the data in batches from the cloud device for backup.
  • the local backup method may include the following steps:
  • S701b The master device sends a second notification message to the standby device if the link-timeout occurs between the device and the cloud device, and the second notification message is used to notify the device.
  • a link timeout occurs between the master device and the cloud device.
  • the master device notifies the standby device that the link device has a broken link timeout with the cloud device, so that the master device can determine the communication state of the cloud device according to the response of the standby device to the second notification message. That is, it is determined whether the communication state of the cloud device is normal or abnormal, and the following steps may be specifically determined.
  • the standby device After receiving the second notification message, the standby device determines whether a link timeout occurs between the standby device and the cloud device; if yes, executing S703b; if not, executing S705b.
  • the standby device determines that the cloud device is faulty.
  • S703b The standby device initiates a local backup mechanism between the master device and the standby device.
  • the standby device After the standby device determines that the cloud device is faulty, the standby device initiates a three-way handshake with the master device to initiate a local backup mechanism between the master device and the standby device.
  • the standby device For the specific process of the three-way handshake, refer to the related introduction in S404, and no further details are provided here.
  • S704b After the local backup mechanism is successfully started, the master device determines that the communication status of the cloud device is abnormal, and sends the second user information to the standby device for backup.
  • the master device After the local backup mechanism is successfully started, the master device directly backs up the second user information to the standby device. At the same time, the master device does not send backup data to the cloud device, and the standby device does not obtain backup data from the cloud device.
  • the standby device returns a notification response message to the primary device, where the notification response message is used to notify the primary device to wait for completion of the broken link reestablishment with the cloud device.
  • the backup device does not have a link timeout with the cloud device, that is, only the master device and the cloud device are disconnected.
  • the standby device notifies the master device to complete the link-breaking reestablishment with the cloud device.
  • the master device receives the notification. Temporarily do not back up data to the cloud device, but wait for the connection to the cloud device to restore the connection to the cloud device.
  • S706b After receiving the notification response message, the master device determines that the communication status of the cloud device is normal, and the link between the master device and the cloud device is reestablished.
  • one or more user devices may be online from the master device.
  • the information to be backed up for each user device is defined as the third user information. Therefore, after the link re-establishment is successful, the master device can upload the third user information to the cloud device in batches to ensure that the backup device can back up the third user information from the cloud device in time.
  • S708b The cloud device receives and stores the third user information.
  • the cloud device records the identity information of the master device (such as the IP address of the master device). Therefore, after receiving the third user information, the cloud device may determine that the third user information is uploaded by the master device according to the identity information of the master device, thereby Store third user information.
  • the standby device obtains the third user information from the cloud device for backup.
  • the cloud device notifies the backup device to download the third user information, or the cloud device directly delivers the third user information to the standby device, thereby implementing backup of the user information.
  • the link-breaking party can wait for the connection to be restored before performing data backup through the cloud device. .
  • the master device and the standby device can communicate normally.
  • the backup device directly initiates the local backup mechanism. After the local backup mechanism is successfully initiated, the master device sends the information to be backed up to the standby device for backup. That is, as shown in FIG. 7-a, when the backup device and the cloud device have a broken link timeout, S703a and S704a are sequentially executed, and no other steps are performed; compared with FIG. 7-b, when the primary device and the cloud device occur When the chain break timeout occurs, S701b, S703b, and S704b are sequentially executed, and other steps are not performed.
  • the local backup is implemented according to the process shown in Figure 8-a below.
  • the master/slave protocol can pre-define the router device that initiates the local backup mechanism.
  • the master device determines that the master device is responsible for initiating the local backup mechanism, the master device detects that the link quality between the device and the cloud device is lower than the preset quality.
  • the local backup is implemented according to the process shown in Figure 8-a. Otherwise, if the standby device detects that the link quality between the device and the cloud device is lower than the preset quality threshold, the following figure is shown in Figure 8-
  • the process shown in b is to implement local backup, as follows.
  • the local backup method may include the following steps:
  • S801a If the master device detects that the link quality with the cloud device is lower than the preset quality threshold and can communicate with the standby device, determine that the communication status of the cloud device is abnormal, and start between the master device and the standby device. Local backup mechanism.
  • the local backup mechanism is initiated in time.
  • the link quality between the master device and the cloud device is lower than the preset quality threshold, the link quality between the two devices is poor or the controller itself has a problem. In this case, if the master device still backs up to the cloud device. Data, there is the possibility of data loss. Therefore, when the RBS channel between the master device and the standby device is continuously chained and the quality is good, the master device can initiate a three-way handshake with the standby device to initiate a local backup mechanism between the master device and the standby device. After the backup mechanism is successfully started, the master device backs up the second user information to the standby device. At the same time, the primary device no longer sends backup data to the cloud device, and the standby device no longer obtains backup data from the cloud device.
  • the local backup method may include the following steps:
  • the standby device sends a third notification message to the master device if it detects that the link quality with the cloud device is lower than a preset quality threshold and can communicate normally with the master device.
  • the standby device Compared with the master device, if the standby device first detects the poor link quality between the device and the cloud device, it notifies the master device that the link quality between the device and the cloud device is deteriorated, so that the master device starts the local backup mechanism in time.
  • S802b After receiving the third notification message sent by the standby device, the master device determines that the communication state of the cloud device is abnormal, and starts a local backup mechanism between the master device and the standby device.
  • the link quality between the standby device and the cloud device is lower than the preset quality threshold, the link quality between the two devices is poor or the controller itself is faulty. In this case, if the standby device is still from the cloud device. Obtain backup data and there is a possibility of data loss. Therefore, when the RBS channel between the master device and the standby device is continuously chained and the quality is good, the master device can initiate a three-way handshake with the standby device to initiate a local backup mechanism between the master device and the standby device. After the backup mechanism is successfully started, the master device backs up the second user information to the standby device. At the same time, the standby device no longer obtains backup data from the cloud device.
  • the master device can back up data to the cloud device while backing up data to the standby device. If the link quality between the master device and the cloud device is also poor, the master device no longer sends backup data to the cloud device.
  • the local backup mechanism is initiated by the master device, and in the embodiment shown in Figures 9-a and 9-b below, The local backup mechanism is initiated by the standby device.
  • the embodiments shown in Figures 9-a and 9-b will be specifically described below.
  • the local backup is implemented according to the process shown in Figure 9-a below. If the backup device determines that the link quality between the device and the cloud device is lower than the preset quality threshold, the device is configured as shown in Figure 9-a below. If the primary device detects that the link quality between the device and the cloud device is lower than the preset quality threshold, the local backup is implemented according to the following process in Figure 9-b, as follows.
  • the local backup method may include the following steps:
  • S901a If the backup device detects that the link quality between the master device and the standby device is lower than the preset quality threshold and communicates with the master device, the device determines that the communication status of the cloud device is abnormal. Local backup mechanism.
  • the local backup mechanism is initiated in time.
  • the standby device can initiate a three-way handshake with the master device to initiate a local backup mechanism between the master device and the standby device. After the backup mechanism is successfully started, the master device backs up the second user information to the standby device. At the same time, the standby device no longer obtains backup data from the cloud device.
  • the master device can back up data to the cloud device while backing up data to the standby device; if the link quality between the master device and the cloud device is also poor. The primary device no longer sends backup data to the cloud device.
  • the local backup method may include the following steps:
  • the primary device sends a fourth notification message to the standby device if it detects that the link quality with the cloud device is lower than the preset quality threshold and can communicate with the standby device.
  • the master device If the primary device first detects the poor link quality between the device and the cloud device, the master device notifies the device that the link quality between the device and the cloud device is deteriorated, so that the device can start the local backup mechanism in time.
  • the standby device After receiving the fourth notification message sent by the standby device, the standby device determines that the communication state of the cloud device is abnormal, and starts a local backup mechanism between the master device and the standby device.
  • the link quality between the master device and the cloud device is lower than the preset quality threshold, the link quality between the two devices is poor or the controller itself has a problem. In this case, if the master device still backs up to the cloud device. Data, there is the possibility of data loss. Therefore, when the RBS channel between the master device and the standby device is continuously chained and the quality is good, the standby device can initiate a three-way handshake with the master device to initiate a local backup mechanism between the master device and the standby device. After the backup mechanism is successfully started, the master device backs up the second user information to the standby device. At the same time, the primary device no longer sends backup data to the cloud device, and the standby device no longer obtains backup data from the cloud device.
  • the standby device and the cloud device can communicate normally.
  • the master/slave identity switchover can be performed. That is, the master device is switched from the master device identity to the standby device identity, and the standby device device is switched from the standby device identity to the master device identity.
  • the master device and the standby device cannot communicate with each other.
  • the link between the master device and the standby device is faulty.
  • the link quality between the master device and the standby device is lower than the preset quality threshold.
  • the master device and the cloud device cannot communicate with each other.
  • the link between the master device and the cloud device is faulty.
  • the link quality between the master device and the cloud device is lower than the preset quality threshold.
  • the local backup mechanism between the master device and the standby device cannot be started.
  • the master device and the cloud device cannot communicate normally, the master device cannot be instructed to The cloud device backs up the data or cannot back up the full data to the cloud device.
  • the primary device is switched to the primary device by the identity of the standby device, so that the user device can go online after the identity switch is performed, so that the master device after the identity switch is backed up to the cloud device.
  • the data is backed up and the data is backed up after the link between the backup device and the cloud device is normal, so as to ensure the reliability of the backup work.
  • a master device 1000 is provided in the embodiment of the present application.
  • the master device 1000 may include a notification sending module 1001 and a cloud backup module 1002, where:
  • the notification sending module 1001 is configured to send a first identity notification to the cloud device, where the first identity notification is that the primary device has a notification of the identity of the primary device;
  • the state determining module 1002 is configured to determine a communication state of the cloud device.
  • the cloud backup module 1003 is configured to upload the obtained first user information to the cloud device, where the communication status of the cloud device is normal.
  • the first user information is stored by the cloud device and provided to the standby device, and the first user information is a user device that is online from the master device when the communication state of the cloud device is normal.
  • the information to be backed up is stored by the cloud device and provided to the standby device, and the first user information is a user device that is online from the master device when the communication state of the cloud device is normal. The information to be backed up.
  • the master device 1000 may further include:
  • a local backup module configured to send the acquired second user information to the standby device, where the communication status of the cloud device is abnormal, and the master device and the standby device can communicate normally
  • the second user information is information to be backed up of the user equipment that is online from the master device in a case that the communication state of the cloud device is abnormal.
  • the state determination module 1002 may include:
  • Querying a sending submodule configured to send a first query message to the standby device after detecting a broken link timeout with the cloud device, where the first query message is used to query the standby device Whether the link timeout occurs between the cloud devices;
  • the first determining submodule is configured to determine a communication state of the cloud device according to the response message received from the standby device.
  • the function implementation of the query sending submodule and the first determining submodule may refer to the above method steps S601a-S604a.
  • the first determining submodule is specifically configured to: if the first response message returned by the standby device is received, determine that the communication status of the cloud device is abnormal, where the first The response message is used to notify that the link timeout occurs between the standby device and the cloud device;
  • the local backup module is further configured to start a local backup mechanism between the primary device and the standby device before sending the obtained second user information to the backup device for backup.
  • the first determining submodule is specifically configured to: if the second response message returned by the standby device is received, determining that the communication state of the cloud device is normal; wherein the second The response message is used to notify that there is no link timeout between the standby device and the cloud device;
  • the master device 1000 may further include:
  • a first broken link reconstruction module configured to perform a broken link reconstruction with the cloud device
  • a first batch backup module configured to send the obtained third user information to the cloud device in batches, where the third user information is stored by the cloud device and provided to the The device is described, and the third user information is information to be backed up by the user equipment that is online from the master device after the master device and the cloud device are disconnected.
  • the function implementation of the first chain breaking reconstruction module and the first batch backup module may refer to the foregoing method steps S604a-S605a.
  • the state determination module 1002 may include:
  • a notification receiving sub-module configured to receive a first notification message sent by the standby device, where the first notification message is used to notify a disconnection timeout between the standby device and the cloud device;
  • a second determining submodule configured to determine, according to a link situation between the master device and the cloud device, a communication state of the cloud device, after receiving the first notification message.
  • the function implementation of the notification receiving submodule and the second determining submodule may refer to the foregoing method step S602b.
  • the second determining submodule is specifically configured to determine that the communication status of the cloud device is abnormal if a link timeout occurs between the primary device and the cloud device.
  • the local backup module is further configured to start a local backup mechanism between the primary device and the standby device before sending the obtained second user information to the backup device for backup.
  • the second determining submodule is specifically configured to determine that a communication state of the cloud device is normal if it is determined that a broken link timeout occurs with the cloud device;
  • the master device 1000 may further include:
  • a re-establishment notification module configured to notify the standby device to wait for completion of a broken link reestablishment with the cloud device.
  • the state determination module 1002 may include:
  • Querying a receiving submodule configured to receive a second query message sent by the standby device, where the second query message is sent by the standby device after determining that a broken link timeout occurs with the cloud device, and the The second query message is used to query whether a link timeout occurs between the master device and the cloud device;
  • a third determining submodule configured to determine, according to a link situation between the master device and the cloud device, a communication state of the cloud device, after receiving the second query message.
  • the third determining sub-module is specifically configured to determine that the communication status of the cloud device is abnormal if it is determined that a broken link timeout occurs with the cloud device;
  • the master device 1000 may further include:
  • a first response sending module configured to send, by the cloud backup module, the acquired second user information to the standby device for backup, to send a third response message to the standby device, so that the standby device receives the After the third response message, the local backup mechanism between the master device and the standby device is started, where the third response message is a link timeout between the master device and the cloud device.
  • the function implementation of the first response sending module may refer to the foregoing method step S702a.
  • the third determining submodule is specifically configured to determine that a communication state of the cloud device is normal if it is determined that a broken link timeout occurs with the cloud device;
  • the master device 1000 may further include:
  • a second response sending module configured to send a fourth response message to the standby device, to wait for the standby device to complete a broken link reconstruction with the cloud device after receiving the fourth response message, where the fourth The response message is that no link timeout occurs between the primary device and the cloud device.
  • the function implementation of the second response sending module may refer to the foregoing method step S702a.
  • the state determination module 1002 may include:
  • a notification sending sub-module configured to send, to the standby device, a second notification message that is sent to the standby device after the disconnection timeout occurs with the cloud device, where the second notification message is used to notify the standby device A link timeout occurs between the master device and the cloud device;
  • a fourth determining submodule configured to determine a communication state of the cloud device according to the response of the standby device to the second notification message.
  • the function implementation of the notification sending sub-module reference may be made to the above method step S701b; the function implementation of the fourth determining sub-module may refer to the above method steps S702b-S706b.
  • the fourth determining submodule is specifically configured to determine the cloud device if it is determined that the standby device has started a local backup mechanism between the primary device and the standby device.
  • the communication status is abnormal.
  • the fourth determining submodule is specifically configured to: if the notification response message returned by the standby device is received, determine that the communication state of the cloud device is normal; wherein the notification response is The message is used to notify the master device to wait for completion of the broken link reconstruction with the cloud device;
  • the master device 1000 may further include:
  • a second broken link reconstruction module configured to perform a broken link reconstruction with the cloud device
  • a second batch backup module configured to send the obtained third user information to the cloud device in batches after the link-synchronization is successfully performed, where the third user information is stored by the cloud device and provided to the device And the third user information is information to be backed up by the user equipment that is online from the master device after the master device and the cloud device are disconnected.
  • the function implementation of the second broken link reconstruction module may refer to the foregoing method step S706b; the function implementation of the fourth determining submodule may refer to the above method step S707b.
  • the state determining module 1002 is specifically configured to: if it is determined that a link quality between the master device and the cloud device is lower than a preset quality threshold, and/or determine the device If the link quality between the device and the cloud device is lower than a preset quality threshold, it is determined that the communication state of the cloud device is abnormal.
  • the function implementation of the state determination module may refer to the foregoing method steps S801a-S802a and S801b-S803b.
  • the master device 1000 may further include:
  • An identity switching module configured to: when it is determined that the master device and the cloud device cannot communicate normally, and the master device and the standby device cannot communicate normally, the master device The primary device identity is switched to the standby device identity.
  • the function implementation of the identity switching module may refer to the content of the active/standby identity switching in the foregoing method.
  • the master device and the cloud device cannot communicate normally, and may include:
  • a link timeout occurs between the master device and the cloud device, or the link quality between the master device and the cloud device is lower than a preset quality threshold.
  • the master device and the standby device cannot communicate normally, and may include:
  • a link timeout occurs between the master device and the standby device, or the link quality between the master device and the standby device is lower than a preset quality threshold.
  • the foregoing description of the embodiment of the present application shows that when the communication status of the cloud device is normal, if the user device is online from the master device, the master device generates the information to be backed up of the user device, and uploads the information to be backed up to The cloud device, so that the standby device can obtain the information to be backed up from the cloud device for backup. It can be seen that the master device in the embodiment of the present application backs up the information to the standby device through the cloud device, thereby preventing the master device from directly backing up to the standby device. The problem of user service discontinuity caused by information.
  • the master device can directly back up information to the standby device to improve the backup work. Reliability.
  • a cloud device 1100 is provided in the embodiment of the present application.
  • the cloud device 1100 may include a notification receiving module 1101 and a cloud backup module 1102, where:
  • the notification receiving module 1101 is configured to receive a first identity notification sent by the primary device and a second identity notification sent by the standby device, where the first identity notification is a notification that the primary device has a primary device identity, and the second identity notification is Notifying the standby device of the device identity;
  • the cloud backup module 1102 is configured to receive and store the first user information uploaded by the master device, and provide the first user information to the standby device.
  • the first user information is uploaded when the master device determines that the communication state of the cloud device is normal, and the first user information is that the communication status of the cloud device is normal.
  • the function implementation of the notification receiving module may refer to the foregoing method steps S402-S403; the function implementation of the cloud backup module may refer to the foregoing method step S503.
  • the foregoing description of the embodiment of the present application shows that when the communication status of the cloud device is normal, if the user device is online from the master device, the master device generates the information to be backed up of the user device, and uploads the information to be backed up to The cloud device, so that the standby device can obtain the information to be backed up from the cloud device for backup. It can be seen that the master device in the embodiment of the present application backs up the information to the standby device through the cloud device, thereby preventing the master device from directly backing up to the standby device. The problem of user service discontinuity caused by information.
  • the standby device 1200 may include a notification sending module 1201 and a cloud backup module 1202, where:
  • the notification sending module 1201 is configured to send a second identity notification to the cloud device, where the second identity notification is that the standby device has a notification of the standby device identity;
  • the cloud backup module 1202 is configured to acquire first user information from the cloud device for backup
  • the first user information is uploaded to the cloud device when the master device determines that the communication state of the cloud device is normal, and the first user information is a communication state of the cloud device.
  • the function implementation of the notification sending module may refer to the foregoing method step S402; the function implementation of the cloud backup module may refer to the foregoing method step S504.
  • the standby device 1200 may further include:
  • a local backup module configured to receive second user information sent by the primary device for backup if the communication status of the cloud device is abnormal
  • the second user information is information to be backed up by the user equipment that is online from the master device when the communication state of the cloud device is abnormal; the second user information is that the master device determines the The communication status of the cloud device is abnormal and is transmitted if the master device and the standby device can communicate normally.
  • the standby device 1200 may further include:
  • a message returning module configured to return a response message to the primary device if receiving the first query message sent by the primary device
  • the first query message is sent by the master device after detecting a disconnection timeout with the cloud device, and the first query message is used to query the standby device and the cloud device. Whether a link timeout occurs between the two ends; a response message returned by the standby device is used to enable the master device to determine a communication state of the cloud device.
  • the function implementation of the message returning module may refer to the foregoing method step S602a.
  • the message returning module is specifically configured to return a first response message to the primary device.
  • the first response message is used to notify a disconnection timeout between the standby device and the cloud device, so that the master device has a link timeout between the standby device and the cloud device. Determining a communication state abnormality of the cloud device, and starting a local backup mechanism between the master device and the standby device after determining that the communication state of the cloud device is abnormal;
  • the local backup module is specifically configured to receive the second user information sent by the primary device after the local backup mechanism is started to perform backup.
  • the message returning module is specifically configured to return a second response message to the primary device.
  • the second response message is used to notify that the link-timeout has not occurred between the standby device and the cloud device, so that the master device does not break between the standby device and the cloud device.
  • the timeout period determining that the communication status of the cloud device is normal, and after determining that the communication state of the cloud device is normal, performing a broken link between the primary device and the cloud device, and causing the primary device to be in the After the link reconstruction is successful, the obtained third user information is sent to the cloud device in batches;
  • the third user information is stored by the cloud device and provided to the standby device, and the third user information is after the master device and the cloud device are disconnected and the link is broken.
  • the standby device 1200 may further include:
  • a notification sending module configured to send a first notification message to the primary device
  • the first notification message is used to notify a disconnection timeout between the standby device and the cloud device, so that the master device has a link timeout between the master device and the cloud device. Determining that the communication status of the cloud device is abnormal.
  • the function implementation of the notification sending module may refer to the foregoing method step S601b.
  • the standby device 1200 may further include:
  • a notification receiving module configured to receive a reconfiguration waiting notification sent by the primary device
  • the re-establishment waiting notification is used to notify the standby device to wait for completion of a broken link reestablishment with the cloud device, where the reconfiguration waiting notification is sent after the main device determines that the communication state of the cloud device is normal.
  • the communication status is normally determined after the master device determines that the link timeout has not occurred between the cloud devices.
  • the function implementation of the notification receiving module may refer to the foregoing method step S604b.
  • the standby device 1200 may further include:
  • a query sending module configured to send a second query message to the master device after determining that a broken link timeout occurs with the cloud device, where the second query message is used to query the master device and the cloud Whether a chain break timeout occurs between devices;
  • the local backup module is configured to: if the third response message returned by the primary device is received, learn, according to the third response message, that the communication status of the cloud device is abnormal, and start the primary device and the standby device. a local backup mechanism between the devices, after successfully starting the local backup mechanism, receiving the second user information sent by the primary device for backup, wherein the third response message is used to notify the primary device and the A broken link timeout occurred between cloud devices.
  • the standby device 1200 may further include:
  • a link-breaking reconstruction module configured to wait for a broken link to be completed with the cloud device, if the fourth response message returned by the master device is received, where the fourth response message is used to notify the master device There is no link timeout between the cloud devices.
  • the standby device 1200 may further include:
  • a notification response module configured to respond to the second notification message if receiving the second notification message sent by the primary device
  • the second notification message is sent by the master device after detecting a disconnection timeout with the cloud device, and the second notification message is used to notify the standby device of the master device A link timeout occurs between the cloud devices; the response of the standby device to the second notification message causes the master device to determine a communication state of the cloud device.
  • the function implementation of the notification response module may refer to the foregoing method steps S702b, S703b, and S705b.
  • the notification response module is specifically configured to start a local backup mechanism between the primary device and the standby device, so that the primary device determines after the local backup mechanism is started.
  • the communication status of the cloud device is abnormal.
  • the local backup module is configured to receive the second user information sent by the primary device for backup after the local backup mechanism is successfully started.
  • the function implementation of the notification response module may refer to the above method step S704b.
  • the notification response module is specifically configured to return a notification response message to the primary device.
  • the notification response message is used to notify the master device to wait for a broken link reestablishment with the cloud device, so that the master device sends the acquired third user information in batches after the link disconnection is successfully completed.
  • the third user information is stored by the cloud device and provided to the standby device, and the third user information is after the master device and the cloud device are disconnected and The information about the user equipment to be backed up from the master device before the broken link is successfully reconstructed.
  • the standby device 1200 may further include:
  • the local backup module is further configured to: determine that a link quality between the standby device and the cloud device is lower than a preset quality threshold, and/or determine a chain between the primary device and the cloud device If the quality of the path is lower than the preset quality threshold, the local backup mechanism between the primary device and the standby device is started, so that the primary device determines that the communication state of the cloud device is abnormal after the local backup mechanism is started. .
  • the standby device 1200 may further include:
  • the identity switching module is configured to: when it is determined that the standby device can communicate with the cloud device, and the standby device cannot communicate with the master device, the backup device The device identity is switched to the primary device identity.
  • the function implementation of the identity switching module may refer to the content of the active/standby identity switching in the foregoing method.
  • the standby device and the master device may not be in normal communication, and may include: a link timeout occurs between the standby device and the master device, or the standby device and the standby device The link quality between the master devices is lower than the preset quality threshold.
  • the foregoing description of the embodiment of the present application shows that when the communication status of the cloud device is normal, if the user device is online from the master device, the master device generates the information to be backed up of the user device, and uploads the information to be backed up to The cloud device, so that the standby device can obtain the information to be backed up from the cloud device for backup. It can be seen that the master device in the embodiment of the present application backs up the information to the standby device through the cloud device, thereby preventing the master device from directly backing up to the standby device. The problem of user service discontinuity caused by information.
  • the master device can directly back up information to the standby device to improve the backup work. Reliability.
  • the main device includes: a processor, a memory, a communication interface, and a bus; the processor, the communication interface, and the memory communicate with each other through the bus; a communication interface for receiving and transmitting data; the memory for storing instructions; the processor for executing the instructions in the memory to perform the aforementioned information backup method.
  • the main device 1300 includes: a receiver 1301, a transmitter 1302, a processor 1303, and a memory 1304 (wherein the number of processors 1303 in the main device 1300) One or more, one processor in Figure 13 is taken as an example).
  • the communication interface may include a receiver 1301 and a transmitter 1302.
  • the receiver 1301, the transmitter 1302, the processor 1303, and the memory 1304 may be connected by a bus or other means, wherein the bus connection is taken as an example in FIG.
  • Memory 1304 can include read only memory and random access memory and provides instructions and data to processor 1303. A portion of the memory 1304 may also include a non-volatile random access memory (English name: Non-Volatile Random Access Memory, English abbreviation: NVRAM).
  • the memory 1304 stores operating systems and operational instructions, executable modules or data structures, or a subset thereof, or an extended set thereof, wherein the operational instructions can include various operational instructions for implementing various operations.
  • the operating system can include a variety of system programs for implementing various basic services and handling hardware-based tasks.
  • the processor 1303 controls the operation of the master device 1300.
  • the processor 1303 may also be referred to as a central processing unit (English name: Central Processing Unit, English abbreviation: CPU).
  • CPU Central Processing Unit
  • each component is coupled together by a bus system.
  • the bus system may include a power bus, a control bus, and a status signal bus in addition to the data bus.
  • the various buses are referred to as bus systems in the figures.
  • the method disclosed in the foregoing embodiment of the present application may be applied to the processor 1303 or implemented by the processor 1303.
  • the processor 1303 can be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 1303 or an instruction in a form of software.
  • the processor 1303 may be a general-purpose processor, a digital signal processor (English name: digital signal processing, English abbreviation: DSP), an application specific integrated circuit (English name: Application Specific Integrated Circuit, English abbreviation: ASIC), field programmable Gate array (English name: Field-Programmable Gate Array, English abbreviation: FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 1304, and the processor 1303 reads the information in the memory 1304 and completes the steps of the above method in combination with its hardware.
  • the receiver 1301 can be configured to receive input digital or character information, and generate signal inputs related to related settings and function control of the main device 1300.
  • the transmitter 1302 can include a display device such as a display screen, and the transmitter 1302 can be used to output through an external interface. Number or character information.
  • the processor 1303 is configured to execute the information backup method performed by the foregoing main device side.
  • the cloud device includes: a processor, a memory, a communication interface, and a bus; the processor, the communication interface, and the memory communicate with each other through the bus; a communication interface for receiving and transmitting data; the memory for storing instructions; the processor for executing the instructions in the memory to perform the aforementioned information backup method.
  • the cloud device 1400 includes: a receiver 1401, a transmitter 1402, a processor 1403, and a memory 1404 (wherein the number of processors 1403 in the cloud device 1400) One or more, one processor in Figure 14 is taken as an example).
  • the communication interface may include a receiver 1401 and a transmitter 1402.
  • the receiver 1401, the transmitter 1402, the processor 1403, and the memory 1404 may be connected by a bus or other means, wherein the bus connection is taken as an example in FIG.
  • Memory 1404 can include read only memory and random access memory and provides instructions and data to processor 1403. A portion of the memory 1404 may also include a non-volatile random access memory (English name: Non-Volatile Random Access Memory, English abbreviation: NVRAM).
  • the memory 1404 stores operating systems and operational instructions, executable modules or data structures, or a subset thereof, or an extended set thereof, wherein the operational instructions can include various operational instructions for implementing various operations.
  • the operating system can include a variety of system programs for implementing various basic services and handling hardware-based tasks.
  • the processor 1403 controls the operation of the cloud device 1400.
  • the processor 1403 may also be referred to as a central processing unit (English name: Central Processing Unit, English abbreviation: CPU).
  • CPU Central Processing Unit
  • each component is coupled together by a bus system.
  • the bus system may include a power bus, a control bus, and a status signal bus in addition to the data bus.
  • the various buses are referred to as bus systems in the figures.
  • the method disclosed in the foregoing embodiment of the present application may be applied to the processor 1403 or implemented by the processor 1403.
  • the processor 1403 can be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 1403 or an instruction in a form of software.
  • the processor 1403 may be a general-purpose processor, a digital signal processor (English full name: digital signal processing, English abbreviation: DSP), an application specific integrated circuit (English name: Application Specific Integrated Circuit, English abbreviation: ASIC), field programmable Gate array (English name: Field-Programmable Gate Array, English abbreviation: FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 1404, and the processor 1403 reads the information in the memory 1404 and completes the steps of the above method in combination with its hardware.
  • the receiver 1401 can be configured to receive input digital or character information, and generate signal inputs related to related settings and function control of the cloud device 1400.
  • the transmitter 1402 can include a display device such as a display screen, and the transmitter 1402 can be used to output through an external interface. Number or character information.
  • the processor 1303 is configured to execute the information backup method performed by the cloud device side.
  • the standby device includes: a processor, a memory, a communication interface, and a bus; the processor, the communication interface, and the memory communicate with each other through the bus; a communication interface for receiving and transmitting data; the memory for storing instructions; the processor for executing the instructions in the memory to perform the aforementioned information backup method.
  • the standby device 1500 includes: a receiver 1501, a transmitter 1502, a processor 1503, and a memory 1504 (wherein the number of processors 1503 in the standby device 1500) One or more, one processor in Figure 15 is taken as an example).
  • the communication interface may include a receiver 1501 and a transmitter 1502.
  • the receiver 1501, the transmitter 1502, the processor 1503, and the memory 1504 may be connected by a bus or other means, wherein the bus connection is taken as an example in FIG.
  • the memory 1504 can include read only memory and random access memory and provides instructions and data to the processor 1503. A portion of the memory 1504 may also include a non-volatile random access memory (English name: Non-Volatile Random Access Memory, English abbreviation: NVRAM).
  • the memory 1504 stores operating systems and operational instructions, executable modules or data structures, or a subset thereof, or an extended set thereof, wherein the operational instructions can include various operational instructions for implementing various operations.
  • the operating system can include a variety of system programs for implementing various basic services and handling hardware-based tasks.
  • the processor 1503 controls the operation of the standby device 1500.
  • the processor 1503 may also be referred to as a central processing unit (English full name: Central Processing Unit, English abbreviation: CPU).
  • CPU Central Processing Unit
  • each component is coupled together by a bus system.
  • the bus system may include a power bus, a control bus, and a status signal bus in addition to the data bus.
  • the various buses are referred to as bus systems in the figures.
  • the method disclosed in the foregoing embodiment of the present application may be applied to the processor 1503 or implemented by the processor 1503.
  • the processor 1503 can be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 1503 or an instruction in a form of software.
  • the processor 1503 may be a general-purpose processor, a digital signal processor (English full name: digital signal processing, English abbreviation: DSP), an application specific integrated circuit (English name: Application Specific Integrated Circuit, English abbreviation: ASIC), field programmable Gate array (English name: Field-Programmable Gate Array, English abbreviation: FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 1504, and the processor 1503 reads the information in the memory 1504 and performs the steps of the above method in combination with its hardware.
  • the receiver 1501 can be configured to receive input digital or character information, and generate signal inputs related to the related settings and function control of the standby device 1500.
  • the transmitter 1502 can include a display device such as a display screen, and the transmitter 1502 can be used to output through an external interface. Number or character information.
  • the processor 1503 is configured to execute the information backup method performed by the standby device side.
  • the embodiment of the present application further provides a computer storage medium, wherein the computer storage medium stores a program, and the program executes some or all of the steps described in the foregoing method embodiments.
  • the embodiment of the present application further provides a computer program product comprising instructions, which when executed on a computer, cause the computer to perform some or all of the steps recited in the above method embodiments.
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be Physical units can be located in one place or distributed to multiple network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • the connection relationship between the modules indicates that there is a communication connection between them, and specifically may be implemented as one or more communication buses or signal lines.
  • U disk mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc., including a number of instructions to make a computer device (may be A personal computer, server, or network device, etc.) performs the methods described in various embodiments of the present application.
  • a computer device may be A personal computer, server, or network device, etc.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • wire eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be stored by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Quality & Reliability (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Environmental & Geological Engineering (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)
  • Telephonic Communication Services (AREA)
  • Hardware Redundancy (AREA)

Abstract

本申请实施例公开了一种信息备份方法及相关设备，能够保证用户业务的连续性。所述方法应用于通信系统中，所述通信系统包括主设备、备设备和云端设备，所述方法由所述主设备执行；所述方法包括：所述主设备向所述云端设备发送第一身份通知，所述第一身份通知为所述主设备具有主设备身份的通知；所述主设备确定所述云端设备的通信状态正常的情况下，将获取的第一用户信息上传至所述云端设备；其中，所述第一用户信息由所述云端设备存储并提供给所述备设备，且所述第一用户信息是在所述云端设备的通信状态正常的情况下从所述主设备上线的用户设备的待备份信息。

Description

一种信息备份方法及相关设备
本申请要求于2018年3月29日提交中国国家知识产权局、申请号为201810273786.2、发明名称为“一种信息备份方法及相关设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种信息备份方法及相关设备。
背景技术
目前，企业用户和个人用户对于网络质量的要求越来越高，其中一方面是希望用户业务不间断，为此，出现了冗余用户信息(Redundancy User Information，简称RUI)多机备份技术。RUI多机备份技术已在现网中实现规模化应用，比如宽带远程接入服务器(Broadband Remote Access Server，简称BRAS)领域的RUI备份、IP无线接入网络(IP Radio Access Network，简称IPRAN)领域的地址解析协议(Address Resolution Protocol，简称ARP)RUI备份等。
以BRAS领域的RUI双机热备业务为例，如图1-a所示，首先通过虚拟路由冗余协议(Virtual Router Redundancy Protocol，简称VRRP)协商出哪个路由器是主设备、哪个路由器是备设备，其中，主设备用于实现用户侧与网络侧之间的流量转发，备设备用于备份用户信息。具体来讲，当某个用户设备在主设备上线后，主设备通过与备设备之间的远端备份服务(Remote Backup Service，简称RBS)通道，将该用户设备的用户信息发送至备设备上进行备份，然而，如图1-b所示，当通过双向转发检测(Bidirectional Forwarding Detection，简称BFD)技术检测出该用户设备与主设备之间发生通信故障时，可以基于备份的用户信息使该用户设备快速切换到备设备上，由备设备接替主设备来对该用户设备的业务进行流量转发，从而保证用户业务不间断。
在现有的RUI多机备份技术中，当主设备与备设备的关系混乱时，将影响用户业务的连续性。例如，对于路由器1和路由器2，当路由器1故障恢复且满足WTR设置值，路由器1会由备设备重新恢复成主设备，路由器2由主设备恢复成备设备，在WTR设置值到达之前，路由器2还是主设备，会向路由器1备份用户信息，如果路由器1与路由器2之间的备份速度较慢或者二者之间的RBS通道迟迟建立不起来，将导致路由器2在WTR前不能完成用户信息备份，从而影响这些用户业务的连续性。
发明内容
本申请实施例提供了一种信息备份方法及相关设备，能够保证用户业务的连续性。
为解决上述技术问题，本申请实施例提供以下技术方案：
第一方面，本申请实施例提供一种信息备份方法，所述方法应用于通信系统中，所述通信系统包括主设备、备设备和云端设备，所述方法由所述主设备执行；所述方法包括：所述主设备向所述云端设备发送第一身份通知，所述第一身份通知为所述主设备具有主设备身份的通知；所述主设备确定所述云端设备的通信状态；所述主设备在确定所述云端设备的通信状态正常的情况下，将获取的第一用户信息上传至所述云端设备；其中，所述第一用户信息由所述云端设备存储并提供给所述备设备，且所述第一用户信息是在所述云端设备的通信状态正常的情况下从所述主设备上线的用户设备的待备份信息。在本申请实施例中，当云端设备的通信状态正常时，如果有用户设备从主设备上线，主设备将生成该用户设备的待备份信息并上传至云端设备，这样，备设备便可以从云端设备获取该待备份信息以进行备份，可见，由于主设备是通过云端设备向备设备备份信息的，避免了主设备直接向备设备备份信息的情况下，有些场景下，例如当主设备与备设备的关系混乱，所导致的用户业务不连续的问题。
在本申请的一个可能设计中，所述方法还包括：所述主设备在确定所述云端设备的通信状态异常，且所述主设备与所述备设备之间能够正常通信的情况下，将获取的第二用户信息发送至所述备设备进行备份；其中，所述第二用户信息是在所述云端设备的通信状态异常的情况下从所述主设备上线的用户设备的待备份信息。在本申请实施例中，当云端设备的通信状态异常时，即无法通过云端设备实现数据备份的情况下，如果主设备与备设备之间能够正常通信，主设备可以直接向备设备备份信息，以实现本地备份，从而提高了备份工作的可靠性。
在本申请的一个可能设计中，所述主设备确定所述云端设备的通信状态包括：所述主设备在检测到与所述云端设备之间发生断链超时后，向所述备设备发送第一询问消息，其中，所述第一询问消息用于询问所述备设备与所述云端设备之间是否发生断链超时；所述主设备根据从所述备设备接收到的响应消息确定所述云端设备的通信状态。在本申请实施例中，如果主设备先检测到与云端设备之间发生断链超时，便询问备设备是否也与云端设备发生断链超时，使得主设备可以根据备设备的响应消息来确定云端设备的通信状态是否异常。
在本申请的一个可能设计中，所述主设备根据从所述备设备接收到的响应消息确定所述云端设备的通信状态，包括：所述主设备若接收到所述备设备返回的第一响应消息，则确定所述云端设备的通信状态异常，其中所述第一响应消息用于告知所述备设备与所述云端设备之间发生断链超时；在将获取的第二用户信息发送至所述备设备进行备份之前，所述方法还包括：所述主设备启动所述主设备与所述备设备之间的本地备份机制。在本申请实施例中，如果主设备与云端设备之间发生断链超时、且备设备也与云端设备之间发生断链超时，主设备便可以确定云端设备的通信状态是异常的，此时，主设备便可以启动本地备份机制并进行本地备份。
在本申请的一个可能设计中，所述主设备根据从所述备设备接收到的响应消息确定所述云端设备的通信状态，包括：所述主设备若接收到所述备设备返回的第二响应消息，则确定所述云端设备的通信状态正常；其中所述第二响应消息用于告知所述备设备与所述云端设备之间未发生断链超时；所述方法还包括：所述主设备与所述云端设备之 间进行断链重建；所述主设备在所述断链重建成功后，将获取的第三用户信息批量发送至所述云端设备，其中，所述第三用户信息由所述云端设备存储并提供给所述备设备，且所述第三用户信息是在所述主设备与所述云端设备发生断链后且在所述断链重建成功之前从所述主设备上线的用户设备的待备份信息。在本申请实施例中，如果主设备与云端设备之间发生断链超时、但备设备与云端设备之间未发生断链超时，主设备便可以确定云端设备的通信状态是正常的，此时，主设备便可以通过与云端设备完成断链重建，并在断链重建成功后实现云端备份。
在本申请的一个可能设计中，所述主设备确定所述云端设备的通信状态，包括：所述主设备接收所述备设备发送的第一通知消息，其中，所述第一通知消息用于告知所述备设备与所述云端设备之间发生断链超时；在接收到所述第一通知消息后，所述主设备根据所述主设备与所述云端设备的链接情况确定所述云端设备的通信状态。在本申请实施例中，如果备设备先检测到与云端设备之间发生断链超时，可以将该情况通知主设备，使得主设备在接收到通知后，可以根据自己与云端设备的链接情况确定云端设备的通信状态是否异常。
在本申请的一个可能设计中，所述主设备根据所述主设备与所述云端设备的链接情况确定所述云端设备的通信状态，包括：所述主设备若确定所述主设备与所述云端设备之间发生断链超时，则确定所述云端设备的通信状态异常；在将获取的第二用户信息发送至所述备设备进行备份之前，所述方法还包括：所述主设备启动所述主设备与所述备设备之间的本地备份机制。在本申请实施例中，如果主设备与云端设备之间发生断链超时、且备设备也与云端设备之间发生断链超时，主设备便可以确定云端设备的通信状态是异常的，此时，主设备便可以启动本地备份机制并进行本地备份。
在本申请的一个可能设计中，所述主设备根据所述主设备与所述云端设备的链接情况确定所述云端设备的通信状态，包括：所述主设备若确定与所述云端设备之间未发生断链超时，则确定所述云端设备的通信状态正常；所述方法还包括：所述主设备通知所述备设备等待与所述云端设备之间完成断链重建。在本申请实施例中，如果备设备与云端设备之间发生断链超时、但主设备与云端设备之间未发生断链超时，主设备便可以确定云端设备的通信状态是正常的，此时，主设备便可以通知备设备与云端设备完成断链重建，以便备设备在断链重建成功后从云端设备备份数据。
在本申请的一个可能设计中，所述主设备确定所述云端设备的通信状态，包括：所述主设备接收所述备设备发送的第二询问消息，所述第二询问消息是所述备设备确定与所述云端设备之间发生断链超时后发送的、且所述第二询问消息用于询问所述主设备与所述云端设备之间是否发生断链超时；所述主设备在接收到所述第二询问消息后，根据所述主设备与所述云端设备的链接情况确定所述云端设备的通信状态。在本申请实施例中，如果备设备先检测到与云端设备之间发生断链超时，便询问主设备是否也与云端设备发生断链超时，使得主设备可以根据自己与云端设备的链接情况来确定云端设备的通信状态是否异常。
在本申请的一个可能设计中，所述主设备根据所述主设备与所述云端设备的链接情况确定所述云端设备的通信状态，包括：所述主设备若确定与所述云端设备之间发生断 链超时，则确定所述云端设备的通信状态异常；在将获取的第二用户信息发送至所述备设备进行备份之前，所述方法还包括：所述主设备向所述备设备发送第三响应消息，以便所述备设备接收到所述第三响应消息后启动所述主设备与所述备设备之间的本地备份机制，其中，所述第三响应消息为所述主设备与所述云端设备之间发生断链超时。在本申请实施例中，如果主设备与云端设备之间发生断链超时、且备设备也与云端设备之间发生断链超时，主设备便可以确定云端设备的通信状态是异常的，此时，主设备可以将此情况通知备设备，备设备接收到通知后，便可以启动本地备份机制并进行本地备份。
在本申请的一个可能设计中，所述主设备根据所述主设备与所述云端设备的链接情况确定所述云端设备的通信状态，包括：所述主设备若确定与所述云端设备之间未发生断链超时，则确定所述云端设备的通信状态正常；所述方法还包括：所述主设备向所述备设备发送第四响应消息，以便所述备设备接收到所述第四响应消息后等待与所述云端设备完成断链重建，其中，所述第四响应消息为所述主设备与所述云端设备之间未发生断链超时。在本申请实施例中，如果备设备与云端设备之间发生断链超时、但主设备与云端设备之间未发生断链超时，主设备便可以确定云端设备的通信状态是正常的，此时，主设备便可以通知备设备与云端设备完成断链重建，以便备设备在断链重建成功后从云端设备备份数据。
在本申请的一个可能设计中，所述主设备确定所述云端设备的通信状态包括：所述主设备在检测到与所述云端设备之间发生断链超时后向所述备设备发送的第二通知消息，其中，所述第二通知消息用于告知所述备设备所述主设备与所述云端设备之间发生断链超时；所述主设备根据所述备设备针对所述第二通知消息的响应确定所述云端设备的通信状态。在本申请实施例中，如果主设备先检测到与云端设备之间发生断链超时，可以将该情况通知备设备，主设备便可以根据备设备对该通知的响应结果确定云端设备的通信状态是否异常。
在本申请的一个可能设计中，所述主设备根据所述备设备针对所述第二通知消息的响应确定所述云端设备的通信状态，包括：若所述主设备确定所述备设备已启动所述主设备与所述备设备之间的本地备份机制，则确定所述云端设备的通信状态异常。在本申请实施例中，如果主设备与云端设备之间发生断链超时、且备设备也与云端设备之间发生断链超时，备设备便会启动本地备份机制，这样，主设备便可以确定云端设备的通信状态是异常的，从而可以进行本地备份。
在本申请的一个可能设计中，所述主设备根据所述备设备针对所述第二通知消息的响应确定所述云端设备的通信状态，包括：所述主设备若接收到所述备设备返回的通知响应消息，则确定所述云端设备的通信状态正常；其中，所述通知响应消息用于告知所述主设备等待与所述云端设备之间完成断链重建；所述方法还包括：所述主设备与所述云端设备之间进行断链重建；所述主设备在所述断链重建成功后，将获取的第三用户信息批量发送至所述云端设备，所述第三用户信息由所述云端设备存储并提供给所述备设备，且所述第三用户信息是在所述主设备与所述云端设备发生断链后且在所述断链重建成功之前从所述主设备上线的用户设备的待备份信息。在本申请实施例中，如果主设备 与云端设备之间发生断链超时、但备设备与云端设备之间未发生断链超时，主设备便可以通过与云端设备完成断链重建，并在断链重建成功后实现云端备份。
在本申请的一个可能设计中，所述主设备确定所述云端设备的通信状态异常包括，包括：所述主设备若确定所述主设备与所述云端设备之间的链路质量低于预设质量阈值、和/或确定所述备设备与所述云端设备之间的链路质量低于预设质量阈值，则确定所述云端设备的通信状态异常。在本申请实施例中，当主设备确定自己和/或备设备中的一方出现链路质量差时，便可以确定云端设备的通信状态是异常的，此时，便可以启动本地备份机制并进行本地备份。
在本申请的一个可能设计中，所述方法还包括：所述主设备在确定所述主设备与所述云端设备之间不能正常通信、且所述主设备与所述备设备之间不能正常通信的情况下，则所述主设备的所述主设备身份切换为备设备身份。在本申请实施例中，如果主设备同时不能与云端设备和备设备进行通信，说明主设备既不能进行云端备份也不能进行本地备份，此时，主设备可以进行主备身份切换，从而使能够实现云端备份的备设备作为主设备来进行云端备份，进而保证备份工作的可靠性。
在本申请的一个可能设计中，所述主设备与所述云端设备之间不能正常通信，包括：所述主设备与所述云端设备之间发生断链超时，或者，所述主设备与所述云端设备之间的链路质量低于预设质量阈值。在本申请实施例中，主设备与云端设备之间不能正常通信，可以表现为断链超时，还可以表现为链路质量差。
在本申请的一个可能设计中，所述主设备与所述备设备之间不能正常通信，包括：所述主设备与所述备设备之间发生断链超时，或者，所述主设备与所述备设备之间的链路质量低于预设质量阈值。在本申请实施例中，主设备与备设备之间不能正常通信，可以表现为断链超时，还可以表现为链路质量差。
第二方面，本申请实施例提供一种信息备份方法，所述方法应用于通信系统中，所述通信系统包括主设备、备设备和云端设备，所述方法由所述云端设备执行；所述方法包括：所述云端设备接收所述主设备发送的第一身份通知以及所述备设备发送的第二身份通知，所述第一身份通知为所述主设备具有主设备身份的通知，所述第二身份通知为所述备设备具有备设备身份的通知；所述云端设备接收并存储所述主设备上传的第一用户信息，并将所述第一用户信息提供给所述备设备；其中，所述第一用户信息是所述主设备确定所述云端设备的通信状态正常的情况下上传的，且所述第一用户信息是当所述云端设备的通信状态正常的情况下从所述主设备上线的用户设备的待备份信息。在本申请实施例中，当云端设备的通信状态正常时，如果有用户设备从主设备上线，主设备将生成该用户设备的待备份信息并上传至云端设备，这样，备设备便可以从云端设备获取该待备份信息以进行备份，可见，由于主设备是通过云端设备向备设备备份信息的，避免了主设备直接向备设备备份信息所导致的用户业务不连续的问题。
第三方面，本申请实施例提供一种信息备份方法，所述方法应用于通信系统中，所述通信系统包括主设备、备设备和云端设备，所述方法由所述备设备执行；所述方法包括：所述备设备向所述云端设备发送第二身份通知，所述第二身份通知为所述备设备具有备设备身份的通知；所述备设备从所述云端设备获取第一用户信息进行备份；其中， 所述第一用户信息是所述主设备确定所述云端设备的通信状态正常的情况下上传至所述云端设备存储的，且所述第一用户信息是当所述云端设备的通信状态正常的情况下从所述主设备上线的用户设备的待备份信息。在本申请实施例中，当云端设备的通信状态正常时，如果有用户设备从主设备上线，主设备将生成该用户设备的待备份信息并上传至云端设备，这样，备设备便可以从云端设备获取该待备份信息以进行备份，可见，由于主设备是通过云端设备向备设备备份信息的，避免了主设备直接向备设备备份信息所导致的用户业务不连续的问题。
在本申请的一个可能设计中，所述方法还包括：在所述云端设备的通信状态异常的情况下，所述备设备接收所述主设备发送的第二用户信息进行备份；其中，所述第二用户信息是在所述云端设备的通信状态异常的情况下从所述主设备上线的用户设备的待备份信息；所述第二用户信息是所述主设备在确定所述云端设备的通信状态异常且所述主设备与所述备设备之间能够正常通信的情况下发送的。在本申请实施例中，当云端设备的通信状态异常时，即无法通过云端设备实现数据备份的情况下，如果主设备与备设备之间能够正常通信，主设备可以直接向备设备备份信息，以实现本地备份，从而提高了备份工作的可靠性。
在本申请的一个可能设计中，所述方法还包括：所述备设备若接收到所述主设备发送的第一询问消息，则向所述主设备返回响应消息；其中，所述第一询问消息是所述主设备在检测到与所述云端设备之间发生断链超时后发送的，且所述第一询问消息用于询问所述备设备与所述云端设备之间是否发生断链超时；所述备设备返回的响应消息用于使所述主设备确定所述云端设备的通信状态。在本申请实施例中，如果主设备先检测到与云端设备之间发生断链超时，便询问备设备是否也与云端设备发生断链超时，使得主设备可以根据备设备的响应消息来确定云端设备的通信状态是否异常。
在本申请的一个可能设计中，所述备设备向所述主设备返回响应消息，包括：所述备设备向所述主设备返回第一响应消息；其中，所述第一响应消息用于告知所述备设备与所述云端设备之间发生断链超时，以使得所述主设备在所述备设备与所述云端设备之间发生断链超时后确定所述云端设备的通信状态异常，并在确定所述云端设备的通信状态异常之后启动所述主设备与所述备设备之间的本地备份机制；所述备设备接收所述主设备发送的第二用户信息进行备份，包括：所述备设备接收所述主设备启动所述本地备份机制后发送的第二用户信息进行备份。在本申请实施例中，如果主设备与云端设备之间发生断链超时、且备设备也与云端设备之间发生断链超时，主设备便可以确定云端设备的通信状态异常，此时，主设备便可以启动本地备份机制并进行本地备份。
在本申请的一个可能设计中，所述备设备向所述主设备返回响应消息，包括：所述备设备向所述主设备返回第二响应消息；其中，所述第二响应消息用于告知所述备设备与所述云端设备之间未发生断链超时，以使得所述主设备在所述备设备与所述云端设备之间未发生断链超时后确定所述云端设备的通信状态正常，并在确定所述云端设备的通信状态正常之后使所述主设备与所述云端设备之间进行断链重建，以及使所述主设备在所述断链重建成功后将获取的第三用户信息批量发送至所述云端设备；其中，所述第三用户信息由所述云端设备存储并提供给所述备设备，且所述第三用户信息是在所述主设 备与所述云端设备发生断链后且在所述断链重建成功之前从所述主设备上线的用户设备的待备份信息。在本申请实施例中，如果主设备与云端设备之间发生断链超时、但备设备与云端设备之间未发生断链超时，主设备便可以确定云端设备的通信状态是正常的，此时，主设备便可以通过与云端设备完成断链重建，并在断链重建成功后实现云端备份。
在本申请的一个可能设计中，所述方法还包括：所述备设备向所述主设备发送第一通知消息；其中，所述第一通知消息用于告知所述备设备与所述云端设备之间发生断链超时，以使得所述主设备在所述主设备与所述云端设备之间发生断链超时后确定所述云端设备的通信状态异常。在本申请实施例中，如果备设备先检测到与云端设备之间发生断链超时，可以将该情况通知主设备，使得主设备在接收到通知后，可以根据自己与云端设备的链接情况确定云端设备的通信状态是否异常。
在本申请的一个可能设计中，所述方法还包括：所述备设备接收所述主设备发送的重建等待通知；其中，所述重建等待通知用于通知所述备设备等待与所述云端设备之间完成断链重建，所述重建等待通知是所述主设备确定所述云端设备的通信状态正常后发送的，所述通信状态正常是所述主设备确定与所述云端设备之间未发生断链超时后确定的。在本申请实施例中，如果备设备与云端设备之间发生断链超时、但主设备与云端设备之间未发生断链超时，主设备便可以确定云端设备的通信状态是正常的，此时，主设备便可以通知备设备与云端设备完成断链重建，以便备设备在断链重建成功后从云端设备备份数据。
在本申请的一个可能设计中，所述方法还包括：所述备设备确定与所述云端设备之间发生断链超时后，向所述主设备发送第二询问消息，其中，所述第二询问消息用于询问所述主设备与所述云端设备之间是否发生断链超时；所述备设备若接收到所述主设备返回的第三响应消息，则根据所述第三响应消息获知所述云端设备的通信状态异常，启动所述主设备与所述备设备之间的本地备份机制，其中，所述第三响应消息用于告知所述主设备与所述云端设备之间发生断链超时；所述备设备接收所述主设备发送的第二用户信息进行备份，包括：所述备设备在成功启动所述本地备份机制后，接收所述主设备发送的第二用户信息进行备份。在本申请实施例中，如果备设备先检测到与云端设备之间发生断链超时，便询问主设备是否也与云端设备发生断链超时；如果主设备与云端设备之间发生断链超时、且备设备也与云端设备之间发生断链超时，主设备便可以确定云端设备的通信状态是异常的，此时，主设备可以将此情况通知备设备，备设备接收到通知后，便可以启动本地备份机制并进行本地备份。
在本申请的一个可能设计中，所述方法还包括：所述备设备若接收到所述主设备返回的第四响应消息，则等待与所述云端设备完成断链重建，其中，所述第四响应消息用于告知所述主设备与所述云端设备之间未发生断链超时。在本申请实施例中，如果备设备与云端设备之间发生断链超时、但主设备与云端设备之间未发生断链超时，主设备便可以确定云端设备的通信状态是正常的，此时，主设备便可以通知备设备与云端设备完成断链重建，以便备设备在断链重建成功后从云端设备备份数据。
在本申请的一个可能设计中，所述方法还包括：所述备设备若接收到所述主设备发送的第二通知消息，则针对所述第二通知消息进行响应；其中，所述第二通知消息是所述主设备在检测到与所述云端设备之间发生断链超时后发送的，且所述第二通知消息用于告知所述备设备所述主设备与所述云端设备之间发生断链超时；所述备设备针对所述第二通知消息的响应使所述主设备确定所述云端设备的通信状态。在本申请实施例中，如果主设备先检测到与云端设备之间发生断链超时，可以将该情况通知备设备，主设备便可以根据备设备对该通知的响应结果确定云端设备的通信状态是否异常。
在本申请的一个可能设计中，所述备设备针对所述第二通知消息进行响应，包括：所述备设备启动所述主设备与所述备设备之间的本地备份机制，以便所述主设备在所述本地备份机制被启动后确定所述云端设备的通信状态异常；所述备设备接收所述主设备发送的第二用户信息进行备份，包括：所述备设备在成功启动所述本地备份机制后，接收所述主设备发送的第二用户信息进行备份。在本申请实施例中，如果主设备与云端设备之间发生断链超时、且备设备也与云端设备之间发生断链超时，备设备便会启动本地备份机制，这样，主设备便可以确定云端设备的通信状态是异常的，从而可以进行本地备份。
在本申请的一个可能设计中，所述备设备针对所述第二通知消息进行响应，包括：所述备设备向所述主设备返回通知响应消息；其中，所述通知响应消息用于告知所述主设备等待与所述云端设备之间完成断链重建，以使所述主设备在所述断链重建成功后将获取的第三用户信息批量发送至所述云端设备；所述第三用户信息由所述云端设备存储并提供给所述备设备，且所述第三用户信息是在所述主设备与所述云端设备发生断链后且在所述断链重建成功之前从所述主设备上线的用户设备的待备份信息。在本申请实施例中，如果主设备与云端设备之间发生断链超时、但备设备与云端设备之间未发生断链超时，主设备便可以通过与云端设备完成断链重建，并在断链重建成功后实现云端备份。
在本申请的一个可能设计中，所述方法还包括：所述备设备若确定所述备设备与所述云端设备之间的链路质量低于预设质量阈值、和/或确定所述主设备与所述云端设备之间的链路质量低于预设质量阈值，则启动所述主设备与所述备设备之间的本地备份机制，以便所述主设备在所述本地备份机制被启动后确定所述云端设备的通信状态异常。在本申请实施例中，当备设备确定自己和/或主设备中的一方出现链路质量差时，便可以启动本地备份机制，当本地备份机制被启动后，主设备便可以确定云端设备的通信状态是异常的，此时，便可以进行本地备份。
在本申请的一个可能设计中，所述方法还包括：所述备设备在确定所述备设备与所述云端设备之间能够正常通信且所述备设备与所述主设备之间不能正常通信的情况下，则所述备设备的所述备设备身份切换为主设备身份。在本申请实施例中，在主设备同时不能与云端设备和备设备进行通信的情况下，如果备设备能与云端设备进行通信，说明备设备可以进行云端备份，此时，备设备可以进行主备身份切换，从而使自己作为主设备来进行云端备份，进而保证备份工作的可靠性。
在本申请的一个可能设计中，所述备设备与所述主设备不能正常通信，包括：所述备设备与所述主设备之间发生断链超时，或者，所述备设备与所述主设备之间的链路质量低于预设质量阈值。在本申请实施例中，备设备与主设备之间不能正常通信，可以表现为断链超时，还可以表现为链路质量差。
第四方面，本申请实施例提供一种主设备，所述主设备包括：通知发送模块，用于向云端设备发送第一身份通知，所述第一身份通知为主设备具有主设备身份的通知；状态确定模块，用于确定所述云端设备的通信状态；云端备份模块，用于在确定所述云端设备的通信状态正常的情况下，将获取的第一用户信息上传至所述云端设备；其中，所述第一用户信息由所述云端设备存储并提供给备设备，且所述第一用户信息是在所述云端设备的通信状态正常的情况下从所述主设备上线的用户设备的待备份信息。
在本申请的一个可能设计中，所述主设备还包括：本地备份模块，用于在确定所述云端设备的通信状态异常，且所述主设备与所述备设备之间能够正常通信的情况下，将获取的第二用户信息发送至所述备设备进行备份；其中，所述第二用户信息是在所述云端设备的通信状态异常的情况下从所述主设备上线的用户设备的待备份信息。
在本申请的一个可能设计中，所述状态确定模块包括：询问发送子模块，用于在检测到与所述云端设备之间发生断链超时后，向所述备设备发送第一询问消息，其中，所述第一询问消息用于询问所述备设备与所述云端设备之间是否发生断链超时；第一确定子模块，用于根据从所述备设备接收到的响应消息确定所述云端设备的通信状态。
在本申请的一个可能设计中，所述第一确定子模块，具体用于若接收到所述备设备返回的第一响应消息，则确定所述云端设备的通信状态异常，其中所述第一响应消息用于告知所述备设备与所述云端设备之间发生断链超时；所述本地备份模块，还用于在将获取的第二用户信息发送至所述备设备进行备份之前，启动所述主设备与所述备设备之间的本地备份机制。
在本申请的一个可能设计中，所述第一确定子模块，具体用于若接收到所述备设备返回的第二响应消息，则确定所述云端设备的通信状态正常；其中所述第二响应消息用于告知所述备设备与所述云端设备之间未发生断链超时；所述主设备还包括：第一断链重建模块，用于与所述云端设备之间进行断链重建；第一批量备份模块，用于在所述断链重建成功后，将获取的第三用户信息批量发送至所述云端设备，其中，所述第三用户信息由所述云端设备存储并提供给所述备设备，且所述第三用户信息是在所述主设备与所述云端设备发生断链后且在所述断链重建成功之前从所述主设备上线的用户设备的待备份信息。
在本申请的一个可能设计中，所述状态确定模块包括：通知接收子模块，用于接收所述备设备发送的第一通知消息，其中，所述第一通知消息用于告知所述备设备与所述云端设备之间发生断链超时；第二确定子模块，用于在接收到所述第一通知消息后，根据所述主设备与所述云端设备的链接情况确定所述云端设备的通信状态。
在本申请的一个可能设计中，所述第二确定子模块，具体用于若确定所述主设备与所述云端设备之间发生断链超时，则确定所述云端设备的通信状态异常；所述本地备份 模块，还用于在将获取的第二用户信息发送至所述备设备进行备份之前，启动所述主设备与所述备设备之间的本地备份机制。
在本申请的一个可能设计中，所述第二确定子模块，具体用于若确定与所述云端设备之间未发生断链超时，则确定所述云端设备的通信状态正常；所述主设备还包括：重建通知模块，用于通知所述备设备等待与所述云端设备之间完成断链重建。
在本申请的一个可能设计中，所述状态确定模块包括：询问接收子模块，用于接收所述备设备发送的第二询问消息，所述第二询问消息是所述备设备确定与所述云端设备之间发生断链超时后发送的、且所述第二询问消息用于询问所述主设备与所述云端设备之间是否发生断链超时；第三确定子模块，用于在接收到所述第二询问消息后，根据所述主设备与所述云端设备的链接情况确定所述云端设备的通信状态。
在本申请的一个可能设计中，所述第三确定子模块，具体用于若确定与所述云端设备之间发生断链超时，则确定所述云端设备的通信状态异常；所述主设备还包括：第一响应发送模块，用于在所述云端备份模块将获取的第二用户信息发送至所述备设备进行备份之前，向所述备设备发送第三响应消息，以便所述备设备接收到所述第三响应消息后启动所述主设备与所述备设备之间的本地备份机制，其中，所述第三响应消息为所述主设备与所述云端设备之间发生断链超时。
在本申请的一个可能设计中，所述第三确定子模块，具体用于若确定与所述云端设备之间未发生断链超时，则确定所述云端设备的通信状态正常；所述主设备还包括：第二响应发送模块，用于向所述备设备发送第四响应消息，以便所述备设备接收到所述第四响应消息后等待与所述云端设备完成断链重建，其中，所述第四响应消息为所述主设备与所述云端设备之间未发生断链超时。
在本申请的一个可能设计中，所述状态确定模块包括：通知发送子模块，用于在检测到与所述云端设备之间发生断链超时后向所述备设备发送的第二通知消息，其中，所述第二通知消息用于告知所述备设备所述主设备与所述云端设备之间发生断链超时；第四确定子模块，用于根据所述备设备针对所述第二通知消息的响应确定所述云端设备的通信状态。
在本申请的一个可能设计中，所述第四确定子模块，具体用于若确定所述备设备已启动所述主设备与所述备设备之间的本地备份机制，则确定所述云端设备的通信状态异常。
在本申请的一个可能设计中，所述第四确定子模块，具体用于若接收到所述备设备返回的通知响应消息，则确定所述云端设备的通信状态正常；其中，所述通知响应消息用于告知所述主设备等待与所述云端设备之间完成断链重建；所述主设备还包括：第二断链重建模块，用于与所述云端设备之间进行断链重建；第二批量备份模块，用于在所述断链重建成功后，将获取的第三用户信息批量发送至所述云端设备，所述第三用户信息由所述云端设备存储并提供给所述备设备，且所述第三用户信息是在所述主设备与所述云端设备发生断链后且在所述断链重建成功之前从所述主设备上线的用户设备的待备份信息。
在本申请的一个可能设计中，所述状态确定模块，具体用于若确定所述主设备与所述云端设备之间的链路质量低于预设质量阈值、和/或确定所述备设备与所述云端设备之间的链路质量低于预设质量阈值，则确定所述云端设备的通信状态异常。
在本申请的一个可能设计中，所述主设备还包括：身份切换模块，用于在确定所述主设备与所述云端设备之间不能正常通信、且所述主设备与所述备设备之间不能正常通信的情况下，则所述主设备的所述主设备身份切换为备设备身份。
在本申请的一个可能设计中，所述主设备与所述云端设备之间不能正常通信，包括：所述主设备与所述云端设备之间发生断链超时，或者，所述主设备与所述云端设备之间的链路质量低于预设质量阈值。
在本申请的一个可能设计中，所述主设备与所述备设备之间不能正常通信，包括：所述主设备与所述备设备之间发生断链超时，或者，所述主设备与所述备设备之间的链路质量低于预设质量阈值。
第五方面，本申请实施例提供一种云端设备，所述云端设备包括：通知接收模块，用于接收主设备发送的第一身份通知以及备设备发送的第二身份通知，所述第一身份通知为所述主设备具有主设备身份的通知，所述第二身份通知为所述备设备具有备设备身份的通知；云端备份模块，用于接收并存储所述主设备上传的第一用户信息，并将所述第一用户信息提供给所述备设备；其中，所述第一用户信息是所述主设备确定所述云端设备的通信状态正常的情况下上传的，且所述第一用户信息是当所述云端设备的通信状态正常的情况下从所述主设备上线的用户设备的待备份信息。
第六方面，本申请实施例提供一种备设备，所述备设备包括：通知发送模块，用于向云端设备发送第二身份通知，所述第二身份通知为所述备设备具有备设备身份的通知；云端备份模块，用于从所述云端设备获取第一用户信息进行备份；其中，所述第一用户信息是所述主设备确定所述云端设备的通信状态正常的情况下上传至所述云端设备存储的，且所述第一用户信息是当所述云端设备的通信状态正常的情况下从所述主设备上线的用户设备的待备份信息。
在本申请的一个可能设计中，所述备设备还包括：本地备份模块，用于在所述云端设备的通信状态异常的情况下，接收所述主设备发送的第二用户信息进行备份；其中，所述第二用户信息是在所述云端设备的通信状态异常的情况下从所述主设备上线的用户设备的待备份信息；所述第二用户信息是所述主设备在确定所述云端设备的通信状态异常且所述主设备与所述备设备之间能够正常通信的情况下发送的。
在本申请的一个可能设计中，所述备设备还包括：消息返回模块，用于若接收到所述主设备发送的第一询问消息，则向所述主设备返回响应消息；其中，所述第一询问消息是所述主设备在检测到与所述云端设备之间发生断链超时后发送的，且所述第一询问消息用于询问所述备设备与所述云端设备之间是否发生断链超时；所述备设备返回的响应消息用于使所述主设备确定所述云端设备的通信状态。
在本申请的一个可能设计中，所述消息返回模块，具体用于向所述主设备返回第一响应消息；其中，所述第一响应消息用于告知所述备设备与所述云端设备之间发生断链超时，以使得所述主设备在所述备设备与所述云端设备之间发生断链超时后确定所述云 端设备的通信状态异常，并在确定所述云端设备的通信状态异常之后启动所述主设备与所述备设备之间的本地备份机制；所述本地备份模块，具体用于接收所述主设备启动所述本地备份机制后发送的第二用户信息进行备份。
在本申请的一个可能设计中，所述消息返回模块，具体用于向所述主设备返回第二响应消息；其中，所述第二响应消息用于告知所述备设备与所述云端设备之间未发生断链超时，以使得所述主设备在所述备设备与所述云端设备之间未发生断链超时后确定所述云端设备的通信状态正常，并在确定所述云端设备的通信状态正常之后使所述主设备与所述云端设备之间进行断链重建，以及使所述主设备在所述断链重建成功后将获取的第三用户信息批量发送至所述云端设备；其中，所述第三用户信息由所述云端设备存储并提供给所述备设备，且所述第三用户信息是在所述主设备与所述云端设备发生断链后且在所述断链重建成功之前从所述主设备上线的用户设备的待备份信息。
在本申请的一个可能设计中，所述备设备还包括：通知发送模块，用于向所述主设备发送第一通知消息；其中，所述第一通知消息用于告知所述备设备与所述云端设备之间发生断链超时，以使得所述主设备在所述主设备与所述云端设备之间发生断链超时后确定所述云端设备的通信状态异常。
在本申请的一个可能设计中，所述备设备还包括：通知接收模块，用于接收所述主设备发送的重建等待通知；其中，所述重建等待通知用于通知所述备设备等待与所述云端设备之间完成断链重建，所述重建等待通知是所述主设备确定所述云端设备的通信状态正常后发送的，所述通信状态正常是所述主设备确定与所述云端设备之间未发生断链超时后确定的。
在本申请的一个可能设计中，所述备设备还包括：询问发送模块，用于确定与所述云端设备之间发生断链超时后，向所述主设备发送第二询问消息，其中，所述第二询问消息用于询问所述主设备与所述云端设备之间是否发生断链超时；所述本地备份模块，具体用于若接收到所述主设备返回的第三响应消息，则根据所述第三响应消息获知所述云端设备的通信状态异常，启动所述主设备与所述备设备之间的本地备份机制，在成功启动所述本地备份机制后，接收所述主设备发送的第二用户信息进行备份，其中，所述第三响应消息用于告知所述主设备与所述云端设备之间发生断链超时。
在本申请的一个可能设计中，所述备设备还包括：断链重建模块，用于若接收到所述主设备返回的第四响应消息，则等待与所述云端设备完成断链重建，其中，所述第四响应消息用于告知所述主设备与所述云端设备之间未发生断链超时。
在本申请的一个可能设计中，所述备设备还包括：通知响应模块，用于若接收到所述主设备发送的第二通知消息，则针对所述第二通知消息进行响应；其中，所述第二通知消息是所述主设备在检测到与所述云端设备之间发生断链超时后发送的，且所述第二通知消息用于告知所述备设备所述主设备与所述云端设备之间发生断链超时；所述备设备针对所述第二通知消息的响应使所述主设备确定所述云端设备的通信状态。
在本申请的一个可能设计中，所述通知响应模块，具体用于启动所述主设备与所述备设备之间的本地备份机制，以便所述主设备在所述本地备份机制被启动后确定所述云 端设备的通信状态异常；所述本地备份模块，具体用于在成功启动所述本地备份机制后，接收所述主设备发送的第二用户信息进行备份。
在本申请的一个可能设计中，所述通知响应模块，具体用于向所述主设备返回通知响应消息；其中，所述通知响应消息用于告知所述主设备等待与所述云端设备之间完成断链重建，以使所述主设备在所述断链重建成功后将获取的第三用户信息批量发送至所述云端设备；所述第三用户信息由所述云端设备存储并提供给所述备设备，且所述第三用户信息是在所述主设备与所述云端设备发生断链后且在所述断链重建成功之前从所述主设备上线的用户设备的待备份信息。
在本申请的一个可能设计中，所述备设备还包括：所述本地备份模块，还用于若确定所述备设备与所述云端设备之间的链路质量低于预设质量阈值、和/或确定所述主设备与所述云端设备之间的链路质量低于预设质量阈值，则启动所述主设备与所述备设备之间的本地备份机制，以便所述主设备在所述本地备份机制被启动后确定所述云端设备的通信状态异常。
在本申请的一个可能设计中，所述备设备还包括：身份切换模块，用于在确定所述备设备与所述云端设备之间能够正常通信且所述备设备与所述主设备之间不能正常通信的情况下，则所述备设备的所述备设备身份切换为主设备身份。
在本申请的一个可能设计中，所述备设备与所述主设备不能正常通信，包括：所述备设备与所述主设备之间发生断链超时，或者，所述备设备与所述主设备之间的链路质量低于预设质量阈值。
第七方面，本申请实施例提供一种主设备，所述主设备包括：处理器，存储器，通信接口和总线；所述处理器、通信接口、存储器通过所述总线相互的通信；所述通信接口，用于接收和发送数据；所述存储器用于存储指令；所述处理器用于执行所述存储器中的所述指令，执行如前述第一方面中任一项所述的方法。
第八方面，本申请实施例提供一种云端设备，所述云端设备包括：处理器，存储器，通信接口和总线；所述处理器、通信接口、存储器通过所述总线相互的通信；所述通信接口，用于接收和发送数据；所述存储器用于存储指令；所述处理器用于执行所述存储器中的所述指令，执行如前述第二方面中任一项所述的方法。
第九方面，本申请实施例提供一种备设备，所述主设备包括：处理器，存储器，通信接口和总线；所述处理器、通信接口、存储器通过所述总线相互的通信；所述通信接口，用于接收和发送数据；所述存储器用于存储指令；所述处理器用于执行所述存储器中的所述指令，执行如前述第三方面中任一项所述的方法。
第十方面，本申请实施例提供一种通信系统，所述通信系统包括上述第四方面的主设备、第五方面的云端设备以及第六方面的备设备，或者，所述通信系统包括上述第七方面的主设备、第八方面的云端设备以及第九方面的备设备。
第十一方面，本申请实施例提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第十二方面，本申请实施例提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
附图说明
图1-a为现有通信系统的数据流向示意图之一；
图1-b为现有通信系统的数据流向示意图之二；
图2为现有通信系统的组成架构示意图；
图3为本申请实施例提供的通信系统的组成架构示意图；
图4为本申请实施例提供的数据准备流程示意图；
图5为本申请实施例提供的正常信息备份方法的交互示意图；
图6-a为本申请实施例提供的本地信息备份方法的交互示意图之一；
图6-b为本申请实施例提供的本地信息备份方法的交互示意图之二；
图7-a为本申请实施例提供的本地信息备份方法的交互示意图之三；
图7-b为本申请实施例提供的本地信息备份方法的交互示意图之四；
图8-a为本申请实施例提供的本地信息备份方法的交互示意图之五；
图8-b为本申请实施例提供的本地信息备份方法的交互示意图之六；
图9-a为本申请实施例提供的本地信息备份方法的交互示意图之七；
图9-b为本申请实施例提供的本地信息备份方法的交互示意图之八；
图10为本申请实施例提供的主设备的组成示意图之一；
图11为本申请实施例提供的云端设备的组成示意图之一；
图12为本申请实施例提供的备设备的组成示意图之一；
图13为本申请实施例提供的主设备的组成示意图之二；
图14为本申请实施例提供的云端设备的组成示意图之二；
图15为本申请实施例提供的备设备的组成示意图之二。
具体实施方式
本申请实施例提供了一种信息备份方法及相关设备，能够保证用户业务的连续性。
如图2所示，为本申请实施例提供的一种RUI多机备份通信系统架构示意图。在该通信系统中，Router-A和Router-B可以是路由器，还可以是其它可以实现用户信息备份的设备，比如交换机。当通过主备协议协商出Router-A为主设备、Router-B为备设备时，用户设备的上下行流量则通过Router-A来转发，Router-A可以通过RBS通道向Router-B备份该用户设备的信息。
基于图2所示的系统架构，其RUI逻辑模型为：
(1)、通过主备协议，例如VRRP等协议，协商出路由器之间的主备关系，可以存在一个主设备和多个备设备，但一般而言同一用户业务对应一个主设备和一个备设备，以针对该用户业务从主设备向备设备备份用户信息；
(2)、创建远端备份模板(Remote Backup Profile，简称RBP)，用于提供用户信息的备份方式和备份方向；
(3)、创建RBS，用于在主设备与备设备之间建立数据通道；
(4)、主备协议会联动BFD部署，用于快速检测用户设备与主设备之间的通信故障，并在出现故障时通知上层应用；
(5)、主设备会发布地址池路由至网络侧，用户设备上线后可以从地址池获取地址，备设备撤销相应的地址池路由，此时网络侧与用户侧之间的流量通过主设备转发；在故障场景下，例如主设备的接口1故障时，只有故障接口1对应的用户业务会切换到备设备，但主设备还存在其它正常接口，比如接口2，由于接口2和故障接口1的用户共用同一个地址池，所以，故障前主设备已发布的地址池路由并不会撤销，而关于故障接口1对应的用户业务流量，即网络侧与用户侧之间的业务流量，会先到主设备、再通过RBS通道到备设备进行流量转发。
如图3所示，为本申请实施例提供的通信系统的组成架构示意图。本申请实施例提供的通信系统，是在图2所示通信系统的基础上增加云端设备，本申请实施例不对云端设备的类型进行限制，比如云端设备可以是标准化网络组件(Standardized Network Component，简称SNC)控制器、服务器或网络管理设备等。其中，Router-A和Router-B作为云端备份系统的本地分支设备，云端设备作为该云端备份系统的集中存储设备；Router-A作为主设备时，用于向云端设备上传用户信息，Router-B作为备设备时，用于从云端设备获取该用户信息进行备份；并且，通常情况下默认Router-A不向Router-B备份用户信息，只有在Router-A和/或Router-B与云端设备通信异常时，Router-A才可能向Router-B备份用户信息。需要说明的是，Router-A和Router-B在流量转发方面主要是由Router-A负责流量转发、而Router-B不负责流量转发，也就是说，Router-A作为主设备时，用户设备将从Router-A上线，并且，该用户设备与网络侧之间的业务流量将由Router-A负责转发，具体的流量转发方式请参见现有技术，在此不再赘述，而Router-B作为备设备不负责该用户设备的流量转发，但需要备份该用户设备的用户信息。
下面结合附图，对本申请的实施例进行描述。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是仅仅是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，这仅仅是描述本申请的实施例中对相同属性的对象在描述时所采用的区分方式。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，以便包含一系列单元的过程、方法、系统、产品或设备不必限于那些单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它单元。
以下将对本申请实施例提供的信息备份方法及相关设备进行详细说明。
在本申请的一些实施例中，为了实现云端备份，需要依次完成以下准备工作一和准备工作二。
准备工作一：通过主备协议协商出主设备和备设备。
现以主备关系的协商对象为路由器为例进行说明，当图3所示通信系统中包括多个路由器时，需要通过主备协议比如VRRP，协商出哪个路由器是主设备、哪个路由器是备设备。为此，VRRP中定义了路由器的三种状态，分别为初始状态(Initialize)、活动状态 (Master)以及备份状态(Backup)，VRRP将根据优先级来确定每台路由器的角色，即确定主设备和备设备，优先级越高，则越有可能成为主设备。
具体地，初始创建VRRP时的每个路由器均工作在Initialize状态，若路由器的优先级小于255，则会先由Initialize状态切换至Backup状态，待定时器超时后再切换至Master状态。对于首先切换至Master状态的路由器通过VRRP通告报文的交互，获知其它路由器的优先级，从而进行主设备的选举。在选举主设备时，对于每个处于Backup状态的路由器来讲，如果VRRP通告报文中的主设备的优先级高于或等于自己的优先级，则自己仍保持Backup状态；如果VRRP通告报文中的主设备的优先级低于自己的优先级，当采用抢占方式时，使自己由Backup状态切换至Master状态，从而成为主设备，当采用非抢占方式时，自己仍保持Backup状态。
准备工作二：使云端设备获知主设备具有主设备身份、备设备具有备设备身份。
参见图4所示的数据准备方法的流程示意图，包括以下步骤：
S401：主设备与云端设备建立连接，备设备与云端设备建立连接。
当通过主备协议协商出主设备和备设备后，主设备和备设备可以分别通过网络配置协议(Network Configuration Protocol，简称NETCONF)或简单网络管理协议(Simple Network Management Protocol，简称SNMP)等与云端设备建立连接。
S402：主设备向云端设备发送第一身份通知，其中，第一身份通知为主设备具有主设备身份的通知；备设备向云端设备发送第二身份通知，其中，第二身份通知为备设备具有备设备身份的通知。
例如，第一身份通知中可以包括主设备的唯一识别标识以及主设备身份的标识，比如主设备的IP地址和“主”；同理，第一身份通知中可以包括备设备的唯一识别标识以及备设备身份的标识，比如备设备的IP地址和“备”。
S403：云端设备建立存储表项。
云端设备接收到第一身份通知后，为主设备建立存储表项，比如主设备的IP地址：主；同理，云端设备接收到第二身份通知后，为备设备建立存储表项，比如备设备的IP地址：备。
S404：主设备与备设备通过三次握手，建立RBS通道。
此外，主设备与备设备之间还要通过三次握手建立RBS通道，用于在主设备与备设备之间的本地备份机制被启动时，通过RBS通道实现主设备向备设备的信息备份。其中，三次握手过程具体为：
在第一次握手中，主设备向备设备发送SYN包，之后等待备设备确认，其中，SYN(synchronous)是TCP/IP建立连接时使用的握手信号；在第二次握手中，当备设备收到主设备发送的SYN包后，备设备向主设备发送SYN+ACK包，其中，ACK(Acknowledgement)是确认字符；在第三次握手中，主设备收到备设备发送的SYN+ACK包后，主设备向备设备发送一个确认包ACK，此包发送完毕后，主设备和备设备进入TCP连接成功状态，完成三次握手。
当完成上述准备工作后，便可以按照本申请的以下实施例实现用户信息备份。
如图5所示，为本申请实施例提供的信息备份方法的交互示意图，该信息备份方法可以包括以下步骤：
S501：主设备获取第一用户信息，其中，第一用户信息是在云端设备的通信状态正常的情况下从主设备上线的用户设备的待备份信息。
当云端设备的通信状态正常时，即主设备能够与云端设备正常通信且备设备也能够与云端设备正常通信，如果某用户设备通过主设备成功上线后，主设备获取该用户设备的待备份信息，该待备份信息可以包括该用户设备的媒体访问控制(Media Access Control，简称MAC)地址、网络之间互连的协议( Internet Protocol，简称IP)地址、动态主机配置协议(Dynamic Host Configuration Protocol，简称DHCP)租期、DHCP option82等。
现以用户设备采用动态主机配置协议(Dynamic Host Configuration Protocol，简称DHCP)方式上线时如何获取待备份信息为例进行说明。
其中，当用户设备需要通过主设备上线时，用户设备先向主设备发送discovery报文，该discovery报文中携带了用户设备的MAC地址，这样主设备便获取了该用户设备的MAC地址；接下来，通过用户设备、主设备与服务器之间的报文交互，服务器会通过主设备将IP地址分配给用户设备，这样主设备便获取了该用户设备的IP地址；服务器在为用户设备分配IP地址的同时还设置了DHCP租期，这样主设备便获取了该用户设备的DHCP租期；关于DHCP option82，用户设备拨号上线时携带了DHCP option82，主设备也可以按照自己的原则重新生成DHCP option82，这样主设备便获取了该用户设备的DHCP option82。
S502：主设备确定云端设备的通信状态正常的情况下，将获取的第一用户信息上传至云端设备。
当主设备生成第一用户信息后，将第一用户信息备份至云端设备。
在本申请的一些实施例中，主设备可以按照实时上传方式或批量上传方式，将第一用户信息上传至云端设备。具体来讲，当采用实时上传方式时，主设备在生成第一用户信息后，即刻将第一用户信息上传至云端设备；当采用批量上传方式时，按照预测时间间隔，例如每隔1秒，批量上传所有未上传的第一用户信息。
需要说明的是，当主设备与云端设备之间完成断链重建后，主设备也会批量向云端设备备份用户信息，具体请参见图6-a的步骤S605a以及图7-b的步骤S707b。
此外，在其它一些场景下也需要进行批量上传，具体地，结合图3进行说明，如果某用户设备通过Router-A上线，如果该用户设备与Router-A之间的通信链路1故障了，此时主备协议起作用，即通信链路1应由主设备身份切换为备设备身份，而Router-B中与该通信链路1对应的通信链路2应由备设备身份切换为主设备身份，以利用通信链路2保证该用户设备的用户业务的连续性。但是，如果Router-A正在使用通信链路1对应的接口向云端设备批量上传数据，为了保证备份数据不会丢失，待批量上传结束后再进行主备切换。
S503：云端设备接收并存储第一用户信息。
由于云端设备记录了主设备的身份信息(例如主设备的IP地址)，因此，当云端设备接收到第一用户信息后，根据主设备身份信息可以确定第一用户信息是主设备上传的，从而存储第一用户信息。
S504：备设备从云端设备获取第一用户信息进行备份。
云端设备通知备设备下载第一用户信息、或者云端设备直接将第一用户信息下发至备设备，从而实现备设备对用户信息的备份。
需要说明的是，正常情况下，备设备不会主动向云端设备备份数据，如果备设备向云端设备备份数据，云端设备可以依据记录的备设备身份将该数据予以丢弃。
可以理解的是，当该用户设备与主设备之间的通信链路1发生故障时，即该用户设备不能通过主设备向网络侧转发业务流量，此时，备设备中与之对应的通信链路2便会升为主设备，这样，新的主设备便可以基于该用户设备的备份信息，使该用户设备的用户业务通过链路2继续进行，从而保证用户业务不间断。
在本申请实施例中，当云端设备的通信状态正常时，如果有用户设备从主设备上线，主设备将生成该用户设备的待备份信息，并将该待备份信息上传至云端设备，这样，备设备便可以从云端设备获取该待备份信息以进行备份。可见，本申请实施例的主设备是通过云端设备向备设备备份信息的，避免了主设备直接向备设备备份信息所导致的用户业务不连续的问题。
以上介绍了当云端设备的通信状态正常时，通过云端设备实现数据备份的方法。然而，当云端设备的通信状态异常时，将导致主设备无法向云端设备备份数据和/或备设备无法从云端设备获取备份数据，在这种情况下，如果主设备与备设备之间能够正常通信，则可以启动主设备与备设备之间的本地备份机制，以实现主设备向备设备的直接备份，下面进行具体介绍。
在本申请的一些实施例中，本申请实施例提供的信息备份方法还可以包括步骤S505：主设备确定云端设备的通信状态，主设备在确定云端设备的通信状态异常，且主设备与备设备之间能够正常通信的情况下，将获取的第二用户信息发送至备设备进行备份；其中，第二用户信息是在云端设备的通信状态异常的情况下从主设备上线的用户设备的待备份信息。在本实施例中，当云端设备的通信状态异常时，主设备与备设备之间的本地备份机制会被启动，在这种情况下，如果某用户设备从主设备上线，主设备将获取该用户设备的待备份信息即第二用户信息，并将该第二用户信息通过RBS通道发送至备设备进行备份。可见，当无法通过云端设备实现数据备份的情况下，采用现有的本地备份机制，可以提高备份工作的可靠性。
接下来，将对上述本地备份方法的具体实施方式进行具体介绍。
需要说明的是，相对于备设备来讲，如果主设备先检测出自己与云端设备之间发生断链超时，则按照下述图6-a所示流程来实现本地备份。当然，主备协议可以预先规定发起本地备份机制的路由器设备，当主备协议规定主设备负责发起本地备份机制时，如果主设备先检测出自己与云端设备之间发生断链超时，则按照下述图6-a所示流程来实现本地备份，反之，如果备设备先检测出自己与云端设备之间发生断链超时，则按照下述图6-b所示流程以实现本地备份，具体如下。
参见图6-a所示的用户信息的本地备份方法的交互示意图，该本地备份方法可以包括以下步骤：
S601a：主设备若检测到与云端设备之间发生断链超时、且确定主设备与备设备之间能够正常通信，则向备设备发送第一询问消息，其中，该第一询问消息用于询问备设备与云端设备之间是否发生断链超时。
相对于备设备来讲，如果主设备先检测出与云端设备之间发生断链超时，便询问备设备是否也与云端设备发生断链超时。
之后，主设备可以根据从备设备接收到的响应消息来确定云端设备的通信状态，即确定云端设备的通信状态是正常还是异常，具体可以采用以下步骤来确定。
S602a：备设备在接收到第一询问消息后，检测备设备与云端设备之间是否发生断链超时；若是，则向主设备返回第一响应消息，该第一响应消息告知备设备与云端设备之间发生断链超时；若否，则向主设备返回第二响应消息，该第二响应消息用于告知备设备与云端设备之间未发生断链超时。
S603a：主设备若接收到备设备返回的第一响应消息，则主设备确定云端设备的通信状态异常并启动主设备与备设备之间的本地备份机制，并在成功启动本地备份机制后将第二用户信息发送至备设备进行备份。
主设备在接收到第一响应消息后，确定主设备和备设备均与云端设备发生断链超时，主设备判断云端设备故障，在此情况下，主设备无法向云端设备备份数据、而备设备也无法从云端设备获取备份数据。
此时，主设备发起与备设备之间的三次握手，用以启动主设备与备设备之间的本地备份机制，在本地备份机制成功启动后，主设备将第二用户信息直接备份至备设备，同时，主设备不再向云端设备发送备份数据，且备设备也不再从云端设备处获取备份数据。其中，三次握手的具体流程请参见S404中的相关介绍，在此不再赘述。
S604a：主设备若接收到备设备返回的第二响应消息，则确定云端设备的通信状态正常，并与云端设备之间进行断链重建。
主设备在接收到第二响应消息后，确定只有自己与云端设备短暂断链，此时，主设备可以通过与云端设备进行断链重建，以恢复与云端设备之间的连接。
S605a：主设备在与云端设备之间的断链重建成功后，将获取的第三用户信息批量发送至云端设备进行备份。
在主设备与云端设备发生断链后且完成断链重建成功之前，可能有一个或多个用户设备已经从主设备上线，本实施例将每一用户设备的待备份信息定义为第三用户信息，因此，在断链重建成功后，主设备可以将这些第三用户信息批量上传至云端设备，以保证备设备可以及时从云端设备处备份这些第三用户信息。
S606a：云端设备接收并存储第三用户信息。
由于云端设备记录了主设备的身份信息(比如主设备的IP地址)，因此，当云端设备接收到第三用户信息后，根据主设备身份信息可以确定第三用户信息是主设备上传的，从而存储第三用户信息。
S607a：备设备从云端设备获取第三用户信息进行备份。
接下来，云端设备通知备设备下载第三用户信息、或者云端设备直接将第三用户信息下发至备设备，从而实现用户信息的备份。
参见图6-b所示的用户信息的本地备份方法的交互示意图，该本地备份方法可以包括以下步骤：
S601b：备设备若检测到与云端设备之间发生断链超时、且确定备设备与主设备之间能够正常通信，则向主设备发送第一通知消息，其中，第一通知消息用于告知备设备与云端设备之间发生断链超时。
相对于主设备来讲，如果备设备先检测出与云端设备之间发生断链超时，便通知主设备，主设备在接收到第一通知消息后，可以根据主设备与云端设备的链接情况确定云端设备的通信状态，即确定云端设备的通信状态是正常还是异常，具体可以采用以下步骤来确定。
S602b：主设备在接收到第一通知消息后，确定主设备与云端设备之间是否发生断链超时；若是，则确定云端设备的通信状态异常，执行S603b；若否，则确定云端设备的通信状态正常，执行S604b。
如果主设备也与云端设备发生断链超时，此时主设备无法向云端设备备份数据、而备设备也无法从云端设备获取备份数据，故而，主设备判断云端设备故障。
S603b：主设备启动主设备与备设备之间的本地备份机制，并在成功启动本地备份机制后将第二用户信息发送至备设备进行备份。
主设备判断云端设备故障后，主设备发起与备设备之间的三次握手，用以启动主设备与备设备之间的本地备份机制，在本地备份机制成功启动后，主设备将第二用户信息直接备份至备设备，同时，主设备不再向云端设备发送备份数据，且备设备也不再从云端设备处获取备份数据。其中，三次握手的具体流程请参见S404中的相关介绍，在此不再赘述。
S604b：主设备向备设备发送重建等待通知，其中，该重建等待通知用于通知备设备等待与云端设备之间完成断链重建。
如果主设备没有与云端设备发生断链超时，即只有备设备与云端设备短暂断链，此时，主设备通知备设备等待与云端设备之间完成断链重建，备设备在接到通知后，暂时不从云端设备获取备份数据，而是等待与云端设备之间恢复连接后再从云端设备获取备份数据。
可见，从图6-a和图6-b所示的本地备份流程可知，如果主设备和备设备均与云端设备之间发生断链超时，即主设备无法向云端设备备份数据、而备设备也无法从云端设备获取备份数据，说明云端设备可能故障，这种情况下，需要将通过云端设备的备份机制，改为主设备与备设备之间的本地备份机制，这样，可以保证从主设备上线的用户信息能够且及时地在备设备侧进行备份，这样，一旦用户设备与主设备之间的通信链路发生故障，备设备可以及时接替主设备工作，从而保证用户业务的连续性。此外，如果主设备和备设备中只有一方与云端设备断链，说明云端设备没有故障，这种短暂断链通常能够很快恢复，因此断链一方可以等待恢复连接后再通过云端设备进行数据备份。
然而，为了避免断链一方不能很快恢复的情形，作为另一种实施方式，只要主设备和备设备其中一方与云端设备之间发生断链超时、但主设备与备设备之间能够正常通信，主设备便直接发起本地备份机制，并在成功发起本地备份机制后将待备份信息发送至备设备进行备份。即，相对于图6-a来讲，当主设备与云端设备发生断链超时时，直接执行S603a，不再执行其它步骤；相对于图6-b来讲，当备设备与云端设备发生断链超时时，依次执行S601b和S603b，不再执行其它步骤。
需要说明的是，在上述图6-a和6-b所示的实施例中，是由主设备启动本地备份机制，而在下面图7-a和7-b所示的实施例中，是由备设备启动本地备份机制，下面将对图7-a和7-b所示的实施例进行具体介绍。
需要说明的是，相对于主设备来讲，如果备设备先检测出自己与云端设备之间发生断链超时，则按照下述图7-a所示流程来实现本地备份。当然，当主备协议规定备设备负责发起本地备份机制时，如果备设备先检测出自己与云端设备之间发生断链超时，则按照下述图7-a所示流程来实现本地备份，反之，如果主设备先检测出自己与云端设备之间发生断链超时，则按照下述图7-b所示流程以实现本地备份，具体如下。
参见图7-a所示的用户信息的本地备份方法的交互示意图，该本地备份方法可以包括以下步骤：
S701a：备设备若检测到与云端设备之间发生断链超时、且备设备与主设备之间能够正常通信，则向主设备发送第二询问消息，其中，该第二询问消息用于询问主设备与云端设备之间是否发生断链超时。
相对于主设备来讲，如果备设备先检测出与云端设备之间发生断链超时，便询问主设备是否也与云端设备发生断链超时。
之后，主设备可以在接收到第二询问消息后，根据主设备与云端设备的链接情况确定云端设备的通信状态，即确定云端设备的通信状态是正常还是异常，具体可以采用以下步骤来确定。
S702a：主设备在接收到第二询问消息后，检测主设备与云端设备之间是否发生断链超时；若是，则确定云端设备的通信状态异常，并向备设备返回第三响应消息，该第三响应消息用于告知主设备与云端设备之间发生断链超时；若否，则确定云端设备的通信状态正常，并向备设备返回第四响应消息，该第四响应消息用于告知主设备与云端设备之间未发生断链超时。
S703a：备设备若接收到主设备返回的第三响应消息，则启动主设备与备设备之间的本地备份机制。
备设备在接收到第三响应消息后，确定主设备和备设备均与云端设备发生断链超时，此种情况下，备设备判断云端设备故障，此时主设备无法向云端设备备份数据、而备设备也无法从云端设备获取备份数据。此时，备设备发起与主设备之间的三次握手，用以启动主设备与备设备之间的本地备份机制。其中，三次握手的具体流程请参见S404中的相关介绍，在此不再赘述。
S704a：主设备在本地备份机制被成功发起后，将第二用户信息发送至备设备进行备份。
在本地备份机制成功启动后，主设备便将第二用户信息直接备份至备设备，同时，主设备不再向云端设备发送备份数据，且备设备也不再从云端设备处获取备份数据。
S705a：备设备若接收到主设备返回的第四响应消息，则等待备设备与云端设备之间完成断链重建。
备设备在接收到第四响应消息后，确定只有自己与云端设备短暂断链，此时，备设备可以通过与云端设备进行断链重建，以恢复与云端设备之间的连接。
备设备在与云端设备之间完成断链重建之前，可能有一个或多个用户设备已经从主设备上线，并且，主设备已经生成了这些用户设备的待备份信息后并备份到了云端设备。因此，在断链重建完成后，备设备可以从云端设备批量获取这些数据进行备份。
参见图7-b所示的用户信息的本地备份方法的交互示意图，该本地备份方法可以包括以下步骤：
S701b：主设备若检测到与云端设备之间发生断链超时且与备设备之间能够正常通信，则向备设备发送第二通知消息，其中，所述第二通知消息用于告知所述备设备所述主设备与所述云端设备之间发生断链超时。
相对于备设备来讲，如果主设备先检测出与云端设备之间发生断链超时，便通知备设备，这样，主设备可以根据备设备针对第二通知消息的响应确定云端设备的通信状态，即确定云端设备的通信状态是正常还是异常，具体可以采用以下步骤来确定。
S702b：备设备在接收到第二通知消息后，确定备设备与云端设备之间是否发生断链超时；若是，则执行S703b；若否，则执行S705b。
如果备设备也与云端设备发生断链超时，此时主设备无法向云端设备备份数据、而备设备也无法从云端设备获取备份数据，故而，备设备判断云端设备故障。
S703b：备设备发起主设备与备设备之间的本地备份机制。
备设备判断云端设备故障后，备设备发起与主设备之间的三次握手，用以启动主设备与备设备之间的本地备份机制。其中，三次握手的具体流程请参见S404中的相关介绍，在此不再赘述。
S704b：主设备在本地备份机制被成功启动后，确定云端设备的通信状态异常，将第二用户信息发送至备设备进行备份。
在本地备份机制成功启动后，主设备将第二用户信息直接备份至备设备，同时，主设备不再向云端设备发送备份数据，且备设备也不再从云端设备处获取备份数据。
S705b：备设备向主设备返回通知响应消息，其中，该通知响应消息用于告知主设备等待与所述云端设备之间完成断链重建。
如果备设备没有与云端设备发生断链超时，即只有主设备与云端设备短暂断链，此时，备设备通知主设备等待与云端设备之间完成断链重建，主设备在接到通知后，暂时不向云端设备备份数据，而是等待与云端设备之间恢复连接后再向云端设备备份数据。
S706b：主设备接收到通知响应消息后，确定云端设备的通信状态正常，主设备与云端设备之间进行断链重建。
S707b：主设备在与云端设备之间断链重建成功后，将获取的第三用户信息批量发送至云端设备。
在主设备与云端设备发生断链后且完成断链重建成功之前，可能有一个或多个用户设备已经从主设备上线，本实施例将每一用户设备的待备份信息定义为第三用户信息，因此，在断链重建成功后，主设备可以将这些第三用户信息批量上传至云端设备，以保证备设备可以及时从云端设备处备份这些第三用户信息。
S708b：云端设备接收并存储第三用户信息。
由于云端设备记录了主设备的身份信息(比如主设备的IP地址)，因此，当云端设备接收到第三用户信息后，根据主设备身份信息可以确定第三用户信息是主设备上传的，从而存储第三用户信息。
S709b：备设备从云端设备获取第三用户信息进行备份。
接下来，云端设备通知备设备下载第三用户信息、或者云端设备直接将第三用户信息下发至备设备，从而实现用户信息的备份。
可见，从图7-a和图7-b所示的本地备份流程可知，如果主设备和备设备均与云端设备之间发生断链超时，即主设备无法向云端设备备份数据、而备设备也无法从云端设备获取备份数据，说明云端设备可能故障，这种情况下，需要将通过云端设备的备份机制，改为主设备与备设备之间的本地备份机制，这样，可以保证从主设备上线的用户信息能够且及时地在备设备侧进行备份，这样，一旦用户设备与主设备之间的通信链路发生故障，备设备可以及时接替主设备工作，从而保证用户业务的连续性。此外，如果主设备和备设备中只有一方与云端设备断链，说明云端设备没有故障，这种短暂断链通常能够很快恢复，因此断链一方可以等待恢复连接后再通过云端设备进行数据备份。
然而，为了避免断链一方不能很快恢复的情形，作为另一种实施方式，只要主设备和备设备其中一方与云端设备之间发生断链超时、但主设备与备设备之间能够正常通信，备设备便直接发起本地备份机制，并在成功发起本地备份机制后，主设备将待备份信息发送至备设备进行备份。即，相对于图7-a来讲，当备设备与云端设备发生断链超时时，依次执行S703a和S704a，不再执行其它步骤；相对于图7-b来讲，当主设备与云端设备发生断链超时时，依次执行S701b、S703b和S704b，不再执行其它步骤。
需要说明的是，当主设备或备设备一方检测出与云端设备之间的链路质量差时，如果主设备与备设备之间能够正常通信，便启动主设备与备设备之间的本地备份机制，下面将通过图8-a、8-b、9-a、9-b所示实施例进行具体介绍。此外，在本实施例的另一种实施方式中，当主设备与云端设备之间的链路质量差、且备设备与云端设备之间的链路质量也差时，如果主设备与备设备之间能够正常通信，则可以采用类似于图6-a、6-b、7-a、7-b的本地备份流程，只要将6-a、6-b、7-a、7-b所示实施例中的“断链超时”替换为“链路质量低于预设质量阈值”即可。
需要说明的是，相对于主设备来讲，如果主设备先检测出自己与云端设备之间的链路质量低于预设质量阈值，则按照下述图8-a所示流程来实现本地备份。当然，主备协议可以预先规定发起本地备份机制的路由器设备，当主备协议规定主设备负责发起本地备份机制时，如果主设备先检测出自己与云端设备之间的链路质量低于预设质量阈值，则按照下述图8-a所示流程来实现本地备份，反之，如果备设备先检测出自己与云端设备之 间的链路质量低于预设质量阈值，则按照下述图8-b所示流程以实现本地备份，具体如下。
参见图8-a所示的用户信息的本地备份方法的交互示意图，该本地备份方法可以包括以下步骤：
S801a：主设备若检测到与云端设备之间的链路质量低于预设质量阈值且与备设备之间能够正常通信，则确定云端设备的通信状态异常，并启动主设备与备设备之间的本地备份机制。
相对于备设备来讲，如果主设备先检测到与云端设备之间的链路质量差，则及时发起本地备份机制。
S802a：主设备在成功发起本地备份机制后，将第二用户信息发送至备设备进行备份。
当主设备与云端设备之间的链路质量低于预设质量阈值，说明两设备之间的链路质量较差或者控制器本身有问题，在这种情况下，如果主设备仍向云端设备备份数据，存在数据丢失的可能。因此，当主设备与备设备之间的RBS通道不断链且质量较好时，主设备可以发起与备设备之间的三次握手，用以启动主设备与备设备之间的本地备份机制，在本地备份机制成功启动后，主设备将第二用户信息备份至备设备。同时，主设备不再向云端设备发送备份数据、而备设备不再从云端设备获取备份数据。
其中，三次握手的具体流程请参见S404中的相关介绍，在此不再赘述。
参见图8-b所示的用户信息的本地备份方法的交互示意图，该本地备份方法可以包括以下步骤：
S801b：备设备若检测到与云端设备之间的链路质量低于预设质量阈值且与主设备之间能够正常通信，则向主设备发送第三通知消息。
相对于主设备来讲，如果备设备先检测与云端设备之间的链路质量差，便通知主设备自己与云端设备之间的链路质量变差，以便主设备及时启动本地备份机制。
S802b：主设备在接收到备设备发送的第三通知消息后，确定所述云端设备的通信状态异常，并启动所述主设备与所述备设备之间的本地备份机制。
S803b：主设备在成功发起本地备份机制后，将第二用户信息发送至备设备进行备份。
当备设备与云端设备之间的链路质量低于预设质量阈值，说明两设备之间的链路质量较差或者控制器本身有问题，在这种情况下，如果备设备仍从云端设备获取备份数据，存在数据丢失的可能。因此，当主设备与备设备之间的RBS通道不断链且质量较好时，主设备可以发起与备设备之间的三次握手，用以启动主设备与备设备之间的本地备份机制，在本地备份机制成功启动后，主设备将第二用户信息备份至备设备。同时，备设备不再从云端设备获取备份数据。
其中，三次握手的具体流程请参见S404中的相关介绍，在此不再赘述。
此外，当主设备与云端设备之间的链路质量差时，如果主设备与云端设备之间的链路质量较好，则主设备在向备设备备份数据的同时，也可以向云端设备备份数据；如果主设备与云端设备之间的链路质量也差，主设备不再向云端设备发送备份数据。
需要说明的是，在上述图8-a和8-b所示的实施例中，是由主设备启动本地备份机制，而在下面图9-a和9-b所示的实施例中，是由备设备启动本地备份机制，下面将对图9-a和9-b所示的实施例进行具体介绍。
需要说明的是，相对于备设备来讲，如果备设备先检测出自己与云端设备之间的链路质量低于预设质量阈值，则按照下述图9-a所示流程来实现本地备份。当然，当主备协议规定备设备负责发起本地备份机制时，如果备设备先检测出自己与云端设备之间的链路质量低于预设质量阈值，则按照下述图9-a所示流程来实现本地备份，反之，如果主设备先检测出自己与云端设备之间的链路质量低于预设质量阈值，则按照下述图9-b所示流程以实现本地备份，具体如下。
参见图9-a所示的用户信息的本地备份方法的交互示意图，该本地备份方法可以包括以下步骤：
S901a：备设备若检测到与云端设备之间的链路质量低于预设质量阈值且与主设备之间能够正常通信，则确定云端设备的通信状态异常，启动主设备与备设备之间的本地备份机制。
相对于主设备来讲，如果备设备先检测到与云端设备之间的链路质量差，则及时发起本地备份机制。
S902a：主设备在本地备份机制备被成功发起后，将第二用户信息发送至备设备进行备份。
当备设备与云端设备之间的链路质量低于预设质量阈值，说明两设备之间的链路质量较差或者控制器本身有问题，在这种情况下，如果备设备仍从云端设备获取备份数据，存在数据丢失的可能。因此，当主设备与备设备之间的RBS通道不断链且质量较好时，备设备可以发起与主设备之间的三次握手，用以启动主设备与备设备之间的本地备份机制，在本地备份机制成功启动后，主设备将第二用户信息备份至备设备。同时，备设备不再从云端设备获取备份数据。
其中，三次握手的具体流程请参见S404中的相关介绍，在此不再赘述。
此外，如果主设备与云端设备之间的链路质量较好，主设备在向备设备备份数据的同时，也可以向云端设备备份数据；如果主设备与云端设备之间的链路质量也差，主设备不再向云端设备发送备份数据。
参见图9-b所示的用户信息的本地备份方法的交互示意图，该本地备份方法可以包括以下步骤：
S901b：主设备若检测到与云端设备之间的链路质量低于预设质量阈值且与备设备之间能够正常通信，则向备设备发送第四通知消息。
相对于备设备来讲，如果主设备先检测与云端设备之间的链路质量差，便通知备设备自己与云端设备之间的链路质量变差，以便备设备及时启动本地备份机制。
S902b：备设备在接收到备设备发送的第四通知消息后，确定云端设备的通信状态异常，并启动主设备与备设备之间的本地备份机制。
S903b：主设备在本地备份机制被成功发起后，将第二用户信息发送至备设备进行备份。
当主设备与云端设备之间的链路质量低于预设质量阈值，说明两设备之间的链路质量较差或者控制器本身有问题，在这种情况下，如果主设备仍向云端设备备份数据，存在数据丢失的可能。因此，当主设备与备设备之间的RBS通道不断链且质量较好时，备设备可以发起与主设备之间的三次握手，用以启动主设备与备设备之间的本地备份机制，在本地备份机制成功启动后，主设备将第二用户信息备份至备设备。同时，主设备不再向云端设备发送备份数据、而备设备不再从云端设备获取备份数据。
其中，三次握手的具体流程请参见S404中的相关介绍，在此不再赘述。
可见，从图8-a和图8-b以及图9-a和图9-b所示的本地备份流程可知，如果主设备与云端设备之间的链路质量变差，这将导致主设备向云端设备上传的备份数据可能丢失；如果备设备与云端设备之间的链路质量变差，这将导致云端设备向备设备下发的备份数据可能丢失。当出现上述其中任一种情形或两种情形同时出现时，均不能保证备设备获取到完整的备份数据，因此，需要将通过云端设备的备份机制，改为主设备与备设备之间的本地备份机制，可以保证从主设备上线的用户信息能够完整地在备设备侧进行备份，这样，一旦用户设备与主设备之间的通信链路发生故障，备设备可以及时接替主设备工作，从而保证用户业务的连续性。
在本申请的一些实施例中，当主设备与备设备不能正常通信时，如果主设备与云端设备也不能正常通信、但备设备与云端设备之间能够正常通信。当出现这种情况时，可以进行主备身份切换，即，主设备由主设备身份切换为备设备身份，而备设备由备设备身份切换为主设备身份。
其中，主设备与备设备不能正常通信，具体可以为：主设备与备设备之间发生断链超时，或者，主设备与备设备之间的链路质量低于预设质量阈值。
其中，主设备与云端设备不能正常通信，具体可以为：主设备与云端设备之间发生断链超时，或者，主设备与云端设备之间的链路质量低于预设质量阈值。
在本实施例中，由于主设备与备设备不能正常通信，因此不能启动主设备与备设备之间的本地备份机制，此外，由于主设备与云端设备也不能正常通信，将导致主设备不能向云端设备备份数据或不能向云端设备备份完整数据。在这种情况下，通过主备身份切换，使备设备由备设备身份切换为主设备身份，使得用户设备可以通过身份切换后的主设备上线，从而使身份切换后的主设备向云端设备备份数据，进而待身份切换后的备设备与云端设备之间的链路正常后进行数据备份，以保证备份工作的可靠性。
为便于更好的实施本申请实施例的上述方案，下面还提供用于实施上述方案的相关装置。
参见图10所示，为本申请实施例提供的一种主设备1000，该主设备1000可以包括通知发送模块1001和云端备份模块1002，其中：
通知发送模块1001，用于向云端设备发送第一身份通知，所述第一身份通知为主设备具有主设备身份的通知；
状态确定模块1002，用于确定所述云端设备的通信状态；具体的实现方式可以参考下述具体模块的功能描述以及参考以上方法实施例中，如步骤S505以及图6a-9b中相关步骤的详细描述。
云端备份模块1003，用于确定所述云端设备的通信状态正常的情况下，将获取的第一用户信息上传至所述云端设备；
其中，所述第一用户信息由所述云端设备存储并提供给备设备，且所述第一用户信息是在所述云端设备的通信状态正常的情况下从所述主设备上线的用户设备的待备份信息。
其中，通知发送模块的功能实现的具体实现可以参考上述方法步骤S402；状态确定模块以及云端备份模块的功能实现可以参考上述方法步骤S501-S502。
在本申请的一些实施例中，所述主设备1000还可以包括：
本地备份模块，用于在确定所述云端设备的通信状态异常，且所述主设备与所述备设备之间能够正常通信的情况下，将获取的第二用户信息发送至所述备设备进行备份；其中，所述第二用户信息是在所述云端设备的通信状态异常的情况下从所述主设备上线的用户设备的待备份信息。
其中，本地备份模块的功能实现可以参考下述各子模块的功能以及上述图6a-9b中本地备份对应的步骤。
在本申请的一些实施例中，所述状态确定模块1002可以包括：
询问发送子模块，用于在检测到与所述云端设备之间发生断链超时后，向所述备设备发送第一询问消息，其中，所述第一询问消息用于询问所述备设备与所述云端设备之间是否发生断链超时；
第一确定子模块，用于根据从所述备设备接收到的响应消息确定所述云端设备的通信状态。
其中，询问发送子模块和第一确定子模块的功能实现可以参考上述方法步骤S601a-S604a。
在本申请的一些实施例中，所述第一确定子模块，具体用于若接收到所述备设备返回的第一响应消息，则确定所述云端设备的通信状态异常，其中所述第一响应消息用于告知所述备设备与所述云端设备之间发生断链超时；
所述本地备份模块，还用于在将获取的第二用户信息发送至所述备设备进行备份之前，启动所述主设备与所述备设备之间的本地备份机制。
在本申请的一些实施例中，所述第一确定子模块，具体用于若接收到所述备设备返回的第二响应消息，则确定所述云端设备的通信状态正常；其中所述第二响应消息用于告知所述备设备与所述云端设备之间未发生断链超时；
所述主设备1000还可以包括：
第一断链重建模块，用于与所述云端设备之间进行断链重建；
第一批量备份模块，用于在所述断链重建成功后，将获取的第三用户信息批量发送至所述云端设备，其中，所述第三用户信息由所述云端设备存储并提供给所述备设备， 且所述第三用户信息是在所述主设备与所述云端设备发生断链后且在所述断链重建成功之前从所述主设备上线的用户设备的待备份信息。
其中，第一断链重建模块和第一批量备份模块的功能实现可以参考上述方法步骤S604a-S605a。
在本申请的一些实施例中，所述状态确定模块1002可以包括：
通知接收子模块，用于接收所述备设备发送的第一通知消息，其中，所述第一通知消息用于告知所述备设备与所述云端设备之间发生断链超时；
第二确定子模块，用于在接收到所述第一通知消息后，根据所述主设备与所述云端设备的链接情况确定所述云端设备的通信状态。
其中，通知接收子模块和第二确定子模块的功能实现可以参考上述方法步骤S602b。
在本申请的一些实施例中，所述第二确定子模块，具体用于若确定所述主设备与所述云端设备之间发生断链超时，则确定所述云端设备的通信状态异常；
所述本地备份模块，还用于在将获取的第二用户信息发送至所述备设备进行备份之前，启动所述主设备与所述备设备之间的本地备份机制。
其中，本地备份模块的功能实现可以参考上述方法步骤S603b。
在本申请的一些实施例中，所述第二确定子模块，具体用于若确定与所述云端设备之间未发生断链超时，则确定所述云端设备的通信状态正常；
所述主设备1000还可以包括：
重建通知模块，用于通知所述备设备等待与所述云端设备之间完成断链重建。
其中，重建通知模块的功能实现可以参考上述方法步骤S604b。
在本申请的一些实施例中，所述状态确定模块1002可以包括：
询问接收子模块，用于接收所述备设备发送的第二询问消息，所述第二询问消息是所述备设备确定与所述云端设备之间发生断链超时后发送的、且所述第二询问消息用于询问所述主设备与所述云端设备之间是否发生断链超时；
第三确定子模块，用于在接收到所述第二询问消息后，根据所述主设备与所述云端设备的链接情况确定所述云端设备的通信状态。
其中，询问接收子模块的功能实现可以参考上述方法步骤S701a；第三确定子模块的功能实现可以参考上述方法步骤S702a。
在本申请的一些实施例中，所述第三确定子模块，具体用于若确定与所述云端设备之间发生断链超时，则确定所述云端设备的通信状态异常；
所述主设备1000还可以包括：
第一响应发送模块，用于在所述云端备份模块将获取的第二用户信息发送至所述备设备进行备份之前，向所述备设备发送第三响应消息，以便所述备设备接收到所述第三响应消息后启动所述主设备与所述备设备之间的本地备份机制，其中，所述第三响应消息为所述主设备与所述云端设备之间发生断链超时。
其中，第一响应发送模块的功能实现可以参考上述方法步骤S702a。
在本申请的一些实施例中，所述第三确定子模块，具体用于若确定与所述云端设备之间未发生断链超时，则确定所述云端设备的通信状态正常；
所述主设备1000还可以包括：
第二响应发送模块，用于向所述备设备发送第四响应消息，以便所述备设备接收到所述第四响应消息后等待与所述云端设备完成断链重建，其中，所述第四响应消息为所述主设备与所述云端设备之间未发生断链超时。
其中，第二响应发送模块的功能实现可以参考上述方法步骤S702a。
在本申请的一些实施例中，所述状态确定模块1002可以包括：
通知发送子模块，用于在检测到与所述云端设备之间发生断链超时后向所述备设备发送的第二通知消息，其中，所述第二通知消息用于告知所述备设备所述主设备与所述云端设备之间发生断链超时；
第四确定子模块，用于根据所述备设备针对所述第二通知消息的响应确定所述云端设备的通信状态。
其中，通知发送子模块的功能实现可以参考上述方法步骤S701b；第四确定子模块的功能实现可以参考上述方法步骤S702b-S706b。
在本申请的一些实施例中，所述第四确定子模块，具体用于若确定所述备设备已启动所述主设备与所述备设备之间的本地备份机制，则确定所述云端设备的通信状态异常。
在本申请的一些实施例中，所述第四确定子模块，具体用于若接收到所述备设备返回的通知响应消息，则确定所述云端设备的通信状态正常；其中，所述通知响应消息用于告知所述主设备等待与所述云端设备之间完成断链重建；
所述主设备1000还可以包括：
第二断链重建模块，用于与所述云端设备之间进行断链重建；
第二批量备份模块，用于在所述断链重建成功后，将获取的第三用户信息批量发送至所述云端设备，所述第三用户信息由所述云端设备存储并提供给所述备设备，且所述第三用户信息是在所述主设备与所述云端设备发生断链后且在所述断链重建成功之前从所述主设备上线的用户设备的待备份信息。
其中，第二断链重建模块的功能实现可以参考上述方法步骤S706b；第四确定子模块的功能实现可以参考上述方法步骤S707b。
在本申请的一些实施例中，所述状态确定模块1002，具体用于若确定所述主设备与所述云端设备之间的链路质量低于预设质量阈值、和/或确定所述备设备与所述云端设备之间的链路质量低于预设质量阈值，则确定所述云端设备的通信状态异常。
其中，状态确定模块的功能实现可以参考上述方法步骤S801a-S802a以及S801b-S803b。
在本申请的一些实施例中，所述主设备1000还可以包括：
身份切换模块，用于在确定所述主设备与所述云端设备之间不能正常通信、且所述主设备与所述备设备之间不能正常通信的情况下，则所述主设备的所述主设备身份切换为备设备身份。
其中，身份切换模块的功能实现可以参考上述方法中关于主备身份切换的内容。
在本申请的一些实施例中，所述主设备与所述云端设备之间不能正常通信，可以包括：
所述主设备与所述云端设备之间发生断链超时，或者，所述主设备与所述云端设备之间的链路质量低于预设质量阈值。
在本申请的一些实施例中，所述主设备与所述备设备之间不能正常通信，可以包括：
所述主设备与所述备设备之间发生断链超时，或者，所述主设备与所述备设备之间的链路质量低于预设质量阈值。
通过前述内容对本申请实施例的举例说明可知，当云端设备的通信状态正常时，如果有用户设备从主设备上线，主设备将生成该用户设备的待备份信息，并将该待备份信息上传至云端设备，这样，备设备便可以从云端设备获取该待备份信息以进行备份，可见，本申请实施例的主设备是通过云端设备向备设备备份信息的，避免了主设备直接向备设备备份信息所导致的用户业务不连续的问题。进一步地，当云端设备的通信状态异常时，即无法通过云端设备实现数据备份的情况下，如果主设备与备设备之间能够正常通信，主设备可以直接向备设备备份信息，以提高备份工作的可靠性。
参见图11所示，为本申请实施例提供的一种云端设备1100，该云端设备1100可以包括通知接收模块1101和云端备份模块1102，其中：
通知接收模块1101，用于接收主设备发送的第一身份通知以及备设备发送的第二身份通知，所述第一身份通知为所述主设备具有主设备身份的通知，所述第二身份通知为所述备设备具有备设备身份的通知；
云端备份模块1102，用于接收并存储所述主设备上传的第一用户信息，并将所述第一用户信息提供给所述备设备；
其中，所述第一用户信息是所述主设备确定所述云端设备的通信状态正常的情况下上传的，且所述第一用户信息是当所述云端设备的通信状态正常的情况下从所述主设备上线的用户设备的待备份信息。
其中，通知接收模块的功能实现可以参考上述方法步骤S402-S403；云端备份模块的功能实现可以参考上述方法步骤S503。
通过前述内容对本申请实施例的举例说明可知，当云端设备的通信状态正常时，如果有用户设备从主设备上线，主设备将生成该用户设备的待备份信息，并将该待备份信息上传至云端设备，这样，备设备便可以从云端设备获取该待备份信息以进行备份，可见，本申请实施例的主设备是通过云端设备向备设备备份信息的，避免了主设备直接向备设备备份信息所导致的用户业务不连续的问题。
参见图12所示，为本申请实施例提供的一种备设备1200，该备设备1200可以包括通知发送模块1201和云端备份模块1202，其中：
通知发送模块1201，用于向云端设备发送第二身份通知，所述第二身份通知为所述备设备具有备设备身份的通知；
云端备份模块1202，用于从所述云端设备获取第一用户信息进行备份；
其中，所述第一用户信息是所述主设备确定所述云端设备的通信状态正常的情况下上传至所述云端设备存储的，且所述第一用户信息是当所述云端设备的通信状态正常的情况下从所述主设备上线的用户设备的待备份信息。
其中，通知发送模块的功能实现可以参考上述方法步骤S402；云端备份模块的功能实现可以参考上述方法步骤S504。
在本申请的一些实施例中，所述备设备1200还可以包括：
本地备份模块，用于在所述云端设备的通信状态异常的情况下，接收所述主设备发送的第二用户信息进行备份；
其中，所述第二用户信息是在所述云端设备的通信状态异常的情况下从所述主设备上线的用户设备的待备份信息；所述第二用户信息是所述主设备在确定所述云端设备的通信状态异常且所述主设备与所述备设备之间能够正常通信的情况下发送的。
其中，本地备份模块的功能实现可以参考下述各子模块的功能以及上述图6a-9b中本地备份对应的步骤。
在本申请的一些实施例中，所述备设备1200还可以包括：
消息返回模块，用于若接收到所述主设备发送的第一询问消息，则向所述主设备返回响应消息；
其中，所述第一询问消息是所述主设备在检测到与所述云端设备之间发生断链超时后发送的，且所述第一询问消息用于询问所述备设备与所述云端设备之间是否发生断链超时；所述备设备返回的响应消息用于使所述主设备确定所述云端设备的通信状态。
其中，消息返回模块的功能实现可以参考上述方法步骤S602a。
在本申请的一些实施例中，所述消息返回模块，具体用于向所述主设备返回第一响应消息；
其中，所述第一响应消息用于告知所述备设备与所述云端设备之间发生断链超时，以使得所述主设备在所述备设备与所述云端设备之间发生断链超时后确定所述云端设备的通信状态异常，并在确定所述云端设备的通信状态异常之后启动所述主设备与所述备设备之间的本地备份机制；
所述本地备份模块，具体用于接收所述主设备启动所述本地备份机制后发送的第二用户信息进行备份。
在本申请的一些实施例中，所述消息返回模块，具体用于向所述主设备返回第二响应消息；
其中，所述第二响应消息用于告知所述备设备与所述云端设备之间未发生断链超时，以使得所述主设备在所述备设备与所述云端设备之间未发生断链超时后确定所述云端设备的通信状态正常，并在确定所述云端设备的通信状态正常之后使所述主设备与所述云端设备之间进行断链重建，以及使所述主设备在所述断链重建成功后将获取的第三用户信息批量发送至所述云端设备；
其中，所述第三用户信息由所述云端设备存储并提供给所述备设备，且所述第三用户信息是在所述主设备与所述云端设备发生断链后且在所述断链重建成功之前从所述主设备上线的用户设备的待备份信息。
在本申请的一些实施例中，所述备设备1200还可以包括：
通知发送模块，用于向所述主设备发送第一通知消息；
其中，所述第一通知消息用于告知所述备设备与所述云端设备之间发生断链超时，以使得所述主设备在所述主设备与所述云端设备之间发生断链超时后确定所述云端设备的通信状态异常。
其中，通知发送模块的功能实现可以参考上述方法步骤S601b。
在本申请的一些实施例中，所述备设备1200还可以包括：
通知接收模块，用于接收所述主设备发送的重建等待通知；
其中，所述重建等待通知用于通知所述备设备等待与所述云端设备之间完成断链重建，所述重建等待通知是所述主设备确定所述云端设备的通信状态正常后发送的，所述通信状态正常是所述主设备确定与所述云端设备之间未发生断链超时后确定的。
其中，通知接收模块的功能实现可以参考上述方法步骤S604b。
在本申请的一些实施例中，所述备设备1200还可以包括：
询问发送模块，用于确定与所述云端设备之间发生断链超时后，向所述主设备发送第二询问消息，其中，所述第二询问消息用于询问所述主设备与所述云端设备之间是否发生断链超时；
所述本地备份模块，具体用于若接收到所述主设备返回的第三响应消息，则根据所述第三响应消息获知所述云端设备的通信状态异常，启动所述主设备与所述备设备之间的本地备份机制，在成功启动所述本地备份机制后，接收所述主设备发送的第二用户信息进行备份，其中，所述第三响应消息用于告知所述主设备与所述云端设备之间发生断链超时。
其中，询问发送模块的功能实现可以参考上述方法步骤S701a；本地备份模块的功能实现可以参考上述方法步骤S703a-S704a。
在本申请的一些实施例中，所述备设备1200还可以包括：
断链重建模块，用于若接收到所述主设备返回的第四响应消息，则等待与所述云端设备完成断链重建，其中，所述第四响应消息用于告知所述主设备与所述云端设备之间未发生断链超时。
其中，断链重建模块的功能实现可以参考上述方法步骤S705a。
在本申请的一些实施例中，所述备设备1200还可以包括：
通知响应模块，用于若接收到所述主设备发送的第二通知消息，则针对所述第二通知消息进行响应；
其中，所述第二通知消息是所述主设备在检测到与所述云端设备之间发生断链超时后发送的，且所述第二通知消息用于告知所述备设备所述主设备与所述云端设备之间发生断链超时；所述备设备针对所述第二通知消息的响应使所述主设备确定所述云端设备的通信状态。
其中，通知响应模块的功能实现可以参考上述方法步骤S702b、S703b和S705b。
在本申请的一些实施例中，所述通知响应模块，具体用于启动所述主设备与所述备设备之间的本地备份机制，以便所述主设备在所述本地备份机制被启动后确定所述云端设备的通信状态异常；
所述本地备份模块，具体用于在成功启动所述本地备份机制后，接收所述主设备发送的第二用户信息进行备份。
其中，通知响应模块的功能实现可以参考上述方法步骤S704b。
在本申请的一些实施例中，所述通知响应模块，具体用于向所述主设备返回通知响应消息；
其中，所述通知响应消息用于告知所述主设备等待与所述云端设备之间完成断链重建，以使所述主设备在所述断链重建成功后将获取的第三用户信息批量发送至所述云端设备；所述第三用户信息由所述云端设备存储并提供给所述备设备，且所述第三用户信息是在所述主设备与所述云端设备发生断链后且在所述断链重建成功之前从所述主设备上线的用户设备的待备份信息。
在本申请的一些实施例中，所述备设备1200还可以包括：
所述本地备份模块，还用于若确定所述备设备与所述云端设备之间的链路质量低于预设质量阈值、和/或确定所述主设备与所述云端设备之间的链路质量低于预设质量阈值，则启动所述主设备与所述备设备之间的本地备份机制，以便所述主设备在所述本地备份机制被启动后确定所述云端设备的通信状态异常。
其中，本地备份模块的功能实现可以参考上述方法步骤S901a-S902a以及S901b-S903b。
在本申请的一些实施例中，所述备设备1200还可以包括：
身份切换模块，用于在确定所述备设备与所述云端设备之间能够正常通信且所述备设备与所述主设备之间不能正常通信的情况下，则所述备设备的所述备设备身份切换为主设备身份。
其中，身份切换模块的功能实现可以参考上述方法中关于主备身份切换的内容。
在本申请的一些实施例中，所述备设备与所述主设备不能正常通信，可以包括：所述备设备与所述主设备之间发生断链超时，或者，所述备设备与所述主设备之间的链路质量低于预设质量阈值。
通过前述内容对本申请实施例的举例说明可知，当云端设备的通信状态正常时，如果有用户设备从主设备上线，主设备将生成该用户设备的待备份信息，并将该待备份信息上传至云端设备，这样，备设备便可以从云端设备获取该待备份信息以进行备份，可见，本申请实施例的主设备是通过云端设备向备设备备份信息的，避免了主设备直接向备设备备份信息所导致的用户业务不连续的问题。进一步地，当云端设备的通信状态异常时，即无法通过云端设备实现数据备份的情况下，如果主设备与备设备之间能够正常通信，主设备可以直接向备设备备份信息，以提高备份工作的可靠性。
需要说明的是，上述设备各模块之间的信息交互、执行过程等内容，由于与本申请方法实施例基于同一构思，其带来的技术效果与本申请方法实施例相同，具体内容可参见本申请前述所示的方法实施例中的叙述，此处不再赘述。
接下来介绍本申请实施例提供的另一种主设备，所述主设备包括：处理器，存储器，通信接口和总线；所述处理器、通信接口、存储器通过所述总线相互的通信；所述通信接口，用于接收和发送数据；所述存储器用于存储指令；所述处理器用于执行所述存储器中的所述指令，执行前述的信息备份方法。
接下来对前述的主设备进行详细说明，请参阅图13所示，主设备1300，包括：接收器1301、发射器1302、处理器1303和存储器1304(其中主设备1300中的处理器1303的数量可以一个或多个，图13中以一个处理器为例)。其中，通信接口可包括接收器1301、发射器1302。在本申请的一些实施例中，接收器1301、发射器1302、处理器1303和存储器1304可通过总线或其它方式连接，其中，图13中以通过总线连接为例。
存储器1304可以包括只读存储器和随机存取存储器，并向处理器1303提供指令和数据。存储器1304的一部分还可以包括非易失性随机存取存储器(英文全称：Non-Volatile Random Access Memory，英文缩写：NVRAM)。存储器1304存储有操作系统和操作指令、可执行模块或者数据结构，或者它们的子集，或者它们的扩展集，其中，操作指令可包括各种操作指令，用于实现各种操作。操作系统可包括各种系统程序，用于实现各种基础业务以及处理基于硬件的任务。
处理器1303控制主设备1300的操作，处理器1303还可以称为中央处理单元(英文全称：Central Processing Unit，英文简称：CPU)。具体的应用中，的各个组件通过总线系统耦合在一起，其中总线系统除包括数据总线之外，还可以包括电源总线、控制总线和状态信号总线等。但是为了清楚说明起见，在图中将各种总线都称为总线系统。
上述本申请实施例揭示的方法可以应用于处理器1303中，或者由处理器1303实现。处理器1303可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器1303中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1303可以是通用处理器、数字信号处理器(英文全称：digital signal processing，英文缩写：DSP)、专用集成电路(英文全称：Application Specific Integrated Circuit，英文缩写：ASIC)、现场可编程门阵列(英文全称：Field-Programmable Gate Array，英文缩写：FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1304，处理器1303读取存储器1304中的信息，结合其硬件完成上述方法的步骤。
接收器1301可用于接收输入的数字或字符信息，以及产生与主设备1300的相关设置以及功能控制有关的信号输入，发射器1302可包括显示屏等显示设备，发射器1302可用于通过外接接口输出数字或字符信息。
本申请实施例中，处理器1303，用于执行前述主设备侧执行的信息备份方法。
接下来介绍本申请实施例提供的另一种云端设备，所述云端设备包括：处理器，存储器，通信接口和总线；所述处理器、通信接口、存储器通过所述总线相互的通信；所述通信接口，用于接收和发送数据；所述存储器用于存储指令；所述处理器用于执行所述存储器中的所述指令，执行前述的信息备份方法。
接下来对前述的云端设备进行详细说明，请参阅图14所示，云端设备1400，包括：接收器1401、发射器1402、处理器1403和存储器1404(其中云端设备1400中的处理器1403的数量可以一个或多个，图14中以一个处理器为例)。其中，通信接口可包括接收器1401、发射器1402。在本申请的一些实施例中，接收器1401、发射器1402、处理器1403和存储器1404可通过总线或其它方式连接，其中，图14中以通过总线连接为例。
存储器1404可以包括只读存储器和随机存取存储器，并向处理器1403提供指令和数据。存储器1404的一部分还可以包括非易失性随机存取存储器(英文全称：Non-Volatile Random Access Memory，英文缩写：NVRAM)。存储器1404存储有操作系统和操作指令、可执行模块或者数据结构，或者它们的子集，或者它们的扩展集，其中，操作指令可包括各种操作指令，用于实现各种操作。操作系统可包括各种系统程序，用于实现各种基础业务以及处理基于硬件的任务。
处理器1403控制云端设备1400的操作，处理器1403还可以称为中央处理单元(英文全称：Central Processing Unit，英文简称：CPU)。具体的应用中，的各个组件通过总线系统耦合在一起，其中总线系统除包括数据总线之外，还可以包括电源总线、控制总线和状态信号总线等。但是为了清楚说明起见，在图中将各种总线都称为总线系统。
上述本申请实施例揭示的方法可以应用于处理器1403中，或者由处理器1403实现。处理器1403可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器1403中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1403可以是通用处理器、数字信号处理器(英文全称：digital signal processing，英文缩写：DSP)、专用集成电路(英文全称：Application Specific Integrated Circuit，英文缩写：ASIC)、现场可编程门阵列(英文全称：Field-Programmable Gate Array，英文缩写：FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1404，处理器1403读取存储器1404中的信息，结合其硬件完成上述方法的步骤。
接收器1401可用于接收输入的数字或字符信息，以及产生与云端设备1400的相关设置以及功能控制有关的信号输入，发射器1402可包括显示屏等显示设备，发射器1402可用于通过外接接口输出数字或字符信息。
本申请实施例中，处理器1303，用于执行前述云端设备侧执行的信息备份方法。
接下来介绍本申请实施例提供的另一种备设备，所述备设备包括：处理器，存储器，通信接口和总线；所述处理器、通信接口、存储器通过所述总线相互的通信；所述通信接口，用于接收和发送数据；所述存储器用于存储指令；所述处理器用于执行所述存储器中的所述指令，执行前述的信息备份方法。
接下来对前述的备设备进行详细说明，请参阅图15所示，备设备1500，包括：接收器1501、发射器1502、处理器1503和存储器1504(其中备设备1500中的处理器1503的数量可以一个或多个，图15中以一个处理器为例)。其中，通信接口可包括接收器1501、发射器1502。在本申请的一些实施例中，接收器1501、发射器1502、处理器1503和存储器1504可通过总线或其它方式连接，其中，图15中以通过总线连接为例。
存储器1504可以包括只读存储器和随机存取存储器，并向处理器1503提供指令和数据。存储器1504的一部分还可以包括非易失性随机存取存储器(英文全称：Non-Volatile Random Access Memory，英文缩写：NVRAM)。存储器1504存储有操作系统和操作指令、可执行模块或者数据结构，或者它们的子集，或者它们的扩展集，其中，操作指令可包括各种操作指令，用于实现各种操作。操作系统可包括各种系统程序，用于实现各种基础业务以及处理基于硬件的任务。
处理器1503控制备设备1500的操作，处理器1503还可以称为中央处理单元(英文全称：Central Processing Unit，英文简称：CPU)。具体的应用中，的各个组件通过总线系统耦合在一起，其中总线系统除包括数据总线之外，还可以包括电源总线、控制总线和状态信号总线等。但是为了清楚说明起见，在图中将各种总线都称为总线系统。
上述本申请实施例揭示的方法可以应用于处理器1503中，或者由处理器1503实现。处理器1503可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器1503中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1503可以是通用处理器、数字信号处理器(英文全称：digital signal processing，英文缩写：DSP)、专用集成电路(英文全称：Application Specific Integrated Circuit，英文缩写：ASIC)、现场可编程门阵列(英文全称：Field-Programmable Gate Array，英文缩写：FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1504，处理器1503读取存储器1504中的信息，结合其硬件完成上述方法的步骤。
接收器1501可用于接收输入的数字或字符信息，以及产生与备设备1500的相关设置以及功能控制有关的信号输入，发射器1502可包括显示屏等显示设备，发射器1502可用于通过外接接口输出数字或字符信息。
本申请实施例中，处理器1503，用于执行前述备设备侧执行的信息备份方法。
本申请实施例还提供一种计算机存储介质，其中，该计算机存储介质存储有程序，该程序执行包括上述方法实施例中记载的部分或全部步骤。
本申请实施例还提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行包括上述方法实施例中记载的部分或全部步骤。
另外需说明的是，以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。另外，本申请提供的装置实施例附图中，模块之间的连接关系表示它们之间具有通信连接，具体可以实现为一条或多条通信总线或信号线。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本申请可借助软件加必需的通用硬件的方式来实现，当然也可以通过专用硬件包括专用集成电路、专用CPU、专用存储器、专用元器件等来实现。一般情况下，凡由计算机程序完成的功能都可以很容易地用相应的硬件来实现，而且，用来实现同一功能的具体硬件结构也可以是多种多样的，例如模拟电路、数字电路或专用电路等。但是，对本申请而言更多情况下软件程序实现是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在可读取的存储介质中，如计算机的软盘、U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述的方法。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。
所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存储的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。

Claims (55)

  1. 一种信息备份方法，其特征在于，所述方法应用于通信系统中，所述通信系统包括主设备、备设备和云端设备，所述方法由所述主设备执行；所述方法包括：
    所述主设备向所述云端设备发送第一身份通知，所述第一身份通知为所述主设备具有主设备身份的通知；
    所述主设备确定所述云端设备的通信状态；
    所述主设备在确定所述云端设备的通信状态正常的情况下，将获取的第一用户信息上传至所述云端设备；
    其中，所述第一用户信息由所述云端设备存储并提供给所述备设备，且所述第一用户信息是在所述云端设备的通信状态正常的情况下从所述主设备上线的用户设备的待备份信息。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述主设备在确定所述云端设备的通信状态异常，且所述主设备与所述备设备之间能够正常通信的情况下，将获取的第二用户信息发送至所述备设备进行备份；
    其中，所述第二用户信息是在所述云端设备的通信状态异常的情况下从所述主设备上线的用户设备的待备份信息。
  3. 根据权利要求2所述的方法，其特征在于，所述主设备确定所述云端设备的通信状态包括：
    所述主设备在检测到与所述云端设备之间发生断链超时后，向所述备设备发送第一询问消息，其中，所述第一询问消息用于询问所述备设备与所述云端设备之间是否发生断链超时；
    所述主设备根据从所述备设备接收到的响应消息确定所述云端设备的通信状态。
  4. 根据权利要求3所述的方法，其特征在于，所述主设备根据从所述备设备接收到的响应消息确定所述云端设备的通信状态，包括：
    所述主设备若接收到所述备设备返回的第一响应消息，则确定所述云端设备的通信状态异常，其中所述第一响应消息用于告知所述备设备与所述云端设备之间发生断链超时；
    在将获取的第二用户信息发送至所述备设备进行备份之前，所述方法还包括：
    所述主设备启动所述主设备与所述备设备之间的本地备份机制。
  5. 根据权利要求3所述的方法，其特征在于，所述主设备根据从所述备设备接收到的响应消息确定所述云端设备的通信状态，包括：
    所述主设备若接收到所述备设备返回的第二响应消息，则确定所述云端设备的通信状态正常；其中所述第二响应消息用于告知所述备设备与所述云端设备之间未发生断链超时；
    所述方法还包括：
    所述主设备与所述云端设备之间进行断链重建；
    所述主设备在所述断链重建成功后，将获取的第三用户信息批量发送至所述云端设备，其中，所述第三用户信息由所述云端设备存储并提供给所述备设备，且所述第三用户信息是在所述主设备与所述云端设备发生断链后且在所述断链重建成功之前从所述主设备上线的用户设备的待备份信息。
  6. 根据权利要求2所述的方法，其特征在于，所述主设备确定所述云端设备的通信状态，包括：
    所述主设备接收所述备设备发送的第一通知消息，其中，所述第一通知消息用于告知所述备设备与所述云端设备之间发生断链超时；
    在接收到所述第一通知消息后，所述主设备根据所述主设备与所述云端设备的链接情况确定所述云端设备的通信状态。
  7. 根据权利要求6所述的方法，其特征在于，所述主设备根据所述主设备与所述云端设备的链接情况确定所述云端设备的通信状态，包括：
    所述主设备若确定所述主设备与所述云端设备之间发生断链超时，则确定所述云端设备的通信状态异常；
    在将获取的第二用户信息发送至所述备设备进行备份之前，所述方法还包括：
    所述主设备启动所述主设备与所述备设备之间的本地备份机制。
  8. 根据权利要求6所述的方法，其特征在于，所述主设备根据所述主设备与所述云端设备的链接情况确定所述云端设备的通信状态，包括：
    所述主设备若确定与所述云端设备之间未发生断链超时，则确定所述云端设备的通信状态正常；
    所述方法还包括：
    所述主设备通知所述备设备等待与所述云端设备之间完成断链重建。
  9. 根据权利要求2所述的方法，其特征在于，所述主设备确定所述云端设备的通信状态，包括：
    所述主设备接收所述备设备发送的第二询问消息，所述第二询问消息是所述备设备确定与所述云端设备之间发生断链超时后发送的、且所述第二询问消息用于询问所述主设备与所述云端设备之间是否发生断链超时；
    所述主设备在接收到所述第二询问消息后，根据所述主设备与所述云端设备的链接情况确定所述云端设备的通信状态。
  10. 根据权利要求9所述的方法，其特征在于，所述主设备根据所述主设备与所述云端设备的链接情况确定所述云端设备的通信状态，包括：
    所述主设备若确定与所述云端设备之间发生断链超时，则确定所述云端设备的通信状态异常；
    在将获取的第二用户信息发送至所述备设备进行备份之前，所述方法还包括：
    所述主设备向所述备设备发送第三响应消息，以便所述备设备接收到所述第三响应消息后启动所述主设备与所述备设备之间的本地备份机制，其中，所述第三响应消息为所述主设备与所述云端设备之间发生断链超时。
  11. 根据权利要求9所述的方法，其特征在于，所述主设备根据所述主设备与所述云端设备的链接情况确定所述云端设备的通信状态，包括：
    所述主设备若确定与所述云端设备之间未发生断链超时，则确定所述云端设备的通信状态正常；
    所述方法还包括：
    所述主设备向所述备设备发送第四响应消息，以便所述备设备接收到所述第四响应消息后等待与所述云端设备完成断链重建，其中，所述第四响应消息为所述主设备与所述云端设备之间未发生断链超时。
  12. 根据权利要求2所述的方法，其特征在于，所述主设备确定所述云端设备的通信状态包括：
    所述主设备在检测到与所述云端设备之间发生断链超时后向所述备设备发送的第二通知消息，其中，所述第二通知消息用于告知所述备设备所述主设备与所述云端设备之间发生断链超时；
    所述主设备根据所述备设备针对所述第二通知消息的响应确定所述云端设备的通信状态。
  13. 根据权利要求12所述的方法，其特征在于，所述主设备根据所述备设备针对所述第二通知消息的响应确定所述云端设备的通信状态，包括：
    若所述主设备确定所述备设备已启动所述主设备与所述备设备之间的本地备份机制，则确定所述云端设备的通信状态异常。
  14. 根据权利要求12所述的方法，其特征在于，所述主设备根据所述备设备针对所述第二通知消息的响应确定所述云端设备的通信状态，包括：
    所述主设备若接收到所述备设备返回的通知响应消息，则确定所述云端设备的通信状态正常；其中，所述通知响应消息用于告知所述主设备等待与所述云端设备之间完成断链重建；
    所述方法还包括：
    所述主设备与所述云端设备之间进行断链重建；
    所述主设备在所述断链重建成功后，将获取的第三用户信息批量发送至所述云端设备，所述第三用户信息由所述云端设备存储并提供给所述备设备，且所述第三用户信息是在所述主设备与所述云端设备发生断链后且在所述断链重建成功之前从所述主设备上线的用户设备的待备份信息。
  15. 根据权利要求2所述的方法，其特征在于，所述主设备确定所述云端设备的通信状态异常包括，包括：
    所述主设备若确定所述主设备与所述云端设备之间的链路质量低于预设质量阈值、和/或确定所述备设备与所述云端设备之间的链路质量低于预设质量阈值，则确定所述云端设备的通信状态异常。
  16. 根据权利要求1至15任一项所述的方法，其特征在于，所述方法还包括：
    所述主设备在确定所述主设备与所述云端设备之间不能正常通信、且所述主设备与所述备设备之间不能正常通信的情况下，则所述主设备的所述主设备身份切换为备设备身 份。
  17. 根据权利要求16所述的方法，其特征在于，所述主设备与所述云端设备之间不能正常通信，包括：
    所述主设备与所述云端设备之间发生断链超时，或者，所述主设备与所述云端设备之间的链路质量低于预设质量阈值。
  18. 根据权利要求16所述的方法，其特征在于，所述主设备与所述备设备之间不能正常通信，包括：
    所述主设备与所述备设备之间发生断链超时，或者，所述主设备与所述备设备之间的链路质量低于预设质量阈值。
  19. 一种信息备份方法，其特征在于，所述方法应用于通信系统中，所述通信系统包括主设备、备设备和云端设备，所述方法由所述云端设备执行；所述方法包括：
    所述云端设备接收所述主设备发送的第一身份通知以及所述备设备发送的第二身份通知，所述第一身份通知为所述主设备具有主设备身份的通知，所述第二身份通知为所述备设备具有备设备身份的通知；
    所述云端设备接收并存储所述主设备上传的第一用户信息，并将所述第一用户信息提供给所述备设备；
    其中，所述第一用户信息是所述主设备确定所述云端设备的通信状态正常的情况下上传的，且所述第一用户信息是当所述云端设备的通信状态正常的情况下从所述主设备上线的用户设备的待备份信息。
  20. 一种信息备份方法，其特征在于，所述方法应用于通信系统中，所述通信系统包括主设备、备设备和云端设备，所述方法由所述备设备执行；所述方法包括：
    所述备设备向所述云端设备发送第二身份通知，所述第二身份通知为所述备设备具有备设备身份的通知；
    所述备设备从所述云端设备获取第一用户信息进行备份；
    其中，所述第一用户信息是所述主设备确定所述云端设备的通信状态正常的情况下上传至所述云端设备存储的，且所述第一用户信息是当所述云端设备的通信状态正常的情况下从所述主设备上线的用户设备的待备份信息。
  21. 根据权利要求20所述的方法，其特征在于，所述方法还包括：
    在所述云端设备的通信状态异常的情况下，所述备设备接收所述主设备发送的第二用户信息进行备份；
    其中，所述第二用户信息是在所述云端设备的通信状态异常的情况下从所述主设备上线的用户设备的待备份信息；所述第二用户信息是所述主设备在确定所述云端设备的通信状态异常且所述主设备与所述备设备之间能够正常通信的情况下发送的。
  22. 根据权利要求21所述的方法，其特征在于，所述方法还包括：
    所述备设备若接收到所述主设备发送的第一询问消息，则向所述主设备返回响应消息；
    其中，所述第一询问消息是所述主设备在检测到与所述云端设备之间发生断链超时后发送的，且所述第一询问消息用于询问所述备设备与所述云端设备之间是否发生断链超 时；所述备设备返回的响应消息用于使所述主设备确定所述云端设备的通信状态。
  23. 根据权利要求22所述的方法，其特征在于，所述备设备向所述主设备返回响应消息，包括：
    所述备设备向所述主设备返回第一响应消息；
    其中，所述第一响应消息用于告知所述备设备与所述云端设备之间发生断链超时，以使得所述主设备在所述备设备与所述云端设备之间发生断链超时后确定所述云端设备的通信状态异常，并在确定所述云端设备的通信状态异常之后启动所述主设备与所述备设备之间的本地备份机制；
    所述备设备接收所述主设备发送的第二用户信息进行备份，包括：
    所述备设备接收所述主设备启动所述本地备份机制后发送的第二用户信息进行备份。
  24. 根据权利要求22所述的方法，其特征在于，所述备设备向所述主设备返回响应消息，包括：
    所述备设备向所述主设备返回第二响应消息；
    其中，所述第二响应消息用于告知所述备设备与所述云端设备之间未发生断链超时，以使得所述主设备在所述备设备与所述云端设备之间未发生断链超时后确定所述云端设备的通信状态正常，并在确定所述云端设备的通信状态正常之后使所述主设备与所述云端设备之间进行断链重建，以及使所述主设备在所述断链重建成功后将获取的第三用户信息批量发送至所述云端设备；
    其中，所述第三用户信息由所述云端设备存储并提供给所述备设备，且所述第三用户信息是在所述主设备与所述云端设备发生断链后且在所述断链重建成功之前从所述主设备上线的用户设备的待备份信息。
  25. 根据权利要求21所述的方法，其特征在于，所述方法还包括：
    所述备设备向所述主设备发送第一通知消息；
    其中，所述第一通知消息用于告知所述备设备与所述云端设备之间发生断链超时，以使得所述主设备在所述主设备与所述云端设备之间发生断链超时后确定所述云端设备的通信状态异常。
  26. 根据权利要求25所述的方法，其特征在于，所述方法还包括：
    所述备设备接收所述主设备发送的重建等待通知；
    其中，所述重建等待通知用于通知所述备设备等待与所述云端设备之间完成断链重建，所述重建等待通知是所述主设备确定所述云端设备的通信状态正常后发送的，所述通信状态正常是所述主设备确定与所述云端设备之间未发生断链超时后确定的。
  27. 根据权利要求21所述的方法，其特征在于，所述方法还包括：
    所述备设备确定与所述云端设备之间发生断链超时后，向所述主设备发送第二询问消息，其中，所述第二询问消息用于询问所述主设备与所述云端设备之间是否发生断链超时；
    所述备设备若接收到所述主设备返回的第三响应消息，则根据所述第三响应消息获知所述云端设备的通信状态异常，启动所述主设备与所述备设备之间的本地备份机制，其中，所述第三响应消息用于告知所述主设备与所述云端设备之间发生断链超时；
    所述备设备接收所述主设备发送的第二用户信息进行备份，包括：
    所述备设备在成功启动所述本地备份机制后，接收所述主设备发送的第二用户信息进行备份。
  28. 根据权利要求27所述的方法，其特征在于，所述方法还包括：
    所述备设备若接收到所述主设备返回的第四响应消息，则等待与所述云端设备完成断链重建，其中，所述第四响应消息用于告知所述主设备与所述云端设备之间未发生断链超时。
  29. 根据权利要求21所述的方法，其特征在于，所述方法还包括：
    所述备设备若确定所述备设备与所述云端设备之间的链路质量低于预设质量阈值、和/或确定所述主设备与所述云端设备之间的链路质量低于预设质量阈值，则启动所述主设备与所述备设备之间的本地备份机制，以便所述主设备在所述本地备份机制被启动后确定所述云端设备的通信状态异常。
  30. 根据权利要求20至29任一项所述的方法，其特征在于，所述方法还包括：
    所述备设备在确定所述备设备与所述云端设备之间能够正常通信且所述备设备与所述主设备之间不能正常通信的情况下，则所述备设备的所述备设备身份切换为主设备身份。
  31. 根据权利要求30所述的方法，其特征在于，所述备设备与所述主设备不能正常通信，包括：
    所述备设备与所述主设备之间发生断链超时，或者，所述备设备与所述主设备之间的链路质量低于预设质量阈值。
  32. 一种主设备，其特征在于，所述主设备包括：
    通知发送模块，用于向云端设备发送第一身份通知，所述第一身份通知为主设备具有主设备身份的通知；
    状态确定模块，用于确定所述云端设备的通信状态；
    云端备份模块，用于在确定所述云端设备的通信状态正常的情况下，将获取的第一用户信息上传至所述云端设备；
    其中，所述第一用户信息由所述云端设备存储并提供给备设备，且所述第一用户信息是在所述云端设备的通信状态正常的情况下从所述主设备上线的用户设备的待备份信息。
  33. 根据权利要求32所述的主设备，其特征在于，所述主设备还包括：
    本地备份模块，用于在确定所述云端设备的通信状态异常，且所述主设备与所述备设备之间能够正常通信的情况下，将获取的第二用户信息发送至所述备设备进行备份；其中，所述第二用户信息是在所述云端设备的通信状态异常的情况下从所述主设备上线的用户设备的待备份信息。
  34. 根据权利要求33所述的主设备，其特征在于，所述状态确定模块包括：
    询问发送子模块，用于在检测到与所述云端设备之间发生断链超时后，向所述备设备发送第一询问消息，其中，所述第一询问消息用于询问所述备设备与所述云端设备之间是否发生断链超时；
    第一确定子模块，用于根据从所述备设备接收到的响应消息确定所述云端设备的通信状态。
  35. 根据权利要求34所述的主设备，其特征在于，所述第一确定子模块，具体用于若接收到所述备设备返回的第一响应消息，则确定所述云端设备的通信状态异常，其中所述第一响应消息用于告知所述备设备与所述云端设备之间发生断链超时；
    所述本地备份模块，还用于在将获取的第二用户信息发送至所述备设备进行备份之前，启动所述主设备与所述备设备之间的本地备份机制。
  36. 根据权利要求34所述的主设备，其特征在于，所述第一确定子模块，具体用于若接收到所述备设备返回的第二响应消息，则确定所述云端设备的通信状态正常；其中所述第二响应消息用于告知所述备设备与所述云端设备之间未发生断链超时；
    所述主设备还包括：
    第一断链重建模块，用于与所述云端设备之间进行断链重建；
    第一批量备份模块，用于在所述断链重建成功后，将获取的第三用户信息批量发送至所述云端设备，其中，所述第三用户信息由所述云端设备存储并提供给所述备设备，且所述第三用户信息是在所述主设备与所述云端设备发生断链后且在所述断链重建成功之前从所述主设备上线的用户设备的待备份信息。
  37. 根据权利要求33所述的主设备，其特征在于，所述状态确定模块包括：
    通知接收子模块，用于接收所述备设备发送的第一通知消息，其中，所述第一通知消息用于告知所述备设备与所述云端设备之间发生断链超时；
    第二确定子模块，用于在接收到所述第一通知消息后，根据所述主设备与所述云端设备的链接情况确定所述云端设备的通信状态。
  38. 根据权利要求37所述的主设备，其特征在于，所述第二确定子模块，具体用于若确定所述主设备与所述云端设备之间发生断链超时，则确定所述云端设备的通信状态异常；
    所述本地备份模块，还用于在将获取的第二用户信息发送至所述备设备进行备份之前，启动所述主设备与所述备设备之间的本地备份机制。
  39. 根据权利要求37所述的主设备，其特征在于，所述第二确定子模块，具体用于若确定与所述云端设备之间未发生断链超时，则确定所述云端设备的通信状态正常；
    所述主设备还包括：
    重建通知模块，用于通知所述备设备等待与所述云端设备之间完成断链重建。
  40. 根据权利要求33所述的主设备，其特征在于，所述状态确定模块，具体用于若确定所述主设备与所述云端设备之间的链路质量低于预设质量阈值、和/或确定所述备设备与所述云端设备之间的链路质量低于预设质量阈值，则确定所述云端设备的通信状态异常。
  41. 根据权利要求32至40任一项所述的主设备，其特征在于，所述主设备还包括：
    身份切换模块，用于在确定所述主设备与所述云端设备之间不能正常通信、且所述主设备与所述备设备之间不能正常通信的情况下，则所述主设备的所述主设备身份切换为备设备身份。
  42. 一种云端设备，其特征在于，所述云端设备包括：
    通知接收模块，用于接收主设备发送的第一身份通知以及备设备发送的第二身份通 知，所述第一身份通知为所述主设备具有主设备身份的通知，所述第二身份通知为所述备设备具有备设备身份的通知；
    云端备份模块，用于接收并存储所述主设备上传的第一用户信息，并将所述第一用户信息提供给所述备设备；
    其中，所述第一用户信息是所述主设备确定所述云端设备的通信状态正常的情况下上传的，且所述第一用户信息是当所述云端设备的通信状态正常的情况下从所述主设备上线的用户设备的待备份信息。
  43. 一种备设备，其特征在于，所述备设备包括：
    通知发送模块，用于向云端设备发送第二身份通知，所述第二身份通知为所述备设备具有备设备身份的通知；
    云端备份模块，用于从所述云端设备获取第一用户信息进行备份；
    其中，所述第一用户信息是所述主设备确定所述云端设备的通信状态正常的情况下上传至所述云端设备存储的，且所述第一用户信息是当所述云端设备的通信状态正常的情况下从所述主设备上线的用户设备的待备份信息。
  44. 根据权利要求43所述的备设备，其特征在于，所述备设备还包括：
    本地备份模块，用于在所述云端设备的通信状态异常的情况下，接收所述主设备发送的第二用户信息进行备份；
    其中，所述第二用户信息是在所述云端设备的通信状态异常的情况下从所述主设备上线的用户设备的待备份信息；所述第二用户信息是所述主设备在确定所述云端设备的通信状态异常且所述主设备与所述备设备之间能够正常通信的情况下发送的。
  45. 根据权利要求44所述的备设备，其特征在于，所述备设备还包括：
    消息返回模块，用于若接收到所述主设备发送的第一询问消息，则向所述主设备返回响应消息；
    其中，所述第一询问消息是所述主设备在检测到与所述云端设备之间发生断链超时后发送的，且所述第一询问消息用于询问所述备设备与所述云端设备之间是否发生断链超时；所述备设备返回的响应消息用于使所述主设备确定所述云端设备的通信状态。
  46. 根据权利要求45所述的备设备，其特征在于，所述消息返回模块，具体用于向所述主设备返回第一响应消息；
    其中，所述第一响应消息用于告知所述备设备与所述云端设备之间发生断链超时，以使得所述主设备在所述备设备与所述云端设备之间发生断链超时后确定所述云端设备的通信状态异常，并在确定所述云端设备的通信状态异常之后启动所述主设备与所述备设备之间的本地备份机制；
    所述本地备份模块，具体用于接收所述主设备启动所述本地备份机制后发送的第二用户信息进行备份。
  47. 根据权利要求45所述的备设备，其特征在于，所述消息返回模块，具体用于向所述主设备返回第二响应消息；
    其中，所述第二响应消息用于告知所述备设备与所述云端设备之间未发生断链超时，以使得所述主设备在所述备设备与所述云端设备之间未发生断链超时后确定所述云端设 备的通信状态正常，并在确定所述云端设备的通信状态正常之后使所述主设备与所述云端设备之间进行断链重建，以及使所述主设备在所述断链重建成功后将获取的第三用户信息批量发送至所述云端设备；
    其中，所述第三用户信息由所述云端设备存储并提供给所述备设备，且所述第三用户信息是在所述主设备与所述云端设备发生断链后且在所述断链重建成功之前从所述主设备上线的用户设备的待备份信息。
  48. 根据权利要求44所述的备设备，其特征在于，所述备设备还包括：
    通知发送模块，用于向所述主设备发送第一通知消息；
    其中，所述第一通知消息用于告知所述备设备与所述云端设备之间发生断链超时，以使得所述主设备在所述主设备与所述云端设备之间发生断链超时后确定所述云端设备的通信状态异常。
  49. 根据权利要求48所述的备设备，其特征在于，所述备设备还包括：
    通知接收模块，用于接收所述主设备发送的重建等待通知；
    其中，所述重建等待通知用于通知所述备设备等待与所述云端设备之间完成断链重建，所述重建等待通知是所述主设备确定所述云端设备的通信状态正常后发送的，所述通信状态正常是所述主设备确定与所述云端设备之间未发生断链超时后确定的。
  50. 根据权利要求43至49任一项所述的备设备，其特征在于，所述备设备还包括：
    身份切换模块，用于在确定所述备设备与所述云端设备之间能够正常通信且所述备设备与所述主设备之间不能正常通信的情况下，则所述备设备的所述备设备身份切换为主设备身份。
  51. 一种主设备，其特征在于，所述主设备包括：处理器，存储器，通信接口和总线；所述处理器、通信接口、存储器通过所述总线相互的通信；
    所述通信接口，用于接收和发送数据；
    所述存储器用于存储指令；
    所述处理器用于执行所述存储器中的所述指令，执行如权利要求1至18中任一项所述的方法。
  52. 一种云端设备，其特征在于，所述云端设备包括：处理器，存储器，通信接口和总线；所述处理器、通信接口、存储器通过所述总线相互的通信；
    所述通信接口，用于接收和发送数据；
    所述存储器用于存储指令；
    所述处理器用于执行所述存储器中的所述指令，执行如权利要求19所述的方法。
  53. 一种备设备，其特征在于，所述主设备包括：处理器，存储器，通信接口和总线；所述处理器、通信接口、存储器通过所述总线相互的通信；
    所述通信接口，用于接收和发送数据；
    所述存储器用于存储指令；
    所述处理器用于执行所述存储器中的所述指令，执行如权利要求20至31中任一项所述的方法。
  54. 一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行 如权利要求1-18中任意一项所述的方法，或者执行如权利要求19所述的方法，或者执行如权利要求20-31中任意一项所述的方法。
  55. 一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行如权利要求1-18中任意一项所述的方法，或者执行如权利要求19所述的方法，或者执行如权利要求20-31中任意一项所述的方法。
PCT/CN2019/079782 2018-03-29 2019-03-27 一种信息备份方法及相关设备 WO2019184923A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP19774599.5A EP3764619B1 (en) 2018-03-29 2019-03-27 Information backup method and related device
US17/036,705 US11989100B2 (en) 2018-03-29 2020-09-29 Information backup method and related device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810273786.2 2018-03-29
CN201810273786.2A CN110324375B (zh) 2018-03-29 2018-03-29 一种信息备份方法及相关设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/036,705 Continuation US11989100B2 (en) 2018-03-29 2020-09-29 Information backup method and related device

Publications (1)

Publication Number Publication Date
WO2019184923A1 true WO2019184923A1 (zh) 2019-10-03

Family

ID=68062561

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/079782 WO2019184923A1 (zh) 2018-03-29 2019-03-27 一种信息备份方法及相关设备

Country Status (4)

Country Link
US (1) US11989100B2 (zh)
EP (1) EP3764619B1 (zh)
CN (1) CN110324375B (zh)
WO (1) WO2019184923A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11159608B2 (en) * 2017-03-06 2021-10-26 Telefonaktiebolaget Lm Ericsson (Publ) Method and control node for managing cloud resources in a communications network
TWI743548B (zh) * 2018-08-31 2021-10-21 財團法人工業技術研究院 用於使用者設備和遠程接入節點的連接重定向方法以及使用所述方法的使用者設備
CN114764377A (zh) * 2020-12-30 2022-07-19 花瓣云科技有限公司 一种数据备份方法、电子设备、数据备份系统及芯片系统
CN114828053A (zh) * 2021-01-28 2022-07-29 华为技术有限公司 通话控制器部署的方法及设备
CN115248746A (zh) * 2021-04-26 2022-10-28 华为云计算技术有限公司 数据备份方法、系统及相关设备
CN115277727B (zh) * 2022-06-30 2024-03-19 达闼机器人股份有限公司 一种数据灾备方法、系统、装置及存储介质
CN117294578B (zh) * 2023-11-24 2024-03-05 深圳市蓝晨科技股份有限公司 一种通信方法、系统、计算机设备和存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102983997A (zh) * 2012-11-21 2013-03-20 中兴通讯股份有限公司 主控服务迁移方法及装置
CN103226483A (zh) * 2013-03-25 2013-07-31 成都瑞科电气有限公司 基于soa、云存储实现的双机热备份系统及其方法
US20150156118A1 (en) * 2013-05-08 2015-06-04 Connectloud, Inc. Method and Apparatus for Dynamic and Distributed Tunnel Routinge
CN106453120A (zh) * 2015-08-05 2017-02-22 北京网御星云信息技术有限公司 一种动态集群方法和系统

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5684984A (en) * 1994-09-29 1997-11-04 Apple Computer, Inc. Synchronization and replication of object databases
US5625818A (en) * 1994-09-30 1997-04-29 Apple Computer, Inc. System for managing local database updates published to different online information services in different formats from a central platform
US5819020A (en) * 1995-10-16 1998-10-06 Network Specialists, Inc. Real time backup system
US7657769B2 (en) * 2007-01-08 2010-02-02 Marcy M Scott N-way synchronization of data
US8421614B2 (en) * 2007-09-19 2013-04-16 International Business Machines Corporation Reliable redundant data communication through alternating current power distribution system
CN101651553B (zh) * 2009-09-03 2013-02-27 华为技术有限公司 用户侧组播业务主备保护系统、方法及路由设备
TWI442087B (zh) * 2010-10-27 2014-06-21 Ind Tech Res Inst 電濕潤顯示裝置及其非極性彩色溶液
CN202309769U (zh) * 2011-10-19 2012-07-04 王吉霞 一种基于云计算的数据存储系统
US8972542B2 (en) * 2011-12-22 2015-03-03 International Business Machines Corporation Extending a DHCP relay to backup a DHCP server
US8996467B2 (en) * 2011-12-29 2015-03-31 Druva Inc. Distributed scalable deduplicated data backup system
US8635373B1 (en) * 2012-09-22 2014-01-21 Nest Labs, Inc. Subscription-Notification mechanisms for synchronization of distributed states
US9776078B2 (en) * 2012-10-02 2017-10-03 Razer (Asia-Pacific) Pte. Ltd. Application state backup and restoration across multiple devices
US9847918B2 (en) * 2014-08-12 2017-12-19 Microsoft Technology Licensing, Llc Distributed workload reassignment following communication failure
CN107222327A (zh) * 2016-03-22 2017-09-29 中兴通讯股份有限公司 一种基于云平台管理服务器的方法及装置
US10031821B2 (en) * 2016-09-26 2018-07-24 James Nelson Distributed network electronic interference abatement system and method
CN107038096B (zh) * 2016-12-30 2018-01-19 平安科技（深圳）有限公司 虚拟磁盘备份系统、方法和装置
CN109936545B (zh) * 2017-12-18 2020-07-24 华为技术有限公司 暴力破解攻击的检测方法和相关装置
FR3076004B1 (fr) * 2017-12-27 2021-03-19 Bull Sas Procede de gestion de panne dans un reseau de noeuds et partie de reseau de noeuds associee
FR3082974B1 (fr) * 2018-06-22 2020-06-05 Bull Sas Procede de gestion de panne dans un reseau de nœuds base sur une strategie globale
US11640340B2 (en) * 2020-10-20 2023-05-02 Nutanix, Inc. System and method for backing up highly available source databases in a hyperconverged system
US11709741B1 (en) * 2021-03-29 2023-07-25 Amazon Technologies, Inc. Systems and methods for enabling a failover service for block-storage volumes

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102983997A (zh) * 2012-11-21 2013-03-20 中兴通讯股份有限公司 主控服务迁移方法及装置
CN103226483A (zh) * 2013-03-25 2013-07-31 成都瑞科电气有限公司 基于soa、云存储实现的双机热备份系统及其方法
US20150156118A1 (en) * 2013-05-08 2015-06-04 Connectloud, Inc. Method and Apparatus for Dynamic and Distributed Tunnel Routinge
CN106453120A (zh) * 2015-08-05 2017-02-22 北京网御星云信息技术有限公司 一种动态集群方法和系统

Also Published As

Publication number Publication date
EP3764619A4 (en) 2021-04-21
EP3764619A1 (en) 2021-01-13
US11989100B2 (en) 2024-05-21
CN110324375A (zh) 2019-10-11
US20210011813A1 (en) 2021-01-14
CN110324375B (zh) 2020-12-04
EP3764619B1 (en) 2023-10-25

Similar Documents

Publication Publication Date Title
WO2019184923A1 (zh) 一种信息备份方法及相关设备
EP2985952B1 (en) Method and device for protecting service reliability, and network virtualization system
EP3525405A1 (en) Packet sending method and network device
JP5913635B2 (ja) 冗長ネットワーク接続
Song et al. Control path management framework for enhancing software-defined network (SDN) reliability
US8509059B2 (en) Method for operating a virtual router redundancy protocol router and communication system therefor
WO2015101168A1 (zh) 故障恢复的方法及控制器
US10164824B2 (en) Indicating a master network controller in a virtual router redundancy protocol
TW201421232A (zh) 在一冗餘群組中實施故障備援的方法、裝置與電腦程式產品
WO2013113228A1 (zh) 网络设备冗余备份的方法、路由设备及系统
WO2021185169A1 (zh) 一种切换方法、装置、设备和存储介质
JP2021529454A (ja) ループ回避通信方法、ループ回避通信デバイスおよびループ回避通信システム
EP3038296B1 (en) Pool element status information synchronization method, pool register and pool element
US20170359253A1 (en) Link Protection Method In SDN, Switching Device, and Network Controller
US20220294728A1 (en) Packet Transmission Path Switching Method, Device, and System
WO2011113395A2 (zh) 一种负载分担方法和装置
JP2015002482A (ja) ネットワークシステム及び制御方法
WO2013007124A1 (zh) 虚拟路由冗余协议通告链路保护方法及系统
CN111447130B (zh) 一种连通性检测会话的创建方法、网络设备和系统
WO2011143888A1 (zh) 一种对协议状态的设备间备份的方法及系统
CN109995541B (zh) 一种组播数据发送方法及节点设备
EP3627766B1 (en) Method and system for switching between active bng and standby bng
KR102376484B1 (ko) 이중화 회선 자동 절체를 위한 장치 및 방법
CN115701031A (zh) 一种业务处理方法和相关装置
WO2021082820A1 (zh) 双归接入时选择切换为工作状态的端口的方法和设备

Legal Events

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

Ref document number: 19774599

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019774599

Country of ref document: EP

Effective date: 20201007