Method and device for continuous upgrading

Abstract

An embodiment of the invention provides a method and device for continuous upgrading, and relates to the field of software upgrading. The method and device for continuous upgrading are used for solving the problem that due to modification of a recovery partition of a middle software version, follow-up continuous upgrading fails. The method comprises the steps that whether the current version of software is a target version or not is judged; if not, a same difference upgrade package of a former version and the current version is searched for in all difference upgrade packages needed by software upgrading from the current version to the target version, wherein any one difference upgrade package only comprises upgrading information of two adjacent versions; a patch package in the searched difference upgrade package is sent to a system partition of the current version; whether a recovery partition of the current version needs to be upgraded or not is detected; if yes, the recovery partition of the current version is restarted, the upgraded system partition is mounted, a patch package in the upgraded system partition is sent to the recovery partition, and therefore upgrading of the recovery partition of the current version is achieved.

Description

technical field [0001] The invention relates to the field of software upgrading, in particular to a continuous upgrading method and device. Background technique [0002] The current software version upgrade generally realizes the upgrade of the client software version by downloading the differential upgrade package provided by the server and targeting the current software version of the client, and updating the differential upgrade package to the current software version by patching. [0003] In order to upgrade the current version to the target version at one time, one implementation method currently adopted is: configure the differential upgrade package from each version to the target version on the server side, for example, if the current target version is upgraded from V4 to V5, then on the server side On the basis of the existing V2-V1, V3-V1, V3-V2, V4-V1, V4-V2, V4-V3 differential upgrade package, add the configuration of V5-V1, V5-V2, V5-V3, V5-V4 Four differential ...

AI Technical Summary

Problems solved by technology

However, if the recovery partition is modified in the V4-V3 differential upgrade package, and this modification affects the upgrade of V5-V4, from the above description, we can know that the upgrade modification of the recovery partition can only be started after upgrading to the target version. When the main system is booting, the patch file in the system is put into the recovery partition to upgrade the recovery partition. That is to say, the recovery partition is not upgraded during the V4-V3 upgrade process. Therefore, this In this case, the V5-V4 differential upgrade package will fail to upgrade

[0005] To sum up, in the existing continuous upgrade method, if the recovery partition of an intermediate version is modified during the process of upgrading the current version to the target version, and this modification affects the upgrade of the next differential upgrade package, after the modification The recovery partition cannot be brought into the upgrade of the next differential upgrade package, resulting in the failure of the subsequent upgrade process, which eventually leads to continuous upgrade failures

Images