WO2017016282A1 - Software upgrading method and apparatus, and computer storage medium - Google Patents

Abstract

A software upgrading method and apparatus, and a computer storage medium. The method comprises: receiving an upgrade package (S110), wherein the upgrade package comprises M upgrade files in total, M being an integer not less than 2; and when software upgrading cannot be performed based on the M upgrade files, performing software upgrading based on N of the upgrade files which have passed the file correctness verification (S120), where N is a positive integer less than M.

Description

Software upgrade method and device, computer storage medium Technical field

The present invention relates to the field of information processing, and in particular, to a software upgrade method and apparatus, and a computer storage medium.

Background technique

With the development of information technology and the widespread application of electronic devices, applications in electronic devices will improve and enhance the functions of applications by upgrading and upgrading applications frequently, and improving application intelligence and user satisfaction. However, during the application upgrade process, it is often found that the upgrade package does not match the current device version, resulting in an upgrade failure, and the upgrade failure rate is high. If the coverage upgrade is used, many user data will be lost, which will affect the user's use after the upgrade. Therefore, how to improve the upgrade success rate is an urgent problem to be solved in the prior art.

Summary of the invention

To solve the above technical problem, an embodiment of the present invention provides a software upgrade method and device, and a computer storage medium, which at least alleviate the problem of high software upgrade failure rate.

A first aspect of the embodiments of the present invention provides a software upgrade method, where the method includes:

Receiving an upgrade package, where the upgrade package includes a total of M upgrade files; the M is an integer not less than 2;

When the software upgrade cannot be performed based on the M upgrade files, the software upgrade is performed based on the N upgrade files verified by the file correctness;

Wherein, the N is a positive integer smaller than the M.

Based on the foregoing solution, when the software upgrade cannot be performed based on the M upgrade files, the software upgrade is performed based on the upgrade files that are verified by the file correctness, including:

Determining important upgrade files for the upgrade package;

Determining the verification result of the correctness of the file of the important upgrade file;

If the verification result indicates that the important upgrade file is verified by the correctness of the file, the software is upgraded based on the N upgrade files verified by the correctness of the file; wherein the N upgrades are verified by the correctness of the file. The file includes at least all of the important upgrade files described.

Based on the foregoing solution, the determining the important upgrade file of the upgrade package includes:

Receiving a download descriptor file of the upgrade package;

The important upgrade file is determined based on the download descriptor file.

Based on the above solution, the download descriptor file includes a file name of all files of the upgrade package and an importance level corresponding to the file;

Determining the important upgrade file based on the download descriptor file, including:

Comparing the importance level to a level threshold;

Based on the result of the comparison, the important upgrade file is determined.

Based on the above solution, the download descriptor file includes a file name of the important upgrade file in the upgrade package;

The determining the important upgrade file of the upgrade package includes:

Extracting a file name of the important upgrade file in the download descriptor file to determine the important upgrade file.

Based on the foregoing solution, the method further includes:

Performing the correctness verification of the upgrade package for the upgrade package;

The verification result of determining the correctness of the file of the important upgrade file includes:

If the verification of the correctness of the upgrade package fails, the verification result of the verification of the correctness of the file of the important upgrade file is determined.

Based on the foregoing solution, the correctness of the upgrade package is verified to verify the correctness of all files in the upgrade package;

If the verification of the correctness of the upgrade package fails, the verification result of the verification of the correctness of the file of the important upgrade file is determined, including:

And obtaining, according to the verification result of the verification of the correctness of the upgrade package, the verification result of the verification of the correctness of the file of the important upgrade file.

Based on the foregoing solution, when the software upgrade cannot be performed based on the M upgrade files, the software upgrade is performed based on the upgrade files that are verified by the file correctness, including:

Determining, by the N upgrade files, the correctness of the files in the M upgrade files;

The software upgrade is performed based on the N upgrade files verified by the correctness of the file.

A second aspect of the embodiments of the present invention provides a software upgrade apparatus, where the apparatus includes:

a receiving unit, configured to receive an upgrade package, where the upgrade package includes a total of M upgrade files; the M is an integer not less than 2;

An upgrade unit configured to perform software upgrade based on the N upgrade files verified by file correctness when the software upgrade cannot be performed based on the M upgrade files;

Wherein, the N is a positive integer smaller than the M.

Based on the foregoing solution, the upgrading unit includes:

a first determining module, configured to determine an important upgrade file of the upgrade package;

a second determining module, configured to determine a verification result of the correctness of the file of the important upgrade file;

An upgrade module, configured to: if the verification result indicates that the important upgrade file is verified by the correctness of the file, upgrade software based on the N upgrade files verified by the correctness of the file; wherein the N pass file correctness The upgrade file verified includes at least all of the important upgrade files.

Based on the above solution, the first determining module is configured to receive a download descriptor file of the upgrade package; and determine the important upgrade file based on the download descriptor file.

Based on the above solution, the download descriptor file includes a file name of all files of the upgrade package and an importance level corresponding to the file;

The first determining module is further configured to compare the importance level with a level threshold; and determine the important upgrade file based on the result of the comparing.

Based on the above solution, the download descriptor file includes a file name of the important upgrade file in the upgrade package;

The first determining module is further configured to extract a file name of the important upgrade file in the download descriptor file, and determine the important upgrade file.

Based on the above solution, the device further includes:

a verification unit configured to verify the correctness of the upgrade package of the upgrade package;

The second determining module is further configured to: if the verification package correctness verification fails, determine a verification result of the file correctness verification of the important upgrade file.

Based on the foregoing solution, the correctness of the upgrade package is verified to verify the correctness of all files in the upgrade package;

The second determining module is further configured to obtain a verification result of the file correctness verification of the important upgrade file based on the verification result of the upgrade package correctness verification.

Based on the above solution, the upgrading unit is further configured to determine N the upgrade files that are verified by the correctness of the files in the M upgrade files; and based on the N upgrade files that are verified by the correctness of the files. software upgrade.

A third aspect of the embodiments of the present invention provides a computer storage medium. The computer storage medium provided by the embodiment of the present invention stores a computer program, where the computer program is used to execute the software upgrade method.

The software upgrade method and device, and the computer storage medium in the embodiment of the present invention can perform software upgrade based on the upgrade file verified by the file correctness in the upgrade package, so that the prior art can be well avoided. Document correctness verification for individual upgrade files If it fails, the entire software cannot be upgraded and the upgrade fails. This improves the software upgrade success rate. It is especially suitable for software upgrades that have only minor differences between upgrade files and client upgrade files in some upgrade packages, and do not affect the main purpose of this upgrade.

DRAWINGS

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

2 is a schematic flowchart of providing software upgrade based on N upgrade files verified by file correctness according to an embodiment of the present invention;

3 is a schematic flowchart of determining an important upgrade file according to an embodiment of the present invention;

4 is a schematic structural diagram of a software upgrading apparatus according to an embodiment of the present invention;

FIG. 5 is a second schematic flowchart of a software upgrade method according to an embodiment of the present disclosure;

FIG. 6 is a third schematic flowchart of a software upgrade method according to an embodiment of the present invention.

detailed description

In the process of using an electronic device (such as a mobile terminal such as a mobile phone, a tablet or a wearable device), if the user intentionally or unintentionally changes some configuration information of the current version of the application or software in the electronic device, or the user has flashed the device Processing, even because of some abnormality in the mass production before shipment, the version downloaded to the device does not match the part of the expected shipping version, and may be based on the firmware of the Firmware Over The Air (FOTA). When the upgrade is performed, the strict verification mechanism before the differential upgrade package is installed detects that the version of the differential upgrade package does not match the current version of the electronic device, and the upgrade fails. The differential upgrade package is one of upgrade packages. The result is that the electronic device can only choose to upgrade the full version, which may overwrite many historical user data. In particular, if the current device does not support the full version upgrade, the device will never be upgraded in the future, which seriously affects the user experience.

The present application provides a software upgrade solution. When the above upgrade failure occurs, the software upgrade is performed based on a part of the upgrade files in the software package, which is also a software upgrade, so that at least Improved partial upgrade success rate based on upgrade package. And the software upgrade method, when the differential upgrade package does not match the current device version, the user data retained by the electronic device can be saved, and the current version of the electronic device can be upgraded successfully, thereby improving the upgrade intelligence and the user. Experience.

The technical solutions of the present invention are further elaborated below in conjunction with the drawings and specific embodiments.

As shown in FIG. 1 , this embodiment provides a software upgrade method, where the method includes:

Step S110: receiving an upgrade package;

Step S120: When the software upgrade cannot be performed based on the M upgrade files, perform software upgrade based on the N upgrade files verified by file correctness;

Wherein, the N is a positive integer smaller than the M.

In this embodiment, the upgrade package may include an overall upgrade package and a differential upgrade package. The overall upgrade package may be information for the upgrade version application, and the overall upgrade and replacement of the software may be implemented according to the complete upgrade package. The differential upgrade package only includes difference information between the upgrade version and the current version, and only the partial upgrade replacement is performed when the software upgrade is performed based on the differential upgrade package. In the embodiment, the upgrade package is preferably a differential upgrade package. In step S110, the client may receive the upgrade package such as the differential upgrade package from the server side.

A software upgrade package includes a total of M upgrade files, and the probability that the M upgrade files are verified by the correctness of the files is obviously lower than the probability that only N of the M upgrade files are required to pass the correctness of the files. When the overall software upgrade cannot be performed based on all the upgrade files in the software upgrade package, the partial upgrade based on the upgrade package also implements the software upgrade, and obviously at least the partial upgrade success rate based on the upgrade package is improved.

The upgrade package includes not only the upgrade file but also the upgrade file is written in the flash area of the client. The file correctness verification in the embodiment includes: performing file verification on the partition to be upgraded, and adopting the existing verification method. , need to compress and digitally sign the upgrade package, and After the upgrade package is downloaded to the electronic device, the above-mentioned file verification is performed by decompressing and digital signature. The upgrade package here may include an OTA upgrade package, the OTA is an abbreviation of Over the Air Technology, and the corresponding Chinese is an over-the-air download technology. The OTA upgrade package is an upgrade package downloaded by using an over-the-air download technology.

It is worth noting that the document correctness verification is not limited to the above examples. In step S120, a sub-step of verifying the correctness of the file may be included. For the verification of the correctness of the file, refer to the method for verifying the correctness of the file in the existing software upgrade technology.

The N upgrade files may include at least two of the following:

The first:

The upgrade file of the upgrade package includes a normal upgrade file and an important upgrade file; the N upgrade files are N important upgrade files that are verified by the correctness of the file.

Second: N upgrade files can be all upgrade files verified by file correctness in M upgrade files.

For the first one:

As shown in FIG. 2, the step S120 may include:

Step S121: determining an important upgrade file of the upgrade package;

Step S122: determining a verification result of the correctness of the file of the important upgrade file;

Step S123: If the verification result indicates that the important upgrade file is verified by the correctness of the file, the upgrade file is upgraded based on the N correctness of the file verification; wherein the N are verified by the correctness of the file. The upgrade file includes at least all of the important upgrade files.

Usually, an upgrade package can include multiple files to be upgraded, and the upgrade importance of these files is different. The upgrade file in the upgrade package in this embodiment may include a normal upgrade file and an important upgrade file. The important upgrade file may be a file that must be upgraded in this software upgrade.

The important upgrade file of the upgrade package will be determined in step S121. The step S121 can be Important upgrade files determined based on user instructions.

In step S122, the important upgrade file in the upgrade package is verified for correctness. If the correctness verification is passed, the upgrade is performed based on at least the important upgrade file in step S123Z. Here, the N upgrade files verified by the correctness of the file include at least all the important upgrade files. It can be understood that if the important upgrade includes a total of P files, the N is not smaller than the P.

The software upgrade is performed based on at least all of the important upgrade files in step S123, and may also be performed based on all the importance upgrade files and some of the normal upgrade files. In this case, not only can the overall upgrade based on the upgrade package be performed based on each file in the upgrade package, but also the upgrade file based on the importance in the upgrade package, and the partial upgrade based on the upgrade package. In this case, when the correctness of the verification of a normal upgrade file is incorrect, the upgrade of the importance upgrade file is still performed, and the upgrade success is achieved, thereby improving the upgrade success rate.

As shown in FIG. 3, the S121 may include:

Step S1201: Receive a download descriptor file of the upgrade package.

Step S1202: Determine the important upgrade file based on the download descriptor file.

The download descriptor file may be simply referred to as a DD file. The DD is an abbreviation of Download Descriptiion. The DD file may further include information such as a file size, a download address, and the like of the upgrade package. Usually it is a file that is downloaded before the client downloads the upgrade package. In this embodiment, the importance upgrade file is obtained from the DD file, instead of the information sent from other files sent by the server, the importance file is determined, and the number of information interactions between the client and the server can be reduced. Reduce the load of information interaction while reducing the power consumption of the client.

There are various implementations of the step S1202, and two alternative methods are provided below:

method one:

The download descriptor file includes a file name of all files of the upgrade package and an importance level corresponding to the file;

The step S1202 may include:

Comparing the importance level to a level threshold;

Based on the result of the comparison, the important upgrade file is determined.

The level threshold may be a level threshold formed by the client based on the user input instruction, or may be a level threshold configured by default before the electronic device leaves the factory.

If the level threshold is higher, the importance of the corresponding upgrade file is higher. In this case, if the result of the comparison indicates that the importance level is not less than the level threshold, the importance level corresponds to the upgrade. The file is the important upgrade file. If the level threshold is lower, the importance of the corresponding upgrade file is higher. In this case, if the result of the comparison indicates that the importance level is less than the level threshold, the upgrade file corresponding to the importance level For the important upgrade file.

The importance level of the upgrade file may be determined by the server side according to the upgrade purpose of the upgrade and the upgrade function of the upgrade file.

Method 2:

The download descriptor file includes a file name of the important upgrade file in the upgrade package;

The step S1202 includes:

Extracting a file name of the important upgrade file in the download descriptor file to determine the important upgrade file.

In the first mode, the DD file includes the file name and the importance level of all the files in the upgrade package. In this embodiment, the DD file may only include the file name of the important upgrade file, so that the client directly includes the file according to the DD file. The file name determines which are important upgrade files.

It is worth noting that the first method can set the level threshold according to the user's instruction, so that the user can participate in the control to determine the important upgrade file, so that the user can control the upgrade, and the importance file of the second method is determined by the server side. , but the implementation is easier.

In a specific implementation process, the DD file may further include partition information of each upgrade file, and the partition information may be used to perform correct verification of the file.

The method in this embodiment further includes:

Performing the correctness verification of the upgrade package for the upgrade package;

The step S122 may include:

If the verification of the correctness of the upgrade package fails, the verification result of the verification of the correctness of the file of the important upgrade file is determined.

The verification of the correctness of the upgrade package here includes verification of the correctness of all the upgrade files in the upgrade package, such as the verification of the correctness of the normal upgrade file and the verification of the correctness of the important upgrade file.

In this embodiment, the software upgrade method first performs the verification of the correctness of the upgrade package, and the verification of the correctness of the upgrade package is essentially the first correctness verification. If the first correctness verification is passed, it means that all the files in the entire upgrade package have passed the correctness verification. Obviously, all the upgrade files in the upgrade package can be upgraded based on the entire upgrade package. At this time, all the upgrades in the upgrade package are directly performed. The file is upgraded by the client software. At this time, if the upgrade package includes a total of M upgrade files; M is an integer of not less than 1, the client software upgrades M files, and the upgraded files are upgrade files in the software upgrade package.

When the correct upgrade of the upgrade package fails, it means that the correctness of some upgrade files in the upgrade package cannot be passed. At this time, the verification result of the correctness verification of the file of the important upgrade file is determined. If the correctness of the file verification of the important upgrade file is passed, it indicates that the software upgrade package can be partially upgraded. In this case, if the correctness of the file verification fails, the correct verification result of the normal upgrade file fails, and it is obvious that the software upgrade of the client can still be performed, which obviously improves the upgrade success rate of the software upgrade, and also avoids the software failure under extreme conditions. The result of the upgrade.

In addition, if the verification of the correctness of the upgrade package fails, the verification result of the verification of the correctness of the file of the important upgrade file is determined, including: obtaining the important upgrade file based on the verification result of the verification of the correctness of the upgrade package. The verification result of the correctness of the file.

The verification result of the correctness verification of the file of the important upgrade file may be re-authenticated for the importance file, or the verification result of the important upgrade file may be confirmed based on the verification result of the verification of the correctness of the upgrade package. Obviously, it is determined directly based on the verification result of the verification of the correctness of the upgrade package, and the verification may be repeated to speed up the determination of efficiency.

Second:

The step S120 may include:

Determining, by the N upgrade files, the correctness of the files in the M upgrade files;

The software upgrade is performed based on the N upgrade files verified by the correctness of the file.

The embodiment of the invention provides a software upgrade method, which can perform software upgrade based on a part of the upgrade file in the upgrade package, and the partial upgrade is also an upgrade success rate, which obviously improves the upgrade success rate.

Device embodiment:

As shown in FIG. 4, this embodiment provides a software upgrade apparatus, where the apparatus includes:

The receiving unit 110 is configured to receive an upgrade package, where the upgrade package includes a total of M upgrade files; the M is an integer not less than 2;

The upgrading unit 120 is configured to perform software upgrade based on the N upgrade files verified by file correctness when the software upgrade cannot be performed based on the M upgrade files;

Wherein, the N is a positive integer smaller than the M.

The receiving unit 110 in this embodiment may include a communication interface configured to receive the upgrade package from a peripheral device such as a server. The upgrade package may be the differential upgrade package described in the foregoing method embodiment, or may be an overall upgrade package.

The specific structure of the upgrading unit 120 may include a processor or processing circuit that can be used for information processing such as software upgrade processing. The processor may include a central processing unit CPU, a microprocessor MCU, a digital signal processor DSP or a programmable array within the client Column PLC and other processors. The processing circuit can include an application specific integrated circuit ASIC or the like.

The software upgrade device in this embodiment breaks all the files in the prior art based on all the upgrade files in the upgrade package, and the present application is based on the N upgrade files in the upgrade package that are verified by the correctness of the files. Upgrade, so through partial upgrades, improve the upgrade success rate and upgrade intelligence.

As shown in FIG. 5, the upgrading unit 120 includes:

The first determining module 121 is configured to determine an important upgrade file of the upgrade package;

The second determining module 122 is configured to determine a verification result of the correctness of the file of the important upgrade file;

The upgrade module 123 is configured to: if the verification result indicates that the important upgrade file is verified by the correctness of the file, upgrade the software based on the N upgrade files verified by the correctness of the file; wherein the N pass files are correct The upgrade file of the sexual verification includes at least all of the important upgrade files.

The first determining module 121 has a plurality of structures, and may include receiving information from the peripheral device to determine the important upgrade file in the upgrade package, or may include the information parser determining the Important upgrade files.

The second determining module 122 may include a structure for performing information verification, and the comparator or the comparing circuit determines the file correctness verification of the important upgrade file in the software package by comparing and matching.

The upgrade module 123 is configured to perform software upgrade, and the specific structure may include the foregoing processor or processing circuit.

In the embodiment, when the upgrade module 123 is upgraded, the software upgrade is performed based on at least all the important upgrade files in the upgrade package. Of course, the software upgrade may be performed based on all the important upgrade files and some common upgrade files.

Further, the first determining module 121 is configured to receive a download descriptor file of the upgrade package; and determine the important upgrade file based on the download descriptor file.

The first determining module 121 may include a communication interface and a parser, where the communication interface is configured to receive the download descriptor file, and the parser is configured to parse the download descriptor file to determine an important upgrade file. In this embodiment, the DD file of the upgrade package carries information indicating the important upgrade file, which simplifies the operation of the client to determine the important upgrade file.

The download descriptor file includes a file name of all files of the upgrade package and an importance level corresponding to the file; the first determining module 121 is further configured to compare the importance level with a level threshold; and Based on the result of the comparison, the important upgrade file is determined.

In the embodiment, the DD file includes an importance level, and the first determining module 121 may include a comparator, and by comparing the importance level with the level threshold, the comparison result can be obtained, and the important upgrade file is determined based on the comparison result. Therefore, the device based on the comparison structure can realize the software upgrade based on the partial threshold of the upgrade package based on the level threshold or the system default setting indicated by the user or the level threshold dynamically determined based on the historical upgrade record.

It is to be noted that the partial upgrades implemented by the technical solution of the present invention in the embodiments of the present invention refer to software upgrades based on partial upgrade files in the upgrade package; and the overall upgrade refers to software based on all upgrade files in the upgrade package. upgrade.

The download descriptor file includes a file name of the important upgrade file in the upgrade package, and the first determining module 121 is further configured to extract a file name of the important upgrade file in the download descriptor file, and determine Out of the important upgrade file. The first determining module 121 in the solution may be different from the first determining module 121 in the previous solution. In the present solution, the first determining module 121 directly confirms the important upgrade file according to the file name recorded in the DD file. An upgrade file whose file name is recorded in the DD file can be regarded as an important upgrade file.

In a specific implementation process, the DD file may further include partition information corresponding to the upgrade file, and the partition information may be used for file correctness verification.

In addition, the device further includes: a verification unit configured to upgrade the upgrade package The second verification module 122 is further configured to determine a verification result of the file correctness verification of the important upgrade file if the verification package correctness verification fails. In this embodiment, the verification unit performs an upgrade package correctness verification on the upgrade package. The verification of the correctness of the upgrade package indicates that all the files in the upgrade package have passed the correctness of the file. Generally, the upgrade can be performed based on all the upgrade files of the upgrade package. Therefore, the upgrade module 123 is not required to perform partial upgrade. Therefore, the upgrade module 123 performs partial upgrade based on the N upgrade files verified by the correctness of the file when the verification of the correctness of the upgrade package fails.

The correctness of the upgrade package is verified to verify the correctness of all the files in the upgrade package. The second determining module 122 is further configured to obtain the important upgrade file based on the verification result of the correctness verification of the upgrade package. The verification result of the correctness of the file verification. How to determine the file correctness verification of the important upgrade file, the second determining module 122 may perform one-by-one verification according to various file correctness verification algorithms, or may be determined based on the upgrade package correctness verification result. In the embodiment, the second determining module 122 determines the verification result of each of the importance upgrade files based on the verification result of the upgrade package correctness verification, which is more convenient.

Further, the upgrading unit 120 is further configured to: determine, by the N upgrade files that are verified by the correctness of the files in the M upgrade files; and perform the N upgrade files that are verified by the correctness of the files. software upgrade. In this embodiment, the N upgrade files may be N upgrade files verified by file correctness, and it is no longer necessary to distinguish whether all the importance files are included. In this case, at least part of the software in the client can be upgraded.

In an embodiment, the software upgrade device is provided in the embodiment, and the software upgrade can be performed based on the partial upgrade file in the upgrade package, so as to prevent the upgrade package from failing to pass the correctness of the file of the upgrade file, the upgrade cannot be performed at all. Phenomenon, improved upgrade success rate and upgrade intelligence.

Several specific examples are provided below in connection with any of the above embodiments.

Example 1:

As shown in FIG. 5, the software upgrade method described in this example includes:

S001: The DM session initiates and the server interacts. The execution body of this step is the client.

The client initiates a FOTA upgrade, and the DM session interacts with the server to query whether the server has a differential upgrade package available.

S002: Determine whether the server has a differential upgrade package available. If yes, go to S003. If no, go to S015.

S003: Download the DD file to obtain the dice address of the differential upgrade package in the DD file. If the server has a differential upgrade package, the server sends a DD file to the client. The DD file contains the information of the original differential upgrade package size and download address, and the file name and location of the differential upgrade package upgrade file. Partition information and its importance level.

S004: Download a differential upgrade package based on the download address.

S005: Perform upgrade package integrity verification. Through the upgrade package integrity verification, it can be verified whether the upgrade package has data loss, bit error, and tampering during the transmission process; specifically, the upgrade can be verified by a checksum algorithm such as parity check or MD5 algorithm. The integrity of the package.

S005: The client restarts to enter the upgrade package correctness check. Before the verification, the client's upgrade agent obtains the file name of the image or file system to be updated by the upgrade package, the partition information of the file, and their importance level.

S006: Determine whether the integrity verification is passed. If yes, go to S007, if no, go to S014.

S007: Obtain a file name, a partition information, and an importance level information of the upgrade file in the upgrade package included in the DD file. The partition information indicates the write area of each file in the software.

S008: Perform the first correctness verification on all upgrade files in the upgrade package. The first correctness verification here is equivalent to the verification of the correctness of the upgrade package in the previous embodiment.

S009: Determine whether the first correctness verification is passed, and if yes, go to S013; if not, go to S010.

S010: Determine an important upgrade file according to the importance level obtained by S007, and upgrade the important upgrade. The file is verified for the second time. Only verify that the importance level is in the partition where the level threshold and above are located. Verify that the image and file system information of this part of the partition completely match the image and file system information of the version of the differential upgrade package.

S011: Determine whether the second correctness verification is passed, and if yes, go to S012; if not, go to S014.

S012: Ignore the verification and upgrade of other parts, and determine that the software upgrade is performed based only on the partition where the important upgrade file passed in step S010 is verified. This is equivalent to performing a partial upgrade in the foregoing embodiment.

S013: Upgrade the software, indicating that the upgrade is successful.

S014: The upgrade failed.

S015: Prompt that no differential upgrade package is available.

Example two:

As shown in Figure 6, the software upgrade method of this example includes:

S101: The client detects that an upgrade package is available on the server.

S102: Download a DD file, and obtain information content of the DD file, where the information content may include information such as an upgrade package size and a download address, and further include a file name, a partition information, and an importance of the upgrade file included in the available upgrade package. grade.

S103: Download the upgrade package and verify the integrity of the upgrade package.

S104: Obtain information such as a file name, a partition information, and an importance level of the upgrade file included in the upgrade package.

S105: The client restarts to enter the first correctness verification.

S106: The verification finds that the sb11.mbn file in the client does not match the sb11.mbn file in the upgrade package, and other files match. At this point, it indicates that the first correctness verification failed.

S107: Perform a second correctness verification.

S108: Determine that the upgrade file included in the upgrade package has NON-NLOS.bin and sb11.mbn, if The current client specifies a level threshold of 3, and determines whether the importance level of NON-HLOS.bin is not less than 3, and the importance level of sb11.mbn is less than 3; then only the partition where NON-HLOS.bin is located is verified. And upgrade, ignore the checksum upgrade of the partition where sb11.mbn is located. Of course, the higher the importance level in this example, the higher the importance of the upgrade.

It should be noted that the software upgrade device and the client described in the embodiments of the present invention all correspond to terminal devices such as mobile phones, network televisions, tablet computers, or wearable devices, especially mobile terminals. The software upgrade device can even be part of the client. In summary, the client or terminal including the software upgrade device in this embodiment has the characteristics of high software upgrade success rate and high upgrade intelligence.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, such as: multiple units or components may be combined, or Can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, or direct coupling, or communication connection of the components shown or discussed may be indirect coupling or communication connection through some interfaces, devices or units, and may be electrical, mechanical or other forms. of.

The units described above as separate components may or may not be physically separated, and the components displayed as the unit may or may not be physical units, that is, may be located in one place or distributed to multiple network units; Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing module, or each unit may be separately used as one unit, or two or more units may be integrated into one unit; the above integration The unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

One of ordinary skill in the art can understand that all or part of the steps of the above method embodiments are implemented. The foregoing may be completed by a program instruction related hardware, where the foregoing program may be stored in a computer readable storage medium, and when executed, the program includes the steps of the foregoing method embodiment; and the foregoing storage medium includes: mobile storage A device that can store program code, such as a device, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

Correspondingly, the embodiment of the present invention further provides a computer storage medium, wherein a computer program is stored, and the computer program is used to execute the software upgrade method of the embodiment of the present invention.

The above is only a specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the appended claims.

Industrial applicability

In the technical solution of the embodiment of the present invention, when the software is upgraded, the software upgrade may be performed based on the upgrade file verified by the file correctness in the upgrade package, so that the files of the individual upgrade files in the prior art are well avoided. If the verification fails, the entire software cannot be upgraded and the upgrade fails. This improves the software upgrade success rate. It is especially suitable for software upgrades that have only minor differences between upgrade files and client upgrade files in some upgrade packages, and do not affect the main purpose of this upgrade.

Claims (17)

1. A software upgrade method, the method comprising:

   Receiving an upgrade package, where the upgrade package includes a total of M upgrade files; the M is an integer not less than 2;

   When the software upgrade cannot be performed based on the M upgrade files, the software upgrade is performed based on the N upgrade files verified by the file correctness;

   Wherein, the N is a positive integer smaller than the M.
2. The method according to claim 1, wherein when the software upgrade cannot be performed based on the M upgrade files, the software upgrade is performed based on the upgrade files that are verified by the file correctness, including:

   Determining important upgrade files for the upgrade package;

   Determining the verification result of the correctness of the file of the important upgrade file;

   If the verification result indicates that the important upgrade file is verified by the correctness of the file, the software is upgraded based on the N upgrade files verified by the correctness of the file; wherein the N upgrades are verified by the correctness of the file. The file includes at least all of the important upgrade files described.
3. The method of claim 2, wherein the determining the important upgrade file of the upgrade package comprises:

   Receiving a download descriptor file of the upgrade package;

   The important upgrade file is determined based on the download descriptor file.
4. The method according to claim 3, wherein said download descriptor file includes a file name of all files of said upgrade package and an importance level corresponding to said file;

   Determining the important upgrade file based on the download descriptor file, including:

   Comparing the importance level to a level threshold;

   Based on the result of the comparison, the important upgrade file is determined.
5. The method of claim 3 wherein said download descriptor file comprises said The file name of the important upgrade file described in the upgrade package;

   The determining the important upgrade file of the upgrade package includes:

   Extracting a file name of the important upgrade file in the download descriptor file to determine the important upgrade file.
6. The method of claim 2, wherein the method further comprises:

   Performing the correctness verification of the upgrade package for the upgrade package;

   The verification result of determining the correctness of the file of the important upgrade file includes:

   If the verification of the correctness of the upgrade package fails, the verification result of the verification of the correctness of the file of the important upgrade file is determined.
7. The method according to claim 6, wherein the upgrade package correctness is verified as correctness verification of all files in the upgrade package;

   If the verification of the correctness of the upgrade package fails, the verification result of the verification of the correctness of the file of the important upgrade file is determined, including:

   And obtaining, according to the verification result of the verification of the correctness of the upgrade package, the verification result of the verification of the correctness of the file of the important upgrade file.
8. The method according to claim 1, wherein when the software upgrade cannot be performed based on the M upgrade files, the software upgrade is performed based on the upgrade files that are verified by the file correctness, including:

   Determining, by the N upgrade files, the correctness of the files in the M upgrade files;

   The software upgrade is performed based on the N upgrade files verified by the correctness of the file.
9. A software upgrade device, the device comprising:

   a receiving unit, configured to receive an upgrade package, where the upgrade package includes a total of M upgrade files; the M is an integer not less than 2;

   An upgrade unit configured to perform a software upgrade based on the M upgrade files, Performing software upgrades on the N upgrade files verified by file correctness;

   Wherein, the N is a positive integer smaller than the M.
10. The apparatus according to claim 9, wherein the upgrading unit comprises:

    a first determining module, configured to determine an important upgrade file of the upgrade package;

    a second determining module, configured to determine a verification result of the correctness of the file of the important upgrade file;

    An upgrade module, configured to: if the verification result indicates that the important upgrade file is verified by the correctness of the file, upgrade software based on the N upgrade files verified by the correctness of the file; wherein the N pass file correctness The upgrade file verified includes at least all of the important upgrade files.
11. The apparatus of claim 10, wherein the first determining module is configured to receive a download descriptor file of the upgrade package; and determine the important upgrade file based on the download descriptor file.
12. The device according to claim 11, wherein the download descriptor file includes a file name of all files of the upgrade package and an importance level corresponding to the file;

    The first determining module is further configured to compare the importance level with a level threshold; and determine the important upgrade file based on the result of the comparing.
13. The apparatus according to claim 11, wherein said download descriptor file includes a file name of said important upgrade file in said upgrade package;

    The first determining module is further configured to extract a file name of the important upgrade file in the download descriptor file, and determine the important upgrade file.
14. The device of claim 10, wherein the device further comprises:

    a verification unit configured to verify the correctness of the upgrade package of the upgrade package;

    The second determining module is further configured to: if the verification package correctness verification fails, determine a verification result of the file correctness verification of the important upgrade file.
15. The apparatus according to claim 14, wherein said upgrade package correctness is verified as correctness verification of all files in said upgrade package;

    The second determining module is further configured to obtain a verification result of the file correctness verification of the important upgrade file based on the verification result of the upgrade package correctness verification.
16. The apparatus according to claim 9, wherein the upgrading unit is further configured to determine N the upgrade files through which the file correctness verification is passed in the M upgrade files; and verifying by using the file correctness N upgrade files for software upgrades.
17. A computer storage medium having stored therein computer executable instructions configured to perform the software upgrade method of any of claims 1-8.

Images