WO2017198015A1

WO2017198015A1 - Software upgrading method and apparatus

Info

Publication number: WO2017198015A1
Application number: PCT/CN2017/080295
Authority: WO
Inventors: 邹林君
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-05-17
Filing date: 2017-04-12
Publication date: 2017-11-23
Also published as: CN107395385A

Abstract

The present invention provides a software upgrading method and apparatus. The method comprises: obtaining a software version of a device board from a server according to a preconfigured upgrading policy, so as to obtain a first software version; determining whether the first software version is consistent with a second software version of the current device board; and if the determining result is not, controlling the current device board to update software. By means of the present invention, the problem in the related art of low efficiency of software upgrading caused by manual updating operations of board software is resolved, thereby achieving the effect of improving the upgrading efficiency of board software.

Description

Software upgrade method and device

Technical field

The present invention relates to the field of communications, and in particular to a software upgrade method and apparatus.

Background technique

The upgrade and loading of transport network products has always been the top priority of after-sales work. There are two ways to upgrade traditional transport network products: network management upgrade and command line upgrade.

Network management upgrades include board-level upgrades and batch upgrades. The board level upgrade is performed on a single board as a component. The components such as app/fpga/boot perform the upgrade and load process in sequence. The user configures one of the program files to start upgrading. After the upgrade loading process ends, check the upgrade version is correct. Configure the next component and execute it one by one. The batch upgrade has been improved on the basis of the original board-level upgrade. Users can select multiple boards and multiple components in the NE. After all the program files are configured, multiple boards and multiple files can be downloaded in parallel. Compared with the board-level upgrade, the batch upgrade implements centralized configuration and parallel download of upgrade files. After all the files to be upgraded are configured, one-click startup can be performed to check the final result, which greatly saves users' time.

The general process of the command line upgrade is divided into two steps: 1. Establish communication between the PC and the device board, connect the board through the command line terminal, enable the tftp or ftp server on the PC, and enter the command to transfer the file to be upgraded to the board. Memory; 2, change file permissions, replace the old version file, manually reset and load new files. Check the board version after the board is reset. After the command line is upgraded, multiple update files can be transferred to the board in batches. After multiple component versions are replaced, the board is reset.

There are two problems with the traditional single-board software upgrade method: 1. Whether it is the network management upgrade or the command line upgrade, the user needs a lot of manual operations, and the low upgrade efficiency is far from meeting the needs of the increasingly large engineering applications; The upgraded version check process is cumbersome. After the fault occurs, the cause cannot be analyzed. 2. If the daughter card device is damaged, replacing the new daughter card requires re-upgrading the board program through the command line. The operation is cumbersome.

Software upgrade caused by manual software upgrade of the board in the related technology. The problem of low efficiency has not yet come up with an effective solution.

Summary of the invention

The embodiment of the invention provides a software upgrade method and device, which at least solves the problem that the software upgrade efficiency caused by the manual software upgrade of the board is low in the related art.

According to an embodiment of the present invention, a software upgrade method is provided, including: obtaining a software version of a device board from a server according to a pre-configured upgrade policy, to obtain a first software version; determining the first software version and Whether the second software version of the current device board is consistent; if the judgment result is negative, the current device board is controlled to perform software upgrade.

Optionally, the obtaining, by the server, the software version of the device board from the server, to obtain the first software version, according to the pre-configured upgrade policy, includes: acquiring the software version of the current device board from the server according to a predetermined period; or The full software version of the server is obtained from the server at a predetermined period.

Optionally, before determining whether the first software version is consistent with the second software version of the current device board, the method further includes: sending, by using a specified protocol, a software version query instruction to the current device board, where the specifying The protocol includes at least one of the following: a simple network management protocol snmp, a telnet protocol; and receiving the second software version reported by the current device board.

