CN102193805A - Device and method for upgrading software patches - Google Patents
Device and method for upgrading software patches Download PDFInfo
- Publication number
- CN102193805A CN102193805A CN2010101251121A CN201010125112A CN102193805A CN 102193805 A CN102193805 A CN 102193805A CN 2010101251121 A CN2010101251121 A CN 2010101251121A CN 201010125112 A CN201010125112 A CN 201010125112A CN 102193805 A CN102193805 A CN 102193805A
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 32
- 238000011084 recovery Methods 0.000 claims description 37
- 238000012217 deletion Methods 0.000 claims description 5
- 230000037430 deletion Effects 0.000 claims description 5
- 238000004140 cleaning Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 239000011248 coating agent Substances 0.000 description 2
- 238000000576 coating method Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 239000012467 final product Substances 0.000 description 2
- 238000004590 computer program Methods 0.000 description 1
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
Upgrading for Software Edition mainly involves file modifying, recovers after backup and the upgrading failure before the upgrading.Backup to the upgrading preceding document in the prior art is to adopt the file that will upgrade is carried out independent backup, if the upgrading failure is carried out recovery operation according to the file that backs up to system.The backup of software, upgrading, recovery all are to finish by hand or by independent exploitation.In other words, when carrying out updating operation, equipment can not be finished the backup functionality of existing program in the prior art, under the situation of upgrading failure, can not realize auto restore facility.
Summary of the invention
The embodiment of the 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 upgrading failure back auto restore facility.
A kind of software patch upgrading method comprises:
After receiving upgrade,, generate stand-by program according to filename and bibliographic structure in the patch file bag;
Call described stand-by program, carry out backup operation;
According to file in the described patch file bag, carry out updating operation.
A kind of software patch upgrading device comprises: receiver module, program generating module and scheduler module;
Described receiver module is used to receive upgrade;
Described program generating module is used for after receiving upgrade, according to filename and bibliographic structure in the patch file bag, generates stand-by program;
Described calling module is used to call described stand-by program, carries out backup operation; According to file in the described patch file bag, carry out updating operation.
The embodiment of the invention adopts filename and bibliographic structure in the patch file bag, compare with the file that is upgraded software, generate stand-by program, call this stand-by program, carry out backup operation, call the patch file bag and carry out updating operation, the technical scheme that makes this enforcement provide can realize being upgraded the backup of software before carrying out updating operation; Further, can comprise the complete file that is upgraded software in the stand-by program, in stand-by program, only need record to be upgraded file file and the position thereof different of software, thereby can generate stand-by program more efficiently with file in the patch file bag.
Description of drawings
In order to be illustrated more clearly in the technical scheme in the embodiment of the invention, the accompanying drawing of required use is done to introduce simply in will describing embodiment below, apparently, accompanying drawing in describing below only is some embodiments of the present invention, for those of ordinary skills, under the prerequisite of not paying creative work, can also obtain other accompanying drawing according to these accompanying drawings.
Fig. 1 is the structural representation of the software patch upgrading device that provides of the embodiment of the invention;
Fig. 2 is the overview flow chart of the software patch upgrading method that provides of the embodiment of the invention;
Fig. 3 is the particular flow sheet of the software patch upgrading method that provides of the embodiment of the invention.
Embodiment
In order to make those skilled in the art person understand the scheme of the embodiment of the invention better, the embodiment of the invention is described in further detail below in conjunction with drawings and embodiments.
Fig. 1 is the structural representation of software patch upgrading device in the embodiment of the invention.This software patch upgrading device comprises: receiver module 11, program generating module 12 and scheduler module 13.
Wherein, receiver module 11 is used to receive upgrade, and upgrade is sent to program generating module 13;
Program generating module 12 is used for after receiving upgrade, according to filename and bibliographic structure in the patch file bag, generates stand-by program;
Wherein, in the program generating module 12 according to filename in the patch file and bibliographic structure, generate stand-by program, specifically can be: with filename in the patch file and bibliographic structure, compare with filename that is upgraded file and bibliographic structure, do not need to compare file content,, generate stand-by program according to the result after the contrast.Because the patch file bag exists and is constant always, and bibliographic structure is identical with the bibliographic structure that is upgraded file, can comprise the complete file that is upgraded software in the stand-by program, in stand-by program, only need record to be upgraded file file and the position thereof different of software, thereby can generate stand-by program more efficiently with file in the patch file bag.
Scheduler module 13 is used for the stand-by program that calling program generation module 12 generates, and carries out backup operation; Scheduler module 13 also is used to call the patch file bag, carries out updating operation;
Wherein, carrying out updating operation in the scheduler module 13 can be specifically: the required change file of non-change file that the upgrading in the patch file bag in the file is required and upgrading covers the software document that is upgraded.
Explanation by the above-mentioned software patch upgrading device that the embodiment of the invention is provided, program generating module 12 is with filename and bibliographic structure in the patch file bag in this device, compare 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 the patch file bag and carried out updating operation.Make this device before carrying out updating operation, can realize to being upgraded the backup of software;
Further, the software patch upgrading device also comprises: memory module 14 is used to store the patch file bag; Wherein, comprise the file that upgrading is required in the patch file bag, specifically can comprise: the upgrade required non-change file and the required change file of upgrading.It will be appreciated that non-change file is meant direct covering or newly-increased file in the patch file bag, the bibliographic structure of file is identical with existing bibliographic structure, still places according to the bibliographic structure after the upgrading if newly-increased file directory is non-existent.After configuring patch according to this principle, just can finish the upgrading of patch by the patch upgrading device.
Further, program generating module 12 compares filename and bibliographic structure in the patch file bag and the file that is upgraded software, generate stand-by program, can comprise the All Files that is upgraded software in the stand-by program, in stand-by program, only need record to be upgraded file file and the position thereof different of software, thereby can generate stand-by program more efficiently with file in the patch file bag.
Preferably, scheduler module 13 is used to also judge whether updating operation fails, if the updating operation failure, then scheduler module 13 also is used for the failure of advising process generation module 12 updating operation; Therefore, program generating module 12 also is used for when updating operation is failed, according to filename and bibliographic structure in the patch file bag, and file in the backup bag that generates after the backup operation, generate recovery routine; Scheduler module 13 also is used to call the recovery routine of generation, carries out recovery operation.
Wherein, program generating module 12 is according to filename and bibliographic structure in the patch file bag, and file in the backup bag that generates after the backup operation, generates recovery routine and can comprise two parts in proper order, a part is to generate the cleaning script, and another part is to generate to recover script.Wherein, by filename and bibliographic structure in the patch file bag, can be easy to know the particular location that is upgraded file in the software that carries out updating operation, after the updating operation failure, only need to be upgraded in the software by the local file full scale clearance of patch file coating lid.Based on this principle, program generating module 12 can generate the cleaning script in the recovery routine.Further, recovering script utilizes the principle of the backup bag rollback system of backup operation generation to generate.After scheduler module 13 is called recovery routine, carry out recovery operation, specifically can execution removing in proper order be coated with file in the patch file bag, the backup bag rollback system with backup operation generates has realized system recovery.
By above-mentioned explanation, program generating module 12 and scheduler module 13 have realized that jointly the software patch upgrading device that makes the embodiment of the invention provide can be realized the system recovery function in the recovery of updating operation failure back system.
Preferably, also need to prove, the order that program generating module 12 generates recovery routine can be not limited to above-mentioned after scheduler module 13 is carried out the 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 the patch file bag, and file in the backup bag that generates after the backup operation, generate recovery routine; Carry out the updating operation failure when scheduler module 13, the recovery routine that directly calls generation gets final product.
Preferably, it can be to comprise non-change file that the patch file of storing in the memory module 14 in the software patch upgrading device that present embodiment provides wraps in when dispatching from the factory, and change file information.In other words, change file directly is not comprised in the patch file bag, but, by modification information with by the file of change software, the indirect change file that acquires.Therefore, the device that provides of present embodiment can also comprise: acquisition module 15 and configuration module 16.
Acquisition module 15 is used for according to patch file bag change file information, obtains and is upgraded file in the software; File stores in the service packs in the software with being upgraded of obtaining; Configuration module 16 is according to the change file information of storage, file is configured in the software to being upgraded of obtaining, and configuration module specifically is used for according to change file information, and file increases in the software to being upgraded of obtaining, any one or several operation are perhaps revised wherein in deletion.Change file in the just above-mentioned said patch file bag of file after the configuration.
Had now the file that is upgraded software by making this device to utilize, and will all do not stored in the service packs by All Files, made that the service packs when dispatching from the factory is simpler increase acquisition module 15 and configuration module 16 in the software patch upgrading device.
Figure 2 shows that a kind of software patch upgrading method overview flow chart that the embodiment of the invention provides.The method that present embodiment provides can be carried out according to filename and bibliographic structure in the patch file bag before updating operation, generated stand-by program, and carried out stand-by program, realized the backup to the file that is upgraded software.This method comprises:
Step 201: receive upgrade;
Step 202: after receiving upgrade, according to filename and bibliographic structure in the patch file bag,, generate stand-by program;
Wherein, can comprise in the patch file bag: non-change file, and change file.Change file can be that the designer is preset in the patch file bag in the patch file bag, also can be that device is being carried out being upgraded the file that obtains after file is configured in the software.
Step 203: call stand-by program, carry out backup operation;
Step 204:, carry out updating operation according to file in the patch file bag.
The particular flow sheet of the software patch upgrading method that Fig. 3 provides for the embodiment of the invention.
Below be described in detail.
Step 301: the software patch upgrading device receives upgrade.Upgrade can be to input to the software patch upgrading device by the site operation personnel in the present embodiment.
Step 302:, obtain the file in the software that is upgraded of change file information correspondence according to change file information.Wherein, change file information can set in advance.
Wherein, change file information can make this update device obtain the program that will upgrade from the program that is upgraded software, it is configured, thereby makes and get access to change file in the service packs.In other words, " file that obtains after the configuration " is exactly " change file " in the patch file bag.
Step 303: according to change file information, file is configured in the software to being upgraded of obtaining.In the present embodiment, the file in the software of being upgraded that obtains is configured specifically and comprises: to wherein any one or several operation of the increase of file, modification, deletion.The file that obtains after the configuration is change file in the patch file bag.
For example: change file information all is revised as 5 respectively for the value of parameter A and B parameter in the program that will be upgraded software, then this update device at first will get access to the file that is upgraded software, then the parameter in the file that is upgraded software is made amendment, amended file just is the change file in the patch file bag.
Wherein, the configuration operation in the above-mentioned steps 303 can be realized (the concrete version that adopts is JDK1.5) by JAVA, can move on different platforms.By at extend markup language (Xml, ExtensibleMarkup Language) in the file configuration of the file that is upgraded software is finished that text increases, deletion, revised wherein any one or several operation, every type operation can be by row number location, the content location that also can comprise by row.The concrete operation of supporting is as shown in table 1, and wherein, the content in the row content location is supported the Java regular expression.
Table 1
Also need to prove, but above-mentioned steps 302 and step 303 are selection operations that if comprise change file in the patch file bag of storage, then the software patch upgrading device can not carried out and obtain the file that needs change, and this document is configured.
Step 304:, generate stand-by program with filename and bibliographic structure in the patch file bag; Wherein, comprise in the patch file bag: the change file that the configuration back forms in the non-change file of storage and the step 303.
With filename in the patch file and bibliographic structure, compare with filename that is upgraded file and bibliographic structure, can need not the documents content, according to the result after the contrast, generate stand-by program.In the present embodiment with filename in the patch file and bibliographic structure, with the file contrast that is upgraded software, because the patch file bag exists and is constant always, filename in the patch file bag is identical with bibliographic structure with existing filename and the bibliographic structure that is upgraded software, can comprise the complete file that is upgraded software in the stand-by program, in stand-by program, only need record to be upgraded file file and the position thereof different of software, thereby can generate stand-by program more efficiently with file in the patch file bag.(explanation of being convenient to understand is, file path in the patch file bag is identical with the path that is upgraded file, the pairing existing file that is upgraded in the software of file in generation stand-by program emphasis record and the patch file bag under the filename at change file place, non-change file in the patch file bag can be used as the file in the stand-by program, but in the patch file bag as except the file that increases newly of non-change file).For example: the filename in the patch file bag with and bibliographic structure be consistent (comprising change file and non-change file) with file in the existing software systems, so just can and duplicate the dest program of " directories/files title " under (copy) software root directory by All Files in the traversal patch file bag, automatically perform this program then, finally in the dest catalogue, can comprise all files that need back up (this stand-by program and patch file bag correspondence).
Step 305: call stand-by program, carry out backup operation.After carrying out backup operation, can generate the backup bag in the present embodiment.
Here the purpose that generates the backup bag is, how in the situation of failure of upgrading, can call this backup bag, upgrades again, so just can advance fast quick-recovery upgrading.
Step 306:, carry out updating operation according to file in the patch file bag.Wherein, updating operation can be specifically: the required change file of non-change file that the upgrading in the patch file bag in the file is required and upgrading covers the software document that is upgraded.
Explanation by the above-mentioned software patch upgrading method that the embodiment of the invention is provided, this method adopts filename and bibliographic structure in the patch file bag, compare with the file that is upgraded software, generate stand-by program, then, call this stand-by program, carry out backup operation, call the patch file bag and carry out updating operation.Make this device before carrying out updating operation, can realize to being upgraded the backup of software;
Further, because filename and bibliographic structure in the patch file bag and the file that is upgraded software are compared, generate stand-by program, can comprise the complete file that is upgraded software in the stand-by program, in stand-by program, only need record to be upgraded file file and the position thereof different of software, thereby can generate stand-by program more efficiently with file in the patch file bag.
Preferably, this method can also comprise:
Step 306: judge whether updating operation fails, if execution in step 307 if not, then can finish.
Step 307: according to filename and bibliographic structure in the patch file bag, and file in the backup bag that generates after the backup operation, generate recovery routine.
Wherein, according to filename and bibliographic structure in the patch file bag, and file in the backup bag that generates after the backup operation generates the two parts that comprise that recovery routine can order in the step 307, and a part is to generate the cleaning script, and another part is to generate to recover script.Wherein, by filename and bibliographic structure in the patch file bag, can be easy to know the particular location that is upgraded file in the software that carries out updating operation, after the updating operation failure, only need to be upgraded in the software by the local file full scale clearance of patch file coating lid.Based on this principle, this device can generate the cleaning script in the 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.
Need to prove, call recovery routine in the step 308 after, carry out recovery operation, execution that specifically can order is removed and is coated with file in the patch file bag, the backup bag rollback system with backup operation generates has realized system recovery.
By increasing above-mentioned steps 306 to step 308, this method has realized that the software patch upgrading device that makes the embodiment of the invention provide can be realized the system recovery function in the recovery of updating operation failure back system.
Need to prove that also above-mentioned steps 307 can be carried out afterwards in execution backup operation (being step 305), promptly after backup operation, generate recovery routine.If this recovery routine is directly called in the updating operation failure, carry out recovery operation and get final product.The method that makes present embodiment provide by increase step 307 can generate recovery routine.
In sum, this technical scheme does not need to develop the patch upgrading script, as long as it is just passable to finish the configuration of patch file bag and change file modification, makes the developer be not related to engineerings such as footnote basis, patch upgrading.When simplifying performance history, be that the peopleware more is absorbed in professional ability, improved efficient greatly.
Further,, make the software upgrading engineering solidify, reduced the risk in the escalation process by automatic generation stand-by program and/or recovery routine.
One of ordinary skill in the art will appreciate that all or part of flow process that realizes in the foregoing description method, be to instruct relevant hardware to finish by computer program, described program can be stored in the computer read/write memory medium, this program can comprise the flow process as the embodiment of above-mentioned each side method when carrying out.Wherein, described storage medium can be magnetic disc, CD, read-only storage memory body (Read-Only Memory, ROM) or at random store memory body (Random Access Memory, RAM) etc.
More than the embodiment of the invention is described in detail, used embodiment herein the present invention set forth, the explanation of above embodiment just is used for help understanding method and apparatus of the present invention; Simultaneously, for one of ordinary skill in the art, according to thought of the present invention, the part that all can change in specific embodiments and applications, in sum, this description should not be construed as limitation of the present invention.
Claims (11)
1. a software patch upgrading method is characterized in that, comprising:
After receiving upgrade,, generate stand-by program according to filename and bibliographic structure in the patch file bag;
Call described stand-by program, carry out backup operation;
According to file in the described patch file bag, carry out updating operation.
2. method according to claim 1 is characterized in that, and is described according to filename and bibliographic structure in the patch file bag, generates stand-by program, specifically comprises:
With filename in the patch file and bibliographic structure, compare with filename that is upgraded file and bibliographic structure, according to the result after the 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 the described patch file bag, and file in the backup bag that generates after the 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 the change file information that presets, obtain and be upgraded file in the software;
According to described change file information, file is configured in the software to being upgraded of obtaining;
Comprise the file that obtains after the described configuration in the then described patch file bag.
5. method according to claim 4 is characterized in that, and is described according to change file information, and file is configured in the software to being upgraded of obtaining, and specifically comprises:
According to change file information, file increases in the software to being upgraded of obtaining, and any one or several operation are perhaps revised wherein in deletion.
6. a software patch upgrading device is characterized in that, comprising: receiver module, program generating module and scheduler module;
Described receiver module is used to receive upgrade;
Described program generating module is used for after receiving upgrade, according to filename and bibliographic structure in the patch file bag, generates stand-by program;
Described calling module is used to call described stand-by program, carries out backup operation; According to file in the described patch file bag, carry out updating operation.
7. device according to claim 6 is characterized in that, described program generating module also is used for according to described patch file bag filename and bibliographic structure, and carries out file in the backup bag that generates after the backup operation, generates recovery routine;
Described scheduler module is used to also judge whether described updating operation fails, if, call described recovery routine, carry 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 is used for obtaining and being upgraded file in the software according to the change file information that presets;
Described configuration module is used for according to described change file information, and file is configured in the software to being upgraded of obtaining; Wherein, comprise the file that obtains after the described configuration in the described patch file bag.
9. device according to claim 8 is characterized in that, described configuration module specifically is used for according to change file information, and file increases in the software to being upgraded of obtaining, and any one or several operation are perhaps revised wherein in deletion.
10. device according to claim 6 is characterized in that, described device also comprises: memory module is used to store the patch file bag.
11. device according to claim 6 is characterized in that, described program generating module, specifically be used for patch file filename and bibliographic structure, compare with filename that is upgraded file and bibliographic structure,, generate stand-by program according to the result after the contrast.
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 true CN102193805A (en) | 2011-09-21 |
| CN102193805B 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) |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102609328A (en) * | 2012-01-29 | 2012-07-25 | 华为终端有限公司 | System difference upgrade method and device and mobile terminal |
| CN102693143A (en) * | 2012-05-22 | 2012-09-26 | 华为技术有限公司 | Method and device for installing patch |
| CN103049343A (en) * | 2011-10-14 | 2013-04-17 | 腾讯科技（深圳）有限公司 | Method and device for restoring operating system blue screen |
| CN103064715A (en) * | 2013-01-09 | 2013-04-24 | 上海大唐移动通信设备有限公司 | Remote upgrade method and system for automatic drive test systems |
| WO2014075523A1 (en) * | 2012-11-14 | 2014-05-22 | International Business Machines Corporation | Content management targeted rollback |
| CN104461612A (en) * | 2014-11-12 | 2015-03-25 | 上海华为技术有限公司 | Data processing method and device |
| CN105872778A (en) * | 2016-03-31 | 2016-08-17 | 乐视控股（北京）有限公司 | Upgrading control method and device |
| CN105868048A (en) * | 2015-12-11 | 2016-08-17 | 乐视移动智能信息技术（北京）有限公司 | Backup method and apparatus in android system upgrading and related device |
| CN106161061A (en) * | 2015-04-08 | 2016-11-23 | 华为技术有限公司 | The rollback method of business configuration and the network equipment |
| CN107861747A (en) * | 2017-06-26 | 2018-03-30 | 平安普惠企业管理有限公司 | Product renewing method, equipment and computer-readable recording medium |
| CN107908441A (en) * | 2017-12-06 | 2018-04-13 | 郑州云海信息技术有限公司 | The upgrade method and update device of a kind of database |
| CN108664255A (en) * | 2017-03-27 | 2018-10-16 | 中兴通讯股份有限公司 | A kind of method for upgrading software and device |
| CN111562934A (en) * | 2020-04-03 | 2020-08-21 | 深圳震有科技股份有限公司 | Software system upgrading method based on hot patch, terminal and storage medium |
| CN112579139A (en) * | 2020-12-09 | 2021-03-30 | 北京红山信息科技研究院有限公司 | Multi-cluster patch updating method, system, server and storage medium |
| CN112732292A (en) * | 2020-12-30 | 2021-04-30 | 北京浪潮数据技术有限公司 | Method, system, equipment and readable storage medium for software upgrading |
| 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 |
Cited By (25)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103049343A (en) * | 2011-10-14 | 2013-04-17 | 腾讯科技（深圳）有限公司 | Method and device for restoring operating system blue screen |
| CN102609328A (en) * | 2012-01-29 | 2012-07-25 | 华为终端有限公司 | System difference upgrade method and device and mobile terminal |
| US9804933B2 (en) | 2012-01-29 | 2017-10-31 | Huawei Device Co., Ltd. | System differential upgrade method, apparatus, and mobile terminal |
| WO2013110233A1 (en) * | 2012-01-29 | 2013-08-01 | 华为终端有限公司 | Method and device for system differential upgrade and mobile terminal |
| CN102693143B (en) * | 2012-05-22 | 2015-03-11 | 华为技术有限公司 | Method and device for installing patch |
| CN102693143A (en) * | 2012-05-22 | 2012-09-26 | 华为技术有限公司 | Method and device for installing patch |
| WO2014075523A1 (en) * | 2012-11-14 | 2014-05-22 | 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 |
| CN104461612A (en) * | 2014-11-12 | 2015-03-25 | 上海华为技术有限公司 | Data processing method and device |
| CN104461612B (en) * | 2014-11-12 | 2018-05-04 | 上海华为技术有限公司 | A kind of data processing method and device |
| CN106161061A (en) * | 2015-04-08 | 2016-11-23 | 华为技术有限公司 | The rollback method of business configuration and the network equipment |
| 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 |
| CN108664255A (en) * | 2017-03-27 | 2018-10-16 | 中兴通讯股份有限公司 | A kind of method for upgrading software 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 |
| CN107908441A (en) * | 2017-12-06 | 2018-04-13 | 郑州云海信息技术有限公司 | The upgrade method and update device of a kind of database |
| CN111562934A (en) * | 2020-04-03 | 2020-08-21 | 深圳震有科技股份有限公司 | Software system upgrading method based on hot patch, terminal and storage medium |
| CN111562934B (en) * | 2020-04-03 | 2023-08-11 | 深圳震有科技股份有限公司 | Software system upgrading method based on hot patch, terminal and storage medium |
| CN112579139A (en) * | 2020-12-09 | 2021-03-30 | 北京红山信息科技研究院有限公司 | Multi-cluster patch updating method, system, server and storage medium |
| CN112732292A (en) * | 2020-12-30 | 2021-04-30 | 北京浪潮数据技术有限公司 | Method, system, equipment and readable storage medium for software upgrading |
| 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102193805B (en) | 2014-05-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102193805B (en) | Device and method for upgrading software patches | |
| US10592229B1 (en) | Method and system for restoring software | |
| CN102609328B (en) | System difference upgrade method and device and mobile terminal | |
| US8819670B2 (en) | Automated software installation with interview | |
| US7802247B1 (en) | Method and system for restoring software | |
| US9442708B1 (en) | System and method for installing, updating and uninstalling applications | |
| CN104866391B (en) | A kind of end message backup method and device based on increment information system | |
| CN106648724B (en) | Application program hot repair method and terminal | |
| EP2805233B1 (en) | Installation engine and package format for parallelizable, reliable installations | |
| EP1609056A2 (en) | System and method for single transparent deployment flow | |
| CN106569863B (en) | Resource and code modularization-based android app resource updating and repairing method | |
| CN109634638B (en) | Cluster software upgrading method, device, equipment and medium | |
| CN100373861C (en) | Software upgrade device in communication network management system and method thereof | |
| CN104111843A (en) | Sandbox based script updating method and system | |
| CN104331311B (en) | A kind of AKU generation method and device | |
| CN102932476A (en) | Network storage synchronization system | |
| CN105700900A (en) | Method and device for optimizing wireless local area network function | |
| CN116028084A (en) | Cross-version hot upgrading method, system and terminal based on OpenStack cloud platform | |
| CN105630783A (en) | Database data migration system | |
| CN115145596A (en) | OTA (over the air) upgrading method and device for robot upgrading package | |
| Cisco | Using the Configuration Save and Restore Feature | |
| CN102110212B (en) | Method and device for realizing patch amendment | |
| CN105653300B (en) | Name-oriented application system upgrading system and method | |
| CN111625256A (en) | Application program upgrading method, system, equipment and computer storage medium | |
| CN106815004A (en) | A kind of method of compatibility difference Cocos2d-x versions |
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 |