[go: up one dir, main page]

WO2018177193A1 - Procédé et dispositif de mise à niveau logicielle - Google Patents

Procédé et dispositif de mise à niveau logicielle Download PDF

Info

Publication number
WO2018177193A1
WO2018177193A1 PCT/CN2018/080043 CN2018080043W WO2018177193A1 WO 2018177193 A1 WO2018177193 A1 WO 2018177193A1 CN 2018080043 W CN2018080043 W CN 2018080043W WO 2018177193 A1 WO2018177193 A1 WO 2018177193A1
Authority
WO
WIPO (PCT)
Prior art keywords
file
patch
backup
model
change
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/CN2018/080043
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.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Publication of WO2018177193A1 publication Critical patent/WO2018177193A1/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
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Definitions

  • This document relates to, but is not limited to, the field of computer technology, and in particular, to a software upgrade method and apparatus.
  • the patch set of the software generally includes multiple patches.
  • 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.
  • An embodiment of the present invention provides a software upgrade method, where the method includes:
  • the backup file model is a tree structure generated according to a directory hierarchy of the change file corresponding to 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.
  • FIG. 1 is a flowchart of a software upgrade method according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a software upgrade method according to another embodiment of the present invention.
  • FIG. 3 is a flowchart of a software upgrade method according to another embodiment of the present invention.
  • FIG. 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.
  • the modified file 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.
  • 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.
  • the upgrade command is used to indicate that the software upgrade operation needs to be performed
  • the target software may be any software that needs to be upgraded
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the backup file model is a tree structure generated according to the directory hierarchy of the newly added file and the changed file.
  • 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.
  • 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 S204 Perform an 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.
  • 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;
  • 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.
  • 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 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
  • 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
  • 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.
  • the upgrade is usually performed according to each of the multiple patches.
  • the upgrade order of the first patch precedes the second patch.
  • 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.
  • 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.
  • 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.
  • 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;
  • 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.
  • 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.
  • the upgrade of 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.
  • the second backup file model and the first backup file model may also be merged to obtain a merged backup file model.
  • 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 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.
  • 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.
  • the tree node may be established according to the directory hierarchy of the description file.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • Step S304 determining whether the upgrade is successful.
  • step S305 is performed, and when the upgrade fails, step S309 is performed.
  • step S305 it is determined whether 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.
  • the subsequent patch refers to a patch whose upgrade order is located after the currently upgraded patch
  • the previous backup file model refers to a backup file model of the previously upgraded patch
  • the process of establishing a backup file model of a subsequent patch is as follows:
  • 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.
  • 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.
  • 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.
  • step S305 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.
  • step S304 to step S307 may be repeatedly performed until all patches are upgraded.
  • Step S308 whether the version needs to be rolled back.
  • step S309 is performed, and when the version is not required to be rolled back, the process ends.
  • 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.
  • deletion 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • Step e perform file backup according to the backup file model of the merged patch, and then upgrade the patch patch2.
  • 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.
  • the full version of the target software can be rolled back, that is, back to the version before the target software upgrade.
  • 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
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the program 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
  • 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.
  • 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.
  • the program may further include: when receiving the rollback instruction, performing a rollback operation according to the backup file model and the backup file.
  • 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.
  • 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.
  • a modulated data signal such as a carrier wave or other transport mechanism

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Quality & Reliability (AREA)
  • Stored Programmes (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

La présente invention concerne un procédé et un dispositif de mise à niveau logicielle. Le procédé consiste : lors de la réception d'une instruction de mise à niveau, à déterminer un fichier de changement correspondant à un correctif selon un fichier dans le correctif et un fichier dans un logiciel cible ; à établir un modèle de fichier de sauvegarde du correctif selon le fichier de changement correspondant au correctif, le modèle de fichier de sauvegarde étant une structure arborescente générée selon une hiérarchie de répertoire du fichier de changement correspondant au correctif ; à effectuer une sauvegarde de fichier selon un nœud correspondant au fichier de changement dans le modèle de fichier de sauvegarde de sorte à obtenir un fichier de sauvegarde ; et à effectuer une opération de mise à niveau sur la base du correctif.
PCT/CN2018/080043 2017-03-27 2018-03-22 Procédé et dispositif de mise à niveau logicielle Ceased WO2018177193A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710187257.6 2017-03-27
CN201710187257.6A CN108664255B (zh) 2017-03-27 2017-03-27 一种软件升级方法及装置

Publications (1)

Publication Number Publication Date
WO2018177193A1 true WO2018177193A1 (fr) 2018-10-04

Family

ID=63674189

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/080043 Ceased WO2018177193A1 (fr) 2017-03-27 2018-03-22 Procédé et dispositif de mise à niveau logicielle

Country Status (2)

Country Link
CN (1) CN108664255B (fr)
WO (1) WO2018177193A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110874237A (zh) * 2019-12-30 2020-03-10 深圳市英博超算科技有限公司 软件升级方法、装置、终端以及可读存储介质
CN113094861A (zh) * 2021-05-08 2021-07-09 国网河北省电力有限公司经济技术研究院 数据存储方法、装置、设备和存储介质

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109446161B (zh) * 2018-10-18 2021-12-28 网易（杭州）网络有限公司 信息监控方法、装置、电子设备及存储介质
CN117931242B (zh) * 2024-02-02 2024-12-10 山东中创软件商用中间件股份有限公司 负载均衡软件补丁升级及回滚方法、装置、设备及介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070245332A1 (en) * 2001-09-28 2007-10-18 Yoram Tal Method and apparatus to perform an application software migration
CN103699410A (zh) * 2013-12-20 2014-04-02 北京奇虎科技有限公司 一种应用程序的更新方法和装置
CN103955363A (zh) * 2014-04-08 2014-07-30 国云科技股份有限公司 一种程序升级安装包的制作方法
CN105550060A (zh) * 2014-10-31 2016-05-04 Tcl集团股份有限公司 一种增量升级的备份方法及装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7251749B1 (en) * 2004-02-12 2007-07-31 Network Appliance, Inc. Efficient true image recovery of data from full, differential, and incremental backups
CN102193805B (zh) * 2010-03-11 2014-05-07 华为技术有限公司 一种软件补丁升级装置及方法
JP2013033334A (ja) * 2011-08-01 2013-02-14 Nippon Telegr & Teleph Corp <Ntt> バックアップ装置、および障害復旧方法
CN104156244B (zh) * 2014-08-06 2018-09-04 北京奇虎科技有限公司 一种软件升级的方法和装置
CN105468396A (zh) * 2014-09-11 2016-04-06 深圳Tcl数字技术有限公司 差分包生成方法、升级方法、生成装置及Linux终端
CN105117263B (zh) * 2015-09-14 2018-06-22 北京空间飞行器总体设计部 一种unix环境软件系统升级方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070245332A1 (en) * 2001-09-28 2007-10-18 Yoram Tal Method and apparatus to perform an application software migration
CN103699410A (zh) * 2013-12-20 2014-04-02 北京奇虎科技有限公司 一种应用程序的更新方法和装置
CN103955363A (zh) * 2014-04-08 2014-07-30 国云科技股份有限公司 一种程序升级安装包的制作方法
CN105550060A (zh) * 2014-10-31 2016-05-04 Tcl集团股份有限公司 一种增量升级的备份方法及装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110874237A (zh) * 2019-12-30 2020-03-10 深圳市英博超算科技有限公司 软件升级方法、装置、终端以及可读存储介质
CN113094861A (zh) * 2021-05-08 2021-07-09 国网河北省电力有限公司经济技术研究院 数据存储方法、装置、设备和存储介质

Also Published As

Publication number Publication date
CN108664255A (zh) 2018-10-16
CN108664255B (zh) 2023-04-11

Similar Documents

Publication Publication Date Title
JP5342302B2 (ja) ファームウェア更新システム、ファームウェア配信サーバ、及びプログラム
US8726262B2 (en) Firmware update system and information apparatus, and program
US10599337B2 (en) Method and device for writing data and acquiring data in a distributed storage system
US6892255B2 (en) Program install method, file renewal method, program and computer system
WO2018177193A1 (fr) Procédé et dispositif de mise à niveau logicielle
US20160034358A1 (en) Storage apparatus and method for controlling cache of storage apparatus
US11099980B2 (en) Host aware update write
CN104484240A (zh) 一种终端数据存储的方法及装置
WO2019041891A1 (fr) Procédé et dispositif permettant de générer un ensemble de mise à niveau
CN114356855A (zh) 文件管理方法、装置、电子装置及可读存储介质
US20130086572A1 (en) Generation apparatus, generation method and computer readable information recording medium
US9921918B1 (en) Cloud-based data backup and management
CN106484312B (zh) 一种虚拟机磁盘数据迁移方法及装置
CN111949287A (zh) 软件升级方法和装置
US11449389B2 (en) Techniques for performing incremental data backups
WO2017067397A1 (fr) Procédé et dispositif de récupération de données
WO2013107158A1 (fr) Procédé et système conçus pour la gestion d&#39;un paramètre système dans un dispositif terminal
CN110879764A (zh) 一种位图设置方法、装置、设备及可读存储介质
CN110471796B (zh) 一种面向文件目录的完全和增量的备份恢复方法
CN115543225B (zh) 数据处理方法、系统、装置、计算机存储介质及电子设备
CN107357536B (zh) 分布式存储系统数据修改写方法及系统
US10860533B1 (en) File size as an indicator of file properties
CN107145501B (zh) 文件更新方法、文件复制方法以及相应的系统
CN109241071A (zh) 一种Android数据库升级方法、装置及终端
JP2005038176A (ja) コンピュータシステムおよびファイル管理方法

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: 18775325

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: 18775325

Country of ref document: EP

Kind code of ref document: A1