Optionally, after the software upgrade is performed on the current device board, the method further includes: activating the upgraded device board according to the software activation policy of the device board; wherein the software activation policy includes: After the device is upgraded, the device sends a reset command to the upgraded device to indicate that the upgraded device is activated. After receiving the selection command for the device activation, the device is upgraded. The device board sends a reset command to instruct the upgraded device board to activate.

Optionally, after the software upgrade of the current device board is performed, the method further includes: detecting an upgrade result of the software upgrade of the current device board, and recording a process log of the software upgrade of the current device board.

Optionally, if the current device adds a board, the method further includes: receiving the current device report. The board type of the newly added board and the software version information corresponding to the board type; determining whether there is a software version corresponding to the received software version information in the first software version; if the judgment result is yes And determining whether the first software version is consistent with the software version of the current device board, and if the determination result is negative, controlling the current device board to perform software upgrade; if the determination result is no, The server obtains a software version corresponding to the newly added board, and controls the current board to perform software upgrade.

According to another embodiment of the present invention, a software upgrade apparatus is provided, including: an obtaining module, configured to acquire a software version of a device board from a server according to a pre-configured upgrade policy, to obtain a first software version; The determining module is configured to determine whether the first software version is consistent with the second software version of the current device board, and the control module is configured to control the current device board to perform software upgrade if the determination result is negative.

Optionally, the device further includes: a sending module, configured to send the software version to the current device board by using a specified protocol before determining whether the first software version is consistent with the second software version of the current device board Querying the command, wherein the specified protocol includes at least one of the following: a simple network management protocol, snmp, and a telnet protocol; and the first receiving module is configured to receive the second software version reported by the current device.

Optionally, the device further includes: an activation module, configured to: after the software upgrade of the current device board is controlled, activate the upgraded device board according to the software activation policy of the device board; wherein the software The activation policy includes: after the software upgrade of the current device board, sending a reset command to the upgraded device board to indicate that the upgraded device board is activated; or receiving the device board activation operation. And after the selecting the command, sending a reset command to the upgraded device board to indicate that the upgraded device board is activated; or the device further includes: a detecting module, configured to control the current device board After the software is upgraded, check the upgrade result of the software upgrade of the current device board, and record the process log of the software upgrade of the current device board.

Optionally, the device further includes: a second receiving module, configured to receive a board type of the newly added board and a pair of the board type when the current device adds a board The second software module is configured to determine whether there is a software version corresponding to the received software version information in the first software version; the first processing module is set to be in the case that the determination result is yes And determining whether the first software version is consistent with the software version of the current device board, and if the determination result is negative, controlling the current device board to perform software upgrade; and the second processing module is set to determine the result. If not, the software version corresponding to the new board is obtained from the server, and the current board is controlled to perform software upgrade.

According to still another embodiment of the present invention, a storage medium is also provided. The storage medium is arranged to store program code for performing the following steps:

Obtain the software version of the device board from the server to obtain the first software version according to the pre-configured upgrade policy.

Determining whether the first software version is consistent with the second software version of the current device board;

If the result of the determination is no, the current device board is controlled to perform software upgrade.

According to the embodiment of the present invention, the software version of the device board is obtained from the server according to the pre-configured upgrade policy to obtain the first software version; and the second software version of the current software board is consistent with the second software version of the current device board; If the result of the determination is negative, the current device board is controlled to perform software upgrade, which solves the problem of low software upgrade efficiency caused by the manual software upgrade of the board in the related art, thereby improving the software upgrade of the board. The effect of efficiency.

DRAWINGS

The drawings described herein are intended to provide a further understanding of the invention, and are intended to be a part of the invention. In the drawing:

1 is a flow chart of a software upgrade method according to an embodiment of the present invention;

2 is a schematic structural diagram of a software upgrading apparatus according to an embodiment of the present invention;

3 is a flowchart (1) of a software upgrade method according to an embodiment of the present invention;

4 is a flowchart (2) of a software upgrade method according to an embodiment of the present invention;

FIG. 5 is a structural block diagram of a software upgrading apparatus according to an embodiment of the present invention; FIG.

6 is a structural block diagram (1) of a software upgrading apparatus according to an embodiment of the present invention;

7 is a structural block diagram (2) of a software upgrading apparatus according to an embodiment of the present invention;

FIG. 8 is a structural block diagram (3) of a software upgrading apparatus according to an embodiment of the present invention; FIG.

FIG. 9 is a structural block diagram of a software upgrading apparatus according to an embodiment of the present invention (4);

FIG. 10 is a structural block diagram (5) of a software upgrading apparatus according to an embodiment of the present invention.

detailed description

The invention will be described in detail below with reference to the drawings in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.

It is to be understood that the terms "first", "second" and the like in the specification and claims of the present invention are used to distinguish similar objects, and are not necessarily used to describe a particular order or order.

Example 1

A software upgrade method is provided in this embodiment. FIG. 1 is a flowchart of a software upgrade method according to an embodiment of the present invention. As shown in FIG. 1 , the process includes the following steps:

Step S102: Obtain a software version of the device board from the server according to the pre-configured upgrade policy, to obtain a first software version.

Step S104: Determine whether the first software version is consistent with the second software version of the current device board.

In step S106, if the determination result is no, the current device board is controlled to perform software upgrade.

Optionally, in this embodiment, the application scenario of the software upgrade method includes, but is not limited to, a board software version upgrade, in which the device board is obtained from the server according to the pre-configured upgrade policy. The software version is obtained to obtain the first software version; whether the first software version is consistent with the second software version of the current device board; if the judgment result is no Control the current device board for software upgrade. That is to say, in this embodiment, the automatic upgrade is implemented by using the pre-configured upgrade policy, and the software upgrade efficiency caused by the manual operation of the board software upgrade is low. The problem is that the effect of improving the software upgrade efficiency of the board is achieved.

Optionally, the software upgrade method may be applied to the structural framework diagram as shown in FIG. 2, and the server uses the device vendor version server as an example. These include:

Device 1: The policy control device provides a UI interface to the user to configure an update activation policy, saves the update policy data xml file to the local, and periodically sends a message to the device 2 and the device 3 according to the update frequency policy.

Device 2: The network repository queries the download device, and can connect to the device vendor version server, query the version file through the protocol such as ftp or http, and download the version file to the local version library.

Device 3: device communication interface device, which can directly integrate the traditional network management system or the command line system, send the query version command to the device board through the snmp or telnet mode, store the device version report to the local, and transmit the version through ftp or tftp protocol. The file is sent to the board and a reset command is sent to control the board reset.

Device 4: The upgrade result check recording device, check the upgraded device version report and the local version library, record the automation result to the log file, and notify the user of the upgrade result through the popup window or the UI interface.

The present embodiment will be exemplified below with reference to specific examples.

This embodiment provides a software upgrade method, which can effectively solve the technical problems existing in the background art. You only need to configure the update and activation policies. All the board update processes and the newly installed board version acquisition process can be automated.

Among them, it mainly includes the following steps:

A. The user configures an automatic upgrade policy and an activation policy through the UI interface.

B. The network repository queries the download device, and periodically queries the device vendor version server for the version update according to the configuration of the policy control device. If there is an update, the version file is obtained. Save to the upgrade agent module locally.

C. The device communication interface device obtains the version of the current device board from all the devices. When the device is inconsistent, the control device upgrades the board version and resets the activation board according to the activation policy.

D. Check the recording device of the upgrade result, wait for the upgrade result to check the upgrade result, record the upgrade process log, and push the upgrade result to the user.

E. When the device has a newly installed board, the device is automatically reported to the device communication interface device. After the device updates the corresponding version file to the device version server, the newly installed board of the control device is upgraded and started with this new version file.

The embodiment can solve the problem that the traditional method is inefficient and the manual operation is cumbersome, and the efficiency of the board program upgrade loading and version checking is improved, and the burden on the user is reduced.

In an optional implementation manner, the foregoing step S102 includes the following steps:

Step S11: Obtain a software version of the current device board from the server according to a predetermined period; or

In step S12, all software versions of the server are obtained from the server according to a predetermined period.

In the optional implementation manner, the latest software version of the latest software is automatically obtained through the board software version update policy, and the automatic upgrade of the board software is further implemented.

In an optional implementation manner, before the step S104, the following steps are further included:

Step S21: Send a software version query instruction to the current device board by using a specified protocol, where the specified protocol includes at least one of the following: a simple network management protocol snmp, a telnet protocol;

Step S22: Receive the second software version reported by the current device board.

In the optional implementation, the software version of the current device board is queried by the current device, and the software version of the current device board is compared with the latest software version obtained from the server, and The comparison results in automatic software upgrades.

Optionally, after the foregoing step S106, the following steps are further included:

In step S31, the upgraded device board is activated according to the software activation policy of the device board.

The software activation policy includes: after the software upgrade of the current device board, the device sends a reset command to the upgraded device board to indicate that the upgraded device board is activated; or, the device board is received. After the operation selection command is activated, a reset command is sent to the upgraded device board to indicate that the upgraded device board is activated.

After the software upgrade is performed on the current device board, the upgraded software board is activated according to the software activation policy of the board. The upgraded software board can run the upgraded software version.

Step S41: The process result of the software upgrade of the current device board is verified, and the process log of the software upgrade of the current device board is recorded.

The process log of the software upgrade is performed on the current device board obtained in step S41, so that the process of software upgrade of the device board can be tracked in real time.

In an optional implementation manner, if a board is added to the current device, the following steps are also included:

Step S51: Receive the board type of the newly added board and the software version information corresponding to the board type.

Step S52, determining whether there is a software version corresponding to the received software version information in the first software version;

Step S54: If the determination result is yes, determine whether the first software version is consistent with the software version of the current device board, and if the determination result is no, control the current device board to perform software upgrade;

In step S55, if the determination result is negative, the software version corresponding to the newly added board is obtained from the server, and the current board is controlled to perform software upgrade.

In this optional mode, the software can be automatically upgraded in time when the board is added to the current device.

Alternative embodiment 1

The premise of the automatic upgrade is to manually configure the update policy, and the user configures the update policy and the activation policy through the UI interface.

The update policy can be configured as the simplest update and the most complete update: the simplest update, that is, only the version of the board type of all the devices of the agent module is downloaded. The most complete update is to download the version of all the device boards of the device vendor.

The activation policy can be configured as automatic activation and manual activation: automatic activation, no need to manually determine the upgrade agent module to update the version file to the board, directly send a reset command to the board to notify the board to reset and activate; when manually activated, you need to wait for the user to After the UI interface or the pop-up interface is clicked, the reset command is sent to the board to notify the board to reset.

The specific process of automating the upgrade of a board includes the following steps:

Step S61: The agent module is upgraded, and the update policy data xml stored by the device 1 is read to obtain an update policy. If the policy is the simplest update, the process proceeds to step S62. If the policy is the most complete update, the process proceeds to step S63.

Step S62: The device 3 is configured to obtain a board of the current device, store the version information of the board to the local device version report, and connect to the device version server through the device 2, and comprehensively compare the device version report, the local version database and the server version library, if any Update to ftp or http to download to the local repository. Go to step S64.

Step S63: The device 2 is connected to the device vendor version server, and checks all versions. If the local version does not exist or the version number is inconsistent, the device is downloaded to the local version repository through ftp or http. Go to step S64.

Step S64: The agent module is upgraded, and the device version report and the local version database obtained by the device 3 are compared. For the board whose current version is inconsistent with the version of the local version, the process proceeds to step S65.

Step S65: The agent module control device 3 is upgraded, and the new version is transferred to the device board memory by using ftp or tftp using the snmp or telnet tool. According to the activation strategy, if The activation policy is automatic activation, and the process proceeds to step S66; if the activation policy is manual activation, the process proceeds to step S67.

Step S66: The agent module control device 3 is upgraded, and the reset message is directly sent to the board by using the snmp or the telnet is sent to the board to input the reboot, and the board is reset and activated, and the process proceeds to step S68.

Step S67: The agent module is upgraded, and the user is required to reset the active board through the UI interface or the popup window. After the user confirms, the user can use the snmp to directly send a reset message to the board or telnet to the board to input the reboot, and notify the board to reset. Go to step S68.

Step S68: After the upgrade agent module waits for a certain period of time, the device 3 obtains the board of the current device, updates the board version information to the local device version report, compares the device version report with the local version, and checks the version information of the upgraded board. Save the upgrade log to a local file and notify the user of the upgrade result through the UI interface or popup window.

It should be noted that, in the step S61 to step S68, the part of the device board upgrade process may refer to step S301 to step S310 in FIG. 3 .

Alternative embodiment 2

The process of automatically obtaining a version of a newly installed board includes the following steps:

Step S71: When the device has a new board installed, the device sends a new board type and version message to the device 3 of the upgrade agent module, and the device 3 saves the message to the locally added board list file. The upgrade agent module searches for the local version based on the newly added board list file. If the corresponding board version file does not go to step S72, if the corresponding board version file exists, the process proceeds to step S73.

Step S72: The upgrade agent module is connected to the device version server to query the version of the new board in the newly added board list file, and the version file is downloaded to the local version through ftp or http, and the process proceeds to step S73.

Step S73: The agent module is upgraded, and the newly added board list file and the local version library are compared. If the version is inconsistent, the process proceeds to step S74.

Step S74: The agent module control device 3 is upgraded, and the new version is transferred to the device board memory in the ftp or tftp mode by using the snmp or telnet tool, and the process proceeds to step S75.

Step S75: The agent module control device 3 is upgraded, and the reset message is directly sent to the board by using the snmp or the telnet is sent to the board to input the reboot, and the board is reset and activated, and the process proceeds to step S76.

Step S76: After the upgrade agent module waits for a certain period of time, the device 3 is configured to query the version information of the board in the new board list file, update the version information to the newly added board list file, and compare the newly added board list file and the local version. The library checks the upgraded board version information, saves the upgrade log to a local file, and notifies the user of the upgrade result through the UI interface or popup window.

It should be noted that a part of the process of automatically acquiring the version of the newly installed board involved in the above steps S71 to S76 may refer to S401 to S409 in FIG. 4 .

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, The optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present invention.

Example 2

In the embodiment, a software upgrade device is also provided, which is used to implement the above-mentioned embodiments and preferred embodiments, and has not been described again. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

FIG. 5 is a structural block diagram of a software upgrading apparatus according to an embodiment of the present invention. As shown in FIG. 5, the apparatus includes:

1) The obtaining module 52 is configured to obtain a software version of the device board from the server according to the pre-configured upgrade policy, to obtain the first software version;

2) The first determining module 54 is configured to determine the first software version and the current device board Whether the second software version is consistent;

3) The control module 56 is configured to control the current device board to perform software upgrade if the determination result is negative.

Optionally, in this embodiment, the application scenario of the software upgrade device includes, but is not limited to, a board software version upgrade. In the application scenario, the device board is obtained from the server according to the pre-configured upgrade policy. The software version is used to obtain the first software version; whether the first software version is consistent with the second software version of the current device board; if the determination result is no, the current device board is controlled to perform software upgrade. That is to say, in this embodiment, the automatic upgrade is implemented by using the pre-configured upgrade policy, and the software upgrade efficiency caused by the manual operation of the board software upgrade is low. The problem is that the effect of improving the software upgrade efficiency of the board is achieved.

