[go: up one dir, main page]

WO2012149785A1 - 一种主备模式下的单板运行方法及系统 - Google Patents

一种主备模式下的单板运行方法及系统 Download PDF

Info

Publication number
WO2012149785A1
WO2012149785A1 PCT/CN2011/080413 CN2011080413W WO2012149785A1 WO 2012149785 A1 WO2012149785 A1 WO 2012149785A1 CN 2011080413 W CN2011080413 W CN 2011080413W WO 2012149785 A1 WO2012149785 A1 WO 2012149785A1
Authority
WO
WIPO (PCT)
Prior art keywords
board
resource block
standby
external
communicate
Prior art date
Application number
PCT/CN2011/080413
Other languages
English (en)
French (fr)
Inventor
申纪伟
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2011/080413 priority Critical patent/WO2012149785A1/zh
Priority to CN201180002282.3A priority patent/CN102388570B/zh
Publication of WO2012149785A1 publication Critical patent/WO2012149785A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
    • G06F11/2035—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant without idle spare hardware

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and system for operating a single board in an active/standby mode.
  • a redundant standby board is added to the main board to ensure that the current service is continuously executed by the redundant standby board when the board is faulty.
  • the redundancy mode used by the board in the prior art generally includes the working mode of the N+1 resource pool or the 1+1 active/standby mode.
  • the working mode of the N+1 resource pool that is, the operation of the N-block board, and the backup of one board.
  • the backup board takes over the work of the board.
  • multiple boards are backed up to one board.
  • the backup board cannot completely back up all call data. Only important data, such as base stations and cells, can be selected. Therefore, when a board fails, the average user will drop the call.
  • each board is configured with a single board for backup.
  • the main board works only.
  • the standby board only performs backup of the main board.
  • the standby board is upgraded to the main board through the switchover.
  • the IP address is switched to the IP address of the main board to take over the work of the original main board.
  • the original user can ensure that the original user does not drop the call, and the reliability is high.
  • the standby board is always idle, which is equivalent to only one single board for two boards. Board thing, this mode has high hardware redundancy and poor performance.
  • the embodiment of the invention provides a method and a system for operating a single board in an active/standby mode, which can reduce hardware redundancy and improve hardware performance under high reliability.
  • a method for operating a board in an active/standby mode where the resource is divided into at least two parts of the resource blocks that can be independently operated, and the resource blocks are allocated to the main board and the standby board.
  • the method includes:
  • the main board runs the first resource block to communicate with the external board, and the standby board runs the second resource block to communicate with the external board, where the first resource block and the second resource are Different blocks;
  • the standby board detects that the main board is faulty, the second resource block is run by the standby board, and the backup of the first resource block stored on the standby board is performed. Communicate with the external board.
  • a single board including:
  • a communication unit configured to run the second resource block to communicate with the external board, where the main board of the board runs the first resource block to communicate with the external board, the first resource block and the first resource block
  • the second resource block is different, and the first resource block and the second resource block are independently operable resource blocks obtained by dividing resources;
  • a fault processing unit configured to: when detecting that the main board is faulty, running the second resource block, and backing up the first resource block stored on the board, and the external board Communicate.
  • a board running system in an active/standby mode including a main board and a standby board, the resources of the system are divided into at least two parts of resource blocks that can be independently operated, and the resource blocks are allocated to the main list.
  • Board and the standby board
  • the main board is configured to run the first resource block to communicate with the external board;
  • the standby board is configured to run the second resource block to communicate with the external board, where the second resource block is different from the first resource block; when detecting that the main board is faulty, running The second resource block, and the backup of the first resource block stored on the standby board, communicate with the external board.
  • the resources are divided and run on the active and standby boards respectively, so that the active and standby boards are simultaneously involved in the running of the resources to communicate with the external boards, thereby avoiding the main board in the active/standby mode of the prior art.
  • the standby board When the standby board is idle, the CPU of the active and standby boards participates in the operation at the same time. This greatly reduces the redundancy of the hardware, fully utilizes the hardware resources, and improves the hardware performance.
  • the processing capability in this mode It is twice the processing power of the prior art method.
  • the other board takes over the resources on the faulty board to avoid interruption of service communication and ensure high reliability of the system.
  • FIG. 1 is a flowchart of a method for operating a single board in an active/standby mode according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a method for operating a single board in an active/standby mode according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of communication between an active and standby single board and an external single board in the embodiment shown in FIG. 2;
  • FIG. 4 is a flowchart of another method for operating a board in an active/standby mode according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of communication between an active and standby single board and an external single board in the embodiment shown in FIG. 4;
  • FIG. 6 is a schematic structural view of a single board according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural view of another single board according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural view of another single board according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a single board operating system in an active/standby mode according to an embodiment of the present invention.
  • FIG. 1 is a flowchart of a method for operating a board in an active/standby mode according to an embodiment of the present invention.
  • the method can include:
  • Step 101 The resource is divided into at least two parts and can be independently operated, and the resource blocks are allocated to the main board and the standby board.
  • the resources on the board are not divided, but are run on the main board or on the standby board.
  • the resources are first divided, and the standard of the division is Each resource block that is divided can be run independently. When running a resource block, there is no need to refer to other resource blocks.
  • the process of dividing the resource may be divided by a third party other than the main board and the standby board, or may be divided by one of the two.
  • the resource block is allocated by the third party or the two. Specifically, the at least two different resource blocks that are allocated are allocated to the main board and the standby board. The resource blocks are different, and the resources can be equal or different. You can also allocate all the resource blocks on the main board and the standby board. For example, all the resource blocks are backed up by the number of boards, and then allocated. , All resource blocks are stored on each board.
  • the step of dividing the resource block can be performed in advance, and it is not necessary to perform the partitioning once each time the board is run.
  • Step 102 The primary board runs the first resource block to communicate with the external board, and the standby board runs the second resource block to communicate with the external board.
  • resource blocks are allocated to the main board and the standby board, some of the resource blocks are run by the main board, which is recorded as the first resource block, and the standby board runs another part of the resource block, which is recorded as the second resource block.
  • a resource block is different from the second resource block.
  • the common communication module can communicate with the external boards.
  • the standby board communicates with the agent through the main board.
  • the module communicates with the external board.
  • the specific communication method is not limited here.
  • Step 103 When the standby board detects that the main board is faulty, the standby board runs the second resource block and the backup of the first resource block stored on the standby board to communicate with the external board.
  • the standby board can detect the running status of the main board through the software handshake between the active and standby boards. When the main board is faulty, the standby board runs the original resource block and takes over. The service on the main board, that is, the backup of the first resource block on the standby board, communicates with other external boards.
  • the backup of the first resource block may be temporarily stored on the standby board when the resource block is allocated, or may be temporarily backed up by the main board to the standby board before the fault occurs or the fault occurs.
  • the method when the faulty board is restored, the method may be switched back to step 102, that is, when the main board is restored, the first resource block is still run by the main board to communicate with the external board.
  • the standby board runs the second resource block to communicate with the external board.
  • the main board and the standby board are relatively different, and are not specifically referred to as a single board, that is, in the foregoing method steps, the "main board” and the “prepare board” are swapped, The same can be achieved and is within the scope of the invention.
  • “First” and “Second” are also only distinguishing between different resource blocks, not special features.
  • the resources are divided and run on the active and standby boards respectively, so that the active and standby boards are simultaneously involved in the running of the resources to communicate with the external boards, thereby avoiding the main board in the active/standby mode of the prior art. If the standby board is idle, the CPU of the active and standby boards participates in the method.
  • the operation greatly reduces the redundancy of the hardware, makes full use of the hardware resources, and improves the hardware performance.
  • the processing capability in this mode is twice that of the prior art methods.
  • the other board takes over the resources on the faulty board, which avoids the interruption of service communication and ensures high reliability of the system.
  • FIG. 2 is a flowchart of another method for operating a board in an active/standby mode according to an embodiment of the present invention.
  • the method can include:
  • the resource M is divided into two parts, the resource blocks M1 and M2, which are independently operable, and the resource blocks are allocated to the main board and the standby board.
  • the resource block M is divided into two resource blocks that can be independently operated, and the first resource block M1 and the second resource block M2 are taken as an example for description.
  • the specific resource partitioning method is to extract the global variables in each resource block and store them in a unified structure called an environment control block.
  • Each board uses a corresponding independent resource block through a different environment control block pointer.
  • the first resource block M1 and the second resource block M2 are backed up, and the backup M2 of the first resource block M1 and the second resource block M2 is allocated to the main board, and the backup of the first resource block M1 is performed.
  • the second resource block M2 is allocated to the standby board.
  • Step 202 The primary board runs the first resource block M1 to communicate with the external board, and the standby board runs the second resource block M2, and communicates with the external board through the proxy communication module on the main board.
  • the first resource block is run by the main board.
  • the standby board runs the second resource block M2, and the two resource blocks are different.
  • the main board communicates with the external board through the IP address IP1 of the main board through the communication module of the main board.
  • the standby board passes the proxy communication module on the main board and uses the main board.
  • the IP address IP1 communicates with the external board. As shown in Figure 3, the mode of the main board proxy communication does not require other boards to be perceived, and the impact is small.
  • the resources of the resource blocks running on the standby board and the main board may be different, for example, the resources of the second resource block M2 running on the standby board are larger than the main
  • the resource amount of the first resource block M1 that the board runs, such as M2: Ml is 6:4.
  • Step 203 When the standby board detects that the main board is faulty, the standby resource board runs the second resource block. M2, and the backup M1 of the first resource block, communicates with the external board by using the IP address IP 1 of the main board.
  • the standby board detects the running status of the main board through the software handshake between the active and standby boards. When the main board is faulty, the standby board takes over the service on the main board.
  • the backup port of the first resource block stored on the board communicates with the external board.
  • the standby board can simultaneously run the backup M1' and the second resource block M2 of the first resource block, and switch the IP address IP1 of the main board to its own IP address, that is, the IP address of the main board. IP1, communicates with external boards, and sends ARP (Address Resolution Protocol) messages to other external boards to update ARP entries of other external boards.
  • ARP Address Resolution Protocol
  • the service may exceed the CPU load of the standby board.
  • the flow control can be started.
  • the flow control can include sharing the call to other boards or rejecting the flow.
  • Step 204 When the standby board detects the recovery of the main board, the standby board runs the second resource block M2 to communicate with the external board, and communicates with the external board through the proxy communication module on the main board; The primary board resumes running the first resource block M1 to communicate with the external board.
  • the backup board detects the recovery of the main board, you can switch the running status of the active and standby boards back to the corresponding state in step 202. That is, the standby board runs the second resource block M2 and passes the proxy communication module on the main board. The main board resumes running the first resource block M1 to communicate with the external board.
  • the backup board is faulty in step 203, the first resource block M1 and the backup M2 of the second resource block are directly operated by the main board, and the IP address IP1 of the main board is used. After communicating with the external board, after the standby board is restored, switch back to the state of step 202.
  • the resources are divided and run on the main board and the standby board respectively, so that the active and standby boards simultaneously participate in the running resources to communicate with the external boards, thereby greatly reducing the redundancy of the hardware and making full use of the hardware.
  • the resources are used to improve the performance of the system.
  • another board takes over the resources on the faulty board to avoid interruption of service communication and ensure high reliability of the system.
  • FIG. 4 is a flowchart of another method for operating a board in an active/standby mode according to an embodiment of the present invention.
  • the method can include: Step 401:
  • the resource M is divided into two parts, the resource blocks M1 and M2, which are independently operable, and the resource blocks are allocated to the main board and the standby board.
  • the first resource block M1 and the second resource block M2 divided by the resource M are taken as an example for description.
  • the resource partitioning process and the resource block allocation process are similar to the foregoing step 201, and are not described herein again.
  • Step 402 The main board runs the first resource block M1, and communicates with the external board through the IP address IP1 of the main board.
  • the standby board runs the second resource block M2 and passes the IP address IP2 of the standby board. Communicate with external boards.
  • the first resource block M1 is run by the main board
  • the second resource block M2 is run by the standby board.
  • the two resource blocks are different.
  • the main board passes its own communication module and uses the IP address of the main board itself.
  • the IP1 communicates with the external board.
  • the standby board communicates with the external board through its own communication module, IP address IP2 of the standby board, as shown in Figure 5.
  • the resources of the resource blocks running on the main board and the standby board can be the same, for example, Ml: M2 is 1:1.
  • Step 403 When the standby board detects that the main board is faulty, the standby board adds the IP address IP1 of the main board and sends an ARP message to the external board.
  • the standby board detects the running status of the main board through the software handshake between the active and standby boards. When the main board is faulty, the standby board needs to take over the services on the main board before the service is replaced. The standby board and the main board communicate with the external board through their own IP addresses. Therefore, the standby board needs to take over the service on the main board and the IP address IP1 of the main board.
  • the standby board can take over the services of the main board and communicate with the external board.
  • Step 404 The standby board runs the second resource block M2, and uses the IP address IP2 of the standby board to communicate with the external board.
  • the standby board runs the backup M1 of the first resource block, and uses the IP address IP1 of the main board. , Communicate with external boards.
  • the standby board After the IP address of the main board is added to the IP address of the main board, the standby board still runs the second resource block M2.
  • the original IP address of the standby board IP2 is used to communicate with the external board.
  • the standby board runs the backup of the first resource block stored on the standby board.
  • the IP address IP1 of the main board is used to communicate with the external board.
  • the service may exceed the CPU load of the standby board.
  • the flow control can be started.
  • the flow control can include the call sharing to other boards, or Reject certain services, etc.
  • Step 405 When the standby board detects that the main board is restored, the standby board runs the second resource block M2 and uses the IP address IP2 of the standby board to communicate with the external board.
  • the standby board When the standby board is restored, the standby board is switched to the status of step 402.
  • the second resource block M2 is used, and the IP address of the standby board is used to communicate with the external board.
  • the service of the main board that is replaced by the standby board is switched back to the main board and executed by the main board.
  • the switching process of the main board can be:
  • the IP address IP1 of the main board is used (the IP1 is added to the standby board in step 403), it is started with the standby IP address IP3.
  • the IP address IP3 of the primary board is switched to the IP address IP1 of the main board, and an ARP message is sent to the external board to restore the ARP entry of the external board to the state before the fault of the main board.
  • the board runs the first resource block M1 and communicates with the external board by using the IP address IP1.
  • step 403 if the backup board is faulty in the step 403, the steps of the main board are performed by the main board directly after the board is restored. The handover process switches back to the state of step 402.
  • the resources are divided and run on the main board and the standby board respectively, so that the active and standby boards simultaneously participate in the running resources to communicate with the external boards, thereby greatly reducing the redundancy of the hardware and making full use of the hardware.
  • the resources are used to improve the performance of the system.
  • another board takes over the resources on the faulty board to avoid interruption of service communication and ensure high reliability of the system.
  • FIG. 6 is a schematic structural diagram of a single board according to an embodiment of the present invention.
  • the board can include:
  • the communication unit 601 is configured to run the second resource block to communicate with an external board, where the single The first resource block of the board is configured to communicate with the external board, where the first resource block is different from the second resource block, and the first resource block and the second resource block are divided.
  • the fault processing unit 602 is configured to: when detecting that the primary board is faulty, run the second resource block, and backup the first resource block stored on the board, and the external ticket The board communicates.
  • the resources are first divided, and the standard of the division is that the divided resource blocks can be independently operated, and when running a certain resource block, there is no need to refer to other resource blocks.
  • resource block allocation is performed, and the dividing process and the allocation process of the resource may be performed by the board or other device.
  • the communication unit 601 can run the second resource block. You can communicate with the external board through the proxy communication module on the main board. You can also communicate with the external board through the communication module of the board.
  • the fault processing unit 602 detects that the main board is faulty, the unit runs the original second resource block and replaces the service on the main board, that is, runs the first resource block stored on the board. Backup, and communicate with other external boards.
  • the board and the main board simultaneously participate in running resources to communicate with the external board through the foregoing unit, thereby greatly reducing hardware redundancy, fully utilizing hardware resources, improving hardware performance, and, at a certain When a board fails, the other board takes over the resources on the faulty board to avoid interruption of service communication and ensure high reliability of the system.
  • FIG. 7 is a schematic structural diagram of another single board according to an embodiment of the present invention.
  • the board may include a first recovery unit 703 in addition to the communication unit 701 and the fault processing unit 702.
  • the communication unit 701 is specifically configured to run the second resource block, and communicate with the external board through the proxy communication module on the main board.
  • the fault processing unit 702 is specifically configured to: when detecting that the primary board is faulty, run the second resource block, and back a backup of the first resource block stored on the board, use the primary The IP address of the board communicates with the external board.
  • the first recovery unit 703 is configured to: when detecting that the primary board recovers, run the second resource block and The external board communicates with the external board through the proxy communication module on the main board. The main board resumes running the first resource block to communicate with the external board.
  • the board and the main board simultaneously participate in running resources to communicate with the external board through the foregoing unit, thereby greatly reducing hardware redundancy, fully utilizing hardware resources, improving hardware performance, and, at a certain When a board fails, the other board takes over the resources on the faulty board to avoid interruption of service communication and ensure high reliability of the system.
  • FIG. 8 is a schematic structural diagram of another single board according to an embodiment of the present invention.
  • the board may include a second recovery unit 803 in addition to the communication unit 801 and the fault processing unit 802.
  • the communication unit 801 is specifically configured to run the second resource block, and communicate with the external board by using an IP address of the board.
  • the fault handling unit 802 can further include:
  • the message sending subunit 8021 is configured to: when detecting that the main board is faulty, increase an IP address of the main board, and send an ARP message to the external board;
  • the fault processing sub-unit 8022 is configured to run a second resource block, communicate with the external board by using an IP address of the board, and run a backup of the first resource block stored on the board. Communicate with the external board by using the IP address of the main board.
  • the second recovery unit 803 is configured to: when detecting the recovery of the main board, run the second resource block, and use the IP address of the board to communicate with the external board.
  • the primary board is detected to use the IP address of the primary board, it is started with a standby IP address, and when the first resource block is resumed, the standby IP address is switched to the primary An IP address of the board, and sends an ARP message to the external board to communicate with the external board.
  • the board and the main board simultaneously participate in running resources to communicate with the external board through the foregoing unit, thereby greatly reducing hardware redundancy, fully utilizing hardware resources, improving hardware performance, and, at a certain When a board fails, the other board takes over the resources on the faulty board to avoid interruption of service communication and ensure high reliability of the system.
  • FIG. 9 is a schematic structural diagram of a single board operating system in an active/standby mode according to an embodiment of the present invention.
  • the system includes a main board 901 and a standby board 902.
  • the resources of the system are divided into at least two parts of the resource blocks that can be independently operated, and the resource blocks are allocated to the main board 901 and the standby board 902.
  • the main board 901 is configured to run the first resource block to communicate with the external board
  • the standby board 902 is configured to run the second resource block to communicate with the external board, where the first resource block and the The second resource block is different; when detecting that the primary board is faulty, running the second resource block, and backing up the first resource block stored on the standby board, and the external The board communicates.
  • the system greatly reduces the redundancy of the hardware, fully utilizes the hardware resources, and improves the hardware performance.
  • the other board takes over the faulty board.
  • the resources avoid the interruption of business communication and ensure the high reliability of the system.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Hardware Redundancy (AREA)

Description

一种主备模式下的单板运行方法及系统
技术领域
本发明涉及通信技术领域，尤其涉及一种主备模式下的单板运行方法及系 统。
背景技术
电信系统中， 为了提高系统的可靠性， 通常会对主要单板增加冗余备板， 以保证当单板发生故障时， 可以及时由冗余备板继续执行当前业务， 减小对用 户的影响。
现有技术中对单板所釆用的冗余方式一般包括 N+1 资源池的工作模式或 1+1主备模式。
其中， N+1资源池的工作模式， 即 N块单板工作， 1块单板进行备份。 当 N块单板中任一单板故障时， 备份单板接替该单板工作。 然而， 该工作模式中 多块单板向一块单板备份，在相同的内存情况下，备份单板不能完全备份所有 的呼叫数据。 只能选择重要的数据， 如基站， 小区等信息， 所以发生单板故障 时， 一般用户都会掉话。
对于 1+1主备模式， 即每一个单板都配有一块单板做备份， 主单板工作， 备单板只做主单板的备份。 当主单板故障时， 备单板通过倒换升为主单板， 将
IP地址切换为主单板 IP地址， 接替原来主单板的工作。 该模式下虽然可以艮 好的保障原有用户不掉话， 可靠性高， 但是在主单板不出现故障时， 备单板始 终处于闲置状态，相当于 2块单板只做了 1块单板的事情，该模式硬件冗余度 高， 性能差。
发明内容
本发明实施例提供一种主备模式下的单板运行方法及系统，能够降低硬件 的冗余度， 在高可靠性的情况下， 提高硬件性能。
为了解决上述技术问题， 本发明实施例的技术方案如下：
一种主备模式下的单板运行方法 ,将资源划分为至少两部分可独立运行的 资源块， 并将所述资源块分配至主单板及其备单板上， 所述方法包括：
所述主单板运行第一资源块与外部单板进行通信，所述备单板运行第二资 源块与所述外部单板进行通信，其中，所述第一资源块与所述第二资源块不同； 当所述备单板检测到所述主单板出现故障时，由所述备单板运行所述第二 资源块， 以及在所述备单板上存储的所述第一资源块的备份， 与所述外部单板 进行通信。
一种单板， 包括：
通信单元， 用于运行第二资源块与外部单板进行通信， 其中， 所述单板的 主单板运行第一资源块与所述外部单板进行通信，所述第一资源块与所述第二 资源块不同，且所述第一资源块与所述第二资源块为划分资源获得的可独立运 行的资源块；
故障处理单元， 用于当检测到所述主单板出现故障时，运行所述第二资源 块， 以及在所述单板上存储的所述第一资源块的备份， 与所述外部单板进行通 信。
一种主备模式下的单板运行系统， 包括主单板及其备单板， 所述系统的资 源划分为至少两部分可独立运行的资源块，所述资源块被分配至所述主单板及 所述备单板上，
所述主单板， 用于运行第一资源块与所述外部单板进行通信；
所述备单板， 用于运行第二资源块与外部单板进行通信， 其中， 所述第二 资源块与所述第一资源块不同； 当检测到所述主单板出现故障时，运行所述第 二资源块， 以及在所述备单板上存储的所述第一资源块的备份， 与所述外部单 板进行通信。
本发明实施例通过将资源进行划分， 并分别在主、备单板上运行， 使得主 备单板同时参与运行资源与外部单板进行通信，避免了现有技术的主备模式下 主单板运行， 备单板闲置的情况， 该实施例方法中主备单板的 CPU同时参与 运行， 大大降低了硬件的冗余度， 充分利用了硬件资源， 提高了硬件性能， 该 方式下的处理能力是现有技术方法处理能力的 2倍。 而且，在某一单板出现故 障时， 由另一单板接替运行故障单板上的资源， 避免了业务通信的中断， 保证 了系统的高可靠性。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施 例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地， 下面描述 中的附图仅仅是本发明的一些实施例， 对于本领域普通技术人员来讲，在不付 出创造性劳动性的前提下， 还可以根据这些附图获得其他的附图。
图 1是本发明实施例一种主备模式下的单板运行方法流程图；
图 2是本发明实施例另一种主备模式下的单板运行方法流程图；
图 3是图 2所示实施例中主备单板与外部单板通信的示意图；
图 4是本发明实施例另一种主备模式下的单板运行方法流程图；
图 5是图 4所示实施例中主备单板与外部单板通信的示意图；
图 6是本发明实施例一种单板的结构示意图；
图 7是本发明实施例另一种单板的结构示意图；
图 8是本发明实施例另一种单板的结构示意图；
图 9是本发明实施例一种主备模式下的单板运行系统结构示意图。
具体实施方式
下面将结合本发明实施例中的附图 ,对本发明实施例中的技术方案进行清 楚、 完整地描述， 显然， 所描述的实施例仅仅是本发明一部分实施例， 而不是 全部的实施例。基于本发明中的实施例， 本领域普通技术人员在没有做出创造 性劳动前提下所获得的所有其他实施例， 都属于本发明保护的范围。
参见图 1 , 为本发明实施例一种主备模式下的单板运行方法流程图。
该方法可以包括：
步骤 101 , 将资源划分为至少两部分可独立运行的资源块， 并将资源块分 配至主单板及其备单板上。
在现有技术中单板上的资源并不进行划分， 而是要么在主单板运行，要么 在备单板运行， 在本发明实施例中， 首先将资源进行划分， 其划分的标准是所 划分出的各资源块可以独立运行，在运行某一资源块时，无需参看其它资源块。
该资源的划分过程可以由主单板和备单板之外的第三方划分，也可以是由 两者之一进行划分。
在划分完成后， 由第三方或两者之一进行资源块的分配， 具体的， 可以将 划分出的至少两部分不同的资源块分别分配在主单板和备单板上，各单板上的 资源块不同， 其资源量可以相等， 也可以不等； 也还可以在主单板和备单板上 分配所有的资源块， 例如， 将所有的资源块按单板数量进行备份， 然后分配， 使得每个单板上都存储有所有的资源块。
该资源块划分的步骤可以预先执行， 无需在每次单板运行时，都执行一次 划分。
步骤 102, 主单板运行第一资源块与外部单板进行通信， 备单板运行第二 资源块与外部单板进行通信。
在将资源块分配至主单板和备单板后， 由主单板运行其中的部分资源块， 记为第一资源块， 备单板运行另一部分资源块， 记为第二资源块， 第一资源块 与第二资源块不同。
主备单板在运行各自的资源块时， 可以分别与外部单板进行业务通信，也 可以是由一公共的通信模块与外部单板进行通信，例如备单板通过主单板上的 代理通信模块与外部单板进行通信等， 此处对于具体的通信方式不作限定。
步骤 103 , 当备单板检测到主单板出现故障时，由备单板运行第二资源块， 以及在备单板上存储的第一资源块的备份， 与外部单板进行通信。
备单板可以通过主备单板之间的软件握手信号对主单板的运行情况进行 检测， 当获知主单板出现故障时， 由备单板在运行原第二资源块的同时， 接替 运行主单板上的业务，也即运行备单板上该第一资源块的备份， 与外部其它单 板进行业务通信。
其中， 该第一资源块的备份可以是预先在资源块分配时存储在备单板上 的， 也可以是出现故障时或出现故障之前， 由主单板临时备份至备单板上的。
在另一实施例中， 当故障单板恢复使用时， 可以切换回步骤 102的方式， 也即当主单板恢复时， 仍由主单板运行第一资源块， 与外部单板进行通信， 由 备单板运行第二资源块， 与外部单板进行通信。
在本发明实施例中， 主单板和备单板是相对而言的， 并非特指某一单板， 也即上述方法步骤中， "主单板" 和 "备单板" 对换， 也同样可以实现， 且在 本发明的保护范围之内。 "第一"、 "第二" 也仅为区分不同的资源块， 并非特 才 Θ。
本发明实施例通过将资源进行划分， 并分别在主、备单板上运行， 使得主 备单板同时参与运行资源与外部单板进行通信，避免了现有技术的主备模式下 主单板运行， 备单板闲置的情况， 该实施例方法中主备单板的 CPU同时参与 运行， 大大降低了硬件的冗余度， 充分利用了硬件资源， 提高了硬件性能， 该 方式下的处理能力是现有技术方法处理能力的 2倍。 而且，在某一单板出现故 障时， 由另一单板接替运行故障单板上的资源， 避免了业务通信的中断， 保证 了系统的高可靠性。
参见图 2, 为本发明实施例另一种主备模式下的单板运行方法流程图。 该方法可以包括：
步骤 201 , 将资源 M划分为两部分可独立运行的资源块 Ml、 M2, 并将 资源块分配至主单板及其备单板上。
在本实施例中， 以将资源 M划分为两部分可独立运行的资源块， 第一资 源块 Ml、 第二资源块 M2为例进行说明。
具体的资源划分方法是将每个资源块中的全局变量都抽离出来，存放在一 个统一的结构中， 称为环境控制块。每个单板通过不同的环境控制块指针使用 对应的独立的资源块。
在划分完成后， 将第一资源块 Ml、 第二资源块 M2进行备份， 将第一资 源块 Ml、 第二资源块 M2的备份 M2 分配至主单板， 将第一资源块 Ml的备 份 及第二资源块 M2分配至备单板， 虽然主备单板中存储的资源块相同， 但各单板运行的资源块并不相同， 如以下步骤 202。
步骤 202, 主单板运行第一资源块 Ml与外部单板进行通信， 备单板运行 第二资源块 M2, 并通过主单板上的代理通信模块与外部单板进行通信。
在将资源块分配至主单板和备单板后， 由主单板运行其中的第一资源块
Ml , 备单板运行第二资源块 M2, 两资源块不同。
在本实施例中， 主单板通过自身的通信模块， 釆用主单板自身的 IP地址 IP1与外部单板进行通信， 备单板通过主单板上的代理通信模块， 釆用主单板 的 IP地址 IP1与外部单板进行通信， 如图 3所示， 该主单板代理通信的模式 不需要其他单板感知， 影响较小。
基于该代理通信模式， 由于主单板上开销相对变大，备单板和主单板上运 行的资源块的资源量可不相同，例如备单板运行的第二资源块 M2的资源量大 于主单板运行的第一资源块 Ml的资源量， 如 M2: Ml为 6: 4等。
步骤 203 , 当备单板检测到主单板出现故障时， 由备单板运行第二资源块 M2, 以及第一资源块的备份 Ml , 使用主单板的 IP地址 IP 1 , 与外部单板进 行通信。
备单板通过主备单板之间的软件握手信号对主单板的运行情况进行检测， 当获知主单板出现故障时， 由备单板接替主单板上的业务，也即使用备单板上 存储的第一资源块的备份 Μ , 与外部单板进行通信。 该情况下， 备单板即 可同时运行第一资源块的备份 Ml'和第二资源块 M2,将主单板的 IP地址 IP1 切换为自身的 IP地址， 也即使用主单板的 IP地址 IP1 , 与外部单板进行通信， 并向其它外部单板发送 ARP ( Address Resolution Protocol, 地址解析协议） 消息 , 更新其他外部单板的 ARP表项。
由于备单板同时运行第一资源块的备份 Ml 和第二资源块 M2, 可能业务 超过备单板的 CPU负荷， 此时可以启动流控， 流控可以包括分担呼叫到其他 单板， 或者拒绝某些服务等。
步骤 204, 当备单板检测到主单板恢复时， 备单板运行第二资源块 M2与 外部单板进行通信， 并通过主单板上的代理通信模块与外部单板进行通信； 其 中， 主单板恢复运行第一资源块 Ml与外部单板进行通信。
当备单板检测到主单板恢复时， 可以将主备单板的运行状态切换回步骤 202对应的状态， 也即备单板运行第二资源块 M2, 通过主单板上的代理通信 模块与外部单板进行通信，主单板恢复运行第一资源块 Ml与外部单板进行通 信。
在另一实施例中，如果在步骤 203中出现故障的是备单板， 则直接由主单 板运行第一资源块 Ml , 以及第二资源块的备份 M2 , 使用主单板的 IP地址 IP1 , 与外部单板进行通信， 备单板恢复后， 切换回步骤 202的状态。
本发明实施例通过将资源进行划分， 并分别在主、备单板上运行， 使得主 备单板同时参与运行资源与外部单板进行通信， 大大降低了硬件的冗余度， 充 分利用了硬件资源， 提高了硬件性能， 而且， 在某一单板出现故障时， 由另一 单板接替运行故障单板上的资源，避免了业务通信的中断，保证了系统的高可 靠性。
参见图 4, 为本发明实施例另一种主备模式下的单板运行方法流程图。 该方法可以包括： 步骤 401 , 将资源 M划分为两部分可独立运行的资源块 Ml、 M2, 并将 资源块分配至主单板及其备单板上。
本实施例仍以资源 M划分的第一资源块 Ml、第二资源块 M2为例进行说 明。其资源划分过程和资源块的分配过程与前述步骤 201类似，此处不再赘述。
步骤 402 , 主单板运行第一资源块 M 1 , 并通过主单板的 IP地址 IP 1与外 部单板进行通信； 备单板运行第二资源块 M2, 并通过备单板的 IP地址 IP2与 外部单板进行通信。
在将资源块分配至主单板和备单板后， 由主单板运行第一资源块 Ml , 备 单板运行其中的第二资源块 M2, 两资源块不同。
在本实施例中， 主单板通过自身的通信模块， 釆用主单板自身的 IP地址
IP1与外部单板进行通信， 备单板通过自身的通信模块， 釆用备单板自身的 IP 地址 IP2与外部单板进行通信， 如图 5所示。
基于该自主通信模式， 主单板和备单板上运行的资源块的资源量可以相 同， 例如 Ml : M2为 1 : 1等。
步骤 403 , 当备单板检测到主单板出现故障时， 备单板增加主单板的 IP 地址 IP1 , 并向外部单板发送 ARP消息。
备单板通过主备单板之间的软件握手信号对主单板的运行情况进行检测， 当获知主单板出现故障时， 需要由备单板接替主单板上的业务，在接替业务之 前， 由于备单板与主单板各自通过自己的 IP地址与外部单板通信， 所以， 备 单板需要接替主单板上的业务以及主单板的 IP地址 IP1。
备单板需要首先在本地增加主单板的 IP地址 IP1 ,并向其它外部单板发送 ARP消息 , 更新其他外部单板的 ARP表项 , 也即将 ARP表项中地址 IP1对应 的主单板的 MAC地址， 更新为备单板的 MAC地址， 以便于备单板可以接替 主单板的业务， 与外部单板进行通信。
步骤 404, 备单板运行第二资源块 M2, 使用备单板的 IP地址 IP2, 与外 部单板进行通信， 且备单板运行第一资源块的备份 Ml , 使用主单板的 IP地 址 IP1 , 与外部单板进行通信。
在备单板将主单板的 IP地址 IP1增加至本地后， 备单板仍然运行第二资 源块 M2, 使用备单板的原 IP地址 IP2, 与外部单板进行通信， 对于接替的主 单板的业务， 备单板则运行在备单板上存储的第一资源块的备份 Μ , 使用 主单板的 IP地址 IP1 , 与外部单板进行通信。
由于备单板同时运行第二资源块 M2和第一资源块的备份 Ml'，可能业务 超过备单板的 CPU负荷， 此时可以启动流控， 流控可以包括分担呼叫到其他 单板， 或者拒绝某些服务等。
步骤 405, 当备单板检测到主单板恢复时， 备单板运行第二资源块 M2, 使用备单板的 IP地址 IP2, 与外部单板进行通信。
当备单板检测到主单板恢复时， 备单板的运行状态切换至步骤 402 的状 态， 即运行第二资源块 M2,使用备单板的 IP地址 IP2, 与外部单板进行通信。 对于备单板所接替的主单板的业务， 再切换回主单板， 由主单板执行。
其中， 主单板的切换过程可以是：
主单板在恢复后， 若检测到主单板的 IP地址 IP1被使用 （已在步骤 403 中将该地址 IP1增加至备单板）， 则先以备用 IP地址 IP3启动， 在恢复运行第 一资源块 Ml时， 将备用 IP地址 IP3切换为主单板的 IP地址 IP1 , 并向外部 单板发送 ARP消息， 以使外部单板的 ARP表项恢复至主单板故障前的状态， 主单板运行第一资源块 Ml , 使用 IP地址 IP1与外部单板进行通信。
在另一实施例中，如果在步骤 403中出现故障的是备单板， 则直接由主单 板执行类似步骤 404〜405的步骤，备单板恢复后，备单板按照上述主单板的切 换过程切换回步骤 402的状态。
本发明实施例通过将资源进行划分， 并分别在主、备单板上运行， 使得主 备单板同时参与运行资源与外部单板进行通信， 大大降低了硬件的冗余度， 充 分利用了硬件资源， 提高了硬件性能， 而且， 在某一单板出现故障时， 由另一 单板接替运行故障单板上的资源，避免了业务通信的中断，保证了系统的高可 靠性。
以上是对本发明方法实施例的描述， 下面对实现上述方法的装置进行介 绍。
参见图 6, 为本发明实施例一种单板的结构示意图。
该单板可以包括：
通信单元 601 , 用于运行第二资源块与外部单板进行通信， 其中， 所述单 板的主单板运行第一资源块与所述外部单板进行通信，所述第一资源块与所述 第二资源块不同，且所述第一资源块与所述第二资源块为划分资源获得的可独 立运行的资源块；
故障处理单元 602, 用于当检测到所述主单板出现故障时， 运行所述第二 资源块， 以及在所述单板上存储的所述第一资源块的备份， 与所述外部单板进 行通信。
在本发明实施例中， 首先将资源进行划分， 其划分的标准是所划分出的各 资源块可以独立运行， 在运行某一资源块时， 无需参看其它资源块。 在划分完 成后， 进行资源块的分配，该资源的划分过程和分配过程可以由该单板或其它 设备执行。该单板及其主单板获得资源分配后 (如第一资源块分配至该单板的 主单板， 第二资源块分配至该单板）， 通信单元 601可运行该第二资源块， 与 外部单板进行业务通信，具体的可以通过主单板上的代理通信模块与外部单板 进行通信，也可以是通过该单板自身的通信模块与外部单板进行通信。 当故障 处理单元 602检测到主单板出现故障时， 由该单元在运行原第二资源块的同 时， 接替运行主单板上的业务， 即运行该单板上存储的该第一资源块的备份， 与外部其它单板进行业务通信。
本实施例中，单板通过上述单元与主单板同时参与运行资源与外部单板进 行通信， 大大降低了硬件的冗余度， 充分利用了硬件资源， 提高了硬件性能， 而且， 在某一单板出现故障时， 由另一单板接替运行故障单板上的资源， 避免 了业务通信的中断， 保证了系统的高可靠性。
参见图 7, 为本发明实施例另一种单板的结构示意图。
该单板除了可以包括通信单元 701 , 故障处理单元 702之外， 还可以包括 第一恢复单元 703。
其中， 通信单元 701 , 具体用于运行第二资源块， 并通过所述主单板上的 代理通信模块与所述外部单板进行通信。
故障处理单元 702, 具体用于当检测到所述主单板出现故障时， 运行所述 第二资源块， 以及在所述单板上存储的所述第一资源块的备份，使用所述主单 板的 IP地址， 与所述外部单板进行通信。
第一恢复单元 703 , 用于当检测到所述主单板恢复时， 运行第二资源块与 外部单板进行通信，并通过所述主单板上的代理通信模块与所述外部单板进行 通信； 其中， 所述主单板恢复运行第一资源块与所述外部单板进行通信。
本实施例中，单板通过上述单元与主单板同时参与运行资源与外部单板进 行通信， 大大降低了硬件的冗余度， 充分利用了硬件资源， 提高了硬件性能， 而且， 在某一单板出现故障时， 由另一单板接替运行故障单板上的资源， 避免 了业务通信的中断， 保证了系统的高可靠性。
参见图 8, 为本发明实施例另一种单板的结构示意图。
该单板除了可以包括通信单元 801 , 故障处理单元 802之外， 还可以包括 第二恢复单元 803。
其中， 通信单元 801 , 具体用于运行第二资源块， 并通过所述单板的 IP 地址与所述外部单板进行通信。
故障处理单元 802可以进一步包括：
消息发送子单元 8021 , 用于当检测到所述主单板出现故障时， 增加所述 主单板的 IP地址， 并向所述外部单板发送 ARP消息；
故障处理子单元 8022, 用于运行第二资源块， 使用所述单板的 IP地址， 与所述外部单板进行通信， 且运行在所述单板上存储的所述第一资源块的备 份， 使用所述主单板的 IP地址， 与所述外部单板进行通信。
第二恢复单元 803 , 用于当检测到所述主单板恢复时， 运行第二资源块， 使用所述单板的 IP地址， 与外部单板进行通信。 其中， 所述主单板在检测到 所述主单板的 IP地址被使用时， 以备用 IP地址启动， 在恢复运行所述第一资 源块时， 将所述备用 IP地址切换为所述主单板的 IP地址， 并向所述外部单板 发送 ARP消息， 与所述外部单板进行通信。
本实施例中，单板通过上述单元与主单板同时参与运行资源与外部单板进 行通信， 大大降低了硬件的冗余度， 充分利用了硬件资源， 提高了硬件性能， 而且， 在某一单板出现故障时， 由另一单板接替运行故障单板上的资源， 避免 了业务通信的中断， 保证了系统的高可靠性。
参见图 9, 为本发明实施例一种主备模式下的单板运行系统结构示意图。 该系统包括主单板 901及其备单板 902 , 该系统的资源划分为至少两部分 可独立运行的资源块， 资源块被分配至主单板 901及备单板 902上， 主单板 901， 用于运行第一资源块与所述外部单板进行通信； 备单板 902, 用于运行第二资源块与外部单板进行通信， 其中， 所述第一 资源块与所述第二资源块不同； 当检测到所述主单板出现故障时，运行所述第 二资源块， 以及在所述备单板上存储的所述第一资源块的备份， 与所述外部单 板进行通信。
本实施例中， 该系统大大降低了硬件的冗余度， 充分利用了硬件资源， 提 高了硬件性能， 而且， 在某一单板出现故障时， 由另一单板接替运行故障单板 上的资源， 避免了业务通信的中断， 保证了系统的高可靠性。
以上单板和系统中各单元的具体实现过程，请参见前述方法实施例的对应 描述， 此处不再赘述。
以上所述的本发明实施方式， 并不构成对本发明保护范围的限定。任何在 本发明的精神和原则之内所作的修改、等同替换和改进等， 均应包含在本发明 的权利要求保护范围之内。

Claims

权 利 要 求
1、 一种主备模式下的单板运行方法， 其特征在于， 将资源划分为至少两 部分可独立运行的资源块， 并将所述资源块分配至主单板及其备单板上， 所述 方法包括：
所述主单板运行第一资源块与外部单板进行通信，所述备单板运行第二资 源块与所述外部单板进行通信，其中，所述第一资源块与所述第二资源块不同； 当所述备单板检测到所述主单板出现故障时，由所述备单板运行所述第二 资源块， 以及在所述备单板上存储的所述第一资源块的备份， 与所述外部单板 进行通信。
2、 根据权利要求 1所述的方法， 其特征在于， 所述备单板运行第二资源 块与外部单板进行通信， 包括：
所述备单板运行第二资源块，并通过所述主单板上的代理通信模块与所述 外部单板进行通信。
3、 根据权利要求 2所述的方法， 其特征在于， 所述备单板运行的第二资 源块的资源量大于所述主单板运行的第一资源块的资源量。
4、 根据权利要求 2所述的方法， 其特征在于， 所述当所述备单板检测到 所述主单板出现故障时， 由所述备单板运行所述第二资源块， 以及在所述备单 板上存储的所述第一资源块的备份， 与所述外部单板进行通信， 包括：
当所述备单板检测到所述主单板出现故障时，由所述备单板运行所述第二 资源块， 以及在所述备单板上存储的所述第一资源块的备份，使用所述主单板 的 IP地址， 与所述外部单板进行通信。
5、 根据权利要求 2所述的方法， 其特征在于， 还包括：
当所述主单板检测到所述备单板出现故障时 ,由所述主单板运行所述第一 资源块， 以及在所述主单板上存储的所述第二资源块的备份，使用所述主单板 的 IP地址， 与所述外部单板进行通信。
6、 根据权利要求 2所述的方法， 其特征在于， 还包括：
当所述备单板检测到所述主单板恢复时，所述备单板运行第二资源块与外 部单板进行通信，并通过所述主单板上的代理通信模块与所述外部单板进行通 信； 其中， 所述主单板恢复运行第一资源块与所述外部单板进行通信。
7、 根据权利要求 1所述的方法， 其特征在于， 所述备单板运行第二资源 块与外部单板进行通信， 包括：
所述备单板运行第二资源块， 并通过所述备单板的 IP地址与所述外部单 板进行通信。
8、 根据权利要求 7所述的方法， 其特征在于， 所述备单板运行的第二资 源块的资源量等于所述主单板运行的第一资源块的资源量。
9、 根据权利要求 7所述的方法， 其特征在于， 所述当所述备单板检测到 所述主单板出现故障时， 由所述备单板运行所述第二资源块， 以及在所述备单 板上存储的所述第一资源块的备份， 与所述外部单板进行通信， 包括：
当所述备单板检测到所述主单板出现故障时，所述备单板增加所述主单板 的 IP地址， 并向所述外部单板发送地址解析协议 ARP消息；
所述备单板运行第二资源块， 使用所述备单板的 IP地址， 与所述外部单 板进行通信， 且所述备单板运行在所述备单板上存储的所述第一资源块的备 份， 使用所述主单板的 IP地址， 与所述外部单板进行通信。
10、 根据权利要求 7所述的方法， 其特征在于， 还包括：
当所述备单板检测到所述主单板恢复时， 所述备单板运行第二资源块，使 用所述备单板的 IP地址， 与外部单板进行通信；
其中， 所述主单板在检测到所述主单板的 IP地址被使用时， 以备用 IP地 址启动， 在恢复运行所述第一资源块时， 将所述备用 IP地址切换为所述主单 板的 IP地址， 并向所述外部单板发送 ARP消息， 与所述外部单板进行通信。
11、 一种单板， 其特征在于， 包括：
通信单元， 用于运行第二资源块与外部单板进行通信， 其中， 所述单板的 主单板运行第一资源块与所述外部单板进行通信，所述第一资源块与所述第二 资源块不同，且所述第一资源块与所述第二资源块为划分资源获得的可独立运 行的资源块；
故障处理单元， 用于当检测到所述主单板出现故障时，运行所述第二资源 块， 以及在所述单板上存储的所述第一资源块的备份， 与所述外部单板进行通 信。
12、 根据权利要求 11所述的单板， 其特征在于， 所述通信单元， 具体用于运行第二资源块， 并通过所述主单板上的代理通 信模块与所述外部单板进行通信。
13、 根据权利要求 12所述的单板， 其特征在于，
所述故障处理单元， 具体用于当检测到所述主单板出现故障时，运行所述 第二资源块， 以及在所述单板上存储的所述第一资源块的备份，使用所述主单 板的 IP地址， 与所述外部单板进行通信。
14、 根据权利要求 12所述的单板， 其特征在于， 还包括：
第一恢复单元， 用于当检测到所述主单板恢复时，运行第二资源块与外部 单板进行通信， 并通过所述主单板上的代理通信模块与所述外部单板进行通 信； 其中， 所述主单板恢复运行第一资源块与所述外部单板进行通信。
15、 根据权利要求 11所述的单板， 其特征在于，
所述通信单元， 具体用于运行第二资源块， 并通过所述单板的 IP地址与 所述外部单板进行通信。
16、 根据权利要求 15所述的单板， 其特征在于， 所述故障处理单元包括： 消息发送子单元， 用于当检测到所述主单板出现故障时，增加所述主单板 的 IP地址， 并向所述外部单板发送 ARP消息；
故障处理子单元， 用于运行第二资源块， 使用所述单板的 IP地址， 与所 述外部单板进行通信，且运行在所述单板上存储的所述第一资源块的备份，使 用所述主单板的 IP地址， 与所述外部单板进行通信。
17、 根据权利要求 15所述的单板， 其特征在于， 还包括：
第二恢复单元， 用于当检测到所述主单板恢复时， 运行第二资源块， 使用 所述单板的 IP地址， 与外部单板进行通信；
其中， 所述主单板在检测到所述主单板的 IP地址被使用时， 以备用 IP地 址启动， 在恢复运行所述第一资源块时， 将所述备用 IP地址切换为所述主单 板的 IP地址， 并向所述外部单板发送 ARP消息， 与所述外部单板进行通信。
18、 一种主备模式下的单板运行系统， 其特征在于， 包括主单板及其备单 板， 所述系统的资源划分为至少两部分可独立运行的资源块， 所述资源块被分 配至所述主单板及所述备单板上，
所述主单板， 用于运行第一资源块与所述外部单板进行通信； 所述备单板， 用于运行第二资源块与外部单板进行通信， 其中， 所述第二 资源块与所述第一资源块不同； 当检测到所述主单板出现故障时，运行所述第 二资源块， 以及在所述备单板上存储的所述第一资源块的备份， 与所述外部单 板进行通信。
PCT/CN2011/080413 2011-09-30 2011-09-30 一种主备模式下的单板运行方法及系统 WO2012149785A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2011/080413 WO2012149785A1 (zh) 2011-09-30 2011-09-30 一种主备模式下的单板运行方法及系统
CN201180002282.3A CN102388570B (zh) 2011-09-30 2011-09-30 一种主备模式下的单板运行方法及系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/080413 WO2012149785A1 (zh) 2011-09-30 2011-09-30 一种主备模式下的单板运行方法及系统

Publications (1)

Publication Number Publication Date
WO2012149785A1 true WO2012149785A1 (zh) 2012-11-08

Family

ID=45826508

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/080413 WO2012149785A1 (zh) 2011-09-30 2011-09-30 一种主备模式下的单板运行方法及系统

Country Status (2)

Country Link
CN (1) CN102388570B (zh)
WO (1) WO2012149785A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105323873A (zh) * 2014-07-03 2016-02-10 中兴通讯股份有限公司 一种基站、基站负荷分担装置及方法

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102629906A (zh) * 2012-03-30 2012-08-08 浪潮电子信息产业股份有限公司 一种将集群管理节点做双机实现提高集群业务可用性的设计办法
CN104731656B (zh) * 2013-12-23 2018-10-30 华为软件技术有限公司 一种资源分配方法及装置
CN103744755A (zh) * 2014-01-08 2014-04-23 烽火通信科技股份有限公司 主备单板端口共享保护的实现系统及方法
CN104778098A (zh) * 2015-04-09 2015-07-15 浪潮电子信息产业股份有限公司 一种内存镜像的方法及系统、一种内存监控器
CN104994071B (zh) * 2015-05-28 2018-11-09 新华三技术有限公司 宽带远程接入服务器设备的备份方法及装置
CN107147511A (zh) * 2016-03-01 2017-09-08 深圳市深信服电子科技有限公司 数据中心控制方法及装置
CN113206698B (zh) * 2021-03-22 2022-08-16 深圳震有科技股份有限公司 一种卫星媒体资源冗余保护方法、智能终端及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1929324A (zh) * 2006-10-17 2007-03-14 杭州华为三康技术有限公司 一种互为备份装置的主从切换方法及主从切换系统
CN101115033A (zh) * 2007-09-04 2008-01-30 武汉市中光通信公司 会话初始协议网关主备倒换系统及其方法
CN101394260A (zh) * 2007-09-17 2009-03-25 华为技术有限公司 一种实现主备倒换及负荷分担的方法和装置
CN101404519A (zh) * 2008-11-14 2009-04-08 华为技术有限公司 一种业务板系统和业务处理方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8051326B2 (en) * 2006-12-29 2011-11-01 Futurewei Technologies, Inc. System and method for completeness of TCP data in TCP HA

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1929324A (zh) * 2006-10-17 2007-03-14 杭州华为三康技术有限公司 一种互为备份装置的主从切换方法及主从切换系统
CN101115033A (zh) * 2007-09-04 2008-01-30 武汉市中光通信公司 会话初始协议网关主备倒换系统及其方法
CN101394260A (zh) * 2007-09-17 2009-03-25 华为技术有限公司 一种实现主备倒换及负荷分担的方法和装置
CN101404519A (zh) * 2008-11-14 2009-04-08 华为技术有限公司 一种业务板系统和业务处理方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105323873A (zh) * 2014-07-03 2016-02-10 中兴通讯股份有限公司 一种基站、基站负荷分担装置及方法

Also Published As

Publication number Publication date
CN102388570B (zh) 2014-03-26
CN102388570A (zh) 2012-03-21

Similar Documents

Publication Publication Date Title
WO2012149785A1 (zh) 一种主备模式下的单板运行方法及系统
US7894334B2 (en) Hierarchical redundancy for a distributed control plane
US8339940B2 (en) Multi-active detection method and stack member device
CN110224871B (zh) 一种Redis集群的高可用方法及装置
CN102439903B (zh) 实现容灾备份的方法、设备及系统
CN108075971B (zh) 一种主备切换方法及装置
US8032786B2 (en) Information-processing equipment and system therefor with switching control for switchover operation
WO2009023996A1 (en) Method for implementing network interconnect via link aggregation
CN105515812A (zh) 资源的故障处理方法及装置
WO2006030623A1 (ja) 冗長化プロトコルと擬似冗長構成手段を用いたネットワーク接続機器の切換方法とネットワークシステム
CN109861867B (zh) 一种mec业务处理方法及装置
WO2007048319A1 (fr) Systeme et procede de recuperation sur sinistre de dispositif de commande de service dans un reseau intelligent
JP2004165810A (ja) 無線ｌａｎ基地局の二重化システム
WO2018166308A1 (zh) 一种分布式nat双机热备份流量切换系统和方法
US11349706B2 (en) Two-channel-based high-availability
WO2011147312A1 (zh) 一种业务接入路由器的端口备份方法、装置和系统
CN101237315A (zh) 一种用于双控高可用系统的同步检测和故障隔离方法
CN102647304A (zh) 地址解析协议表的同步方法及装置
JP2009187090A (ja) クラスタシステムおよび情報処理方法
WO2015039512A1 (zh) 一种池元素状态信息同步的方法、池注册器和池元素
JPH09259096A (ja) ネットワーク高信頼化方式及びシステム
JP2013172393A (ja) エッジ装置冗長化システム、切替制御装置およびエッジ装置冗長化方法
WO2011110134A2 (zh) 负载分担的方法及装置、宽带接入服务器系统
CN116074187B (zh) 主备链路切换方法及装置、电子设备、存储介质
US11418382B2 (en) Method of cooperative active-standby failover between logical routers based on health of attached services

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201180002282.3

Country of ref document: CN

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

Ref document number: 11864891

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

Country of ref document: EP

Kind code of ref document: A1