CN104052818B - The version upgrading method and device of a kind of mobile terminal - Google Patents
The version upgrading method and device of a kind of mobile terminal Download PDFInfo
- Publication number
- CN104052818B CN104052818B CN201410299466.6A CN201410299466A CN104052818B CN 104052818 B CN104052818 B CN 104052818B CN 201410299466 A CN201410299466 A CN 201410299466A CN 104052818 B CN104052818 B CN 104052818B
- Authority
- CN
- China
- Prior art keywords
- upgrade file
- file
- mobile terminal
- intermediate releases
- version
- 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.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols 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/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Stored Programmes (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses the version upgrading method and device of a kind of mobile terminal, it is used to solve verify failure caused by target version in the prior art is inconsistent with the key signatures of user terminal, it is impossible to the problem of completion system upgrading, the method is：System upgrade file is obtained, intermediate releases upgrade file and target version upgrade file are at least carried in the system upgrade file；The public key file of user terminal is obtained, and according to the intermediate releases upgrade file carried in the public key file and system upgrade file, the system of user terminal is upgraded into intermediate releases by current version；After confirming to upgrade successfully, continue, according to the target version upgrade file carried in system upgrade file, the system of user terminal to be upgraded into target version by intermediate releases.So, when intermediate releases are upgraded to target version, it is not necessary to which public key file and the signing messages of target version to user terminal are verified, it is ensured that the system of user terminal can complete edition upgrading.
Description
Technical field
The present invention relates to the online upgrading field of mobile terminal, more particularly to a kind of mobile terminal version upgrading method and
Device.
Background technology
After mobile terminal listing, some system problems are may find that during the use of user, mobile terminal is solution
A series of system problems occurred after certainly listing, sophisticated systems function, the later stage can be issued and a series of be for this mobile terminal
System upgraded version.User settles a dispute by the parties concerned themselves system upgrade problem for convenience, mobile terminal manufacturer problem can be repaired after system
Upgraded version boil down to is downloaded (Over The Air, OTA) AKU and is put on server in the air, facilitates user to pass through mobile whole
The online upgrading function at end, is upgraded to newest version.
At present, mobile terminal can only download the AKU of the manufacturer of the mobile terminal, specifically in system upgrade
For：Mobile terminal is signed by key and AKU is verified, only just can be as by the AKU of key signature authentications
AKU trusty moves terminal system upgrading, and security of system energy is caused so as to avoid to be utilized by Malware
Problem.For third-party testing requirement and the consideration of secure context, usual mobile terminal is needed according to key in system upgrade
Signature OTA AKUs are verified, i.e., from the Recovery mirror image root file systems of mobile terminal /res/keys loading
Public key source file, then loading is embedded in RSA signature information in OTA AKUs, and with the public key source document that preserves in/res/keys
Part is matched, if the match is successful, system upgrade is carried out according to OTA AKUs, and otherwise, OTA upgradings are exited in verification failure.
However, the key signatures used such as current mobile terminal must not be cracked is changed without signature, or developer is compiling
When translating redaction AKU, T card versions will be generated and exchanged with the order of generation OTA AKUs, or used in mk files
Testkey, cause AKU inconsistent with the signing messages of mobile terminal etc., then the verification according to key signatures to OTA AKUs
Will verification failure, cause mobile terminal cannot completion system upgrade.
The content of the invention
The embodiment of the present invention cannot be complete caused by failing due to AKU signature check present in solution prior art
Into the technical problem of system upgrade, there is provided the version upgrading method and device of a kind of mobile terminal, can both avoid due to AKU
Signature check failure caused by cannot completion system upgrading, while can guarantee that the security of AKU again.
Concrete technical scheme provided in an embodiment of the present invention is as follows：
A kind of version upgrading method of mobile terminal, including：
System upgrade file is obtained, intermediate releases upgrade file and target version upgrading are carried in the system upgrade file
File, wherein, the intermediate releases upgrade file is the first version of the target version upgrade file, the intermediate releases liter
The signing messages of level file is corresponding with the public key file of mobile terminal, and the ROMPaq in the intermediate releases upgrade file
Verification data is not carried, the ROMPaq in the target version upgrade file carries verification data；
The public key file of mobile terminal is obtained, and according to the public key file and the signature of the intermediate releases upgrade file
Information, intermediate releases are upgraded to by the system of the mobile terminal by current version；
After confirming to upgrade successfully, continue according to the target version upgrade file, by the system of the mobile terminal by
The intermediate releases upgrade to target version.
In this way, target version is upgraded to again by the way that mobile terminal is upgraded into intermediate releases first, wherein,
When intermediate releases are upgraded to target version, it is not necessary to carry out school to the public key file of mobile terminal and the signing messages of target version
Test, so as to avoid target version caused verification failure inconsistent with the key signatures of mobile terminal, it is impossible to which completion system is upgraded
Problem.
It is preferred that the intermediate releases upgrade file is the upgrading difference bag relative to mobile terminal current version.
It is preferred that the intermediate releases upgrade file is the full bag of upgrading.
It is preferred that system upgrade file is obtained, including：
According to the priority of default system upgrade file, after obtaining the intermediate releases upgrade file, then obtain described
Target version upgrade file.
In this way, target version upgrade file is obtained again after can first obtaining intermediate releases upgrade file.
It is preferred that further including：
If the system of the mobile terminal is upgraded into target version by the intermediate releases failing, will be described mobile whole
The system at end retracts to the intermediate releases, and deletes the target version upgrade file in the system upgrade file.
In this way, when the system upgrade of mobile terminal fails to target version, during system has still been upgraded to
Between version, it is ensured that system renewal upgrading.
A kind of version upgrading method of mobile terminal, including：
Receive the system upgrade request of mobile terminal；
System upgrade file is determined according to system upgrade request, and the system upgrade file is sent to the shifting
Dynamic terminal, carries intermediate releases upgrade file and target version upgrade file in the system upgrade file, wherein, the centre
Edition upgrading file is the first version of the target version upgrade file, the signature of the intermediate releases upgrade file with it is described
The public key file of mobile terminal is corresponding, and ROMPaq in the intermediate releases upgrade file does not carry verification data, institute
The ROMPaq stated in target version upgrade file carries verification data.
In this way, by intermediate releases upgrade file and target version upgrade file sending value mobile terminal, it is ensured that
Mobile terminal is upgraded to target version again after being upgraded to intermediate releases first, wherein, it is upgraded to target version in intermediate releases
When, it is not necessary to public key file and the signing messages of target version to mobile terminal are verified, so as to avoid target version
Verification failure caused by inconsistent with the key signatures of mobile terminal, it is impossible to the problem of completion system upgrading.
Preferably the intermediate releases upgrade file is the upgrading difference bag relative to mobile terminal current version.
It is preferred that the intermediate releases upgrade file is the full bag of upgrading.
A kind of edition upgrading device of mobile terminal, including：
Acquiring unit, for obtaining system upgrade file, carries intermediate releases upgrade file in the system upgrade file
With target version upgrade file, wherein, the intermediate releases upgrade file is the first version of the target version upgrade file,
The signing messages of the intermediate releases upgrade file is corresponding with the public key file of mobile terminal, and intermediate releases upgrading text
ROMPaq in part does not carry verification data, and the ROMPaq in the target version upgrade file carries verification data；
First upgrade unit, the public key file for obtaining mobile terminal, and according to the public key file and the centre
The signing messages of edition upgrading file, intermediate releases are upgraded to by the system of the mobile terminal by current version；
Second upgrade unit, for after confirming to upgrade successfully, continuing according to the target version upgrade file, will be described
The system of mobile terminal upgrades to target version by the intermediate releases.
So, target version is upgraded to again by the way that mobile terminal is upgraded into intermediate releases first, wherein, in intermediate releases
When being upgraded to target version, it is not necessary to which public key file and the signing messages of target version to mobile terminal are verified, so that
Avoid target version caused verification failure inconsistent with the key signatures of mobile terminal, it is impossible to the problem of completion system upgrading.
It is preferred that the intermediate releases upgrade file is the upgrading difference bag relative to mobile terminal current version.
It is preferred that the intermediate releases upgrade file is the full bag of upgrading.
It is preferred that the acquiring unit obtains system upgrade file, including：
According to the priority of default system upgrade file, after obtaining the intermediate releases upgrade file, then obtain described
Target version upgrade file.
So, acquiring unit obtains target version upgrade file again after can first obtaining intermediate releases upgrade file.
It is preferred that second upgrade unit, is further used for：
If the system of the mobile terminal is upgraded into target version by the intermediate releases failing, will be described mobile whole
The system at end retracts to the intermediate releases, and deletes the target version upgrade file in the system upgrade file.
So, the second upgrade unit can be when the system upgrade of mobile terminal to target version fails, and system still rises
Level has arrived intermediate releases, it is ensured that the renewal upgrading of system.
A kind of edition upgrading device of mobile terminal, including：
Receiving unit, the system upgrade for receiving mobile terminal is asked；
Transmitting element for determining system upgrade file and the system upgrade is literary according to system upgrade request
Part is sent to the mobile terminal, and intermediate releases upgrade file and target version upgrading text are carried in the system upgrade file
Part, wherein, the intermediate releases upgrade file is the first version of the target version upgrade file, the intermediate releases upgrading
The signature of file is corresponding with the public key file of the mobile terminal, and ROMPaq in the intermediate releases upgrade file is not
Verification data is carried, the ROMPaq in the target version upgrade file carries verification data.
So, server is by intermediate releases upgrade file and target version upgrade file sending value mobile terminal, it is ensured that
Mobile terminal is upgraded to target version again after being upgraded to intermediate releases first, wherein, when intermediate releases are upgraded to target version,
The public key file of mobile terminal and the signing messages of target version need not be verified, so as to avoid target version and move
Verification failure caused by the key signatures of dynamic terminal are inconsistent, it is impossible to the problem of completion system upgrading.
It is preferred that the intermediate releases upgrade file is the upgrading difference bag relative to mobile terminal current version.
It is preferred that the intermediate releases upgrade file is the full bag of upgrading.
Using technical solution of the present invention, mobile terminal is upgraded to during intermediate releases by current version, due to current version
This is consistent with the signature of intermediate releases, therefore by verifying and can be upgraded to intermediate releases.By intermediate edition upgrading to mesh
During mark version, because the Recovery in intermediate releases is without key verifying functions, in this manner it is ensured that mobile whole
End with upgrading packet signature it is inconsistent in the case of can still be upgraded with completion system, and be upgraded in final version in Recovery
It is that with key verifying functions, can so ensure the security of AKU, makes the system still can be normal in subsequent process
Upgrading.
Brief description of the drawings
Fig. 1 is a kind of specific stream of the version upgrading method of mobile terminal of mobile terminal side provided in an embodiment of the present invention
Cheng Tu；
Fig. 2 is a kind of idiographic flow of the version upgrading method of mobile terminal of server side provided in an embodiment of the present invention
Figure；
Fig. 3 is that a kind of structure of the edition upgrading device of mobile terminal of mobile terminal side provided in an embodiment of the present invention is shown
It is intended to；
Fig. 4 is a kind of structural representation of the edition upgrading device of mobile terminal of server side provided in an embodiment of the present invention
Figure.
Specific embodiment
Using technical solution of the present invention, can be effectively prevented from present in prior art because key signature checks fail
It is caused cannot completion system upgrading, and then cause the insurmountable problem of defect that system is present in mobile terminal.
A kind of version upgrading method of mobile terminal is the embodiment of the invention provides, all kinds of intelligent mobile terminals are applied to,
Such as smart mobile phone, the terminal device such as intelligent television is described in detail to the preferred embodiment of the present invention below in conjunction with the accompanying drawings.
Refering to shown in Fig. 1, a kind of version upgrading method of mobile terminal of mobile terminal side provided in an embodiment of the present invention
Specific handling process include：
Step 101：System upgrade file is obtained, intermediate releases upgrade file and mesh are at least carried in the system upgrade file
Mark edition upgrading file, wherein, the intermediate releases upgrade file is the first version of target version upgrade file, intermediate releases liter
The signing messages of level file is corresponding with the public key file of mobile terminal, and ROMPaq in intermediate releases upgrade file is not taken
Tape verifying data, the ROMPaq in target version upgrade file carries verification data.
In actual applications, mobile terminal manufacturer can periodically constantly by mobile terminal improve after system upgrade file
Upload onto the server, usual system upgrade file is uploaded onto the server in the form of OTA AKUs.
After mobile terminal sets up connection with corresponding server, system upgrade text is obtained by local online upgrading function
Part, i.e. OTA AKUs.
Wherein, OTA AKUs are usually two types, a kind of for OTA is wrapped entirely, i.e., be comprising all applications of whole system
System upgrade file, another kind is OTA difference bags, i.e., only comprising the system liter for needing (the changing) of upgrading several applications
Level file.OTA difference bags are wrapped entirely relative to OTA, generally smaller.
The intermediate releases upgrade file of acquisition for mobile terminal be relative to mobile terminal current version upgrading difference bag (i.e.
OTA difference bag), or be the full bag of upgrading (i.e. OTA is wrapped entirely).
For example, the difference between version A and version B, version B has the certain applications to need to improve relative to version A, then OTA
Difference bag contains only the upgrade file for needing improved these certain applications, if the current system of mobile terminal is version A, need
When being upgraded to version B, after mobile terminal determines online upgrading, the OTA difference bags of system meeting download version A and version B are
After system installation, version B will be directly upgraded to, in addition, mobile terminal can bag be risen entirely with the OTA of download version B
Level.
When acquisition for mobile terminal system upgrade file, (i.e. the OTA of latest edition is complete to obtain target version upgrade file
Bag), and intermediate releases upgrade file (OTA is wrapped or OTA difference bag entirely), wherein, the intermediate releases upgrade file is target version
The first version of this upgrade file.
Signing messages in intermediate releases upgrade file should be consistent with the signing messages of mobile terminal, i.e., in compiling
During intermediate releases upgrade file, its signing messages is set corresponding with signing messages or public key the file holding of mobile terminal.
Wherein, the ROMPaq in intermediate releases upgrade file --- in Recovery files, be without verification data,
And verification data is carried in the Recovery files in target version upgrade file.In this manner it is ensured that updating mobile terminal is arrived
After intermediate releases, because the ROMPaq in intermediate releases upgrade file is without verification data, it is not used in carrying out signing messages testing
Card just can directly upgrade to target version, and after being upgraded to target version, inspection can be proceeded in subsequent upgrade, protect
The security of mobile terminal system is demonstrate,proved.
When obtaining system upgrade file, according to the priority of default system upgrade file, intermediate releases upgrading text is obtained
After part, then obtain target version upgrade file.
Preferably, the system upgrade request that can be sent according to mobile terminal, sets the preferential of intermediate releases upgrade file
Level is higher than target version upgrade file, so, can preferentially download intermediate releases upgrade file, it is determined that under continuing after the completion of downloading
Carry target version upgrade file.
Step 102：The public key file of mobile terminal is obtained, and according to the public key file and the label of intermediate releases upgrade file
Name information, intermediate releases are upgraded to by the system of mobile terminal by current version.
Preferably, when performing step 102, following steps are specifically included：
Verified for the signing messages in intermediate releases upgrade file in public key file and system upgrade file, when sentencing
When signing messages in the fixed intermediate releases upgrade file is corresponding with the public key file, according to the intermediate releases upgrade file,
The system of mobile terminal is upgraded into intermediate releases by current version.
Specifically, when obtaining the public key file of mobile terminal, including, from the version of mobile terminal current system
Recovery mirror image root file systems /res/keys loading public key files.
It is first when being verified for the signing messages in intermediate releases upgrade file in public key file and system upgrade file
First loading is embedded in RSA signature information in intermediate releases upgrade file (i.e. OTA AKUs), then by the RSA signature information with/
The public key file preserved in res/keys is matched, if verification passes through, the system of mobile terminal can be upgraded by current version
To intermediate releases.
Step 103：After confirming to upgrade successfully, continue according to target version upgrade file, by the system of mobile terminal by
Intermediate releases upgrade to target version.
Wherein, according to the target version upgrade file carried in system upgrade file, by the system of mobile terminal by centre
Edition upgrading is target version, including：
Based on the ROMPaq in intermediate releases, will be moved according to the target version upgrade file carried in system upgrade file
The system of dynamic terminal upgrades to target version by intermediate releases.
Specifically, in the system according to target version upgrade file update mobile terminal, due to intermediate releases upgrading journey
Be in Recovery files in sequence without verifying function, therefore need not be directed to mobile terminal public key file and the target
Signing messages in edition upgrading file is verified, but is by mobile terminal directly by the target version upgrade file
System is upgraded.So, it is to avoid because key signatures differ between the public key file of target version upgrade file and mobile terminal
Cause cause verification fail, caused by entering cannot completion system upgrading phenomenon.
Further, fail if the system of mobile terminal is upgraded into target version by intermediate releases, by mobile terminal
System retract to intermediate releases, and delete the target version upgrade file in upgrade file.
So, in the case where mobile terminal fails when target version is upgraded to, the system of mobile terminal is still upgraded
Intermediate releases are arrived, relative to version before, system has still carried out upgrading and improved.
For example, the system of current mobile terminal is version B (signature is key2), the target version of upgrading is version C (signatures
It is key1), the version issued in the past is A (signature is key1), if system is directly upgraded to version C by mobile terminal from version B,
During upgrading, because the signature in version B and version C is inconsistent, therefore cannot be by signature check, failure of upgrading.Therefore, set
One intermediate releases --- version C0, but do not include key signature check functions in Recovery in version C0.Then also need
Making the OTA difference bags of a version B to version C0 --- (i.e. intermediate releases upgrade file, sign is version B- versions C0
Key2), because the signature of version B and version B- versions C0 is key2, therefore, signature check can lead in escalation process
Cross, mobile terminal can be upgraded to version C0, after updating mobile terminal is to C0, system detects that the OTA of target version C is complete again
Bag, although the key1 signatures of version C, but during due to upgrading, key signature check work(is not included in the Recovery of version C0
Can, therefore can directly upgrade without signature check, finally it is upgraded to target version.Wherein, the generation of version B- versions C0
Process is：The corresponding intermediate file src.zip of version A for issue in the past are needed, by ordering " java-Xmx2048m-
jar signapk.jar-w key2/releasekey.x509.pem key2/releasekey.pk8src.zip
Target.zip " is signed with key2 and is formed target.zip again, then compiles being signed with key2 for generation before again
The intermediate file for crossing name is combined with target.zip, forms final intermediate releases upgrade file version B- versions 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 system is directly upgraded to version F from version d by mobile terminal, during upgrading, due to version d and version
Signature in F is inconsistent, therefore cannot be by signature check, failure of upgrading.Therefore, an intermediate releases --- version E is set,
Wherein, version E is wrapped for OTA entirely, and it is key_old to sign, and does not include key signature check functions in Recovery in version E.
Then after the OTA of mobile terminal download version E is wrapped entirely, because the signature of version d and version E is key_old, therefore, rising
Signature check can pass through during level, and mobile terminal can be upgraded to version E, and after updating mobile terminal is to E, system is examined again
The OTA for surveying target version F is wrapped entirely, although the key_new signatures of version F, but during due to upgrading, the Recovery of version E
In do not include key signature check functions, therefore can be without signature check, directly upgrading, is finally upgraded to target version F.
Target version upgrade file is necessary for full bag of upgrading, because target version and intermediate releases signing messages are inconsistent,
If still selecting upgrading difference bag to be upgraded, the signature of the application do not upgraded after having upgraded is consistent with intermediate releases, and after upgrading
Application signature it is consistent with target version, can cause the application after upgrading that operation exception occurs.
Needed by key during mobile terminal is upgraded to intermediate releases by current version by the embodiment of the present invention
Recovery in signature check, and the intermediate releases be without key verifying functions, in this manner it is ensured that mobile terminal with
Can still be upgraded with completion system in the case that upgrading packet signature is inconsistent, and it is to carry to be upgraded in final version in Recovery
Key verifying functions, can so ensure the security of AKU, system still can be normally upgraded in subsequent process.
Based on above-described embodiment, refering to shown in Fig. 2, the embodiment of the present invention additionally provides a kind of mobile terminal of server side
Version upgrading method, the specific handling process of the method includes：
Step 201：Receive the system upgrade request of mobile terminal.
Step 202：System upgrade file is determined according to system upgrade request, and system upgrade file is sent to movement eventually
End, carries intermediate releases upgrade file and target version upgrade file in system upgrade file, wherein, intermediate releases upgrade file
It is the first version of target version upgrade file, the signature of intermediate releases upgrade file is relative with the public key file of mobile terminal
Should, and ROMPaq in intermediate releases upgrade file does not carry verification data, the ROMPaq in target version upgrade file
Carry verification data.
Intermediate releases upgrade file is the upgrading difference bag relative to mobile terminal current version, or the full bag of upgrading.
Based on above-described embodiment, refering to shown in Fig. 3, one kind that the embodiment of the present invention additionally provides mobile terminal side is mobile eventually
The edition upgrading device at end, the device includes：Acquiring unit 301, the first upgrade unit 302 and the second upgrade unit 303, its
In,
Acquiring unit 301, 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 first version of target version upgrade file, intermediate releases liter
The signing messages of level file is corresponding with the public key file of mobile terminal, and ROMPaq in intermediate releases upgrade file is not taken
Tape verifying data, the ROMPaq in target version upgrade file carries verification data；
First upgrade unit 302, the public key file for obtaining mobile terminal, and according to public key file and intermediate releases liter
The signing messages of level file, intermediate releases are upgraded to by the system of mobile terminal by current version；
Second upgrade unit 303, for after confirming to upgrade successfully, continuing according to target version upgrade file, by movement
The system of terminal upgrades to target version by intermediate releases.
Intermediate releases upgrade file is the upgrading difference bag relative to mobile terminal current version.
Intermediate releases upgrade file is the full bag of upgrading.
Acquiring unit 301 obtains system upgrade file, including：
According to the priority of default system upgrade file, after obtaining intermediate releases upgrade file, then target version is obtained
Upgrade file.
Second upgrade unit 303, is further used for：
If the system of mobile terminal is upgraded into target version by intermediate releases to fail, the system of mobile terminal is retracted
Target version upgrade file into intermediate releases, and deletion system upgrade file.
Based on above-described embodiment, refering to shown in Fig. 4, the embodiment of the present invention additionally provides a kind of mobile terminal of server side
Edition upgrading device, the device includes：Receiving unit 401 and transmitting element 402, wherein,
Receiving unit 401, the system upgrade for receiving mobile terminal is asked；
Transmitting element 402, for determining system upgrade file according to system upgrade request, and system upgrade file is sent
To mobile terminal, intermediate releases upgrade file and target version upgrade file are carried in system upgrade file, wherein, intermediate releases
Upgrade file is the first version of target version upgrade file, the signature of intermediate releases upgrade file and the public key text of mobile terminal
Part is corresponding, and ROMPaq in intermediate releases upgrade file does not carry verification data, the liter in target version upgrade file
Level program carries verification data.
Intermediate releases upgrade file is the upgrading difference bag relative to mobile terminal current version.
Intermediate releases upgrade file is the full bag of upgrading.
In sum, the version upgrading method and device of a kind of mobile terminal by being provided in the embodiment of the present invention, should
Method includes intermediate releases upgrade file and target version upgrade file by obtaining, by the system of mobile terminal by current version
Intermediate releases are upgraded to, are finally realized updating mobile terminal to target version, so, be upgraded to first by by mobile terminal
Intermediate releases are upgraded to target version again, wherein, when intermediate releases are upgraded to target version, it is not necessary to the public affairs of mobile terminal
Key file is verified with the signing messages of target version, so as to avoid due to AKU signature check failure caused by cannot
Completion system is upgraded, while can guarantee that the security of AKU again.
, but those skilled in the art once know basic creation although preferred embodiments of the present invention have been described
Property concept, then can make other change and modification to these embodiments.So, appended claims are intended to be construed to include excellent
Select embodiment and fall into having altered and changing for the scope of the invention.
Obviously, those skilled in the art can carry out various changes and modification without deviating from this hair to the embodiment of the present invention
The spirit and scope of bright embodiment.So, if these modifications of the embodiment of the present invention and modification belong to the claims in the present invention
And its within the scope of equivalent technologies, then the present invention is also intended to comprising these changes and modification.
Claims (16)
1. a kind of version upgrading method of mobile terminal, it is characterised in that including：
System upgrade file is obtained, intermediate releases upgrade file and target version upgrading text are carried in the system upgrade file
Part, wherein, the intermediate releases upgrade file is the first version of the target version upgrade file, the intermediate releases upgrading
The signing messages of file is corresponding with the public key file of mobile terminal, and ROMPaq in the intermediate releases upgrade file is not
Verification data is carried, the ROMPaq in the target version upgrade file carries verification data；
The public key file of mobile terminal is obtained, and according to the public key file and the A.L.S. of the intermediate releases upgrade file
Breath, intermediate releases are upgraded to by the system of the mobile terminal by current version；
After confirming to upgrade successfully, continue according to the target version upgrade file, by the system of the mobile terminal by described
Intermediate releases upgrade to target version.
2. the method for claim 1, it is characterised in that the intermediate releases upgrade file is to work as relative to mobile terminal
The upgrading difference bag of preceding version.
3. the method for claim 1, it is characterised in that the intermediate releases upgrade file is the full bag of upgrading.
4. the method as described in claim any one of 1-3, it is characterised in that obtain system upgrade file, including：
According to the priority of default system upgrade file, after obtaining the intermediate releases upgrade file, then the target is obtained
Edition upgrading file.
5. the method as described in claim any one of 1-3, it is characterised in that further include：
If the system of the mobile terminal is upgraded into target version by the intermediate releases to fail, by the mobile terminal
System retracts to the intermediate releases, and deletes the target version upgrade file in the system upgrade file.
6. a kind of version upgrading method of mobile terminal, it is characterised in that including：
Receive the system upgrade request of mobile terminal；
System upgrade file is determined according to system upgrade request, and the system upgrade file is sent to the movement eventually
End, carries intermediate releases upgrade file and target version upgrade file in the system upgrade file, wherein, the intermediate releases
Upgrade file is the first version of the target version upgrade file, signature and the movement of the intermediate releases upgrade file
The public key file of terminal is corresponding, and ROMPaq in the intermediate releases upgrade file does not carry verification data, the mesh
ROMPaq in mark edition upgrading file carries verification data.
7. method as claimed in claim 6, it is characterised in that the intermediate releases upgrade file is to work as relative to mobile terminal
The upgrading difference bag of preceding version.
8. method as claimed in claim 6, it is characterised in that the intermediate releases upgrade file is the full bag of upgrading.
9. the edition upgrading device of a kind of mobile terminal, it is characterised in that including：
Acquiring unit, for obtaining system upgrade file, carries intermediate releases upgrade file and mesh in the system upgrade file
Mark edition upgrading file, wherein, the intermediate releases upgrade file is the first version of the target version upgrade file, described
The signing messages of intermediate releases upgrade file is corresponding with the public key file of mobile terminal, and in the intermediate releases upgrade file
ROMPaq do not carry verification data, ROMPaq in the target version upgrade file carries verification data；
First upgrade unit, the public key file for obtaining mobile terminal, and according to the public key file and the intermediate releases
The signing messages of upgrade file, intermediate releases are upgraded to by the system of the mobile terminal by current version；
Second upgrade unit, for after confirming that current version upgrades to intermediate releases, continuing to be upgraded according to the target version
File, target version is upgraded to by the system of the mobile terminal by the intermediate releases.
10. device as claimed in claim 9, it is characterised in that the intermediate releases upgrade file is relative to mobile terminal
The upgrading difference bag of current version.
11. devices as claimed in claim 9, it is characterised in that the intermediate releases upgrade file is the full bag of upgrading.
12. device as described in claim any one of 9-11, it is characterised in that the acquiring unit obtains system upgrade text
Part, including：
According to the priority of default system upgrade file, after obtaining the intermediate releases upgrade file, then the target is obtained
Edition upgrading file.
13. device as described in claim any one of 9-11, it is characterised in that second upgrade unit, is further used for：
If the system of the mobile terminal is upgraded into target version by the intermediate releases to fail, by the mobile terminal
System retracts to the intermediate releases, and deletes the target version upgrade file in the system upgrade file.
A kind of edition upgrading device of 14. mobile terminals, it is characterised in that including：
Receiving unit, the system upgrade for receiving mobile terminal is asked；
Transmitting element, for determining system upgrade file according to system upgrade request, and the system upgrade file is sent out
The mobile terminal is delivered to, intermediate releases upgrade file and target version upgrade file are carried in the system upgrade file, its
In, the intermediate releases upgrade file is the first version of the target version upgrade file, the intermediate releases upgrade file
Signature it is corresponding with the public key file of the mobile terminal, and ROMPaq in the intermediate releases upgrade file do not carry
Verification data, the ROMPaq in the target version upgrade file carries verification data.
15. devices as claimed in claim 14, it is characterised in that the intermediate releases upgrade file is relative to mobile terminal
The upgrading difference bag of current version.
16. devices as claimed in claim 14, it is characterised in that the intermediate releases upgrade file is the full bag of upgrading.
Priority Applications (3)
| 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 |
| CN201710426362.0A CN107193612B (en) | 2014-06-27 | 2014-06-27 | Version upgrading method and device for mobile terminal |
| CN201710426363.5A CN107239288B (en) | 2014-06-27 | 2014-06-27 | Version upgrading method and device for mobile terminal |
Applications Claiming Priority (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 |
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 CN104052818A (en) | 2014-09-17 |
| CN104052818B true CN104052818B (en) | 2017-07-11 |
Family
ID=51505169
Family Applications (3)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710426363.5A Active CN107239288B (en) | 2014-06-27 | 2014-06-27 | Version upgrading method and device for mobile terminal |
| CN201710426362.0A Active CN107193612B (en) | 2014-06-27 | 2014-06-27 | Version upgrading method and device for mobile terminal |
| CN201410299466.6A Active CN104052818B (en) | 2014-06-27 | 2014-06-27 | The version upgrading method and device of a kind of mobile terminal |
Family Applications Before (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710426363.5A Active CN107239288B (en) | 2014-06-27 | 2014-06-27 | Version upgrading method and device for mobile terminal |
| CN201710426362.0A Active CN107193612B (en) | 2014-06-27 | 2014-06-27 | Version upgrading method and device for mobile terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (3) | CN107239288B (en) |
Families Citing this family (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104778057A (en) * | 2015-03-11 | 2015-07-15 | 小米科技有限责任公司 | Terminal system upgrading method and device, and server |
| 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 |
| CN105068848B (en) * | 2015-08-28 | 2018-12-11 | 小米科技有限责任公司 | Method for upgrading system and device |
| 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 |
| CN105809055B (en) * | 2016-02-26 | 2019-03-22 | 深圳天珑无线科技有限公司 | Access control method, device and relevant device |
| CN108170461B (en) * | 2017-12-28 | 2021-07-27 | 北京四达时代软件技术股份有限公司 | Differential upgrade package generation method, differential upgrade method and device |
| CN111736859B (en) * | 2019-03-25 | 2023-08-01 | 成都鼎桥通信技术有限公司 | Version updating method of operating system, server and terminal |
| CN110377308A (en) * | 2019-07-18 | 2019-10-25 | 上海擎感智能科技有限公司 | Data updating method, system |
| CN110597542B (en) * | 2019-09-17 | 2023-01-31 | Oppo（重庆）智能科技有限公司 | Software automatic OTA (over the air) upgrading method and device and electronic equipment |
| CN111427609A (en) * | 2020-04-01 | 2020-07-17 | 山东汇贸电子口岸有限公司 | Automatic application upgrading method based on multi-node server |
| CN111478897A (en) * | 2020-04-03 | 2020-07-31 | 爱瑟福信息科技(上海)有限公司 | OTA (over the air) upgrading method and system for vehicle ECU (electronic control Unit) |
| CN112148330A (en) * | 2020-09-23 | 2020-12-29 | 南京爱奇艺智能科技有限公司 | Target equipment system upgrading method and device |
| CN112162770B (en) * | 2020-10-20 | 2023-11-10 | 深圳技术大学 | Firmware version upgrading method and device for realizing integrity verification based on block chain |
| CN115883359A (en) * | 2022-10-26 | 2023-03-31 | 深圳市兆珑科技有限公司 | Upgrade installation method and device, system, electronic equipment and storage medium thereof |
Citations (6)
| 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)
| 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 |
| CA2675351C (en) * | 2008-10-08 | 2015-05-19 | 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 |
| US8756617B1 (en) * | 2010-05-18 | 2014-06-17 | Google Inc. | Schema validation for secure development of browser extensions |
| 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 |
-
2014
- 2014-06-27 CN CN201710426363.5A patent/CN107239288B/en active Active
- 2014-06-27 CN CN201710426362.0A patent/CN107193612B/en active Active
- 2014-06-27 CN CN201410299466.6A patent/CN104052818B/en active Active
Patent Citations (6)
| 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107193612B (en) | 2021-03-23 |
| CN107239288A (en) | 2017-10-10 |
| CN104052818A (en) | 2014-09-17 |
| CN107193612A (en) | 2017-09-22 |
| CN107239288B (en) | 2021-03-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104052818B (en) | The version upgrading method and device of a kind of mobile terminal | |
| CN104346167B (en) | The method and device of channel bag is applied in generation | |
| US20070061800A1 (en) | System and method for updating software in a network device | |
| US7907531B2 (en) | Apparatus and methods for managing firmware verification on a wireless device | |
| CN103309768B (en) | Method and device for repairing system files | |
| JP2015092374A5 (en) | ||
| JP5357152B2 (en) | Information processing apparatus, information processing method, computer program and integrated circuit for realizing the same | |
| JP2012084159A5 (en) | ||
| CN110557452B (en) | Node management method and device of block chain, storage medium and computer equipment | |
| JP2008547092A5 (en) | ||
| CN103412767A (en) | Method and system for recognizing and upgrading application version | |
| CN106161336A (en) | A kind of information updating method, Apparatus and system | |
| WO2016058350A1 (en) | Base station software version management method and device | |
| CN104699511B (en) | Plug-in unit upgrade method and device | |
| CN105808273B (en) | Method for upgrading software and software updating apparatus | |
| CN107643882A (en) | The storage and restoration methods of a kind of data reliability, system and storage device | |
| CN107301343A (en) | Secure data processing method, device and electronic equipment | |
| CN107239299A (en) | Plug-in unit upgrade method and device | |
| CN106210877A (en) | The method for upgrading system of intelligent television and device | |
| CN108280341A (en) | Channel number addition, installation kit method of calibration and device | |
| CN106250548A (en) | A kind of code update method | |
| KR20080083512A (en) | Firmware over the air system | |
| CN108170461A (en) | Difference upgrade package generation method, difference upgrade method and device | |
| CN104572169B (en) | A kind of software distribution and installation system based on UEFI | |
| CN105589718A (en) | System updating method and updating apparatus for intelligent device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |