CN112104531B - Backup implementation method and device - Google Patents

Backup implementation method and device Download PDF

Info

Publication number
CN112104531B
CN112104531B CN202010864286.3A CN202010864286A CN112104531B CN 112104531 B CN112104531 B CN 112104531B CN 202010864286 A CN202010864286 A CN 202010864286A CN 112104531 B CN112104531 B CN 112104531B
Authority
CN
China
Prior art keywords
sharing
message
equipment
reply
devices
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202010864286.3A
Other languages
Chinese (zh)
Other versions
CN112104531A (en
Inventor
宛清
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
New H3C Technologies Co Ltd
Original Assignee
New H3C Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by New H3C Technologies Co Ltd filed Critical New H3C Technologies Co Ltd
Priority to CN202010864286.3A priority Critical patent/CN112104531B/en
Publication of CN112104531A publication Critical patent/CN112104531A/en
Application granted granted Critical
Publication of CN112104531B publication Critical patent/CN112104531B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854—Wide area networks, e.g. public data networks
    • H04L12/2856—Access arrangements, e.g. Internet access
    • H04L12/2869—Operational details of access network equipments
    • H04L12/287—Remote access server, e.g. BRAS
    • 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
    • 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

Abstract

The application provides a backup implementation method and a device, wherein the method comprises the following steps: sending a sharing request message; when sharing-allowed reply messages sent by a plurality of second CP devices are received, acquiring a first sharing-allowed reply message corresponding to first receiving time and a second sharing-allowed reply message corresponding to second receiving time from the plurality of sharing-allowed reply messages; sending a sharing reconfirmation message to third CP equipment which sends the first sharing reply message and the second sharing reply message; and when a sharing confirmed message sent by the third CP equipment is received and the sharing confirmed message indicates that the third CP equipment can be used as target equipment for cross storage, synchronizing data to the third CP equipment so that the third CP equipment stores the synchronous data.

Description

Backup implementation method and device
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for implementing backup.
Background
In order to solve the problems of low equipment resource utilization rate, complex operation and maintenance, slow opening of new services and the like in the conventional BRAS, a vBRAS system architecture with separated forwarding and control is proposed in the industry. As shown in fig. 1, fig. 1 is a diagram of a networking scenario applying vbars transfer control separation.
In fig. 1, an uplink traffic (e.g., a User presence message) sent by a User terminal reaches a User Plane (UP) device, and then reaches a vbars device through a Core Router (CR). The vbrs device takes on the functions of a Control Plane (CP) device, and the following description refers to the CP device as the vbrs device.
After the CP equipment receives the user on-line message, the CP equipment generates a user authentication message according to the user on-line message and the configuration of the CP equipment. And the CP sends a user authentication message to the AAA server and performs user authentication. If AAA server passes the user authentication, CP device sends the pass information to UP device. Therefore, when the data message subsequently sent by the user reaches the UP device, the UP device can directly forward the data message, and meanwhile, the UP device updates the charging information. The UP device informs the CP device to update the charging information, and the CP device informs the AAA server to update the charging information.
In the foregoing case, the CP device usually stores user information generated after the user terminal is online, or called operation data. Such as the specific time the user was on-line, the location the user was on-line, etc. When the CP equipment is abnormal and is restarted, the user information is lost, and the user information needs to be recovered after the CP equipment is restarted. At this time, other devices are required to store the aforementioned user information.
In response to the foregoing requirement, in an implementation manner, the CP device may store the user information in a separate server, and when the CP device needs to recover the user information, the CP device obtains the user information from the server; in another implementation, by configuring a corresponding backup CP device for each CP device, if the main CP device needs to restore the user information, the user information is acquired from the backup CP device.
However, the two aforementioned implementations also suffer from the following drawbacks: 1) in the first implementation mode, one or more servers need to be additionally deployed, so that resources are wasted and cost is increased; 2) in the second implementation manner, each CP device needs to configure one backup CP device, that is, when N CP devices are deployed, N backup CP devices need to be deployed, which also results in high cost.
Disclosure of Invention
In view of this, the present application provides a backup implementation method and device, so as to solve the problems of resource waste and cost increase caused by additionally deploying one or more servers or configuring one backup CP device for each CP device to store user information in the prior art.
In a first aspect, the present application provides a backup implementation method, where the method is applied to a first CP device, and the method includes:
sending a sharing request message, wherein the sharing request message comprises the size of a storage space required by the first CP equipment for storing user information;
when receiving a sharing permission reply message sent by a plurality of second CP devices according to the size of the storage space, acquiring a first sharing permission reply message corresponding to first receiving time and a second sharing permission reply message corresponding to second receiving time from the sharing permission reply messages;
sending a sharing reconfirmation message to third CP equipment which sends the first sharing replying message and the second sharing replying message, wherein the sharing reconfirmation message is used for enabling the third CP equipment to determine that the first CP equipment selects the third CP equipment as a target equipment of cross storage;
and when a sharing confirmed message sent by the third CP equipment is received and the sharing confirmed message indicates that the third CP equipment can be used as target equipment for cross storage, synchronizing data to the third CP equipment so that the third CP equipment stores the synchronous data.
In a second aspect, the present application provides a backup implementation apparatus, where the apparatus is applied to a first CP device, and the apparatus includes:
a sending unit, configured to send a sharing request packet, where the sharing request packet includes a size of a storage space required by the first CP device for storing user information;
a receiving unit, configured to receive a reply message allowing sharing sent by multiple second CP devices;
an obtaining unit, configured to obtain, from the multiple reply messages allowing sharing, a first reply message allowing sharing corresponding to a first receiving time and a second reply message allowing sharing corresponding to a second receiving time when the receiving unit receives the reply messages allowing sharing sent by the multiple second CP devices according to the size of the storage space;
the sending unit is further configured to send a sharing reconfirmation message to a third CP device that sends the first sharing permission reply message and the second sharing permission reply message, where the sharing reconfirmation message is used to enable the third CP device to determine that the first CP device selects the third CP device as a cross-type stored target device;
the receiving unit is further configured to receive a shared acknowledgment packet sent by the third CP device;
the sending unit is further configured to synchronize data with the third CP device when the receiving unit receives a sharing confirmed message sent by the third CP device and the sharing confirmed message indicates that the third CP device can serve as a target device for cross storage, so that the third CP device stores the synchronized data.
Therefore, by applying the backup implementation method and apparatus provided by the present application, the first CP device sends the sharing request message. When receiving the sharing permission reply messages sent by the second CP devices, the first CP device obtains a first sharing permission reply message corresponding to the first receiving time and a second sharing permission reply message corresponding to the second receiving time from the sharing permission reply messages. And the first CP equipment sends a sharing reconfirmation message to third CP equipment which sends the first sharing permission reply message and the second sharing permission reply message. And when the sharing confirmed message sent by the third CP equipment is received and the sharing confirmed message indicates that the third CP equipment can be used as target equipment for cross storage, the first CP equipment synchronizes data to the third CP equipment so that the third CP equipment stores the synchronized data.
The user information stored in the first CP device is synchronized to other CP devices to realize cross storage, so that the problems of resource waste and cost increase caused by additionally deploying one or more servers or correspondingly configuring one backup CP device for each CP device to store the user information in the prior art are solved.
Drawings
Fig. 1 is a network scenario diagram applying vbars transfer control separation;
fig. 2 is a flowchart of a backup implementation method provided in an embodiment of the present application;
fig. 3 is a structural diagram of a backup implementation apparatus provided in the embodiment of the present application;
fig. 4 is a hardware structure diagram of a network device according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the corresponding listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
The following describes in detail a backup implementation method provided in an embodiment of the present application. Referring to fig. 2, fig. 2 is a flowchart of a backup implementation method provided in the embodiment of the present application. The method is applied to the first CP device, and the backup implementation method provided in the embodiment of the present application may include the following steps.
Step 210, sending a sharing request message, where the sharing request message includes a size of a storage space required by the first CP device for storing user information.
Specifically, the first CP device is within a CP device group, in which a plurality of CP devices are included. After the first CP device is powered on and started, the first CP device determines whether to store a device list locally, where the device list is used to store the identifiers of the plurality of second CP devices. The second CP device corresponding to the identifier of each second CP device may serve as a target device of the cross-store of the first CP device.
If the first CP device does not store the device list locally, the first CP device generates a sharing request message, wherein the sharing request message comprises the size of a storage space required by the first CP device for storing the user information. And the first CP equipment broadcasts and sends a sharing request message in the CP equipment group.
In this embodiment, the destination MAC of the sharing request message is the broadcast address of the full F. The specific format of the sharing request message is described in detail later.
If the device list is stored locally, the first CP device acquires address information of a plurality of fourth CP devices in the device list. And according to the address information of the plurality of fourth CP devices, the first CP device generates a plurality of first detection request messages. And the first CP equipment sends a first detection request message to each fourth CP equipment. If the fourth CP device receives the first detection request message, the fourth CP device generates a first detection reply message. And the fourth CP equipment sends the first detection reply message to the first CP equipment.
If the first CP device receives the first probe reply message sent by the fourth CP device within a preset time (e.g., within 1 second), the first CP device determines that the fourth CP device can continue to be the target device of the cross storage. If the first CP device does not receive the first probe reply message sent by the fourth CP device within a preset time (for example, within 1 second), the first CP device deletes the address information of the fourth CP device from the device list.
In this embodiment of the present application, the first probe request message and the first probe reply message are messages for checking whether the fourth CP device is connected normally. The first CP device may send 3 first probe request messages every 1 second and wait for a reply from the fourth CP device. If a reply of the fourth CP device is received within 1 second after 1 first probe request message is sent (that is, in the process of sending 3 first probe request messages, after 1 first probe request message is sent, a corresponding first probe reply message is received), the first CP device determines that the fourth CP device is normally connected. It can be understood that the period for the first CP device to send the first probe request message is not limited to 1 second, and in practical applications, the period may be set according to the current situation.
In the embodiment of the present application, specific formats of the first detection request message and the first detection reply message are described in detail in the following.
Step 220, when receiving the reply messages allowing sharing sent by the second CP devices according to the size of the storage space, obtaining a first reply message allowing sharing corresponding to the first receiving time and a second reply message allowing sharing corresponding to the second receiving time from the reply messages allowing sharing.
Specifically, after receiving the sharing request message, the second CP devices obtain, from the sharing request message, the size of the storage space required by the first CP device for storing the user information.
Each second CP device checks whether it has a backup storage space matching the size of the storage space according to the size of the storage space, that is, each second CP device checks whether it has a redundant storage space, so as to store the user information for the first CP device.
And if each second CP device has a backup storage space with the size matched with that of the storage space, each second CP device respectively generates a reply message allowing sharing. And if the second CP equipment does not have the backup storage space with the size matched with the storage space, the second CP equipment discards the sharing request message.
And the plurality of second CP devices send the message allowing the sharing reply to the first CP device.
After receiving the multiple reply messages allowing sharing, the first CP device obtains a first reply message allowing sharing corresponding to the first receiving time and a second reply message allowing sharing corresponding to the second receiving time from the multiple reply messages allowing sharing.
Further, in an example, when the first CP device receives multiple reply messages allowing sharing, the receiving time of each reply message allowing sharing is recorded, and the receiving times are sorted. For example, the reception times are sorted from small to large, with the first-ranked received first and the last-ranked received last. The first CP equipment acquires a first sharing reply message corresponding to first receiving time arranged at the first position, and also acquires a second sharing reply message corresponding to second receiving time arranged at the second first position. And for the allowed sharing reply message corresponding to the receiving time arranged after the first bit, the first CP equipment directly discards the message.
In this embodiment of the application, if the second CP device that sends the first and second allowed shared reply messages determines in the subsequent steps that it cannot serve as the target device for cross storage, that is, cannot store the user information for the first device, at this time, the first CP device may further sequentially select the allowed shared reply messages for the receiving times arranged in the third and fourth bits according to the sorting result of the receiving times, and execute the subsequent steps.
In another example, after receiving the two sharing permission reply messages, the first CP device does not receive any other sharing permission reply message, that is, discards the other sharing permission reply message.
In the embodiment of the present application, the specific format of the reply message allowed to be shared will be described in detail later.
Step 230, sending a sharing reconfirmation message to a third CP device that sends the first sharing reconfirmation message and the second sharing reconfirmation message, where the sharing reconfirmation message is used for enabling the third CP device to determine that the first CP device selects the third CP device as a target device of cross storage.
Specifically, after acquiring the first sharing permission reply message and the second sharing permission reply message, the first CP device determines the CP devices that send the two sharing permission reply messages, respectively. E.g., a third CP device.
The first CP device generates two sharing reconfirmation messages respectively and sends the sharing reconfirmation messages to the two third CP devices respectively. The shared reconfirmation message is used for enabling each third CP device to determine that the first CP device selects itself as the target device in the cross storage.
It should be noted that, the number of the target devices may be previously issued to the first CP device by the administrator through a configuration command. For example, when the number of the target devices is two, the first CP device obtains two reply messages allowing sharing in step 220, and generates two sharing reconfirmation messages in step 230. When the number of the target devices is three, the first CP device obtains three reply messages allowing sharing in step 220, and generates three sharing reconfirmation messages in step 230.
In the embodiment of the present application, the specific format of the shared reconfirmation message is described in detail later.
Step 240, when receiving a sharing confirmed message sent by the third CP device and the sharing confirmed message indicates that the third CP device can be used as a target device for cross storage, synchronizing data to the third CP device, so that the third CP device stores the synchronized data.
Specifically, after each third CP device receives the shared reconfirmation message, each third CP device reconfirmations whether itself can serve as the target device of the first CP device in the cross storage.
Further, the third CP may check again whether it has a backup storage space matching the size of the storage space, and whether it is already a target device of the cross storage of other CP devices.
In one implementation, if the third CP device has a backup storage space with a matching storage space size and does not serve as a target device for cross storage of other CP devices, the third CP device generates a shared confirmation message, and the shared confirmation message indicates that the third CP device can serve as the target device for cross storage. And after the third CP equipment generates a sharing confirmed message, locally recording the third CP equipment as the target equipment of the first CP equipment in the cross storage mode.
The third CP device sends a sharing confirmed message to the first CP device. And the first CP equipment determines that the third CP equipment can be used as target equipment of cross storage according to the shared confirmed message, and the first CP equipment synchronizes data to the third CP equipment.
After the third CP device receives the synchronization data, the third CP device stores the synchronization data.
Further, before the first CP device synchronizes data to the third CP device, the first CP device further records the address information of the third CP device in the local device list.
In another implementation, if the third CP device has already been used as a target device for cross storage of other CP devices; or, if the third CP device does not currently have a backup storage space with a matching storage space size, the third CP device also generates a shared confirmation message, and the shared confirmation message indicates that the third CP device cannot be used as a target device for cross storage.
The third CP device sends a sharing confirmed message to the first CP device. And the first CP equipment determines that the third CP equipment can not be used as target equipment for cross storage according to the shared confirmed message, and judges whether the number of the target equipment reaches a preset value or not. If the number of the target devices does not reach the preset value, the first CP device repeats step 210-step 240 again until the first CP device receives a sharing confirmed message indicating that the third CP device may serve as the target device stored in the cross-type manner, and the first CP device determines that the number of the current target devices reaches the preset value.
In the embodiment of the present application, the specific format of the shared acknowledged message is described in detail in the following.
Therefore, by applying the backup implementation method provided by the present application, the first CP device sends the sharing request packet. When receiving the sharing permission reply messages sent by the second CP devices, the first CP device obtains a first sharing permission reply message corresponding to the first receiving time and a second sharing permission reply message corresponding to the second receiving time from the sharing permission reply messages. And the first CP equipment sends a sharing reconfirmation message to third CP equipment which sends the first sharing permission reply message and the second sharing permission reply message. And when the sharing confirmed message sent by the third CP equipment is received and the sharing confirmed message indicates that the third CP equipment can be used as target equipment for cross storage, the first CP equipment synchronizes data to the third CP equipment so that the third CP equipment stores the synchronized data.
The user information stored in the first CP device is synchronized to other CP devices to realize cross storage, so that the problems of resource waste and cost increase caused by additionally deploying one or more servers or correspondingly configuring one backup CP device for each CP device to store the user information in the prior art are solved.
Optionally, in this embodiment of the present application, the controller controls the CP device group. After the CP devices included in the CP device group determine the target devices of the respective cross storage according to the foregoing steps 210 to 240, the CP devices synchronize the user information to the corresponding target devices.
When the controller senses that a certain CP device (e.g., CP1) in the CP device group fails, the controller selects a CP device from the CP device group to replace CP 1. The controller acquires the correspondence of each CP device as a target device stored in a crossbar. From the correspondence, the controller determines a CP device, for example, CP2, which stores user information of CP 1. The controller notifies the CP2 to perform the function of the CP1 instead. Therefore, when a certain CP device in the CP device group fails, the controller can quickly select a substitute CP device, and the failure time is shortened.
When the controller senses that the CP1 has failed back, the controller notifies the CP1 that its functionality is also replaced by the CP 2. The CP1 sends a synchronization request to the CP2 to synchronize the user information in the CP1 that the CP2 previously stored in the CP 1. CP1 resumes traffic functions. CP1 again performs the foregoing steps 210-250, determines the target devices that can be cross-stored, and synchronizes the user information to the selected target devices. Meanwhile, the CP1 informs the CP2 to delete the previously stored user information.
Further, the controller and each CP device also detect whether the connection is normal through the probe request message and the probe reply message.
Optionally, in this embodiment of the present application, the first CP device periodically checks whether the connection with the third CP device is normal. If the first CP device determines that the connection with the third CP device is abnormal and the number of the current target devices does not reach the preset value, the first CP device performs steps 210 to 240 again. If the first CP device determines that the connection with the third CP device is normal, the first CP device periodically checks the connection with the third CP device.
Specifically, the first CP device generates a plurality of second probe request packets according to the number of current target devices. And the first CP equipment respectively sends second detection request messages to the plurality of third CP equipment.
And after each third CP device receives the second detection request message, each third CP device generates a second detection reply message. And each third CP device sends a second detection reply message to the first CP device.
Further, the first CP device may send 3 second probe request messages to each third CP device every 1 second and wait for a reply from each third CP device. If the first CP device receives the second probe reply message sent by the third CP device within a preset time (e.g., within 1 second) (that is, receives the corresponding second probe reply message within 1 second after sending 1 second probe request message), the first CP device determines that the third CP device is normally connected, and periodically checks the connection with the third CP device in the subsequent process.
If the first CP device does not receive the second probe reply message sent by the third CP device within a preset time (for example, within 1 second) (that is, does not receive the corresponding second probe reply message after sending every 1 second probe request message), the first CP device may repeat the sending for 3 times, and send 3 second probe request messages to the third CP device again at an interval of 1 second each time. If the third CP device does not reply (i.e., the first CP device does not receive the second probe reply message corresponding to each transmitted 1 second probe request message in the process of repeatedly transmitting the second probe request 3 times), the first CP device determines that the third CP device fails. The first CP device performs steps 210 to 240 again.
For the third CP device, if the second probe request packet sent by the first CP device is not received within 1 second, the third CP device retains the data synchronized by the first CP device for 5 minutes. And if the second detection request message sent by the first CP equipment is not received within 5 minutes, the third CP equipment deletes the synchronous data and deletes the record of the target equipment which is used as the first CP equipment in the cross storage.
It is understood that the fact that the third CP device retains the synchronization data is not limited to 5 minutes, and in practical applications, the third CP device can be set according to the current situation, for example, 3 minutes or 8 minutes.
Optionally, the message formats of the aforementioned sharing request message, the allowed sharing reply message, the shared reconfirmation message, the shared confirmed message, the first/second detection request message, and the first/second detection reply message are shown in table 1 below.
Table 1 message format
Figure BDA0002649216820000111
Wherein, the messages may adopt a message format shown in table 1. The message types borne by the driving private heads of all the messages are all shared message types. And determining the specific content of the information sending part according to the current process node.
For example, the CP1 sends a request message to request other CP devices to share the memory, at this time, the destination MAC address of the message is full F, the type of the message carried by the driver private header is a shared message type, and the sending information part is a shared request.
The CP2 replies to the sharing request message, where the destination MAC is the MAC address of CP1, the type of the message carried by the driver private header is the sharing message type, and the sending information part is the permission of sharing reply.
Based on the same inventive concept, the embodiment of the application also provides a backup implementation device corresponding to the backup implementation method. Referring to fig. 3, fig. 3 is a structural diagram of a backup implementation apparatus provided in an embodiment of the present application, where the apparatus is applied to a first CP device, and the apparatus includes:
a sending unit 310, configured to send a sharing request packet, where the sharing request packet includes a size of a storage space required by the first CP device for storing user information;
a receiving unit 320, configured to receive reply messages allowing sharing sent by multiple second CP devices;
an obtaining unit 330, configured to, when the receiving unit receives a sharing permission reply message sent by multiple second CP devices according to the size of the storage space, obtain, from the multiple sharing permission reply messages, a first sharing permission reply message corresponding to the first receiving time and a second sharing permission reply message corresponding to the second receiving time;
the sending unit 310 is further configured to send a shared reconfirmation message to a third CP device that sends the first sharing permission reply message and the second sharing permission reply message, where the shared reconfirmation message is used to enable the third CP device to determine that the first CP device selects the third CP device as a target device stored in a cross;
the receiving unit 320 is further configured to receive a shared acknowledged packet sent by the third CP device;
the sending unit 310 is further configured to, when the receiving unit receives a sharing confirmed message sent by the third CP device and the sharing confirmed message indicates that the third CP device can be used as a target device for cross storage, synchronize data with the third CP device, so that the third CP device stores the synchronized data.
Optionally, the apparatus further comprises: a first judging unit (not shown in the figure) configured to judge whether a device list is locally stored, where the device list is used to store the identifiers of the plurality of second CP devices;
the sending unit 310 is further configured to send the sharing request packet if the device list is not stored locally.
Optionally, the obtaining unit 330 is further configured to, if the device list is stored locally, obtain address information of a plurality of fourth CP devices in the device list;
the sending unit 310 is further configured to send a first probe request packet to each fourth CP device according to address information of multiple fourth CP devices;
the device further comprises: a determining unit (not shown in the figure), configured to determine, if the receiving unit receives the first detection reply packet sent by the fourth CP device within a preset time, that the fourth CP device is a target device in cross storage;
a deleting unit (not shown in the figure), configured to delete the address information of the fourth CP device from the device list if the receiving unit does not receive the first probe reply packet sent by the fourth CP device within a preset time.
Optionally, the apparatus further comprises: a discarding unit (not shown in the figure) configured to discard other allowed sharing reply messages in the multiple allowed sharing reply messages;
the other sharing permission reply messages are sharing permission reply messages except the first sharing permission reply message and the second sharing permission reply message.
Optionally, the apparatus further comprises: a recording unit (not shown in the figure) for recording address information of the third CP device in the device list.
Optionally, the apparatus further comprises: a second determining unit (not shown in the figure), configured to determine whether the number of target devices reaches a preset value when the receiving unit receives a sharing confirmed message sent by the third CP device, where the sharing confirmed message indicates that the third CP device cannot be used as a target device in cross storage;
the sending unit 310 is further configured to send the sharing request message again if the number of the target devices does not reach a preset value.
Therefore, by applying the backup implementation device provided by the application, the device sends the sharing request message. When receiving the reply messages allowing sharing sent by the second CP devices, the apparatus obtains a first reply message allowing sharing corresponding to the first receiving time and a second reply message allowing sharing corresponding to the second receiving time from the multiple reply messages allowing sharing. The device sends a sharing reconfirmation message to third CP equipment which sends the first sharing reply message and the second sharing reply message. When a sharing confirmed message sent by the third CP device is received and the sharing confirmed message indicates that the third CP device can be used as a target device of the cross storage, the device synchronizes data to the third CP device so that the third CP device stores the synchronized data.
The user information stored in the device is synchronized to other CP devices to realize cross-type storage, so that the problems of resource waste and cost increase caused by additionally arranging one or more servers or correspondingly configuring one backup CP device for each CP device to store the user information in the prior art are solved.
Based on the same inventive concept, the embodiment of the present application further provides a network device, as shown in fig. 4, including a processor 410, a transceiver 420, and a machine-readable storage medium 430, where the machine-readable storage medium 430 stores machine-executable instructions capable of being executed by the processor 410, and the processor 410 is caused by the machine-executable instructions to perform the backup implementation method provided by the embodiment of the present application. The backup implementation apparatus shown in fig. 3 can be implemented by using the hardware structure of the network device shown in fig. 4.
The computer-readable storage medium 430 may include a Random Access Memory (RAM) or a Non-volatile Memory (NVM), such as at least one disk Memory. Optionally, the computer-readable storage medium 430 may also be at least one memory device located remotely from the processor 410.
The Processor 410 may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; the Integrated Circuit can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.
In the embodiment of the present application, the processor 410 is caused by machine executable instructions by reading the machine executable instructions stored in the machine readable storage medium 430 to enable the processor 410 itself and the call transceiver 420 to execute the backup implementation method described in the embodiment of the present application.
Additionally, the present application provides a machine-readable storage medium 430, wherein the machine-readable storage medium 430 stores machine executable instructions, which when invoked and executed by the processor 410, cause the processor 410 itself and the invoking transceiver 420 to perform the backup implementation method described in the present application.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
For the embodiment of the backup implementation apparatus and the machine-readable storage medium, since the contents of the related methods are substantially similar to those of the foregoing method embodiments, the description is relatively simple, and for the relevant points, reference may be made to the partial description of the method embodiments.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.

