Method and device for controlling version upgrade and rollback

Abstract

The invention relates to a method and device for controlling version upgrade and backspacing, and belongs to the technical field of version upgrade and backspacing, and the method for controlling version upgrade comprises the following steps: a server stores all client version installation files; the client checks whether version upgrade exists or not, and if the version upgrade exists and an operation of confirming a version upgrade instruction by a user is received, the version upgrade instruction and a new version program file downloading address are notified to the independent upgrade backspacing detection program; receiving a version upgrading instruction, downloading the new version program file from the new version program file downloading address, and compressing and backing up the old version program file; creating a new version relation mapping record table, and recording new version program file information and old version program file information in the version relation mapping record table; and decompressing the new version program file, and covering the old version program file to complete version upgrading. According to the method, a user can autonomously select version upgrading or backspacing, and version upgrading and backspacing are completed in an independent upgrading and backspacing detection program.

Description

Technical Field

[0001] The present invention belongs to the technical field of version upgrade and rollback, and in particular, relates to a method and device for controlling version upgrade and rollback. Background Art

[0002] As the client business continues to develop, the client functions are becoming more and more abundant, which in turn leads to the increasing consumption of computer system resources. In order to allow users to use the latest functions and the latest versions, the clients used by users will be upgraded uniformly. Because the user's computer equipment will not upgrade the computer hardware configuration along with the client software upgrade, when using a computer with a low computer hardware configuration to use the new version, there will be user experience problems caused by insufficient resources.

[0003] Existing technical solutions are mostly for forced or non-forced upgrades for users. Most of the current upgrade solutions are implemented by the client process, and after the upgrade is successful, the old version is overwritten and updated. Users are not supported to independently choose to roll back the client upgrade. For example, due to low computer hardware configuration, when using the new version of the client, there may be insufficient system resources, which affects the client experience and the user wishes to roll back to the old version. However, there is no download channel for the old version of the client or the old version information is not recorded, resulting in the user being unable to roll back to the old version. Summary of the invention

[0004] In view of the above deficiencies in the prior art, the purpose of the invention is to provide a method and device for controlling version upgrades and rollbacks, whereby users can independently choose version upgrades or rollbacks, and complete version upgrades and rollbacks within an independent upgrade and rollback detection program, thereby improving the user experience.

[0005] A first aspect of the present invention provides a method for controlling version upgrade and rollback, comprising:

[0006] The server saves all client version installation files;

[0007] The client checks whether there is a version upgrade. If the check result shows that there is a version upgrade and the user confirms the version upgrade instruction, the client notifies the independent upgrade rollback detection program of the version upgrade instruction and the download address of the new version program file;

[0008] The independent upgrade rollback detection program receives the version upgrade instruction, downloads the new version program file from the new version program file download address, and compresses and backs up the old version program file;

[0009] Create a new version relationship mapping record table, and record the new version program file information and the old version program file information in the version relationship mapping record table;

[0010] Unzip the new version program file, overwrite the old version program file, and complete the version upgrade;

[0011] Upon receiving the user's confirmation of the version rollback instruction, the independent upgrade rollback detection program receives the version rollback instruction and reads the version relationship mapping record table to confirm whether there is an old version of the program file information;

[0012] If the confirmation result shows that the old version of the program file information exists, the old version of the program file path in the old version of the program file information is read;

[0013] Read the path of the old version program file to determine whether there is a compressed backup file of the old version program file;

[0014] If the judgment result is that there is a compressed backup file of the old version of the program file, the old version of the program file is decompressed and overwritten with the new version of the program file to complete the version rollback.

[0015] Furthermore, in the above method for controlling version upgrade and rollback, the new version program file information includes the version number, version serial number and whether to force upgrade, and the old version program file information includes the version number, version serial number, whether to force upgrade and file path.

[0016] Furthermore, in the above method for controlling version upgrade and rollback, before the client checks whether there is a version upgrade, it also includes:

[0017] Receive the user's operation of starting the client, start the client and the independent upgrade rollback detection program process.

[0018] Furthermore, in the above method for controlling version upgrade and rollback, the independent upgrade rollback detection program is notified of the version upgrade instruction and the download address of the new version program file, including:

[0019] The version upgrade instruction and the download address of the new version program file are notified to the independent upgrade rollback detection program through inter-process communication.

[0020] Furthermore, the above method for controlling version upgrade and rollback further includes:

[0021] Read the path of the old version program file to determine whether there is a compressed backup file of the old version program file;

[0022] If the result of the judgment is that there is no compressed backup file of the old version of the program file, the independent upgrade rollback detection program downloads the old version of the program file from the server according to the version number and version sequence number of the old version of the program file information;

[0023] Update the path of the old version program file in the version mapping relationship record table;

[0024] Unzip the old version program files, overwrite the new version program files, and complete the version rollback.

[0025] Furthermore, in the above method for controlling version upgrade and rollback, after the independent upgrade rollback detection program receives the version rollback instruction, it also includes:

[0026] The version number and version serial number of the current new version are consistent with the new version number and new version serial number recorded in the version relationship mapping record table;

[0027] If the matching result is that the version number and version serial number of the current new version are consistent with the new version number and new version serial number recorded in the version relationship mapping record table, the version relationship mapping record table is read to confirm whether there is old version program file information.

[0028] Furthermore, the above method for controlling version upgrade and rollback further includes:

[0029] Read the version relationship mapping record table to confirm whether there is old version program file information;

[0030] If the confirmation result is that there is no old version program file information, it will prompt that there is no old version information and cannot be rolled back.

[0031] A second aspect of the present invention further provides a device for controlling version upgrade and rollback, comprising:

[0032] Save module: used by the server to save all client version installation files;

[0033] Check module: used for the client to check whether there is a version upgrade. If the check result is that there is a version upgrade and the user confirms the version upgrade instruction, the version upgrade instruction and the download address of the new version program file are notified to the independent upgrade rollback detection program;

[0034] Receiving module: used for independently upgrading the rollback detection program, receiving the version upgrade instruction, downloading the new version program file from the new version program file download address, and compressing and backing up the old version program file;

[0035] New module: used to create a new version relationship mapping record table, in which the new version program file information and the old version program file information are recorded;

[0036] Upgrade module: used to decompress the new version program files, overwrite the old version program files, and complete the version upgrade;

[0037] Reading module: used for receiving the operation of the user confirming the version rollback instruction, the independent upgrade rollback detection program receives the version rollback instruction, and reads the version relationship mapping record table to confirm whether there is the old version program file information;

[0038] Confirmation module: used for reading the path of the old version of the program file in the old version of the program file information if the confirmation result is that the old version of the program file information exists;

[0039] Judgment module: used to read the path of the old version program file to determine whether there is a compressed backup file of the old version program file;

[0040] Rollback module: if the judgment result is that there is a compressed backup file of the old version of the program file, it is used to decompress the old version of the program file, overwrite the new version of the program file, and complete the version rollback.

[0041] According to a third aspect of the present invention, an electronic device is provided, comprising: a processor and a memory;

[0042] The processor calls the program or instruction stored in the memory to execute any one of the above methods for controlling version upgrade and rollback.

[0043] In a fourth aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a program or instruction, and the program or instruction enables a computer to execute any one of the above methods for controlling version upgrade and rollback.

[0044] The beneficial effects of the present invention are as follows: under the premise of non-mandatory upgrade, the present invention starts an independent upgrade and rollback detection program process. The independent upgrade and rollback detection program does not need to be bound to a specific desktop client program and supports access and use by any client. The independent upgrade and rollback detection program provides version upgrade and rollback interfaces. The user can independently select the upgrade or rollback operation, and the version upgrade is completed or the rollback operation is quickly completed within the independent upgrade and rollback detection application program, thereby reducing client program coupling and implementation complexity; the independent upgrade and rollback detection program is internally implemented in the process of version upgrade, and the version mapping relationship table is recorded through a local configuration file to improve the efficiency of resolving the impact of client version upgrades. The version relationship can be quickly read through local recording without relying on a network interface; the independent upgrade and rollback detection program is internally implemented in the process of version rollback, and the old version backup file is decompressed to quickly complete file overwriting and restore the old version for use without repeated installation, thereby reducing user rollback costs and reducing the scope of impact of version upgrades. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] The accompanying drawings are only used to illustrate specific embodiments and are not considered to limit the present invention. In the entire drawings, the same reference symbols represent the same components. Obviously, the drawings described below are only some embodiments recorded in the embodiments of the present invention. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings.

[0046] Figure 1A diagram of a method for controlling version upgrades provided by an embodiment of the present invention;

[0047] Figure 2 A method for controlling version rollback provided in an embodiment of the present invention Figure 1 ;

