WO2020135578A1 - 无cpu交换单板的资源管理方法、系统及存储介质 - Google Patents

无cpu交换单板的资源管理方法、系统及存储介质 Download PDF

Info

Publication number
WO2020135578A1
WO2020135578A1 PCT/CN2019/128671 CN2019128671W WO2020135578A1 WO 2020135578 A1 WO2020135578 A1 WO 2020135578A1 CN 2019128671 W CN2019128671 W CN 2019128671W WO 2020135578 A1 WO2020135578 A1 WO 2020135578A1
Authority
WO
WIPO (PCT)
Prior art keywords
board
switching
main control
information
switching board
Prior art date
Application number
PCT/CN2019/128671
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 WO2020135578A1 publication Critical patent/WO2020135578A1/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/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/16—Constructional details or arrangements
    • 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/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • 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/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements

Definitions

  • This application relates to the communication field, for example, to a resource management method, system, and storage medium without a central processing unit (Central Processing Unit, CPU) exchange board.
  • CPU Central Processing Unit
  • a set of resource management system is deployed on the main control board, but the management functions related to the switching board still need to be implemented by the resource management system included in each switching board.
  • the board's resource management system needs to be deployed in the CPU of the switching board and driven by its own management logic. In this way, for the main control board and the switching board, there are two sets of resources to manage the resources of the board. This not only leads to management redundancy, but also consumes some resources of the switching board, and ultimately reduces the switching board. Exchange ability.
  • the embodiments of the present application provide a resource management method, system and storage medium for a CPU-free exchange board, to at least solve the main board management function of the exchange board in the related art, which needs to be implemented with its own resource management system, resulting in the exchange The shortage of board resources and the reduction of exchange capacity.
  • a resource management method for a CPU-free switching board including: the main control board determines that a predetermined trigger condition is established, wherein the predetermined trigger condition includes at least one of the following: a switch is received The registration message sent by the board, the keep-alive message sent by the exchange board is received, it is determined that the keep-alive message sent by the exchange board is not received within a predetermined time, and the reset message to reset the exchange board is received; the master The control board generates a management instruction according to the management strategy corresponding to the predetermined trigger condition and sends the management instruction to the switching board to implement management of the switching board.
  • a resource management system which is located in a main control board, and the resource management system is used to: determine that a predetermined trigger condition is established, wherein the predetermined trigger condition includes at least one of the following : Received the registration message sent by the exchange board, received the keep-alive message sent by the exchange board, determined that the keep-alive message sent by the exchange board was not received within the predetermined time, and received the reset message to reset the exchange board Generating a management instruction according to the management strategy corresponding to the predetermined trigger condition and sending the management instruction to the switching board to implement management of the switching board.
  • a storage medium in which a computer program is stored, wherein the computer program is configured to execute the steps in any one of the above method embodiments during runtime.
  • FIG. 1 is a flowchart of a resource management method for a CPU-less switching board provided in Embodiment 1 of the present application;
  • Example 2 is a schematic diagram of a resource management system without CPU switching boards provided in Example 2 of the present application;
  • Example 3 is a system logic diagram of a resource management solution for a CPU-less switching board provided in Example 4 of the present application;
  • Example 4 is a flowchart of a method for managing a resource management solution without CPU switching boards provided in Example 4 of the present application;
  • FIG. 5 is a power-on flow chart of a CPU-less switching board provided in Embodiment 5 of the present application.
  • FIG. 6 is a keepalive flow chart of a CPU-free switching board provided in Embodiment 6 of the present application.
  • Example 7 is a flowchart of a keep-alive timeout for a CPU-free switching board provided in Example 7 of the present application;
  • FIG. 8 is a reset flow chart of a CPU-free switching board provided in Embodiment 8 of the present application.
  • the switching boards with CPUs all brought their own resource management systems.
  • the exchange board interacts with the main control board through these resource management processes to complete the management of the exchange board.
  • the redundant resource management system also increases the maintenance cost of the exchange board.
  • the essential task of the switching board is to provide data exchange services, that is to say, it is mainly to complete the configuration of the switching path of the business data and the forwarding of business packets. Any extra maintenance or overhead will reduce the processing capacity of the switching board.
  • the embodiments of the present application provide a new switching board resource management solution, which deploys the resource management system on the main control board, And the resource management system can complete the management tasks related to the exchange board, complete the resource management of the exchange board through a new resource management method, abandon the redundancy of the exchange board in resource management, and further improve the data of the exchange board Exchange ability.
  • the resource management system can no longer be deployed on the switching board, so the hardware carrying the resource management system can be tailored accordingly, including the CPU.
  • the 5th Generation mobile communication system 5th Generation mobile communication system, 5G
  • a CPU and its surrounding logic circuits have more than 100 electronic components. These electronic components are not only expensive, but also consume The power is also large. Therefore, on the basis of this resource management method, the CPU of the exchange board and the surrounding hardware can be eliminated, so that the hardware cost of the board can be reduced.
  • FIG. 1 is a flowchart of a method for resource management without CPU switching boards provided in Embodiment 1 of the present application. As shown in FIG. 1, the process includes the following steps:
  • Step S102 the main control board determines that the predetermined trigger condition is established, wherein the predetermined trigger condition includes at least one of the following: a registration message sent by the exchange board is received, a keep-alive message sent by the exchange board is received, and it is determined No keepalive message sent by the switching board or reset message for resetting the switching board was received within the time.
  • Step S104 The main control board generates a management instruction according to the management strategy corresponding to the predetermined trigger condition and sends the management instruction to the switching board to implement management of the switching board.
  • the main control board when the predetermined trigger condition is established, the main control board generates a management instruction according to the management strategy corresponding to the predetermined trigger condition and sends the management instruction to the switching board to implement Board management.
  • This application solves the problem that the main board management function of the exchange board in the related technology needs to be implemented with its own resource management system, resulting in the shortage of exchange board resources and the reduction of the exchange capacity.
  • the main control board realizes all exchanges in a unified way
  • the resource management function of the board reduces the management pressure of the switching board, thus creating conditions for enhancing the data exchange capability of the switching board.
  • the exchange board can be configured without a CPU, that is, the exchange board can be a CPU-free exchange board.
  • the main control board For different management tasks, the following describes that the main control board generates management instructions according to the management strategy corresponding to the predetermined trigger condition and sends the management instructions to the switching board, so as to realize the control of the switching board The process of management.
  • the following is only an exemplary description of the management tasks involved in the actual application scenario, and is not intended to limit the scenarios to which the method can be applied.
  • the predetermined trigger condition includes receiving the registration message sent by the switching board.
  • the registration message may include the programmable device version information of the exchange board, and in addition to the information, it may also include at least one of the following information: message type, shelf number (shelf), slot number (slot), backplane Type, board identifier (Identifier, ID), etc.
  • Step S104 may include:
  • Step S104-1-10 the main control board compares the programmable device version information stored in the local database of the main control board with the programmable device version information of the switching board included in the registration message.
  • Step S104-1-20 when it is determined by comparison that the version information of the programmable device stored in the local database of the main control board and the version information of the programmable device of the exchange board included in the registration message are different,
  • the main control board generates asynchronous version upgrade information and sends the asynchronous version upgrade information to the switching board, wherein the asynchronous version upgrade information is used to indicate the availability of the switching board to the switching board Program the device for version upgrade.
  • step S104-1-20 it may further include:
  • Step S1046 the main control board receives the upgrade result message sent by the exchange board
  • Step S1048 when the upgrade result message indicates that the upgrade fails, the main control board repeatedly sends the version upgrade asynchronous information to the switching board.
  • the main control board when the initialization condition is satisfied, the main control board initializes the switching chip in the switching board, where the initialization condition includes one of the following:
  • the upgrade result message indicates that the upgrade is successful.
  • the number of times that the main control board repeatedly sends the version upgrade asynchronous information to the exchange board exceeds a predetermined number of attempts.
  • the main control board may further include:
  • the main control board sends a registration completion message to the exchange board, wherein the registration completion message is used to trigger the exchange board to send a keep-alive message.
  • the predetermined trigger condition includes when the keep-alive message sent by the switching board is received.
  • the keep-alive message includes microswitch status information.
  • it may also include at least one of the following information: message type, rack number (shelf), slot number (slot), backplane type, board ID .
  • Step S104 may include:
  • Step S104-2-10 the main control board compares the microswitch state information stored in the local database of the main control board with the microswitch state information included in the keep-alive message.
  • Step S104-2-20 when it is determined by comparison that the microswitch status information stored in the local database of the main control board and the microswitch status information included in the keep-alive message are different, all The master control board generates Switch Fabric (SF) synchronization information and sends the SF synchronization information to the switching board, wherein, when the microswitch status information included in the keep-alive message is on When the SF synchronization information is used to instruct to close the SF in the switching board, when the microswitch status information included in the keep-alive message is closed, the SF synchronization information is used to instruct to open the SF Describe the SF in the exchange board.
  • SF Switch Fabric
  • microswitch state information stored in the local database of the main control board and the microswitch state information included in the keep-alive message are different, you can also include:
  • Step S104-2-30 (but the order between it and step S104-2-20 is not limited, it can be processed sequentially or simultaneously), the main control board according to the The microswitch status information updates the microswitch status information stored in the local database of the main control board.
  • the predetermined trigger condition includes determining that the keep-alive message sent by the switching board or the reset message that resets the switching board is not received within a predetermined time.
  • Step S104 may include:
  • Step S104-3-10 the main control board generates SF synchronization information of the switching structure and sends the SF synchronization information to the switching board, wherein the SF synchronization information is used to instruct to close the switching board SF.
  • the keep-alive message sent by the switching board or the reset message that resets the switching board may further include at least one of the following:
  • the main control board deletes the information of the exchange board stored in the local database.
  • the main control board reports the notification message of the exchange board to the alarm module, wherein, in the case where it is determined that the keep-alive message sent by the exchange board is not received within a predetermined time, the notification message is the exchange In the case of a dislocation alarm of a board, when a reset message that resets the switching board is received, the notification message is a reset notification of the switching board.
  • the method according to the above embodiments can be implemented by means of software plus a necessary universal hardware platform, and of course, it can also be implemented by hardware.
  • the technical solution of the present application can be essentially embodied in the form of a software product, and the computer software product is stored in a storage medium (such as Read-Only Memory (ROM)/Random Access Memory (Random Access (Memory, RAM), magnetic disk, and optical disk) include instructions to enable a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to perform the method described in the embodiments of the present application.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • magnetic disk magnetic disk
  • optical disk include instructions to enable a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to perform the method described in the embodiments of the present application.
  • a resource management system is also provided.
  • the system is located in the main control board and is used to implement the foregoing embodiments and implementation modes, and descriptions that have already been described will not be repeated.
  • the term "module” may implement a combination of software and/or hardware that performs predetermined functions.
  • FIG. 2 is a structural block diagram of a resource management system provided in Embodiment 2 of the present application. As shown in FIG. 2, the resource management system 202 is located in the main control board 20, and the resource management system 202 is configured as:
  • the predetermined trigger condition includes at least one of the following: a registration message sent by the exchange board is received, a keep-alive message sent by the exchange board is received, and it is determined that the exchange order is not received within a predetermined time The keepalive message sent by the board and the reset message received to reset the switching board.
  • a management instruction is generated according to the management strategy corresponding to the predetermined trigger condition and the management instruction is sent to the switching board to implement management of the switching board.
  • the registration message includes programmable device version information of the switching board
  • the resource management system 202 It is set to generate a management instruction according to the management strategy corresponding to the predetermined trigger condition and send the management instruction to the switching board by:
  • the resource management system 202 is set to pass Generate a management instruction according to the management strategy corresponding to the predetermined trigger condition and send the management instruction to the switching board as follows:
  • the switching structure SF synchronization information is generated and Sending the SF synchronization information to the switching board, wherein, when the microswitch status information included in the keep-alive message is on, the SF synchronization information is used to instruct to close the switching board SF, when the microswitch status information included in the keep-alive message is closed, the SF synchronization information is used to instruct to open the SF in the switching board.
  • the resource management system 202 It is set to generate a management instruction according to the management strategy corresponding to the predetermined trigger condition and send the management instruction to the switching board by:
  • the above modules can be implemented by software or hardware. For the latter, they can be implemented in the following ways, but not limited to this: the above modules are all located in the same processor; or, the above modules are located in different processes in any combination. In the device.
  • An embodiment of the present application further provides a storage medium in which a computer program is stored, wherein the computer program is configured to execute any of the steps in the above method embodiments during runtime.
  • the above storage medium may be set to store a computer program for performing the following steps: S10, the main control board determines that a predetermined trigger condition is established, wherein the predetermined trigger condition includes at least one of the following One: Received the registration message sent by the exchange board, received the keep-alive message sent by the exchange board, determined that the keep-alive message sent by the exchange board was not received within the predetermined time, received the reset to reset the exchange board Message; S20, the main control board generates a management instruction according to the management strategy corresponding to the predetermined trigger condition and sends the management instruction to the switching board to implement management of the switching board.
  • the above storage medium may include, but is not limited to: Universal Serial Bus flash disk (Universal Serial Bus flash disk, U disk), ROM, RAM, mobile hard disk, magnetic disk or optical disk, etc.
  • Universal Serial Bus flash disk Universal Serial Bus flash disk, U disk
  • ROM Read Only Memory
  • RAM Random Access Memory
  • mobile hard disk magnetic disk or optical disk
  • etc. A medium that can store computer programs.
  • This embodiment provides a resource management method for a CPU-free switching board. This method is to deploy a centralized single board resource management system on the main control board, through the circuit interface between the main control board and the exchange board, using the communication message interaction between the boards, so that the main control board can control the PTN All CPU-less switch boards in the device are managed.
  • FIG. 3 is a system logic diagram of a resource management solution provided in Example 4 of the present application.
  • the method is applied to a complete software system, including a resource management module and a communication unit on a main control board It consists of a module, a communication unit module on a switching board, a communication link module between boards, and a switching chip state change module. These modules work together to complete the resource management of the exchange board. This method can also manage the resources of multiple CPU-free switching boards at the same time.
  • FIG. 4 is a flowchart of a method for managing a resource management solution without CPU switching boards provided in Embodiment 4 of the present application. As shown in FIG. 4, it includes the following steps:
  • step S4010 a CPU-less switching board is inserted into the PTN device.
  • Step S4020 the main control board receives the power-on information sent by the CPU-less exchange board.
  • Step S4030 when the main control board successfully completes the management by using the board resource management method of the solution, the main control board responds successfully to the non-CPU switching board and proceeds to step S4040.
  • Step S4040 the CPU-less board starts to exchange keep-alive messages with the main control board until the exchange board is restarted or unplugged.
  • Step S4050 when the main control board fails to complete the management by adopting the board resource management method of the solution, the main control board initiates a CPU-less board reset.
  • This method overcomes the problems of complex resource management logic and large system maintenance costs in related technologies. It not only greatly simplifies the resource management method of the switching board, but also provides guidance for reducing the hardware cost of the switching board, which in turn makes Exchange boards have greater product competitiveness.
  • the resource management system of the present application is defined as the BRDPROXY system in the following embodiments, and the agent module senses the registration, keep-alive, and micro-switch status of the field programmable logic gate array (FPGA) of the exchange board. And other information.
  • FPGA field programmable logic gate array
  • This embodiment describes the flow of processing on the board.
  • the system receives the registration message sent by the FPGA that exchanges the board, it means that a new board is added at this time, and the board needs to be powered on at this time.
  • the single board should be able to automatically complete the FPGA board upgrade during the power-on process.
  • FIG. 5 is a power-on flowchart of a CPU-less switching board provided in Embodiment 5 of the present application. As shown in Figure 5, it includes the following steps:
  • Step S5010 The BRDPROXY system receives the registration message from the FPGA of the exchange board.
  • the registration message includes the message type, shelf number, slot number, backplane type, board ID, FPGA version, and so on.
  • Step S5020 The BRDPROXY system writes the information in the registration message to the local database.
  • Step S5030 The BRDPROXY system obtains local FPGA version information and compares it with the received FPGA version information:
  • step S5050 If the local FPGA version information is the same as the received FPGA version information, go to step S5050.
  • the version upgrade asynchronous message is delivered to the FPGA of the switching board. If the delivery is successful, go to step S5040; if the delivery fails, try sending again, and if it is unsuccessful more than 3 times, reset the CPUless exchange board.
  • Step S5040 Waiting to receive the FPGA upgrade result message from the exchange board:
  • step S5050 If the upgrade is successful, go to step S5050.
  • step S5050 is entered.
  • Step S5050 Initialize the switching chip.
  • the chip initialization synchronization message is sent to the switching chip management process, and the timeout period is permanent waiting.
  • the switching chip management process returns abnormally, reset the CPUless switching board; when the switching chip management process does not return abnormal, continue.
  • Step S5060 report board power information to the management platform, including board ID, board bill of materials ID (Bill of Material ID, BOMID), board printed circuit board ID (Printed Circuit Board ID, PCBID), subrack , Slot and sub-slot information, and report the FPGA version and PCB version of the board to the management platform.
  • board ID board bill of materials ID
  • BOMID Board of Material ID
  • PCBID Board printed circuit board ID
  • subrack Slot and sub-slot information
  • Step S5070 report onboard power-on information to the alarm platform.
  • Step S5080 send a registration complete message to the FPGA of the switching board. After receiving the message, the FPGA stops sending registration messages and sends keep-alive messages instead.
  • Step S5090 Start the board keep-alive timer.
  • This embodiment describes the process of keeping a board alive. Under normal circumstances, after the board registration is completed, the FPGA that exchanges the boards starts to send keep-alive messages to the BRDPROXY system. At the same time, considering the change of the single-board micro-switch, the FPGA that exchanges the single-board also needs to carry the single-board micro-switch state information.
  • FIG. 6 is a keepalive flow chart of a CPU-free switching board provided in Embodiment 6 of the present application. As shown in Figure 6, it includes the following steps:
  • Step S6010 The BRDPROXY system receives the keep-alive message from the FPGA of the switching board.
  • the message includes the message type, shelf number, slot number, backplane type, board ID, and micro switch status.
  • Step S6020 The BRDPROXY system searches the microswitch state of the single board in the local database and compares it with the microswitch state in the keep-alive message.
  • microswitch status of the board found in the local database is the same as the microswitch status in the keepalive message, no processing is performed.
  • the SF close synchronization message is sent to the switching board. Wait for the completion of SF closing; when the status of the microswitch in the keep-alive message is closed, send an SF opening synchronization message to the switching board, and wait for the completion of SF opening.
  • Step S6030 The BRDPROXY system updates the latest microswitch status in the local database.
  • This embodiment describes the keep-alive timeout processing flow. Under abnormal circumstances, when the main control board does not receive the keep-alive information without a CPU switching board within the specified time, the BRDPROXY system considers the board to be abnormal (power-off, hang, etc.). This situation is called keep-alive timeout. .
  • FIG. 7 is a flowchart of a keep-alive timeout for a CPU-free switching board provided in Embodiment 7 of the present application. As shown in Figure 7, it includes the following steps:
  • Step S7010 The BRDPROXY system has not received the keep-alive message reported by the non-CPU switching board within the specified time.
  • Step S7020 The BRDPROXY system delivers the SF synchronization message to close the switching board without the CPU to the switching board. If the shutdown is successful, update the local microswitch status information, and proceed to step S7030. If the shutdown fails (including timeout), go to step S7030.
  • Step S7030 The BRDPROXY system reports the alarm of the single board dislocation to the alarm module. If the report fails, an error log is recorded.
  • Step S7040 The BRDPROXY system deletes the information of the board locally according to the shelf number and slot number. If the deletion fails, record an error log.
  • This embodiment describes the process of resetting a single board.
  • the user needs to reset a board.
  • the network management needs to reset the board. Only the processing of reset messages in the BRDPROXY system is described below.
  • FIG. 8 is a reset flow chart of a CPU-free switching board provided in Embodiment 8 of the present application. As shown in Figure 8, it includes the following steps:
  • Step S8010 The BRDPROXY system receives a reset message from the user.
  • the reset message includes the message type, shelf number, source slot number, and destination slot number information.
  • Step S8020 The BRDPROXY system deletes the information of the exchange board locally according to the rack number (shelf) and the destination slot number (slot):
  • Step S8030 The BRDPROXY system reports the reset information of the exchange board to the alarm module.
  • Step S8040 The BRDPROXY system sends an SF synchronization message to close the CPU-less exchange board to the chip management process of the main control. If closing SF fails, record a serious error log.
  • modules or steps of the present application can be implemented by a general-purpose computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, optionally, they can be Implemented program code, so that they can be stored in the storage device to be executed by the computing device, and in some cases, the steps shown or described can be performed in a different order than here, or they can be separated It can be realized by making multiple integrated circuit modules, or by making multiple modules or steps among them into a single integrated circuit module. In this way, this application is not limited to any specific combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本文公开了一种无CPU交换单板的资源管理方法、系统及存储介质，该方法包括：主控单板确定预定触发条件成立，其中，所述预定触发条件包括以下至少之一：接收到交换单板发送的注册消息、接收到交换单板发送的保活消息、确定在预定时间内未接收到交换单板发送的保活消息、接收到对交换单板进行复位的复位消息；所述主控单板根据所述预定触发条件对应的管理策略生成管理指令并向所述交换单板发送所述管理指令。

Description

无CPU交换单板的资源管理方法、系统及存储介质
本申请要求在2018年12月29日提交中国专利局、申请号为201811648080.6的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，例如，涉及一种无中央处理单元(Central Processing Unit，CPU)交换单板的资源管理方法、系统及存储介质。
背景技术
随着新一代通讯的标准的不断提出，对网络设备的带宽、时延、抖动等提出了很高的要求。为了适应这种要求，基于分组传送网(Packet Transport Network，PTN)承载技术的交换网络就需要有更大的带宽和更小的时延，因此，提升设备交换能力、便捷管理交换资源，对PTN设备来说就显得日益重要。
在相关技术的PTN设备中，主控单板上部署了一套资源管理系统，但是，关于交换单板相关的管理功能，仍然需要由每个交换单板包含的资源管理系统来实现，而交换单板的资源管理系统需要部署在交换单板的CPU中，由自身的管理逻辑进行驱动。这样，对于主控单板和交换单板，就有两套资源来进行单板的资源管理，这样不但导致管理冗余，而且还消耗了交换单板的一些资源，最终降低了交换单板的交换能力。
发明内容
本申请实施例提供了一种无CPU交换单板的资源管理方法、系统及存储介质，以至少解决相关技术中交换单板的主要单板管理功能需要借助自身资源管理系统来实现，导致交换单板资源紧张、交换能力降低的问题。
根据本申请的一个实施例，提供了一种无CPU交换单板的资源管理方法，包括：主控单板确定预定触发条件成立，其中，所述预定触发条件包括以下至少之一：接收到交换单板发送的注册消息、接收到交换单板发送的保活消息、确定在预定时间内未接收到交换单板发送的保活消息、接收到对交换单板进行复位的复位消息；所述主控单板根据所述预定触发条件对应的管理策略生成管理指令并向所述交换单板发送所述管理指令，以实现对所述交换单板的管理。
根据本申请的另一个实施例，提供了一种资源管理系统，位于主控单板中，所述资源管理系统用于：确定预定触发条件成立，其中，所述预定触发条件包 括以下至少之一：接收到交换单板发送的注册消息、接收到交换单板发送的保活消息、确定在预定时间内未接收到交换单板发送的保活消息、接收到对交换单板进行复位的复位消息；根据所述预定触发条件对应的管理策略生成管理指令并向所述交换单板发送所述管理指令，以实现对所述交换单板的管理。
根据本申请的又一个实施例，还提供了一种存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
附图说明
图1是本申请实施例1提供的一种无CPU交换单板的资源管理方法的流程图；
图2是本申请实施例2提供的一种无CPU交换单板的资源管理系统的示意图；
图3是本申请实施例4提供的一种无CPU交换单板的资源管理方案的系统逻辑图；
图4是本申请实施例4提供的一种无CPU交换单板的资源管理方案的管理方法流程图；
图5是本申请实施例5提供的一种无CPU交换单板的上电流程图；
图6是本申请实施例6提供的一种无CPU交换单板的保活流程图；
图7是本申请实施例7提供的一种无CPU交换单板的保活超时流程图；
图8是本申请实施例8提供的一种无CPU交换单板的复位流程图。
具体实施方式
在PTN领域中，虽然有多种多样的交换单板，但都是传统的单板资源管理方式，在每个交换单板上都设有专用于管理本交换单板的资源管理系统，但是这种资源管理方式，存在三大缺点：
1)功能冗余，维护开销大。
在以往有CPU的交换单板上，都自带了一套自身的资源管理系统。交换单板通过这些资源管理进程来和主控单板进行交互，以完成交换单板的管理。这样，同一交换单板，就存在两套资源管理方式，存在冗余管理。同时，冗余的资源管理系统也增加了交换单板的维护成本。
2)核心业务处理能力低。
交换单板本质的任务是用来进行数据交换服务，也就是说，主要是要完成业务数据的交换路径配置和业务报文的转发，任何多余的维护或开销都会降低交换单板的处理能力。
为了提升交换单板的交换能力、降低交换单板的管理复杂度，本申请实施例提供了一种新的交换单板资源管理方案，这种方案将资源管理系统部署在主控单板上，且该资源管理系统能够完成交换单板的相关管理任务，通过全新的资源管理方式来完成对交换单板的资源管理，摈弃交换单板在资源管理方面的冗余，进而提升交换单板的数据交换能力。通过该方案，交换单板上可以不再部署资源管理系统，那么承载资源管理系统的硬件就可以相应的做出裁剪，包括CPU等。在第五代移动通信系统(the 5th Generation mobile communication system，5G)的业务交换单板上，一个CPU及其周围的逻辑电路有100多个电子元器件，这些电子元器件不但成本高昂，而且耗电量也大。因此在本资源管理方法的基础上，就可以消除交换单板的CPU及其周围的硬件，从而可以降低单板的硬件成本。
下文中将参考附图并结合实施例来说明本申请。
本文中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
实施例1
图1是本申请实施例1提供的一种无CPU交换单板的资源管理方法的流程图，如图1所示，该流程包括如下步骤：
步骤S102，主控单板确定预定触发条件成立，其中，所述预定触发条件包括以下至少之一：接收到交换单板发送的注册消息、接收到交换单板发送的保活消息、确定在预定时间内未接收到交换单板发送的保活消息、接收到对交换单板进行复位的复位消息。
步骤S104，所述主控单板根据所述预定触发条件对应的管理策略生成管理指令并向所述交换单板发送所述管理指令，以实现对所述交换单板的管理。
通过该方案，主控单板在预定触发条件成立的情况下，根据所述预定触发条件对应的管理策略生成管理指令并向所述交换单板发送所述管理指令，以实现对所述交换单板的管理。通过本申请，解决了解决相关技术中交换单板的主要单板管理功能需要借助自身资源管理系统来实现，导致交换单板资源紧张、交换能力降低的问题，由主控单板统一实现所有交换单板的资源管理功能，减轻了交换单板的管理压力，从而为提升交换单板的数据交换能力创造了条件。在此基础上，交换单板可以不设置CPU，也就是说，交换单板可以为无CPU交 换单板。
以下针对不同的管理任务，分别描述所述主控单板根据所述预定触发条件对应的管理策略生成管理指令并向所述交换单板发送所述管理指令，以实现对所述交换单板的管理的过程。以下仅仅是针对实际应用场景中涉及的管理任务给出示例性的说明，并不是用于限定该方法所能够应用到的场景。
(1)在所述预定触发条件包括接收到所述交换单板发送的所述注册消息的情况下。
所述注册消息可以包括所述交换单板的可编程器件版本信息，除了该信息，还可以包括以下信息至少之一：消息类型、机架号(shelf)、槽位号(slot)、背板类型、单板标识(Identifier，ID)等。
步骤S104可以包括：
步骤S104-1-10，所述主控单板比较所述主控单板本地数据库保存的可编程器件版本信息和所述注册消息中包括的所述交换单板的可编程器件版本信息。
步骤S104-1-20，在通过比较确定所述主控单板本地数据库保存的可编程器件版本信息和所述注册消息中包括的所述交换单板的可编程器件版本信息不同的情况下，所述主控单板生成版本升级异步信息并向所述交换单板发送所述版本升级异步信息，其中，所述版本升级异步信息用于指示所述交换单板对所述交换单板的可编程器件进行版本升级。
在步骤S104-1-20之后，还可以包括：
步骤S1046，所述主控单板接收所述交换单板发送的升级结果消息；
步骤S1048，在所述升级结果消息指示升级失败的情况下，所述主控单板重复向所述交换单板发送所述版本升级异步信息。
作为一个示例性的实施方式，在初始化条件满足的情况下，所述主控单板对所述交换单板中的交换芯片进行初始化，其中，所述初始化条件包括以下之一：
通过比较确定所述主控单板本地数据库保存的可编程器件版本信息和所述注册消息中包括的所述交换单板的可编程器件版本信息相同。
所述升级结果消息指示升级成功。
所述主控单板重复向所述交换单板发送所述版本升级异步信息的次数超过预定尝试次数。
作为一个示例性的实施方式，所述主控单板对所述交换单板中的交换芯片进行初始化之后，还可以包括：
所述主控单板向所述交换单板发送注册完成消息，其中，所述注册完成消息用于触发所述交换单板发送保活消息。
(2)所述预定触发条件包括接收到所述交换单板发送的所述保活消息的情况下。
所述保活消息包括微动开关状态信息，除此之外，还可以包括以下信息至少之一：消息类型、机架号(shelf)、槽位号(slot)、背板类型、单板ID。
步骤S104可以包括：
步骤S104-2-10，所述主控单板比较所述主控单板本地数据库保存的微动开关状态信息和所述保活消息中包括的所述微动开关状态信息。
步骤S104-2-20，在通过比较确定所述主控单板本地数据库保存的所述微动开关状态信息和所述保活消息中包括的所述微动开关状态信息不同的情况下，所述主控单板生成交换结构(Switch Fabric，SF)同步信息并向所述交换单板发送所述SF同步信息，其中，当所述保活消息中包括的所述微动开关状态信息为打开时，所述SF同步信息用于指示关闭所述交换单板中的SF，当所述保活消息中包括的所述微动开关状态信息为关闭时，所述SF同步信息用于指示打开所述交换单板中的SF。
作为一个示例性的实施例，在通过比较确定所述主控单板本地数据库保存的所述微动开关状态信息和所述保活消息中包括的所述微动开关状态信息不同之后，还可以包括：
步骤S104-2-30(但其与步骤S104-2-20之间的顺序并不加以限定，可以先后处理也可以同时处理)，所述主控单板根据所述保活消息中包括的所述微动开关状态信息更新所述主控单板本地数据库保存的微动开关状态信息。
(3)在所述预定触发条件包括确定在预定时间内未接收到交换单板发送的保活消息或接收到对所述交换单板进行复位的复位消息的情况下。
步骤S104可以包括：
步骤S104-3-10，所述主控单板生成交换结构SF同步信息并向所述交换单板发送所述SF同步信息，其中，所述SF同步信息用于指示关闭所述交换单板中的SF。
作为一个示例性的实施方式，确定在预定时间内未接收到交换单板发送的保活消息或接收到对所述交换单板进行复位的复位消息之后，还可以包括以下至少之一：
所述主控单板删除本地数据库中存储的所述交换单板的信息。
所述主控单板向告警模块上报所述交换单板的通知消息，其中，在确定在预定时间内未接收到交换单板发送的保活消息的情况下，所述通知消息为所述交换单板的脱位告警，在接收到对所述交换单板进行复位的复位消息的情况下，所述通知消息为所述交换单板的复位通知。
通过以上的实施方式的描述，根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件。基于这样的理解，本申请的技术方案本质上可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如只读存储器(Read-Only Memory，ROM)/随机存取存储器(Random Access Memory，RAM)、磁碟、光盘)中，包括一些指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本申请实施例所述的方法。
实施例2
在本实施例中还提供了一种资源管理系统，该系统位于主控单板中，并用于实现上述实施例及实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的系统以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图2是本申请实施例2提供的一种资源管理系统的结构框图，如图2所示，该资源管理系统202位于主控单板20中，所述资源管理系统202设置为：
确定预定触发条件成立，其中，所述预定触发条件包括以下至少之一：接收到交换单板发送的注册消息、接收到交换单板发送的保活消息、确定在预定时间内未接收到交换单板发送的保活消息、接收到对交换单板进行复位的复位消息。
根据所述预定触发条件对应的管理策略生成管理指令并向所述交换单板发送所述管理指令，以实现对所述交换单板的管理。
(1)在所述预定触发条件包括接收到所述交换单板发送的所述注册消息的情况下，所述注册消息包括所述交换单板的可编程器件版本信息，所述资源管理系统202是设置为通过如下方式根据所述预定触发条件对应的管理策略生成管理指令并向所述交换单板发送所述管理指令：
比较所述主控单板20本地数据库保存的可编程器件版本信息和所述注册消息中包括的所述交换单板的可编程器件版本信息。
在通过比较确定所述主控单板20本地数据库保存的可编程器件版本信息和所述注册消息中包括的所述交换单板的可编程器件版本信息不同的情况下，生 成版本升级异步信息并向所述交换单板发送所述版本升级异步信息，其中，所述版本升级异步信息用于指示所述交换单板对所述交换单板的可编程器件进行版本升级。
(2)在所述预定触发条件包括接收到所述交换单板发送的所述保活消息的情况下，所述保活消息包括微动开关状态信息，所述资源管理系统202是设置为通过如下方式根据所述预定触发条件对应的管理策略生成管理指令并向所述交换单板发送所述管理指令：
比较所述主控单板20本地数据库保存的微动开关状态信息和所述保活消息中包括的所述微动开关状态信息。
在通过比较确定所述主控单板20本地数据库保存的所述微动开关状态信息和所述保活消息中包括的所述微动开关状态信息不同的情况下，生成交换结构SF同步信息并向所述交换单板发送所述SF同步信息，其中，当所述保活消息中包括的所述微动开关状态信息为打开时，所述SF同步信息用于指示关闭所述交换单板中的SF，当所述保活消息中包括的所述微动开关状态信息为关闭时，所述SF同步信息用于指示打开所述交换单板中的SF。
(3)在所述预定触发条件包括确定在预定时间内未接收到交换单板发送的保活消息或接收到对所述交换单板进行复位的复位消息的情况下，所述资源管理系统202是设置为通过如下方式根据所述预定触发条件对应的管理策略生成管理指令并向所述交换单板发送所述管理指令：
生成交换结构SF同步信息并向所述交换单板发送所述SF同步信息，其中，所述SF同步信息用于指示关闭所述交换单板中的SF。
上述模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述模块以任意组合的形式分别位于不同的处理器中。
实施例3
本申请的实施例还提供了一种存储介质，该存储介质中存储有计算机程序，其中，该计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的计算机程序：S10，主控单板确定预定触发条件成立，其中，所述预定触发条件包括以下至少之一：接收到交换单板发送的注册消息、接收到交换单板发送的保活消息、确定在预定时间内未接收到交换单板发送的保活消息、接收到对交换单板进行复位的复位消息；S20，所述主控单板根据所述预定触发条件对应的管理策略生成管理指令并向所述交换单板发送所述管理指令，以实现对所 述交换单板的管理。
可选地，在本实施例中，上述存储介质可以包括但不限于：通用串行总线闪存盘(Universal Serial Bus flash disk，U盘)、ROM、RAM、移动硬盘、磁碟或者光盘等多种可以存储计算机程序的介质。
可选地，本实施例中的示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
实施例4
本实施例提供了一种无CPU交换单板的资源管理方法。本方法是在主控单板上部署一个集中式单板资源管理系统，通过主控单板和交换单板之间的电路接口，采用板间的通信消息交互，使得主控单板能够对PTN设备中所有无CPU交换单板进行管理。
图3是本申请实施例4提供的一种资源管理方案的系统逻辑图，如图4所示，本方法应用于一套完整的软件系统，包括主控单板上的资源管理模块和通信单元模块、交换单板上的通信单元模块、板间的通信链路模块、以及交换芯片状态变更模块等组成。这些模块协同工作，共同完成对交换单板的资源管理。本方法也能够同时管理多块无CPU交换单板的资源。
图4是本申请实施例4提供的一种无CPU交换单板的资源管理方案的管理方法流程图，如图4所示，包括以下步骤：
步骤S4010，PTN设备中插入无CPU交换单板。
步骤S4020，主控单板接收到无CPU交换单板发送的上电信息。
步骤S4030，当主控单板采用本方案的单板资源管理方法成功完成管理时，主控单板对无CPU交换单板进行上电成功应答，并进入步骤S4040。
步骤S4040，无CPU单板开始和主控单板进行保活消息交互，直至交换单板重启或拔出。
步骤S4050，当主控单板采用本方案的单板资源管理方法完成管理失败时，主控单板发起无CPU单板复位。
本方法克服了相关技术中存在的资源管理逻辑复杂、系统维护成本大等问题，不但极大的简化了交换单板的资源管理方法，也为降低交换单板的硬件成本做出指引，进而使得交换单板有更大的产品竞争力。
以下将通过实施例5-8描述单板上电、保活、保活失败、复位的管理流程。本申请的资源管理系统在以下实施例中定义为BRDPROXY系统，并通过代理模块感知到交换单板的现场可编程逻辑门阵列(Field Programmable Gate Array， FPGA)的注册、保活、微动开关状态等信息。
实施例5
本实施例描述单板上电处理流程。当系统接收到交换单板的FPGA发送的注册报文时，就意味着此时有新加单板，此时就需要对单板进行上电操作。同时，考虑到FPGA的版本变化，单板在上电的过程中也应能够自动完成FPGA的本板升级。
图5是本申请实施例5提供的一种无CPU交换单板的上电流程图。如图5所示，包括以下步骤：
步骤S5010：BRDPROXY系统接收到来自交换单板的FPGA的注册消息，注册消息包括消息类型、机架号(shelf)、槽位号(slot)、背板类型、单板ID、FPGA版本等。
步骤S5020：BRDPROXY系统将注册消息中的信息写入到本地数据库。
步骤S5030：BRDPROXY系统获取本地的FPGA版本信息，与接收到的FPGA版本信息进行比较：
如果本地的FPGA版本信息与接收到的FPGA版本信息相同，进入步骤S5050。
如果本地的FPGA版本信息与接收到的FPGA版本信息不同，在本地数据库中保存该单板的FPGA路径后，向交换单板的FPGA下发版本升级异步消息。如果下发成功，进入步骤S5040；如果下发失败再次尝试发送，当超过3次都不成功时，复位无CPU交换单板。
步骤S5040：等待接收来自交换单板的FPGA的升级结果消息：
如果升级成功，进入步骤S5050。
如果升级失败，在本地数据库中保存该交换单板的FPGA的升级次数，再次尝试对FPGA本板进行升级。如果连续3都升级失败，则不再升级，进入步骤S5050。
步骤S5050：初始化交换芯片。向交换芯片管理进程发送芯片初始化同步消息，超时时间为永久等待。当交换芯片管理进程返回异常时，复位无CPU交换单板；当交换芯片管理进程不返回异常时，继续。
步骤S5060：向管理平台上报单板上电信息，包括单板ID、单板物料清单ID(Bill of Material ID，BOMID)、单板印制电路板ID(Printed Circuit Board ID，PCBID)、子架、槽位、子槽信息，并向管理平台上报单板的FPGA版本、PCB版本信息。
步骤S5070：向告警平台上报单板上电信息。
步骤S5080：向交换单板的FPGA发送注册完成消息。FPGA在接收到该消息后，停止发送注册消息，改为发送保活消息。
步骤S5090：启动单板保活定时器。
实施例6
本实施例描述单板保活处理流程。正常情况下，在单板注册完成后，交换单板的FPGA开始向BRDPROXY系统发送保活消息。同时，考虑到单板微动开关的变化，交换单板的FPGA也需要携带单板的微动开关状态信息。
图6是本申请实施例6提供的一种无CPU交换单板的保活流程图。如图6所示，包括以下步骤：
步骤S6010：BRDPROXY系统接收到来自交换单板的FPGA的保活消息，消息包括消息类型、机架号(shelf)、槽位号(slot)、背板类型、单板ID、微动开关状态。
步骤S6020：BRDPROXY系统在本地数据库中查找单板的微动开关状态，与保活消息中的微动开关状态进行比较。
如果本地数据库中查找到的单板的微动开关状态与保活消息中的微动开关状态相同，不做处理。
如果本地数据库中查找到的单板的微动开关状态与保活消息中的微动开关状态不同，当保活消息中的微动开关状态为打开时，向交换单板发送SF关闭同步消息，等待SF关闭完成；当保活消息中的微动开关状态为关闭时，向交换单板发送SF打开同步消息，等待SF打开完成。
步骤S6030：BRDPROXY系统在本地数据库中更新最新的微动开关状态。
实施例7
本实施例描述了保活超时处理流程。异常情况下，当主控单板在规定时间内没有收到无CPU交换板的保活信息时，BRDPROXY系统认为单板异常(掉电、挂起等)，这种情形被称为保活超时。
图7是本申请实施例7提供的一种无CPU交换单板的保活超时流程图。如图7所示，包括以下步骤：
步骤S7010：BRDPROXY系统在规定时间内没有收到无CPU交换单板上报的保活消息。
步骤S7020：BRDPROXY系统向交换单板下发关闭无CPU交换单板的SF 同步消息。如果关闭成功，更新本地的微动开关状态信息，进入步骤S7030。如果关闭失败(包含超时)，进入步骤S7030。
步骤S7030：BRDPROXY系统向告警模块上报单板脱位告警，如果上报失败，记录错误日志。
步骤S7040：BRDPROXY系统根据机架号(shelf)、槽位号(slot)，在本地删除该单板的信息。如果删除失败，记录错误日志。
实施例8
本实施例描述了单板复位处理流程。在一些情况下，用户需要对一个单板进行复位，此时就需要通过网管来对该单板进行复位操作。以下仅描述BRDPROXY系统中对复位消息的处理。
图8是本申请实施例8提供的一种无CPU交换单板的复位流程图。如图8所示，包括以下步骤：
步骤S8010：BRDPROXY系统接收到来自用户的复位消息，复位消息包含消息类型、机架号(shelf)、源槽位号(slot)、目的槽位号(slot)信息。
步骤S8020：BRDPROXY系统根据机架号(shelf)、目的槽位号(slot)，在本地删除该交换单板的信息：
如果删除失败，记录错误日志，继续下一步。
如果删除成功，继续下一步。
步骤S8030：BRDPROXY系统向告警模块上报交换单板复位信息。
如果上报失败，记录错误日志，继续下一步。
如果上报成功，继续下一步。
步骤S8040：BRDPROXY系统向主控的芯片管理进程发送关闭无CPU交换单板的SF同步消息。如果关闭SF失败，记录严重错误日志。
上述的本申请的模块或步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在一些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成多个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本申请不限制于任何特定的硬件和软件结合。

