CN112306552A - System software version management method, device and storage medium - Google Patents
System software version management method, device and storage medium Download PDFInfo
- Publication number
- CN112306552A CN112306552A CN202011199164.3A CN202011199164A CN112306552A CN 112306552 A CN112306552 A CN 112306552A CN 202011199164 A CN202011199164 A CN 202011199164A CN 112306552 A CN112306552 A CN 112306552A
- Authority
- CN
- China
- Prior art keywords
- configuration file
- information configuration
- file
- upgrading
- module
- 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
- 238000007726 management method Methods 0.000 title claims abstract description 28
- 238000000034 method Methods 0.000 claims abstract description 25
- 238000012545 processing Methods 0.000 claims abstract description 23
- 238000004806 packaging method and process Methods 0.000 claims abstract description 15
- 238000004590 computer program Methods 0.000 claims description 21
- 238000009434 installation Methods 0.000 claims description 8
- 230000001419 dependent effect Effects 0.000 claims description 4
- 230000006835 compression Effects 0.000 claims description 3
- 238000007906 compression Methods 0.000 claims description 3
- 230000003993 interaction Effects 0.000 claims description 3
- 238000012795 verification Methods 0.000 abstract description 6
- 230000008569 process Effects 0.000 abstract description 3
- 238000010586 diagram Methods 0.000 description 12
- 230000006870 function Effects 0.000 description 9
- 230000000694 effects Effects 0.000 description 5
- 230000004048 modification Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 238000012217 deletion Methods 0.000 description 3
- 230000037430 deletion Effects 0.000 description 3
- 238000005538 encapsulation Methods 0.000 description 2
- 238000003672 processing method Methods 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 238000011900 installation process Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
Images
Classifications
-
- 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
-
- 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
Abstract
The application discloses a system software version management method, a device and a storage medium, which are used for realizing automatic packaging processing of a system software upgrading packet and file integrity verification and upgrading processing in the system software upgrading process, avoiding manual intervention and improving the safety and reliability of system software upgrading. The software version management method disclosed by the application comprises the following steps: packaging the system software upgrading package, and determining an upgrading package information configuration file; acquiring a system information configuration file of a baseline version; and updating the upgrade package information configuration file to the system information configuration file of the baseline version to obtain a second system information configuration file, and performing software version upgrade operation according to the upgrade package information configuration file and the second system information configuration file. The application also provides a system software version management device and a storage medium.
Description
Technical Field
The present application relates to the field of software, and in particular, to a method, an apparatus, and a storage medium for managing system software versions.
Background
In the prior art, software version management usually relies on an upgrade script or an upgrade program to install or execute a specific operation on different software modules according to an expected processing manner. The problem that may occur in this way is that the modules or files involved in each version release and the corresponding operations may be different, the upgrade script needs to be rewritten manually each time, and the risk of upgrade failure may be introduced by manual processing; and the upgrading involves the possibility that the modules are newly added, and the processing flow of a new module needs to be written every time the modules are newly added, so that the efficiency is low.
Disclosure of Invention
In view of the foregoing technical problems, embodiments of the present application provide a software version management method, apparatus, and storage medium, so as to implement automatic software upgrade processing, avoid manual intervention, and improve security and efficiency of software upgrade.
In a first aspect, a method for managing a system software version provided in an embodiment of the present application includes:
packaging the system software upgrading package, and determining an upgrading package information configuration file;
acquiring a system information configuration file of a baseline version, and updating the upgrade package information configuration file into the system information configuration file of the baseline version to obtain a second system information configuration file;
and carrying out version upgrading operation on the software system according to the upgrading package information configuration file and the second system information configuration file.
Further, before the encapsulating the system software upgrade package and determining the upgrade package information configuration file, the method further includes:
determining a module upgrading information configuration file, wherein the module upgrading information configuration file is used for recording the names, MD5 values, relative paths and processing modes of all files related to the module in the upgrading.
Further, the encapsulating the system software upgrade package and determining the upgrade package information configuration file includes:
verifying the file name and the relative path;
calculating the MD5 value of the file in the upgrade package, and carrying out integrity check comparison according to the MD5 value in the module upgrade information configuration file to realize the integrity check of the file before the upgrade package is packaged;
packaging all upgrading modules of the current version into a compression package;
and determining the upgrade package information configuration file according to the module upgrade information configuration file contents of all the modules.
Preferably, the baseline version of the system information configuration file includes one or a combination of the following:
operating system type and version number;
all installed software names, corresponding dependent library names, version numbers of installed software and version numbers of installed dependent libraries in the system;
system-related configuration information;
developed software or module related information.
Preferably, the developed software or module related information includes:
a module name;
all file names contained by the module;
upgrading the file;
the installation position of the file;
a file source location;
file MD5 values;
file permissions;
the group to which the file belongs;
and upgrading the subsequent operation mode of the file.
Further, the performing version upgrade operations according to the upgrade package information configuration file and the second system information configuration file includes:
backing up files needing to be replaced;
updating the module to be upgraded according to the module processing mode recorded in the second system information configuration file;
performing upgrading subsequent operation by taking the module as a unit;
and checking whether the MD5 value of the updated file is consistent with the MD5 value in the upgrade package information configuration file.
By using the software version management method provided by the invention, manual intervention is avoided through software automation processing, so that the safety and reliability of software upgrading are improved.
In a second aspect, an embodiment of the present application further provides a system software version management apparatus, including:
the automatic system software upgrading package packaging module is used for packaging the system software upgrading package and determining an upgrading package information configuration file;
the system information reconstruction module is used for acquiring a system information configuration file of a baseline version, and updating the upgrade package information configuration file into the system information configuration file of the baseline version to obtain a second system information configuration file;
and the software management module is used for carrying out version upgrading operation on the software system according to the upgrading package information configuration file and the second system information configuration file.
In a third aspect, an embodiment of the present application further provides a system software version management apparatus, including: a memory, a processor, and a user interface;
the memory for storing a computer program;
the user interface is used for realizing interaction with a user;
the processor is used for reading the computer program in the memory, and when the processor executes the computer program, the system software version management method provided by the invention is realized.
In a fourth aspect, an embodiment of the present invention further provides a processor-readable storage medium, where a computer program is stored in the processor-readable storage medium, and when the processor executes the computer program, the processor implements the system software version management method provided in the present invention.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic diagram of a system software version management method according to an embodiment of the present application;
FIG. 2 is a schematic diagram illustrating a process flow of system software packaging according to an embodiment of the present application;
fig. 3 is a schematic flowchart of an upgrade operation process provided in an embodiment of the present application;
fig. 4 is a schematic structural diagram of a system software version management apparatus according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of another system software version management device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer, the present invention will be described in further detail with reference to the accompanying drawings, and it is apparent that the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Some of the words that appear in the text are explained below:
1. the term "and/or" in the embodiments of the present invention describes an association relationship of associated objects, and indicates that three relationships may exist, for example, a and/or B may indicate: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.
2. In the embodiments of the present application, the term "plurality" means two or more, and other terms are similar thereto.
3. MD5, Message-Digest Algorithm5, a cryptographic hash function, may generate a 128-bit (16-byte) hash value to ensure that the Message is transmitted in a complete and consistent manner.
The software version upgrade in the system is processed by taking a software module as a unit, and one module can be installation software or a deployed software package or a set of configuration files of open source software. The module upgrade may be a full upgrade or an upgrade of a partial file.
The software version management of the complex system refers to the updating of modules in the system, and besides conventional operations such as file replacement, file deletion, updating installation, deletion installation and the like, operations with specific requirements such as configuration modification, command execution, script execution and the like can also be performed, and the updating of each module can have interdependence relation and can only function when the module needs to be updated cooperatively.
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that the display sequence of the embodiment of the present application only represents the sequence of the embodiment, and does not represent the merits of the technical solutions provided by the embodiments.
Example one
Referring to fig. 1, a schematic diagram of a system software version management method provided in an embodiment of the present application is shown, where the method includes steps S101 to S103:
s101, packaging a system software upgrading package, and determining an upgrading package information configuration file;
s102, acquiring a system information configuration file of a baseline version, and updating the upgrade package information configuration file into the system information configuration file of the baseline version to obtain a second system information configuration file;
s103, carrying out version upgrading operation according to the upgrading package information configuration file and the second system information configuration file.
Through the steps, the software automatically encapsulates the upgrade file, automatically checks the upgrade file and automatically performs upgrade operation, so that the risk caused by manual intervention is avoided, and the safety and efficiency of software upgrade are improved.
As a preferable example, before the step S101, the method further includes:
and determining a module upgrading information configuration file, wherein the module upgrading information configuration file is used for recording the names, MD5 values, relative paths and processing modes of all files involved in the upgrading.
It should be noted that the module upgrade information configuration file may be provided by a module developer.
Preferably, the module upgrade information configuration file may be a json file, such as a fileinfo. Each upgrading module of the file is attached with a file for recording the names, MD5 values, relative paths, processing modes and other information of all files related to the current module in the upgrading. As a preferred example, the processing method information may not be filled, and if the processing method is not filled, the processing is performed by a replacement or installation method by default.
It should be noted that, the module upgrade information configuration file and all related files are submitted to an upgrade version library (the submission may be to generate a new file or to update an original file), and the upgrade version library is monitored by continuous integration software such as jenkins and the like for a version update event, so as to automatically trigger the execution of step S101, or trigger the execution of step S101 through a preset start button.
As a preferred example, the step S101 specifically includes the following steps, as shown in fig. 2, including steps S201 to S204:
s201, verifying the file name and the relative path;
as an optional scheme, if the verification passes, S202 is executed, and if the verification fails, an alarm is triggered, and an alarm message is sent to a preset target device or target software, or a related person is notified by an email.
S202, calculating an MD5 value, and carrying out integrity check according to the MD5 value in the module upgrading information configuration file; as a preferred example, a file provided by a developer calculates the MD5 value to be 20abe48e15 leaf 253a389062cf29df72, but the MD5 value of the file is 11526c9bc771f38fd99fce7690d54bb2 recorded in the module upgrading information configuration file, and the file can be judged to be damaged or tampered if the values are inconsistent.
In this step, the MD5 value is calculated for all files involved in the current module upgrade. After the calculation is completed, the MD5 value in the module upgrade information configuration file corresponding to the current module is read, and the two MDs 5 are checked (for example, whether the comparison is the same or not). It should be noted that the verification operation in this step is performed on all modules that need to be upgraded.
As an optional scheme, if all the modules pass the verification, the step S203 is continuously executed, and if not all the modules pass the verification, an alarm is triggered, and an alarm message is sent to a preset target device or target software, or a related person is notified in an email manner.
S203, packaging all upgrading modules of the current version into a compression package;
in this step, in order to reduce the risk that a plurality of files in one version are delayed before and after transmission or a certain file fails to be transmitted, files related to all modules of which the current version needs to be upgraded are packaged into a compressed package.
And S204, determining the upgrade package information configuration file according to the module upgrade information configuration file contents of all the modules.
In this step, the module upgrade information configuration Files (for example, file info. json Files of all modules) of all modules are merged into one file to form an upgrade Package information configuration file (Package InfoModel Files).
And completing the packaging of the software upgrading package of the automatic system after the steps S201 to S204.
As another preferred example, in step S102, the system information configuration file of the baseline version is used to record the last version and the system-related full-scale information, where the full-scale information may include one or a combination of the following:
operating system type and version number;
all installed software names in the system, the names of the corresponding dependency libraries of the installed software, the version numbers of the installed software and the version numbers of the installed dependency libraries;
system-related configuration information; specifically, the configuration information related to the system may include network card information, routing information, network firewall information, system kernel parameters, system startup start-up items, system timing tasks, and the like.
Developed software or module related information.
It should be noted that the developed software or module refers to software or module developed by a product developer besides an operating system, and the software that needs to be upgraded in this embodiment is included in the developed software or module.
As a preferred example, the software or module related information developed above includes one or a combination of the following:
a module name;
all file names contained by the module;
the file upgrading method comprises the following steps of (1) upgrading a file, wherein the upgrading method can comprise one of installation, replacement, deletion or addition;
the installation position of the file;
a file source location;
file MD5 values;
file permissions;
the group to which the file belongs;
the subsequent operation mode of the file upgrade can comprise executing a script or executing a command.
If a plurality of modules are involved, each module includes the software developed as described above or information related to the module.
As another preferred example, in the step S103, performing a version upgrade operation according to the upgrade package information configuration file and the second system information configuration file includes steps S301 to S304 shown in fig. 3:
s301, backing up files needing to be replaced;
in this step, all files to be replaced by the upgrade operation are backed up so as to be used for the software version rollback operation. The backup modes corresponding to different processing modes are different. For example, if the module upgrade is an upgrade in an alternate manner, the backup operation precedes the replacement; if the module is upgraded in an installation mode, the backup operation is performed after the module is upgraded successfully.
S302, updating the module to be upgraded according to the module processing mode;
the module processing mode in this step is to search in the upgrade package information configuration file preferentially, and if not found, to search in the second system information configuration file.
S303, performing upgrading subsequent operation by taking the module as a unit;
the subsequent operation mode in this step is preferably searched in the upgrade package information configuration file, and if not found, the upgrade package information configuration file is searched in the second system information configuration file.
S304, checking whether the MD5 value of the updated file is consistent with the MD5 value in the upgrade package information configuration file.
In this step, if the MD5 value of the updated file is consistent with the MD5 value in the upgrade package information configuration file, the upgrade operation is successful, otherwise, an error may be reported to the network server by triggering an http request and recorded.
By the method, software automatically checks and encapsulates the upgrade file, automatically reads the baseline version information, generates a new system information configuration file according to the upgrade file and the baseline version information, and performs checking and upgrade package encapsulation and upgrade package installation processes according to developed software or module related information recorded in the system information configuration file, manual participation is not needed, uncertain factors are prevented from being introduced by manual participation, and safety and reliability of software version management are improved.
Example two
Based on the same inventive concept, an embodiment of the present invention further provides a system software version management apparatus, as shown in fig. 4, the apparatus includes:
an automatic system software upgrade package packaging module 401, configured to package a system software upgrade package and determine an upgrade package information configuration file;
a system information reconstruction module 402, configured to obtain a system information configuration file of a baseline version, and update the upgrade package information configuration file to the system information configuration file of the baseline version to obtain a second system information configuration file;
the software management module 403 is configured to perform version upgrade operations according to the upgrade package information configuration file and the second system information configuration file.
It should be noted that the automation system software upgrade package encapsulation module 401 provided in this embodiment can implement all the functions included in step S101 in fig. 1, solve the same technical problem, achieve the same technical effect, and is not described herein again;
accordingly, the system information reconstruction module 402 provided in this embodiment can implement all the functions included in step S102 in fig. 1, solve the same technical problem, and achieve the same technical effect, which is not described herein again.
Accordingly, the software management module 403 provided in this embodiment can implement all the functions included in step S103 in fig. 1, solve the same technical problem, and achieve the same technical effect, which is not described herein again.
It should be noted that the apparatus provided in the second embodiment and the method provided in the first embodiment belong to the same inventive concept, solve the same technical problem, and achieve the same technical effect, and the apparatus provided in the second embodiment can implement all the methods of the first embodiment, and the same parts are not described again.
EXAMPLE III
Based on the same inventive concept, an embodiment of the present invention further provides a system software version management apparatus, as shown in fig. 5, the apparatus includes:
comprising a memory 502, a processor 501 and a user interface 503;
the memory 502 for storing a computer program;
the user interface 503 is used for realizing interaction with a user;
the processor 501 is configured to read the computer program in the memory 502, and when the processor 501 executes the computer program, the processor 501 implements:
packaging the system software upgrading package, and determining an upgrading package information configuration file;
acquiring a system information configuration file of a baseline version, and updating the upgrade package information configuration file into the system information configuration file of the baseline version to obtain a second system information configuration file;
and carrying out version upgrading operation according to the upgrading package information configuration file and the second system information configuration file.
Where in fig. 5 the bus architecture may include any number of interconnected buses and bridges, in particular one or more processors represented by processor 501 and various circuits of memory represented by memory 502, linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The processor 501 is responsible for managing the bus architecture and general processing, and the memory 502 may store data used by the processor 501 in performing operations.
The processor 501 may be a CPU, an ASIC, an FPGA, or a CPLD, and the processor 501 may also adopt a multi-core architecture.
The processor 501, when executing the computer program stored in the memory 502, implements any of the system software version management methods shown in fig. 1 to 3.
It should be noted that the apparatus provided in the third embodiment and the method provided in the first embodiment belong to the same inventive concept, solve the same technical problem, and achieve the same technical effect, and the apparatus provided in the third embodiment can implement all the methods of the first embodiment, and the same parts are not described again.
The present application also proposes a processor-readable storage medium. Wherein the processor-readable storage medium stores a computer program, and the processor implements any one of the software version management methods shown in fig. 1 to 3 when executing the computer program.
It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation. In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.
Claims (11)
1. A system software version management method is characterized by comprising the following steps:
packaging the system software upgrading package, and determining an upgrading package information configuration file;
acquiring a system information configuration file of a baseline version, and updating the upgrade package information configuration file into the system information configuration file of the baseline version to obtain a second system information configuration file;
and carrying out version upgrading operation on the software system according to the upgrading package information configuration file and the second system information configuration file.
2. The method of claim 1, wherein before encapsulating the system software upgrade package and determining the upgrade package information configuration file, further comprising:
determining a module upgrading information configuration file, wherein the module upgrading information configuration file is used for recording the names, MD5 values, relative paths and processing modes of all files related to the module in the upgrading.
3. The method of claim 2, wherein encapsulating the system software upgrade package and determining an upgrade package information configuration file comprises:
verifying the file name and the relative path;
calculating the MD5 value of the file in the upgrade package, and carrying out integrity check comparison according to the MD5 value in the information configuration file of the upgrade package to realize the integrity check of the file before the upgrade package is packaged;
packaging all upgrading modules of the current version into a compression package;
and determining the upgrade package information configuration file according to the module upgrade information configuration file contents of all the modules.
4. The method of claim 1, wherein the baseline version of the system information profile comprises one or a combination of:
operating system type and version number;
all installed software names, corresponding dependent library names, version numbers of installed software and version numbers of installed dependent libraries in the system;
system-related configuration information;
developed software or module related information.
5. The method of claim 4, wherein the developed software or module related information comprises one or a combination of:
a module name;
all file names contained by the module;
upgrading the file;
the installation position of the file;
a file source location;
file MD5 values;
file permissions;
the group to which the file belongs;
and upgrading the subsequent operation mode of the file.
6. The method of claim 5, wherein the piece upgrade processing mode comprises one of:
install, replace, delete, or add.
7. The method of claim 5, wherein the file upgrade follow-up operation comprises:
execute a script or execute a command.
8. The method of claim 1, wherein performing a version upgrade operation according to the upgrade package information configuration file and the second system information configuration file comprises:
backing up files needing to be replaced;
updating the module to be upgraded according to the module processing mode recorded in the second system information configuration file;
performing upgrading subsequent operation by taking the module as a unit;
and checking whether the MD5 value of the updated file is consistent with the MD5 value in the upgrade package information configuration file.
9. A system software version management apparatus, comprising:
the automatic system software upgrading package packaging module is used for packaging the system software upgrading package and determining an upgrading package information configuration file;
the system information reconstruction module is used for acquiring a system information configuration file of a baseline version, and updating the upgrade package information configuration file into the system information configuration file of the baseline version to obtain a second system information configuration file;
and the software management module is used for carrying out version upgrading operation according to the upgrading package information configuration file and the second system information configuration file.
10. A system software version management device comprising a memory, a processor and a user interface;
the memory for storing a computer program;
the user interface is used for realizing interaction with a user;
the processor, configured to read the computer program in the memory, and when the processor executes the computer program, implement the system software version management method according to one of claims 1 to 8.
11. A processor-readable storage medium, characterized in that the processor-readable storage medium stores a computer program which, when executed by a processor, implements a system software version management method according to one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011199164.3A CN112306552A (en) | 2020-11-01 | 2020-11-01 | System software version management method, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011199164.3A CN112306552A (en) | 2020-11-01 | 2020-11-01 | System software version management method, device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112306552A true CN112306552A (en) | 2021-02-02 |
Family
ID=74333341
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011199164.3A Pending CN112306552A (en) | 2020-11-01 | 2020-11-01 | System software version management method, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112306552A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113760354A (en) * | 2021-09-07 | 2021-12-07 | 广东电网有限责任公司 | Method and device for managing and controlling body information version of dispatching automation system |
| CN114356363A (en) * | 2021-11-30 | 2022-04-15 | 重庆长安汽车股份有限公司 | Online manufacturing method and management system of software upgrading package |
| CN116009912A (en) * | 2022-12-26 | 2023-04-25 | 郑州云智信安安全技术有限公司 | Construction method for automatically generating upgrade package aiming at private network environment |
| CN116028100A (en) * | 2022-07-29 | 2023-04-28 | 荣耀终端有限公司 | Software version upgrading method and electronic equipment |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101136770A (en) * | 2006-10-13 | 2008-03-05 | 中兴通讯股份有限公司 | Automatically updating method and apparatus for telecom multi-branch network management system |
| CN102045201A (en) * | 2010-12-27 | 2011-05-04 | 北京锐安科技有限公司 | Automatic upgrading method and system of intranet server cluster |
| CN102148714A (en) * | 2011-05-13 | 2011-08-10 | 大唐移动通信设备有限公司 | Method and device for upgrading software |
| CN103136013A (en) * | 2011-12-01 | 2013-06-05 | 腾讯科技（深圳）有限公司 | Method and system of software upgrade |
| WO2016086654A1 (en) * | 2014-12-03 | 2016-06-09 | 广州广电运通金融电子股份有限公司 | Remote upgrade method and system for software on self-service terminal, and upgrade package creation method |
| CN106484484A (en) * | 2016-10-20 | 2017-03-08 | 广东欧珀移动通信有限公司 | Application program installs management method and terminal unit |
| CN106528086A (en) * | 2016-10-10 | 2017-03-22 | 广州视源电子科技股份有限公司 | Method and system for upgrading Android software |
| CN106886422A (en) * | 2017-04-07 | 2017-06-23 | 广州华多网络科技有限公司 | Method for upgrading software and device, electronic equipment |
| CN107643920A (en) * | 2016-07-20 | 2018-01-30 | 平安科技（深圳）有限公司 | Application software update method and device |
| CN109582325A (en) * | 2017-09-28 | 2019-04-05 | 深圳市优必选科技有限公司 | Method for upgrading software, robot and the computer readable storage medium of robot |
| CN111142903A (en) * | 2019-12-23 | 2020-05-12 | 杭州安恒信息技术股份有限公司 | Configuration file interactive updating method and device based on file comparison |
-
2020
- 2020-11-01 CN CN202011199164.3A patent/CN112306552A/en active Pending
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101136770A (en) * | 2006-10-13 | 2008-03-05 | 中兴通讯股份有限公司 | Automatically updating method and apparatus for telecom multi-branch network management system |
| CN102045201A (en) * | 2010-12-27 | 2011-05-04 | 北京锐安科技有限公司 | Automatic upgrading method and system of intranet server cluster |
| CN102148714A (en) * | 2011-05-13 | 2011-08-10 | 大唐移动通信设备有限公司 | Method and device for upgrading software |
| CN103136013A (en) * | 2011-12-01 | 2013-06-05 | 腾讯科技（深圳）有限公司 | Method and system of software upgrade |
| WO2016086654A1 (en) * | 2014-12-03 | 2016-06-09 | 广州广电运通金融电子股份有限公司 | Remote upgrade method and system for software on self-service terminal, and upgrade package creation method |
| CN107643920A (en) * | 2016-07-20 | 2018-01-30 | 平安科技（深圳）有限公司 | Application software update method and device |
| CN106528086A (en) * | 2016-10-10 | 2017-03-22 | 广州视源电子科技股份有限公司 | Method and system for upgrading Android software |
| CN106484484A (en) * | 2016-10-20 | 2017-03-08 | 广东欧珀移动通信有限公司 | Application program installs management method and terminal unit |
| CN106886422A (en) * | 2017-04-07 | 2017-06-23 | 广州华多网络科技有限公司 | Method for upgrading software and device, electronic equipment |
| CN109582325A (en) * | 2017-09-28 | 2019-04-05 | 深圳市优必选科技有限公司 | Method for upgrading software, robot and the computer readable storage medium of robot |
| CN111142903A (en) * | 2019-12-23 | 2020-05-12 | 杭州安恒信息技术股份有限公司 | Configuration file interactive updating method and device based on file comparison |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113760354A (en) * | 2021-09-07 | 2021-12-07 | 广东电网有限责任公司 | Method and device for managing and controlling body information version of dispatching automation system |
| CN113760354B (en) * | 2021-09-07 | 2023-10-20 | 广东电网有限责任公司 | Ontology information version management and control method and device of dispatching automation system |
| CN114356363A (en) * | 2021-11-30 | 2022-04-15 | 重庆长安汽车股份有限公司 | Online manufacturing method and management system of software upgrading package |
| CN116028100A (en) * | 2022-07-29 | 2023-04-28 | 荣耀终端有限公司 | Software version upgrading method and electronic equipment |
| CN116028100B (en) * | 2022-07-29 | 2024-04-05 | 荣耀终端有限公司 | Software version upgrading method and electronic equipment |
| 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 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112306552A (en) | System software version management method, device and storage medium | |
| CN104679534B (en) | System application installation package loading processing method, apparatus and terminal | |
| US11392461B2 (en) | Method and apparatus for processing information | |
| US9205809B2 (en) | Vehicle unit and method for operating the vehicle unit | |
| US11144401B2 (en) | Component aware incremental backup, restore, and reconciliation solution | |
| CN111694592A (en) | Management method and system for project version release | |
| CN111506326A (en) | Method, device and equipment for upgrading terminal equipment and storage medium | |
| CN113342387A (en) | Automatic software upgrading method, updating client and updating server | |
| CN112035472A (en) | Data processing method, data processing device, computer equipment and storage medium | |
| CN111008034A (en) | Patch generation method and device | |
| CN106708550B (en) | Method and device for loading shared object library | |
| CN111651304B (en) | Software recovery method and device based on double-core intelligent ammeter and computer equipment | |
| KR102194974B1 (en) | System for monitoring and controling electric power system for process verification | |
| CN112732285A (en) | Upgrading method and device suitable for cloud computing linux operating system and electronic equipment | |
| EP3734445A1 (en) | Secure and reliable remote update of a control device in an elevator | |
| CN109408133B (en) | Method and equipment for starting assembly | |
| CN112685063B (en) | Feature library updating method, device, network equipment and readable storage medium | |
| CN114995958A (en) | Virtualization platform information consistency control method, device and medium | |
| CN114895916A (en) | Code deployment method, device, storage medium and electronic equipment | |
| CN114153503A (en) | BIOS control method, device and medium | |
| US11070377B1 (en) | Blended virtual machine approach for flexible production delivery of intelligent business workflow rules | |
| CN113806139A (en) | Operating system recovery method, operating system recovery device, storage medium and computer program product | |
| CN113360914A (en) | BIOS updating method, system, equipment and medium | |
| CN112579113A (en) | Application program upgrading method and device, storage medium and terminal | |
| CN113672269B (en) | Data processing method, system, electronic device and program product |
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 |