WO2016037314A1

WO2016037314A1 - Software version upgrade method, apparatus and device

Info

Publication number: WO2016037314A1
Application number: PCT/CN2014/086133
Authority: WO
Inventors: 朱湘毅
Original assignee: 华为技术有限公司
Priority date: 2014-09-09
Filing date: 2014-09-09
Publication date: 2016-03-17
Also published as: CN105594184B; CN105594184A

Abstract

Provided are a software version upgrade method and apparatus. The method comprises: determining a patch file package for a software version; according to a patch file in the patch file package, determining a file which does not need to be updated in the software version; determining link addresses of various files contained in an upgrade version of the software version, wherein the link addresses of the various files comprise a link address of the patch file and a link address of the file which does not need to be updated; and triggering a process for operating the software version, and operating corresponding files linked with the link addresses of the various files according to the link addresses of the various files. The embodiments of the present application reduce the influence on services when a software version is upgraded.

Description

Software version upgrade method, device and device

Technical field

The present application relates to the field of communications technologies, and in particular, to a software version upgrade method, apparatus, and device.

Background technique

In order to improve the software version, 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.

In the prior art, in the process of upgrading the software version by using the patch file, first, the file to be modified that needs to be updated in the software version is determined, and the file to be modified is backed up; then, the process of stopping the file to be modified is stopped. , use the patch file to overwrite the file to be modified; after that, restart the process.

It can be seen that in the process of upgrading the software version, the process needs to be stopped first, so that the process running the software version needs to be interrupted for a period of time, which may affect the operation of the service corresponding to the process.

Summary of the invention

The application provides a software version upgrade method, device and device for reducing the impact on the service during the software version upgrade process.

In a first aspect, a software version upgrade method is provided, including:

Determining a patch file package for the software version;

Determining files that are not required to be updated in the software version according to the patch file in the patch file package;

Determining a link address of each file included in the upgraded version of the software version, where 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 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.

In a first possible implementation manner of the first aspect, 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, The method also includes:

When the patch fallback command is detected, the process is triggered to run the file in the software version.

In a second possible implementation manner of the first aspect, before the determining the patch file package for the software version, the method further includes:

Download and install the patch file.

With reference to the first aspect or any one of the foregoing possible implementation manners of the first aspect, in a third possible implementation manner of the first aspect, 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.

With reference to the first aspect or any one of the foregoing possible implementation manners of the first aspect, in a fourth possible implementation manner of the first aspect, 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:

When the process running the software version is a plug-in process, 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.

In a second aspect, a software version upgrade apparatus is provided, 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.

In the first possible implementation manner of the second aspect, 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.

In a second possible implementation manner of the second aspect, the method further includes:

A patch installation module for downloading and installing the patch file.

With reference to the second aspect or any one of the foregoing possible implementation manners of the second aspect, in the third possible implementation manner of the second aspect, the upgrading module is specifically configured to:

With reference to the second aspect, or any one of the foregoing possible implementation manners of the second aspect, in the fourth possible implementation manner of the second aspect, the upgrading module is specifically configured to:

In a third aspect, a software version upgrade device is provided, 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:

Determining a patch file package for the software version;

According to the foregoing technical solution, after the patch file package is determined, 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.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present application. Other drawings may also be obtained from those of ordinary skill in the art in light of the inventive work.

FIG. 1 is a schematic flowchart of a method for upgrading a software version according to an embodiment of the present disclosure;

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;

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;

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.

detailed description

The technical solutions in the embodiments of the present application are clearly and completely described in the following with reference to the drawings in the embodiments of the present application. It is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.

Referring to 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:

101. Determine a patch file package for the software version.

When you need to update the software version in the NE device, you can use the patch file in the patch file package in the NE device to upgrade the software version after downloading and installing the patch file package.

102. 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.

By comparing the patch file in the patch package with the files included in the software version, files that do not need to be updated in the software version and/or files that need to be updated can be determined.

103. 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 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.

Based on the patch file and the files in the software version, you can determine the files included in the upgraded version after the software version is upgraded.

Due to the location of the files in the software version and the location of the patch files in the patch package, the link addresses of the individual files that make up the upgrade version can be determined.

104. Trigger a process of running the software version, and running a corresponding file linked by a link address of each file according to a link address of each file.

In this embodiment of the present application, it is not necessary to use the patch file to update the software version of the file, and it is not necessary to back up the files in the software version. Just determine the link address of each file in the upgraded version, and 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.

When upgrading with a patch file, 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.

It can be understood that, in the process of upgrading the software version in the embodiment of the present application, 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 the patch is When an exception occurs in a package, 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 process when the patch is rolled back.

Therefore, in the embodiment of the present application, after the process of triggering the running of the software version is performed, according to the link address of each file, after running the corresponding file linked to the link address of each file, the method further includes:

The patch rollback command may be generated when the patch file is abnormally detected.

It can be understood that in the actual application, it is necessary to download the patch file package and install it before determining the patch file for the software version.

After the patch file package is installed, 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.

Optionally, 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 following is an introduction to an example. Assume that the NE device is currently installed and running as software version V1.01.0.0. You need to upgrade the software version to the upgrade version V1.01.0.1 by using the patch file in the patch file package. It can be understood that the program file that can be run and the data file generated during the process of running the program file are included. The data files will not change during the software version upgrade, and the program files may be updated.

Assume that the software version contains the program file software, including: file1 to filen. At the same time, the software version also includes a plurality of data files date generated in the running software version, specifically including date1 to daten, where n is a natural number greater than 1. As shown in FIG. 2, it is a directory diagram of files included in the software version V1.0.1.0.0.

Assume that 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. As shown in 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.

Comparing the file directories of Figure 2 and Figure 3, it can be seen that the original software version V1.0.1.0.0 does not need to be updated except for the program file file3 that needs to be updated. According to the file directory included in the software version V1.0.1.0.0 and the patch file directory included in the patch file package, it can be determined that the software version V1.0.1.0.0 is upgraded by using the patch file package, and the upgrade version includes The file includes files that need not be updated in the software version V1.0.1.0.0, that is, the program files file1, file2, file4 to filen, and all the data files in the software version V1.0.1.0.0; Including: patch file file3 and new file filex in the patch package. After the software version and the patch file package are installed in the network element device, 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. By combining the link addresses, you can get the link address of each file included in the upgraded version. As shown in 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.

It can also be seen from the above process that in the process of upgrading the software version, the application does not need to use the patch file to overwrite the file that needs to be updated in the software version, that is, it is not necessary to construct a complete upgrade version, so that the original software version is obtained. Reserved, in the case of an exception in the patch file package, you do not need to rebuild the version before the upgrade, you can directly switch the process to the file in the original software version.

The file in the software version of the process may not need to be updated. In this case, the process can run the file in the software version without running the corresponding file linked by the link address.

There are several ways to implement the determination of a process that needs to run an upgraded version.

In a possible implementation manner, when it is determined that there is a file that needs to be updated in the software version according to the patch file, triggering a process of running the software version, and running a link address of each file according to a link address of each file 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.

That is, 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.

If the files in the software version running by the process do not need to be updated, the process can continue to run the software version of the file.

Of course, as another possible implementation manner, 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. For example, the patch file includes the patch files file3 and fileX. In 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.

Therefore, 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:

In any of the above embodiments, when the process running the files in the software version is a normal process At the time of triggering the process of running the software version, according to the link address of each file, when the corresponding file of the link address link of each file is run, 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.

When the process of running the file in the software version is an insertion process, when the process running the software version is triggered, according to the link address of each file, when the corresponding file of the link address of each file is run, It is the plugin process that uninstalls the plugin that runs the files in the software version and reloads the plugin that runs the corresponding file of the link address link of the respective file.

Among them, 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 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.

According to 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.

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.

In this embodiment of the present application, it is not necessary to use the patch file to update the software version of the file, and it is not necessary to back up the files in the software version. Just determine the link address of each file in the upgraded version, and 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.

In the process of upgrading the software version in the embodiment of the present application, 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.

Therefore, in this embodiment of the present application, the device may further include:

In practical applications, it is necessary to download the patch package and install it before determining the patch file for the software version. Therefore, the device may further comprise:

A patch installation module for downloading and installing the patch file.

In a possible implementation, 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.

Of course, as another possible implementation manner, 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:

In the above description, when the process of running the file in the software version is a normal process, 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. General process.

When the process of running the file in the software version is an insertion process, 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.

Among them, 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.

From the above description, those skilled in the art can clearly understand that the present application can be implemented by means of software plus a necessary general hardware platform. Therefore, referring to FIG. 6, 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:

Determining a patch file package for the software version;

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.

Optionally, the software version upgrade device may be used to perform the example provided in the embodiment of the present application. The software version upgrade method shown.

The various embodiments in the present specification are described in a progressive manner, and each embodiment focuses on differences from other embodiments, and the same similar parts between the various embodiments may be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.

A person skilled in the art will further appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware, computer software or a combination of both, in order to clearly illustrate the hardware and software. Interchangeability, the composition and steps of the various examples have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope 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.

The above description of the disclosed embodiments enables those skilled in the art to make or use the application. Various modifications to these embodiments are obvious to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the application. Therefore, the application is not limited to the embodiments shown herein, but is to be accorded the broadest scope of the principles and novel features disclosed herein.

Claims

A software version upgrade method, which is characterized by comprising:

Determining a patch file package for the software version;

Determining files that are not required to be updated in the software version according to the patch file in the patch file package;

Determining a link address of each file included in the upgraded version of the software version, where 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 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 method according to claim 1, wherein the triggering the process of 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, the method Also includes:

When the patch fallback command is detected, the process is triggered to run the file in the software version.
The method according to claim 1, wherein before the determining the patch file package for the software version, the method further comprises:

Download and install the patch file.
The method according to any one of claims 1 to 3, further comprising a configuration file in the patch file package, where the configuration file is used to indicate a process of running a 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 method according to any one of claims 1 to 3, wherein the triggering the process of running the software version, according to the link address of each file, running a corresponding file of a link address link of each file include:

When the process running the software version is a plug-in process, 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 upgrading device, comprising:

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 ;

And an upgrade module, 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 device according to claim 6, further comprising:

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 device according to claim 6, further comprising:

A patch installation module for downloading and installing the patch file.
The device according to any one of claims 6 to 8, wherein the upgrade 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 device according to any one of claims 6 to 8, wherein the upgrade module is specifically configured to:

When the process running the software version is a plug-in process, 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 upgrading device, comprising: 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:

Determining a patch file package for the software version;

Determining files that are not required to be updated in the software version according to the patch file in the patch file package;

Determining a link address of each file included in the upgraded version of the software version, wherein the link address of each file includes a link address of the patch file and the file that does not need to be updated Link address

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.