Claims (14)

  1. 一种无中央处理单元CPU交换单板的资源管理方法，包括：
    主控单板确定预定触发条件成立，其中，所述预定触发条件包括以下至少之一：接收到交换单板发送的注册消息、接收到交换单板发送的保活消息、确定在预定时间内未接收到交换单板发送的保活消息、接收到对交换单板进行复位的复位消息；
    所述主控单板根据所述预定触发条件对应的管理策略生成管理指令并向所述交换单板发送所述管理指令。
  2. 根据权利要求1所述的方法，其中，在所述预定触发条件包括接收到所述交换单板发送的所述注册消息的情况下，所述注册消息包括所述交换单板的可编程器件版本信息；
    所述主控单板根据所述预定触发条件对应的管理策略生成管理指令并向所述交换单板发送所述管理指令包括：
    所述主控单板比较所述主控单板本地数据库保存的可编程器件版本信息和所述注册消息中包括的所述交换单板的可编程器件版本信息；
    在通过比较确定所述主控单板本地数据库保存的可编程器件版本信息和所述注册消息中包括的所述交换单板的可编程器件版本信息不同的情况下，所述主控单板生成版本升级异步信息并向所述交换单板发送所述版本升级异步信息，其中，所述版本升级异步信息用于指示所述交换单板对所述交换单板的可编程器件进行版本升级。
  3. 根据权利要求2所述的方法，在所述主控单板生成所述版本升级异步信息并向所述交换单板发送所述版本升级异步信息之后，还包括：
    所述主控单板接收所述交换单板发送的升级结果消息；
    在所述升级结果消息指示升级失败的情况下，所述主控单板重复向所述交换单板发送所述版本升级异步信息。
  4. 根据权利要求3所述的方法，还包括：
    在初始化条件满足的情况下，所述主控单板对所述交换单板中的交换芯片进行初始化，其中，所述初始化条件包括以下之一：
    通过比较确定所述主控单板本地数据库保存的可编程器件版本信息和所述注册消息中包括的所述交换单板的可编程器件版本信息相同；
    所述升级结果消息指示升级成功；
    所述主控单板重复向所述交换单板发送所述版本升级异步信息的次数超过 预定尝试次数。
  5. 根据权利要求4所述的方法，在所述主控单板对所述交换单板中的交换芯片进行初始化之后，还包括：
    所述主控单板向所述交换单板发送注册完成消息，其中，所述注册完成消息用于触发所述交换单板发送保活消息。
  6. 根据权利要求1所述的方法，其中，在所述预定触发条件包括接收到所述交换单板发送的所述保活消息的情况下，所述保活消息包括微动开关状态信息；
    所述主控单板根据所述预定触发条件对应的管理策略生成管理指令并向所述交换单板发送所述管理指令包括：
    所述主控单板比较所述主控单板本地数据库保存的微动开关状态信息和所述保活消息中包括的所述微动开关状态信息；
    在通过比较确定所述主控单板本地数据库保存的所述微动开关状态信息和所述保活消息中包括的所述微动开关状态信息不同的情况下，所述主控单板生成交换结构SF同步信息并向所述交换单板发送所述SF同步信息，其中，在所述保活消息中包括的所述微动开关状态信息为打开的情况下，所述SF同步信息用于指示关闭所述交换单板中的SF，在所述保活消息中包括的所述微动开关状态信息为关闭的情况下，所述SF同步信息用于指示打开所述交换单板中的SF。
  7. 根据权利要求6所述的方法，在所述在通过比较确定所述主控单板本地数据库保存的所述微动开关状态信息和所述保活消息中包括的所述微动开关状态信息不同之后，还包括：
    所述主控单板根据所述保活消息中包括的所述微动开关状态信息更新所述主控单板本地数据库保存的微动开关状态信息。
  8. 根据权利要求1所述的方法，其中，在所述预定触发条件包括确定在预定时间内未接收到所述交换单板发送的所述保活消息或接收到对所述交换单板进行复位的复位消息的情况下，所述主控单板根据所述预定触发条件对应的管理策略生成管理指令并向所述交换单板发送所述管理指令包括：
    所述主控单板生成SF同步信息并向所述交换单板发送所述SF同步信息，其中，所述SF同步信息用于指示关闭所述交换单板中的SF。
  9. 根据权利要求8所述的方法，在确定在预定时间内未接收到所述交换单板发送的所述保活消息或接收到对所述交换单板进行复位的复位消息之后，还包括以下至少之一：
    所述主控单板删除本地数据库中存储的所述交换单板的信息；
    所述主控单板向告警模块上报所述交换单板的通知消息，其中，在确定在预定时间内未接收到所述交换单板发送的所述保活消息的情况下，所述通知消息为所述交换单板的脱位告警，在接收到对所述交换单板进行复位的复位消息的情况下，所述通知消息为所述交换单板的复位通知。
  10. 一种资源管理系统，位于主控单板中，所述资源管理系统设置为：
    确定预定触发条件成立，其中，所述预定触发条件包括以下至少之一：接收到交换单板发送的注册消息、接收到交换单板发送的保活消息、确定在预定时间内未接收到交换单板发送的保活消息、接收到对交换单板进行复位的复位消息；
    根据所述预定触发条件对应的管理策略生成管理指令并向所述交换单板发送所述管理指令。
  11. 根据权利要求10所述的系统，其中，在所述预定触发条件包括接收到所述交换单板发送的所述注册消息的情况下，所述注册消息包括所述交换单板的可编程器件版本信息；
    所述资源管理系统是设置为通过如下方式根据所述预定触发条件对应的管理策略生成管理指令并向所述交换单板发送所述管理指令：
    比较所述主控单板本地数据库保存的可编程器件版本信息和所述注册消息中包括的所述交换单板的可编程器件版本信息；
    在通过比较确定所述主控单板本地数据库保存的可编程器件版本信息和所述注册消息中包括的所述交换单板的可编程器件版本信息不同的情况下，生成版本升级异步信息并向所述交换单板发送所述版本升级异步信息，其中，所述版本升级异步信息用于指示所述交换单板对所述交换单板的可编程器件进行版本升级。
  12. 根据权利要求10所述的系统，其中，在所述预定触发条件包括接收到所述交换单板发送的所述保活消息的情况下，所述保活消息包括微动开关状态信息；
    所述资源管理系统是设置为通过如下方式根据所述预定触发条件对应的管理策略生成管理指令并向所述交换单板发送所述管理指令：
    比较所述主控单板本地数据库保存的微动开关状态信息和所述保活消息中包括的所述微动开关状态信息；
    在通过比较确定所述主控单板本地数据库保存的所述微动开关状态信息和 所述保活消息中包括的所述微动开关状态信息不同的情况下，生成交换结构SF同步信息并向所述交换单板发送所述SF同步信息，其中，在所述保活消息中包括的所述微动开关状态信息为打开的情况下，所述SF同步信息用于指示关闭所述交换单板中的SF，在所述保活消息中包括的所述微动开关状态信息为关闭的情况下，所述SF同步信息用于指示打开所述交换单板中的SF。
  13. 根据权利要求10所述的系统，其中，在所述预定触发条件包括确定在预定时间内未接收到所述交换单板发送的所述保活消息或接收到对所述交换单板进行复位的复位消息的情况下，所述资源管理系统是设置为通过如下方式根据所述预定触发条件对应的管理策略生成管理指令并向所述交换单板发送所述管理指令：
    生成SF同步信息并向所述交换单板发送所述SF同步信息，其中，所述SF同步信息用于指示关闭所述交换单板中的SF。
  14. 一种存储介质，存储有计算机程序，其中，所述计算机程序被设置为运行时执行所述权利要求1至9任一项中所述的无中央处理单元CPU交换单板的资源管理方法。
