CN115543403A - System upgrading method and device - Google Patents
System upgrading method and device Download PDFInfo
- Publication number
- CN115543403A CN115543403A CN202211508272.3A CN202211508272A CN115543403A CN 115543403 A CN115543403 A CN 115543403A CN 202211508272 A CN202211508272 A CN 202211508272A CN 115543403 A CN115543403 A CN 115543403A
- Authority
- CN
- China
- Prior art keywords
- version
- patch
- upgrade
- upgrading
- determining
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/658—Incremental updates; Differential updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Abstract
The application discloses a system upgrading method and a system upgrading device, which can determine a system upgrading version through a version management rule; then, determining a target patch according to the system upgrading version; then, if the target patch is downloaded, determining a downloading step of the target patch through a flow management rule, and judging whether the downloading is interrupted or not according to the downloading step; then, if the downloading is interrupted, determining a patch version method table through a data management rule; and then, determining an operation version after the interruption is downloaded according to the patch code and a patch version method table, wherein the patch version method table comprises the corresponding relation between the patch version before the upgrading and the patch version after the upgrading interruption.
Description
Technical Field
The present application relates to the field of device system upgrading technologies, and in particular, to a method and an apparatus for upgrading a system.
Background
The upgrading of the equipment system refers to the improvement of the performance of the equipment system or the enrichment of functions through software. The upgrading time of most equipment systems is relatively long, and when some systems are upgraded, the operation of the whole equipment is occupied, and the equipment needs to wait for the completion of the system upgrading. However, in the long-time equipment system upgrading process, the equipment is urgently needed for some reasons, and the system upgrading has to be interrupted.
In the prior art, after system upgrade is interrupted, the successfully upgraded part cannot be operated, and the whole system can be used after being completely upgraded.
Disclosure of Invention
In order to solve the defects of the prior art, the application provides a system upgrading method, after the downloading of a target patch is interrupted, a patch version method table is determined through the data management rules, the running version after the downloading is interrupted is determined according to the patch version method table, and the patch version method table comprises the corresponding relation between the patch version before the upgrading and the patch version after the upgrading is interrupted, so that the part which is upgraded successfully can run.
The technical effect that this application will reach is realized through following scheme:
the application provides a system upgrading method, which is used for equipment system upgrading, the system is established with version management rules, process management rules and data management rules, and the method comprises the following steps:
determining a system upgrading version according to the version management rule;
determining a target patch according to the system upgrading version;
if the target patch is downloaded, determining a downloading step of the target patch through the process management rule, and judging whether the downloading is interrupted according to the downloading step;
if the downloading is interrupted, determining a patch version method table through the data management rule;
determining an operation version after downloading interruption according to the patch version method table;
the patch version method table comprises the corresponding relation between the patch version before upgrading and the patch version after upgrading interruption.
Optionally, the patch includes a Java patch and a local patch, and correspondingly, the patch version includes a Java patch version and a local patch version; the version management rule includes: the version number comprises a first byte and a second byte, the first byte comprises a first sub byte and a second sub byte, upgrading is completed by marking the version with the first sub byte, the Java patch version is marked by the second sub byte, and the local patch version is marked by the second byte.
Optionally, in the version management rule, the system upgrade version includes a base version, a base patch version, and a delta patch version;
the basic version is a chip mask version without patches;
the basic patch version is a version downloaded with a patch on the basis of the basic version;
the delta patch version is a version of a re-downloaded patch on the basis of the base patch version.
Optionally, the determining a system upgrade version according to the version management rule includes:
and determining the system upgrading version according to the existing system version in the equipment system.
Optionally, the determining the system upgrade version according to the existing system version in the device system includes:
if the existing system version is the basic version, the system upgrading version is the basic patch version;
and if the existing system version is the basic patch version, the system upgrading version is the incremental patch version.
Optionally, the determining the system upgrade version according to the existing system version in the device system further includes:
if the downloaded patch is detected on the basis of the basic version, taking the version of the downloaded patch as the basic patch version, and taking the subsequently downloaded patch as a delta patch for downloading;
when the downloading time consumption of the basic patch version is equal to or greater than a first time threshold, downloading the patch which exceeds the first time threshold as the incremental patch;
and when the time consumption for downloading the incremental patch is equal to or equal to a second time threshold, taking the existing incremental patch and the basic patch version as new basic patch versions, and taking the patch exceeding the second time threshold as a new incremental patch for downloading.
Optionally, the determining a target patch according to the system upgrade version includes:
acquiring the existing system version and the system upgrading version of the equipment system;
and determining the target patch according to the existing system version and the system upgrading version.
Optionally, the determining, according to the patch version method table, an operation version after the download interruption includes:
comparing the patch version before upgrading with the patch version after upgrading interruption;
if the patch version before the upgrade is different from the patch version after the upgrade break, and the Java patch version and the local patch version in the patch version after the upgrade break are the same, the running version is the patch version after the upgrade break;
if the patch version before the upgrade is different from the patch version after the upgrade is interrupted, and the Java patch version and the local patch version in the patch version after the upgrade is interrupted are different, the running version is the basic version before the upgrade;
if the patch version before the upgrade is the same as the patch version after the upgrade is interrupted, the running version is the basic version before the upgrade.
The present application further provides a system upgrade apparatus, including:
the first determining unit determines the system upgrading version through the version management rule;
the second determining unit is used for determining a target patch according to the system upgrading version;
the judging unit is used for determining the downloading step of the target patch through a flow management rule if the target patch is downloaded, and judging whether the downloading is interrupted or not according to the downloading step;
a third determining unit, determining a patch version method table through the data management rule if the downloading is interrupted;
and the fourth determining unit determines the running version after the downloading interruption according to the patch version method table.
The present application also proposes a readable medium comprising executable instructions, which when executed by a processor of an electronic device, perform the method according to any one of the above.
The present application further proposes an electronic device, which includes a processor and a memory storing execution instructions, and when the processor executes the execution instructions stored in the memory, the processor executes the method according to any one of the above descriptions.
The application has the following advantages:
the system upgrading method is used for equipment system upgrading, and the equipment system is provided with version management rules, flow management rules and data management rules. The system upgrading method can determine the system upgrading version through the version management rule; then, determining a target patch according to the system upgrading version; then, if the target patch is downloaded, determining a downloading step of the target patch through the process management rule, and judging whether the downloading is interrupted or not according to the downloading step; then, if the downloading is interrupted, determining a patch version method table according to the data management rule; and then, determining the running version after the download interruption according to the patch version method table, wherein the patch version method table comprises the corresponding relation between the patch version before the upgrade and the patch version after the upgrade interruption. According to the method and the device, after the downloading of the target patch is interrupted, the patch version method table is determined through the data management rules, the running version after the downloading is interrupted is determined according to the patch version method table, and the patch version method table comprises the corresponding relation between the patch version before the upgrading and the patch version after the upgrading is interrupted, so that the part which is upgraded successfully can run.
Drawings
In order to more clearly illustrate the embodiments or prior art solutions of the present application, the drawings used in the description of the embodiments or prior art will be briefly described below, it is obvious that the drawings in the description below are only some embodiments described in the present application, and that other drawings can be obtained by those skilled in the art without inventive labor.
Fig. 1 is a schematic flowchart of a system upgrading method according to an embodiment of the present application;
fig. 2 is a schematic diagram of an upgrade process according to an embodiment of the present application;
FIG. 3 is a table of a method of the patch version in one embodiment of the present application;
fig. 4 is a schematic diagram of a change flow of the local patch method in an embodiment of the present application;
FIG. 5 is a schematic structural diagram of the system upgrading apparatus according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following embodiments and accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The upgrading of the equipment system is a main way for improving the performance of the equipment or enriching the functions, but the upgrading of the equipment system needs more time, after the upgrading of the system is interrupted, the part which is successfully upgraded cannot run, and the whole system can be used after the whole system is completely upgraded. In order to solve the technical problem, the application provides a system upgrading method.
Fig. 1 shows a process of a system upgrading method in an embodiment of the present application, which is used for upgrading a device system, where the device includes a mobile phone, a computer, a television, a watch, and other terminal devices, and the following device takes the mobile phone as an example, and the mobile phone is provided with an NFC SE (Near Field Communication Secure Element). When the user uses the mobile phone, after the upgrade is interrupted, the mobile phone system can run the successfully upgraded part, namely, the successfully downloaded patch, so that the mobile phone does not need to wait for all the upgraded parts to be used. As can be seen from fig. 1, the system upgrade method includes step 01, step 02, step 03, step 04, and step 05.
The equipment system is provided with version management rules, process management rules and data management rules, specifically, the version management rules comprise setting rules of equipment system version numbers, and the system version numbers are defined by numbers, characters and letters, so that the system versions can be conveniently identified. The process management rule comprises a process of system upgrading, whether the system upgrading is completed or not can be judged according to the process, if the system upgrading is completed, all the processes are completed by the system upgrading, and if the system upgrading is interrupted, only a part of the processes are completed by the system upgrading. The system upgrade downloads the running code, and the data management rule marks the code so as to identify the system version to which the code belongs, thereby facilitating the management of the code and the running of the code and ensuring the running of the system.
Step 01: and determining the system upgrading version according to the version management rule.
The version management rules can determine the system version number of each system upgrade, and the system upgrade version can be determined according to the system version number. In an example, the system version in the mobile phone is updated to the latest version, so that the version upgrade is not needed. If the system in the mobile phone is an old version, the system of the mobile phone needs to be upgraded to the latest system version. In another example, if the system version of the mobile phone has already been upgraded initially and further system upgrade needs to be completed, the upgrade that the system version of the mobile phone has already been upgraded needs to be identified, that is, the patch that has been downloaded to the mobile phone system needs to be identified, and then the patch that needs to be downloaded continuously can be determined.
In an embodiment, the patch (patch) comprises a Java patch and a Native (Native) patch, and accordingly, the patch version comprises a Java patch version and a Native patch version; the version management rule includes: the version number comprises a first byte and a second byte, the first byte comprises a first sub byte and a second sub byte, upgrading is completed by marking the version with the first sub byte, the Java patch version is marked by the second sub byte, and the local patch version is marked by the second byte. At one endIn an example, the version number of the entire patch is X 1 .X 2 X 3 .X 4 X 5 The first byte is X 1 .X 2 X 3 X1 is the first sub-byte, and may be 0 or 1,0 represents the version number before the system upgrade, 1 represents the version number after the system upgrade is performed, and also represents the completion of the version upgrade. X 2 X 3 A second sub-byte is indicated for marking the Java patch version. X 4 X 5 Representing a second byte used to mark the local patch version. For example, 0.jp1.Np1 indicates an incomplete system upgrade version, i.e., an interrupted system upgrade version, and marks the Java patch version as JP1 and the local patch version as NP 1.JP1.NP1 shows that the system upgrade version is successful, the Java patch version is marked as JP1, and the local patch version is NP1.
In order to facilitate management of the system upgrade version, in the version management rule, the system upgrade version comprises a basic version, a basic patch version and an incremental patch version; the basic version is a chip mask version without patches; the basic patch version is a version downloaded on the basis of the basic version; the delta patch version is a version of the patch downloaded on the basis of the basic patch version.
In an embodiment, step 01 includes step 11, where step 11 is to determine the system upgrade version according to an existing system version in the equipment system, that is, to determine the system upgrade version according to the version management rule, and may determine the system upgrade version according to the existing system version in the equipment system.
Specifically, step 11 includes step 111, and step 112.
Step 111: if the existing system version is the basic version, the system upgrading version is the basic patch version;
step 112: and if the existing system version is the basic patch version, the system upgrading version is the increment patch version.
The system upgrading version is the basic patch version, so that in the upgrading process, only the version needing to be upgraded of the basic patch version can be upgraded, repeated parts exist between the basic patch version and the content needing to be upgraded, the repeated parts are not upgraded, only different parts are upgraded, the system upgrading version is the incremental patch version, the different parts are used as incremental patches, all patches do not need to be downloaded, and the time for upgrading the system can be saved.
In an embodiment, the determining the system upgrade version according to the existing system version in the device system further includes:
and if the downloaded patch is detected on the basis of the basic version, taking the version of the downloaded patch as the basic patch version, and taking the subsequently downloaded patch as the incremental patch for downloading. By the arrangement, the system can be upgraded in a plurality of times, and the system can be interrupted and the single system upgrading time can be shortened.
And when the downloading time consumption of the basic patch version is equal to or greater than a first time threshold, downloading the patch exceeding the first time threshold as the incremental patch. Similarly, in order to limit the upgrading time to a more appropriate time, a first time threshold is set, and the part of the basic patch version, which takes more time than the first time threshold, is downloaded as the incremental patch.
And when the time consumption for downloading the incremental patch is equal to or equal to a second time threshold, taking the existing incremental patch and the basic patch version as new basic patch versions, and taking the patch exceeding the second time threshold as a new incremental patch for downloading. And when the system has more upgraded patches and the downloading time of the incremental patches is also very long, setting a second time threshold value, and taking the part of the incremental patches, which takes more time to download than the second time threshold value, as new incremental patches. The first time threshold and the second time threshold may be equal or unequal, and are specifically set according to actual situations. Multiple thresholds may be set, with the portion of the delta patch that exceeds the threshold being a new delta patch, and then the portion of the new delta patch that exceeds the threshold being used as yet another new delta patch.
Step 02: and determining a target patch according to the system upgrading version.
It can be known from the system upgrade version that the upgraded patch is specific, so that the patch is downloaded, and all codes or patches in all system upgrade versions do not need to be downloaded.
Specifically, step 02 includes step 21, and step 22.
Step 21: acquiring the existing system version and the system upgrading version of the equipment system;
step 22: and determining the target patch according to the existing system version and the system upgrading version.
In one example, the existing system version is a base version, then the system upgrade version is a base patch version, and the target patch is a base patch. In another example, the existing system version is a base patch version, then the system upgrade version is a delta patch version and the target patch is a delta patch. The system version can be upgraded only by downloading the target patch, the patch can be downloaded for multiple times, the single downloading time is short, and the upgrading of the equipment system is not sensed when a user uses the equipment, namely the user does not feel the upgrading of the system when using the equipment and does not interfere the user in using the equipment.
Step 03: and if the target patch is downloaded, determining the downloading step of the target patch through the process management rule, and judging whether the downloading is interrupted according to the downloading step.
Specifically, the process management rule includes an upgrade process, as shown in fig. 2, in the upgrade process, it is first determined whether the current system version is the same as the system upgrade version; if not, starting patch upgrade. For example, the current system version is 1.JPn.NPn, the system upgrade version is 1.JPn +1.NPn + 1, and the upgraded Java patch and/or local patch are determined. And writing the mapping relation of the Java patch and/or the mapping relation of the local patch, enabling the Java patch and/or the local patch, and setting a version number. For example, the version number is set to base patch version 0.jp1.Np1. Downloading a local patch of an upgrade version number, for example, downloading a local patch of a version NPn + 1, deleting a local patch of a current version number, for example, deleting a local patch of a version NPn, enabling the local patch of the version NPn + 1, and setting the version number to be 0.JP1.NPn + 1. Similarly, the Java patch of the version JPn is deleted, the Java patch of the version JPn +1 is downloaded, the Java patch of the version JPn +1 is enabled, and the version number is set to be 0.JPn +1.NPn + 1. And ending the patch upgrade, and setting the system version number to 1.JPn +1.NPn + 1. If the version number is 0.JP1.NP1, 0.JP1.NPn +1 or 0.JPn +1.NPn + 1, it represents that the downloading of the target patch is interrupted.
Step 04: and if the downloading is interrupted, determining a patch version method table according to the data management rule.
Step 05: and determining the running version after the downloading interruption according to the patch version method table.
The patch version method table comprises the corresponding relation between the patch version before upgrading and the patch version after upgrading interruption. As shown in fig. 3, the version of the patch before upgrade is 1.jpn. Npn, the version of the patch returns to the base version 1.jp1.Np1, and the version of the upgrade target is 1.jpn +1.npn +1, but the version after the upgrade is interrupted is 0.jp1.Npn + 1, and the version after the upgrade is 0.jp1.Npn + 1 is obviously not completely downloaded, and the version numbers of the Java patch and the local patch are different, then the running version is determined to be the base version before upgrade.
Specifically, step 05: the determining the running version after the downloading interruption according to the patch version method table comprises the following steps:
step 51: and comparing the patch version before upgrading with the patch version after upgrading interruption.
Step 52: if the patch version before upgrade is different from the patch version after upgrade and the Java patch version after upgrade and the local patch version after upgrade and break are the same, for example, the patch version before upgrade is 1.jpn.npn, the patch version returns to the basic version 1.jp1.np1, the upgrade target version is 1.jpn +1.npn +1, and the patch version after upgrade is 0.jpn +1.npn +1, which indicates that all the downloads are completed, then the running version is the patch version after upgrade and break 1.jpn +1.npn +1.
Step 53: if the patch version before upgrade is different from the patch version after upgrade and the Java patch version in the patch version after upgrade and the local patch version are different, for example, the patch version before upgrade is 1.jpn. NPn, the patch version returns to the basic version 1.jp1.Np1, the upgrade target version is 1.jpn +1.npn +1, and the patch version after upgrade is 0.jp1.NPn + 1, the running version is 1.jp1.Np1 before upgrade, and the returned version is the local version of NPn + 1.
Step 54: if the patch version before the upgrade is the same as the patch version after the upgrade break, for example, the patch version before the upgrade is 1.JP1.NP1, which is already a basic version, and the patch version after the upgrade break is 0.JP1.NP1, the running version is 1.JP1.NP1 of the basic version before the upgrade. For example, the patch version before upgrade is 1.JPn.NPn, the patch version returns to the basic version 1.JP1.NP1, the upgrade target version is 1.JPn +1.NPn + 1, and the patch version after upgrade is 0.JPn.NPn, then the running version is 1.JP1.NP1 of the basic version before upgrade, or 1.JPn.NPn of the patch version before upgrade.
The data management rule also comprises a local patching method changing flow, the local patching method changing flow is shown in figure 4, and when the equipment system is in a basic version, a current using method pointer is a basic version method table and a basic version method code; when the basic patch is downloaded and made to take effect, the current using method pointer is the basic patch method table and the basic patch method code; when the increment patch is downloaded and made to take effect, the current using method pointer is an increment patch method table and an increment patch method code; when the existing delta patch and the base patch version are merged to be used as a new base patch version, the currently used method pointers are a new base patch method table and a new base patch method code.
Referring to fig. 5, a schematic structural diagram of a system upgrading apparatus in an embodiment of the present application is shown, and as can be seen from fig. 5, the system upgrading apparatus includes:
the first determining unit is used for determining the system upgrading version through the version management rule;
the second determining unit determines a target patch according to the system upgrading version;
the judging unit is used for determining the downloading step of the target patch through a flow management rule if the target patch is downloaded, and judging whether the downloading is interrupted or not according to the downloading step;
a third determining unit, determining a patch version method table through the data management rule if the downloading is interrupted;
and the fourth determining unit determines the running version after the downloading interruption according to the patch version method table.
Optionally, the first determining unit is configured to:
and determining the system upgrading version according to the existing system version in the equipment system.
Specifically, the first determining unit is configured to:
if the existing system version is the basic version, the system upgrade version is the basic patch version;
and if the existing system version is the basic patch version, the system upgrading version is the increment patch version.
Optionally, the first determining unit is configured to:
if the downloaded patch is detected on the basis of the basic version, taking the version of the downloaded patch as the basic patch version, and taking the subsequently downloaded patch as a delta patch for downloading;
when the downloading time consumption of the basic patch version is equal to or greater than a first time threshold, downloading the patch which exceeds the first time threshold as the incremental patch;
and when the time consumption for downloading the incremental patch is equal to or equal to a second time threshold, taking the existing incremental patch and the basic patch version as new basic patch versions, and taking the patch exceeding the second time threshold as a new incremental patch for downloading.
Optionally, the second determining unit is configured to:
acquiring the existing system version and the system upgrading version of the equipment system;
and determining the target patch according to the existing system version and the system upgrading version.
Optionally, the fourth determining unit is configured to:
comparing the patch version before upgrading with the patch version after upgrading interruption;
if the patch version before the upgrade is different from the patch version after the upgrade break, and the Java patch version and the local patch version in the patch version after the upgrade break are the same, the running version is the patch version after the upgrade break;
if the patch version before the upgrade is different from the patch version after the upgrade interruption, and the Java patch version and the local patch version in the patch version after the upgrade interruption are different, the running version is the basic version before the upgrade;
and if the patch version before the upgrade is the same as the patch version after the upgrade is interrupted, the running version is the basic version before the upgrade.
Fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application. On the hardware level, the electronic device comprises a processor and optionally an internal bus, a network interface and a memory. The Memory may include a Memory, such as a Random-Access Memory (RAM), and may further include a non-volatile Memory, such as at least 1 disk Memory. Of course, the electronic device may also include hardware required for other services.
The processor, the network interface, and the memory may be connected to each other via an internal bus, which may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, an EISA (Extended Industry Standard Architecture) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one double-headed arrow is shown in FIG. 6, but that does not indicate only one bus or one type of bus.
And the memory is used for storing the execution instruction. In particular, a computer program that can be executed by executing instructions. The memory may include both memory and non-volatile storage and provides execution instructions and data to the processor.
In a possible implementation manner, the processor reads the corresponding execution instruction from the nonvolatile memory to the memory and then runs the corresponding execution instruction, and may also obtain the corresponding execution instruction from other devices, so as to form the system upgrade method on a logic level. The processor executes the execution instructions stored in the memory, so that the system upgrading method provided by any embodiment of the application is realized through the executed execution instructions.
The method executed by the system upgrading method provided by the embodiment shown in fig. 1 of the present application may be applied to a processor, or may be implemented by a processor. The processor may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also Digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and combines hardware thereof to complete the steps of the method.
The embodiment of the present application further provides a readable medium, where the readable storage medium stores an execution instruction, and when the stored execution instruction is executed by a processor of an electronic device, the electronic device can execute the system upgrade method provided in any embodiment of the present application, and is specifically configured to execute the system upgrade method.
The electronic device described in the foregoing embodiments may be a computer.
It will be apparent to those skilled in the art that embodiments of the present application may be provided as a method or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects.
The embodiments in the present application are described in a progressive manner, and the same and similar parts among the embodiments can be referred to each other, and each embodiment focuses on differences from other embodiments. In particular, as for the apparatus embodiment, since it is substantially similar to the method embodiment, the description is relatively simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising one of 8230; \8230;" 8230; "does not exclude the presence of additional like elements in a process, method, article, or apparatus that comprises that element.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement or the like made within the spirit and principle of the present application shall be included in the scope of the claims of the present application.
Claims (11)
1. A system upgrading method is used for equipment system upgrading, and is characterized in that the equipment system is provided with version management rules, process management rules and data management rules, and the method comprises the following steps:
determining a system upgrading version according to the version management rule;
determining a target patch according to the system upgrading version;
if the target patch is downloaded, determining a downloading step of the target patch through the process management rule, and judging whether the downloading is interrupted according to the downloading step;
if the downloading is interrupted, determining a patch version method table through the data management rule;
determining an operation version after downloading interruption according to the patch version method table;
the patch version method table comprises the corresponding relation between the patch version before upgrading and the patch version after upgrading interruption.
2. The system upgrade method according to claim 1, wherein the patch comprises a Java patch and a local patch, and accordingly, the patch version comprises a Java patch version and a local patch version; the version management rule comprises: the version number comprises a first byte and a second byte, the first byte comprises a first sub byte and a second sub byte, upgrading is completed by marking the version with the first sub byte, the Java patch version is marked by the second sub byte, and the local patch version is marked by the second byte.
3. The system upgrade method according to claim 1, wherein in the version management rule, the system upgrade version includes a base version, a base patch version, and a delta patch version;
the basic version is a chip mask version without patches;
the basic patch version is a version downloaded on the basis of the basic version;
the delta patch version is a version of the patch downloaded on the basis of the basic patch version.
4. The system upgrade method according to claim 3, wherein said determining a system upgrade version by said version management rules comprises:
and determining the system upgrading version according to the existing system version in the equipment system.
5. The system upgrade method according to claim 4, wherein said determining the system upgrade version based on an existing system version in the equipment system comprises:
if the existing system version is the basic version, the system upgrade version is the basic patch version;
and if the existing system version is the basic patch version, the system upgrading version is the increment patch version.
6. The system upgrade method according to claim 5, wherein said determining the system upgrade version based on an existing system version in the device system, further comprises:
if the downloaded patch is detected on the basis of the basic version, taking the version of the downloaded patch as the basic patch version, and taking the subsequently downloaded patch as a delta patch for downloading;
when the downloading time consumption of the basic patch version is equal to or greater than a first time threshold, downloading the patch which exceeds the first time threshold as the incremental patch;
and when the time consumption for downloading the incremental patch is equal to or equal to a second time threshold, taking the existing incremental patch and the basic patch version as new basic patch versions, and taking the patch exceeding the second time threshold as a new incremental patch for downloading.
7. The system upgrade method according to claim 1, wherein said determining a target patch from the system upgrade version comprises:
acquiring the existing system version and the system upgrading version of the equipment system;
and determining the target patch according to the existing system version and the system upgrading version.
8. The system upgrade method according to claim 2, wherein said determining a running version after download interruption from said patch version method table comprises:
comparing the patch version before upgrading with the patch version after upgrading interruption;
if the patch version before the upgrade is different from the patch version after the upgrade is interrupted, and the Java patch version and the local patch version in the patch version after the upgrade is interrupted are the same, the running version is the patch version after the upgrade is interrupted;
if the patch version before the upgrade is different from the patch version after the upgrade interruption, and the Java patch version and the local patch version in the patch version after the upgrade interruption are different, the running version is the basic version before the upgrade;
and if the patch version before the upgrade is the same as the patch version after the upgrade is interrupted, the running version is the basic version before the upgrade.
9. A system upgrade apparatus, comprising:
the first determining unit is used for determining the system upgrading version through the version management rule;
the second determining unit is used for determining a target patch according to the system upgrading version;
the judging unit is used for determining the downloading step of the target patch through a flow management rule if the target patch is downloaded, and judging whether the downloading is interrupted or not according to the downloading step;
a third determining unit, determining a patch version method table through the data management rule if the downloading is interrupted;
and the fourth determining unit determines the running version after the downloading interruption according to the patch version method table.
10. A computer-readable storage medium storing a computer program for executing the system upgrade method of any one of claims 1 to 8.
11. An electronic device, the electronic device comprising:
a processor;
a memory for storing the processor-executable instructions;
the processor is used for reading the executable instruction from the memory and executing the instruction to realize the system upgrading method of any one of the claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211508272.3A CN115543403B (en) | 2022-11-29 | 2022-11-29 | System upgrading method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211508272.3A CN115543403B (en) | 2022-11-29 | 2022-11-29 | System upgrading method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115543403A true CN115543403A (en) | 2022-12-30 |
| CN115543403B CN115543403B (en) | 2023-03-21 |
Family
ID=84721802
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211508272.3A Active CN115543403B (en) | 2022-11-29 | 2022-11-29 | System upgrading method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115543403B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1777867A (en) * | 2003-12-15 | 2006-05-24 | 微软公司 | System and method for updating files utilizing delta compression patching. |
| US7472384B1 (en) * | 2003-12-02 | 2008-12-30 | Swsoft Holdings, Ltd. | System, method and computer program product for on-the-fly patching of executable code |
| CN101593118A (en) * | 2009-02-24 | 2009-12-02 | 浪潮集团山东通用软件有限公司 | A kind of software upgrade method flexibly |
| CN102624861A (en) * | 2011-11-28 | 2012-08-01 | 苏州奇可思信息科技有限公司 | Enterprise network-oriented operating system upgrade patch updating method |
| CN103246528A (en) * | 2012-02-10 | 2013-08-14 | 中兴通讯股份有限公司 | Software updating method and device |
| CN107861736A (en) * | 2017-11-01 | 2018-03-30 | 网易（杭州）网络有限公司 | Patch generates and update method and device, electronic equipment, storage medium |
| US20190155598A1 (en) * | 2017-11-17 | 2019-05-23 | Apple Inc. | Techniques for updating a file using a multi-version patch file |
| CN115344434A (en) * | 2022-10-19 | 2022-11-15 | 紫光同芯微电子有限公司 | Patching method and device, electronic equipment and storage medium |
-
2022
- 2022-11-29 CN CN202211508272.3A patent/CN115543403B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7472384B1 (en) * | 2003-12-02 | 2008-12-30 | Swsoft Holdings, Ltd. | System, method and computer program product for on-the-fly patching of executable code |
| CN1777867A (en) * | 2003-12-15 | 2006-05-24 | 微软公司 | System and method for updating files utilizing delta compression patching. |
| CN101593118A (en) * | 2009-02-24 | 2009-12-02 | 浪潮集团山东通用软件有限公司 | A kind of software upgrade method flexibly |
| CN102624861A (en) * | 2011-11-28 | 2012-08-01 | 苏州奇可思信息科技有限公司 | Enterprise network-oriented operating system upgrade patch updating method |
| CN103246528A (en) * | 2012-02-10 | 2013-08-14 | 中兴通讯股份有限公司 | Software updating method and device |
| CN107861736A (en) * | 2017-11-01 | 2018-03-30 | 网易（杭州）网络有限公司 | Patch generates and update method and device, electronic equipment, storage medium |
| US20190155598A1 (en) * | 2017-11-17 | 2019-05-23 | Apple Inc. | Techniques for updating a file using a multi-version patch file |
| CN115344434A (en) * | 2022-10-19 | 2022-11-15 | 紫光同芯微电子有限公司 | Patching method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115543403B (en) | 2023-03-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108196878B (en) | Method and device for generating application program installation package, electronic equipment and storage medium | |
| CN109814524B (en) | Vehicle diagnosis method, device and system | |
| CN111427596B (en) | Software upgrading method and device and terminal equipment | |
| CN108874426B (en) | Application program updating method and device and readable storage medium | |
| CN110308880B (en) | Log printing method, system, computer device and computer readable storage medium | |
| CN108874437B (en) | Online cloud updating method for android application program | |
| CN106055375B (en) | Application program installation method and device | |
| CN106293849B (en) | application updating method and terminal | |
| CN115017058B (en) | Test method and device of kernel module, electronic equipment and storage medium | |
| CN111881150A (en) | Web application program offline data processing method and device | |
| CN109032612B (en) | Interface calling method and device of hybrid application and computer readable storage medium | |
| CN115543403B (en) | System upgrading method and device | |
| CN111399849B (en) | Method and system for determining application program installation package | |
| CN106569865B (en) | Method and device for manufacturing system upgrade file of terminal | |
| CN110764809A (en) | OTA APN upgrading method, device, equipment and medium | |
| CN111400091A (en) | Factory setting restoring method, factory setting restoring device and mobile terminal | |
| CN113535206A (en) | Multi-version code upgrading method and system | |
| CN112328288A (en) | Method, system, equipment and storage medium for updating server component | |
| CN111563038A (en) | SDK test method, device, computer equipment and computer readable storage medium | |
| CN111142913A (en) | Hot updating method and equipment for iOS system application program | |
| CN108829574B (en) | Test data laying method, test server and computer readable storage medium | |
| CN112822248A (en) | OTA upgrading method, OTA upgrading device, readable medium and electronic equipment | |
| CN113709195A (en) | Vehicle software upgrading method, device and system | |
| CN111427603A (en) | Application program upgrading method and device | |
| CN110928753A (en) | Method and device for controlling log output of browser console, computer equipment and computer readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |