CN107395385A - Method for upgrading software and device - Google Patents
Method for upgrading software and device Download PDFInfo
- Publication number
- CN107395385A CN107395385A CN201610327571.5A CN201610327571A CN107395385A CN 107395385 A CN107395385 A CN 107395385A CN 201610327571 A CN201610327571 A CN 201610327571A CN 107395385 A CN107395385 A CN 107395385A
- Authority
- CN
- China
- Prior art keywords
- board
- software
- software version
- upgrade
- version
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
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
-
- 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/02—Standardisation; Integration
- H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Stored Programmes (AREA)
Abstract
本发明提供了一种软件升级方法及装置。其中，该方法包括：根据预先配置的升级策略，从服务器获取设备单板的软件版本，以得到第一软件版本；判断该第一软件版本和当前设备单板的第二软件版本是否一致；在判断结果为否的情况下，控制该当前设备单板进行软件升级。通过本发明，解决了相关技术中通过手工操作进行单板软件升级所造成的软件升级效率较低的问题，进而达到了提高单板软件升级效率的效果。
The invention provides a software upgrading method and device. Wherein, the method includes: according to a pre-configured upgrade strategy, obtaining the software version of the equipment single board from the server to obtain the first software version; judging whether the first software version is consistent with the second software version of the current equipment single board; If the judging result is negative, control the single board of the current device to upgrade the software. The present invention solves the problem of low software upgrade efficiency caused by manual operation of the single board software upgrade in the related art, and further achieves the effect of improving the single board software upgrade efficiency.
Description
Technical Field
The invention relates to the field of communication, in particular to a software upgrading method and device.
Background
The upgrading and loading of the transmission network products are always the most important of after-sale work, and the traditional upgrading of the transmission network products has two modes: network management upgrading and command line upgrading.
The network management upgrading comprises board-level upgrading and batch upgrading. The board-level upgrading takes a single board as a unit, the components such as app/fpga/boot and the like sequentially execute upgrading and loading processes, a user configures a certain program file to start upgrading, and after the upgrading and loading processes are finished, the next component is configured after the upgrading version is checked to be correct, and the upgrading and loading processes are sequentially executed. The batch upgrading is improved on the basis of the original board-level upgrading, and a user can independently select a plurality of single boards and a plurality of components in a network element, and after all program files are configured, the parallel downloading of the plurality of single boards and the plurality of files is realized. Compared with board-level upgrading, the batch upgrading realizes the centralized configuration and parallel downloading of the upgrading files, only needs to configure all the files to be upgraded, starts by one key, checks the final result, and greatly saves the time of a user.
The general process of command line upgrading is divided into two steps: 1. establishing communication between a PC and a single board of equipment, connecting the single board through a command line terminal, starting a tftp or ftp server on the PC, inputting a command and transmitting a version file to be upgraded to a single board memory; 2. and changing file authority, replacing the old version file, and manually resetting and loading the new file. And after the single board is reset, checking the version of the single board. The command line upgrading can also transmit a plurality of update files to the single board in batch, and after a plurality of component versions are replaced, the single board is reset in a unified mode.
The traditional single board software upgrading method has two problems: 1. whether the network management upgrading or the command line upgrading is carried out, a large amount of manual operation is required for a user, and the low upgrading efficiency of the network management upgrading or the command line upgrading is far from meeting the requirement of increasingly huge engineering application; meanwhile, the checking process of the upgraded version is complicated, and the reason cannot be analyzed after the version fails; 2. if the daughter card device is damaged, the program of the single board needs to be upgraded again through a command line when the daughter card is replaced, and the operation is complicated.
Aiming at the problem of low software upgrading efficiency caused by manual operation of single board software upgrading in the related art, no effective solution is provided.
Disclosure of Invention
The embodiment of the invention provides a software upgrading method and a software upgrading device, which at least solve the problem of low software upgrading efficiency caused by manual operation of single board software upgrading in the related technology.
According to an embodiment of the present invention, there is provided a software upgrading method including: acquiring a software version of the equipment single board from a server according to a pre-configured upgrading strategy to obtain a first software version; judging whether the first software version is consistent with a second software version of the current equipment single board; and controlling the current equipment single board to carry out software upgrading under the condition that the judgment result is negative.
Optionally, the obtaining, according to a preconfigured upgrade policy, a software version of the device board from the server to obtain a first software version includes: acquiring the software version of the current equipment single board from a server according to a preset period; or, all software versions of the server are acquired from the server according to a preset 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 a software version query instruction to the current equipment single board through a specified protocol, wherein the specified protocol comprises at least one of the following: simple network management protocol (snmp) and telnet protocol; and receiving the second software version reported by the current equipment single board.
Optionally, after controlling the current device board to perform software upgrade, the method further includes: activating the upgraded equipment single board according to the software activation strategy of the equipment single board; wherein the software activation policy comprises: after the software of the current equipment single board is upgraded, a reset instruction is directly sent to the upgraded equipment single board to indicate the upgraded equipment single board to be activated; or after receiving a selection instruction of an equipment single board activation operation, sending a reset instruction to the upgraded equipment single board to instruct the upgraded equipment single board to activate.
Optionally, after controlling the current device board to perform software upgrade, the method further includes: detecting the upgrading result of the current equipment single board after software upgrading, and recording the process log of the current equipment single board for software upgrading.
Optionally, when a new board is added to the current device, the method further includes: receiving a veneer type of a newly added veneer reported by current equipment and software version information corresponding to the veneer type; judging whether a software version corresponding to the received software version information exists in the first software version or not; if the judgment result is yes, judging whether the first software version is consistent with the software version of the current equipment single board, and if the judgment result is no, controlling the current equipment single board to carry out software upgrading; and under the condition that the judgment result is negative, acquiring a software version corresponding to the newly added single board from the server, and controlling the current single board to carry out software upgrading.
According to another embodiment of the present invention, there is provided a software upgrading apparatus including: the acquisition module is used for acquiring the software version of the equipment single board from the server according to a preset upgrading strategy so as to obtain a first software version; the first judging module is used for judging whether the first software version is consistent with the second software version of the current equipment single board; and the control module is used for controlling the current equipment single board to carry out software upgrading under the condition that the judgment result is negative.
Optionally, the apparatus further comprises: a sending module, configured to send a software version query instruction to a current device board through a specified protocol before determining whether the first software version is consistent with a second software version of the current device board, where the specified protocol includes at least one of the following: simple network management protocol (snmp) and telnet protocol; a first receiving module, configured to receive the second software version reported by the current device board.
Optionally, the apparatus further comprises: the activation module is used for activating the upgraded equipment single board according to the software activation strategy of the equipment single board after controlling the current equipment single board to carry out software upgrade; wherein the software activation policy comprises: after the software of the current equipment single board is upgraded, a reset instruction is directly sent to the upgraded equipment single board to indicate the upgraded equipment single board to be activated; or after receiving a selection instruction of an equipment single board activation operation, sending a reset instruction to the upgraded equipment single board to instruct the upgraded equipment single board to activate; alternatively, the apparatus further comprises: and the detection module is used for detecting the upgrading result of the current equipment single board after the current equipment single board is controlled to carry out software upgrading, and recording the process log of the current equipment single board for carrying out software upgrading.
Optionally, the apparatus further comprises: a second receiving module, configured to receive, when a newly added board is added to a current device, a board type of the newly added board and software version information corresponding to the board type, which are reported by the current device; the second judgment module is used for judging whether the first software version has a software version corresponding to the received software version information; the first processing module is used for judging whether the first software version is consistent with the software version of the current equipment single board or not under the condition that the judgment result is yes, and controlling the current equipment single board to carry out software upgrading under the condition that the judgment result is no; and the second processing module is used for acquiring the software version corresponding to the newly added single board from the server and controlling the current single board to carry out software upgrading under the condition that the judgment result is negative.
According to still another embodiment of the present invention, there is also provided a storage medium. The storage medium is configured to store program code for performing the steps of:
acquiring a software version of the equipment single board from a server according to a pre-configured upgrading strategy to obtain a first software version;
judging whether the first software version is consistent with a second software version of the current equipment single board;
and controlling the current equipment single board to carry out software upgrading under the condition that the judgment result is negative.
According to the invention, the software version of the equipment single board is obtained from the server according to the pre-configured upgrading strategy so as to obtain a first software version; judging whether the first software version is consistent with a second software version of the current equipment single board; and under the condition that the judgment result is negative, controlling the current equipment single board to carry out software upgrading, solving the problem of low software upgrading efficiency caused by carrying out single board software upgrading through manual operation in the related technology, and further achieving the effect of improving the single board software upgrading efficiency.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
FIG. 1 is a flow diagram of a method for upgrading software according to an embodiment of the invention;
FIG. 2 is a schematic structural diagram of a software upgrading apparatus according to an embodiment of the present invention;
FIG. 3 is a flow chart of a software upgrade method according to an embodiment of the present invention;
FIG. 4 is a flow chart of a software upgrade method according to an embodiment of the present invention (two);
fig. 5 is a block diagram of a software upgrading apparatus according to an embodiment of the present invention;
FIG. 6 is a block diagram (one) of the software upgrading apparatus according to the embodiment of the present invention;
fig. 7 is a block diagram (two) of the configuration of the software upgrading apparatus according to the embodiment of the present invention;
fig. 8 is a block diagram (three) of the structure of a software upgrading apparatus according to an embodiment of the present invention;
fig. 9 is a block diagram (iv) of the software upgrading apparatus according to the embodiment of the present invention;
fig. 10 is a block diagram (v) of the software upgrading apparatus according to the embodiment of the present invention.
Detailed Description
The invention will be described in detail hereinafter with reference to the accompanying drawings in conjunction with embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.
Example 1
In this embodiment, a software upgrading method is provided, and fig. 1 is a flowchart of a software upgrading method according to an embodiment of the present invention, as shown in fig. 1, the flowchart includes the following steps:
step S102, acquiring a software version of the equipment single board from a server according to a preset upgrading strategy to obtain a first software version;
step S104, judging whether the first software version is consistent with the second software version of the current equipment single board;
and step S106, controlling the current equipment single board to carry out software upgrading under the condition that the judgment result is negative.
Optionally, in this embodiment, the application scenarios of the software upgrading method include, but are not limited to: in the single board software version upgrading, under the application scene, acquiring the software version of the equipment single board from the server according to a preset upgrading strategy to obtain a first software version; judging whether the first software version is consistent with a second software version of the current equipment single board; and controlling the current equipment single board to carry out software upgrading under the condition that the judgment result is negative. That is to say, the present embodiment implements automatic upgrade through a preconfigured upgrade policy, and does not need manual upgrade of board software, thereby solving the problem of low software upgrade efficiency caused by manual upgrade of board software in the related art, and achieving the effect of improving board software upgrade efficiency.
Optionally, the software upgrading method may be applied to the structural framework schematic diagram shown in fig. 2, where the server takes an equipment provider version server as an example. Which comprises the following steps:
the device 1: and the strategy control device provides a UI (user interface) for configuring an updating activation strategy for a user, stores the updating strategy data xml file to the local, and regularly sends messages to the device 2 and the device 3 according to the updating frequency strategy.
The device 2: the network version library query downloading device can be connected with an equipment version server, and is used for querying the version file and downloading the version file to the local version library for storage through protocols such as ftp or http.
Device 3: the device communication interface device can directly integrate the traditional network management or command line system, sends a version query command to the device single board in a snmp or telnet mode, stores a device version report to the local, transmits a version file to the single board through an ftp or tftp protocol, and sends a reset instruction to control the single board to reset and activate.
The device 4: and the updating result checking and recording device is used for checking the updated equipment version report and the local version library, recording the automatic result to a log file, and informing the user of the updating result through a popup window or a UI (user interface).
The present embodiment will be described below with reference to specific examples.
The embodiment provides a method for upgrading software, which can effectively solve the technical problems in the background technology. The user only needs to configure the updating and activating strategy, and the updating process of all the equipment single boards and the obtaining process of the version of the newly installed single board can be automated.
The method mainly comprises the following steps:
A. and the user configures the automatic upgrading strategy and the activation strategy through the UI interface.
B. The network version library inquiry downloading device inquires the version updating condition of the equipment version server periodically according to the configuration condition of the strategy control device, and if the version updating condition exists, the obtained version file is stored to the local upgrading agent module.
C. The equipment communication interface device obtains the current equipment single board version from all the equipment, compares the current equipment single board version with the local version, controls the equipment to upgrade the single board version when the inconsistency is found, and resets and activates the upgraded single board according to the activation strategy.
D. And the upgrading result checking and recording device is used for checking the upgrading result after the upgrading is finished, recording the log of the upgrading process and pushing the upgrading result to the user.
E. When the equipment has a new installation single board, the equipment communication interface device is actively reported, and after the equipment communication interface device updates the corresponding version file to the equipment manufacturer version server, the equipment new installation single board is controlled to be upgraded and started by using the new version file.
The problems of low efficiency and complex manual operation of the traditional method can be solved through the embodiment, the efficiency of upgrading, loading and version checking of the single board program is improved, and the burden of a user is reduced.
In an optional embodiment, the step S102 includes the following steps:
step S11, acquiring the software version of the current equipment single board from the server according to the preset period; or,
in step S12, all software versions of the server are acquired from the server at a predetermined cycle.
In this optional embodiment, the latest partial or all software versions are automatically obtained through the single board software version update policy, so as to further achieve the effect of automatically upgrading the single board software.
In an optional embodiment, before the step S104, the following steps are further included:
step S21, sending a software version query instruction to the current device board through a specified protocol, where the specified protocol includes at least one of the following: simple network management protocol (snmp) and telnet protocol;
step S22, receiving the second software version reported by the current device board.
In this optional embodiment, the software version of the current device board is queried for the current device board through a specified protocol, so that the software version of the current device board can be compared with the latest software version obtained from the server according to the obtained software version of the current device board, and automatic software upgrade is implemented according to the comparison result.
Optionally, after the step S106, the following steps are further included:
step S31, activating the upgraded equipment single board according to the software activation strategy of the equipment single board;
wherein the software activation policy comprises: after the current equipment single board is subjected to software upgrading, directly sending a reset instruction to the upgraded equipment single board to indicate the upgraded equipment single board to be activated; or after receiving a selection instruction of the activation operation of the equipment board, sending a reset instruction to the upgraded equipment board to instruct the upgraded equipment board to activate.
Through step S31, after the current device board is upgraded, the upgraded device board is activated according to the software activation policy of the device board, so that the upgraded device board can normally run the upgraded software version.
Optionally, after the step S106, the following steps are further included:
step S41, detecting an upgrade result after the current device board performs software upgrade, and recording a process log of the current device board performing software upgrade.
The process log of the current software upgrade performed by the equipment board obtained in step S41 enables the process of performing software upgrade performed by the equipment board to be tracked in real time.
In an optional embodiment, in the case that a new board is added to the current device, the method further includes the following steps:
step S51, receiving the veneer type of the newly added veneer reported by the current equipment and the software version information corresponding to the veneer type;
step S52, determining whether a software version corresponding to the received software version information exists in the first software version;
step S54, if the determination result is yes, determining whether the first software version is consistent with the software version of the current device board, and if the determination result is no, controlling the current device board to perform software upgrade;
step S55, if the determination result is negative, obtaining the software version corresponding to the newly added board from the server, and controlling the current board to perform software upgrade.
Through the optional mode, under the condition that the newly added single board is added to the current equipment, the software can be automatically upgraded on the newly added single board in time.
The present embodiment will be described below with reference to specific examples.
Alternative embodiment 1
The premise of automatic upgrading is that the updating strategy is configured manually, and a user configures the updating strategy and the activating strategy through a UI interface.
The updating strategy can be configured to be simplest updating and simplest updating, namely only downloading versions of all administration devices of the agent module with single board types; the most updated, i.e., downloading, versions of all device slate types for the device vendor.
The activation policy may be configured for automatic activation and manual activation: the method comprises the steps of automatically activating, without manual determination, directly sending a reset command to a single board to inform the single board of reset activation after an upgrade agent module updates a version file to the single board; when manual activation is performed, a reset command is sent to the single board to inform the single board of reset activation after a user clicks and determines a UI interface or a popup interface.
The specific process of the equipment single board automatic upgrading comprises the following steps:
step S61: the upgrade agent module reads the update policy data xml stored in the apparatus 1, acquires the update policy, and proceeds to step S62 if the policy is the simplest update, or proceeds to step S63 if the policy is the most recent update.
Step S62: the device 3 is used for obtaining the single board of the current equipment, storing the version information of the single board to the version report of the local equipment, connecting the equipment version server through the device 2, comprehensively comparing the version report of the equipment, the local version library and the server version library, and downloading ftp or http to the local version library if the version report of the equipment, the local version library and the server version library is updated. The process advances to step S64.
Step S63: the device 2 is connected with the equipment manufacturer version server, checks all versions, and downloads the versions to the local version library storage through ftp or http if the versions do not exist locally or are inconsistent. The process advances to step S64.
Step S64: the upgrade agent module compares the device version report obtained by the device 3 with the local version library, and proceeds to step S65 for the board whose current version is inconsistent with the version of the local version library.
Step S65: the upgrade agent module control device 3 transfers the new version to the device board memory in ftp or tftp mode by using the snmp or telnet tool. If the activation policy is automatic activation according to the activation policy, proceeding to step S66; if the activation policy is manual activation, the process proceeds to step S67.
Step S66: the upgrade agent module control device 3 directly sends a reset message to the board using the snmp or sends a reset message to the board via telnet to input the reboot, notifies the board of reset activation, and then proceeds to step S68.
Step S67: the upgrade agent module notifies the user of the activation of the board to be reset through the UI interface or the popup window, and after the user confirms, directly sends a reset message to the board by using the snmp or sends the reset message to the board through telnet to input the reboot, notifies the board of the activation of the reset, and then the process goes to step S68.
Step S68: after waiting for a certain time, the upgrade agent module obtains the single board of the current equipment through the device 3, updates the version information of the single board to the version report of the local equipment, compares the version report of the equipment with the local version library, checks the version information of the upgraded single board, saves the upgrade log to the local file, and informs the user of the upgrade result through a UI (user interface) or a popup window.
It should be noted that, in the above-mentioned step S61 to step S68, the partial equipment board automation upgrade process may refer to step S301 to step S310 in fig. 3.
Alternative embodiment 2
The specific process for automatically acquiring the version of the newly installed single board comprises the following steps:
step S71: when a new board is installed in the device, the device 3 reports the new board type and version information to the upgrade agent module, and the device 3 stores the information to the local newly added board list file. The upgrade agent module searches the local version library according to the newly added board list file, and if no corresponding board version file exists, the step S72 is performed, and if a corresponding board version file exists, the step S73 is performed.
Step S72: the upgrade agent module, through the device 2, connects to the equipment provider version server to query the version of the new board corresponding to the new board in the new added board list file, downloads the version file to the local version library through ftp or http, and then proceeds to step S73.
Step S73: and the upgrading agent module compares the newly added board list file with the local version library, and if the version is inconsistent, the step S74 is carried out.
Step S74: the upgrade agent module control apparatus 3 transfers the new version to the device board memory in an ftp or tftp manner using the snmp or telnet tool, and the process proceeds to step S75.
Step S75: the upgrade agent module control device 3 directly sends a reset message to the board using the snmp or sends a reset message to the board via telnet to input the reboot, notifies the board of reset activation, and then proceeds to step S76.
Step S76: after waiting for a certain time, the upgrade agent module queries the board version information in the newly added board list file, updates the version information to the newly added board list file, compares the newly added board list file with the local version library, checks the upgraded board version information, saves the upgrade log to the local file, and notifies the user of the upgrade result through a UI interface or a popup window.
It should be noted that, in the partial flow of the new installed board automatically acquiring the version involved in the above steps S71 to S76, reference may be made to steps S401 to S409 in fig. 4.
Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.
Example 2
In this embodiment, a software upgrading apparatus is further provided, and the apparatus is used to implement the foregoing embodiments and preferred embodiments, and the description already made is omitted. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.
Fig. 5 is a block diagram of a software upgrading apparatus according to an embodiment of the present invention, as shown in fig. 5, the apparatus including:
1) an obtaining module 52, configured to obtain, according to a preconfigured upgrade policy, a software version of the device board from the server, so as to obtain a first software version;
2) a first determining module 54, configured to determine whether the first software version is consistent with a second software version of the current device board;
3) and 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 scenarios of the software upgrading apparatus include, but are not limited to: in the single board software version upgrading, under the application scene, acquiring the software version of the equipment single board from the server according to a preset upgrading strategy to obtain a first software version; judging whether the first software version is consistent with a second software version of the current equipment single board; and controlling the current equipment single board to carry out software upgrading under the condition that the judgment result is negative. That is to say, the present embodiment implements automatic upgrade through a preconfigured upgrade policy, and does not need manual upgrade of board software, thereby solving the problem of low software upgrade efficiency caused by manual upgrade of board software in the related art, and achieving the effect of improving board software upgrade efficiency.
In an optional implementation manner, fig. 6 is a block diagram (a) of a software upgrading apparatus according to an embodiment of the present invention, and as shown in fig. 6, the obtaining module 52 includes:
1) a first obtaining unit 62, configured to obtain, according to a predetermined period, a software version of the current device board from a server; alternatively, the first acquisition unit may be equivalently replaced with a second acquisition unit for acquiring all software versions of the server from the server at a predetermined cycle.
In this optional embodiment, the latest partial or all software versions are automatically obtained through the single board software version update policy, so as to further achieve the effect of automatically upgrading the single board software.
In an alternative implementation manner, fig. 7 is a block diagram (ii) of a software upgrading apparatus according to an embodiment of the present invention, and as shown in fig. 7, the apparatus includes, in addition to the modules shown in fig. 5:
1) a sending module 72, configured to send a software version query instruction to a current device board through a specified protocol before determining whether the first software version is consistent with a second software version of the current device board, where the specified protocol includes at least one of the following: simple network management protocol (snmp) and telnet protocol;
2) a first receiving module 74, configured to receive the second software version reported by the current device board.
In this optional embodiment, the software version of the current device board is queried for the current device board through a specified protocol, so that the software version of the current device board can be compared with the latest software version obtained from the server according to the obtained software version of the current device board, and automatic software upgrade is implemented according to the comparison result.
In an alternative implementation manner, fig. 8 is a block diagram (three) of a software upgrading apparatus according to an embodiment of the present invention, and as shown in fig. 8, the apparatus includes, in addition to the modules shown in fig. 5:
1) an activation module 82, configured to activate the upgraded equipment board according to a software activation policy of the equipment board after controlling the current equipment board to perform software upgrade;
wherein the software activation policy comprises: after the current equipment single board is subjected to software upgrading, directly sending a reset instruction to the upgraded equipment single board to indicate the upgraded equipment single board to be activated; or after receiving a selection instruction of the activation operation of the equipment board, sending a reset instruction to the upgraded equipment board to instruct the upgraded equipment board to activate.
By the device, after the current equipment single board is upgraded, the upgraded equipment single board is activated according to the software activation strategy of the equipment single board, so that the upgraded equipment single board can normally run the upgraded software version.
In an alternative implementation manner, fig. 9 is a block diagram (iv) of a software upgrading apparatus according to an embodiment of the present invention, and as shown in fig. 9, the apparatus includes, in addition to the modules shown in fig. 5:
1) the detecting module 92 is configured to detect an upgrade result after the current device board performs software upgrade after controlling the current device board to perform software upgrade, and record a process log of the current device board performing software upgrade.
The process log of the current equipment single board for software upgrading is obtained by the device, so that the process of software upgrading of the equipment single board can be tracked in real time.
In an alternative implementation manner, fig. 10 is a block diagram (v) of a software upgrading apparatus according to an embodiment of the present invention, and as shown in fig. 10, the apparatus includes, in addition to the modules shown in fig. 5:
1) a second receiving module 1002, configured to receive, under the condition that a new board is added to current equipment, a board type of the new board reported by the current equipment and software version information corresponding to the board type;
2) a second determining module 1004, configured to determine whether a software version corresponding to the received software version information exists in the first software version;
3) a first processing module 1006, configured to, 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;
4) the second processing module 1008 is configured to, if the determination result is negative, obtain the software version corresponding to the newly added board from the server, and control the current board to perform software upgrade.
Through the optional mode, under the condition that the newly added single board is added to the current equipment, the software can be automatically upgraded on the newly added single board in time.
It should be noted that, the above modules may be implemented by software or hardware, and for the latter, the following may be implemented, but not limited to: the modules are all positioned in the same processor; alternatively, the modules are respectively located in different processors in any combination.
Example 3
The embodiment of the invention also provides a storage medium. Alternatively, in the present embodiment, the storage medium may be configured to store program codes for performing the following steps:
s1, acquiring the software version of the equipment single board from the server according to the preset upgrading strategy to obtain a first software version;
s2, judging whether the first software version is consistent with the second software version of the current device single board;
and S3, controlling the current equipment single board to carry out software upgrading under the condition that the judgment result is negative.
Optionally, in this embodiment, the storage medium may include, but is not limited to: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk, which can store program codes.
Alternatively, in the present embodiment, the processor performs the above steps S1, S2, and S3 according to program codes already stored in the storage medium.
Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation manners, and this embodiment is not described herein again.
It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610327571.5A CN107395385A (en) | 2016-05-17 | 2016-05-17 | Method for upgrading software and device |
| PCT/CN2017/080295 WO2017198015A1 (en) | 2016-05-17 | 2017-04-12 | Software upgrading method and apparatus |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610327571.5A CN107395385A (en) | 2016-05-17 | 2016-05-17 | Method for upgrading software and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107395385A true CN107395385A (en) | 2017-11-24 |
Family
ID=60324820
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610327571.5A Pending CN107395385A (en) | 2016-05-17 | 2016-05-17 | Method for upgrading software and device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN107395385A (en) |
| WO (1) | WO2017198015A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116009912A (en) * | 2022-12-26 | 2023-04-25 | 郑州云智信安安全技术有限公司 | Construction method for automatically generating upgrade package aiming at private network environment |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110764803B (en) * | 2019-10-21 | 2023-03-31 | 北京云迹科技股份有限公司 | Software upgrading method and device |
| CN112423290B (en) * | 2020-11-05 | 2022-10-18 | 歌尔科技有限公司 | Wireless upgrading method, terminal equipment, device to be upgraded and medium |
| CN112910948B (en) * | 2021-01-12 | 2023-05-09 | 拉扎斯网络科技（上海）有限公司 | Protocol upgrade method, device, electronic equipment, storage medium and program product |
| CN113434167B (en) * | 2021-06-15 | 2023-06-16 | 青岛海尔科技有限公司 | Function upgrading method and device, storage medium and electronic device |
| CN113596084B (en) * | 2021-06-24 | 2023-10-24 | 青岛海尔科技有限公司 | Home appliance status feedback method and system, storage medium, electronic device |
| CN114489750A (en) * | 2021-12-28 | 2022-05-13 | 深圳市鸿合创新信息技术有限责任公司 | Remote upgrading method and device |
| CN116185452A (en) * | 2023-02-10 | 2023-05-30 | 深圳市共进电子股份有限公司 | Software upgrade system and method based on WEB automation |
| CN117032765B (en) * | 2023-10-10 | 2024-01-16 | 浙江大华技术股份有限公司 | Model upgrading method, model upgrading device and computer storage medium |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1178402A1 (en) * | 2000-08-03 | 2002-02-06 | Hsing Tech Enterprises Co., Ltd. | Method and apparatus for actively updating program file(s) of a client computer |
| CN101267344B (en) * | 2008-04-25 | 2011-07-13 | 中兴通讯股份有限公司 | An upgrade method and device for network element single-board software |
| CN101388792B (en) * | 2008-10-15 | 2011-06-15 | 上海华为技术有限公司 | Single board plug-and-use processing method, device and telecommunication system |
| CN101924643A (en) * | 2009-06-10 | 2010-12-22 | 中兴通讯股份有限公司 | Method and system for upgrading single-board software in communication system equipment |
-
2016
- 2016-05-17 CN CN201610327571.5A patent/CN107395385A/en active Pending
-
2017
- 2017-04-12 WO PCT/CN2017/080295 patent/WO2017198015A1/en not_active Ceased
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116009912A (en) * | 2022-12-26 | 2023-04-25 | 郑州云智信安安全技术有限公司 | Construction method for automatically generating upgrade package aiming at private network environment |
| CN116009912B (en) * | 2022-12-26 | 2023-08-18 | 郑州云智信安安全技术有限公司 | Construction method for automatically generating upgrade package aiming at private network environment |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2017198015A1 (en) | 2017-11-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107395385A (en) | Method for upgrading software and device | |
| KR100620054B1 (en) | Device Management System and Method in Device Management Technology | |
| EP2456257B1 (en) | Method and system for upgrading wireless data card | |
| JP6217034B2 (en) | Related plug-in management method, apparatus and system | |
| CN112187531B (en) | Module upgrading method and system, storage medium and electronic device | |
| CN110912728B (en) | Operating system patch batch automatic update management method and system | |
| CN108235763B (en) | Detection system, method and related device | |
| CN103019757A (en) | Method, device and system for synchronizing software among multiple clients | |
| WO2015143794A1 (en) | Creating and upgrading methods, server, terminal, upgrading system, and storage media | |
| CN113504922B (en) | Robot software upgrading method and device, bridge server and upgrading server | |
| CN103957117A (en) | System and method for achieving intelligent installation of network equipment | |
| CN102063321B (en) | The installation method of terminal software, device and system | |
| CN113312064A (en) | Installation configuration method and device of physical machine and computer readable medium | |
| CN108512747A (en) | The plug-in management method and home gateway of home gateway, communication system | |
| CN114189440B (en) | A method, device and storage medium for remote upgrading of multiple control panels of an Internet of Things device | |
| WO2017059724A1 (en) | Operating system starting method and device | |
| CN103973474A (en) | Network terminal update configuration method | |
| CN105072398B (en) | A kind of device updating method and device | |
| CN117435224A (en) | Firmware updating method and device for retimer, storage medium and electronic equipment | |
| CN111209012A (en) | Linux system-oriented software agent end automatic deployment method | |
| WO2022110645A1 (en) | Software upgrade method and device, storage medium and electronic device | |
| CN120215966A (en) | Server operating system installation method, server management system, storage medium and electronic device | |
| CN102843252A (en) | Method and device for updating network element through network management | |
| CN109992295A (en) | A kind of method for edition management and server | |
| CN104104701A (en) | Online service configuration updating method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20171124 |
|
| WD01 | Invention patent application deemed withdrawn after publication |