WO2021244500A1 - 一种备份状态确定方法、装置及系统 - Google Patents

一种备份状态确定方法、装置及系统 Download PDF

Info

Publication number
WO2021244500A1
WO2021244500A1 PCT/CN2021/097531 CN2021097531W WO2021244500A1 WO 2021244500 A1 WO2021244500 A1 WO 2021244500A1 CN 2021097531 W CN2021097531 W CN 2021097531W WO 2021244500 A1 WO2021244500 A1 WO 2021244500A1
Authority
WO
WIPO (PCT)
Prior art keywords
state
condition
message
backup
status
Prior art date
Application number
PCT/CN2021/097531
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 华为技术有限公司
Publication of WO2021244500A1 publication Critical patent/WO2021244500A1/zh

Links

Images

Classifications

    • 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
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks

Definitions

  • This application relates to the field of communications, and in particular to a method, device and system for determining a backup status.
  • broadband remote access server broadband and remote access server, BRAS
  • CP control plane
  • UP forwarding portion
  • the CP device can manage multiple UP devices to realize the unified configuration of services, the unified management of users, and the unified allocation of resources. In this scenario, it is often necessary to implement hot backup between two UPs. When a user goes online from the main UP, the CP will back up user information to the backup UP.
  • the main UP When the main UP fails, the user traffic will automatically switch to the backup UP to ensure the reliability of the network.
  • the issuance of user information, the determination of the primary/backup UP relationship, and the switching between the primary and backup UPs are all determined by the CP.
  • some failure scenarios such as when the CP fails or the connection between the UP and the CP fails, There may be a dual-master or dual-standby situation, which affects network reliability.
  • the embodiments of the present application provide a method, device, and system for determining a backup status, so as to improve the reliability of the CU separation network.
  • a method for determining a backup status includes: a first device receives a first message sent by a second device, the first message includes a first condition, and the first condition includes a control plane of the second device Separate the protocol CUSP state from the user plane, the first device and the second device are mutually backup; the first device determines that the backup state of the first device is the first state according to the first condition, the second condition, and the current backup state of the first device , The second condition includes the CUSP state of the first device, and the first state includes the main state or the standby state.
  • the first device can synthesize the CUSP status of the first device and the CUSP status of the second device by receiving the CUSP status information sent by the mutually backup devices, and combine the backup status of the first device to determine that the backup status of the first device is the first device.
  • the one-state approach can avoid the dual-master or dual-standby problem that may occur when the CP fails or the connection between the UP and the CP fails, and improves the reliability of the CU separation network.
  • the first condition in the first message further includes the network side state of the second device, and the second condition further includes the network side state of the first device.
  • the accuracy of determining the first state by the first device can be improved. Further provide the reliability of the CU separation network.
  • the first device determines that the backup state of the first device is the first state according to the first condition, the second condition, and the current backup state of the first device, including: the first device according to the first condition , The second condition and the current backup state of the first device, and determine that the backup state of the first device is the first state.
  • the CP In the scenario where the CU is separated, the CP usually determines the status of the active and standby UP, and the CP sends a message to enable the UP to switch between the active and the standby. However, if the CP fails, or the channel between the UP and the CP fails, it may cause the UP to fail to receive the message sent by the UP, or the CP to fail to send the message, and the UP cannot perform the active/standby switch.
  • the first condition by the first device itself based on the condition, the occurrence of the above situation can be avoided and the reliability of the network can be improved.
  • the first device determines that the backup state of the first device is the first state according to the first condition, the second condition, and the current backup state of the first device, including: the first device sends to the management device A first message, the first message includes a first condition and a second condition, and the first message is used to instruct the management device to determine the first state according to the first condition, the second condition, and the current backup state of the first device; in response to the first condition, A message: the first device receives the second message sent by the management device; the first device determines that its backup state is the first state according to the second message.
  • the unified management and control method is still adopted by the CP, which helps to use the existing management method and reduce the processing capacity requirements of the UP equipment.
  • the first device in response to the first message, sends a second message to the second device, and the second message includes the above-mentioned second condition.
  • the first device After the first device receives the first packet sent by the second device, the first device also sends a second packet to the second device, sending the CUSP status of the first device to the second device, or also sending the first device's CUSP status to the second device.
  • the status of the network side can enable the second device to also obtain related information of the first device.
  • the second device can also determine the backup status of the second device and whether it needs to perform a master/backup switch based on this information, which can further improve the reliability of the CU separation network.
  • the first device determines that the connection of the first device is faulty; in response to the connection failure, the first device sends the message to the second device Send a second message, the second message includes the above second condition, and the first message is a response message of the second message.
  • the first device determines that its connection is faulty, it sends a second message to the second device, carrying relevant information about the first device, and after receiving the second message, the second device sends the first message to the first device.
  • Messages enabling this solution to interact with messages and determine state actions only when the device is faulty.
  • the pressure on the first device and the second device can be reduced.
  • a method for determining a backup status including: a management device receives a first message sent by a first device, the first message includes a first condition and a second condition, and the first condition includes a control plane of the first device and User plane separation protocol CUSP status, the second condition includes the CUSP status of the second device, and the first device and the second device are mutually backup; the management device determines the first condition, the second condition, and the current backup status of the first device.
  • the backup state of a device corresponds to the first state, and the first state includes the main state or the standby state; the management device sends a second message to the first device, and the second message is used to indicate that the backup state of the first device corresponds to the first state.
  • the management device receives the message sent by the first device, and the message includes the CUSP status of the first device and the second device, so that the management device can quickly obtain the relevant information required for the judgment of the active/standby switch. Improve the efficiency of management equipment processing. At the same time, this solution can also enable the management device to obtain all the information even when the connection between a certain device and the management device in the main and backup devices is interrupted, which can further improve the reliability of the CU separation network. .
  • the above-mentioned first condition further includes the network side state of the first device
  • the second condition further includes the network side state of the second device.
  • the accuracy of determining the first state by the management device can be improved. Further provide the reliability of the CU separation network.
  • a backup device which has the function of realizing the backup status determination method in the first aspect or any one of the possible design manners in the first aspect.
  • the device includes a receiving unit and a processing unit.
  • the device further includes a sending unit.
  • the device is used to implement the backup status determination method provided in the first aspect or any one of the possible designs of the first aspect.
  • a device in a fourth aspect, includes a processor and at least one physical communication interface, and the processor is used to execute instructions so that the device executes the first aspect or any one of the optional methods provided in the first aspect.
  • the communication interface is used for receiving and sending messages.
  • a backup device which has the function of realizing the backup status determination method in the second aspect or any one of the possible design manners of the second aspect.
  • the device includes a receiving unit, a processing unit, and a sending unit, and the device is used to implement the backup status determination method provided in the second aspect or any one of the possible designs of the second aspect.
  • a device in a sixth aspect, includes a processor and at least one physical communication interface, and the processor is used to execute instructions so that the device executes the foregoing second aspect or any one of the optional manners provided in the second aspect
  • the communication interface is used for receiving and sending messages.
  • an embodiment of the present application also provides a computer-readable storage medium, including a computer program, which when running on a computer, causes the computer to execute the above-mentioned first aspect or any one of the optional methods provided in the first aspect How to determine the backup status of the system.
  • the embodiments of the present application also provide a computer-readable storage medium, including a computer program, which when running on a computer, causes the computer to execute the second aspect or any of the optional methods provided in the second aspect. How to determine the backup status of the system.
  • a computer program product is provided.
  • the first device executes the method for determining the backup status provided in the first aspect or any one of the optional methods of the first aspect.
  • a computer program product is provided.
  • the device executes the method for determining the backup status provided in the second aspect or any one of the optional methods of the second aspect.
  • a chip is provided, when the chip runs on a first device, the first device executes the method for determining the backup status provided in the first aspect or any one of the optional methods of the first aspect.
  • a chip is provided, when the chip runs on a device, the device executes the method for determining the backup status provided in the second aspect or any one of the optional manners in the second aspect.
  • a network system in a thirteenth aspect, includes a first device configured to execute the method described in the first aspect or any one of the optional manners in the first aspect.
  • the foregoing network system further includes a management device configured to execute the method described in the foregoing second aspect or any one of the optional manners of the second aspect.
  • Figure 1 is a schematic diagram of a broadband access network scenario provided by an embodiment of the application
  • FIG. 2a is a schematic flowchart of a method for determining a backup status provided by an embodiment of this application
  • FIG. 2b is a schematic flowchart of a method for determining a backup status according to an embodiment of the application
  • 2c is a schematic flowchart of a method for determining a backup status provided by an embodiment of this application
  • FIG. 3 is a schematic diagram of a message format provided by an embodiment of the application.
  • FIG. 4 is a schematic structural diagram of an apparatus for implementing a method for determining a backup state according to an embodiment of the application
  • FIG. 5 is a schematic structural diagram of an apparatus for implementing a method for determining a backup status according to an embodiment of the application
  • FIG. 6 is a schematic structural diagram of an apparatus for implementing a method for determining a backup status according to an embodiment of the application
  • FIG. 7 is a schematic structural diagram of an apparatus for implementing a method for determining a backup status according to an embodiment of the application
  • FIG. 8 is a schematic structural diagram of a network system 800 provided by an embodiment of the present application.
  • Figure 1 shows a broadband access network that includes a first device, a second device, a management device, and a broadband access network.
  • the connection network, the first device, the second device and the management device are respectively connected to the connection network.
  • the connection network may be a connection network for transmitting user services, and can be connected to the management device, the first device and the second device at the same time.
  • the first device can be the primary UP
  • the second device can be the backup UP
  • the first device can be the backup UP
  • the second device can be the primary UP.
  • the first device and the second device can use the remote backup service (remote backup service, RBS) channel for communication.
  • RBS remote backup service
  • the RBS channel can be carried on the heartbeat link between the first device and the second device, or on the above-mentioned connection network.
  • the heartbeat link here includes the first device and the second device.
  • the network also includes a management device, namely a CP device, which is responsible for managing the first device and the second device, and the management device can manage the first device and the second device through a virtual channel or a physical channel.
  • the first device, the second device, and the management device in the figure may be physical devices or virtual devices. This application does not make specific restrictions.
  • the first device and the second device can be configured as a hot backup.
  • the distribution of user information, the determination of the primary/standby UP relationship, and the switching between primary and secondary UPs are all determined by the CP.
  • the reliability rules are as follows:
  • the standby UP will not be automatically promoted to the primary UP before receiving the CP command.
  • connection failures include one or more of CUSP failures or network-side failures.
  • CUSP failures include CUSP channel failures or CP failures
  • network-side failures refer to failures such as the unreachable connection link between UP and the network side or certain routes.
  • UP cannot distinguish between CUSP channel failures and CP failures in CUSP failures, this rule will contradict the following two scenarios.
  • the primary UP when the CP fails, the primary UP will automatically be reduced to the standby UP, but at this time, due to the CP failure, the standby UP will not automatically become the primary UP, resulting in the status of both UPs being the standby state. It may cause the user traffic to be unprocessed.
  • Fig. 2a is a flowchart of a method for determining a backup status provided by an embodiment of the present application, which includes the following steps:
  • the first device generates a first message, the first message includes the first condition, and the first condition includes the CUSP state of the first device.
  • the first device and the second device are mutual backups.
  • the first device may be the main UP
  • the second device may be the backup UP
  • the first device may be the backup UP
  • the second device may be the main UP, which is not specifically limited in this application.
  • the first device may carry the CUSP state of the first device in the generated first packet.
  • the CUSP status of the first device is the CUSP fault status. It corresponds to CUSP channel failure and/or CP failure.
  • the CUSP status of the first device carried in the first message is: working (UP), indicating that the CUSP channel and the connected CP have no faults.
  • the CUPS status of the first device carried in the first message is: down, indicating that its CUSP channel and/or connected CP is faulty.
  • the first condition includes the CUSP of the first device
  • the example where the first condition includes the CUSP of the first device may also have other forms.
  • the first condition further includes the network-side state of the first device.
  • the state of the network side indicates the state of the first device connected to the network shown in FIG. 1.
  • the network-side status of the first device carried in the first packet is: down, indicating that the link between the first device and the connection network shown in FIG. 1 is faulty or that the second device is connected to the connection network.
  • the route is unreachable.
  • the network-side state of the first device carried in the first packet is: up, indicating that there is no fault temporarily between the first device and the connection network shown in FIG. 1.
  • the first condition includes the network-side state of the first device
  • the example where the first condition includes the network-side state of the first device may also have other forms.
  • the 0 or 1 flag is used to indicate the status of the network side. This application does not make specific restrictions.
  • the format of the first message generated by the first device is shown in FIG. 3, and the first message may include the following information:
  • Backup group ID (optional): Use the backup group ID to identify the scope of the message as the backup group to which the first device and the second device belong.
  • Service type It can be used to indicate the backup mode between the first device and the second device, such as hot backup.
  • Message length (optional): Indicate the length of the first message.
  • the first message is an RBS message.
  • the first message may be another protocol message, such as a self-defined message message.
  • the manner in which the first device generates the first message may include the following three situations:
  • the first device may generate the first message at regular intervals, for example, generate the first message every 30 minutes.
  • the first device may also generate the first message because of a trigger condition.
  • the trigger condition may include that the first device determines that its connection is faulty or that the first device receives the second packet sent by the second device. That is, Case 2 includes the following cases 2.1 or 2.2.
  • Case 2.1 in an example, before the first device generates the first message, the first device determines that its connection is faulty, and in response to the connection failure, the first device generates the first message.
  • the first device can determine the connection failure through monitoring or alarming.
  • the first device's determination of its connection failure includes: the first device's determination of its CUSP failure and/or network-side failure.
  • the first message generated by the first device includes the first condition, and the first condition includes the CUSP state.
  • the first condition generated by the first device may only include the CUSP state.
  • the CUSP state is down.
  • the first condition generated by the first device includes the CUSP state and the network side state.
  • the state of the network side is down.
  • the trigger condition includes that the first device receives the second message sent by the second device.
  • the method for determining the backup status shown in FIG. 2c may further include steps: S201 to S204:
  • S201 The second device determines that the connection is faulty.
  • the manner in which the second device determines the connection failure is similar to the manner in which the first device determines the connection failure. For details, please refer to the above and will not be repeated in this application.
  • the second device In response to the connection failure, the second device generates a second message, the second message includes a second condition, and the second condition includes the CUSP state of the second device.
  • the first condition generated by the second device may only include the CUSP state.
  • the CUSP state is down.
  • the first condition generated by the second device includes the CUSP state and the network side state.
  • the network side status is down.
  • the second message is a request message.
  • S203 The second device sends a second message to the first device.
  • the second device may send the second packet through the interaction channel between the second device and the first device.
  • the second device may send the second packet to the first device through the RBS channel.
  • S204 The first device receives the second message.
  • the first device receives a second packet sent by the second device, where the second packet includes a second condition, and the second condition includes the CUSP state of the second device.
  • the first device In response to the second message, the first device generates the aforementioned first message.
  • the first message may also be referred to as a response message.
  • S210 The first device sends the first message to the second device.
  • the first device can send the first message to the second device through the connection channel with the second device,
  • connection channel may be an RBS channel.
  • S215 The second device receives the first message.
  • the second device receives the first packet sent by the first device.
  • the second device may A second message is generated, the second message includes a second condition, the second condition includes the CUSP state of the second device, and the second condition may also include the network side state of the second device.
  • the content carried in the second packet generated by the second device is similar to the content carried in the first packet generated by the first device described above, and will not be repeated in this application.
  • the second device also sends the second packet to the first device. This application does not specifically limit the time for the second device to send the second message to the first device.
  • the second device may send the second message to the first device after receiving the first message and generating the second message.
  • the second message may also be sent after the following S220 is executed. That is, this application does not limit the timing for the second device to send the second message to the first device, and it may be before S220 or after S220.
  • S220 The second device determines that the backup state of the second device is the first state according to the first condition, the second condition, and its current backup state.
  • the second device obtains the foregoing first condition from the received first message.
  • the second device may obtain the second condition according to its own state, the second condition includes the CUSP state of the second device, and the second condition may also include the network side state of the second device.
  • the current backup state of the second device refers to the backup state of the second device before obtaining the first state.
  • the second device determines that the backup state of the second device is the first state according to the first condition, the second condition, and its current backup state, including the following multiple methods:
  • Manner 1 The second device makes a judgment based on the first condition, the second condition, and the current backup state of the second device to obtain the first state.
  • the second device makes a judgment based on the first condition, the second condition, and the current backup state of the second device to obtain the first state.
  • the second device does not perform special processing.
  • the second device performs the switching of the backup state, such as switching from the main to the standby, or from the standby to the main.
  • the second device mainly adopts method 1 to switch between active and standby.
  • the manner in which the second device determines the first state corresponding to the second device according to the first condition, the second condition, and the current backup state of the second device can refer to the rules shown in Table 1 or Table 2 below.
  • the main UP may be the above-mentioned first device
  • the standby UP may be the above-mentioned second device.
  • the main UP is the above-mentioned second device
  • the standby UP is the above-mentioned first device.
  • the second device is the main UP
  • its determined first state is the state corresponding to the main UP in the first state column in Table 1 or Table 2 below.
  • the second device is the standby UP
  • the determined first state is the state corresponding to the standby UP in the first state column in Table 1 or Table 2 below.
  • the determination rule for the first state may be as shown in Table 1.
  • the determination rule of the first state may be as shown in Table 2.
  • Manner 2 The second device sends the first condition and the second condition to the management device.
  • the method 2 will be introduced below in conjunction with Figure 2c.
  • the method for determining the backup status shown in FIG. 2a may further include the steps in FIG. 2c, and FIG. 2c includes the following steps:
  • S2201 The second device sends a first message to the management device, where the first message includes the foregoing first condition and second condition.
  • the first message also includes the current backup status of the second device.
  • the second device may send the first message through the management channel with the management device.
  • the second device may only change the content of the first condition included in the received first message, or the first message Second, when the status of the device itself changes, the first message is sent to the management device.
  • the second device when the second device is the first packet obtained due to a connection failure (including the connection failure of the first device and/or the connection failure of the second device), the second device may obtain the first packet after obtaining the first packet. , The first message is sent to the management device.
  • the information carried in the first message sent by the second device to the management device may specifically include the following information:
  • the role of the backup group ID and the service type can be referred to the explanation of the first message generated by the first device, which will not be repeated here.
  • S2203 The management device determines that the backup state of the second device corresponds to the first state according to the first condition, the second condition, and the current backup state of the second device.
  • the first message also includes the current backup status of the second device.
  • the management device includes the current backup status of the second device according to other information, such as stored information of the second device.
  • the management device obtains the first condition and the second condition from the received first message, and determines the first state corresponding to the backup state of the second device through the first condition, the second condition, and the current backup state of the second device.
  • S2204 The way that the management device determines that the backup state of the second device corresponds to the first state through the first condition and the second condition is similar to the above-mentioned determination rule for the second device to determine the first state through the first condition and the second condition. For details, please see the description above. , I won’t repeat it here.
  • S2204 The management device sends a second message to the second device, where the second message is used to indicate that the backup state of the second device corresponds to the first state.
  • the management device may send a second message to the second device.
  • the second message sent by the management device to the second device may have multiple situations:
  • the second message may only indicate to the second device that the first message sent by the second device has been received. That is, the second message indicates that the second device can maintain the current backup state.
  • the management device may directly send an instruction to the second device to instruct the second device to switch to the first state.
  • the two messages indicate that the backup state of the second device is switched to the primary state or to the standby state.
  • S2205 The second device determines according to the second message that the backup state of the second device is the first state.
  • the second device After receiving the second message, the second device determines that its backup state is the first state according to the second message. Corresponding to situation 1 above, the second device does not need to switch the backup state. Corresponding to situation 2 above, the second device executes the instruction of the second message to switch between the active and standby states, and switch its backup state to the first state. Corresponding to the situation 3 above, the second device obtains the first state after receiving the second message, and judges according to the first state. If the first state is consistent with the current backup state, the backup state switch will not be performed. If the status is inconsistent with the current backup status, the backup status switch is executed.
  • the method of the embodiment of the present application is described above, and the device of the embodiment of the present application is described below.
  • the device introduced below has any function of the first network device in the above method.
  • FIG. 4 is a schematic structural diagram of a device 400 provided by an embodiment of the present application.
  • the device 400 includes a receiving unit 401, a processing unit 402, and optionally, the device further includes a sending unit 403.
  • the foregoing receiving unit may be used to implement the method related to receiving the first message in the foregoing method embodiment
  • the processing unit 402 may be used to implement the method related to determining the first state in the foregoing method embodiment
  • the sending unit 403 may be used to implement the foregoing The related method of sending the second message or sending the first message in the method embodiment.
  • the apparatus 400 may correspond to the first device or the second device in the foregoing method embodiment.
  • the modules in the device 400 and the other operations and/or functions described above are used to implement various steps and methods implemented by the first device or the second device in the method embodiment.
  • the device 400 implements the foregoing method for determining the backup status
  • only the division of the foregoing functional modules is used as an example for illustration.
  • the foregoing function allocation can be completed by different functional modules as required, that is, the internal structure of the device 400 is divided into Different functional modules to complete all or part of the functions described above.
  • the device 400 provided in the foregoing embodiment belongs to the same concept as the foregoing method embodiment, and its specific implementation process is detailed in the foregoing method embodiment, and will not be repeated here.
  • FIG. 5 is a schematic structural diagram of an apparatus 500 provided by an embodiment of the present application.
  • the apparatus 500 includes a receiving unit 501, a processing unit 502, and a sending unit 503.
  • the foregoing receiving unit may be used to implement the method related to receiving the first message related to the management device in the foregoing method embodiment
  • the processing unit 402 may be used to implement the method related to the management device determining the first state in the foregoing method embodiment.
  • the sending unit 403, It can be used to implement the related method for sending the second message of the management device in the foregoing method embodiment.
  • the apparatus 500 may correspond to the management device in the foregoing method embodiment.
  • the modules in the device 500 and the above-mentioned other operations and/or functions are used to implement various steps and methods implemented by the management device in the method embodiment.
  • the device 500 implements the foregoing method for determining the backup status
  • only the division of the foregoing functional modules is used as an example for illustration.
  • the foregoing function allocation can be completed by different functional modules as required, that is, the internal structure of the device 500 is divided into Different functional modules to complete all or part of the functions described above.
  • the device 500 provided in the foregoing embodiment belongs to the same concept as the foregoing method embodiment, and its specific implementation process is detailed in the foregoing method embodiment, and will not be repeated here.
  • the embodiments of this application also provide a device, and the hardware structure of the device is introduced below.
  • the apparatus 600 described below corresponds to the first device in the foregoing method embodiment, and the various hardware, modules, and the foregoing other operations and/or functions in the apparatus 600 are used to implement various implementations of the first device in the foregoing method embodiment. Steps and methods. Regarding the detailed flow of how the device 600 implements the method for determining the backup status, for specific details, please refer to the foregoing method embodiment. For the sake of brevity, details are not described herein again. Wherein, each step in the above method can be completed by an integrated logic circuit of hardware in the processor of the device 600 or instructions in the form of software.
  • the steps of the method combined with the embodiments of the present application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware. In order to avoid repetition, it will not be described in detail here.
  • the device 600 corresponds to the device 400 in the foregoing virtual device embodiment, and each functional module in the device 400 is implemented by the software of the device 600.
  • the functional modules included in the device 400 are generated after the processor of the device 600 reads the program code stored in the memory.
  • FIG. 6 shows a schematic structural diagram of an apparatus 600 provided by an exemplary embodiment of the present application.
  • the apparatus 600 may be the first device or the second device in the foregoing method embodiment.
  • the device 600 can be implemented by a general bus architecture.
  • the apparatus 600 includes at least one processor 601, a communication bus 602, a memory 603, and at least one physical communication interface 604.
  • the processor 601 may be a general-purpose CPU, NP, microprocessor, or may be one or more integrated circuits used to implement the solution of the present application, for example, application-specific integrated circuit (ASIC), programmable logic A device (programmable logic device, PLD) or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic A device
  • the above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (generic array logic, GAL), or any combination thereof.
  • the communication bus 602 is used to transfer information between the aforementioned components.
  • the communication bus 602 can be divided into an address bus, a data bus, a control bus, and so on. For ease of representation, only one thick line is used in FIG. 6, but it does not mean that there is only one bus or one type of bus.
  • the memory 603 can be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, or it can be a random access memory (RAM) or can store information and instructions
  • ROM read-only memory
  • RAM random access memory
  • Other types of dynamic storage devices can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage , CD storage (including compressed CDs, laser disks, CDs, digital universal CDs, Blu-ray CDs, etc.), disk storage media or other magnetic storage devices, or can be used to carry or store desired program codes in the form of instructions or data structures And any other media that can be accessed by the computer, but not limited to this.
  • the memory 603 may exist independently and is connected to the processor 601 through the communication bus 602.
  • the memory 603 may also be integrated with the processor 601.
  • the at least one physical communication interface 604 uses any device such as a transceiver for communicating with other devices or communication networks.
  • the at least one physical communication interface 604 includes a wired communication interface, and may also include a wireless communication interface.
  • the wired communication interface may be, for example, an Ethernet interface.
  • the Ethernet interface can be an optical interface, an electrical interface or a combination thereof.
  • the wireless communication interface may be a wireless local area network (WLAN) interface, a cellular network communication interface, or a combination thereof.
  • WLAN wireless local area network
  • the processor 601 may include one or more CPUs, such as CPU0 and CPU1 as shown in FIG. 6.
  • the apparatus 600 may include multiple processors, such as the processor 601 and the processor 605 as shown in FIG. 6. Each of these processors can be a single-core processor or a multi-core processor.
  • the processor here may refer to one or more devices, circuits, and/or processing cores for processing data (such as computer program instructions).
  • the apparatus 600 may further include an output device (not shown in the figure) and an input device (not shown in the figure).
  • the output device communicates with the processor 601 and can display information in a variety of ways.
  • the output device may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector (projector).
  • the input device communicates with the processor 601 and can receive user input in a variety of ways.
  • the input device can be a mouse, a keyboard, a touch screen device, or a sensor device.
  • the memory 603 is used to store the program code 610 for executing the solution of the present application, and the processor 601 can execute the program code 610 stored in the memory 603. That is, the apparatus 600 can implement the method provided in the foregoing method embodiment through the processor 601 and the program code 610 in the memory 603.
  • the device 600 of the embodiment of the present application may correspond to the first device or the second device in the foregoing method embodiments, and the device 600, etc. may implement the functions of the first device or the second device in the foregoing method embodiments And/or the various steps and methods implemented. For the sake of brevity, I will not repeat them here.
  • FIG. 7 shows a schematic structural diagram of an apparatus 700 provided by an exemplary embodiment of the present application.
  • the apparatus 700 may be the management device in the foregoing method embodiment.
  • the device 700 can be implemented by a general bus architecture.
  • the apparatus 700 includes at least one processor 701, a communication bus 702, a memory 703, and at least one physical communication interface 704.
  • the processor 701 may be a general-purpose CPU, NP, or microprocessor, or may be one or more integrated circuits used to implement the solution of the present application, for example, application-specific integrated circuit (ASIC), programmable logic A device (programmable logic device, PLD) or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic A device
  • the aforementioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.
  • the communication bus 702 is used to transfer information between the aforementioned components.
  • the communication bus 702 can be divided into an address bus, a data bus, a control bus, and so on. For ease of presentation, only one thick line is used to represent in FIG. 7, but it does not mean that there is only one bus or one type of bus.
  • the memory 703 can be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, or it can be a random access memory (RAM) or can store information and instructions
  • ROM read-only memory
  • RAM random access memory
  • Other types of dynamic storage devices can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage , CD storage (including compressed CDs, laser disks, CDs, digital universal CDs, Blu-ray CDs, etc.), disk storage media or other magnetic storage devices, or can be used to carry or store desired program codes in the form of instructions or data structures And any other media that can be accessed by the computer, but not limited to this.
  • the memory 703 may exist independently and is connected to the processor 701 through the communication bus 702.
  • the memory 703 may also be integrated with the processor 701.
  • the at least one physical communication interface 704 uses any device such as a transceiver for communicating with other devices or communication networks.
  • the at least one physical communication interface 704 includes a wired communication interface, and may also include a wireless communication interface.
  • the wired communication interface may be, for example, an Ethernet interface.
  • the Ethernet interface can be an optical interface, an electrical interface or a combination thereof.
  • the wireless communication interface may be a wireless local area network (WLAN) interface, a cellular network communication interface, or a combination thereof.
  • WLAN wireless local area network
  • the processor 701 may include one or more CPUs, such as CPU0 and CPU1 as shown in FIG. 7.
  • the apparatus 700 may include multiple processors, such as the processor 701 and the processor 705 as shown in FIG. 7. Each of these processors can be a single-core processor or a multi-core processor.
  • the processor here may refer to one or more devices, circuits, and/or processing cores for processing data (such as computer program instructions).
  • the apparatus 700 may further include an output device (not shown in the figure) and an input device (not shown in the figure).
  • the output device communicates with the processor 701 and can display information in a variety of ways.
  • the output device may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector (projector).
  • the input device communicates with the processor 701 and can receive user input in a variety of ways.
  • the input device can be a mouse, a keyboard, a touch screen device, or a sensor device.
  • the memory 703 is used to store the program code 710 for executing the solution of the present application, and the processor 701 can execute the program code 710 stored in the memory 703. That is, the apparatus 700 can implement the method provided in the foregoing method embodiment through the processor 701 and the program code 710 in the memory 703.
  • the apparatus 700 in the embodiment of the present application may correspond to the management device in the foregoing method embodiment, and the apparatus 700 and the like may implement the functions and/or various steps implemented by the management device in the foregoing method embodiments. method.
  • I will not repeat them here.
  • the foregoing first device, second device, or management device may be implemented as a virtualized device.
  • the virtualization device may be a virtual machine (English: Virtual Machine, VM) running a program for sending a message function, and the virtual machine is deployed on a hardware device (for example, a physical server).
  • a virtual machine refers to a complete computer system with complete hardware system functions that is simulated by software and runs in a completely isolated environment.
  • the first device can be implemented based on a general physical server combined with Network Functions Virtualization (NFV) technology.
  • the first device is a virtual host, a virtual router, or a virtual switch.
  • NFV Network Functions Virtualization
  • the virtualization device may be a container, and the container is an entity used to provide an isolated virtualization environment.
  • the container may be a docker container.
  • the container can be configured as a first device, a second device, or a management device.
  • the first device, the second device, or the management device can be created through the corresponding image.
  • two container instances can be created for the proxy-container through the image of proxy-container (a container that provides proxy services), which are containers respectively.
  • the instance proxy-container1, the container instance proxy-container2, the container instance proxy-container1 is provided as the first device or the first computing device, and the container instance proxy-container2 is provided as the second device or the second computing device.
  • the first device or the second device can run using the kernel of a physical machine, and multiple first devices or second devices can share the operating system of the physical machine.
  • the container technology can isolate different first or second devices.
  • the containerized first device or second device can run in a virtualized environment, for example, can run in a virtual machine, and the containerized first device or second device can also run directly in a physical machine.
  • the virtualization device can be a Pod, which is Kubernetes (Kubernetes is a container orchestration engine open sourced by Google, referred to as K8s in English) as the basic unit for deploying, managing, and orchestrating containerized applications.
  • Pod can include one or more containers. Each container in the same Pod is usually deployed on the same host, so each container in the same Pod can communicate through the host, and can share storage resources and network resources of the host.
  • Pod can be configured as the first device.
  • container as a service full English name: container as a service, English abbreviation: CaaS, which is a PaaS service based on containers
  • CaaS which is a PaaS service based on containers
  • the first device, the second device, or the management device may also be other virtualized devices, which are not listed here.
  • the foregoing first device, second device, or management device may also be implemented by a general-purpose processor.
  • the general-purpose processor may be in the form of a chip.
  • the general-purpose processor that implements the first device, the second device, or the management device includes a processing circuit and an input interface and an output interface that are internally connected and communicated with the processing circuit, and the processing circuit is used to execute the foregoing method embodiments through the input interface. The steps in the lost clock message.
  • the general-purpose processor may further include a storage medium, and the processing circuit is configured to execute the storage steps in each of the foregoing method embodiments through the storage medium.
  • the storage medium may store instructions executed by the processing circuit, and the processing circuit is configured to execute the instructions stored in the storage medium to execute the foregoing method embodiments.
  • an embodiment of the present application provides a network system 800, and the system 800 includes a first device 801.
  • the first device 801 is, for example, the device 400 or the device 600.
  • the system further includes a second device 802.
  • the second device 802 may be the device 400 or the device 600.
  • the first device 801 and the second device 802 are used to implement the function of the UP part of the BRAS device.
  • the first device 801 and the second device 802 are mutual backups.
  • the system 800 further includes a management device 803, and the management device may be the apparatus 500 or the apparatus 700.
  • the management device is used to implement the CP function in the BRAS device.
  • the embodiments of the present application provide a computer program product, which when the computer program product runs on a first device, causes the first device to execute the method in the foregoing method embodiment.
  • the embodiments of the present application provide a computer program product, which when the computer program product runs on a second device, causes the second device to execute the method in the foregoing method embodiment.
  • the embodiment of the present application provides a computer program product, which when the computer program product runs on a management device, causes the management device to execute the method in the foregoing method embodiment.
  • This application provides a computer storage medium for storing programs, codes or instructions used by the above-mentioned devices.
  • the processors or hardware devices execute these programs, codes or instructions, the above-mentioned first device, second device or management can be completed. The function or procedure of the device.
  • An embodiment of the present application further provides a chip system, including: a processor, the processor is coupled with a memory, the memory is used to store a program or instruction, when the program or instruction is executed by the processor, the The chip system implements the method in any of the foregoing method embodiments.
  • processors in the chip system there may be one or more processors in the chip system.
  • the processor can be implemented by hardware or software.
  • the processor may be a logic circuit, an integrated circuit, or the like.
  • the processor may be a general-purpose processor, which is implemented by reading software codes stored in the memory.
  • the memory may be integrated with the processor, or may be provided separately from the processor, which is not limited in this application.
  • the memory may be a non-transitory processor, such as a read-only memory ROM, which may be integrated with the processor on the same chip, or may be set on different chips.
  • the setting method of the processor is not specifically limited.
  • the chip system may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or a system on chip (SoC). It can also be a central processor unit (CPU), a network processor (NP), a digital signal processing circuit (digital signal processor, DSP), or a microcontroller (microcontroller).
  • the controller unit, MCU may also be a programmable logic device (PLD) or other integrated chips.
  • each step in the foregoing method embodiments may be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software.
  • the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiment described above is only illustrative.
  • the division of the unit is only a logical function division, and there may be other division methods in actual implementation, for example, multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may also be electrical, mechanical or other forms of connection.
  • the unit described as a separate component may or may not be physically separated, and the component displayed as a unit may or may not be a physical unit, that is, it may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments of the present application.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium.
  • the technical solution of this application is essentially or the part that contributes to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium It includes several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other media that can store program code .
  • the computer program product includes one or more computer program instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer program instructions can be passed from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a digital video disc (DVD), or a semiconductor medium (for example, a solid state hard disk).

Abstract

本申请公开了一种备份状态确定方法、装置及系统。第一设备接收第二设备发送的第一报文，第一报文包括第一条件，第一条件包括第二设备的控制面和用户面分离协议CUSP状态，第一设备与第二设备互为备份；第一设备根据上述第一条件、第二条件和第一设备的当前备份状态，确定第一设备的备份状态为第一状态，上述第二条件包括第一设备的CUSP状态，第一状态包括主状态或备状态。

Description

一种备份状态确定方法、装置及系统
本申请要求于2020年5月30日提交的申请号为202010480723.1、发明名称为“一种备份状态确定方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种备份状态确定方法、装置及系统。
背景技术
在宽带接入网络中，宽带远程接入服务器(broad and remote access server，BRAS)设备可以通过控制部分(control plane，CP)和转发部分(也可以称为用户面(user plane，UP))相互分离来实现。CP负责用户的管理和控制，UP负责用户报文的转发，执行传统设备转发面的功能。CP设备可以管理多个UP设备，实现业务的统一配置、用户的统一管理、资源的统一分配。在这种场景下，常常需要实现两个UP之间的热备。用户从主UP上线时，CP会将用户信息备份到备UP，当主UP故障时，用户流量会自动切换到备UP上，以保障该网络的可靠性。在UP热备场景下，用户信息的下发、主备UP关系的确定、主备UP的切换均由CP决定，在一些故障场景下，如当CP出现故障或者UP与CP的连接故障时，可能会出现双主或双备的情况，影响网络可靠性。
发明内容
本申请实施例提供了一种备份状态确定方法、装置及系统，以提高CU分离网络的可靠性。
技术方案如下：
第一方面，提供了一种备份状态确定方法，该方法包括：第一设备接收第二设备发送的第一报文，第一报文包括第一条件，第一条件包括第二设备的控制面和用户面分离协议CUSP状态，第一设备与第二设备互为备份；第一设备根据第一条件、第二条件和第一设备的当前备份状态，确定第一设备的备份状态为第一状态，第二条件包括第一设备的CUSP状态，第一状态包括主状态或备状态。
第一设备通过接收互为备份的设备发送的CUSP状态信息，可以综合第一设备的CUSP状态、第二设备的CUSP状态，并结合第一设备的备份状态，确定第一设备的备份状态为第一状态的方式，可以避免当CP出现故障或者UP与CP的连接故障时，可能会出现双主或双备的问题，提高CU分离网络的可靠性。
在一种可能的设计方式中，第一报文中的第一条件还包括第二设备的网络侧状态，第二条件还包括第一设备的网络侧状态。
通过在第一报文中携带第二设备的更多信息，可以提升第一设备确定第一状态的准确性。进一步提供CU分离网络的可靠性。
在一种可能的设计方式中，第一设备根据第一条件、第二条件和第一设备的当前备份状态，确定第一设备的备份状态为第一状态，包括：第一设备根据第一条件、第二条件和第一 设备的当前备份状态，判断第一设备的备份状态为第一状态。
CU分离的场景下，通常由CP来决定主备UP的状态，CP通过发送消息来使得UP实现主备的切换。但是如果CP故障，或UP与CP之间的通道故障，可能导致UP无法接收到UP发送的消息，或CP无法发送消息，则使得UP无法进行主备切换。通过第一设备自己根据条件判断得出第一条件，可以避免上述情况的发生，提高该网络的可靠性。
在一种可能的设计方式中，第一设备根据第一条件、第二条件和第一设备的当前备份状态，确定第一设备的备份状态为第一状态，包括：第一设备向管理设备发送第一消息，第一消息包括第一条件和第二条件，该第一消息用于指示管理设备根据第一条件、第二条件和第一设备的当前备份状态确定上述第一状态；响应于第一消息，第一设备接收管理设备发送的第二消息；第一设备根据该第二消息确定其备份状态为第一状态。
当某台UP与CP之间的通道没有故障的时候，仍然采用由CP实现统一管理、控制的方式，有助于沿用现有管理方式，降低对UP设备的处理能力要求。
在一种可能的设计方式中，响应于第一报文，第一设备向第二设备发送第二报文，第二报文包括上述第二条件。
当第一设备接收到第二设备发送的第一报文后，第一设备还向第二设备发送第二报文，向第二设备发送第一设备的CUSP状态，或还发送第一设备的网络侧状态，可以使得第二设备也能获取到第一设备的相关信息。第二设备也可以根据这些信息确定第二设备的备份状态以及是否需要进行主备切换，可以进一步提升本CU分离网络的可靠性。
在一种可能的设计方式中，在第一设备接收第二设备发送的第一报文之前，第一设备确定所述第一设备的连接故障；响应于连接故障，第一设备向第二设备发送第二报文，第二报文包括上述第二条件，而第一报文为第二报文的响应报文。
即，当第一设备确定其连接故障后，向第二设备发送第二报文，携带第一设备的相关信息，第二设备在接收到第二报文后，再向第一设备发送第一报文，使得本方案仅在设备有故障时再进行报文的交互以及确定状态动作。可以降低对第一设备和第二设备的压力。
第二方面，提供了一种备份状态确定方法，包括：管理设备接收第一设备发送的第一消息，第一消息包括第一条件和第二条件，第一条件包括第一设备的控制面和用户面分离协议CUSP状态，第二条件包括第二设备的CUSP状态，第一设备和第二设备互为备份；管理设备根据第一条件、第二条件和第一设备的当前备份状态，确定第一设备的备份状态对应为第一状态，第一状态包括主状态或备状态；管理设备向第一设备发送第二消息，第二消息用于指示第一设备的备份状态对应第一状态。
管理设备通过接收第一设备发送的消息，该消息中包括第一设备和第二设备的CUSP状态可以使得管理设备快速的获取到做主备切换判断所需的相关信息。提高管理设备处理的效率。同时，这种方案，也可以使得，即使当主备设备中，有某一台设备跟管理设备的连接中断的情况下，管理设备任然能获得所有信息，可以进一步提高该CU分离网络的可靠性。
在一种可能的设计方式中，上述第一条件还包括第一设备的网络侧状态，第二条件还包括第二设备的网络侧状态。
通过在第一消息中携带更多的信息，可以提升管理设备确定第一状态的准确性。进一步提供CU分离网络的可靠性。
第三方面，提供了一种备份装置，该装置具有实现上述第一方面或第一方面任一种可能 的设计方式中的备份状态确定方法的功能。该装置包括接收单元、处理单元，可选的，该装置还包括发送单元，该装置用于实现上述第一方面或第一方面任一种可能的设计中所提供的备份状态确定方法。第三方面提供的装置的具体细节可参见上述第一方面或第一方面任一种可选方式，此处不再赘述。
第四方面，提供了一种装置，该装置包括处理器和至少一个物理通信接口，该处理器用于执行指令，使得该装置执行上述第一方面或第一方面任一种可选方式所提供的备份状态确定方法，所述通信接口用于接收报文和发送报文。第四方面提供的装置的具体细节可参见上述第一方面或第一方面任一种可选方式，此处不再赘述。
第五方面，提供了一种备份装置，该装置具有实现上述第二方面或第二方面任一种可能的设计方式中的备份状态确定方法的功能。该装置包括接收单元、处理单元，和发送单元，该装置用于实现上述第二方面或第二方面任一种可能的设计中所提供的备份状态确定方法。第五方面提供的装置的具体细节可参见上述第一方面或第一方面任一种可选方式，此处不再赘述。
第六方面，提供了一种装置，该装置包括处理器和至少一个物理通信接口，该处理器用于执行指令，使得该装置执行上述第二方面或第二方面任一种可选方式所提供的备份状态确定方法，所述通信接口用于接收报文和发送报文。第六方面提供的装置的具体细节可参见上述第一方面或第一方面任一种可选方式，此处不再赘述。
第七方面，本申请实施例还提供了一种计算机可读存储介质，包括计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面或第一方面任一种可选方式所提供的备份状态确定方法。
第八方面，本申请实施例还提供了一种计算机可读存储介质，包括计算机程序，当其在计算机上运行时，使得计算机执行上述第二方面或第二方面任一种可选方式所提供的备份状态确定方法。
第九方面，提供了一种计算机程序产品，当该计算机程序产品在设备上运行时，使得第一设备执行上述第一方面或第一方面任一种可选方式所提供的备份状态确定方法。
第十方面，提供了一种计算机程序产品，当该计算机程序产品在设备上运行时，使得设备执行上述第二方面或第二方面任一种可选方式所提供的备份状态确定方法。
第十一方面，提供了一种芯片，当该芯片在第一设备上运行时，使得第一设备执行上述第一方面或第一方面任一种可选方式所提供的备份状态确定方法。
第十二方面，提供了一种芯片，当该芯片在设备上运行时，使得设备执行上述第二方面或第二方面任一种可选方式所提供的备份状态确定方法。
第十三方面，提供了一种网络系统，该网络系统包括第一设备，该第一设备用于执行上述第一方面或第一方面任一种可选方式所述的方法。
在一种可能的设计方式中，上述网络系统还包括管理设备，该管理设备用于执行上述第二方面或第二方面任一种可选方式所述的方法。
附图说明
图1为本申请实施例提供的宽带接入网络场景示意图；
图2a为本申请实施例提供的一种备份状态确定方法流程示意图；
图2b为本申请实施例提供的一种备份状态确定方法流程示意图；
图2c为本申请实施例提供的一种备份状态确定方法流程示意图；
图3为本申请实施例提供的一种报文格式示意图；
图4为本申请实施例提供的一种用于实现备份状态确定方法的装置结构示意图；
图5为本申请实施例提供的一种用于实现备份状态确定方法的装置结构示意图；
图6为本申请实施例提供的一种用于实现备份状态确定方法的装置结构示意图；
图7为本申请实施例提供的一种用于实现备份状态确定方法的装置结构示意图；
图8是本申请实施例提供的一种网络系统800的结构示意图。
具体实施方式
本申请的实施方式部分使用的术语仅用于对本申请的具体实施例进行解释，而非旨在限定本申请。
本申请中术语“第一”“第二”“第三”等字样用于对作用和功能基本相同的相同项或相似项进行区分，应理解，“第一”、“第二”和“第三”之间不具有逻辑或时序上的依赖关系，也不对数量和执行顺序进行限定。
以下，简单介绍本申请实施例涉及的相关技术：
以图1为示例，介绍本申请提供的一种宽带接入网络场景示意图，图1中示出了一个宽带接入网络，该宽带接入网络中包括第一设备、第二设备、管理设备和连接网络，第一设备、第二设备和管理设备分别与连接网络相连，该连接网络可以是用于传输用户业务的连接网络，同时能连接管理设备、第一设备和第二设备。其中第一设备可以为主UP，第二设备可以为备UP，也可以是第一设备可以为备UP，第二设备为主UP，第一设备和第二设备之间通过远程备份服务(remote backup service，RBS)通道进行通信，该RBS通道可以承载在第一设备和第二设备之间的心跳链路上，也可以承载在上述连接网络中，这里的心跳链路包括第一设备和第二设备之间有物理链路相连。该网络中还包括管理设备，即CP设备，该管理设备负责管理第一设备和第二设备，管理设备可以通过虚拟通道或物理通道管理第一设备和第二设备。图中的第一设备、第二设备和管理设备可以为物理设备，也可以为虚拟设备。本申请不做具体限定。
在该网络场景中，第一设备和第二设备之间可以被配置为热备份。在这种UP热备场景中，用户信息的下发、主备UP关系的确定、主备UP的切换均由CP决定，当CP出现故障或者UP与CP断链时，可靠性规则如下：
1、备UP在没有收到CP的命令前不会自动升为主UP。
2、当CP出现故障或者主UP与CP之间的通道故障时，主UP会自动降备。
在这种情况下，会影响UP主备状态切换的原因包括连接故障，该连接故障包括：CUSP故障或网络侧故障中的一种或多种。其中，CUSP故障包括CUSP通道故障或CP故障，网络侧故障指UP与网络侧的连接链路或某些路由不可达等故障。但是，由于UP无法对CUSP故障中的CUSP通道故障和CP故障进行区别，因此，这种规则在处理如下两种场景时会出现矛盾。
如，当CP故障时，主UP会自动降为备UP，但此时，但由于CP故障，备UP不会自动升为主UP，导致两个UP的状态都为备状态。可能导致用户流量无法处理。
以上仅为出现两个UP的状态都为备状态的一个示例，在相关的方案中，可能还会出现两 个UP的状态都为主状态的情况，不再一一举例。
以上，简单介绍了本申请实施例的相关技术，以下，对本申请的方法实施例进行示例性介绍。
参见图2a，图2a是本申请实施例提供的一种备份状态确定方法的流程图，包括如下步骤：
S205：第一设备生成第一报文，第一报文包括第一条件，第一条件包括第一设备的CUSP状态。
其中，第一设备与第二设备互为备份。第一设备可以为主UP，第二设备可以为备UP，或第一设备为备UP，第二设备为主UP，本申请不做具体限定。
第一设备可以在生成的第一报文中，携带第一设备的CUSP状态。如上所述，第一设备的CUSP状态即为CUSP的故障状态。其对应CUSP通道故障和/或CP故障。
在一个示例中，第一报文中携带的第一设备的CUSP状态为：工作(UP)，表明其CUSP通道和连接的CP均无故障。
在另一个示例中，第一报文中携带的第一设备的CUPS状态为:宕(down)，表明其CUSP通道和/或连接的CP故障。
以上，仅为第一条件包括第一设备的CUSP的示例，第一条件包括第一设备的CUSP的示例还可以有其他的形式。如使用0或1标志来表示CUSP的状态等。本申请不做具体限定。
可选的，该第一条件中还包括第一设备的网络侧状态。该网络侧状态表明第一设备与图1所示的连接网络的状态。
在一个示例中，第一报文中携带的第一设备的网络侧状态为：down，表明第一设备到图1所示的连接网络的链路故障或第二设备到该连接网络的某些路由不可达。
在另一个示例中，第一报文中携带的第一设备的网络侧状态为：up，表明第一设备到图1所示的连接网络暂无故障。
以上，仅为第一条件包括第一设备的网络侧状态的示例，第一条件包括第一设备的网络侧状态的示例还可以有其他的形式。如使用0或1标志来表示网络侧状态等。本申请不做具体限定。
在一个示例中，第一设备生成的第一报文的格式如图3所示，该第一报文可以包括如下信息：
备份组ID(可选项)：采用备份组ID标识该报文的范围为第一设备和第二设备所属的备份组。
服务类型(可选项)：可以用于指示第一设备和第二设备之间的备份方式，如热备。
报文长度(可选项)：表明该第一报文的长度。
CUSP状态(必选项)：详见上方解释，在此不再赘述。
网络侧状态(可选项)：详见上方解释，在此不再赘述。
可选的，该第一报文为RBS报文。
可选的，该第一报文可以为其他协议报文，如自定义的消息报文等。
第一设备生成第一报文的方式可以包括如下3种情况：
情况1，第一设备可以定时生成第一报文，如每隔30分钟生成一次第一报文。
情况2：第一设备也可以是因为触发条件才生成第一报文。
该触发条件可以包括第一设备确定其连接故障或第一设备收到第二设备发送的第二报文。即，情况2包括如下情况2.1或情况2.2两种情况。
情况2.1，在一个示例中，在第一设备生成第一报文之前，第一设备确定其连接故障，响应于该连接故障，第一设备生成该第一报文。
第一设备可以通过监测、或告警等方式确定连接故障。第一设备确定其连接故障包括，第一设备确定其CUSP故障和/或网络侧故障。响应于连接故障，第一设备生成的第一报文包括第一条件，第一条件包括CUSP状态。
当第一设备确定其CUSP故障时，第一设备生成的第一条件可以仅包括该CUSP状态。在一个示例中，该CUSP状态为down。
当第一设备确定其网络侧故障时，则第一设备生成的第一条件包括CUSP状态和网络侧状态。这一个示例中，该网络侧状态为down。
情况2.2，触发条件包括第一设备收到第二设备发送的第二报文。如图2b所示，图2c所示的备份状态确定方法还可以包括步骤：S201～S204：
S201：第二设备确定连接故障。
第二设备确定连接故障的方式与第一设备确定连接故障的方式类似，详细参见上方，本申请不再赘述。
S202：响应于连接故障，第二设备生成第二报文，第二报文包括第二条件，第二条件包括第二设备的CUSP状态。
当第二设备确定其CUSP故障时，第二设备生成的第一条件可以仅包括该CUSP状态。在一个示例中，该CUSP状态为down。
当第二设备确定其网络侧故障时，则第二设备生成的第一条件包括CUSP状态和网络侧状态。这一个示例中，该网络侧状态为down。
第二设备生成的第二报文的详细信息，参见上方第一设备生成第一报文的详细信息，本申请在此不再赘述。
在一个示例中，该第二报文为请求报文。
S203：第二设备向第一设备发送第二报文。
第二设备可以通过第二设备与第一设备之间的交互通道发送第二报文。
在一个示例中，第二设备可以通过RBS通道向第一设备发送第二报文。
S204：第一设备接收第二报文。
第一设备接收第二设备发送的第二报文，第二报文中包括第二条件，第二条件包括第二设备的CUSP状态。
响应于该第二报文，第一设备生成上述第一报文。
在一个示例中，该第一报文也可以称为响应报文。
S210：第一设备向第二设备发送第一报文。
第一设备可以通过与第二设备之间的连接通道向第二设备发送第一报文，
在一个示例中，该连接通道可以为RBS通道。
S215：第二设备接收第一报文。
第二设备接收第一设备发送的第一报文。
可选的，当第一设备生成第一报文的情况为上述情况2.1时，第二设备在接收到第一设备发送的第一报文后，响应于该第一报文，第二设备可以生成第二报文，该第二报文中包括第二条件，第二条件包括第二设备的CUSP状态，第二条件还可以包括第二设备的网络侧状态。第二设备生成的第二报文携带的内容与上述第一设备生成的第一报文的携带的内容类似，本申请在此不再赘述。在第二设备响应于第一报文生成第二报文的情况下，第二设备还向第一设备发送该第二报文。本申请不对第二设备向第一设备发送该第二报文的时间做具体限定，即，第二设备可以在接收到第一报文、生成第二报文后即向第一设备发送第二报文，也可以在下述S220执行之后再发送该第二报文。即，本申请并不限定第二设备向第一设备发送第二报文的时机，其可以在S220之前也可以在S220之后。
S220：第二设备根据第一条件、第二条件和其当前备份状态确定第二设备的备份状态为第一状态。
第二设备从接收到的第一报文中获取到上述第一条件。
第二设备可以根据自身的状态获得第二条件，第二条件包括第二设备的CUSP状态，第二条件还可以包括第二设备的网络侧状态。
第二设备的当前备份状态指第二设备在获得第一状态前的备份状态。
第二设备根据第一条件、第二条件和其当前备份状态确定第二设备的备份状态为第一状态包括以下多种方式：
方式1：第二设备根据第一条件、第二条件和第二设备的当前备份状态进行判断，得到第一状态。
第二设备根据第一条件、第二条件和第二设备的当前备份状态进行判断，得到第一状态，当第一状态与第二设备的备份状态一致时，第二设备不进行特殊处理。当第一状态与第二设备的备份状态不一致时，第二设备执行备份状态的切换，如，从主切换到备，或者，从备切换到主。
当第二设备与管理设备的CUSP故障时，则第二设备主要采用方式1进行主备切换。
在一个示例中，第二设备根据第一条件、第二条件和第二设备的当前备份状态确定第二设备对应的第一状态的方式都可以参见下方表1或表2所示的规则。在本示例中，主UP可为上述第一设备，备UP可为上述第二设备。或主UP为上述第二设备，备UP为上述第一设备。当第二设备为主UP时，其确定的第一状态为下方表1或表2中的第一状态列中的主UP对应的状态。当第二设备为备UP时，其确定的第一状态为下方表1或表2中的第一状态列中的备UP对应的状态。
第一条件包括第一设备的网络侧状态，第二条件包括第二设备的网络侧状态时，第一状态的确定规则可如表1所示。
表1
Figure PCTCN2021097531-appb-000001
Figure PCTCN2021097531-appb-000002
当第一条件不包括第一设备的网络侧状态，或第二条件不包括第二设备的网络侧状态时，第一状态的确定规则可如表2所示。
表2
Figure PCTCN2021097531-appb-000003
方式2：第二设备将第一条件、第二条件发送给管理设备。下面结合图2c对方式2进行介绍。图2a所示的备份状态确定方法还可以包括图2c中的步骤，图2c包括如下步骤：
S2201：第二设备向管理设备发送第一消息，第一消息包括上述第一条件和第二条件。
可选的，第一消息还包括第二设备的当前备份状态。
第二设备可以通过与管理设备之间的管理通道发送第一消息。
在一个示例中，当第一设备为定时向第二设备发送第一报文时，则第二设备可以在仅当接收到的第一报文中包括的第一条件的内容有变化，或者第二设备本身的状态有变化时再向管理设备发送该第一消息。
在另一个示例中，当第二设备是因连接故障获得的第一报文时(包括第一设备连接故障和/或第二设备连接故障)，则第二设备可以在获得第一报文后，则向管理设备发送该第一消 息。
在一个示例中，第二设备向管理设备发送的第一消息携带的信息可以具体包括如下信息：
备份组ID、服务类型、主UP CUSP状态、主UP网络侧状态、备UP CUSP状态、备UP网络侧状态。其中，备份组ID和服务类型的作用可以参考上述第一设备生成第一报文除的解释，在此不再赘述。
S2203：管理设备根据第一条件、第二条件和第二设备的当前备份状态确定第二设备的备份状态对应第一状态。
可选的，该第一消息中还包括第二设备的当前备份状态。
可选的，管理设备根据其他信息，如其存储有的第二设备的信息，包括第二设备的当前备份状态。
管理设备根据接收到的第一消息，从中获得第一条件和第二条件，并通过第一条件、第二条件和第二设备的当前备份状态确定第二设备的备份状态对应的第一状态。
管理设备通过第一条件和第二条件确定第二设备的备份状态对应第一状态的方式与上述第二设备通过第一条件和第二条件确定第一状态的确定规则类似，详情请见上方描述，在此不再赘述。S2204：管理设备向第二设备发送第二消息，该第二消息用于指示第二设备的备份状态对应第一状态。
管理设备确认第二设备的备份状态对应的第一状态后，可以向第二设备发送第二消息。
可选的，管理设备向第二设备发送的第二消息可以有多种情况：
情况1、当该第一状态与第二设备的备份状态一致时，该第二消息可以仅向第二设备表示，已接收到第二设备发送的第一消息。即，该第二消息指示第二设备可保持当前的备份状态。
情况2、当该第一状态与第二设备的备份状态不一致时，管理设备可以直接向第二设备发送一个指示第二设备切换为第一状态的指示。如，该二消息指示该第二设备的备份状态切换为主状态，或切换为备状态。
情况3、第二消息中包括该第一状态。
S2205：第二设备根据第二消息确定第二设备的备份状态为第一状态。
第二设备收到第二消息后，根据该第二消息确定其备份状态为第一状态。对应上方的情况1，第二设备不需要进行备份状态切换。对应于上方的情况2，第二设备执行第二消息的指示，进行主备状态切换，将其备份状态切换为第一状态。对应于上方的情况3，第二设备在接收到第二消息后，获得第一状态，根据第一状态进行判断，如果该第一状态与当前备份状态一致，则不执行备份状态切换，如果第一状态与当前备份状态不一致，则执行备份状态切换。
以上介绍了本申请实施例的方法，以下介绍本申请实施例的装置。以下介绍的装置具有上述方法中第一网络设备的任意功能。
图4是本申请实施例提供的一种装置400的结构示意图，如图4所示，该装置400包括接收单元401，处理单元402，可选的，该装置还包括发送单元403。上述接收单元，可用于实现上述方法实施例中的接收第一报文相关的方法，处理单元402可用于实现上述方法实施例中的确定第一状态相关的方法，发送单元403，可用于实现上述方法实施例中的发送第二报文或发送 第一报文的相关方法。
该装置400可对应于上述方法实施例中的第一设备或第二设备。装置400中的各模块和上述其他操作和/或功能分别为了实现方法实施例中的第一设备或第二设备所实施的各种步骤和方法，具体细节可参见上述方法实施例，为了简洁，在此不再赘述。
装置400在实现上述备份状态确定方法时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置400的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。另外，上述实施例提供的装置400与上述方法实施例属于同一构思，其具体实现过程详见上方方法实施例，这里不再赘述。
图5是本申请实施例提供的一种装置500的结构示意图，如图5所示，该装置500包括接收单元501，处理单元502，和发送单元503。上述接收单元，可用于实现上述方法实施例中管理设备相关的接收第一消息相关的方法，处理单元402可用于实现上述方法实施例中的管理设备确定第一状态相关的方法，发送单元403，可用于实现上述方法实施例中管理设备的发送第二消息的相关方法。
该装置500可对应于上述方法实施例中的管理设备。装置500中的各模块和上述其他操作和/或功能分别为了实现方法实施例中的管理设备所实施的各种步骤和方法，具体细节可参见上述方法实施例，为了简洁，在此不再赘述。
装置500在实现上述备份状态确定方法时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置500的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。另外，上述实施例提供的装置500与上述方法实施例属于同一构思，其具体实现过程详见上方方法实施例，这里不再赘述。
与本申请提供的方法实施例以及虚拟装置实施例相对应，本申请实施例还提供了一种装置，下面对装置的硬件结构进行介绍。
下面描述的装置600对应于上述方法实施例中的第一设备，装置600中的各硬件、模块和上述其他操作和/或功能分别为了实现上述方法实施例中的第一设备所实施的各种步骤和方法，关于装置600如何实现备份状态确定方法的详细流程，具体细节可参见上述方法实施例，为了简洁，在此不再赘述。其中，上文方法中的各步骤可以通过装置600处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
装置600对应于上述虚拟装置实施例中的装置400，装置400中的每个功能模块采用装置600的软件实现。换句话说，装置400包括的功能模块为装置600的处理器读取存储器中存储的程序代码后生成的。
参见图6，图6示出了本申请一个示例性实施例提供的装置600的结构示意图，该装置600可以为上述方法实施例中的第一设备或第二设备。该装置600可以由一般性的总线体系结构来实现。
装置600包括至少一个处理器601、通信总线602、存储器603以及至少一个物理通信接口 604。
处理器601可以是一个通用CPU、NP、微处理器、或者可以是一个或多个用于实现本申请方案的集成电路，例如，专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)或其任意组合。
通信总线602用于在上述组件之间传送信息。通信总线602可以分为地址总线、数据总线、控制总线等。为便于表示，图6中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
存储器603可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其它类型的静态存储设备，也可以是随机存取存储器(random access memory，RAM)或者可存储信息和指令的其它类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only Memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其它光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其它磁存储设备，或者是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其它介质，但不限于此。存储器603可以是独立存在，并通过通信总线602与处理器601相连接。存储器603也可以和处理器601集成在一起。
至少一个物理通信接口604使用任何收发器一类的装置，用于与其它设备或通信网络通信。至少一个物理通信接口604包括有线通信接口，还可以包括无线通信接口。其中，有线通信接口例如可以为以太网接口。以太网接口可以是光接口，电接口或其组合。无线通信接口可以为无线局域网(wireless local area networks，WLAN)接口，蜂窝网络通信接口或其组合等。
在具体实现中，作为一种实施例，处理器601可以包括一个或多个CPU，如图6中所示的CPU0和CPU1。
在具体实现中，作为一种实施例，装置600可以包括多个处理器，如图6中所示的处理器601和处理器605。这些处理器中的每一个可以是一个单核处理器，也可以是一个多核处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(如计算机程序指令)的处理核。
在具体实现中，作为一种实施例，装置600还可以包括输出设备(图未视)和输入设备(图未视)。输出设备和处理器601通信，可以以多种方式来显示信息。例如，输出设备可以是液晶显示器(liquid crystal display，LCD)、发光二级管(light emitting diode，LED)显示设备、阴极射线管(cathode ray tube，CRT)显示设备或投影仪(projector)等。输入设备和处理器601通信，可以以多种方式接收用户的输入。例如，输入设备可以是鼠标、键盘、触摸屏设备或传感设备等。
在一些实施例中，存储器603用于存储执行本申请方案的程序代码610，处理器601可以执行存储器603中存储的程序代码610。也即是，装置600可以通过处理器601以及存储器603中的程序代码610，来实现上述方法实施例提供的方法。
本申请实施例的装置600可对应于上述方法实施例中的第一设备或第二设备，并且，该装置600等可以实现上述各个方法实施例中的第一设备或第二设备所具有的功能和/或所实施的各种步骤和方法。为了简洁，在此不再赘述。
参见图7，图7示出了本申请一个示例性实施例提供的装置700的结构示意图，该装置700可以为上述方法实施例中的管理设备。该装置700可以由一般性的总线体系结构来实现。
装置700包括至少一个处理器701、通信总线702、存储器703以及至少一个物理通信接口704。
处理器701可以是一个通用CPU、NP、微处理器、或者可以是一个或多个用于实现本申请方案的集成电路，例如，专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)或其任意组合。
通信总线702用于在上述组件之间传送信息。通信总线702可以分为地址总线、数据总线、控制总线等。为便于表示，图7中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
存储器703可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其它类型的静态存储设备，也可以是随机存取存储器(random access memory，RAM)或者可存储信息和指令的其它类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only Memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其它光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其它磁存储设备，或者是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其它介质，但不限于此。存储器703可以是独立存在，并通过通信总线702与处理器701相连接。存储器703也可以和处理器701集成在一起。
至少一个物理通信接口704使用任何收发器一类的装置，用于与其它设备或通信网络通信。至少一个物理通信接口704包括有线通信接口，还可以包括无线通信接口。其中，有线通信接口例如可以为以太网接口。以太网接口可以是光接口，电接口或其组合。无线通信接口可以为无线局域网(wireless local area networks，WLAN)接口，蜂窝网络通信接口或其组合等。
在具体实现中，作为一种实施例，处理器701可以包括一个或多个CPU，如图7中所示的CPU0和CPU1。
在具体实现中，作为一种实施例，装置700可以包括多个处理器，如图7中所示的处理器701和处理器705。这些处理器中的每一个可以是一个单核处理器，也可以是一个多核处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(如计算机程序指令)的处理核。
在具体实现中，作为一种实施例，装置700还可以包括输出设备(图未视)和输入设备(图未视)。输出设备和处理器701通信，可以以多种方式来显示信息。例如，输出设备可以是液晶显示器(liquid crystal display，LCD)、发光二级管(light emitting diode，LED) 显示设备、阴极射线管(cathode ray tube，CRT)显示设备或投影仪(projector)等。输入设备和处理器701通信，可以以多种方式接收用户的输入。例如，输入设备可以是鼠标、键盘、触摸屏设备或传感设备等。
在一些实施例中，存储器703用于存储执行本申请方案的程序代码710，处理器701可以执行存储器703中存储的程序代码710。也即是，装置700可以通过处理器701以及存储器703中的程序代码710，来实现上述方法实施例提供的方法。
本申请实施例的装置700可对应于上述方法实施例中的管理设备，并且，该装置700等可以实现上述各个方法实施例中的管理设备所具有的功能和/或所实施的各种步骤和方法。为了简洁，在此不再赘述。
在一些可能的实施例中，上述第一设备、第二设备或管理设备可以实现为虚拟化设备。
例如，虚拟化设备可以是运行有用于发送报文功能的程序的虚拟机(英文：Virtual Machine，VM)，虚拟机部署在硬件设备上(例如，物理服务器)。虚拟机指通过软件模拟的具有完整硬件系统功能的、运行在一个完全隔离环境中的完整计算机系统。例如，可以基于通用的物理服务器结合网络功能虚拟化(Network Functions Virtualization，NFV)技术来实现第一设备。第一设备为虚拟主机、虚拟路由器或虚拟交换机。本领域技术人员通过阅读本申请即可结合NFV技术在通用物理服务器上虚拟出具有上述功能的第一设备、第二设备或管理设备。此处不再赘述。
例如，虚拟化设备可以是容器，容器是一种用于提供隔离的虚拟化环境的实体，例如，容器可以是docker容器。可以将容器配置为第一设备、第二设备或管理设备。例如，可以通过对应的镜像来创建出第一设备、第二设备或管理设备，例如可以通过proxy-container(提供代理服务的容器)的镜像，为proxy-container创建2个容器实例，分别是容器实例proxy-container1、容器实例proxy-container2，将容器实例proxy-container1提供为第一设备或第一计算设备，将容器实例proxy-container2提供为第二设备或第二计算设备。采用容器技术实现时，第一设备或第二设备可以利用物理机的内核运行，多个第一设备或第二设备可以共享物理机的操作系统。通过容器技术可以将不同的第一设备或第二设备隔离开来。容器化的第一设备或第二设备可以在虚拟化的环境中运行，例如可以在虚拟机中运行，容器化的第一设备或第二设备可也可以直接在物理机中运行。
例如，虚拟化设备可以是Pod，Pod是Kubernetes(Kubernetes是谷歌开源的一种容器编排引擎，英文简称为K8s)为部署、管理、编排容器化应用的基本单位。Pod可以包括一个或多个容器。同一个Pod中的每个容器通常部署在同一主机上，因此同一个Pod中的每个容器可以通过该主机进行通信，并且可以共享该主机的存储资源和网络资源。可以将Pod配置为第一设备。例如，具体地，可以指令容器即服务(英文全称：container as a service，英文简称：CaaS，是一种基于容器的PaaS服务)来创建Pod，将Pod提供为第一设备、第二设备或管理设备。
当然，第一设备、第二设备或管理设备还可以是其他虚拟化设备，在此不做一一列举。
在一些可能的实施例中，上述第一设备、第二设备或管理设备也可以由通用处理器来实现。例如，该通用处理器的形态可以是一种芯片。具体地，实现第一设备、第二设备或管理设备的通用处理器包括处理电路和与该处理电路内部连接通信的输入接口以及输出接口，该 处理电路用于通过输入接口执行上述各个方法实施例中的丢失时钟报文的步骤。可选地，该通用处理器还可以包括存储介质，该处理电路用于通过存储介质执行上述各个方法实施例中的存储步骤。存储介质可以存储处理电路执行的指令，该处理电路用于执行存储介质存储的指令以执行上述方法实施例。
上述各种产品形态的装置，具有上述方法实施例中第一设备、第二设备或管理设备的任意功能，此处不再赘述。
参见图8，本申请实施例提供了一种网络系统800，所述系统800包括：第一设备801。第一设备801为如装置400或装置600。可选的，该系统还包括第二设备802，第二设备802可以为装置400或装置600，第一设备801和第二设备802用于实现BRAS设备中的UP部分的功能。第一设备801与第二设备802互为备份。可选的，该系统800还包括管理设备803，该管理设备可以为装置500或装置700。该管理设备用于实现BRAS设备中的CP的功能。
本申请实施例提供了一种计算机程序产品，当该计算机程序产品在第一设备上运行时，使得第一设备执行上述方法实施例中的方法。
本申请实施例提供了一种计算机程序产品，当该计算机程序产品在第二设备上运行时，使得第二设备执行上述方法实施例中的方法。
本申请实施例提供了一种计算机程序产品，当该计算机程序产品在管理设备上运行时，使得管理设备执行上述方法实施例中的方法。
本申请提供了一种计算机存储介质，用于储存为上述设备所用的程序、代码或指令，当处理器或硬件设备执行这些程序、代码或指令时可以完成上述第一设备、第二设备或管理设备的功能或步骤。
本申请实施例还提供一种芯片系统，包括：处理器，所述处理器与存储器耦合，所述存储器用于存储程序或指令，当所述程序或指令被所述处理器执行时，使得该芯片系统实现上述任一方法实施例中的方法。
可选地，该芯片系统中的处理器可以为一个或多个。该处理器可以通过硬件实现也可以通过软件实现。当通过硬件实现时，该处理器可以是逻辑电路、集成电路等。当通过软件实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现。
可选地，该芯片系统中的存储器也可以为一个或多个。该存储器可以与处理器集成在一起，也可以和处理器分离设置，本申请并不限定。示例性的，存储器可以是非瞬时性处理器，例如只读存储器ROM，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请对存储器的类型，以及存储器与处理器的设置方式不作具体限定。
示例性的，该芯片系统可以是现场可编程门阵列(field programmable gate array，FPGA)，可以是专用集成芯片(application specific integrated circuit，ASIC)，还可以是系统芯片(system on chip，SoC)，还可以是中央处理器(central processor unit，CPU)，还可以是网络处理器(network processor，NP)，还可以是数字信号处理电路(digital signal processor，DSP)，还可以是微控制器(micro controller unit，MCU)，还可以是可编程控制器(programmable logic device，PLD)或其他集成芯片。
应理解，上述方法实施例中的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
本领域普通技术人员可以意识到，结合本文中所公开的实施例中描述的各方法步骤和单元，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各实施例的步骤及组成。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。本领域普通技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参见前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，该单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口、装置或单元的间接耦合或通信连接，也可以是电的，机械的或其它的形式连接。
该作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本申请实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
该集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分，或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例中方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上描述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到各种等效的修改或替换，这些修改或替换都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。该计算机程序产品包括一个或多个计算机程序指令。在计算机上加载和执行该计算机程序指令时，全部或部分地产生按照本申请实施例中的流程或功能。该计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。该计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，该计算机程序指令可以从一个网站站点、计算机、服务器或数据中心通过有线或无线方式向另一个网站站点、计算机、服务器或数据中心进行传输。该计算机可读存储介质可以是计算机能够存取的任何可用介质或 者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。该可用介质可以是磁性介质(例如软盘、硬盘、磁带)、光介质(例如，数字视频光盘(digital video disc，DVD)、或者半导体介质(例如固态硬盘)等。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，该程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
以上描述仅为本申请的可选实施例，并不用以限制本申请，凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (18)

  1. 一种备份状态确定方法，其特征在于，所述方法包括：
    第一设备接收第二设备发送的第一报文，所述第一报文包括第一条件，所述第一条件包括所述第二设备的控制面和用户面分离协议CUSP状态，所述第一设备与所述第二设备互为备份；
    所述第一设备根据所述第一条件、第二条件和所述第一设备的当前备份状态，确定所述第一设备的备份状态为第一状态，所述第二条件包括所述第一设备的CUSP状态，所述第一状态包括主状态或备状态。
  2. 根据权利要求1所述的方法，其特征在于，所述第一条件还包括所述第二设备的网络侧状态，所述第二条件还包括所述第一设备的网络侧状态。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一设备根据第一条件、第二条件和所述第一设备的当前备份状态，确定所述第一设备的备份状态为第一状态，包括：
    所述第一设备根据所述第一条件、所述第二条件和所述第一设备的当前备份状态，判断所述第一设备的备份状态为所述第一状态。
  4. 根据权利要求1或2所述的方法，其特征在于，所述第一设备根据第一条件、第二条件和所述第一设备的当前备份状态，确定所述第一设备的备份状态为第一状态，包括：
    所述第一设备向管理设备发送第一消息，所述第一消息包括所述第一条件和所述第二条件，所述第一消息用于指示所述管理设备根据所述第一条件、所述第二条件和所述第一设备的当前备份状态确定所述第一状态；
    响应于所述第一消息，所述第一设备接收所述管理设备发送的第二消息；
    所述第一设备根据所述第二消息确定其备份状态为所述第一状态。
  5. 根据权利要求1-4任一项所述的方法，其特征在于，所述方法还包括：
    响应于所述第一报文，所述第一设备向所述第二设备发送第二报文，所述第二报文包括所述第二条件。
  6. 根据权利要求1-4任一项所述的方法，其特征在于，在第一设备接收第二设备发送的第一报文之前，所述方法还包括：
    所述第一设备确定所述第一设备的连接故障；
    响应于所述连接故障，所述第一设备向所述第二设备发送第二报文，所述第二报文包括所述第二条件，所述第一报文为所述第二报文的响应报文。
  7. 一种备份状态确定方法，其特征在于，包括：
    管理设备接收第一设备发送的第一消息，所述第一消息包括第一条件和第二条件，所述第一条件包括第一设备的控制面和用户面分离协议CUSP状态，所述第二条件包括第二设备的CUSP状态，所述第一设备和所述第二设备互为备份；
    所述管理设备根据所述第一条件、第二条件和所述第一设备的当前备份状态，确定所述第一设备的备份状态对应为第一状态，所述第一状态包括主状态或备状态；
    所述管理设备向所述第一设备发送第二消息，所述第二消息用于指示所述第一设备的备份状态对应所述第一状态。
  8. 根据权利要求7所述的方法，其特征在于，所述第一条件还包括所述第一设备的网络侧状态，所述第二条件还包括所述第二设备的网络侧状态。
  9. 一种备份装置，其特征在于，包括：
    接收单元，用于接收第二设备发送的第一报文，所述第一报文包括第一条件，所述第一条件包括所述第二设备的控制面和用户面分离协议CUSP状态，所述第二设备与所述装置互为备份；
    处理单元，用于根据所述第一条件、第二条件和所述装置的当前备份状态，确定所述装置的备份状态为第一状态，所述第二条件包括所述装置的CUSP状态，所述第一状态包括主状态或备状态。
  10. 根据权利要求9所述的装置，其特征在于，所述第一条件还包括所述第二设备的网络侧状态，所述第二条件还包括所述装置的网络侧状态。
  11. 根据权利要求9或10所述的装置，其特征在于，
    所述处理单元，用于根据所述第一条件、所述第二条件和所述装置的当前备份状态，判断所述装置的备份状态为所述第一状态。
  12. 根据权利要求9或10所述的装置，其特征在于，包括：发送单元，
    所述发送单元，用于向管理设备发送第一消息，所述第一消息包括所述第一条件和所述第二条件，所述第一消息用于指示所述管理设备根据所述第一条件、所述第二条件和所述第一设备的当前备份状态确定所述第一状态；
    响应于所述第一消息，所述接收单元，还用于接收所述管理设备发送的第二消息；
    所述处理单元，用于根据所述第二消息确定其备份状态为所述第一状态。
  13. 根据权利要求9-12任一项所述的装置，其特征在于，
    响应于所述第一报文，所述发送单元，还用于向所述第二设备发送第二报文，所述第二报文包括所述第二条件。
  14. 根据权利要求9-12任一项所述的装置，其特征在于，
    所述处理单元，还用于确定所述装置连接故障；
    响应于所述连接故障，所述发送单元，还用于向所述第二设备发送第二报文，所述第二报文包括所述第二条件，所述第一报文为所述第二报文的响应报文。
  15. 一种备份装置，其特征在于，包括：
    接收单元，用于接收第一设备发送的第一消息，所述第一消息包括第一条件和第二条件，所述第一条件包括第一设备的控制面和用户面分离协议CUSP状态，所述第二条件包括第二设备的CUSP状态，所述第一设备和所述第二设备互为备份；
    处理单元，用于根据所述第一条件、第二条件和所述第一设备的当前备份状态，确定所述第一设备的备份状态对应为第一状态，所述第一状态包括主状态或备状态；
    发送单元，用于向所述第一设备发送消息，所述消息用于指示所述第一设备的备份状态对应所述第一状态。
  16. 根据权利要求15所述的装置，其特征在于，所述第一条件还包括所述第一设备的网络侧状态，所述第二条件还包括所述第二设备的网络侧状态。
  17. 一种备份系统，其特征在于，包括：
    第一设备，所述第一设备为权利要求9-14中任一项所述的装置。
  18. 根据权利要求17所述的系统，其特征在于，还包括：管理设备，
    所述管理设备为权利要求15或16所述的装置。
PCT/CN2021/097531 2020-05-30 2021-05-31 一种备份状态确定方法、装置及系统 WO2021244500A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010480723.1 2020-05-30
CN202010480723.1A CN113746655B (zh) 2020-05-30 2020-05-30 一种备份状态确定方法、装置及系统

Publications (1)

Publication Number Publication Date
WO2021244500A1 true WO2021244500A1 (zh) 2021-12-09

Family

ID=78727771

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/097531 WO2021244500A1 (zh) 2020-05-30 2021-05-31 一种备份状态确定方法、装置及系统

Country Status (2)

Country Link
CN (1) CN113746655B (zh)
WO (1) WO2021244500A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023131138A1 (zh) * 2022-01-05 2023-07-13 华为技术有限公司 一种数据流的传输方法，光通信系统以及相关装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106685818A (zh) * 2016-12-30 2017-05-17 北京华为数字技术有限公司 报文反馈方法及装置
CN107623593A (zh) * 2017-08-31 2018-01-23 北京华为数字技术有限公司 基于cu分离的双机热备的方法及设备
CN108512703A (zh) * 2018-03-28 2018-09-07 新华三技术有限公司 Bras转控分离的备份方法、装置、设备及机器可读存储介质
US20200145278A1 (en) * 2018-11-07 2020-05-07 Cisco Technology, Inc. Redundancy support for control and user plane separation

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107547317A (zh) * 2016-06-27 2018-01-05 中兴通讯股份有限公司 虚拟化宽带接入服务器的控制方法、装置及通信系统
CN108667575B (zh) * 2017-09-06 2021-04-27 新华三技术有限公司 一种bras转控分离的备份方法和装置
CN109873761A (zh) * 2017-12-04 2019-06-11 中兴通讯股份有限公司 一种热备环境中切换主备设备的方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106685818A (zh) * 2016-12-30 2017-05-17 北京华为数字技术有限公司 报文反馈方法及装置
CN107623593A (zh) * 2017-08-31 2018-01-23 北京华为数字技术有限公司 基于cu分离的双机热备的方法及设备
CN108512703A (zh) * 2018-03-28 2018-09-07 新华三技术有限公司 Bras转控分离的备份方法、装置、设备及机器可读存储介质
US20200145278A1 (en) * 2018-11-07 2020-05-07 Cisco Technology, Inc. Redundancy support for control and user plane separation

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023131138A1 (zh) * 2022-01-05 2023-07-13 华为技术有限公司 一种数据流的传输方法，光通信系统以及相关装置

Also Published As

Publication number Publication date
CN113746655B (zh) 2022-10-04
CN113746655A (zh) 2021-12-03

Similar Documents

Publication Publication Date Title
US10205653B2 (en) Fabric discovery for a cluster of nodes
US8346997B2 (en) Use of peripheral component interconnect input/output virtualization devices to create redundant configurations
US7969989B2 (en) High performance ethernet networking utilizing existing fibre channel arbitrated loop HBA technology
US8831029B2 (en) Flexibly integrating endpoint logic into varied platforms
CN116501681B (zh) Cxl数据传输板卡及控制数据传输的方法
CN111147274B (zh) 为集群解决方案创建高度可用的仲裁集的系统和方法
WO2012097588A1 (zh) 数据存储方法、设备和系统
KR20110124333A (ko) 가상 네트워크 환경에서 복사 회피
WO2021244500A1 (zh) 一种备份状态确定方法、装置及系统
WO2021012169A1 (zh) 一种提高存储系统可靠性的方法和相关装置
WO2018107433A1 (zh) 信息处理方法和装置
WO2022052496A1 (zh) 地址预留的方法、网络设备和系统
WO2022012489A1 (zh) 一种能力通告方法及相关设备
US20220417112A1 (en) Network operation method, apparatus, and device and storage medium
CN111488247B (zh) 一种管控节点多次容错的高可用方法及设备
US20230161726A1 (en) Multiprocessor System and Method for Configuring Multiprocessor System
CN116010307A (zh) 服务器资源分配系统、方法和装置
WO2024067051A1 (zh) 一种多az仲裁系统及方法
WO2023029485A1 (zh) 数据处理方法、装置、计算机设备及计算机可读存储介质
WO2023207235A1 (zh) 用户面管理方法、控制面设备及用户面设备
WO2022022313A1 (zh) 传输路由信息的方法、装置和通信系统
US11386026B1 (en) Shell PCIe bridge and shared-link-interface services in a PCIe system
TWI774464B (zh) 經擴展可用性計算系統
CN117519908B (zh) 一种虚拟机热迁移方法、计算机设备及介质
US11190394B2 (en) Soft-failure protection for multicast communications

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21816694

Country of ref document: EP

Kind code of ref document: A1