CN102193805B - Device and method for upgrading software patches - Google Patents
Device and method for upgrading software patches Download PDFInfo
- Publication number
- CN102193805B CN102193805B CN201010125112.1A CN201010125112A CN102193805B CN 102193805 B CN102193805 B CN 102193805B CN 201010125112 A CN201010125112 A CN 201010125112A CN 102193805 B CN102193805 B CN 102193805B
- Authority
- CN
- China
- Prior art keywords
- file
- patch
- software
- program
- bag
- 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.)
- Expired - Fee Related
Links
- 238000000034 method Methods 0.000 title claims abstract description 32
- 238000011084 recovery Methods 0.000 claims description 35
- 238000004140 cleaning Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 2
- 238000004590 computer program Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
Images
Landscapes
- Stored Programmes (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the invention discloses a method for upgrading software patches, which comprises the following steps of: receiving an upgrading instruction; after receiving the upgrading instruction, generating a backup program according to the file names and the directory structure in a patch file packet; calling the backup program and executing the backup operation; and executing the upgrading operation according to the files in the patch file packet. The method also can execute automatic rollback after upgrading is failed. The embodiment of the invention also provides a corresponding device. According to the technical scheme of the invention, the file names and the directory structure in the patch file packet are compared with the files of the upgraded software to generate the backup program, the backup program is called to execute the backup operation, and the patch file packet is called for executing the upgrading operation, so that the technical scheme of the invention can be used for backing up the upgraded software before the upgrading operation is executed.
Description
Technical field
The present invention relates to field of computer technology, be specifically related to a kind of software patch upgrading device and method.
Background technology
For the upgrading of Software Edition, mainly involve the modification of file, upgrading before backup and upgrade unsuccessfully after recover.In prior art, to the backup of upgrading preceding document, be to adopt the file that will upgrade to carry out independent backup, if upgraded unsuccessfully, according to the file of backup, system carried out to recovery operation.The backup of software, upgrading, recovery are all manual or complete by independent exploitation.In other words, in prior art, when carrying out updating operation, equipment can not complete the backup functionality of existing program, in the situation that upgrading is failed, can not realize auto restore facility.
Summary of the invention
The embodiment of the present invention provides a kind of software patch upgrading device and method, and this technical scheme can realize the backup functionality of program, and upgrade function can also be realized the unsuccessfully rear auto restore facility of upgrading.
A software patch upgrading method, comprising:
After receiving upgrade, according to filename and bibliographic structure in patch file bag, generate stand-by program;
Call described stand-by program, carry out backup operation;
According to file in described patch file bag, carry out updating operation.
A software patch upgrading device, comprising: receiver module, program generating module and scheduler module;
Described receiver module, for receiving upgrade;
Described program generating module, for after receiving upgrade, according to filename and bibliographic structure in patch file bag, generates stand-by program;
Described calling module, for calling described stand-by program, carries out backup operation; According to file in described patch file bag, carry out updating operation.
The embodiment of the present invention adopts filename and bibliographic structure in patch file bag, contrast with the file that is upgraded software, generate stand-by program, call this stand-by program, carry out backup operation, call patch file bag and carry out updating operation, the technical scheme that this enforcement provides can be realized being upgraded the backup of software before carrying out updating operation; Further, in stand-by program, can comprise the complete file that is upgraded software, in stand-by program, only need record to be upgraded file file and the position thereof different from file in patch file bag of software, thereby can generate more efficiently stand-by program.
Accompanying drawing explanation
In order to be illustrated more clearly in the technical scheme in the embodiment of the present invention, below the accompanying drawing of required use during embodiment is described is briefly described, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skills, do not paying under the prerequisite of creative work, can also obtain according to these accompanying drawings other accompanying drawing.
Fig. 1 is the structural representation of the software patch upgrading device that provides of the embodiment of the present invention;
Fig. 2 is the overview flow chart of the software patch upgrading method that provides of the embodiment of the present invention;
Fig. 3 is the particular flow sheet of the software patch upgrading method that provides of the embodiment of the present invention.
Embodiment
In order to make those skilled in the art person understand better the scheme of the embodiment of the present invention, below in conjunction with drawings and embodiments, the embodiment of the present invention is described in further detail.
Fig. 1 is the structural representation of software patch upgrading device in the embodiment of the present invention.This software patch upgrading device comprises: receiver module 11, program generating module 12 and scheduler module 13.
Wherein, receiver module 11, for receiving upgrade, sends to program generating module 13 by upgrade;
Program generating module 12, for after receiving upgrade, according to filename and bibliographic structure in patch file bag, generates stand-by program;
Wherein, in program generating module 12 according to filename in patch file and bibliographic structure, generate stand-by program, can be specifically: by filename in patch file and bibliographic structure, contrast with the filename and the bibliographic structure that are upgraded file, do not need to compare file content, according to the result after contrast, generate stand-by program.Because patch file bag exists and constant always, and bibliographic structure is identical with the bibliographic structure that is upgraded file, in stand-by program, can comprise the complete file that is upgraded software, in stand-by program, only need record to be upgraded file file and the position thereof different from file in patch file bag of software, thereby can generate more efficiently stand-by program.
The stand-by program that scheduler module 13 generates for calling program generation module 12, carries out backup operation; Scheduler module 13, also for calling patch file bag, is carried out updating operation;
Wherein, in scheduler module 13, carrying out updating operation can be specifically: required non-change file and the required change file of upgrading of upgrading in patch file bag in file covers the software document being upgraded.
By the explanation of the above-mentioned software patch upgrading device that the embodiment of the present invention is provided, this device Program generation module 12 is by filename and bibliographic structure in patch file bag, contrast with the file that is upgraded software, generate stand-by program, then, scheduler module 13 is called this stand-by program, carries out backup operation, and scheduler module 13 is called patch file bag and carried out updating operation.This device can be realized being upgraded the backup of software before carrying out updating operation;
Further, software patch upgrading device also comprises: memory module 14 is for storing patch file bag; Wherein, patch file bag comprises the file that upgrading is required, specifically can comprise: the required non-change file of upgrading, and the required change file of upgrading.It will be appreciated that, in patch file bag, non-change file refers to direct covering or newly-increased file, and the bibliographic structure of file is identical with existing bibliographic structure, if newly-increased file directory is non-existent or place according to the bibliographic structure after upgrading.According to this principle, configure after patch, just can complete the upgrading of patch by patch upgrading device.
Further, program generating module 12 contrasts filename and bibliographic structure in patch file bag and the file that is upgraded software, generate stand-by program, in stand-by program, can comprise the All Files that is upgraded software, in stand-by program, only need record to be upgraded file file and the position thereof different from file in patch file bag of software, thereby can generate more efficiently stand-by program.
Preferably, scheduler module 13 is also for judging that whether updating operation is failed, if updating operation failure, scheduler module 13 is also for the 12 updating operation failures of advising process generation module; Therefore, program generating module 12 is also for when updating operation when failure, according to filename and bibliographic structure in patch file bag, and file in the backup bag generating after backup operation, generate recovery routine; Scheduler module 13, also for calling the recovery routine of generation, is carried out recovery operation.
Wherein, program generating module 12 is according to filename and bibliographic structure in patch file bag, and file in the backup bag generating after backup operation, generates recovery routine and can sequentially comprise two parts, a part is to generate cleaning script, and another part is to generate to recover script.Wherein, filename and bibliographic structure in patch file bag, can be easy to know the particular location that is upgraded file in software that carries out updating operation, after updating operation failure, only need to will be upgraded in software by the local file full scale clearance of the coated lid of patch file.Based on this principle, program generating module 12 can generate the cleaning script in recovery routine.Further, recovering script utilizes the principle of the backup bag rollback system of backup operation generation to generate.Scheduler module 13 is called after recovery routine, carries out recovery operation, specifically can execution removing sequentially be coated with file in patch file bag, and the backup bag rollback system generating by backup operation, has realized system recovery.
By above-mentioned explanation, program generating module 12 and scheduler module 13 have realized the recovery of system after updating operation failure jointly, make the software patch upgrading device that the embodiment of the present invention provides can realize system restore funcitons.
Preferably, also it should be noted that, the order that program generating module 12 generates recovery routine can be not limited to above-mentioned after scheduler module 13 is carried out updating operation failure, also program generating module 12 can be after scheduler module 13 be carried out backup operation, according to filename and bibliographic structure in patch file bag, and file in the backup bag generating after backup operation, generate recovery routine; When scheduler module 13, carry out updating operation failure, directly call the recovery routine of generation.
Preferably, it can be to comprise non-change file that the patch file of storing in memory module 14 in the software patch upgrading device that the present embodiment provides wraps in while dispatching from the factory, and change file information.In other words, change file is not directly comprised in patch file bag, but, by modification information and the file that is changed software, indirectly acquire change file.Therefore the device that, the present embodiment provides can also comprise: acquisition module 15 and configuration module 16.
By to increasing acquisition module 15 and configuration module 16 in software patch upgrading device, this device can being utilized by the existing file that is upgraded software, and will all not store in service packs by All Files, the service packs while making to dispatch from the factory is simpler.
Figure 2 shows that a kind of software patch upgrading method overview flow chart that the embodiment of the present invention provides.The method that the present embodiment provides can be carried out according to filename and bibliographic structure in patch file bag before updating operation, generated stand-by program, and carried out stand-by program, realized being upgraded the backup of the file of software.The method comprises:
Step 201: receive upgrade;
Step 202: after receiving upgrade, according to filename and bibliographic structure in patch file bag,, generate stand-by program;
Wherein, in patch file bag, can comprise: non-change file, and change file.In patch file bag, change file can be that designer is preset in patch file bag, can be also the file that device obtains after execution is configured file in being upgraded software.
Step 203: call stand-by program, carry out backup operation;
Step 204: according to file in patch file bag, carry out updating operation.
The particular flow sheet of the software patch upgrading method that Fig. 3 provides for the embodiment of the present invention.
Below be described in detail.
Step 301: software patch upgrading device receives upgrade.In the present embodiment, upgrade can be to input to software patch upgrading device by site operation personnel.
Step 302: according to change file information, obtain change file information corresponding be upgraded file in software.Wherein, change file information can set in advance.
Wherein, change file information can make this update device obtain the program that will upgrade from be upgraded the program of software, is configured, thereby makes to get in service packs change file.In other words, " file obtaining after configuration " is exactly " change file " in patch file bag.
Step 303: according to change file information, the file in software that is upgraded obtaining is configured.In the present embodiment, the file that is upgraded in software obtaining is configured specifically and is comprised: to wherein any one or several operation of the increase of file, modification, deletion.The file that obtains after configuration is the change file in patch file bag.
For example: change file information is for being all revised as 5 respectively by being upgraded the value of parameter A and B parameter in the program of software, first this update device will get the file that is upgraded software, then the parameter being upgraded in the file of software is modified, amended file is just the change file in patch file bag.
Wherein, the configuration operation in above-mentioned steps 303 can be realized by JAVA (the concrete version adopting is JDK1.5), can on different platforms, move.By at extend markup language (Xml, ExtensibleMarkup Language) in file, to being upgraded the text that configures into of the file of software, increase, delete, revise wherein any one or several operation, the content that the operation of every type can locate by line number, also can comprise by row is located.The concrete operation of supporting is as shown in table 1, and wherein, the content in row content location is supported Java regular expression.
Table .1
Also it should be noted that, above-mentioned steps 302 and step 303 are can selection operation, if the patch file bag of storage comprises change file, software patch upgrading device can not carried out and obtain the file that needs change, and this document is configured.
Step 304: by filename and bibliographic structure in patch file bag, generate stand-by program; Wherein, patch file bag comprises: the change file forming after configuration in the non-change file of storage and step 303.
By filename in patch file and bibliographic structure, contrast with the filename and the bibliographic structure that are upgraded file, can, without documents content, according to the result after contrast, generate stand-by program.In the present embodiment by filename in patch file and bibliographic structure, with the file contrast that is upgraded software, because patch file bag exists and constant always, filename in patch file bag and bibliographic structure are identical with existing filename and the bibliographic structure that is upgraded software, in stand-by program, can comprise the complete file that is upgraded software, in stand-by program, only need record to be upgraded file file and the position thereof different from file in patch file bag of software, thereby can generate more efficiently stand-by program.(explanation of being convenient to understand is, file path in patch file bag is identical with the path that is upgraded file, the corresponding existing file being upgraded in software of file in generation stand-by program emphasis record and patch file bag under the filename at change file place, non-change file in patch file bag can be used as the file in stand-by program, but in patch file bag as except the file newly increasing of non-change file).For example: the filename in patch file bag with and bibliographic structure be consistent (comprising change file and non-change file) with the file in existing software systems, so just can and copy the dest program of " directories/files title " under (copy) software root directory by All Files in traversal patch file bag, then automatically perform this program, finally in dest catalogue, can comprise the file (this stand-by program and patch file bag are corresponding) of all needs backups.
Step 305: call stand-by program, carry out backup operation.In the present embodiment, after carrying out backup operation, can generate backup bag.
Here the object that generates backup bag is, how in the failed situation of upgrading, can call this backup bag, again upgrades, and so just can enter fast quick-recovery upgrading.
Step 306: according to file in patch file bag, carry out updating operation.Wherein, updating operation can be specifically: required non-change file and the required change file of upgrading of upgrading in patch file bag in file covers the software document being upgraded.
By the explanation of the above-mentioned software patch upgrading method that the embodiment of the present invention is provided, the method adopts filename and bibliographic structure in patch file bag, contrast with the file that is upgraded software, generate stand-by program, then, call this stand-by program, carry out backup operation, call patch file bag and carry out updating operation.This device can be realized being upgraded the backup of software before carrying out updating operation;
Further, due to filename and bibliographic structure in patch file bag and the file that is upgraded software are contrasted, generate stand-by program, in stand-by program, can comprise the complete file that is upgraded software, in stand-by program, only need record to be upgraded file file and the position thereof different from file in patch file bag of software, thereby can generate more efficiently stand-by program.
Preferably, the method can also comprise:
Step 306: judge that whether updating operation is failed, if so, execution step 307, if not, can finish.
Step 307: according to filename and bibliographic structure in patch file bag, and file in the backup bag generating after backup operation, generate recovery routine.
Wherein, in step 307, according to filename and bibliographic structure in patch file bag, and file in the backup bag generating after backup operation, generates the two parts that comprise that recovery routine can order, and a part is to generate cleaning script, and another part is to generate to recover script.Wherein, filename and bibliographic structure in patch file bag, can be easy to know the particular location that is upgraded file in software that carries out updating operation, after updating operation failure, only need to will be upgraded in software by the local file full scale clearance of the coated lid of patch file.Based on this principle, this device can generate the cleaning script in recovery routine.Further, recovering script utilizes the principle of the backup bag rollback system of backup operation generation to generate.
Step 308: call the recovery routine of generation, carry out recovery operation.
It should be noted that, call after recovery routine in step 308, carry out recovery operation, specifically can execution removing sequentially be coated with file in patch file bag, the backup bag rollback system generating by backup operation, has realized system recovery.
By increasing above-mentioned steps 306 to step 308, the method has realized the recovery of system after updating operation failure, makes the software patch upgrading device that the embodiment of the present invention provides can realize system restore funcitons.
Also it should be noted that, above-mentioned steps 307 can be carried out afterwards in execution backup operation (being step 305),, after backup operation, generates recovery routine.If updating operation failure, directly calls this recovery routine, carry out recovery operation.By increasing step 307, make the method that the present embodiment provides can generate recovery routine.
In sum, this technical scheme does not need to develop patch upgrading script, as long as it is just passable to complete the configuration of patch file bag and change file modification, makes developer be not related to the engineerings such as footnote basis, patch upgrading.When simplifying performance history, be that peopleware is more absorbed in professional ability, greatly improved efficiency.
Further, by automatic generation stand-by program and/or recovery routine, software upgrading engineering is solidified, reduced the risk in escalation process.
One of ordinary skill in the art will appreciate that all or part of flow process realizing in above-described embodiment method, to come the hardware that instruction is relevant to complete by computer program, described program can be stored in computer read/write memory medium, this program, when carrying out, can comprise as the flow process of the embodiment of above-mentioned each side method.Wherein, described storage medium can be magnetic disc, CD, read-only store-memory body (Read-Only Memory, ROM) or random store-memory body (Random Access Memory, RAM) etc.
Above the embodiment of the present invention is described in detail, has applied embodiment herein the present invention is set forth, the explanation of above embodiment is just for helping to understand method and apparatus of the present invention; , for one of ordinary skill in the art, according to thought of the present invention, all will change in specific embodiments and applications, in sum, this description should not be construed as limitation of the present invention meanwhile.
Claims (11)
1. a software patch upgrading method, is characterized in that, comprising:
After receiving upgrade, according to filename and bibliographic structure in patch file bag, generate stand-by program;
Call described stand-by program, carry out backup operation;
According to file in described patch file bag, carry out updating operation.
2. method according to claim 1, is characterized in that, described according to filename and bibliographic structure in patch file bag, generates stand-by program, specifically comprises:
By filename in patch file and bibliographic structure, contrast with the filename and the bibliographic structure that are upgraded file, according to the result after contrast, generate stand-by program.
3. method according to claim 1, is characterized in that, described method also comprises:
According to filename and bibliographic structure in described patch file bag, and file in the backup bag generating after backup operation, recovery routine generated;
After determining described updating operation failure, call described recovery routine, carry out recovery operation.
4. method according to claim 1, is characterized in that, described method also comprises:
According to preset change file information, obtain and be upgraded file in software;
According to described change file information, the file in software that is upgraded obtaining is configured;
Described patch file bag comprises the file obtaining after described configuration.
5. method according to claim 4, is characterized in that, described according to change file information, and the file in software that is upgraded obtaining is configured, and specifically comprises:
According to change file information, the file in software that is upgraded obtaining is increased, delete, or revise wherein any one or several operation.
6. a software patch upgrading device, is characterized in that, comprising: receiver module, program generating module and scheduler module;
Described receiver module, for receiving upgrade;
Described program generating module, for after receiving upgrade, according to filename and bibliographic structure in patch file bag, generates stand-by program;
Described scheduler module, for calling described stand-by program, carries out backup operation; According to file in described patch file bag, carry out updating operation.
7. device according to claim 6, is characterized in that, described program generating module also for according to described patch file bag filename and bibliographic structure, and is carried out file in the backup bag generating after backup operation, generates recovery routine;
Described scheduler module also, for judging that whether described updating operation is failed, if so, is called described recovery routine, carries out recovery operation.
8. device according to claim 6, is characterized in that, described device also comprises: acquisition module and configuration module;
Described acquisition module, for according to preset change file information, obtains and is upgraded file in software;
Described configuration module, for according to described change file information, is configured the file in software that is upgraded obtaining; Wherein, described patch file bag comprises the file obtaining after described configuration.
9. device according to claim 8, is characterized in that, described configuration module, specifically for according to change file information, increases the file in software that is upgraded obtaining, and deletes, or revises wherein any one or several operation.
10. device according to claim 6, is characterized in that, described device also comprises: memory module, and for storing patch file bag.
11. devices according to claim 6, is characterized in that, described program generating module, specifically for by filename in patch file and bibliographic structure, contrast with the filename and the bibliographic structure that are upgraded file, according to the result after contrast, generate stand-by program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010125112.1A CN102193805B (en) | 2010-03-11 | 2010-03-11 | Device and method for upgrading software patches |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010125112.1A CN102193805B (en) | 2010-03-11 | 2010-03-11 | Device and method for upgrading software patches |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102193805A CN102193805A (en) | 2011-09-21 |
| CN102193805B true CN102193805B (en) | 2014-05-07 |
Family
ID=44601923
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010125112.1A Expired - Fee Related CN102193805B (en) | 2010-03-11 | 2010-03-11 | Device and method for upgrading software patches |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102193805B (en) |
Families Citing this family (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103049343B (en) * | 2011-10-14 | 2016-08-17 | 腾讯科技（深圳）有限公司 | Operating system blue screen restoration methods and device |
| CN102609328B (en) * | 2012-01-29 | 2015-04-15 | 华为终端有限公司 | System difference upgrade method and device and mobile terminal |
| CN102693143B (en) * | 2012-05-22 | 2015-03-11 | 华为技术有限公司 | Method and device for installing patch |
| US20140136487A1 (en) * | 2012-11-14 | 2014-05-15 | International Business Machines Corporation | Content management targeted rollback |
| CN103064715A (en) * | 2013-01-09 | 2013-04-24 | 上海大唐移动通信设备有限公司 | Remote upgrade method and system for automatic drive test systems |
| CN104461612B (en) * | 2014-11-12 | 2018-05-04 | 上海华为技术有限公司 | A kind of data processing method and device |
| CN106161061B (en) * | 2015-04-08 | 2020-01-31 | 华为技术有限公司 | Service configuration rollback method and network equipment |
| CN105868048A (en) * | 2015-12-11 | 2016-08-17 | 乐视移动智能信息技术（北京）有限公司 | Backup method and apparatus in android system upgrading and related device |
| CN105872778A (en) * | 2016-03-31 | 2016-08-17 | 乐视控股（北京）有限公司 | Upgrading control method and device |
| CN108664255B (en) * | 2017-03-27 | 2023-04-11 | 深圳市中兴通讯技术服务有限责任公司 | Software upgrading method and device |
| CN107861747A (en) * | 2017-06-26 | 2018-03-30 | 平安普惠企业管理有限公司 | Product renewing method, equipment and computer-readable recording medium |
| CN107908441B (en) * | 2017-12-06 | 2021-07-02 | 郑州云海信息技术有限公司 | Database upgrading method and upgrading device |
| CN111562934B (en) * | 2020-04-03 | 2023-08-11 | 深圳震有科技股份有限公司 | Software system upgrading method based on hot patch, terminal and storage medium |
| CN112579139B (en) * | 2020-12-09 | 2024-07-12 | 北京红山信息科技研究院有限公司 | Multi-cluster patch updating method, system, server and storage medium |
| CN112732292B (en) * | 2020-12-30 | 2024-02-23 | 北京浪潮数据技术有限公司 | Method, system, equipment and readable storage medium for upgrading software |
| CN113157286A (en) * | 2021-04-20 | 2021-07-23 | 深圳市优必选科技股份有限公司 | System upgrading method and device |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1409239A (en) * | 2001-09-14 | 2003-04-09 | 北京瑞星科技股份有限公司 | Method for upgrading software |
| CN101377744A (en) * | 2008-09-24 | 2009-03-04 | 深圳华为通信技术有限公司 | Method and apparatus for recovering terminal equipment software upgrade |
-
2010
- 2010-03-11 CN CN201010125112.1A patent/CN102193805B/en not_active Expired - Fee Related
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1409239A (en) * | 2001-09-14 | 2003-04-09 | 北京瑞星科技股份有限公司 | Method for upgrading software |
| CN101377744A (en) * | 2008-09-24 | 2009-03-04 | 深圳华为通信技术有限公司 | Method and apparatus for recovering terminal equipment software upgrade |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102193805A (en) | 2011-09-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102193805B (en) | Device and method for upgrading software patches | |
| US10922067B1 (en) | System and method for installing, updating and uninstalling applications | |
| CN102609328B (en) | System difference upgrade method and device and mobile terminal | |
| US6442754B1 (en) | System, method, and program for checking dependencies of installed software components during installation or uninstallation of software | |
| US20160026452A1 (en) | Efficient deployment of application revisions and implementation of application rollbacks across multiple application servers | |
| US11662996B2 (en) | System and method for downgrading applications | |
| US20160378458A1 (en) | Method and device for system application installation package, and terminal | |
| US20110138374A1 (en) | Downtime reduction for enterprise manager patching | |
| CN1936844A (en) | Method and system for updating software | |
| KR20110086732A (en) | Application restore points | |
| CN113032032B (en) | System management method and device, computing equipment and readable storage medium | |
| CN112463191A (en) | File updating method and device, equipment and storage medium | |
| CN102346673A (en) | Method and device for upgrading mobile phone system | |
| CA2860657C (en) | Installation engine and package format for parallelizable, reliable installations | |
| US20150242282A1 (en) | Mechanism to update software packages | |
| US20100211943A1 (en) | Method for simplifying process for installing application of windows operating system | |
| CN111611160B (en) | Software testing method, device, equipment and storage medium | |
| CN104331311A (en) | Upgrade package generating method and device | |
| CN116028084A (en) | Cross-version hot upgrading method, system and terminal based on OpenStack cloud platform | |
| JP5052472B2 (en) | Program setting information switching system and switching method | |
| CN115145596A (en) | OTA (over the air) upgrading method and device for robot upgrading package | |
| Cisco | Software Upgrade | |
| Cisco | Using the Configuration Save and Restore Feature | |
| Cisco | Configuration Save and Restore | |
| CN107608698B (en) | Command line tool updating method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20140507 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |