CN101247268A - Synchronization method and apparatus of terminal system version - Google Patents
Synchronization method and apparatus of terminal system version Download PDFInfo
- Publication number
- CN101247268A CN101247268A CNA2008100811190A CN200810081119A CN101247268A CN 101247268 A CN101247268 A CN 101247268A CN A2008100811190 A CNA2008100811190 A CN A2008100811190A CN 200810081119 A CN200810081119 A CN 200810081119A CN 101247268 A CN101247268 A CN 101247268A
- Authority
- CN
- China
- Prior art keywords
- version
- backup
- information
- upgrade
- version information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Abstract
The present invention discloses a synchronization process of a terminal system version, which includes: preserving first version information correspond to operation version and second version information correspond to backup version on terminal; judging whether or not update backup version into operation version by comparing first version information and second version information; if need update, operation version is replicated to storage zone of backup version and cover the backup version. Furthermore, the present invention also discloses a synchronization device of terminal system version. Two system version consistency is effective remained by using the invention without affecting normal use, and two version backup is realized in true meaning, thereby safety and reliability of terminal system and user experience are improved.
Description
Technical field
The present invention relates to the communications field, and especially, relate to a kind of method for synchronous and device of terminal system version.
Background technology
In computer application system and embedded system, online upgrading is common operation.For reliability and the ease for use that improves online upgrading, system adopts usually and preserve two versions in system storage, and one of them is operation version, another backup version.Common online upgrading process as shown in Figure 1, that is, and in when upgrading, operation version and long-range server alternately, the download redaction is also finished with redaction and is upgraded the backup version zone, and for the backup version of redaction becomes the operation of operation version, former operation version then becomes backup version then.When the operation version lost efficacy, backup version as new operation version operation, is substituted the operation version that lost efficacy.
Yet there is following problem in this method: if backup version lost efficacy, at this moment, if the operation version had also lost efficacy, the version reliability of operation can't be guaranteed (1); (2) operation version and backup version can not be consistent, can there be version situation inequality, even situation widely different between the version can occur, in this case, if the operation version lost efficacy and the backup version of utilization and operation, can user's normal use be had a negative impact.
So far, the technical scheme that can address the above problem is proposed as yet.
Summary of the invention
Consider the problems referred to above and make the present invention, for this reason, main purpose of the present invention is to provide a kind of synchronization mechanism of terminal system version, thereby to solve backup version and the inconsistent normal problem of using of terminal that influences of operation version in the correlation technique.
According to embodiments of the invention, provide a kind of method for synchronous of terminal system version.
This method comprises: preserve on terminal corresponding to the first version information of operation version and corresponding to second version information of backup version; The first version information and second version information are compared, judge whether backup version to be updated to the operation version; In judged result is under the situation that is, with the storage area of operation version replication to backup version, and covers backup version.
Wherein, the first version information and second version information include: whether current version number, version be complete and/or whether the version verification is correct.
At this moment, judge that the situation that needs to upgrade backup version comprises: backup version lags behind the operation version, backup version is imperfect and/or the backup version verification is incorrect.
In addition, this method may further include: upgrade under the case of successful at backup version, with the version information of the second version information updating for the backup version after upgrading.
In addition, this method can further comprise: upgrade under the unsuccessful situation at backup version, do not upgrade second version information, and after determine to need upgrade after contrasting the first version information and second version information under the situation of backup version and upgrade backup version again.
In addition, can when starting terminal, the first version information and second version information be compared.
A kind of synchronizer of terminal system version is provided according to another embodiment of the present invention.
This device comprises: memory module is used to preserve corresponding to the first version information of operation version and corresponding to second version information of backup version; Comparison module compares the first version information and second version information, judges whether backup version to be updated to the operation version; Update module is used for being judged as under the situation that is at comparison module, with the storage area of operation version replication to backup version, and covers backup version.
Wherein, the first version information and second version information include: whether current version number, version be complete and/or whether the version verification is correct.
And judge that the situation that needs to upgrade backup version comprises: backup version lags behind the operation version, backup version is imperfect and/or the backup version verification is incorrect.
In addition, upgrade under the case of successful at backup version, update module is with the version information of the second version information updating for the backup version after upgrading; Upgrade under the unsuccessful situation at backup version, update module is not upgraded second version information, and need upgrade backup version again under the situation of renewal backup version in comparison module judgement afterwards.
By technique scheme of the present invention, can under the situation that does not influence normal use, effectively keep the unanimity of two system versions, truly realize two version backups, thereby improving fail safe, reliability and the user experience of terminal system.
Description of drawings
Accompanying drawing described herein is used to provide further understanding of the present invention, constitutes the application's a part, and illustrative examples of the present invention and explanation thereof are used to explain the present invention, do not constitute improper qualification of the present invention.In the accompanying drawings:
Fig. 1 is the flow chart according to the method for synchronous of the terminal system version of correlation technique;
Fig. 2 is the flow chart according to the method for synchronous of the terminal system version of the inventive method embodiment;
Fig. 3 is the flow chart according to the detailed process process of the method for synchronous of the terminal system version of the inventive method embodiment; And
Fig. 4 is the block diagram according to the synchronizer of the terminal system version of apparatus of the present invention embodiment.
Embodiment
Method embodiment
A kind of method for synchronous of terminal system version is provided in the present embodiment.This method can be after the finishing of end product remote online upgrading certain time, the version of finishing two versions is synchronous, thereby guarantees the product reliability of operation, and does not influence the normal operation of product business.Describe the present invention in detail below in conjunction with accompanying drawing.
As shown in Figure 2, comprise according to the method for synchronous of the terminal system version of present embodiment: step S202, preserve on terminal corresponding to the first version information of operation version and corresponding to second version information of backup version; Step S204 compares the first version information and second version information, judges whether backup version to be updated to the operation version; Step S206 is under the situation that is in judged result, with the storage area of operation version replication to backup version, and covers backup version.
Wherein, the first version information and second version information include: whether current version number, version be complete and/or whether the version verification is correct.
At this moment, judge that the situation that needs to upgrade backup version comprises: backup version lags behind the operation version, backup version is imperfect and/or the backup version verification is incorrect.
In addition, this method may further include: upgrade under the case of successful at backup version, with the version information of the second version information updating for the backup version after upgrading.
In addition, this method can further comprise: upgrade under the unsuccessful situation at backup version, do not upgrade second version information, and after determine to need upgrade after contrasting the first version information and second version information under the situation of backup version and upgrade backup version again.
In addition, can when starting terminal, the first version information and second version information be compared.
That is to say, the state information that this method can be divided into two versions (operation version and backup version) safeguard and the version of two versions synchronous.Wherein, the state information of two versions is safeguarded and comprised: the release status information of two two versions of version is preserved in the appointed area in system, and carries out corresponding release status according to the upgrading of version and after finishing synchronously and upgrade; The version of two versions comprises synchronously: according to the state information of two versions of two versions, the version of finishing two versions is synchronous, wait fortuitous event if outage in two version synchronizing processes, occurs, cause two version synchronization failures, two versions still can be when next version starts, again it is synchronous to carry out version, thereby guarantees two synchronous reliabilities of version.
Particularly, as shown in Figure 3, system is carrying out two versions when synchronous, check earlier the state of two two versions of version, and according to set version synchronization rules, it is synchronous to judge whether to carry out version, synchronous if desired, then will move version replication to the backup version zone, in the version synchronizing process, not influence the normal use of version business from operation version zone.Then do not do any operation synchronously if do not need.
To be that example is described the present invention as the scene that the operation version starts this terminal with the backup version after backup version being upgraded and will upgrading below.
System provides the storage area of release status information for two versions of two versions;
Two versions for two versions in the product memory provide the storage area of release status information, and finish the setting of initial release status information;
System's online upgrading is downloaded redaction to the backup version storage area, and revises corresponding release status information;
During the system online upgrading, operation version and upgrade server are mutual, download redaction in Installed System Memory, finish the storage area that the redaction that downloads to is written to after the verification of version backup version, write finish after, backup version is set to the operation version of next time, and the version that is moving is set to backup version;
System restarts, with new operation version start and finish two versions synchronously.
After system restarts operation with new operation version, check the state of operation version and backup version, it is synchronous to judge whether to carry out version; Because system has just finished online upgrading, operation version and backup version may there are differences, therefore current backup version (the operation version that does not upgrade before) is not a redaction, then the two versions of system start-up are synchronous, with current operation version from operation version zone complete copy to the backup version zone; After two versions are finished synchronously, revise corresponding release status information;
If two edition upgrading synchronization failures then do not change release status information, system is when release status inspection is next time compared like this, and it is synchronous still can to start two versions; If two versions are success synchronously, then the release status information of two versions is revised by system, shows that two versions in the system have been consistent, and at this moment, it is synchronous just can not restart two versions in version sync check next time.
As mentioned above, in application, can also be according to the release status of reality, state information such as for example, whether version is complete, and whether the version verification is correct, it is synchronous whether decision needs to carry out version, enumerates no longer one by one here.
Device embodiment
A kind of synchronizer of terminal system version is provided in the present embodiment.
As shown in Figure 4, comprise according to the synchronizer of the terminal system version of present embodiment: memory module 402 is used to preserve corresponding to the first version information of operation version and corresponding to second version information of backup version; Comparison module 404 compares the first version information and second version information, judges whether backup version to be updated to the operation version; Update module 406 is used for being judged as under the situation that is at comparison module 404, with the storage area of operation version replication to backup version, and covers backup version.
Wherein, the first version information and second version information include: whether current version number, version be complete and/or whether the version verification is correct.
And judge that the situation that needs to upgrade backup version comprises: backup version lags behind the operation version, backup version is imperfect and/or the backup version verification is incorrect.
In addition, upgrade under the case of successful at backup version, update module is with the version information of the second version information updating for the backup version after upgrading; Upgrade under the unsuccessful situation at backup version, update module is not upgraded second version information, and need upgrade backup version again under the situation of renewal backup version in comparison module judgement afterwards.
The present invention is from reliability of products, fail safe, and aspects such as ease for use consider, the angle design from end product characteristics and user use makes end product reliable and stable; Owing to when version is synchronous, can not change the version zone of moving version, just will move version replication to the backup version zone, all business can normally be used in this process, and user's imperceptible product in whole process is synchronous at version, therefore can effectively improve the satisfaction of user to terminal; In addition, even in two version synchronization failures, damaged the backup version zone, because the operation version still can normally start operation, it is synchronous to carry out two versions once more, finishes synchronously until two versions.
In sum, by means of technical scheme of the present invention, the unanimity that can effectively keep two system versions under the situation that does not influence normal use is truly realizing two version backups, thereby has improved fail safe, reliability and the user experience of terminal system.
The above is the preferred embodiments of the present invention only, is not limited to the present invention, and for a person skilled in the art, the present invention can have various changes and variation.Within the spirit and principles in the present invention all, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (10)
1. the method for synchronous of a terminal system version is characterized in that, comprising:
On terminal, preserve corresponding to the first version information of operation version and corresponding to second version information of backup version;
The described first version information and second version information are compared, judge whether described backup version to be updated to described operation version;
In judged result is under the situation that is, with the storage area of described operation version replication to described backup version, and covers described backup version.
2. method for synchronous according to claim 1 is characterized in that, described first version information and described second version information include: whether current version number, version be complete and/or whether the version verification is correct.
3. method for synchronous according to claim 2 is characterized in that, judge that the situation that needs to upgrade described backup version comprises: described backup version lags behind described operation version, the imperfect and/or described backup version verification of described backup version is incorrect.
4. according to each described method for synchronous in the claim 1 to 3, it is characterized in that, further comprise:
Upgrade under the case of successful at described backup version, with the version information of the described second version information updating for the backup version after upgrading.
5. according to each described method for synchronous in the claim 1 to 3, it is characterized in that, further comprise:
Upgrade under the unsuccessful situation at described backup version, do not upgrade described second version information, and after determine to need upgrade after contrasting described first version information and described second version information under the situation of described backup version and upgrade described backup version again.
6. according to each described method for synchronous in the claim 1 to 3, it is characterized in that, when described starting terminal, described first version information and described second version information are compared.
7. the synchronizer of a terminal system version is characterized in that, comprising:
Memory module is used to preserve corresponding to the first version information of operation version and corresponding to second version information of backup version;
Comparison module compares the described first version information and second version information, judges whether described backup version to be updated to described operation version;
Update module is used for being judged as under the situation that is at described comparison module, with the storage area of described operation version replication to described backup version, and covers described backup version.
8. synchronizer according to claim 7 is characterized in that, described first version information and described second version information include: whether current version number, version be complete and/or whether the version verification is correct.
9. synchronizer according to claim 8 is characterized in that, judge that the situation that needs to upgrade described backup version comprises: described backup version lags behind described operation version, the imperfect and/or described backup version verification of described backup version is incorrect.
10. according to each described synchronizer in the claim 6 to 9, it is characterized in that, upgrade under the case of successful that described update module is with the version information of the described second version information updating for the described backup version after upgrading at described backup version; Upgrade under the unsuccessful situation at described backup version, described update module is not upgraded described second version information, and after described comparison module judge under the situation that needs to upgrade described backup version and upgrade described backup version again.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008100811190A CN101247268B (en) | 2008-02-26 | 2008-02-26 | Synchronization method and apparatus of terminal system version |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008100811190A CN101247268B (en) | 2008-02-26 | 2008-02-26 | Synchronization method and apparatus of terminal system version |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101247268A true CN101247268A (en) | 2008-08-20 |
| CN101247268B CN101247268B (en) | 2010-09-29 |
Family
ID=39947494
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2008100811190A Active CN101247268B (en) | 2008-02-26 | 2008-02-26 | Synchronization method and apparatus of terminal system version |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101247268B (en) |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101815099A (en) * | 2010-04-20 | 2010-08-25 | 中兴通讯股份有限公司 | Double-controller configuration information synchronization method and device in double-control disk array |
| CN105095074A (en) * | 2015-07-10 | 2015-11-25 | 北京金山安全软件有限公司 | Upgrade test method and device for configuration file |
| CN105554530A (en) * | 2015-12-14 | 2016-05-04 | 深圳市九洲电器有限公司 | Method and system for managing set-top box ad |
| CN105677409A (en) * | 2015-12-31 | 2016-06-15 | 中科创达软件股份有限公司 | System upgrading method and device |
| CN105740096A (en) * | 2016-01-21 | 2016-07-06 | 浪潮(北京)电子信息产业有限公司 | Method and apparatus for data remote disaster tolerance backup of cluster file system |
| CN107995284A (en) * | 2017-11-29 | 2018-05-04 | 艾体威尔电子技术(北京)有限公司 | A kind of OTA upgrade methods suitable for POS machine |
| CN110399023A (en) * | 2019-07-12 | 2019-11-01 | 苏州浪潮智能科技有限公司 | Radiate policy management method, device, equipment and computer readable storage medium |
| CN112099845A (en) * | 2020-09-21 | 2020-12-18 | 华人运通(上海)云计算科技有限公司 | Software version updating method, server, vehicle, and computer storage medium |
| CN112287348A (en) * | 2019-07-23 | 2021-01-29 | 上汽通用汽车有限公司 | Self-refreshing method and system of vehicle-mounted module |
| CN113721959A (en) * | 2021-08-30 | 2021-11-30 | 联想(北京)有限公司 | Information processing method and device and electronic equipment |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100349116C (en) * | 2003-08-05 | 2007-11-14 | 华为技术有限公司 | Method for device for improving computer furction for accessing internet |
| CN100461108C (en) * | 2007-03-13 | 2009-02-11 | 中兴通讯股份有限公司 | Method for on-line upgrading of edition in terminal product without interrupting the operation |
-
2008
- 2008-02-26 CN CN2008100811190A patent/CN101247268B/en active Active
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101815099A (en) * | 2010-04-20 | 2010-08-25 | 中兴通讯股份有限公司 | Double-controller configuration information synchronization method and device in double-control disk array |
| CN105095074B (en) * | 2015-07-10 | 2018-12-18 | 北京金山安全软件有限公司 | Upgrade test method and device for configuration file |
| CN105095074A (en) * | 2015-07-10 | 2015-11-25 | 北京金山安全软件有限公司 | Upgrade test method and device for configuration file |
| CN105554530A (en) * | 2015-12-14 | 2016-05-04 | 深圳市九洲电器有限公司 | Method and system for managing set-top box ad |
| CN105677409A (en) * | 2015-12-31 | 2016-06-15 | 中科创达软件股份有限公司 | System upgrading method and device |
| CN105677409B (en) * | 2015-12-31 | 2019-02-05 | 中科创达软件股份有限公司 | A kind of method for upgrading system and device |
| CN105740096A (en) * | 2016-01-21 | 2016-07-06 | 浪潮(北京)电子信息产业有限公司 | Method and apparatus for data remote disaster tolerance backup of cluster file system |
| CN107995284A (en) * | 2017-11-29 | 2018-05-04 | 艾体威尔电子技术(北京)有限公司 | A kind of OTA upgrade methods suitable for POS machine |
| CN107995284B (en) * | 2017-11-29 | 2021-02-05 | 艾体威尔电子技术(北京)有限公司 | OTA (over the air) upgrading method suitable for POS (point of sale) machine |
| CN110399023A (en) * | 2019-07-12 | 2019-11-01 | 苏州浪潮智能科技有限公司 | Radiate policy management method, device, equipment and computer readable storage medium |
| CN112287348A (en) * | 2019-07-23 | 2021-01-29 | 上汽通用汽车有限公司 | Self-refreshing method and system of vehicle-mounted module |
| CN112099845A (en) * | 2020-09-21 | 2020-12-18 | 华人运通(上海)云计算科技有限公司 | Software version updating method, server, vehicle, and computer storage medium |
| CN113721959A (en) * | 2021-08-30 | 2021-11-30 | 联想(北京)有限公司 | Information processing method and device and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101247268B (en) | 2010-09-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101247268B (en) | Synchronization method and apparatus of terminal system version | |
| CN109491698B (en) | System updating method and device based on hot patch | |
| CN100461108C (en) | Method for on-line upgrading of edition in terminal product without interrupting the operation | |
| CN107493290B (en) | OTA (over the air) upgrading method for Android smart television system software | |
| CN105138347A (en) | Difference upgrade patch generating method, software upgrading method and corresponding apparatus | |
| US20070074201A1 (en) | Method and system for updating software and computer readable recording medium storing the method | |
| CN105940397A (en) | Application synchornization | |
| CN101436138A (en) | Control device and control method for software upgrade and dynamic rolling back | |
| CN101770372B (en) | Firmware update system, method and building method of firmware of firmware update system | |
| CN101751593B (en) | Smart card and backup, recovering method and system thereof | |
| CN101158906A (en) | Customer terminals program automatic update method | |
| CN106685691A (en) | Efficient configuration update method and system of terminal device in Internet of things system | |
| CN104572206A (en) | Application program self updating and backup recovery method | |
| CN102662798A (en) | Data recovery method and terminal for Android system | |
| CN103064715A (en) | Remote upgrade method and system for automatic drive test systems | |
| CN109062598A (en) | A kind of safe OTA upgrade method and system | |
| CN104133709A (en) | Upgrading method and device for embedded system | |
| CN103677902A (en) | Method for ensuring safety and success of updating of line-card software in distributed OLT system | |
| CN111142911B (en) | Embedded system with abnormal recovery function and upgrading method thereof | |
| CN110535776B (en) | Gateway current limiting method, device, gateway, system and storage medium | |
| KR20170067826A (en) | Updating of firmware | |
| CN101196839A (en) | Data renovation and synchronization process of double-flash read-only memory | |
| CN102081539A (en) | Reliable software upgrade method for dual-mode terminal | |
| US20010046157A1 (en) | Electronic apparatus | |
| CN106250548A (en) | A kind of code update method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |