WO2018177193A1

WO2018177193A1 - Software upgrade method and device

Info

Publication number: WO2018177193A1
Application number: PCT/CN2018/080043
Authority: WO
Inventors: 冯浩展
Original assignee: 中兴通讯股份有限公司
Priority date: 2017-03-27
Filing date: 2018-03-22
Publication date: 2018-10-04
Also published as: CN108664255A; CN108664255B

Abstract

Provided are a software upgrade method and a device. The method comprises: upon receipt of upgrade instruction, determining a change file corresponding to a patch according to a file in the patch and a file in a target software; establishing a backup file model of the patch according to the change file corresponding to the patch, wherein the backup file model is a tree structure generated according to a directory hierarchy of the change file corresponding to the patch; performing file backup according to a node corresponding to the change file in the backup file model, so as to obtain a backup file; and performing an upgrade operation on the basis of the patch.

Description

Software upgrade method and device

Technical field

This document relates to, but is not limited to, the field of computer technology, and in particular, to a software upgrade method and apparatus.

Background technique

After the software version is released, in order to fix bugs or add new features, it is often upgraded in the form of a patch set. The patch set of the software generally includes multiple patches. When the patch set is upgraded, the patches are first patched one by one. If the software version is not backed up before the patch set is upgraded, once a patch upgrade has a problem, the software can only be reinstalled, so the backup of the version of the patch set is very important.

Summary of the invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

An embodiment of the present invention provides a software upgrade method, where the method includes:

When receiving the upgrade instruction, determining the change file corresponding to the patch according to the file in the patch and the file in the target software;

Establishing a backup file model of the patch according to the change file corresponding to the patch, where the backup file model is a tree structure generated according to a directory hierarchy of the change file corresponding to the patch;

Performing a file backup according to the node corresponding to the change file in the backup file model, and obtaining a backup file;

Perform an upgrade operation based on the patch.

The embodiment of the invention further provides a software upgrading device, the device comprising:

Determining a module, configured to: when receiving an upgrade instruction, determine a change file corresponding to the patch according to the file in the patch and the file in the target software;

Establishing a module, configured to establish a backup file model of the patch according to the change file corresponding to the patch, where the backup file model is a tree structure generated according to a directory hierarchy of the change file corresponding to the patch;

The first backup module is configured to perform file backup according to the node corresponding to the change file in the backup file model, to obtain a backup file;

The upgrade module is configured to perform an upgrade operation based on the patch.

The embodiment of the present invention further provides a computer storage medium, where the computer storage medium stores one or more programs executable by a computer, and when the one or more programs are executed by the computer, the computer is executed as described above. A software upgrade method provided.

In the embodiment of the present invention, only the change file is backed up based on the backup file model during the software upgrade, which reduces the number of backup files, saves time spent in upgrading the software patch, and improves the upgrade efficiency.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

BRIEF abstract

FIG. 1 is a flowchart of a software upgrade method according to an embodiment of the present invention;

2 is a flowchart of a software upgrade method according to another embodiment of the present invention;

3 is a flowchart of a software upgrade method according to another embodiment of the present invention;

4 is a schematic diagram of a file backup model according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of a software upgrade apparatus according to an embodiment of the present invention.

Embodiments of the invention

The detailed description will be made below in conjunction with the accompanying drawings and specific embodiments.

Before the patch set is upgraded, the modified file cannot be known in advance, and only the entire software version can be backed up. After the software runs for a period of time, the number of files will become very large, which will greatly increase the time-consuming of the patch set upgrade.

As shown in FIG. 1 , an embodiment of the present invention provides a software upgrade method, including the following steps:

Step S101: When receiving the upgrade instruction, determine the change file corresponding to the patch according to the file in the patch and the file in the target software.

In the embodiment of the present invention, the upgrade command is used to indicate that the software upgrade operation needs to be performed, and the target software may be any software that needs to be upgraded, and the change file may be at least one of a delete file and a modified file, where the deleted file may include A file that does not exist in the patch and exists in the target software. The modification file may include files that exist in the patch file and that do not exist in the target software. In the embodiment of the present invention, based on the file in the patch, it is found from the file in the target software whether there is a file with the same directory level and the same name as the file in the patch.

Step S102: Establish a backup file model of the patch according to the change file corresponding to the patch, where the backup file model is a tree structure generated according to a directory hierarchy of the change file corresponding to the patch.

In the embodiment of the present invention, the backup file model is a tree structure generated according to the directory hierarchy of the change file, and the tree node may be first generated based on the directory hierarchy of each change file. After obtaining the tree node corresponding to each change file, the tree node corresponding to each change file may be merged to obtain a backup file model.

Step S103: Perform file backup according to the node corresponding to the change file in the backup file model to obtain a backup file.

In the embodiment of the present invention, the file backup is performed according to the node corresponding to the change file, so that only the changed file is backed up, so that the number of backup files can be reduced.

Step S104: Perform an upgrade operation based on the patch.

As shown in FIG. 2, an embodiment of the present invention further provides a software upgrade method, including the following steps:

Step S201: When receiving the upgrade instruction, determine the new file and the change file corresponding to the patch according to the file in the patch and the file in the target software.

In the embodiment of the present invention, the newly added file may include a file that exists in the patch and does not exist in the target software.

Step S202: Establish a backup file model of the patch according to the newly added file corresponding to the patch and the change file.

In the embodiment of the present invention, the backup file model is a tree structure generated according to the directory hierarchy of the newly added file and the changed file. In the embodiment of the present invention, a tree node may be generated according to a directory hierarchy of each newly added file and each changed file, and attribute identifiers are set for each tree node. For example, for a newly added file, the corresponding node may be newly added. To delete a file, you can identify its corresponding node as deleted. The tree nodes are merged to obtain a backup file model.

Step S203: Perform file backup according to the node corresponding to the change file in the backup file model to obtain a backup file.

Step S204: Perform an upgrade operation based on the patch.

After performing the upgrade operation based on the patch, the method may further include: when the rollback instruction is received, performing a rollback operation according to the backup file model and the backup file.

In the embodiment of the present invention, the file corresponding to each node of the backup file model may be directly deleted from the upgraded target software, and the backup file is added to the target software, so that the target software is quickly rolled back to the pre-upgrade version. .

The patch may include a first patch and a second patch, and determining, according to the file in the patch and the file in the target software, a new file and a change file corresponding to the patch, including: according to the first patch Determining, in the file in the target software, the new file and the change file corresponding to the first patch, determining the second according to the file in the second patch and the file in the target software New files and change files corresponding to the patch;

The establishing a backup file model of the patch according to the newly added file and the change file corresponding to the patch includes: establishing the first patch according to the newly added file and the change file corresponding to the first patch. a first backup file model, the second backup file model of the second patch is established according to the newly added file and the change file corresponding to the second patch; and the first backup file model and the second backup file model are merged Each node gets the merged backup file model;

And performing the file backup according to the node corresponding to the change file in the backup file model, and obtaining the backup file, including: performing file backup according to the node corresponding to the change file in the merged backup file model, to obtain the backup file.

In the embodiment of the present invention, when the number of patches is multiple, the backup file model of each patch is established according to the newly added file and the change file corresponding to each patch, and the nodes in the backup file model of each patch are merged, and based on the merge After the backup file model for file backup. The following describes the first patch and the second patch as an example.

In the embodiment of the present invention, the first backup file model is a tree structure established according to each newly added file of the first patch and a directory hierarchy of each changed file, and the second backup file model is each newly added file and each according to the second patch. The tree structure of the directory hierarchy of the change file, since the same new file and the change file may exist in the first patch and the second patch, in order to avoid redundancy of the backup file, the first backup file model and the Each node in the second backup file model, where, for the same node, only one is retained after the merge. The embodiment of the present invention may use the backup file model of the first patch as a reference, traverse the nodes of the backup file model of the second patch, and add a node different from the backup file model of the first patch in the backup file model of the second patch to The first patch is in the backup file model, thereby obtaining a merged backup file model. Therefore, when the file is backed up based on the node corresponding to the changed file in the merged backup file model, the backup file redundancy can be avoided by repeatedly backing up the same file between different patches.

The upgrade order of the first patch may be located before the second patch, and the first backup file model of the first patch is established according to the newly added file and the change file corresponding to the first patch, according to the second After the new file and the change file corresponding to the patch are used to establish the second backup file model of the second patch, the method further includes: performing file backup according to the node corresponding to the change file in the first backup file model, a backup file corresponding to the first patch; deleting a node in the second backup file model that is the same as the first backup file model, obtaining an updated second backup file model, and according to the updated second file The node corresponding to the change file in the backup file model performs file backup to obtain a backup file corresponding to the second patch.

In actual situations, when there are multiple patches, the upgrade is usually performed according to each of the multiple patches. In the embodiment of the present invention, the upgrade order of the first patch precedes the second patch. After obtaining the first backup file model, the embodiment of the present invention performs file backup based on the first backup file model to obtain a backup file corresponding to the first patch. The backup file corresponding to the first patch may be a file that needs to be changed based on the target software when the first patch is upgraded. After obtaining the second backup file model, the node in the second backup file model that is the same as the first backup file model may be deleted, and the updated second backup file model is obtained, so that the updated second backup file is obtained. The file is backed up by the model, and the backup file corresponding to the second patch is obtained. The backup file corresponding to the second patch is a file that needs to be changed according to the target software when the second patch is upgraded.

In the embodiment of the present invention, each of the restore points can be respectively associated with each backup file model and each backup file, so that the target software can be quickly rolled back to the restore point according to the backup file model and the backup file corresponding to a certain restore point.

The patch may include a first patch and a second patch, where the upgrade order of the first patch is located before the second patch, and the patch is determined according to a file in the patch and a file in the target software. The newly added file and the change file include: determining, according to the file in the first patch and the file in the target software, a new file and a change file corresponding to the first patch;

The establishing a backup file model of the patch according to the newly added file and the change file corresponding to the patch includes: establishing the first patch according to the newly added file and the change file corresponding to the first patch. First backup file model;

And performing the file backup according to the node corresponding to the change file in the backup file model, including: performing file backup according to the node corresponding to the change file in the first backup file model, and obtaining the corresponding corresponding to the first patch. backup file;

Performing the upgrading operation based on the patch includes: performing an upgrade operation based on the first patch;

After performing the upgrade operation based on the first patch, the method further includes: determining, according to the file in the second patch and the file in the target software, that the upgrade is successful according to the first patch Adding a new file and a change file corresponding to the second patch; establishing a second backup file model of the second patch according to the newly added file and the change file corresponding to the second patch; deleting the second backup file model and the Obtaining a second backup file model of the same file as the backup file model of the first patch; performing file backup according to the node corresponding to the change file in the updated second backup file model, and obtaining the second A backup file corresponding to the patch; performing an upgrade operation based on the second patch.

In the embodiment of the present invention, the file backup and upgrade of each patch are performed in a serial manner, and the newly added file and the change corresponding to the first patch may be determined according to the file in the first patch and the file in the target software. And creating a first backup file model of the first patch according to the newly added file and the change file corresponding to the first patch; and performing file backup according to the node corresponding to the change file in the first backup file model a backup file corresponding to the first patch; performing an upgrade operation based on the first patch. When the upgrade of the first patch is successful, determining, according to the file in the second patch and the file in the target software, a new file and a change file corresponding to the second patch; Adding a new backup file and a change file to establish a second backup file model of the second patch; deleting a node in the second backup file model that is the same as the backup file model of the first patch, and obtaining an updated second backup The file model is configured to perform a file backup according to the node corresponding to the change file in the updated second backup file model, to obtain a backup file corresponding to the second patch, and perform an upgrade operation based on the second patch.

In the embodiment of the present invention, after obtaining the second backup file model, the second backup file model and the first backup file model may also be merged to obtain a merged backup file model.

After performing the upgrade operation based on the patch, the method may further include: when receiving the rollback instruction, acquiring a backup file model and a backup file corresponding to the target restore point according to the target restore point in the rollback instruction And performing a rollback operation on the upgraded target software according to the backup file model and the backup file corresponding to the target restore point.

In the embodiment of the present invention, the rollback instruction is used to indicate that a rollback operation needs to be performed, for example, when the upgrade fails through a certain patch. You can use the pop-up window to prompt the user whether to perform the rollback operation and input the target restore point. After receiving the target restore point input by the user, obtain the backup file model and the backup file corresponding to the target restore point.

The performing the rollback operation on the upgraded target software according to the backup file model and the backup file corresponding to the target restore point may include: deleting the backup corresponding to the target restore point from the upgraded target software A file corresponding to each node in the file model, and a backup file corresponding to the target restore point is added to the target software.

The method may further include: before the file in the patch includes an empty directory, before the backup file model of the patch is established according to the new file, the deleted file, and the modified file corresponding to the patch, the method may further include: Add a description file to the empty directory.

The description file may be any format file, for example, a WORD file, a TXT file, or the like. After the description file is added to the empty directory in the embodiment of the present invention, the tree node may be established according to the directory hierarchy of the description file. By converting an empty directory into a description file contained below, the entire backup file model can be simplified, and the entire backup file model is ultimately attributed to multiple separate files, so that the file is the smallest unit of operation, so that multiple patches are upgraded successively. There is no such thing as adding a new file to a recorded empty directory.

In the embodiment of the present invention, only the change file is backed up based on the backup file model during the software upgrade, thereby reducing the number of backup files, saving time spent in upgrading the software patch, and improving the upgrade efficiency. Moreover, the target software can be quickly and easily rolled back to the pre-upgrade version based on the backup file model and the backup file.

As shown in FIG. 3, an embodiment of the present invention provides a software upgrade method, including the following steps:

Step S301: Referring to the file in the patch as a reference, scanning the file of the same name in the target software one by one, and setting the corresponding identifier bit.

For the file in the patch, if the file exists in the target software, it can be identified as modified; if the file does not exist in the target software, the identifier is added; if the file needs to be deleted, the identifier is deleted.

Step S302: Establish a backup file model of the patch.

Referring to Figure 4, the backup file model is established as follows:

If it is a new file (that is, a new file), a tree node is created according to the directory hierarchy of the file, and the node is marked as new, wherein if the newly added file is an empty directory, then a new directory is created in the directory. Add a description file, for example, ignore.txt, and create a tree node based on the directory hierarchy of the description file, marking the node as new.

In the embodiment of the present invention, by converting the newly added empty directory into a new description file in the empty directory, the entire backup file model can be simplified, and the entire backup file model is ultimately attributed to a plurality of separate files, so that the file is minimized. The operating unit can avoid the situation where multiple files are added to the recorded empty directory when multiple patches are upgraded one after another.

If the file is deleted (that is, deleted), the tree node is created according to the directory hierarchy of the file, and the node is marked as deleted. If the deleted file is an empty directory, the description file is added in the empty directory. For example, ignore.txt creates a tree node based on the directory hierarchy of the description file and identifies the node as deleted.

If it is a modified file (that is, a modified file), the modification can be used as a combination of deletion and addition. Doing so further simplifies the type of file operations, simplifying all operations on the file to both new and deleted. Convert the modified file into a combination of the deleted file and the newly added file, and establish a tree node according to the deleted file and the directory hierarchy of the newly added file.

The tree nodes established according to the above rules are merged into the same tree structure to obtain a backup file model.

Step S303: Perform file backup according to the backup file model of the patch, and perform an upgrade operation based on the patch.

In the embodiment of the present invention, when the file is backed up, the nodes identified as deleted in the backup file model are sequentially backed up to a fixed directory, and only the records identified as newly added nodes are not processed.

You can also save the current backup file model before the patch is upgraded. When a patch fails to be upgraded or manually rolled back, you can choose to roll back to the restore point.

Step S304, determining whether the upgrade is successful.

When the upgrade is successful, step S305 is performed, and when the upgrade fails, step S309 is performed.

In step S305, it is determined whether there are other patches.

In the embodiment of the present invention, other patches refer to patches that need to be upgraded in addition to the upgraded patches. When there are other patches, step S306 is performed, and when there are no other patches, step S308 is performed.

Step S306, continuing to establish a backup file model for the subsequent patches, and merging the backup file model of the patch into the previous backup file model to obtain the merged backup file model.

In the embodiment of the present invention, the subsequent patch refers to a patch whose upgrade order is located after the currently upgraded patch, and the previous backup file model refers to a backup file model of the previously upgraded patch.

In the embodiment of the present invention, the process of establishing a backup file model of a subsequent patch is as follows:

If it is a new file, a new tree node is created according to the directory hierarchy of the file, and the tree node of the merged backup file model is obtained. If the node exists in the previous backup file model, it is not processed if the node does not exist. The node is added to the previous backup file model and identified as new.

If it is a deleted file, a new tree node is created according to the directory hierarchy of the file, and if the node exists in the previous backup file model, it is not processed; if the node does not exist, the node is added to the previous backup file model. And identified as deleted.

In the embodiment of the present invention, the presence and deletion of the newly added and deleted tree nodes are first performed, and the purpose is to record only the first operation for the same file, and no matter what operation or how many times the subsequent file is upgraded. The operations are no longer processed, so that the complexity of the software upgrade method of the embodiment of the present invention can be reduced.

Step S307: Perform a backup again according to the merged backup file model, and then perform a patch upgrade.

After the patch is upgraded, the process returns to step S305. The embodiment of the present invention may repeatedly perform steps S305 to S307 until all patches are upgraded.

It should be noted that, in the embodiment of the present invention, step S304 to step S307 may be repeatedly performed until all patches are upgraded.

Step S308, whether the version needs to be rolled back.

When the version needs to be rolled back (ie, rolled back), step S309 is performed, and when the version is not required to be rolled back, the process ends. In the actual situation, if a patch fails to be upgraded, or the patch is upgraded successfully, but the service is abnormal, you usually need to roll back the upgraded target software to the pre-upgrade version.

Step S309: Perform software rollback according to the backup file model.

The software rollback process may include: traversing the nodes in the merged backup file model, and deleting the files corresponding to each node in the merged backup file model from the target software; and overwriting the backup file to the target software.

It should be noted that the deletion here refers to the deletion of all nodes, not only the node identified as new, but also deleted after the identifier is deleted, because the node identified as deleted is recorded when the node is operated for the first time. In the subsequent operation, the node may be newly created, modified, and even placed other files in the directory. The deletion will completely clean up the files, so as to ensure the state of the software version and the current state after the backup file is overwritten to the target. It is exactly the same.

In the software upgrade method of the embodiment of the present invention, the backup file is greatly reduced; and the redundant backup of the same file between the patches is also removed, thereby further reducing the number of files that need to be backed up, and saving time spent in software patch upgrade. Improve the efficiency of the upgrade.

The embodiments of the present invention are described below by way of examples:

Patch set patchSet contains patch patch1 and patch patch2. Patch 1 includes: Add file FileAdd1, add empty directory DirAdd1, delete file FileDel1, delete empty directory DirDel2, delete directory DirDel3, modify file FileModify; patch patch2 includes: delete files FileAdd1, FileDel4, add FileAdd2, DirDel2.

Step a, refer to the file in the patch patch1 as a reference, scan the file of the same name in the target software one by one, and set the corresponding identifier, FileAdd1, DirAdd1 does not exist in the software version, set to add; FileDel1, DirDel2, DirDel3 in the target software Existing but need to be deleted, set to delete; FileModify exists in the software version and patch1, set to modify.

Step b, create a patch1 backup file model.

The tree node can be created according to the directory hierarchy of FileAdd1 and identified as new. Since DirAdd1 is a new empty directory, a new description file is added to DirAdd1, for example, ignore.txt. The tree node is created according to the directory hierarchy of ignore.txt and is identified as new.

A tree node is created according to the directory hierarchy of FileDel1 and identified as deleted. Since DirDel2 is an empty directory to be deleted, a description file is added to DirDel2, for example, ignore.txt, and a tree node is created according to the directory hierarchy of ignore.txt, and is identified as deleted.

Since DirDel3 is a deleted non-empty directory, a tree node is created according to the directory hierarchy of each file in DirDel3, and is identified as deleted. FileModify is a modified file that establishes a tree node based on FileModify's directory hierarchy and identifies it as deleted.

Step c: Perform file backup according to the backup file model of the patch patch1, and then upgrade based on the patch patch1.

When the file is backed up, only the files identified as deleted are backed up, for example, FileDel1, DirDel2/ignore.txt, all leaf node files under DirDel3, FileModify.

In step d, a patch patch2 backup file model is created, and the backup file model of the patch is merged into the previous backup file model.

FileAdd1 and DirDel2 have been recorded in patch1 and are not merged into the previous backup file model. Simply merge FileDel4 and FileAdd2.

Step e, perform file backup according to the backup file model of the merged patch, and then upgrade the patch patch2.

Simply back up FileDel4 and FileAdd2 in the backup file model.

Step f: If the upgrade of patch 1 and patch 2 fails or the version needs to be rolled back after the upgrade is successful, perform the following operations: Delete all nodes in the merged backup file model in the upgraded target software; overwrite all backup files to In the target software.

After the above operations, the full version of the target software can be rolled back, that is, back to the version before the target software upgrade.

As shown in FIG. 5, an embodiment of the present invention provides a software upgrade apparatus, where the software upgrade apparatus 50 includes:

The determining module 51 is configured to: when receiving the upgrade instruction, determine the change file corresponding to the patch according to the file in the patch and the file in the target software;

The establishing module 52 is configured to establish a backup file model of the patch according to the change file corresponding to the patch, where the backup file model is a tree structure generated according to a directory hierarchy of the change file corresponding to the patch ;

The first backup module 53 is configured to perform file backup according to the node corresponding to the change file in the backup file model, to obtain a backup file;

The upgrade module 54 is configured to perform an upgrade operation based on the patch.

The determining module 51 is further configured to: when receiving the upgrade instruction, determine, according to the file in the patch and the file in the target software, a new file and a change file corresponding to the patch; The method is configured to: establish a backup file model of the patch according to the newly added file corresponding to the patch and the change file.

The patch may include a first patch and a second patch, and the determining module 51 is configured to: determine, according to the file in the first patch and the file in the target software, a new one corresponding to the first patch And the file and the change file, the new file and the change file corresponding to the second patch are determined according to the file in the second patch and the file in the target software; the establishing module 52 is configured to: The first backup file model of the first patch is created by the new file and the change file corresponding to the first patch, and the second backup file model of the second patch is established according to the newly added file and the change file corresponding to the second patch. Merging each node in the first backup file model and the second backup file model to obtain a merged backup file model; the first backup module 53 is configured to: according to the merged backup file model The node corresponding to the change file performs file backup to obtain the backup file.

The device may further include: a second backup module, configured to establish the first file according to the newly added file and the change file corresponding to the first patch, where the upgrade order of the first patch is located before the second patch After the second backup file model of the second patch is created according to the new file and the change file corresponding to the second patch, the first backup file model of the patch is corresponding to the change file according to the first backup file model. The node performs a file backup to obtain a backup file corresponding to the first patch; and the third backup module is configured to delete the node in the second backup file model that is the same as the first backup file model, and obtain an updated And backing up the file model, and performing file backup according to the node corresponding to the change file in the updated second backup file model, to obtain a backup file corresponding to the second patch.

The patch may include a first patch and a second patch, where the upgrade order of the first patch is located before the second patch, and the determining module 51 is configured to: according to the file in the first patch and the a file in the target software, the new file and the change file corresponding to the first patch are determined; the establishing module 52 is configured to: establish the first patch according to the newly added file and the change file corresponding to the first patch The first backup file module is configured to: perform file backup according to the node corresponding to the change file in the first backup file model, and obtain a backup file corresponding to the first patch; The upgrade module 54 is configured to: perform an upgrade operation based on the first patch;

The determining module 51 is further configured to: after performing the upgrading operation based on the first patch, when the upgrade according to the first patch is successful, according to the file in the second patch and the file in the target software, Determining the new file and the change file corresponding to the second patch; the establishing module 52 is further configured to: establish a second backup file model of the second patch according to the newly added file and the change file corresponding to the second patch Deleting the same node as the backup file model of the first patch in the second backup file model to obtain an updated second backup file model; the first backup module 53 is further configured to: according to the update The node corresponding to the change file in the second backup file model performs file backup to obtain a backup file corresponding to the second patch. The upgrade module 54 is further configured to perform an upgrade operation based on the second patch.

The apparatus may further include: a rollback module configured to perform a rollback operation according to the backup file model and the backup file when receiving a rollback instruction after performing an upgrade operation based on the patch.

When the determining module 51 receives the upgrade command, the determining module 51 determines the change file corresponding to the patch according to the file in the patch and the file in the target software; the establishing module 52 establishes the change file according to the change file corresponding to the patch. a backup file model of the patch, wherein the backup file model is a tree structure generated according to a directory hierarchy of the change file corresponding to the patch; and the first backup module 53 corresponds to the change file in the backup file model. The node performs a file backup to obtain a backup file; the upgrade module 54 performs an upgrade operation based on the patch. In the embodiment of the present invention, only the change file is backed up based on the backup file model during the software upgrade, which reduces the number of backup files, saves time spent in upgrading the software patch, and improves the upgrade efficiency.

It should be noted that, in the embodiment of the present invention, the foregoing software upgrade device may be a user terminal in any embodiment of the method in the embodiment of the present invention, and any implementation manner of the user terminal in the method embodiment in the embodiment of the present invention may be The above software upgrade device in the embodiment is implemented, and the same beneficial effects are achieved, and details are not described herein again.

It will be understood by those skilled in the art that all or part of the steps of implementing the above embodiments may be performed by hardware associated with program instructions, which may be stored in a computer readable medium, including when executed, including The following steps are: when the upgrade command is received, the change file corresponding to the patch is determined according to the file in the patch and the file in the target software; and the backup file model of the patch is established according to the change file corresponding to the patch, where The backup file model is a tree structure generated according to a directory hierarchy of the change file corresponding to the patch; performing file backup according to the node corresponding to the change file in the backup file model to obtain a backup file; The patch performs an upgrade operation.

When the program is executed, the program further includes: determining, according to the file in the patch and the file in the target software, a new file and a change file corresponding to the patch; And establishing, by the corresponding change file, the backup file model of the patch, including: establishing a backup file model of the patch according to the newly added file corresponding to the patch and the change file.

The patch may include a first patch and a second patch, and determining, according to the file in the patch and the file in the target software, a new file and a change file corresponding to the patch, including: according to the first patch Determining, in the file in the target software, the new file and the change file corresponding to the first patch, determining the second according to the file in the second patch and the file in the target software a new file and a change file corresponding to the patch; the backup file model of the patch is established according to the newly added file and the change file corresponding to the patch, including: adding a new file corresponding to the first patch Establishing a first backup file model of the first patch, and a second backup file model of the second patch according to the new file and the change file corresponding to the second patch; and merging the first backup file a model and a node in the second backup file model, to obtain a merged backup file model; the corresponding change file according to the backup file model The node performs the file backup to obtain the backup file, and includes: performing file backup according to the node corresponding to the change file in the merged backup file model, to obtain the backup file.

The patch may include a first patch and a second patch, where the upgrade order of the first patch is located before the second patch, and the patch is determined according to a file in the patch and a file in the target software. The newly added file and the change file include: determining, according to the file in the first patch and the file in the target software, a new file and a change file corresponding to the first patch; The newly added file and the change file establish a backup file model of the patch, including: establishing a first backup file model of the first patch according to the newly added file and the change file corresponding to the first patch; The file backup is performed according to the node corresponding to the change file in the backup file model, including: performing file backup according to the node corresponding to the change file in the first backup file model, and obtaining a backup corresponding to the first patch. And performing the upgrading operation based on the patch, including: performing an upgrade operation based on the first patch; performing, based on the first patch After the level operation, the program further includes the following steps: when the upgrade is successful according to the first patch, determining the second patch according to the file in the second patch and the file in the target software Corresponding new file and change file; establishing a second backup file model of the second patch according to the newly added file and the change file corresponding to the second patch; deleting the second backup file model and the first The second backup file model is obtained by the same node of the backup file model of the patch, and the file corresponding to the change file in the updated second backup file model is used for file backup, and the second patch is obtained. Backing up the file; performing an upgrade operation based on the second patch.

After the upgrade operation is performed based on the patch, the program may further include: when receiving the rollback instruction, performing a rollback operation according to the backup file model and the backup file.

Those of ordinary skill in the art will appreciate that all or some of the steps, systems, and functional blocks/units of the methods disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical units; for example, one physical component may have multiple functions, or one function or step may be composed of several physical The components work together. Some or all of the components may be implemented as software executed by a processor, such as a digital signal processor or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on a computer readable medium, which may include computer storage media (or non-transitory media) and communication media (or transitory media). As is well known to those of ordinary skill in the art, the term computer storage medium includes volatile and nonvolatile, implemented in any method or technology for storing information, such as computer readable instructions, data structures, program modules, or other data. , removable and non-removable media. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridge, magnetic tape, magnetic disk storage or other magnetic storage device, or may Any other medium used to store the desired information and that can be accessed by the computer. Moreover, it is well known to those skilled in the art that communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and can include any information delivery media. The above is an alternative embodiment of the present invention, and it should be noted that those skilled in the art can make several improvements and retouchings without departing from the principles of the present invention. It should also be considered as the scope of protection of the present invention.

Industrial applicability

Claims

A software upgrade method, including:

When receiving the upgrade instruction, determining the change file corresponding to the patch according to the file in the patch and the file in the target software;

Establishing a backup file model of the patch according to the change file corresponding to the patch, where the backup file model is a tree structure generated according to a directory hierarchy of the change file corresponding to the patch;

Performing a file backup according to the node corresponding to the change file in the backup file model, and obtaining a backup file;

Perform an upgrade operation based on the patch.
The method according to claim 1, further comprising: when receiving an upgrade instruction, determining a new file and a change file corresponding to the patch according to a file in the patch and a file in the target software;

The establishing a backup file model of the patch according to the change file corresponding to the patch includes: establishing a backup file model of the patch according to the newly added file corresponding to the patch and the change file.
The method according to claim 2, wherein the patch comprises a first patch and a second patch, and according to files in the patch and files in the target software, determining new files and changes corresponding to the patches The file includes: determining, according to the file in the first patch and the file in the target software, a new file and a change file corresponding to the first patch, according to the file in the second patch and the target a file in the software, determining a new file and a change file corresponding to the second patch;

The establishing a backup file model of the patch according to the newly added file and the change file corresponding to the patch includes: establishing the first patch according to the newly added file and the change file corresponding to the first patch. a first backup file model, the second backup file model of the second patch is established according to the newly added file and the change file corresponding to the second patch; and the first backup file model and the second backup file model are merged Each node gets the merged backup file model;

And performing the file backup according to the node corresponding to the change file in the backup file model, and obtaining the backup file, including: performing file backup according to the node corresponding to the change file in the merged backup file model, and obtaining the file backup file.
The method according to claim 2, wherein the patch comprises a first patch and a second patch, and an upgrade order of the first patch is located before the second patch, according to a file in the patch and the target The file in the software, the new file and the change file corresponding to the patch are determined, including: determining, according to the file in the first patch and the file in the target software, a new file corresponding to the first patch and Change document;

The establishing a backup file model of the patch according to the newly added file and the change file corresponding to the patch includes: establishing the first patch according to the newly added file and the change file corresponding to the first patch. First backup file model;

And performing the file backup according to the node corresponding to the change file in the backup file model, and obtaining the backup file, including: performing file backup according to the node corresponding to the change file in the first backup file model, to obtain the a backup file corresponding to a patch;

Performing the upgrading operation based on the patch includes: performing an upgrade operation based on the first patch;

The method further includes: after performing an upgrade operation based on the first patch, when the upgrade according to the first patch is successful, determining, according to a file in the second patch and a file in the target software, New files and change files corresponding to the second patch;

Establishing a second backup file model of the second patch according to the newly added file and the change file corresponding to the second patch;

Deleting a node in the second backup file model that is the same as the backup file model of the first patch, and obtaining an updated second backup file model;

And performing a file backup according to the node corresponding to the change file in the updated second backup file model, to obtain a backup file corresponding to the second patch;

An upgrade operation is performed based on the second patch.
The method according to claim 2, further comprising: performing a rollback operation according to the backup file model and the backup file when receiving a rollback instruction after performing an upgrade operation based on the patch.
A software upgrade device, comprising:

Determining a module, configured to: when receiving an upgrade instruction, determine a change file corresponding to the patch according to the file in the patch and the file in the target software;

Establishing a module, configured to establish a backup file model of the patch according to the change file corresponding to the patch, where the backup file model is a tree structure generated according to a directory hierarchy of the change file corresponding to the patch;

The first backup module is configured to perform file backup according to the node corresponding to the change file in the backup file model, to obtain a backup file;

The upgrade module is configured to perform an upgrade operation based on the patch.
The apparatus according to claim 6, wherein the determining module is further configured to: when receiving an upgrade instruction, determine a new file corresponding to the patch according to a file in the patch and a file in the target software And change documents;

The establishing module is configured to: establish a backup file model of the patch according to the newly added file corresponding to the patch and the change file.
The apparatus according to claim 7, wherein the patch comprises a first patch and a second patch, and the determining module is configured to: determine, according to a file in the first patch and a file in the target software, And the new file and the change file corresponding to the first patch, and the new file and the change file corresponding to the second patch are determined according to the file in the second patch and the file in the target software;

The establishing module is configured to: establish a first backup file model of the first patch according to the newly added file and the change file corresponding to the first patch, and establish a new file and a change file corresponding to the second patch. a second backup file model of the second patch; merging each node in the first backup file model and the second backup file model to obtain a merged backup file model;

The first backup module is configured to: perform file backup according to the node corresponding to the change file in the merged backup file model, to obtain the backup file.
The apparatus according to claim 7, wherein the patch comprises a first patch and a second patch, the upgrade order of the first patch is located before the second patch, and the determining module is: according to the first patch a file in the target file and a file in the target software, and determining a new file and a change file corresponding to the first patch;

The establishing module is configured to: establish a first backup file model of the first patch according to the newly added file and the change file corresponding to the first patch;

The first backup module is configured to: perform file backup according to the node corresponding to the change file in the first backup file model, and obtain a backup file corresponding to the first patch;

The upgrading module is configured to: perform an upgrade operation based on the first patch;

The determining module is further configured to: after performing the upgrading operation based on the first patch, when the upgrade according to the first patch is successful, determining, according to the file in the second patch and the file in the target software, The new file and the change file corresponding to the second patch;

The establishing module is further configured to: establish a second backup file model of the second patch according to the newly added file and the change file corresponding to the second patch; and delete the second backup file model and the first patch The backup file model has the same node and gets the updated second backup file model;

The first backup module is further configured to: perform file backup according to the node corresponding to the change file in the updated second backup file model, to obtain a backup file corresponding to the second patch;

The upgrade module is further configured to perform an upgrade operation based on the second patch.
The apparatus of claim 7 further comprising:

The rollback module is configured to perform a rollback operation according to the backup file model and the backup file when receiving a rollback instruction after performing an upgrade operation based on the patch.
A computer readable storage medium storing computer executable instructions that, when executed by a processor, implement the method of any one of claims 1 to 5.