In an alternative embodiment, FIG. 6 is a structural block diagram (1) of a software upgrading apparatus according to an embodiment of the present invention. As shown in FIG. 6, the obtaining module 52 includes:

1) The first obtaining unit 62 is configured to acquire the software version of the current device board from the server according to a predetermined period; or, the second acquiring unit is equivalent to replace the first acquiring unit, and the second acquiring unit is configured to follow the predetermined period from The server obtains the full software version of the server.

In an alternative embodiment, FIG. 7 is a structural block diagram (2) of a software upgrading apparatus according to an embodiment of the present invention. As shown in FIG. 7, the apparatus includes: in addition to the module shown in FIG.

The sending module 72 is configured to send a software version query instruction to the current device board by using a specified protocol before determining whether the first software version is consistent with the second software version of the current device board, where the specified protocol includes At least one of the following: simple network management protocol snmp, telnet protocol;

2) The first receiving module 74 is configured to receive the second software version reported by the current device board.

In an alternative embodiment, FIG. 8 is a structural block diagram (3) of a software upgrading apparatus according to an embodiment of the present invention. As shown in FIG. 8, the apparatus includes, in addition to the module shown in FIG.

1) The activation module 82 is configured to activate the upgraded device board according to the software activation policy of the device board after the software upgrade of the current device board is performed;

After the software upgrade is performed on the current device board, the upgraded device board is activated according to the software activation policy of the board. The upgraded board can run the upgraded software version.

In an alternative embodiment, FIG. 9 is a structural block diagram (4) of a software upgrading apparatus according to an embodiment of the present invention. As shown in FIG. 9, the apparatus includes, in addition to the module shown in FIG.

The detection module 92 is configured to detect the upgrade result of the software upgrade of the current device board after the software upgrade of the current device board is performed, and record the process log of the software upgrade of the current device board.

The process log of the software upgrade of the current device board obtained by the above device enables real-time tracking of the software upgrade process of the device board.

In an alternative embodiment, FIG. 10 is a structural block diagram (5) of a software upgrading apparatus according to an embodiment of the present invention. As shown in FIG. 10, the apparatus includes: in addition to the module shown in FIG.

1) The second receiving module 1002 is configured to receive the board type of the newly added board and the software version letter corresponding to the board type when the current device adds a board. interest;

2) The second determining module 1004 is configured to determine whether there is a software version corresponding to the received software version information in the first software version;

3) The first processing module 1006 is configured to determine whether the software version of the first software version and the current device board are consistent, and if the determination result is negative, control the current device. The board is upgraded with software.

4) The second processing module 1008 is configured to obtain a software version corresponding to the newly added board and control the current board to perform software upgrade if the determination result is negative.

It should be noted that each of the above modules may be implemented by software or hardware. For the latter, the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination. The forms are located in different processors.

Example 3

Embodiments of the present invention also provide a storage medium. Optionally, in the embodiment, the foregoing storage medium may be configured to store program code for performing the following steps:

S1. Obtain a software version of the device board from the server according to the pre-configured upgrade policy to obtain the first software version.

S2, determining whether the first software version is consistent with the second software version of the current device board;

S3. If the judgment result is negative, the current device board is controlled to perform software upgrade.

Optionally, in this embodiment, the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory. A variety of media that can store program code, such as a disc or a disc.

Optionally, in the embodiment, the processor performs the above steps S1, S2, and S3 according to the stored program code in the storage medium.

For example, the specific examples in this embodiment may refer to the examples described in the foregoing embodiments and the optional embodiments, and details are not described herein again.

It will be apparent to those skilled in the art that the various modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.

The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Industrial applicability

The foregoing technical solution provided by the embodiment of the present invention may be applied to the software upgrade process, and the software version of the device board is obtained from the server according to the pre-configured upgrade policy to obtain the first software version; the first software version and the current software version are determined. Whether the second software version of the board is the same. If the result of the judgment is no, the current device board is controlled to perform software upgrade, which solves the software upgrade efficiency caused by the manual software upgrade of the board. The low problem has the effect of improving the efficiency of the board software upgrade.

Claims

A software upgrade method, including:

Obtain the software version of the device board from the server to obtain the first software version according to the pre-configured upgrade policy.

Determining whether the first software version is consistent with the second software version of the current device board;

If the result of the determination is no, the current device board is controlled to perform software upgrade.
The method of claim 1, wherein the obtaining the software version of the device board from the server according to the pre-configured upgrade policy to obtain the first software version comprises:

Obtaining the software version of the current device board from the server according to a predetermined period; or

The full software version of the server is obtained from the server in accordance with a predetermined period.
The method of claim 1, wherein before determining whether the first software version and the second software version of the current device board are consistent, the method further comprises:

Sending a software version query instruction to the current device board by using a specified protocol, where the specified protocol includes at least one of the following: a simple network management protocol snmp, a telnet protocol;

Receiving the second software version reported on the current device board.
The method of claim 1, further comprising: after controlling the software upgrade of the current device board:

Activate the upgraded device board according to the software activation policy of the board.

The software activation policy includes: after the software upgrade of the current device board, directly sending a reset instruction to the upgraded device board to indicate the upgraded The device board is activated. After receiving the selection command of the device board activation operation, the device sends a reset command to the upgraded device board to indicate that the upgraded device board is activated.
The method of claim 1, further comprising: after controlling the software upgrade of the current device board:

Check the upgrade result of the software upgrade of the current device board, and record the process log of the software upgrade of the current device board.
The method according to any one of claims 1 to 5, wherein, in the case that a board is added to the current device, the method further includes:

Receives the board type of the newly added board and the software version information corresponding to the board type.

Determining whether there is a software version corresponding to the received software version information in the first software version;

If the result of the determination is yes, it is determined whether the first software version is consistent with the software version of the current device board, and if the determination result is no, the current device board is controlled to perform software upgrade;

If the result of the determination is no, the software version corresponding to the newly added board is obtained from the server, and the current device board is controlled to perform software upgrade.
A software upgrade device, comprising:

Obtaining a module, configured to obtain a software version of the device board from the server according to the pre-configured upgrade policy, to obtain the first software version;

The first judging module is configured to determine whether the first software version is consistent with the second software version of the current device board;

The control module is configured to control the current device board to perform software upgrade if the determination result is negative.
The apparatus of claim 7 wherein said apparatus further comprises:

a sending module, configured to send a software version query instruction to the current device board by using a specified protocol, before determining whether the first software version is consistent with the second software version of the current device board, where the specified protocol includes At least one of the following: simple network management protocol snmp, telnet protocol;

The first receiving module is configured to receive the second software version reported by the current device board.
The apparatus of claim 7 wherein said apparatus further comprises:

The activation module is configured to activate the upgraded device board according to the software activation policy of the device board after the software upgrade is performed on the current device board.

The software activation policy includes: after the software upgrade of the current device board, sending a reset command to the upgraded device board to indicate that the upgraded device board is activated; or After the device board is activated, the device sends a reset command to the upgraded device board to indicate that the upgraded device board is activated. Alternatively, the device further includes:

The detection module is configured to check the upgrade result of the software upgrade of the current device board after the software upgrade of the current device board is performed, and record the process log of the software upgrade of the current device board.
The apparatus according to any one of claims 7 to 9, wherein the apparatus further comprises:

The second receiving module is configured to receive the board type of the newly added board and the software version letter corresponding to the board type when the current device adds a board. interest;

a second determining module, configured to determine whether a software version corresponding to the received software version information exists in the first software version;

The first processing module is configured to determine whether the first software version is consistent with the software version of the current device board, and if the determination result is negative, the current device list is controlled. Board for software upgrades;

The second processing module is configured to obtain a software version corresponding to the newly added board and control the current device board to perform software upgrade when the determination result is negative.