Claims (12)

1. A backup implementation method is applied to a first CP device, and comprises the following steps:
sending a sharing request message, wherein the sharing request message comprises the size of a storage space required by the first CP equipment for storing user information;
when receiving a sharing permission reply message sent by a plurality of second CP devices according to the size of the storage space, acquiring a first sharing permission reply message corresponding to first receiving time and a second sharing permission reply message corresponding to second receiving time from the sharing permission reply messages;
sending a sharing reconfirmation message to third CP equipment which sends the first sharing reconfirmation message and the second sharing reconfirmation message, wherein the sharing reconfirmation message is used for enabling the third CP equipment to determine that the first CP equipment selects the third CP equipment as target equipment of cross storage;
and when a sharing confirmed message sent by the third CP equipment is received and the sharing confirmed message indicates that the third CP equipment can be used as target equipment for cross storage, synchronizing data to the third CP equipment so that the third CP equipment stores the synchronous data.
2. The method of claim 1, wherein prior to sending the sharing request message, the method further comprises:
judging whether a device list is stored locally or not, wherein the device list is used for storing the identifiers of a plurality of second CP devices;
and if the equipment list is not stored locally, sending the sharing request message.
3. The method of claim 2, further comprising:
if the device list is stored locally, address information of a plurality of fourth CP devices in the device list is obtained;
according to the address information of a plurality of fourth CP devices, sending a first detection request message to each fourth CP device;
if a first detection reply message sent by the fourth CP equipment is received within a preset time, determining that the fourth CP equipment is used as target equipment in cross storage;
and if the first detection reply message sent by the fourth CP equipment is not received within the preset time, deleting the address information of the fourth CP equipment from the equipment list.
4. The method according to claim 1, wherein after obtaining a first sharing permission reply message corresponding to a first receiving time and a second sharing permission reply message corresponding to a second receiving time from the plurality of sharing permission reply messages, the method further comprises:
discarding other allowed sharing reply messages in the multiple allowed sharing reply messages;
the other sharing permission reply messages are sharing permission reply messages except the first sharing permission reply message and the second sharing permission reply message.
5. The method of claim 2, wherein prior to synchronizing data to the third CP device, the method further comprises:
and recording the address information of the third CP device in the device list.
6. The method of claim 1, further comprising:
when a sharing confirmed message sent by the third CP device is received and the sharing confirmed message indicates that the third CP device cannot be used as a target device in cross storage, judging whether the number of the target devices reaches a preset value;
and if the number of the target devices does not reach the preset value, the sharing request message is sent again.
7. A backup implementation apparatus, applied to a first CP device, the apparatus comprising:
a sending unit, configured to send a sharing request packet, where the sharing request packet includes a size of a storage space required by the first CP device for storing user information;
a receiving unit, configured to receive a reply message allowing sharing sent by multiple second CP devices;
an obtaining unit, configured to obtain, from the multiple reply messages allowing sharing, a first reply message allowing sharing corresponding to a first receiving time and a second reply message allowing sharing corresponding to a second receiving time when the receiving unit receives the reply messages allowing sharing sent by the multiple second CP devices according to the size of the storage space;
the sending unit is further configured to send a sharing reconfirmation message to a third CP device that sends the first sharing permission reply message and the second sharing permission reply message, where the sharing reconfirmation message is used to enable the third CP device to determine that the first CP device selects the third CP device as a cross-type stored target device;
the receiving unit is further configured to receive a shared acknowledged packet sent by the third CP device;
the sending unit is further configured to synchronize data to the third CP device when the receiving unit receives the shared acknowledged packet sent by the third CP device and the shared acknowledged packet indicates that the third CP device can be used as a target device for cross storage, so that the third CP device stores the synchronized data.
8. The apparatus of claim 7, further comprising: a first judging unit, configured to judge whether a device list is locally stored, where the device list is used to store identifiers of multiple second CP devices;
the sending unit is further configured to send the sharing request packet if the device list is not stored locally.
9. The apparatus of claim 8, wherein the obtaining unit is further configured to,
if the device list is stored locally, address information of a plurality of fourth CP devices in the device list is obtained;
the sending unit is further configured to send a first probe request packet to each fourth CP device according to address information of the plurality of fourth CP devices;
the device further comprises: a determining unit, configured to determine, if the receiving unit receives the first detection reply packet sent by the fourth CP device within a preset time, that the fourth CP device is a target device in cross storage;
a deleting unit, configured to delete the address information of the fourth CP device from the device list if the receiving unit does not receive the first probe reply packet sent by the fourth CP device within a preset time.
10. The apparatus of claim 7, further comprising:
a discarding unit, configured to discard other allowed sharing reply messages in the multiple allowed sharing reply messages;
the other sharing permission reply messages are sharing permission reply messages except the first sharing permission reply message and the second sharing permission reply message.
11. The apparatus of claim 8, further comprising:
a recording unit, configured to record address information of the third CP device in the device list.
12. The apparatus of claim 11, further comprising: a second determining unit, configured to determine whether the number of target devices reaches a preset value when the receiving unit receives a shared acknowledged message sent by the third CP device, where the shared acknowledged message indicates that the third CP device cannot be used as a target device stored in a cross-type manner;
the sending unit is further configured to send the sharing request message again if the number of the target devices does not reach a preset value.
CN202010864286.3A 2020-08-25 2020-08-25 Backup implementation method and device Active CN112104531B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010864286.3A CN112104531B (en) 2020-08-25 2020-08-25 Backup implementation method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010864286.3A CN112104531B (en) 2020-08-25 2020-08-25 Backup implementation method and device