[0048] Figure 3 A method for controlling version rollback provided in an embodiment of the present invention Figure 2 ;

[0049] Figure 4 A method for controlling version rollback provided in an embodiment of the present invention Figure 3 ;

[0050] Figure 5 A diagram of a device for controlling version upgrade and rollback provided in an embodiment of the present invention;

[0051] Figure 6 A schematic block diagram of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0052] In order to enable those skilled in the art to better understand the technical solutions in the embodiments of the present invention, the technical solutions of the present invention will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all of the embodiments. It should be understood that these descriptions are only exemplary and are not intended to limit the scope of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in the field without making creative work should fall within the scope of protection of the present invention.

[0053] Furthermore, in the following description, descriptions of well-known structures and technologies are omitted to avoid unnecessarily obscuring the concepts disclosed in the present invention.

[0054] In the description of the present invention, the terms "first", "second", and "third" are used for descriptive purposes only and should not be understood as indicating or implying relative importance. The terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be internal communication between two components. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0055] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Instead, they are merely examples of methods and systems consistent with some aspects of the present invention as detailed in the appended claims.

[0056] The present invention proposes a method, device, electronic device and storage medium for controlling version upgrade and rollback. Users can independently choose version upgrade or rollback, and complete version upgrade and rollback within an independent upgrade and rollback detection program, thereby improving the user experience.

[0057] Before introducing the embodiments of the present invention, professional terms involved in the present invention are first introduced.

[0058] New version: refers to the latest version that needs to be upgraded by the server-deployed client;

[0059] Old version: refers to a specific version currently being used on the user's computer.

[0060] Method Embodiment

[0061] A first aspect of the present invention provides a method for controlling version upgrade and rollback, which specifically includes a method for controlling version upgrade and a method for controlling version rollback.

[0062] Figure 1 A diagram of a method for controlling version upgrades provided in an embodiment of the present invention.

[0063] A method for controlling version upgrade proposed by the present invention is combined with Figure 1 , including five steps from S1 to S6,

[0064] S1: The server saves all client version installation files.

[0065] Specifically, in the embodiment of the present invention, before releasing a new version upgrade, the server saves the old version file program file on the server for use as an upgrade rollback download, so that the server saves all client version installation files.

[0066] S2: The client checks whether there is a version upgrade. If the check result is that there is a version upgrade and the user confirms the version upgrade instruction, the client notifies the independent upgrade rollback detection program of the version upgrade instruction and the download address of the new version program file.

[0067] Specifically, in an embodiment of the present invention, this is a non-mandatory version upgrade. When the client checks for the existence of a version upgrade and receives a user confirmation instruction for the version upgrade, the user independently chooses the version upgrade and notifies the independent upgrade rollback detection program of the version upgrade instruction and the download address of the new version program file through the independent upgrade rollback detection program process.

[0068] S3: The independent upgrade rollback detection program receives the version upgrade instruction, downloads the new version program file from the new version program file download address, and compresses and backs up the old version program file.

[0069] Specifically, in an embodiment of the present invention, the independent upgrade rollback detection program receives a version upgrade instruction, starts a download action for the new version program file, downloads the new version program file from the new version program file download address, and simultaneously starts an old version program file compression and backup action to compress and back up the old version program file.

[0070] S4: Create a new version relationship mapping record table, and record the new version program file information and the old version program file information in the version relationship mapping record table.

[0071] Specifically, in an embodiment of the present invention, the new version program file information includes the version number, version serial number, and whether to force an upgrade; the old version program file information includes the version number, version serial number, whether to force an upgrade, and the file path; the version mapping relationship record table is used for reading and judging when the user chooses to upgrade or roll back.

[0072] S5: Unzip the new version program file and overwrite the old version program file to complete the version upgrade.

[0073] Specifically, in the embodiment of the present invention, after completing the version mapping relationship record, the new version file is decompressed to overwrite the original old version program file content to complete the version upgrade.

[0074] Figure 2 A method for controlling version rollback provided in an embodiment of the present invention Figure 1 .

[0075] The present invention proposes a method for controlling version rollback, combining Figure 2 , including: four steps from S21 to S24,

[0076] S21: receiving the operation of the user confirming the version rollback instruction, the independent upgrade rollback detection program receives the version rollback instruction, and reads the version relationship mapping record table to confirm whether there is old version program file information.

[0077] S22: If the confirmation result is that the old version program file information exists, read the old version program file path in the old version program file information.

[0078] S23: Read the old version program file path to determine whether there is a compressed backup file of the old version program file;

[0079] S24: If the result of the determination is that there is a compressed backup file of the old version of the program file, the old version of the program file is decompressed and the new version of the program file is overwritten to complete the version rollback.

[0080] Specifically, in an embodiment of the present invention, an operation of confirming a version rollback instruction from the user is received, the user independently selects version rollback, and the version rollback instruction is notified to the independent upgrade rollback detection program through the independent upgrade rollback detection program process. The independent upgrade rollback detection program receives the version rollback instruction, reads the version relationship mapping record table to confirm whether there is old version program file information, and if there is old version program file information, reads the old version program file path in the old version program file information, reads the old version program file path to determine whether there is a compressed backup file of the old version program file, and if there is a compressed backup file of the old version program file, decompresses the old version program file, overwrites the new version program file, and completes the version rollback.

[0081] In some embodiments, after the version rollback is completed, the compressed backup file is deleted to avoid occupying disk resources.

[0082] Furthermore, in the above method for controlling version upgrade and rollback, before the client checks whether there is a version upgrade, it also includes:

[0083] Receive the user's operation of starting the client, start the client and the independent upgrade rollback detection program process.

[0084] Specifically, in an embodiment of the present invention, when an operation of starting the client by the user is received, the client is started and an independent upgrade rollback detection program process is started. The independent upgrade rollback detection program process here is independent of the client process and does not affect the use of the client. It has the functions of upgrading, downloading, overwriting and installing and detecting the user's autonomous selection of rollback version action operations.

[0085] Furthermore, in the above method for controlling version upgrade and rollback, the independent upgrade rollback detection program is notified of the version upgrade instruction and the download address of the new version program file, including:

[0086] The version upgrade instruction and the download address of the new version program file are notified to the independent upgrade rollback detection program through inter-process communication.

[0087] Specifically, in the embodiment of the present invention, the process is an independent upgrade rollback detection program process.

[0088] Figure 3 A method for controlling version rollback provided in an embodiment of the present invention Figure 2.

[0089] Furthermore, the above method for controlling version upgrade and rollback is combined with Figure 3 , and also includes four steps S31 to S34:

[0090] S31: Read the path of the old version program file to determine whether there is a compressed backup file of the old version program file;

[0091] S32: If the result of the determination is that there is no compressed backup file of the old version of the program file, the independent upgrade rollback detection program downloads the old version of the program file from the server according to the version number and version sequence number of the old version of the program file information;

[0092] S33: updating the path of the old version program file in the version mapping relationship record table;

[0093] S34: decompress the old version program file, overwrite the new version program file, and complete the version rollback.

[0094] Specifically, in an embodiment of the present invention, the path of the old version of the program file is read to determine whether there is a compressed backup file of the old version of the program file. If there is no compressed backup file of the old version of the program file, the version number and version sequence number of the old version of the program file information of the independent upgrade rollback detection program are used to download the old version of the program file from the server. After the download is complete, the path of the old version of the program file in the version mapping relationship record table is updated, the old version of the program file is decompressed, and the new version of the program file is overwritten to complete the version rollback.

[0095] Furthermore, in the above method for controlling version upgrade and rollback, after the independent upgrade rollback detection program receives the version rollback instruction, it also includes:

[0096] The version number and version serial number of the current new version are consistent with the new version number and new version serial number recorded in the version relationship mapping record table;

[0097] If the matching result is that the version number and version serial number of the current new version are consistent with the new version number and new version serial number recorded in the version relationship mapping record table, the version relationship mapping record table is read to confirm whether there is old version program file information.

[0098] Specifically, in an embodiment of the present invention, after the independent upgrade rollback detection program receives the version rollback instruction, when the version number and version serial number of the current new version are matched with the new version number and new version serial number recorded in the version relationship mapping record table, the version relationship mapping record table is read to confirm whether there is old version program file information.

[0099] Figure 4 A method for controlling version rollback provided in an embodiment of the present invention Figure 3 .

[0100] Furthermore, the above method for controlling version upgrade and rollback is combined with Figure 4 , and also includes two steps S41 to S42:

[0101] S41: Read the version relationship mapping record table to confirm whether there is old version program file information;

[0102] S42: If the confirmation result is that the old version of the program file information does not exist, it is prompted that the old version information does not exist and rollback is not possible.

[0103] Specifically, in an embodiment of the present invention, the version relationship mapping record table is read to confirm whether there is old version program file information. If the confirmation result is that there is no old version program file information, it is prompted that there is no old version information and rollback is not possible, so that the user understands the reason why rollback is not possible.

[0104] Device Embodiment

[0105] Figure 5 A diagram of a device for controlling version upgrade and rollback provided in an embodiment of the present invention.

[0106] In a second aspect of the present invention, a device for controlling version upgrade and rollback is also provided, Figure 5 ,include:

[0107] Saving module 51: used by the server to save all client version installation files.

[0108] Specifically, in the embodiment of the present invention, before releasing a new version upgrade, the server saves the old version file program file on the server for use as an upgrade rollback download, so that the server's storage module 51 saves all client version installation files.

[0109] Check module 52: used for the client to check whether there is a version upgrade. If the check result is that there is a version upgrade and the user confirms the version upgrade instruction, the version upgrade instruction and the new version program file download address are notified to the independent upgrade rollback detection program.

[0110] Specifically, in the embodiment of the present invention, this is a non-mandatory version upgrade. The client's inspection module 52 checks whether there is a version upgrade and receives the user's confirmation of the version upgrade instruction. The user independently chooses the version upgrade and notifies the independent upgrade rollback detection program of the version upgrade instruction and the download address of the new version program file through the independent upgrade rollback detection program process.

[0111] Receiving module 53: used for independently upgrading the rollback detection program, upon receiving the version upgrade instruction, downloading the new version program file from the new version program file download address, and compressing and backing up the old version program file.

[0112] Specifically, in the embodiment of the present invention, the receiving module 53 of the independent upgrade rollback detection program receives a version upgrade instruction, starts a download action for the new version program file, downloads the new version program file from the new version program file download address, and simultaneously starts an old version program file compression and backup action to compress and back up the old version program file.

[0113] New creation module 54: used to create a new version relationship mapping record table, in which the new version program file information and the old version program file information are recorded.

[0114] Specifically, in an embodiment of the present invention, the new creation module 54 creates a new version relationship mapping record table, and records the new version program file information and the old version program file information in the version relationship mapping record table. The new version program file information includes the version number, version serial number, and whether to force an upgrade. The old version program file information includes the version number, version serial number, whether to force an upgrade, and the file path. The version mapping relationship record table is used for reading and judging when the user chooses to upgrade or roll back.

[0115] Upgrade module 55: used to decompress the new version program file, overwrite the old version program file, and complete the version upgrade.

[0116] Specifically, in the embodiment of the present invention, after completing the version mapping relationship record, the upgrade module 55 decompresses the new version file, overwrites the original old version program file content, and completes the version upgrade.

[0117] Reading module 56: used for receiving the operation of the user confirming the version rollback instruction, the independent upgrade rollback detection program receives the version rollback instruction, and reads the version relationship mapping record table to confirm whether there is an old version of the program file information;

[0118] Confirmation module 57: for reading the path of the old version of the program file in the old version of the program file information if the confirmation result is that the old version of the program file information exists;

[0119] Determination module 58: used for reading the path of the old version program file to determine whether there is a compressed backup file of the old version program file;

[0120] Rollback module 59: if the result of the determination is that there is a compressed backup file of the old version of the program file, decompress the old version of the program file and overwrite the new version of the program file to complete the version rollback.

[0121] Specifically, in an embodiment of the present invention, when a user confirms a version rollback instruction, the user independently selects version rollback and notifies the independent upgrade rollback detection program of the version rollback instruction through the independent upgrade rollback detection program process. The independent upgrade rollback detection program receives the version rollback instruction, and the reading module 56 reads the version relationship mapping record table to confirm whether there is old version program file information. When the confirmation module 57 confirms that there is old version program file information, it reads the old version program file path in the old version program file information. The judgment module 58 reads the old version program file path to determine whether there is a compressed backup file of the old version program file. When there is a compressed backup file of the old version program file, the rollback module 59 decompresses the old version program file, overwrites the new version program file, and completes the version rollback.

[0122] According to a third aspect of the present invention, an electronic device is provided, comprising: a processor and a memory;

[0123] The processor calls the program or instruction stored in the memory to execute any one of the above methods for controlling version upgrade and rollback.

[0124] In a fourth aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a program or instruction, and the program or instruction enables a computer to execute any one of the above methods for controlling version upgrade and rollback.

[0125] Figure 6 It is a schematic block diagram of an electronic device provided by an embodiment of the present invention.

[0126] like Figure 6 As shown, the electronic device includes: at least one processor 601, at least one memory 602 and at least one communication interface 603. The various components in the electronic device are coupled together through a bus system 604. The communication interface 603 is used to transmit information between external devices. It can be understood that the bus system 604 is used to achieve connection and communication between these components. In addition to the data bus, the bus system 604 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, Figure 6 Various buses are labeled as bus system 604 .

[0127] It can be understood that the memory 602 in this embodiment can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories.

[0128] In some implementations, the memory 602 stores the following elements, executable units or data structures, or a subset thereof, or an extended set thereof: an operating system and application programs.

[0129] The operating system includes various system programs, such as a framework layer, a core library layer, a driver layer, etc., which are used to implement various basic services and process hardware-based tasks. The application includes various application programs, such as a media player (Media Player), a browser (Browser), etc., which are used to implement various application services. A program that implements any method of a method for controlling version upgrade and rollback provided in an embodiment of the present invention can be included in the application.

[0130] In an embodiment of the present invention, the processor 601 calls a program or instruction stored in the memory 602, specifically, a program or instruction stored in an application, and the processor 601 is used to execute the steps of each embodiment of a method for controlling version upgrade and rollback provided in an embodiment of the present invention.

[0131] The server saves all client version installation files;

[0132] The client checks whether there is a version upgrade. If the check result shows that there is a version upgrade and the user confirms the version upgrade instruction, the client notifies the independent upgrade rollback detection program of the version upgrade instruction and the download address of the new version program file;

[0133] The independent upgrade rollback detection program receives the version upgrade instruction, downloads the new version program file from the new version program file download address, and compresses and backs up the old version program file;

[0134] Create a new version relationship mapping record table, and record the new version program file information and the old version program file information in the version relationship mapping record table;

[0135] Unzip the new version program file, overwrite the old version program file, and complete the version upgrade;

[0136] Upon receiving the user's confirmation of the version rollback instruction, the independent upgrade rollback detection program receives the version rollback instruction and reads the version relationship mapping record table to confirm whether there is an old version of the program file information;

[0137] If the confirmation result shows that the old version of the program file information exists, the old version of the program file path in the old version of the program file information is read;

[0138] Read the path of the old version program file to determine whether there is a compressed backup file of the old version program file;

[0139] If the judgment result is that there is a compressed backup file of the old version of the program file, the old version of the program file is decompressed and overwritten with the new version of the program file to complete the version rollback.

[0140] Any of the methods for controlling version upgrade and rollback provided in an embodiment of the present invention can be applied to the processor 601, or implemented by the processor 601. The processor 601 can be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in the processor 601 or an instruction in the form of software. The above-mentioned processor 601 can be a general-purpose processor, a digital signal processor (DigitalSignal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc.

[0141] The steps of any method in a method for controlling version upgrade and rollback provided by an embodiment of the present invention can be directly embodied as being executed by a hardware decoding processor, or being executed by a combination of hardware and software units in the decoding processor. The software unit can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory 602, and the processor 601 reads the information in the memory 602 and completes the steps of the method in combination with its hardware.

[0142] Those skilled in the art will appreciate that although some embodiments described herein include certain features included in other embodiments but not other features, the combination of features from different embodiments is meant to be within the scope of the present invention and to form different embodiments.

[0143] Those skilled in the art will appreciate that the description of each embodiment has its own emphasis, and for parts not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0144] Although the embodiments of the present invention are described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations all fall within the scope defined by the appended claims. The above are only specific embodiments of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art who is familiar with the technical field can easily think of various equivalent modifications or substitutions within the technical scope disclosed by the present invention, and these modifications or substitutions should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

[0145] The above are only specific embodiments of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed by the present invention, and these modifications or replacements should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention shall be based on the protection scope of the claims.

Claims

1. A method for controlling version upgrade and rollback, characterized in that: include: The server saves all client version installation files; The client checks whether there is a version upgrade. If the check result shows that there is a version upgrade and the user confirms the version upgrade instruction, the client notifies the independent upgrade rollback detection program of the version upgrade instruction and the download address of the new version program file; The independent upgrade rollback detection program receives the version upgrade instruction, downloads the new version program file from the new version program file download address, and compresses and backs up the old version program file; Create a new version relationship mapping record table, and record the new version program file information and the old version program file information in the version relationship mapping record table; Unzip the new version program file, overwrite the old version program file, and complete the version upgrade; Upon receiving the user's confirmation of the version rollback instruction, the independent upgrade rollback detection program receives the version rollback instruction and reads the version relationship mapping record table to confirm whether there is an old version of the program file information; If the confirmation result shows that the old version of the program file information exists, the old version of the program file path in the old version of the program file information is read; Read the path of the old version program file to determine whether there is a compressed backup file of the old version program file; If the judgment result is that there is a compressed backup file of the old version of the program file, the old version of the program file is decompressed and overwritten with the new version of the program file to complete the version rollback.

2. A method for controlling version upgrade and rollback according to claim 1, characterized in that: The new version program file information includes the version number, version serial number, and whether to force an upgrade, and the old version program file information includes the version number, version serial number, whether to force an upgrade, and the file path.

3. A method for controlling version upgrade and rollback according to claim 1, characterized in that: Before the client checks whether there is a version upgrade, the following steps are also included: Receive the user's operation of starting the client, start the client and the independent upgrade rollback detection program process.

4. A method for controlling version upgrade and rollback according to claim 1, characterized in that: The step of notifying the independent upgrade rollback detection program of the version upgrade instruction and the download address of the new version program file includes: The version upgrade instruction and the download address of the new version program file are notified to the independent upgrade rollback detection program through inter-process communication.

5. A method for controlling version upgrade and rollback according to claim 1, characterized in that: The method further comprises: Read the path of the old version program file to determine whether there is a compressed backup file of the old version program file; If the result of the judgment is that there is no compressed backup file of the old version of the program file, the independent upgrade rollback detection program downloads the old version of the program file from the server according to the version number and version sequence number of the old version of the program file information; Update the path of the old version program file in the version mapping relationship record table; Unzip the old version program files, overwrite the new version program files, and complete the version rollback.

6. A method for controlling version upgrade and rollback according to claim 1, characterized in that: After the independent upgrade rollback detection program receives the version rollback instruction, it also includes: The version number and version serial number of the current new version are consistent with the new version number and new version serial number recorded in the version relationship mapping record table; If the matching result is that the version number and version serial number of the current new version are consistent with the new version number and new version serial number recorded in the version relationship mapping record table, the version relationship mapping record table is read to confirm whether there is old version program file information.

7. A method for controlling version upgrade and rollback according to claim 1, characterized in that: The method further comprises: Read the version relationship mapping record table to confirm whether there is old version program file information; If the confirmation result is that there is no old version program file information, it will prompt that there is no old version information and cannot be rolled back.

8. A device for controlling version upgrade and rollback, characterized in that: include: Save module: used by the server to save all client version installation files; Check module: used by the client to check whether there is a version upgrade. If the check result is that there is a version upgrade and the user confirms the version upgrade instruction, the version upgrade instruction and the download address of the new version program file are notified to the independent upgrade rollback detection program; Receiving module: used for independently upgrading the rollback detection program, receiving the version upgrade instruction, downloading the new version program file from the new version program file download address, and compressing and backing up the old version program file; New module: used to create a new version relationship mapping record table, in which the new version program file information and the old version program file information are recorded; Upgrade module: used to decompress the new version program files, overwrite the old version program files, and complete the version upgrade; Reading module: used for receiving the operation of the user confirming the version rollback instruction, the independent upgrade rollback detection program receives the version rollback instruction, reads the version relationship mapping record table to confirm whether there is the old version program file information; Confirmation module: used for reading the path of the old version of the program file in the old version of the program file information if the confirmation result is that the old version of the program file information exists; Judgment module: used to read the path of the old version program file to determine whether there is a compressed backup file of the old version program file; Rollback module: if the judgment result is that there is a compressed backup file of the old version of the program file, it is used to decompress the old version of the program file, overwrite the new version of the program file, and complete the version rollback.

9. An electronic device, characterized in that: include: Processor and memory; The processor is used to execute the method for controlling version upgrade and rollback as described in any one of claims 1 to 7 by calling the program or instruction stored in the memory.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a program or instruction, and the program or instruction enables a computer to execute a method for controlling version upgrade and rollback as described in any one of claims 1 to 7.

Images