PCT/CN2019/128671 2018-12-29 2019-12-26 无cpu交换单板的资源管理方法、系统及存储介质 WO2020135578A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811648080.6A CN111385133A (zh) 2018-12-29 2018-12-29 资源管理方法及系统
CN201811648080.6 2018-12-29

Publications (1)

Publication Number Publication Date
WO2020135578A1 true WO2020135578A1 (zh) 2020-07-02

Family

ID=71129693

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/128671 WO2020135578A1 (zh) 2018-12-29 2019-12-26 无cpu交换单板的资源管理方法、系统及存储介质

Country Status (2)

Country Link
CN (1) CN111385133A (zh)
WO (1) WO2020135578A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1665154A (zh) * 2004-03-04 2005-09-07 中兴通讯股份有限公司 一种嵌入式系统带内复位的方法及其装置
EP2093934A4 (en) * 2007-03-29 2010-03-24 Huawei Tech Co Ltd SYSTEM, DEVICE, DEVICE AND METHOD FOR MONITORING MANAGEMENT
CN102346501A (zh) * 2010-07-30 2012-02-08 中兴通讯股份有限公司 一种具有统一机框管理架构的设备及其管理控制方法
CN105337757A (zh) * 2014-08-15 2016-02-17 中兴通讯股份有限公司 线卡管理方法及系统
CN105656711A (zh) * 2014-12-02 2016-06-08 中兴通讯股份有限公司 信号检测方法及装置
CN106487549A (zh) * 2015-08-26 2017-03-08 中兴通讯股份有限公司 与无中央处理器单板通讯的方法及通讯设备

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1299213C (zh) * 2002-09-19 2007-02-07 华为技术有限公司 利用系统板上的cpu进行集中控制处理的方法
CN101097563A (zh) * 2006-06-27 2008-01-02 中兴通讯股份有限公司 一种单板集中管理与控制的实现系统与方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1665154A (zh) * 2004-03-04 2005-09-07 中兴通讯股份有限公司 一种嵌入式系统带内复位的方法及其装置
EP2093934A4 (en) * 2007-03-29 2010-03-24 Huawei Tech Co Ltd SYSTEM, DEVICE, DEVICE AND METHOD FOR MONITORING MANAGEMENT
CN102346501A (zh) * 2010-07-30 2012-02-08 中兴通讯股份有限公司 一种具有统一机框管理架构的设备及其管理控制方法
CN105337757A (zh) * 2014-08-15 2016-02-17 中兴通讯股份有限公司 线卡管理方法及系统
CN105656711A (zh) * 2014-12-02 2016-06-08 中兴通讯股份有限公司 信号检测方法及装置
CN106487549A (zh) * 2015-08-26 2017-03-08 中兴通讯股份有限公司 与无中央处理器单板通讯的方法及通讯设备

Also Published As

Publication number Publication date
CN111385133A (zh) 2020-07-07

Similar Documents

Publication Publication Date Title
US8448162B2 (en) Hitless software upgrades
US9391877B2 (en) System and method for reducing information loss in an aggregated information handling system
US8375363B2 (en) Mechanism to change firmware in a high availability single processor system
CN102185718B (zh) 一种系统升级方法及其装置
WO2017210209A1 (en) Keepalive scheduler in a network device
CN102238093A (zh) 防止业务中断的方法和装置
CN105407475B (zh) 配置文件启用处理方法和eUICC
CN110958151B (zh) 保活检测方法、装置、节点、存储介质及通信系统
CN105577408A (zh) 一种vnfm容灾保护的方法、装置和nfvo
CN110109772B (zh) 一种cpu的重启方法、通信设备及可读存储介质
CN111585835B (zh) 一种带外管理系统的控制方法、装置和存储介质
US7660234B2 (en) Fault-tolerant medium access control (MAC) address assignment in network elements
JP5531487B2 (ja) サーバシステム及びサーバシステムの管理方法
JP2006285443A (ja) オブジェクト救済システム及び方法
EP3474501B1 (en) Network device stacking
WO2020135578A1 (zh) 无cpu交换单板的资源管理方法、系统及存储介质
JP2002049502A (ja) 複数プロセッサシステムにおけるアップデート方式
CN111698157A (zh) 一种链路管理方法、板卡及交换机
CN114189471B (zh) 跨设备链路聚合组主备配置方法、系统、终端及存储介质
CN105871524B (zh) 一种基于tipc协议实现双机热备的方法及系统
JP2009075710A (ja) 冗長化システム
CN107995319A (zh) 虚拟设备配置方法及网络设备
Cisco FIB through MICA messages
CN113961402A (zh) 一种虚拟化集群的管理方法、装置、设备及介质
Cisco Message and Recovery Procedure

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 081121)

122 Ep: pct application non-entry in european phase

Ref document number: 19904558

Country of ref document: EP

Kind code of ref document: A1