Publications (2)

Publication Number Publication Date
CN112104531A CN112104531A (en) 2020-12-18
CN112104531B true CN112104531B (en) 2022-08-30

Family

ID=73753426

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010864286.3A Active CN112104531B (en) 2020-08-25 2020-08-25 Backup implementation method and device

Country Status (1)

Country Link
CN (1) CN112104531B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114501445B (en) * 2022-01-06 2024-02-09 新华三技术有限公司合肥分公司 Access control method and device

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102025475A (en) * 2009-09-23 2011-04-20 中兴通讯股份有限公司 Address allocation method, apparatus and system in hot backup scene
CN104734952A (en) * 2015-03-09 2015-06-24 杭州华三通信技术有限公司 Data message forwarding method and device
WO2018006684A1 (en) * 2016-07-08 2018-01-11 中兴通讯股份有限公司 Message processing method and device, and router
CN107733728A (en) * 2017-11-30 2018-02-23 新华三技术有限公司 Multi-computer back-up method and apparatus
CN108616431A (en) * 2018-04-20 2018-10-02 新华三技术有限公司 A kind of message processing method, device, equipment and machine readable storage medium
CN108810248A (en) * 2017-04-27 2018-11-13 三星电子株式会社 The method of shared summary image and the electronic equipment for realizing this method

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7356577B2 (en) * 2003-06-12 2008-04-08 Samsung Electronics Co., Ltd. System and method for providing an online software upgrade in load sharing servers
US9112728B2 (en) * 2012-05-31 2015-08-18 Broadcom Corporation Implementing control planes for hybrid networks

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102025475A (en) * 2009-09-23 2011-04-20 中兴通讯股份有限公司 Address allocation method, apparatus and system in hot backup scene
CN104734952A (en) * 2015-03-09 2015-06-24 杭州华三通信技术有限公司 Data message forwarding method and device
WO2018006684A1 (en) * 2016-07-08 2018-01-11 中兴通讯股份有限公司 Message processing method and device, and router
CN108810248A (en) * 2017-04-27 2018-11-13 三星电子株式会社 The method of shared summary image and the electronic equipment for realizing this method
CN107733728A (en) * 2017-11-30 2018-02-23 新华三技术有限公司 Multi-computer back-up method and apparatus
CN108616431A (en) * 2018-04-20 2018-10-02 新华三技术有限公司 A kind of message processing method, device, equipment and machine readable storage medium

Also Published As

Publication number Publication date
CN112104531A (en) 2020-12-18

Similar Documents

Publication Publication Date Title
CN108111432B (en) Message forwarding method and device
US7406037B2 (en) Packet forwarding apparatus with redundant routing module
EP1697843B1 (en) System and method for managing protocol network failures in a cluster system
CN110971698A (en) Data forwarding system, method and device
US10498627B2 (en) Detecting packet forwarding path
CN111259072B (en) Data synchronization method, device, electronic equipment and computer readable storage medium
US20200076724A1 (en) Path management for segment routing based mobile user-plane using seamless bfd
WO2017128901A1 (en) Forwarding control method and device
CN108600069B (en) Link switching method and device
CN112367257B (en) Route notification method and device
CN111225401A (en) Method and related equipment for realizing disaster tolerance
CN112104531B (en) Backup implementation method and device
CN108234358B (en) Multicast message transmission method, device and machine readable storage medium
WO2016085375A1 (en) Methods, routing device and further routing device for managing data frames in switched networks
US8724518B2 (en) Communication system, node, terminal, program and communication method
CN109347746B (en) MAC address learning method and device
US10735248B2 (en) Cloudified N-way routing protection at hyper scale
CN114301842B (en) Route searching method and device, storage medium, processor and network system
CN111385324A (en) Data communication method, device, equipment and storage medium
US9189347B2 (en) High reliability redundant voting system for a signal received by voting processors in a communication system
WO2016177211A1 (en) Address resolution protocol (arp) table entry synchronization method and device
WO2012100711A1 (en) Method, device, computer program, and storage medium for protecting signaling route at application layer
CN115277379B (en) Distributed lock disaster recovery processing method and device, electronic equipment and storage medium
CN113821334A (en) Method, device and system for configuring edge side equipment
CN114430310A (en) Information processing method and device, broadband access server and storage medium

Legal Events

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