WO2016037314A1 - Procédé, appareil et dispositif de mise à niveau de version de logiciel - Google Patents

Procédé, appareil et dispositif de mise à niveau de version de logiciel Download PDF

Info

Publication number
WO2016037314A1
WO2016037314A1 PCT/CN2014/086133 CN2014086133W WO2016037314A1 WO 2016037314 A1 WO2016037314 A1 WO 2016037314A1 CN 2014086133 W CN2014086133 W CN 2014086133W WO 2016037314 A1 WO2016037314 A1 WO 2016037314A1
Authority
WO
WIPO (PCT)
Prior art keywords
file
software version
link address
patch
running
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.)
Ceased
Application number
PCT/CN2014/086133
Other languages
English (en)
Chinese (zh)
Inventor
朱湘毅
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to PCT/CN2014/086133 priority Critical patent/WO2016037314A1/fr
Priority to CN201480049719.2A priority patent/CN105594184B/zh
Publication of WO2016037314A1 publication Critical patent/WO2016037314A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a software version upgrade method, apparatus, and device.
  • the software version developer will release a patch file for the software version after the software version is released.
  • the client that installed the software version can download the patch file and use the patch file to upgrade the software version to fix the vulnerability in the software version or optimize the software version.
  • the application provides a software version upgrade method, device and device for reducing the impact on the service during the software version upgrade process.
  • a software version upgrade method including:
  • the process of triggering the running of the software version is executed, and the corresponding file linked by the link address of each file is run according to the link address of each file.
  • the process of triggering running the software version, after running the corresponding file of the link address link of each file according to the link address of each file also includes:
  • the process is triggered to run the file in the software version.
  • the method before the determining the patch file package for the software version, the method further includes:
  • a configuration file is further included in the patch file package, The configuration file is used to indicate the process running the patch file.
  • the process of triggering the running of the software version, according to the link address of each file, running the corresponding file of the link address link of each file includes:
  • the process of running the patch file indicated by the configuration file is triggered, and corresponding files of the link address links of the respective files are run according to the link address of the respective files.
  • the triggering the process of running the software version, according to the The link address of each file, the corresponding file of the link address link running the respective file includes:
  • the plug-in process is triggered to uninstall a plug-in that runs a file in the software version, and loads a plug-in that runs the file linked by the link address.
  • a software version upgrade apparatus including:
  • a first file determining module configured to determine a patch file package for the software version
  • a second file determining module configured to determine, according to the patch file in the patch file package, a file that is not required to be updated in the software version
  • An address determining module configured to determine a link address of each file included in an upgraded version of the software version, where a link address of each file includes a link address of the patch file and a link address of the file that does not need to be updated ;
  • An upgrade module configured to trigger a process of running the software version, according to a link of each file Address, the corresponding file that runs the link address link for each file.
  • the method further includes:
  • the rollback module is configured to trigger the process to run the file in the software version when the patch back command is detected.
  • the method further includes:
  • a patch installation module for downloading and installing the patch file.
  • the upgrading module is specifically configured to:
  • the process of running the patch file indicated by the configuration file is triggered, and corresponding files of the link address links of the respective files are run according to the link address of the respective files.
  • the upgrading module is specifically configured to:
  • the plug-in process is triggered to uninstall a plug-in that runs a file in the software version, and loads a plug-in that runs the file linked by the link address.
  • a software version upgrade device including a processor and a memory.
  • the memory user stores a set of program instructions
  • the processor is configured to invoke the program instruction of the memory, and perform the following operations:
  • the process of triggering the running of the software version is executed, and the corresponding file linked by the link address of each file is run according to the link address of each file.
  • the file that is not required to be updated in the software version is determined according to the patch file in the patch file package, and the link address of the file that is not to be updated and the patch file in the patch file package are determined.
  • Link address determine the link address of each file to be included in the upgrade version after the software version is upgraded, and then trigger the process running the software version, run the The corresponding file of the link address of each file, because the file linked by the link address includes the patch file and the file that is not required to be updated in the software version, the purpose of running the upgrade version file by the process is realized, thereby realizing the software version upgrade.
  • the process only needs to switch to the file corresponding to the running link address, without stopping for a long time, so the impact on the business can be reduced.
  • FIG. 1 is a schematic flowchart of a method for upgrading a software version according to an embodiment of the present disclosure
  • FIG. 2 is a schematic diagram of a directory of multiple files included in a software version V1.0.1.0.0 provided by an embodiment of the present application;
  • FIG. 3 is a schematic diagram of a directory of a patch file in a patch file package for software version V1.0.1.0.0 according to an embodiment of the present application;
  • FIG. 4 is a schematic diagram of a link relationship between a software version and an upgrade version according to an embodiment of the present application
  • FIG. 5 is a schematic structural diagram of an apparatus for upgrading a software version according to an embodiment of the present disclosure
  • FIG. 6 is a schematic structural diagram of an embodiment of a software version upgrading device according to an embodiment of the present disclosure.
  • FIG. 1 a flow chart of an embodiment of a software version upgrade method of the present application is shown.
  • the method of this embodiment may include:
  • the patch file in the patch file package may be a file that needs to be added to the software version, that is, a file included in the patch file package and not included in the software version; or a file that is updated in the software version, that is, the file
  • the software version and the patch file contain the same file name, but the data content contained in the file is different.
  • the link address of each file includes a link address of the patch file in the patch file package and a link address of the file that is not required to be updated in the software version.
  • the link address may specifically refer to location information of each file and the like.
  • the link addresses of the individual files that make up the upgrade version can be determined.
  • the process that originally runs the file in the software version triggers the corresponding file running the link of the link address.
  • the file linked by the link address includes the patch file (including the software version that needs to be updated).
  • the patch file corresponding to the file) and the file that is not required to be updated in the software version thus realizing the purpose of running the upgrade version file for the process, thereby implementing the software version upgrade.
  • the process only needs to switch to the file corresponding to the running link address. There is no need to stop for a long time, so the impact on the business corresponding to the process can be reduced. It also eliminates the need for complicated operations such as backing up files and overwriting files, saving upgrade time and improving upgrade efficiency.
  • a process may not need to run all the files in the software version, so you can run the corresponding file of the link address of each file according to your needs.
  • an upgrade command can be sent directly to the process running the file in the software version.
  • the process running the file in the software version responds to the upgrade instruction, and the corresponding file linked by the link address of each file may be run according to the link address of each file. That is, the implementation process is switched from the file that needs to be updated in the software version to the patch file in the patch file package, so that the files that need to be updated in the software version are upgraded to the patch file in the patch file package.
  • the method further includes:
  • the process is triggered to run the file in the software version.
  • the patch rollback command may be generated when the patch file is abnormally detected.
  • the patch file package and the software version are two separate software packages, and the link address of each file in the determined upgrade version is actually established in the patch file package and the software version does not need to be updated.
  • the link relationship of the files is two separate software packages, and the link address of each file in the determined upgrade version is actually established in the patch file package and the software version does not need to be updated. The link relationship of the files.
  • the file that is not required to be updated in the software version and the patch file in the patch file package may be first determined as a file included in the upgrade version after the software version is upgraded, and then the link address of the file that does not need to be updated is determined.
  • the link address of the patch file in the patch package which will not need to be updated.
  • the link address of the file and the link address of the patch file are combined to obtain the link address of each file in the upgraded version.
  • the software version contains the program file software, including: file1 to filen.
  • the software version also includes a plurality of data files date generated in the running software version, specifically including date1 to schemes, where n is a natural number greater than 1.
  • n is a natural number greater than 1.
  • FIG. 2 it is a directory diagram of files included in the software version V1.0.1.0.0.
  • the patch file for the software version V1.0.1.0.0 includes the patch files file3 and fileX, wherein the patch file file3 is an update file of the file file3 included in the software version V1.0.1.0.0, and the fileX is new. program files.
  • FIG. 3 a directory diagram of a patch file in a patch file package is shown, that is, the patch file package includes a patch file file3 and a patch file fileX.
  • the software version and the link address of each file in the patch file package are determined, and the link address of the file and the patch file of the software version that are not required to be updated are determined.
  • FIG. 4 it is a schematic diagram of the relationship between the files that need not be updated in the software version and the patch files in the patch file package. It can be seen that the files in the upgraded version include the patch file and the files that need to be updated in the linked software version.
  • the file in the software version of the process may not need to be updated.
  • the process can run the file in the software version without running the corresponding file linked by the link address.
  • the corresponding file of the link may specifically be a process of running a file that needs to be updated in the software version, and according to the link address of the respective file, running a corresponding file linked by the link address of each file.
  • the process that needs to run the upgraded version can be the process that runs the file that needs to be updated in the software version.
  • the process can continue to run the software version of the file.
  • the patch file package may further include a configuration file, where the configuration file includes process information for indicating each patch file in the patch file package.
  • the patch file includes the patch files file3 and fileX.
  • the configuration file it can be indicated that the patch file file3 is run by the process A of the file3 running the original software version, and the fileX is run by the process B.
  • the process of triggering the running of the software version, according to the link address of each file, running the corresponding file of the link address link of each file includes:
  • the process of running the patch file indicated by the configuration file is triggered, and corresponding files of the link address links of the respective files are run according to the link address of the respective files.
  • the process running the files in the software version is a normal process
  • the normal process may be triggered to terminate the operation, and at the same time The normal process is restarted in the corresponding file of the link address of each file.
  • the plug-in process is composed of multiple plug-ins or modules, each plug-in can be started, stopped, uninstalled, installed, etc. independently. Therefore, a plugin of the plugin process is upgraded and patched, which only affects the plugin. It is therefore possible to determine whether or not to insert the upgrade for the files in the software version inserted into the run.
  • FIG. 5 is a schematic structural diagram of an apparatus for upgrading a software version according to an embodiment of the present disclosure, where the apparatus may include:
  • the first file determining module 501 is configured to determine a patch file package for the software version.
  • the second file determining module 502 is configured to determine, according to the patch file in the patch file package, a file that is not required to be updated in the software version.
  • the patch file in the patch file package may be a file that needs to be added to the software version, that is, a file included in the patch file package and not included in the software version; or a file that is updated in the software version, that is, the file
  • the software version and the patch file contain the same file name, but the data content contained in the file is different.
  • the address determining module 503 is configured to determine a link address of each file included in the upgraded version of the software version.
  • the link address of each file includes a link address of the patch file and a link address of the file that does not need to be updated.
  • the link address may specifically refer to location information of each file and the like.
  • the patch file and the files in the software version it can be determined that the software version is upgraded after the upgrade.
  • the files included in the level version it can be determined that the software version is upgraded after the upgrade.
  • the link addresses of the individual files that make up the upgrade version can be determined.
  • the upgrading module 501 is configured to trigger a process of running the software version, and run a corresponding file linked by the link address of each file according to the link address of each file.
  • the process that originally runs the file in the software version triggers the corresponding file running the link of the link address.
  • the file linked by the link address includes the patch file (including the software version that needs to be updated).
  • the patch file corresponding to the file) and the file that is not required to be updated in the software version thus realizing the purpose of running the upgrade version file for the process, thereby implementing the software version upgrade.
  • the process only needs to switch to the file corresponding to the running link address, without stopping for a long time, so the impact on the business can be reduced. It also eliminates the need for complicated operations such as backing up files and overwriting files, saving upgrade time and improving upgrade efficiency.
  • a process may not need to run all the files in the software version, so you can run the corresponding file of the link address of each file according to your needs.
  • the original software version is not covered by the patch file, so that the original software version is still completely stored in the device, so that when the patch file package is abnormal, , you can directly switch the process back to the file in the running software version. Therefore, there is no need to back up files, and there is no need to interrupt the service when the patch is rolled back.
  • the device may further include:
  • the rollback module is configured to trigger the process to run the file in the software version when the patch back command is detected.
  • the patch rollback command may be generated when the patch file is abnormally detected.
  • the device may further comprise:
  • a patch installation module for downloading and installing the patch file.
  • the patch file package and the software version are two separate software packages, and the link address of each file in the determined upgrade version is actually established in the patch file package and the software version does not need to be updated.
  • the link relationship of the files is two separate software packages, and the link address of each file in the determined upgrade version is actually established in the patch file package and the software version does not need to be updated. The link relationship of the files.
  • the file in the software version of the process may not need to be updated.
  • the process can run the file in the software version without running the corresponding file linked by the link address.
  • the upgrade module when it is determined that there is a file that needs to be updated in the software version according to the patch file, the upgrade module may be specifically a process of running a file that needs to be updated in the software version, according to the The link address, the corresponding file that runs the link address link of each file.
  • the process that needs to run the upgraded version can be the process that runs the file that needs to be updated in the software version.
  • the process can continue to run the software version of the file.
  • the patch file package may further include a configuration file, where the configuration file includes process information for indicating each patch file in the patch file package. Therefore, the upgrade module can be specifically used for:
  • the process of running the patch file indicated by the configuration file is triggered, and corresponding files of the link address links of the respective files are run according to the link address of the respective files.
  • the upgrade module may trigger the normal process to terminate the operation, and restart the corresponding file in the corresponding file of the link address of the respective file.
  • the upgrade module may be the plug-in process uninstalling the plug-in that runs the file in the software version, and reloading the link address link running the respective file.
  • the plugin for the corresponding file may be the plug-in process uninstalling the plug-in that runs the file in the software version, and reloading the link address link running the respective file.
  • the plug-in process is composed of multiple plug-ins or modules, each plug-in can be started independently, Stop, uninstall, install, etc. Therefore, a plugin of the plugin process is upgraded and patched, which only affects the plugin. It is therefore possible to determine whether or not to insert the upgrade for the files in the software version inserted into the run.
  • the software version upgrade device described in the foregoing embodiment may be integrated into the software version upgrade device, and the software version upgrade device may be a network element device with a software version upgrade requirement.
  • the software version of the software version upgrade device of the embodiment of the present application is upgraded, and the process does not need to be stopped for a long time. Therefore, the service interruption time of the process can be detected, and the impact on the service is reduced. It also eliminates the need for complicated operations such as backing up files and overwriting files, saving upgrade time and improving upgrade efficiency.
  • the embodiment of the present application further provides a software version upgrading device, where the software version upgrading device includes at least a processor 601 and a memory 602.
  • the memory 602 stores a set of program instructions, which may be a high speed RAM memory or a non-volatile memory such as at least one disk memory or the like.
  • the processor 601 is configured to invoke the program instructions stored in the memory 602, and perform the following operations:
  • the process of triggering the running of the software version is executed, and the corresponding file linked by the link address of each file is run according to the link address of each file.
  • the processor may be a central processing unit CPU, or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention.
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • the software version upgrade device may be used to perform the example provided in the embodiment of the present application.
  • the steps of a method or algorithm described in connection with the embodiments disclosed herein can be implemented directly in hardware, a software module executed by a processor, or a combination of both.
  • the software module can be placed in random access memory (RAM), memory, read only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or technical field. Any other form of storage medium known.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

La présente invention concerne un procédé et un appareil de mise à niveau de version de logiciel. Le procédé comprend les étapes suivantes : la détermination d'un ensemble fichier de correction destiné à une version de logiciel ; selon un ensemble fichier de correction dans l'ensemble fichier de correction, la détermination d'un fichier qui n'a pas besoin d'être mis à niveau dans la version de logiciel ; la détermination des adresses de liens des divers fichiers contenus dans une version de mise à niveau de la version de logiciel, les adresses des liens des divers fichiers comprenant une adresse de lien du fichier de correction et une adresse de lien du fichier qui n'a pas besoin d'être mis à niveau ; et le déclenchement d'un procédé destiné à la mise en œuvre de la version de logiciel et la mise en œuvre des fichiers correspondants liés aux adresses de liens des divers fichiers selon les adresses de liens des divers fichiers. Les modes de réalisation de la présente invention réduisent l'influence sur les services lorsqu'une version de logiciel est mise à niveau.
PCT/CN2014/086133 2014-09-09 2014-09-09 Procédé, appareil et dispositif de mise à niveau de version de logiciel Ceased WO2016037314A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2014/086133 WO2016037314A1 (fr) 2014-09-09 2014-09-09 Procédé, appareil et dispositif de mise à niveau de version de logiciel
CN201480049719.2A CN105594184B (zh) 2014-09-09 2014-09-09 软件版本升级方法、装置及设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2014/086133 WO2016037314A1 (fr) 2014-09-09 2014-09-09 Procédé, appareil et dispositif de mise à niveau de version de logiciel

Publications (1)

Publication Number Publication Date
WO2016037314A1 true WO2016037314A1 (fr) 2016-03-17

Family

ID=55458239

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/086133 Ceased WO2016037314A1 (fr) 2014-09-09 2014-09-09 Procédé, appareil et dispositif de mise à niveau de version de logiciel

Country Status (2)

Country Link
CN (1) CN105594184B (fr)
WO (1) WO2016037314A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109976794A (zh) * 2019-03-31 2019-07-05 联想(北京)有限公司 更新方法、更新系统以及电子设备
CN112073994A (zh) * 2020-09-03 2020-12-11 百度在线网络技术（北京）有限公司 用于空中升级的方法、装置、电子设备及可读存储介质
CN114003257A (zh) * 2021-10-29 2022-02-01 联想(北京)信息技术有限公司 一种升级方法及装置

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117931242B (zh) * 2024-02-02 2024-12-10 山东中创软件商用中间件股份有限公司 负载均衡软件补丁升级及回滚方法、装置、设备及介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009081502A1 (fr) * 2007-12-26 2009-07-02 Fujitsu Limited Terminal de communication
CN102724308A (zh) * 2012-06-13 2012-10-10 腾讯科技（深圳）有限公司 软件更新方法及软件更新系统
CN103631629A (zh) * 2013-12-17 2014-03-12 江苏名通信息科技有限公司 获取远程更新文件自动更新方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1107907C (zh) * 2000-02-21 2003-05-07 英业达股份有限公司 借由增量的方式来使数据文件升级的方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009081502A1 (fr) * 2007-12-26 2009-07-02 Fujitsu Limited Terminal de communication
CN102724308A (zh) * 2012-06-13 2012-10-10 腾讯科技（深圳）有限公司 软件更新方法及软件更新系统
CN103631629A (zh) * 2013-12-17 2014-03-12 江苏名通信息科技有限公司 获取远程更新文件自动更新方法

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109976794A (zh) * 2019-03-31 2019-07-05 联想(北京)有限公司 更新方法、更新系统以及电子设备
CN112073994A (zh) * 2020-09-03 2020-12-11 百度在线网络技术（北京）有限公司 用于空中升级的方法、装置、电子设备及可读存储介质
CN114003257A (zh) * 2021-10-29 2022-02-01 联想(北京)信息技术有限公司 一种升级方法及装置

Also Published As

Publication number Publication date
CN105594184B (zh) 2019-05-24
CN105594184A (zh) 2016-05-18

Similar Documents

Publication Publication Date Title
US9552201B2 (en) System and method for incremental software installation
CN105637479B (zh) 修改计算机程序的方法、计算机系统和计算机可读介质
JP5444368B2 (ja) アプリケーション復元ポイント
US7937697B2 (en) Method, system and computer program for distributing software patches
US7703090B2 (en) Patch un-installation
CN104918114B (zh) 一种操作系统升级方法及装置
CN103745158A (zh) 修复系统漏洞的方法和装置
WO2013078951A1 (fr) Procédé et système de mise à niveau de logiciel
WO2012116637A1 (fr) Procédé et dispositif de restauration de système
CN107506221A (zh) 应用程序升级方法、装置及设备
CN107783776B (zh) 固件升级包的处理方法及装置、电子设备
US7627866B2 (en) Systems and methods for dynamic application patching
US20160328227A1 (en) Dynamically Applying A Software Patch To A Computer Program
US20160162278A1 (en) System and method for applying an update to a device system via a system snapshot
CN109634638B (zh) 一种集群软件升级方法、装置、设备及介质
CN103353846A (zh) 一种项目自动部署插件
US8132047B2 (en) Restoring application upgrades using an application restore point
WO2020029967A1 (fr) Procédé et appareil de réparation de défaut dans un système d'exploitation
WO2016037314A1 (fr) Procédé, appareil et dispositif de mise à niveau de version de logiciel
CN102880478B (zh) 软件更新方法
US8453141B1 (en) High performance install update
US20060085685A1 (en) System and method for computer system rejuvenation
TWI514279B (zh) 伺服器系統與韌體更新方法
CN111258681B (zh) 一种BeeGFS服务启动方法和装置
CN107391216A (zh) 一种软件升级方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14901765

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14901765

Country of ref document: EP

Kind code of ref document: A1