CN104052818A - Version upgrade method and device for mobile terminal - Google Patents

Version upgrade method and device for mobile terminal Download PDF

Info

Publication number
CN104052818A
CN104052818A CN201410299466.6A CN201410299466A CN104052818A CN 104052818 A CN104052818 A CN 104052818A CN 201410299466 A CN201410299466 A CN 201410299466A CN 104052818 A CN104052818 A CN 104052818A
Authority
CN
China
Prior art keywords
upgrade file
releases
mobile terminal
version
file
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
Application number
CN201410299466.6A
Other languages
Chinese (zh)
Other versions
CN104052818B (en
Inventor
朱晓亮
桑圣杰
张景新
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hisense Mobile Communications Technology Co Ltd
Original Assignee
Hisense Mobile Communications Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hisense Mobile Communications Technology Co Ltd filed Critical Hisense Mobile Communications Technology Co Ltd
Priority to CN201410299466.6A priority Critical patent/CN104052818B/en
Publication of CN104052818A publication Critical patent/CN104052818A/en
Application granted granted Critical
Publication of CN104052818B publication Critical patent/CN104052818B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communication
    • H04L9/32Cryptographic mechanisms or cryptographic arrangements for secret or secure communication including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3247Cryptographic mechanisms or cryptographic arrangements for secret or secure communication including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures

Abstract

The invention discloses a version upgrade method and device for a mobile terminal. The version upgrade method and device for the mobile terminal are used for solving the problem that because a target version in the prior art is inconsistent with a key signature of a user terminal, verification fails, and system upgrade can not be completed. The method includes the steps that a system upgrade file is obtained, and the system upgrade file at least comprises a middle version upgrade file and a target version upgrade file; a public key file of the user terminal is obtained, and the system of the user terminal is upgraded to a middle version from the current version according to the public key file and the middle version upgrade file carried in the system upgrade file; after it is confirmed that upgrade succeeds, the system of the user terminal is continuously upgraded to a target version from the middle version according to the target version upgrade file carried in the system upgrade file. In this way, when the middle version is upgraded to the target version, the public key file of the user terminal and signature information of the target version do not need to be verified, and it is guaranteed that the version of the system of the user terminal can be upgraded.

Description

A kind of version upgrading method of mobile terminal and device
Technical field
The present invention relates to the online upgrading field of mobile terminal, relate in particular to a kind of version upgrading method and device of mobile terminal.
Background technology
After mobile terminal listing, in user's use procedure, may find some system problems, mobile terminal is the rear a series of system problems that occur of solution listing, sophisticated systems function, and the later stage can be issued a series of system upgrade versions for this mobile terminal.In order to facilitate user's system upgrade problem of settling a dispute by the parties concerned themselves, mobile terminal manufacturer can download (Over The Air in the air by the system upgrade version boil down to after problem reparation, OTA) AKU is put on server, facilitate user to pass through the online upgrading function of mobile terminal, be upgraded to up-to-date version.
At present, mobile terminal is when system upgrade, can only download the AKU of the manufacturer of this mobile terminal, be specially: mobile terminal is signed AKU is carried out to verification by key, only have AKU by key signature authentication just to can be used as AKU trusty and carry out mobile terminal system upgrading, thereby avoided being caused by Malware utilization the problem of system safety performance.Consideration for third-party testing requirement and secure context, conventionally mobile terminal need to carry out verification to OTA AKU according to key signature when system upgrade, from the Recovery mirror image root file system of mobile terminal /res/keys loads PKI source file, then load and be embedded in the RSA signing messages in OTA AKU, and mate with the PKI source file of preserving in/res/keys, if the match is successful, according to OTA AKU, carry out system upgrade, otherwise, verification failure, exits OTA upgrading.
Yet, as being cracked, the key signature of current mobile terminal use has to change signature, or developer is when compiling redaction AKU, T card version and the order transposing that generates OTA AKU will be generated, or used testkey in mk file, cause the signing messages of AKU and mobile terminal inconsistent etc., according to key signature to the verification of OTA AKU by verification failure, cause the mobile terminal cannot completion system upgrading.
Summary of the invention
The embodiment of the present invention is for solving the technical problem of cannot completion system upgrading unsuccessfully causing due to AKU signature check existing in prior art, a kind of version upgrading method and device of mobile terminal are provided, both can avoid, due to cannot upgrading by completion system that AKU signature check unsuccessfully causes, guaranteeing the fail safe of AKU again simultaneously.
The concrete technical scheme that the embodiment of the present invention provides is as follows:
A version upgrading method for mobile terminal, comprising:
Obtain system upgrade file, in described system upgrade file, carry intermediate releases upgrade file and target version upgrade file, wherein, described intermediate releases upgrade file is the formerly version of described target version upgrade file, the signing messages of described intermediate releases upgrade file is corresponding with the PKI file of mobile terminal, and the ROMPaq in described intermediate releases upgrade file is not carried checking data, the ROMPaq in described target version upgrade file is carried checking data;
Obtain the PKI file of mobile terminal, and according to the signing messages of described PKI file and described intermediate releases upgrade file, the system of described mobile terminal is upgraded to intermediate releases by current version;
After confirmation upgrades successfully, continue according to described target version upgrade file, the system of described mobile terminal is upgraded to target version by described intermediate releases.
Adopt in this way, by first mobile terminal is upgraded to intermediate releases, be upgraded to again target version, wherein, when intermediate releases is upgraded to target version, do not need the signing messages of the PKI file of mobile terminal and target version to carry out verification, thereby the inconsistent verification failure causing of the key signature of having avoided target version and mobile terminal, problem that cannot completion system upgrading.
Preferably, described intermediate releases upgrade file is the upgrading difference bag with respect to mobile terminal current version.
Preferably, described intermediate releases upgrade file is the full bag of upgrading.
Preferably, obtain system upgrade file, comprising:
According to the priority of default system upgrade file, obtain after described intermediate releases upgrade file, then obtain described target version upgrade file.
Adopt in this way, obtain again target version upgrade file after can first obtaining intermediate releases upgrade file.
Preferably, further comprise:
If the system of described mobile terminal is upgraded to target version failure by described intermediate releases, by the system rollback of described mobile terminal to described intermediate releases, and delete the target version upgrade file in described system upgrade file.
Adopt in this way, at the system upgrade of mobile terminal, during to target version failure, system has still been upgraded to intermediate releases, guarantees the renewal upgrading of system.
A version upgrading method for mobile terminal, comprising:
The system upgrade request of mobile terminal receive;
According to described system upgrade request, determine system upgrade file, and described system upgrade file is sent to described mobile terminal, in described system upgrade file, carry intermediate releases upgrade file and target version upgrade file, wherein, described intermediate releases upgrade file is the formerly version of described target version upgrade file, the signature of described intermediate releases upgrade file is corresponding with the PKI file of described mobile terminal, and the ROMPaq in described intermediate releases upgrade file is not carried checking data, ROMPaq in described target version upgrade file is carried checking data.
Adopt in this way, by intermediate releases upgrade file and target version upgrade file sending value mobile terminal, guaranteed to be upgraded to again target version after first mobile terminal is upgraded to intermediate releases, wherein, when intermediate releases is upgraded to target version, do not need the signing messages of the PKI file of mobile terminal and target version to carry out verification, thereby avoided the inconsistent verification failure causing of key signature of target version and mobile terminal, problem that cannot completion system upgrading.
Preferably described intermediate releases upgrade file is the upgrading difference bag with respect to mobile terminal current version.
Preferably, described intermediate releases upgrade file is the full bag of upgrading.
An edition upgrading device for mobile terminal, comprising:
Acquiring unit, be used for obtaining system upgrade file, in described system upgrade file, carry intermediate releases upgrade file and target version upgrade file, wherein, described intermediate releases upgrade file is the formerly version of described target version upgrade file, the signing messages of described intermediate releases upgrade file is corresponding with the PKI file of mobile terminal, and the ROMPaq in described intermediate releases upgrade file do not carry checking data, and the ROMPaq in described target version upgrade file is carried checking data;
The first upgrading unit, for obtaining the PKI file of mobile terminal, and according to the signing messages of described PKI file and described intermediate releases upgrade file, upgrades to intermediate releases by the system of described mobile terminal by current version;
The second upgrading unit, after upgrading successfully in confirmation, continues according to described target version upgrade file, and the system of described mobile terminal is upgraded to target version by described intermediate releases.
Like this, by first mobile terminal is upgraded to intermediate releases, be upgraded to again target version, wherein, when intermediate releases is upgraded to target version, do not need the signing messages of the PKI file of mobile terminal and target version to carry out verification, thereby the inconsistent verification failure causing of the key signature of having avoided target version and mobile terminal, problem that cannot completion system upgrading.
Preferably, described intermediate releases upgrade file is the upgrading difference bag with respect to mobile terminal current version.
Preferably, described intermediate releases upgrade file is the full bag of upgrading.
Preferably, described acquiring unit obtains system upgrade file, comprising:
According to the priority of default system upgrade file, obtain after described intermediate releases upgrade file, then obtain described target version upgrade file.
Like this, acquiring unit obtains target version upgrade file after can first obtaining intermediate releases upgrade file again.
Preferably, described the second upgrading unit, is further used for:
If the system of described mobile terminal is upgraded to target version failure by described intermediate releases, by the system rollback of described mobile terminal to described intermediate releases, and delete the target version upgrade file in described system upgrade file.
Like this, the second upgrading unit can be at the system upgrade of mobile terminal during to target version failure, and system has still been upgraded to intermediate releases, guarantees the renewal upgrading of system.
An edition upgrading device for mobile terminal, comprising:
Receiving element, for the system upgrade request of mobile terminal receive;
Transmitting element, for determining system upgrade file according to described system upgrade request, and described system upgrade file is sent to described mobile terminal, in described system upgrade file, carry intermediate releases upgrade file and target version upgrade file, wherein, described intermediate releases upgrade file is the formerly version of described target version upgrade file, the signature of described intermediate releases upgrade file is corresponding with the PKI file of described mobile terminal, and the ROMPaq in described intermediate releases upgrade file is not carried checking data, ROMPaq in described target version upgrade file is carried checking data.
Like this, server is by intermediate releases upgrade file and target version upgrade file sending value mobile terminal, guaranteed to be upgraded to again target version after first mobile terminal is upgraded to intermediate releases, wherein, when intermediate releases is upgraded to target version, do not need the signing messages of the PKI file of mobile terminal and target version to carry out verification, thereby avoided the inconsistent verification failure causing of key signature of target version and mobile terminal, problem that cannot completion system upgrading.
Preferably, described intermediate releases upgrade file is the upgrading difference bag with respect to mobile terminal current version.
Preferably, described intermediate releases upgrade file is the full bag of upgrading.
Adopt technical solution of the present invention, mobile terminal is upgraded in intermediate releases process by current version, because current version is consistent with the signature of intermediate releases, therefore can and be upgraded to intermediate releases by verification.By intermediate edition upgrading in the process of target version, because the Recovery in intermediate releases is not with key verifying function, like this, can guarantee that mobile terminal is sign in inconsistent situation still with AKU can completion system upgrading, and be upgraded in final version in Recovery with key verifying function, can guarantee the fail safe of AKU like this, system still can normally be upgraded in subsequent process.
Accompanying drawing explanation
The particular flow sheet of the version upgrading method of a kind of mobile terminal of the mobile terminal side that Fig. 1 provides for the embodiment of the present invention;
The particular flow sheet of the version upgrading method of a kind of mobile terminal of the server side that Fig. 2 provides for the embodiment of the present invention;
The structural representation of the edition upgrading device of a kind of mobile terminal of the mobile terminal side that Fig. 3 provides for the embodiment of the present invention;
The structural representation of the edition upgrading device of a kind of mobile terminal of the server side that Fig. 4 provides for the embodiment of the present invention.
Embodiment
Adopt technical solution of the present invention, can effectively avoid existing in prior art due to key signature check unsuccessfully cause cannot completion system upgrading, and then cause the insurmountable problem of defect of system existence in mobile terminal.
The embodiment of the present invention provides a kind of version upgrading method of mobile terminal, is applied to all kinds of intelligent mobile terminals, and as smart mobile phone, the terminal equipments such as intelligent television, are elaborated to the preferred embodiment of the present invention below in conjunction with accompanying drawing.
Consult shown in Fig. 1, the concrete handling process of the version upgrading method of a kind of mobile terminal of the mobile terminal side that the embodiment of the present invention provides comprises:
Step 101: obtain system upgrade file, in this system upgrade file, at least carry intermediate releases upgrade file and target version upgrade file, wherein, this intermediate releases upgrade file is the formerly version of target version upgrade file, the signing messages of intermediate releases upgrade file is corresponding with the PKI file of mobile terminal, and the ROMPaq in intermediate releases upgrade file is not carried checking data, the ROMPaq in target version upgrade file is carried checking data.
In actual applications, mobile terminal manufacturer can be regularly constantly uploads onto the server the system upgrade file after the improving of mobile terminal, and system upgrade file uploads onto the server with the form of OTA AKU conventionally.
Mobile terminal, with after corresponding server connects, obtains system upgrade file by local online upgrading function, i.e. OTA AKU.
Wherein, OTA AKU is generally two types, a kind ofly for OTA, entirely wraps, and comprises the system upgrade file of all application of whole system, and another kind is OTA difference bag, only comprises the system upgrade file of (changing) several application of needs upgrading.OTA difference bag wraps entirely with respect to OTA, conventionally less.
The intermediate releases upgrade file of acquisition for mobile terminal is the upgrading difference bag (being OTA difference bag) with respect to mobile terminal current version, or is the full bag of upgrading (being that OTA wraps entirely).
For example, difference between version A and version B, version B has certain applications to need to improve with respect to version A, OTA difference bag has only comprised the upgrade file of improved these certain applications of needs, if the current system of mobile terminal is version A, in the time of need to being upgraded to version B, at mobile terminal, determine after online upgrading, the OTA difference bag of system meeting download version A and version B, after system installation, will directly be upgraded to version B, in addition, the full bag of OTA that mobile terminal can also download version B is upgraded.
When acquisition for mobile terminal system upgrade file, can obtain target version upgrade file (OTA that is latest edition wraps entirely), and intermediate releases upgrade file (OTA wraps or OTA difference bag entirely), wherein, this intermediate releases upgrade file is the formerly version of target version upgrade file.
Signing messages in intermediate releases upgrade file should be consistent with the signing messages of mobile terminal,, when compiling intermediate releases upgrade file, sets its signing messages and keep corresponding with signing messages or the PKI file of mobile terminal.
Wherein, the ROMPaq in intermediate releases upgrade file---in Recovery file, be tape verifying data not, and in the Recovery file in target version upgrade file with checking data.Like this, can guarantee that updating mobile terminal is after intermediate releases, due to the tape verifying data not of the ROMPaq in intermediate releases upgrade file, not be used in and carry out signing messages checking and just can directly upgrade to target version, and be upgraded to after target version, when subsequent upgrade, can proceed check, guarantee the fail safe of mobile terminal system.
While obtaining system upgrade file, according to the priority of default system upgrade file, obtain after intermediate releases upgrade file, then obtain target version upgrade file.
Preferably, the system upgrade request that can send according to mobile terminal, arranges the priority of intermediate releases upgrade file higher than target version upgrade file, like this, can preferentially download intermediate releases upgrade file, determine that having downloaded rear continuation downloads target version upgrade file.
Step 102: obtain the PKI file of mobile terminal, and according to the signing messages of this PKI file and intermediate releases upgrade file, the system of mobile terminal is upgraded to intermediate releases by current version.
Preferably, perform step at 102 o'clock, specifically comprise the following steps:
For the signing messages in intermediate releases upgrade file in PKI file and system upgrade file, carry out verification, when signing messages in judging this intermediate releases upgrade file is corresponding with this PKI file, according to this intermediate releases upgrade file, the system of mobile terminal is upgraded to intermediate releases by current version.
Concrete, while obtaining the PKI file of mobile terminal, comprise, the Recovery mirror image root file system from the version of mobile terminal current system /res/keys loading PKI file.
While carrying out verification for the signing messages in intermediate releases upgrade file in PKI file and system upgrade file, first load and be embedded in the RSA signing messages in intermediate releases upgrade file (being OTA AKU), then this RSA signing messages is mated with the PKI file of preserving in/res/keys, if verification is passed through, the system of mobile terminal can be upgraded to intermediate releases by current version.
Step 103: after confirmation upgrades successfully, continue according to target version upgrade file, the system of mobile terminal is upgraded to target version by intermediate releases.
Wherein, the target version upgrade file according to carrying in system upgrade file, upgrades to target version by the system of mobile terminal by intermediate releases, comprising:
ROMPaq based in intermediate releases, upgrades to target version by the system of mobile terminal by intermediate releases according to the target version upgrade file carrying in system upgrade file.
Concrete, when according to the system of target version upgrade file update mobile terminal, owing in the Recovery file in intermediate releases ROMPaq being tape verifying function not, therefore need to not carry out verification for the PKI file of mobile terminal and the signing messages in this target version upgrade file, but directly the system of mobile terminal be upgraded by this target version upgrade file.Like this, avoided between target version upgrade file and the PKI file of mobile terminal causing verification failure because key signature is inconsistent, so cause cannot completion system upgrading phenomenon.
Further, if the system of mobile terminal is upgraded to target version failure by intermediate releases, by the system rollback of mobile terminal to intermediate releases, and delete the target version upgrade file in upgrade file.
Like this, at mobile terminal, when being upgraded to target version failure in the situation that, the system of mobile terminal has still been upgraded to intermediate releases, and with respect to version before, system is still upgraded and improved.
For example, the system of current mobile terminal is version B (signature is key2), the target version of upgrading is version C (signature is key1), the version of issue was A (signature is key1) in the past, if mobile terminal is directly upgraded to version C by system from version B, during upgrading, because the signature in version B and version C is inconsistent, therefore cannot pass through signature check, upgrade unsuccessfully.Therefore, an intermediate releases---version C0 is set, but does not comprise key signature check function in the Recovery in version C0.Then also needing to be a version B to the OTA difference bag of version C0---version B-version C0 (is intermediate releases upgrade file, signature is key2), because the signature of version B and version B-version C0 is key2, therefore, in escalation process, signature check can be passed through, mobile terminal can be upgraded to version C0, when updating mobile terminal is after C0, the OTA that system detects target version C again wraps entirely, although the key1 that version C uses signature, but during due to upgrading, in the Recovery of version C0, do not comprise key signature check function, therefore can be without signature check, directly upgrading, finally be upgraded to target version.Wherein, the generative process of version B-version C0 is: intermediate file src.zip that need to be corresponding for the version A of former issue, by order " java-Xmx2048m-jar signapk.jar-w key2/releasekey.x509.pem key2/releasekey.pk8src.zip target.zip ", again with key2, sign and form target.zip, and then with before the intermediate file with key2 signed that generates of compiling be combined with target.zip, form final intermediate releases upgrade file version B-version C0.
Again for example, the system of current mobile terminal is version d (signature is key_old), the target version of upgrading is version F (signature is key_new), if mobile terminal is directly upgraded to version F by system from version d, during upgrading, because the signature in version d and version F is inconsistent, therefore cannot pass through signature check, upgrade unsuccessfully.Therefore, an intermediate releases---version E is set, wherein, version E is that OTA wraps entirely, signs as key_old, and in the Recovery in version E, does not comprise key signature check function.Then after the full bag of the OTA of mobile terminal download version E, because the signature of version d and version E is key_old, therefore, in escalation process, signature check can be passed through, mobile terminal can be upgraded to version E, when updating mobile terminal is after E, the OTA that system detects target version F again wraps entirely, although the key_new that version F uses signature, but during due to upgrading, in the Recovery of version E, do not comprise key signature check function, therefore can be without signature check, directly upgrading, is finally upgraded to target version F.
Target version upgrade file is necessary for the full bag of upgrading, because target version and intermediate releases signing messages are inconsistent, the difference bag of upgrading if still select is upgraded, after having upgraded, the signature of the application of upgrading is not consistent with intermediate releases, and upgrading after application signature with target version consistent, can cause upgrading after application there will be operation exception.
By need the signature check by key in the embodiment of the present invention in mobile terminal is upgraded to intermediate releases process by current version, and the Recovery in this intermediate releases is not with key verifying function, like this, can guarantee that mobile terminal is sign in inconsistent situation still with AKU can completion system upgrading, and be upgraded in final version in Recovery with key verifying function, can guarantee the fail safe of AKU like this, system still can normally be upgraded in subsequent process.
Based on above-described embodiment, to consult shown in Fig. 2, the embodiment of the present invention also provides the version upgrading method of a kind of mobile terminal of server side, and the concrete handling process of the method comprises:
Step 201: the system upgrade request of mobile terminal receive.
Step 202: system upgrade file is determined in request according to system upgrade, and system upgrade file is sent to mobile terminal, in system upgrade file, carry intermediate releases upgrade file and target version upgrade file, wherein, intermediate releases upgrade file is the formerly version of target version upgrade file, the signature of intermediate releases upgrade file is corresponding with the PKI file of mobile terminal, and the ROMPaq in intermediate releases upgrade file is not carried checking data, the ROMPaq in target version upgrade file is carried checking data.
Intermediate releases upgrade file is the upgrading difference bag with respect to mobile terminal current version, or the full bag of upgrading.
Based on above-described embodiment, to consult shown in Fig. 3, the embodiment of the present invention also provides the edition upgrading device of a kind of mobile terminal of mobile terminal side, and this device comprises: acquiring unit 301, the first upgrading unit 302 and the second upgrading unit 303, wherein,
Acquiring unit 301, be used for obtaining system upgrade file, in system upgrade file, carry intermediate releases upgrade file and target version upgrade file, wherein, intermediate releases upgrade file is the formerly version of target version upgrade file, the signing messages of intermediate releases upgrade file is corresponding with the PKI file of mobile terminal, and the ROMPaq in intermediate releases upgrade file do not carry checking data, and the ROMPaq in target version upgrade file is carried checking data;
The first upgrading unit 302, for obtaining the PKI file of mobile terminal, and according to the signing messages of PKI file and intermediate releases upgrade file, upgrades to intermediate releases by the system of mobile terminal by current version;
The second upgrading unit 303, after upgrading successfully in confirmation, continues according to target version upgrade file, and the system of mobile terminal is upgraded to target version by intermediate releases.
Intermediate releases upgrade file is the upgrading difference bag with respect to mobile terminal current version.
Intermediate releases upgrade file is the full bag of upgrading.
Acquiring unit 301 obtains system upgrade file, comprising:
According to the priority of default system upgrade file, obtain after intermediate releases upgrade file, then obtain target version upgrade file.
The second upgrading unit 303, is further used for:
If the system of mobile terminal is upgraded to target version failure by intermediate releases, by the system rollback of mobile terminal to intermediate releases, and the target version upgrade file in deletion system upgrade file.
Based on above-described embodiment, to consult shown in Fig. 4, the embodiment of the present invention also provides the edition upgrading device of a kind of mobile terminal of server side, and this device comprises: receiving element 401 and transmitting element 402, wherein,
Receiving element 401, for the system upgrade request of mobile terminal receive;
Transmitting element 402, be used for the request according to system upgrade and determine system upgrade file, and system upgrade file is sent to mobile terminal, in system upgrade file, carry intermediate releases upgrade file and target version upgrade file, wherein, intermediate releases upgrade file is the formerly version of target version upgrade file, the signature of intermediate releases upgrade file is corresponding with the PKI file of mobile terminal, and the ROMPaq in intermediate releases upgrade file is not carried checking data, the ROMPaq in target version upgrade file is carried checking data.
Intermediate releases upgrade file is the upgrading difference bag with respect to mobile terminal current version.
Intermediate releases upgrade file is the full bag of upgrading.
In sum, by version upgrading method and the device of a kind of mobile terminal of providing in the embodiment of the present invention, the method comprises intermediate releases upgrade file and target version upgrade file by obtaining, the system of mobile terminal is upgraded to intermediate releases by current version, final realization updating mobile terminal to target version, like this, by first mobile terminal is upgraded to intermediate releases, be upgraded to again target version, wherein, when intermediate releases is upgraded to target version, do not need the signing messages of the PKI file of mobile terminal and target version to carry out verification, thereby avoided due to cannot upgrading by completion system that AKU signature check unsuccessfully causes, can guarantee the fail safe of AKU again simultaneously.
Although described the preferred embodiments of the present invention, once those skilled in the art obtain the basic creative concept of cicada, can make other change and modification to these embodiment.So claims are intended to all changes and the modification that are interpreted as comprising preferred embodiment and fall into the scope of the invention.
Obviously, those skilled in the art can carry out various changes and modification and not depart from the spirit and scope of the embodiment of the present invention the embodiment of the present invention.Like this, if within these of the embodiment of the present invention are revised and modification belongs to the scope of the claims in the present invention and equivalent technologies thereof, the present invention is also intended to comprise these changes and modification interior.

Claims (16)

1. a version upgrading method for mobile terminal, is characterized in that, comprising:
Obtain system upgrade file, in described system upgrade file, carry intermediate releases upgrade file and target version upgrade file, wherein, described intermediate releases upgrade file is the formerly version of described target version upgrade file, the signing messages of described intermediate releases upgrade file is corresponding with the PKI file of mobile terminal, and the ROMPaq in described intermediate releases upgrade file is not carried checking data, the ROMPaq in described target version upgrade file is carried checking data;
Obtain the PKI file of mobile terminal, and according to the signing messages of described PKI file and described intermediate releases upgrade file, the system of described mobile terminal is upgraded to intermediate releases by current version;
After confirmation upgrades successfully, continue according to described target version upgrade file, the system of described mobile terminal is upgraded to target version by described intermediate releases.
2. the method for claim 1, is characterized in that, described intermediate releases upgrade file is the upgrading difference bag with respect to mobile terminal current version.
3. the method for claim 1, is characterized in that, described intermediate releases upgrade file is the full bag of upgrading.
4. the method as described in claim 1-3 any one, is characterized in that, obtains system upgrade file, comprising:
According to the priority of default system upgrade file, obtain after described intermediate releases upgrade file, then obtain described target version upgrade file.
5. the method as described in claim 1-3 any one, is characterized in that, further comprises:
If the system of described mobile terminal is upgraded to target version failure by described intermediate releases, by the system rollback of described mobile terminal to described intermediate releases, and delete the target version upgrade file in described system upgrade file.
6. a version upgrading method for mobile terminal, is characterized in that, comprising:
The system upgrade request of mobile terminal receive;
According to described system upgrade request, determine system upgrade file, and described system upgrade file is sent to described mobile terminal, in described system upgrade file, carry intermediate releases upgrade file and target version upgrade file, wherein, described intermediate releases upgrade file is the formerly version of described target version upgrade file, the signature of described intermediate releases upgrade file is corresponding with the PKI file of described mobile terminal, and the ROMPaq in described intermediate releases upgrade file is not carried checking data, ROMPaq in described target version upgrade file is carried checking data.
7. method as claimed in claim 6, is characterized in that, described intermediate releases upgrade file is the upgrading difference bag with respect to mobile terminal current version.
8. method as claimed in claim 6, is characterized in that, described intermediate releases upgrade file is the full bag of upgrading.
9. an edition upgrading device for mobile terminal, is characterized in that, comprising:
Acquiring unit, be used for obtaining system upgrade file, in described system upgrade file, carry intermediate releases upgrade file and target version upgrade file, wherein, described intermediate releases upgrade file is the formerly version of described target version upgrade file, the signing messages of described intermediate releases upgrade file is corresponding with the PKI file of mobile terminal, and the ROMPaq in described intermediate releases upgrade file do not carry checking data, and the ROMPaq in described target version upgrade file is carried checking data;
The first upgrading unit, for obtaining the PKI file of mobile terminal, and according to the signing messages of described PKI file and described intermediate releases upgrade file, upgrades to intermediate releases by the system of described mobile terminal by current version;
The second upgrading unit, after upgrading successfully in confirmation, continues according to described target version upgrade file, and the system of described mobile terminal is upgraded to target version by described intermediate releases.
10. device as claimed in claim 9, is characterized in that, described intermediate releases upgrade file is the upgrading difference bag with respect to mobile terminal current version.
11. devices as claimed in claim 9, is characterized in that, described intermediate releases upgrade file is the full bag of upgrading.
12. devices as described in claim 9-11 any one, is characterized in that, described acquiring unit obtains system upgrade file, comprising:
According to the priority of default system upgrade file, obtain after described intermediate releases upgrade file, then obtain described target version upgrade file.
13. devices as described in claim 9-11 any one, is characterized in that, described the second upgrading unit, is further used for:
If the system of described mobile terminal is upgraded to target version failure by described intermediate releases, by the system rollback of described mobile terminal to described intermediate releases, and delete the target version upgrade file in described system upgrade file.
The edition upgrading device of 14. 1 kinds of mobile terminals, is characterized in that, comprising:
Receiving element, for the system upgrade request of mobile terminal receive;
Transmitting element, for determining system upgrade file according to described system upgrade request, and described system upgrade file is sent to described mobile terminal, in described system upgrade file, carry intermediate releases upgrade file and target version upgrade file, wherein, described intermediate releases upgrade file is the formerly version of described target version upgrade file, the signature of described intermediate releases upgrade file is corresponding with the PKI file of described mobile terminal, and the ROMPaq in described intermediate releases upgrade file is not carried checking data, ROMPaq in described target version upgrade file is carried checking data.
15. devices as claimed in claim 14, is characterized in that, described intermediate releases upgrade file is the upgrading difference bag with respect to mobile terminal current version.
16. devices as claimed in claim 14, is characterized in that, described intermediate releases upgrade file is the full bag of upgrading.
CN201410299466.6A 2014-06-27 2014-06-27 The version upgrading method and device of a kind of mobile terminal Active CN104052818B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201410299466.6A CN104052818B (en) 2014-06-27 2014-06-27 The version upgrading method and device of a kind of mobile terminal

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
CN201710426362.0A CN107193612B (en) 2014-06-27 2014-06-27 Version upgrading method and device for mobile terminal
CN201410299466.6A CN104052818B (en) 2014-06-27 2014-06-27 The version upgrading method and device of a kind of mobile terminal
CN201710426363.5A CN107239288B (en) 2014-06-27 2014-06-27 Version upgrading method and device for mobile terminal

Related Child Applications (2)

Application Number Title Priority Date Filing Date
CN201710426363.5A Division CN107239288B (en) 2014-06-27 2014-06-27 Version upgrading method and device for mobile terminal
CN201710426362.0A Division CN107193612B (en) 2014-06-27 2014-06-27 Version upgrading method and device for mobile terminal

Publications (2)

Publication Number Publication Date
CN104052818A true CN104052818A (en) 2014-09-17
CN104052818B CN104052818B (en) 2017-07-11

Family

ID=51505169

Family Applications (3)

Application Number Title Priority Date Filing Date
CN201410299466.6A Active CN104052818B (en) 2014-06-27 2014-06-27 The version upgrading method and device of a kind of mobile terminal
CN201710426362.0A Active CN107193612B (en) 2014-06-27 2014-06-27 Version upgrading method and device for mobile terminal
CN201710426363.5A Active CN107239288B (en) 2014-06-27 2014-06-27 Version upgrading method and device for mobile terminal

Family Applications After (2)

Application Number Title Priority Date Filing Date
CN201710426362.0A Active CN107193612B (en) 2014-06-27 2014-06-27 Version upgrading method and device for mobile terminal
CN201710426363.5A Active CN107239288B (en) 2014-06-27 2014-06-27 Version upgrading method and device for mobile terminal

Country Status (1)

Country Link
CN (3) CN104052818B (en)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104699515A (en) * 2015-04-01 2015-06-10 广东欧珀移动通信有限公司 Android operating system based upgrading method and intelligent terminal
CN104778057A (en) * 2015-03-11 2015-07-15 小米科技有限责任公司 Terminal system upgrading method and device, and server
CN105068848A (en) * 2015-08-28 2015-11-18 小米科技有限责任公司 System upgrading method and apparatus
CN105357031A (en) * 2015-09-30 2016-02-24 青岛海信移动通信技术股份有限公司 OTA (over the air) upgrade method and device
CN105700917A (en) * 2016-01-04 2016-06-22 浪潮通用软件有限公司 Method and apparatus for synchronizing DLL and database
CN105718268A (en) * 2016-01-22 2016-06-29 青岛海信移动通信技术股份有限公司 Method and device for verifying OTA multi-pack upgrading
CN105809055A (en) * 2016-02-26 2016-07-27 深圳天珑无线科技有限公司 Access control method and device, and related equipment
WO2017016282A1 (en) * 2015-07-30 2017-02-02 中兴通讯股份有限公司 Software upgrading method and apparatus, and computer storage medium

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108170461B (en) * 2017-12-28 2021-07-27 北京四达时代软件技术股份有限公司 Differential upgrade package generation method, differential upgrade method and device

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101356519A (en) * 2006-06-19 2009-01-28 三星电子株式会社 Program upgrade system and method for ota-capable portable device
CN101646162A (en) * 2009-08-24 2010-02-10 中兴通讯股份有限公司 Mobile terminal software upgrading method and system based on OTA
CN102360298A (en) * 2011-09-27 2012-02-22 青岛海信电器股份有限公司 Software upgrading method of terminal equipment
CN102833745A (en) * 2012-07-17 2012-12-19 华为技术有限公司 Method for safely upgrading software, communication device and communication system
CN103297429A (en) * 2013-05-23 2013-09-11 北京大学 Embedded upgrading file transmission method
WO2014059874A1 (en) * 2012-10-15 2014-04-24 华为终端有限公司 Mobile terminal and software upgrade method thereof

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8352916B2 (en) * 2006-02-17 2013-01-08 International Business Machines Corporation Facilitating the automated testing of daily builds of software
US20080195868A1 (en) * 2007-02-12 2008-08-14 Nokia Corporation Rollback-Resistant Code-Signing
CN101163044A (en) * 2007-11-12 2008-04-16 北京深思洛克数据保护中心 Remote updating method and system for information safety equipment
US9237070B2 (en) * 2008-07-22 2016-01-12 Siemens Industry, Inc. Development, test, and demonstration of automation solutions using web-based virtual computers and VPN tunneling
EP2175366B1 (en) * 2008-10-08 2012-10-10 Research In Motion Limited Server for sending new application portions to mobile wireless communications devices and related methods
JP2010220019A (en) * 2009-03-18 2010-09-30 Panasonic Corp Key management method and key management apparatus
US8601468B1 (en) * 2010-05-18 2013-12-03 Google Inc. Web-based applications using web extents
CN103019789B (en) * 2012-12-17 2016-01-20 深圳市九洲电器有限公司 A kind of sign software upgrade method, device and mobile terminal
CN103425932B (en) * 2013-08-09 2017-02-01 华为终端有限公司 Signature calibration method and terminal device
CN103473498B (en) * 2013-09-12 2016-03-23 深圳市文鼎创数据科技有限公司 Application security verification method and terminal
CN103761329B (en) * 2014-02-08 2017-06-16 广东欧珀移动通信有限公司 A kind of method and its device that brush machine is carried out to mobile device

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101356519A (en) * 2006-06-19 2009-01-28 三星电子株式会社 Program upgrade system and method for ota-capable portable device
CN101646162A (en) * 2009-08-24 2010-02-10 中兴通讯股份有限公司 Mobile terminal software upgrading method and system based on OTA
CN102360298A (en) * 2011-09-27 2012-02-22 青岛海信电器股份有限公司 Software upgrading method of terminal equipment
CN102833745A (en) * 2012-07-17 2012-12-19 华为技术有限公司 Method for safely upgrading software, communication device and communication system
WO2014059874A1 (en) * 2012-10-15 2014-04-24 华为终端有限公司 Mobile terminal and software upgrade method thereof
CN103297429A (en) * 2013-05-23 2013-09-11 北京大学 Embedded upgrading file transmission method

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104778057A (en) * 2015-03-11 2015-07-15 小米科技有限责任公司 Terminal system upgrading method and device, and server
CN104699515A (en) * 2015-04-01 2015-06-10 广东欧珀移动通信有限公司 Android operating system based upgrading method and intelligent terminal
CN104699515B (en) * 2015-04-01 2018-03-16 广东欧珀移动通信有限公司 A kind of upgrade method and intelligent terminal based on Android operation system
CN106406922A (en) * 2015-07-30 2017-02-15 中兴通讯股份有限公司 Software upgrade method and device
WO2017016282A1 (en) * 2015-07-30 2017-02-02 中兴通讯股份有限公司 Software upgrading method and apparatus, and computer storage medium
CN105068848B (en) * 2015-08-28 2018-12-11 小米科技有限责任公司 Method for upgrading system and device
CN105068848A (en) * 2015-08-28 2015-11-18 小米科技有限责任公司 System upgrading method and apparatus
CN105357031A (en) * 2015-09-30 2016-02-24 青岛海信移动通信技术股份有限公司 OTA (over the air) upgrade method and device
CN105700917A (en) * 2016-01-04 2016-06-22 浪潮通用软件有限公司 Method and apparatus for synchronizing DLL and database
CN105718268A (en) * 2016-01-22 2016-06-29 青岛海信移动通信技术股份有限公司 Method and device for verifying OTA multi-pack upgrading
CN105809055A (en) * 2016-02-26 2016-07-27 深圳天珑无线科技有限公司 Access control method and device, and related equipment
CN105809055B (en) * 2016-02-26 2019-03-22 深圳天珑无线科技有限公司 Access control method, device and relevant device

Also Published As

Publication number Publication date
CN107193612B (en) 2021-03-23
CN107239288A (en) 2017-10-10
CN107239288B (en) 2021-03-30
CN104052818B (en) 2017-07-11
CN107193612A (en) 2017-09-22

Similar Documents

Publication Publication Date Title
CN104052818A (en) Version upgrade method and device for mobile terminal
CN104166565B (en) A kind of intelligent display terminal firmware upgrade method
US8560823B1 (en) Trusted modular firmware update using digital certificate
CN105138347A (en) Difference upgrade patch generating method, software upgrading method and corresponding apparatus
US7350205B2 (en) Upgrading electronic files of a mobile device upgrade client
TWI518595B (en) Method and system of software update and mobile device
US20070061800A1 (en) System and method for updating software in a network device
US9984255B2 (en) Methods and apparatus to enable runtime checksum verification of block device images
CN106201607A (en) The upgrade method of a kind of software version and equipment
CN106572372A (en) Set-top box upgrading method and set-top box
CN109829294B (en) Firmware verification method, system, server and electronic equipment
CN102227732A (en) Method, apparatus, and computer program product for managing software versions
WO2009157133A1 (en) Information processing device, information processing method, and computer program and integrated circuit for the realization thereof
TW201621647A (en) Operating system updating method
US20180217831A1 (en) Method and apparatus for secure multi-cycle vehicle software updates
CN105045640A (en) Software upgrading method and apparatus and intelligent device
CN104572169B (en) A kind of software distribution and installation system based on UEFI
CN105700918A (en) System upgrading method and device
CN107203379B (en) A kind of preset, the installation method of Android customized application APP
WO2018032757A1 (en) Method and device for updating component
CN105808273A (en) Software upgrading method and software upgrading device
CN106210877A (en) The method for upgrading system of intelligent television and device
CN102880478B (en) Oftware updating method
CN106886436B (en) Android system upgrading method and device
CN106293814B (en) Upgrading method and device

Legal Events

Date Code Title Description
PB01 Publication
C06 Publication
SE01 Entry into force of request for substantive examination
C10 Entry into substantive examination
GR01 Patent grant
GR01 Patent grant