CN108874410B - Patch management method and device - Google Patents
Patch management method and device Download PDFInfo
- Publication number
- CN108874410B CN108874410B CN201710322899.2A CN201710322899A CN108874410B CN 108874410 B CN108874410 B CN 108874410B CN 201710322899 A CN201710322899 A CN 201710322899A CN 108874410 B CN108874410 B CN 108874410B
- Authority
- CN
- China
- Prior art keywords
- package
- patch
- activated
- version
- software
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a patch management method and device. Wherein the method comprises the following steps: determining a patch package to be activated according to the corresponding relation between the version number of the software upgrading package requested by the current equipment and the patch package; and when the software upgrade package is activated, activating the patch package to be activated. The invention solves the problem that in the related technology, the software upgrading package and the patch package are respectively upgraded and reset for two times to cause the service interruption for two times, thereby achieving the technical effect of reducing the influence of the patch upgrading on the current network service.
Description
Technical Field
The present invention relates to the field of communications, and in particular, to a patch management method and apparatus.
Background
In the field of communication, each equipment manufacturer has a unique software version upgrading management method to complete the upgrading of the software version of the whole equipment, and the whole equipment is restarted usually when the whole software version is upgraded. Meanwhile, some various bugs may be found after the version-up is run for a while. In order to affect the normal operation of the device as little as possible, manufacturers generally repair existing bug by applying software patches. The patches provided can be roughly divided into two types: 1. the hot patch is mostly a patch at the function level, and the repair of the known bug is completed under the condition that the process is not restarted; 2. cold patches are generally functional bug, and many places need to be repaired, and the problem can not be solved by hot patch. The cold patch needs to reset the single board to repair the fault, but the hot patch is not needed, so that the advantages are very obvious in the aspect of small influence on the service, but the cold patch can repair a plurality of faults at the same time, even solve the bug on the single board hardware, and the advantages in the aspect of problem solving efficiency are very obvious. Therefore, both patches are often used in an engineering environment.
This often occurs in engineering where all devices in the existing network cannot all perform upgrade operations at the first time when a vendor releases a new software version. In general, when a device in one place is ready for a software version upgrade, it may be found that a manufacturer has released a plurality of cold or hot patches for the software version ready for upgrade, and these patches may be patches repaired by devices in other places using the found bug. If the user releases a plurality of cold patches and the locally used equipment needs to repair related faults, the plurality of cold patches may need to be activated, so that a plurality of single boards need to be reset, thus, once the service is interrupted in the upgrading software corpus, the service is possibly interrupted again when the cold patches are activated, and the use experience of the user is very poor. At the same time, even if the device manufacturer provides a hot patch and multiple services are simultaneously run, it is not very friendly for the user to use the operation. In view of the above problems, no effective solution has been proposed in the related art.
Disclosure of Invention
The embodiment of the invention provides a patch management method and a patch management device, which at least solve the problem that a software upgrade package and a patch package are respectively upgraded and reset twice to cause service interruption twice in the related technology.
According to an embodiment of the present invention, there is provided a patch management method and apparatus, including: determining a patch package to be activated according to the corresponding relation between the version number of the software upgrading package requested by the current equipment and the patch package; and activating the patch package to be activated.
Optionally, before determining the patch package to be activated, the method further includes: obtaining a patch activation configuration file, wherein the patch activation configuration file comprises at least one of the following information: the name of the patch package, the version number of the software upgrade package corresponding to the patch package, the type of the patch package and the type of the device corresponding to the patch package.
Optionally, before determining the patch package to be activated, the method further includes: and storing a software upgrading package set to be upgraded and a patch package corresponding to the software upgrading package in the software upgrading package set.
Optionally, when the software upgrade package is activated, activating the patch package to be activated includes: judging whether the patch package to be activated supports the current equipment or not according to the patch package activation configuration file; if the judgment result is yes, activating the patch package to be activated
Optionally, the number of the patch packages to be activated is multiple.
According to another embodiment of the present invention, there is provided a patch management apparatus including: the determining module is used for determining the patch package to be activated according to the corresponding relation between the version number of the software upgrading package requested by the current equipment and the patch package; and the activating module is used for activating the patch package to be activated when the software upgrading package is activated.
Optionally, the apparatus further comprises: the system comprises an acquisition module, a storage module and a storage module, wherein the acquisition module is used for acquiring a patch activation configuration file before determining a patch to be activated, and the patch activation configuration file comprises at least one of the following information: the name of the patch package, the version number of the software upgrade package corresponding to the patch package, the type of the patch package and the type of the device corresponding to the patch package.
Optionally, the apparatus further comprises: and the storage module is used for storing the software upgrading package set to be upgraded and the patch package corresponding to the software upgrading package in the software upgrading package set before determining the patch package to be activated.
Optionally, the activation module includes: the judging unit is used for judging whether the patch package to be activated supports the current equipment according to the patch package activation configuration file; and the activating unit is used for activating the patch package to be activated under the condition that the judging result is yes.
Optionally, the number of the patch packages to be activated is multiple.
According to still another embodiment of the present invention, there is also provided a storage medium. The storage medium is arranged to store program code for performing the steps of: .
Determining a patch package to be activated according to the corresponding relation between the version number of the software upgrading package requested by the current equipment and the patch package;
and when the software upgrade package is activated, activating the patch package to be activated.
According to the method and the device, the patch package to be activated is determined according to the corresponding relation between the version number of the software upgrading package requested by the current equipment and the patch package; and when the software upgrade package is activated, activating the patch package to be activated. That is, the current device upgrades the patch package while upgrading the software, and combines the two upgrade processes into one upgrade process, thereby solving the problem that in the related art, the software upgrade package and the patch package are respectively upgraded and reset for two times to cause two times of service interruption, and further achieving the technical effect of reducing the influence of patch upgrade on the current network service.
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 embodiments of the invention and together with the description serve to explain the invention and do not constitute a limitation on the invention. In the drawings:
fig. 1 is a block diagram of a hardware structure of a mobile terminal of a patch management method according to an embodiment of the present invention;
FIG. 2 is a patch management flow diagram according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a patch management structure according to an embodiment of the present invention;
FIG. 4 is a patch management flow diagram (one) according to an embodiment of the present invention;
FIG. 5 is a patch management flow chart (II) according to an embodiment of the present invention;
fig. 6 is a block diagram of a patch management apparatus according to an embodiment of the present invention;
fig. 7 is a block diagram (a) of a configuration of a patch management apparatus according to an embodiment of the present invention;
fig. 8 is a block diagram (two) of the configuration of the patch management apparatus according to the embodiment of the present invention;
fig. 9 is a block diagram (iii) of the configuration of the patch management apparatus according to the embodiment of the present invention.
Detailed Description
The invention will be described in detail hereinafter with reference to the drawings in conjunction with embodiments. It should be noted that, in the case of no conflict, the embodiments and features in the embodiments may be combined with each other.
It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order.
Example 1
The method embodiment provided in the first embodiment of the present application may be executed in a mobile terminal, a computer terminal or a similar computing device. Taking the mobile terminal as an example, fig. 1 is a block diagram of a hardware structure of the mobile terminal of a patch management method according to an embodiment of the present invention. As shown in fig. 1, the mobile terminal 10 may include one or more (only one is shown in fig. 1) processors 102 (the processors 102 may include, but are not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission device 106 for communication functions. It will be appreciated by those of ordinary skill in the art that the configuration shown in fig. 1 is merely illustrative and is not intended to limit the configuration of the electronic device described above. For example, the mobile terminal 10 may also include more or fewer components than shown in FIG. 1 or have a different configuration than shown in FIG. 1.
The memory 104 may be used to store software programs and modules of application software, such as program instructions/modules corresponding to the patch management method in the embodiment of the present invention, and the processor 102 executes the software programs and modules stored in the memory 104 to perform various functional applications and data processing, i.e., implement the method described above. Memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory located remotely from the processor 102, which may be connected to the mobile terminal 10 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The transmission means 106 is arranged to receive or transmit data via a network. The specific examples of networks described above may include wireless networks provided by the communication provider of the mobile terminal 10. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, NIC) that can connect to other network devices through a base station to communicate with the internet. In one example, the transmission device 106 may be a Radio Frequency (RF) module for communicating with the internet wirelessly.
In this embodiment, a patch management method is provided, fig. 2 is a patch management flowchart according to an embodiment of the present invention, and as shown in fig. 2, the flowchart includes the following steps:
step S202, determining a patch package to be activated according to the corresponding relation between the version number of the software upgrade package requested by the current equipment and the patch package;
in step S204, when the software upgrade package is activated, the patch package to be activated is activated.
Through the steps, the patch package to be activated is determined according to the corresponding relation between the version number of the software upgrading package requested by the current equipment and the patch package; and when the software upgrade package is activated, activating the patch package to be activated. That is, the current device upgrades the patch package while upgrading the software, and combines the two upgrade processes into one upgrade process, thereby solving the problem that in the related art, the software upgrade package and the patch package are respectively upgraded and reset for two times to cause two times of service interruption, and further achieving the technical effect of reducing the influence of patch upgrade on the current network service.
The embodiments are illustrated below in conjunction with specific examples.
The embodiment of the invention provides a method for managing and upgrading cold patch butyl, which supports equipment to upgrade cold patch Ding Banben while upgrading a software corpus, and solves the problem that service is interrupted twice because the software corpus and the cold patch butyl are respectively upgraded and reset for two times.
The proposed method for upgrading cold patch Ding Bao and software full package simultaneously comprises the following steps:
the software of the whole equipment is centrally managed on the main control board by a version analysis management module and a version download management module, wherein the version analysis management module finishes analysis of a software version package, and the version download management module finishes version request response of the main control or line card. The software version package includes the following three types: the software full package, the cold patch Ding Bao and the hot patch Ding Bao, wherein when the software full package is upgraded, the whole equipment needs to be restarted, and when the cold patch Ding Bao is upgraded, only the corresponding single board with problems needs to be restarted, and when the hot patch Ding Bao is upgraded, any single board does not need to be restarted.
The realization steps of the simultaneous upgrading of the cold patch package and the software full package are as follows:
1. uploading the software complete set package and the cold patch butyl package to a specific path of a memory on a main control board of the equipment;
2. uploading a cold patch Ding Bao activation configuration file to a main control board;
3. activating a software complete set package on a main control board and restarting the whole equipment;
4. loading a version management module after restarting the equipment, and analyzing a new software full set package;
5. the version management module reads the cold patch activation configuration file, determines patches to be activated, and completes analysis of the patches;
6. the version management module enables a version downloading module to respond to version requests of the main control and the line cards.
In step 1, if the main control board has 1+1 protection, the uploaded version file needs to be synchronized between the main and the standby files;
the cold patch Ding Bao activation configuration file uploaded in step 2 mainly includes the following information: 1. cold patch package name; 2. the cold patch corresponds to the version number of the software full set package, and because the bug repaired by the cold patch is fixed, the version number of the software full set package corresponding to the bug is fixed and unique; 3. the patch package type, wherein the fixing is cold patch Ding Bao, and hot patch Ding Bao can also adopt the same mode; 4. the device type corresponding to the patch package is mainly aimed at a plurality of types of devices with the same function possibly released by a device manufacturer at a time, and some patch packages do not need to distinguish the device types, so this field is added here.
The main purpose of the step 3 is to inform the equipment of which software complete set package needs to be upgraded to the version management, and at the same time, the whole machine is restarted to start upgrading;
in step 4, the version analysis management module can complete analysis of the software full set package, and directly enter step 6 under the condition that no cold patch package needs to be activated, so that the version download management module is enabled, and the version request of the board or other single boards is responded.
And 5, the version analysis management module reads and analyzes the cold patch activating configuration file, and if any one of the following conditions occurs, the step 6 is directly carried out, and the whole upgrading process of the equipment is not affected:
1) Failure to read the file;
2) Reading the file to find that the version number of the configuration is inconsistent with the current software complete set package to be upgraded;
3) Cold patch Ding Bao found to be activated is not present;
4) Patches that need to be activated are found to not support the present device type.
In the case that the above steps are successful, the version resolution management module performs resolution of all cold patches Ding Bao that need to be activated, so that both cold patches Ding Bao and the software corpus are resolved.
At this time, step 6 is entered, enabling the version download management module to start to answer the version request of the board or other boards, and for the version file with bug, answering the latest file in the patch package to the board, thereby completing the repair of the version bug in the upgrade starting process of the whole equipment.
Of course, in step 5, the version analysis management module may be used to read the patch package under the fixed path from the main control board, and manage the corresponding software corpus and device type information in the patch package.
Meanwhile, the method can be also suitable for a scene that a plurality of cold patches or a plurality of hot patches need to be activated simultaneously after the software corpus has been upgraded, and the plurality of cold patches or the hot patches Ding Yici can be successfully activated in a configuration file mode.
In summary, the embodiment of the invention provides a method for managing and upgrading cold patch Ding Bao, which can support equipment to upgrade a cold patch package while upgrading a software corpus, combine two upgrade processes into one upgrade process, improve upgrade efficiency, reduce the influence of cold patch upgrade on the current network service, and greatly improve the satisfaction degree of users on equipment upgrade. Meanwhile, the method can also be used for a scene that the equipment has upgraded the software corpus and needs to activate a plurality of cold patches or hot patches, thereby greatly improving the activation efficiency of the patches.
Optionally, before determining the patch package to be activated, the method further comprises the following steps:
step S11, a patch activation configuration file is obtained, wherein the patch activation configuration file comprises at least one of the following information: the name of the patch package, the version number of the software upgrade package corresponding to the patch package, the type of the patch package and the type of the device corresponding to the patch package.
By acquiring the patch package activation configuration file, patches to be activated can be further determined, so that the upgrading efficiency is improved, and the influence of cold patch upgrades on the current network service is reduced.
Optionally, before determining the patch package to be activated, the method further comprises the following steps:
step S21, a software upgrading package set needing upgrading and a patch package corresponding to the software upgrading package in the software upgrading package set are stored.
It should be noted that, in the foregoing steps, the method of saving the set of software upgrade packages to be upgraded and the patch package corresponding to the software upgrade package in the set of software upgrade packages may be a 1+1 method.
In an alternative embodiment, when the software upgrade package is activated, activating the patch package to be activated includes the steps of:
step S31, judging whether the patch to be activated supports the current device or not according to the patch activation configuration file;
step S32, if the judgment result is yes, activating the patch package to be activated.
Optionally, the number of the patch packages to be activated is multiple.
Embodiments of the invention are illustrated below in conjunction with alternative embodiments.
Alternative embodiment one
As shown in fig. 3, a version parsing management and version downloading management module exists on the main control board, the version parsing management module is responsible for parsing the version package and storing version information, and the version downloading management module is responsible for responding to version request messages of the main control board or other single boards. Under normal conditions, the whole equipment upgrading process comprises the following steps:
1. uploading a software complete set package to be upgraded to a specific path on a main control board of the equipment, and synchronizing to the standby main control if the standby main control exists;
2. activating a software complete set package, namely designating the name and the upgrading mode of an upgrading package to equipment, storing the information in a storage medium by the equipment, and restarting the equipment by the whole machine;
3. reading the file stored in the corresponding storage medium when the equipment is restarted, acquiring the name of the software package to be upgraded and the corresponding path, and analyzing the version whole collection package under a specific catalogue by a version analysis management module and storing corresponding information;
4. after the version analysis management module analyzes the complete set of versions, the version download management module is informed to start responding to the version requests of other modules, wherein the version download management module is initialized to default to not respond to the version requests of other modules after being started.
5. The starting management module of the board or the starting management module of other single boards downloads and operates the corresponding version files after the version is requested to the version download management module of the main control in a circulating way and the version information of the response of the version download management module is received.
6. All single boards of the whole equipment request the required version information, and the equipment is successfully upgraded.
Alternative embodiment II
This is often the case in engineering where when one device is ready to upgrade a software corpus, it is found that the device manufacturer has issued multiple cold patches and hot patches for the problems found by other devices, and after the cold patches are activated, the single board or the device needs to be restarted to be effective, which results in two restarts of the device when the software corpus is upgraded and the cold patches Ding Bao are upgraded, and in addition to two impacts on customer service, the upgrade efficiency is very low.
The present alternative embodiment mainly aims at this situation, and proposes a patch activation configuration file, according to which a device can determine which patches need to be activated at the same time when restarting, and key parameters are as shown in the following table 1:
TABLE 1
| Field sequence number | Field name | Meaning of field |
| 1 | PatchFileName | Patch file name |
| 2 | SoftVersion | Patch-corresponding software full set package version number |
| 3 | PatchType | Patch type: cold patch and hot patch |
| 4 | DevType | Device type corresponding to patch |
The specific format of the configuration file is not limited, and may be txt or xml, and the same configuration file may have multiple records, that is, multiple cold patches may be activated at a time. Similarly, the hot-fill may be performed in a similar manner, but the version resolution may not be performed in the same manner.
As shown in fig. 4, the specific upgrading process includes: uploading the software complete set package to a specific path on a main control board of the equipment, and synchronizing to the standby main control if the standby main control exists; uploading the patch package to be activated to a specific path on a main control board, and processing the basic same full-set package; the upload patch activation profile may be, for example, a PatchCfg.xml to the master board specific path, and also synchronized to the standby master if present. Activating a software complete set package, namely designating the name and the upgrading mode of an upgrading package to equipment, storing the information in a storage medium by the equipment, and restarting the equipment by the whole machine; reading the file stored in the corresponding storage medium when the equipment is restarted, acquiring the name of the software package to be upgraded and the corresponding path, and analyzing the version whole collection package under a specific catalogue by a version analysis management module and storing corresponding information; the version analysis management module reads patch activation configuration file PatchCfg.xml, if the reading fails, all single boards directly jumping to the whole equipment request the needed version information, and the equipment is successfully upgraded; judging whether the version numbers of the software in all records are consistent with the version numbers of the software which needs to be upgraded currently, whether a cold patch butyl set exists, and whether the set equipment types are matched, if one of the software types does not meet the set equipment types, all single boards entering the whole equipment request the required version information, and the equipment is successfully upgraded; the analysis management module analyzes all patch packages which are required to be activated and recorded in PatchCfg.xml, and enables the version download management module after analysis is completed; the version download management module responds to the version requests of other modules, and returns the information of the patch file if the patch version file exists in the same file when inquiring the version information; otherwise, returning the information of the queried version file; the patch file may have the same file name as the patched file, but may have a different small version number, and it may be determined which file is the patch file by comparing the version numbers, or the like. All single boards of the whole device request the required version information, and the device is updated successfully (refer to steps S401 to S412 in fig. 4 for details).
As described above, the hot patch may also be activated in a manner similar to a cold patch, and may also reduce the operation of the user on the device; meanwhile, in a non-upgrading state, namely, only the whole machine restarting state of the equipment, the mode can be adopted, the activation of the patch package can be completed while the whole machine restarting, and unnecessary operations are reduced.
Optionally, a method for batch activation of patches as shown in fig. 5 is also provided in this embodiment (refer specifically to steps S501-508 in fig. 5).
In summary, the embodiment of the invention provides a method for managing and upgrading cold patch Ding Bao, which can support equipment to upgrade a cold patch package while upgrading a software corpus, combine two upgrade processes into one upgrade process, improve upgrade efficiency, reduce the influence of cold patch upgrade on the current network service, and greatly improve the satisfaction degree of users on equipment upgrade. Meanwhile, when a plurality of cold patches or hot patches are activated, the activating efficiency and the flexibility are improved, and the convenience of a user for using the equipment is improved greatly.
From the description of the above embodiments, it will be clear to a person skilled in the art that the method according to the above embodiments may be implemented by means of software plus the necessary general hardware platform, but of course also by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method according to the embodiments of the present invention.
Example 2
The present embodiment also provides a patch management device, which is used to implement the foregoing embodiments and preferred embodiments, and is not described in detail. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. While the means described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.
Fig. 6 is a block diagram of a patch management apparatus according to an embodiment of the present invention, as shown in fig. 6, the apparatus includes:
1) The determining module 62 is configured to determine a patch package to be activated according to a corresponding relationship between a version number of a software upgrade package requested by a current device and the patch package;
2) An activating module 64, configured to activate the patch package to be activated when the software upgrade package is activated.
By the device shown in fig. 6, determining a patch package to be activated according to the corresponding relation between the version number of the software upgrade package requested by the current equipment and the patch package; and when the software upgrade package is activated, activating the patch package to be activated. That is, the current device upgrades the patch package while upgrading the software, and combines the two upgrade processes into one upgrade process, thereby solving the problem that in the related art, the software upgrade package and the patch package are respectively upgraded and reset for two times to cause two times of service interruption, and further achieving the technical effect of reducing the influence of patch upgrade on the current network service.
Fig. 7 is a block diagram (a) of a patch management apparatus according to an embodiment of the present invention, as shown in fig. 7, the apparatus includes, in addition to the modules shown in fig. 6:
1) An obtaining module 72, configured to obtain a patch activation configuration file before determining a patch to be activated, where the patch activation configuration file includes at least one of the following information: the name of the patch package, the version number of the software upgrade package corresponding to the patch package, the type of the patch package and the type of the device corresponding to the patch package.
Fig. 8 is a block diagram (two) of a patch management 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. 6:
1) And a saving module 82, configured to save, before determining the patch package to be activated, a set of software upgrade packages to be upgraded and a patch package corresponding to the software upgrade package in the set of software upgrade packages.
Fig. 9 is a block diagram (iii) of a patch management apparatus according to an embodiment of the present invention, and as shown in fig. 9, the activation module 64 includes:
1) A judging unit 92, configured to judge whether the patch to be activated supports the current device according to the patch activation configuration file;
2) And the activating unit 94 is configured to activate the patch package to be activated if the determination result is yes.
Optionally, the number of the patch packages to be activated is multiple.
It should be noted that each of the above modules may be implemented by software or hardware, and for the latter, it may be implemented by, but not limited to: the modules are all located in the same processor; alternatively, the above modules may be 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 above-described storage medium may be configured to store program code for performing the steps of:
s1, determining a patch package to be activated according to a corresponding relation between a version number of a software upgrade package requested by current equipment and the patch package;
s2, when the software upgrade package is activated, activating the patch package to be activated.
Alternatively, in the present embodiment, the storage medium may include, but is not limited to: a U-disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing program codes.
Alternatively, in the present embodiment, the processor performs the above steps S1, S2 according to the program code stored in the storage medium.
Alternatively, specific examples in this embodiment may refer to examples described in the foregoing embodiments and optional implementations, and this embodiment is not described herein.
It will be appreciated by those skilled in the art that the modules or steps of the invention described above may be implemented in a general purpose computing device, they may be concentrated on a single computing device, or distributed across a network of computing devices, they may alternatively be implemented in program code executable by computing devices, so that they may be stored in a memory device for execution by computing devices, and in some cases, the steps shown or described may be performed in a different order than that shown or described, or they may be separately fabricated into individual integrated circuit modules, or multiple modules or steps within them may be fabricated into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only of the preferred embodiments of the present invention and is not intended to limit the present invention, but various modifications and variations can be made to the present invention by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. A patch management method, comprising:
according to the corresponding relation between the version number of the software upgrading package requested by the current equipment and the patch package, analyzing the software upgrading package requested by the current equipment and the patch package configuration file through a version analysis management module, and determining the patch package to be activated;
when the software upgrade package is activated, the control equipment is restarted;
when the equipment is restarted, and the analysis of the software upgrading package and the patch package configuration file requested by the current equipment is completed through the version analysis management module, and the patch package to be activated is determined, the version download management module is enabled through the version analysis management module, the version requests of the main control and the line card are responded, and the patch package to be activated is activated.
2. The method of claim 1, wherein prior to determining the patch package to be activated, further comprising:
obtaining a patch activation configuration file, wherein the patch activation configuration file comprises at least one of the following information: the name of the patch package, the version number of the software upgrade package corresponding to the patch package, the type of the patch package and the type of the device corresponding to the patch package.
3. The method of claim 1, wherein prior to determining the patch package to be activated, further comprising:
and storing a software upgrading package set to be upgraded and a patch package corresponding to the software upgrading package in the software upgrading package set.
4. The method of claim 2, wherein activating the patch package to be activated when the software upgrade package is activated comprises:
judging whether the patch package to be activated supports the current equipment or not according to the patch package activation configuration file;
and if the judgment result is yes, activating the patch package to be activated.
5. The method of any one of claims 1 to 4, wherein the number of patches to be activated is a plurality.
6. A patch management apparatus, comprising:
the determining module is used for analyzing the software upgrading package requested by the current equipment and the patch package configuration file through the version analysis management module according to the corresponding relation between the version number of the software upgrading package requested by the current equipment and the patch package, and determining the patch package to be activated;
the activation module is used for controlling the equipment to restart when the software upgrade package is activated; and
when the equipment is restarted, and the analysis of the software upgrading package and the patch package configuration file requested by the current equipment is completed through the version analysis management module, and the patch package to be activated is determined, the version download management module is enabled through the version analysis management module, the version requests of the main control and the line card are responded, and the patch package to be activated is activated.
7. The apparatus of claim 6, wherein the apparatus further comprises:
the system comprises an acquisition module, a storage module and a storage module, wherein the acquisition module is used for acquiring a patch activation configuration file before determining a patch to be activated, and the patch activation configuration file comprises at least one of the following information: the name of the patch package, the version number of the software upgrade package corresponding to the patch package, the type of the patch package and the type of the device corresponding to the patch package.
8. The apparatus of claim 6, wherein the apparatus further comprises:
and the storage module is used for storing the software upgrading package set to be upgraded and the patch package corresponding to the software upgrading package in the software upgrading package set before determining the patch package to be activated.
9. The apparatus of claim 7, wherein the activation module comprises:
the judging unit is used for judging whether the patch package to be activated supports the current equipment according to the patch package activation configuration file;
and the activating unit is used for activating the patch package to be activated under the condition that the judging result is yes.
10. The apparatus according to any one of claims 6 to 9, wherein the number of patches to be activated is a plurality.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710322899.2A CN108874410B (en) | 2017-05-09 | 2017-05-09 | Patch management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710322899.2A CN108874410B (en) | 2017-05-09 | 2017-05-09 | Patch management method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108874410A CN108874410A (en) | 2018-11-23 |
| CN108874410B true CN108874410B (en) | 2023-05-05 |
Family
ID=64287331
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710322899.2A Active CN108874410B (en) | 2017-05-09 | 2017-05-09 | Patch management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108874410B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109828768A (en) * | 2018-12-21 | 2019-05-31 | 福建新大陆支付技术有限公司 | A kind of management method and system of software patch |
| CN110928569A (en) * | 2019-11-20 | 2020-03-27 | 杭州依赛通信有限公司 | Method for realizing Live Update function of communication equipment |
| CN114518891A (en) * | 2020-11-19 | 2022-05-20 | 中兴通讯股份有限公司 | Single board upgrading method, single board equipment and computer readable storage medium |
| CN113779939B (en) * | 2021-09-14 | 2024-02-27 | 成都海光核电技术服务有限公司 | Document hot patch generation method, document hot patch application method and document hot patch Ding Zhuangzhi |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1889041A (en) * | 2006-08-02 | 2007-01-03 | 华为技术有限公司 | Software staging and back spacing method |
| US20110055821A1 (en) * | 2009-08-31 | 2011-03-03 | Sony Computer Entertainment Inc. | Information Processing Apparatus |
| CN102387165A (en) * | 2010-08-27 | 2012-03-21 | 腾讯科技（深圳）有限公司 | System and method for upgrading software |
| CN103246528A (en) * | 2012-02-10 | 2013-08-14 | 中兴通讯股份有限公司 | Software updating method and device |
-
2017
- 2017-05-09 CN CN201710322899.2A patent/CN108874410B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1889041A (en) * | 2006-08-02 | 2007-01-03 | 华为技术有限公司 | Software staging and back spacing method |
| US20110055821A1 (en) * | 2009-08-31 | 2011-03-03 | Sony Computer Entertainment Inc. | Information Processing Apparatus |
| CN102387165A (en) * | 2010-08-27 | 2012-03-21 | 腾讯科技（深圳）有限公司 | System and method for upgrading software |
| CN103246528A (en) * | 2012-02-10 | 2013-08-14 | 中兴通讯股份有限公司 | Software updating method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108874410A (en) | 2018-11-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108874410B (en) | Patch management method and device | |
| EP2456257B1 (en) | Method and system for upgrading wireless data card | |
| CN110083374B (en) | Upgrade rollback method, system and terminal equipment | |
| CN111367545A (en) | Terminal upgrading method and device, server, terminal equipment and readable storage medium | |
| CN102164363B (en) | Base station version updating realization method and base station | |
| CN103024782A (en) | Base station software version management method and system | |
| CN106612192A (en) | An equipment upgrading method, apparatus and system | |
| CN106648781B (en) | Method and system for upgrading remote firmware of communication equipment | |
| CN105517015A (en) | Upgrading method, device of wifi product by over the air OTA and terminal | |
| CN110543321A (en) | OTA (over the air) upgrading method, device, terminal and computer readable storage medium | |
| CN102063321B (en) | The installation method of terminal software, device and system | |
| CN105530130A (en) | Method and device for upgrading Over-The-Air downloading technology | |
| CN112615747B (en) | Method and device for automatically deploying and configuring network equipment | |
| CN107395385A (en) | Method for upgrading software and device | |
| CN109002305B (en) | Method and system for updating equipment program | |
| CN102300239B (en) | Base station and self-starting method thereof | |
| CN104580360A (en) | System and method for updating firmware through heterogeneous network | |
| CN101854442B (en) | Network device and firmware updating method thereof | |
| CN102841801A (en) | Method and device for upgrading firmware of driving-free terminal | |
| CN100484038C (en) | Network element version switching method and device | |
| CN113190565B (en) | Data updating method and device, storage medium and electronic device | |
| CN111427603B (en) | Application program upgrading method and device | |
| KR20150080356A (en) | remote update method for home automatic system | |
| CN113946354A (en) | Software upgrading method and device, storage medium and electronic device | |
| WO2017097180A1 (en) | Method and apparatus for quickly starting base station |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |