CN103713911A - Single version upgrading method and single version upgrading device - Google Patents
Single version upgrading method and single version upgrading device Download PDFInfo
- Publication number
- CN103713911A CN103713911A CN201210370432.2A CN201210370432A CN103713911A CN 103713911 A CN103713911 A CN 103713911A CN 201210370432 A CN201210370432 A CN 201210370432A CN 103713911 A CN103713911 A CN 103713911A
- Authority
- CN
- China
- Prior art keywords
- version
- upgrading
- area
- product
- redaction
- 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
Landscapes
- Stored Programmes (AREA)
Abstract
The invention discloses a single version upgrading method and a single version upgrading device, and relates to the field of communication technical products. The method includes dividing a single version into at least a first portion and a second portion which are mutually independent, storing the first portion in a first area, and storing the second portion in a second area; during version upgrading, storing a first portion of a new version in the first area and upgrading a version information identifier of the first portion to realize upgrading of the first portion; storing a second portion of the new version in the first area and upgrading a version information identifier of the second portion to realize upgrading of the second portion. By the single version upgrading method and the single version upgrading device, reliable upgrading of the single version is realized, occupation space of a storage is reduced, and accordingly, product cost is reduced.
Description
Technical field
The present invention relates to communication technology products field, particularly a kind of reliable upgrade method and relevant apparatus of single version.
Background technology
Fast development along with internet broadband technology, demand as the home gateway of family's broadband access door is increasing, and the expansion along with telecommunications broadband services, the chance that home gateway software version carries out software release upgrade renewal online by remote network management also increases gradually, needing to provide safe and reliable upgrading scheme, guarantees the reliability of device upgrade.In order to guarantee the reliability of family gateway equipment upgrading, home gateway adopts the method for two versions or big or small version to realize conventionally at present.Wherein, in two version Shi family gateway memory, preserve two on all four software versions, one is operation version, and another is backup version, during edition upgrading, version to be upgraded is saved in to backup version region, operation version is unaffected, in upgrading is abnormal, has no progeny, and operation version still can normally move, and proceed edition upgrading, after upgrading successfully, the version of newly upgrading of take is operation version, and old operation version transforms into as backup version.Big or small version scheme is in home gateway, to preserve an operation version (large paper edition, possess full release function) and a secure version (little version, support software edition upgrading and restore funcitons), during edition upgrading, by operation version, carry out self edition upgrading, secure version remains unchanged, in edition upgrading is abnormal, have no progeny, operation version is damaged, home gateway can start from secure version, and complete the recovery upgrading that moves version, after recovering to upgrade successfully, home gateway still starts and moves from operation version.
Along with Home Gateway Technology is more and more ripe, and operator is more and more higher to operation maintenance cost control requirement, although the amount of purchase of home gateway is increasing, but procurement price is but reduced year by year, and product quality and O&M cost are had higher requirement, therefore, need home gateway product when guaranteeing that product up-gradation is safeguarded reliable and security of operation, to reduce cost of products.
From realizing of two versions and big or small version, two versions and big or small version all need to be preserved two version files on product, except operation version, also need a backup version or secure version, and backup version or secure version can not used in product normal course of operation, but still to take sizable storage space, increased the cost of product.
Summary of the invention
The object of the present invention is to provide a kind of single version upgrade method and device, the present invention is by version functions is divided into groups, and controls upgrading by grouping, realizes the reliable upgrading of single operation version, can reduce the memory usage of product, reach the object that reduces cost of products.
According to an aspect of the present invention, a kind of single version upgrade method providing, comprising:
Single version is at least divided into separate first and second portion, and described first is stored in to first area, described second portion is stored in to second area;
When carrying out edition upgrading, the first of redaction is stored to described second area, upgrade its version information sign, realize first's upgrading;
The second portion of redaction is stored to described first area, upgrades its version information sign, realize second portion upgrading.
Preferably, described first at least has version and starts and recover upgrade function, and described second portion has other business and the function of the version outside described first.
Preferably, also comprise:
If first upgrades unsuccessfully, utilize the first of original version to carry out version startup, and recover upgrading processing after version starts.The step of described recovery upgrading processing comprises: the first of redaction is saved to second area, and upgrades its version information sign, then the second portion of redaction is saved to first area, and upgrade its version information sign.
Preferably, also comprise:
If second portion is upgraded unsuccessfully, utilize the first of redaction to carry out version startup, and recover upgrading processing after version starts.The step of described recovery upgrading processing comprises: the first of redaction is saved to first area, and upgrades its version information sign, then the second portion of redaction is saved to second area, and upgrade its version information sign.
Preferably, also comprise, before version starts, detect version first and second portion whether complete effectively.
According to a further aspect in the invention, a kind of single version update device providing, comprising:
Storage unit, for being stored in respectively first area and second area by the separate first of single version and second portion;
Edition upgrading unit, during for edition upgrading, is stored to described second area by the first of redaction, upgrade its version information sign, realize first's upgrading, and the second portion of redaction is stored to described first area, upgrade its version information sign, realize second portion upgrading.
Preferably, described edition upgrading unit is also when upgrading unsuccessfully when first, utilize the first of original version to carry out version startup and recover upgrading processing, when second portion is upgraded unsuccessfully, utilize the first of redaction to carry out version startup and recover upgrading processing, wherein, described first at least has version and starts and recover upgrade function, and described second portion has other business and the function of the version outside described first.
Preferably, also comprise:
Version detection unit, for before version starts, whether the first and the second portion that detect version be complete effectively.
Compared with prior art, beneficial effect of the present invention is:
1, the present invention realizes reliable upgrading when product is only preserved single version, has reduced the space size of product storer, has reduced the integral device cost of product;
2, the present invention has realized the reliable upgrading of single version product, and when interrupting appears in upgrading, equipment still can recover upgrading, has reduced the cost of product up-gradation and after-sales service.
Accompanying drawing explanation
Fig. 1 is the single version upgrade method theory diagram that the embodiment of the present invention provides;
Fig. 2 is the single version upgrading complete operation process flow diagram that the embodiment of the present invention provides;
Fig. 3 is single version that the embodiment of the present invention the provides schematic flow sheet of normally upgrading for the first time;
Fig. 4 is the single version that provides of the embodiment of the present invention normal schematic flow sheet of upgrading again after upgrading for the first time;
Fig. 5 is single version that the embodiment of the present invention provides first's failed schematic flow sheet of upgrading while upgrading for the first time;
Fig. 6 is single version that the embodiment of the present invention the provides second portion failed schematic flow sheet of upgrading while upgrading for the first time;
Fig. 7 is the single version update device block diagram that the embodiment of the present invention provides.
Embodiment
Below in conjunction with accompanying drawing, to a preferred embodiment of the present invention will be described in detail, should be appreciated that following illustrated preferred embodiment, only for description and interpretation the present invention, is not intended to limit the present invention.
The following stated P1 and P2 are respectively actual version first and the second portion being kept in product storer, D1 and D2 are respectively first area and the second area at P1 and P2 place on product storer, UP1 and UP2 are respectively first and the second portion of version file to be upgraded, NP1 and NP2 are respectively first and the second portion that is saved in the redaction in product storer after edition upgrading, ND1 and ND2 are respectively first area and the second area at NP1 and NP2 place on product storer, and L1, L2 are respectively the length that version P1 is corresponding with P2.
The present invention is from the reliability of product version upgrading, and reduce the aspects such as cost of products and consider and design, single version is at least divided into two parts P1 and P2, wherein, P1 be at least by guaranteeing that the version core of the normal operation of product and product version recover the relevant funtion part of upgrading and form, and guarantees that product normally starts when operation starts extremely with product, to carry out version and recover upgrading; P2 is comprised of other the business function beyond product version P1, forms complete product version together with P1.The P1 of product version and P2 have separately independently version information sign, preserve the information such as type, deposit position, size, integrality and validity separately.
Product version is independently kept at respectively first area D1 and the second area D2 on storer by P1 and P2 two parts, P1 during startup in searching storage and P2, and the validity of verification P1 and P2, when P1 and P2 are effectively time, product starts the complete product function of operation.When only having P1 effective, product startup enters version and recovers upgrade mode, until complete product version P1 and the two-part recovery upgrading of P2.During product up-gradation, first the UP1 of first of version file to be upgraded is saved on product storer for preserving the D2 of P2, after success, UP1 is kept at the D2 of storer, and on storer, new first area ND1(is D2) preserved the NP1 of first of new upgrading; The second portion UP2 of version to be upgraded is saved in afterwards on product storer for preserving the D1 of P1, after success, UP2 is kept at the D1 on storer again, and on storer, new second area ND2(is D1) preserved the second portion NP2 of new upgrading.In any moment of product up-gradation process, on product storer, all can preserve a complete version that can start and carry out and recover the P1 or the NP1 that upgrade, thereby guaranteed when product version escalation process interrupts, still can start and continue the recovery of product version, thereby realize the reliable upgrading of single version.Especially, when the length of P1 is not more than the length of P2, can in minimum product storage space, realize reliable upgrading.When the length of P1 is greater than the length of P2, need in the storage space of 2 times of above length of P1, realize reliable upgrading.
Fig. 1 is the single version upgrade method theory diagram that the embodiment of the present invention provides, and as shown in Figure 1, step comprises:
Step 101, single version is at least divided into the separate P1 of first and second portion P2, and the described P1 of first is stored in to first area D1, described second portion P2 is stored in to second area D2.
Furtherly, described single version is at least divided into first and second portion, and wherein first has the function that version starts and version recovery is upgraded, and second portion is comprised of other parts outside the first of version.Described first and second portion have separately independently version information sign, and separate, stored is on product storer.During edition upgrading, the first that first upgrades is to the second portion memory block of storer, and upgrades corresponding version information sign, then the second portion of upgrading is to the first memory block of storer, and upgrades corresponding version information and identify.In edition upgrading process, product storer at least guarantees to preserve on product storer the first of a version at any one time, even while there is so abnormal interruptions the such as power-off in edition upgrading process, on product storer, always preserve a first that can start and support version recovery upgrading, can guarantee to occur in abnormal having no progeny at product version escalation process, the recovery that still can be carried out product startup and continued product version by described first is upgraded.
Fig. 2 is the single version upgrading complete operation process flow diagram that the embodiment of the present invention provides, as shown in Figure 2, below take respectively product normal start and edition upgrading success, product up-gradation unsuccessfully as example is explained in detail the present invention.
Embodiment 1: product version normally starts and carry out edition upgrading success
The first step, normally startup
Version P1 and P2 in product storer, have been preserved, and the version information of each several part sign, product searches for and checks P1 and the P2 preserving on checksum memory when starting, and corresponding version information sign, after the state of confirming version each several part is normal, product partly starts to start operation by P1.
Second step, version are downloaded
When edition upgrading, version file to be upgraded is downloaded in product internal memory, and checks the state of UP1 part and the UP2 part of verification version to be upgraded, after being verified, carries out edition upgrading.
The 3rd step, edition upgrading
Steps A: the UP1 of version to be upgraded is saved in to the storage area D2 of P2 in product storer, is about to the new NP1 of first and is kept at storage area ND1, and upgrade corresponding version information sign.
Step B: the UP2 of version to be upgraded is saved in to the storage area D1 of P1 in product storer, is about to new second portion NP2 and is kept at storage area ND2, and upgrade corresponding version information sign.
UP1 and UP2 at version to be upgraded are saved in respectively after storer, on storer, have preserved after the NP1 and NP2 of upgraded version, and edition upgrading completes.
The 4th step, restart
After edition upgrading success, NP1 and the NP2 preserving on checksum memory searched for and checked to product when restarting, and corresponding version information sign, and after confirming that each several part state is normal, product is partly started the software version of the new upgrading of operation by NP1.
Embodiment 2: product version is upgraded unsuccessfully
The first step, normally startup
Version P1 and P2 in product storer, have been preserved, and the version information of each several part sign, product searches for and checks P1 and the P2 preserving on checksum memory when starting, and corresponding version information sign, after the state of confirming version each several part is normal, product partly starts to start operation by P1.
Second step, version are downloaded
When edition upgrading, version file to be upgraded is downloaded in product internal memory, and checks the state of UP1 part and the UP2 part of verification version to be upgraded, after being verified, carries out edition upgrading.
The 3rd step, in escalation process, because causing upgrading, power-off interrupts
Step C: the UP1 of version to be upgraded is saved in to the storage area D2 of P2 in product storer, is about to the new NP1 of first and is kept at storage area ND1, and upgrade corresponding version information sign.
While there are the abnormal conditions such as power-off in execution step C process, in product storer, the P1 of the original version of preserving is complete and P2 has damaged, when product starts again, P2 can be detected damages, and P1 remains complete effective, therefore, product is started by P1 and automatically enters version recovery upgrade status, and forwards the 4th continuation execution to.
When step C upgrades when normal, continue to carry out step D below.
Step D: the UP2 of version to be upgraded is saved in to the storage area D1 of P1 in product storer, is about to new second portion NP2 and is kept at storage area ND2, and upgrade corresponding version information sign.
While there are the abnormal conditions such as power-off in execution step D process, the P1 of the version of the original preservation in product storer is damaged, but product has been preserved the new NP1 of first in step C process, when product starts again, P1 can be detected and damage, but the new NP1 preserving is complete effectively, therefore, product is started by NP1 and enters version recovery upgrade status, and forwards the 4th step continuation execution to.
When step D upgrading is normal, continue to carry out the 5th step below, that is to say, at UP1 and the UP2 of version to be upgraded, be saved in respectively after storer, on storer, preserved NP1 and the NP2 of upgraded version, edition upgrading completes, and forwards the 5th step to and restarts.
The 4th step, version recover upgrading
When product is when interrupting appears in step C, the P2 of the version of preserving in product storer because of breakdown during upgrading bad, but the P1 of version is complete effectively, product is started and is carried out following version recovery upgrade step by P1: the storage area D2(that first UP1 of version to be upgraded is saved in to the P2 having damaged in product storer is that NP1 is stored in ND1), and upgrade corresponding version information sign; The storage area D1(that again UP2 of version to be upgraded is saved in to P1 in product storer is that NP2 is stored in ND2), and upgrade corresponding version information sign.
When product is when interrupting appears in step D, version P1 in product storer is damaged, but product has newly been preserved NP1 at step C, product is started and is carried out following version recovery upgrade step by NP1: the storage area D1(that first UP1 of version to be upgraded is saved in to the P1 having damaged in product storer is that NP1 is stored in ND1), and upgrade corresponding version information sign; Again the UP2 of version to be upgraded is saved in to product storer Central Plains P2(and recovers the NP1 part starting) storage area D2(be that NP2 is stored in ND2), and upgrade corresponding version information sign.
As recover upgrading normally, and forward the 5th step to and carry out, as abnormal in still occurred, forward the 3rd step to and proceed.
The 5th step, restart
After edition upgrading success, NP1 and the NP2 preserving on checksum memory searched for and checked to product when restarting, and corresponding version information sign, and after confirming that each several part state is normal, product is partly started the software version of the new upgrading of operation by NP1.
Fig. 3 is single version that the embodiment of the present invention the provides schematic flow sheet of normally upgrading for the first time, as shown in Figure 3, the prototype version distributing in storer before edition upgrading has P2 two parts that P1 that length is L1 and length are L2, when existence comprises UP1 and the two-part version file to be upgraded of UP2, described UP1 and UP2 are downloaded to internal memory.By carrying out successively steps A and the step B of above-described embodiment 1, UP1 is saved to the storage area at P2 place, realize the upgrading of P1, be on storer, to preserve NP1 as shown in the figure, again UP2 is saved to the storage area at P1 place, realizes the upgrading of P2, on storer, preserve NP2 as shown in the figure.
Fig. 4 is the single version that provides of the embodiment of the present invention normal schematic flow sheet of upgrading again after upgrading for the first time, and as shown in Figure 4, when the version of having upgraded is once upgraded again, the flow process shown in its upgrading flow process and Fig. 3 is similar, does not repeat them here.
Fig. 5 is single version that the embodiment of the present invention provides first's failed schematic flow sheet of upgrading while upgrading for the first time, as shown in Figure 5, in edition upgrading process, if while carrying out the step C of above-described embodiment 2, upgrading is interrupted, carry out version and extremely start, now the version in storer is distributed as the invalid P2 of damage that complete effective P1 that length is L1 and length are L2.Download package contains after UP1 and the two-part version file to be upgraded of UP2, carry out version and recover upgrading, carry out successively steps A and the step B of above-described embodiment 1, UP1 is saved to the storage area that damages invalid P2 place, realize the upgrading of P1, on storer, preserve NP1 as shown in the figure, then UP2 is saved to the storage area at complete effective P1 place, realize the upgrading of P2, on storer, preserve NP2 as shown in the figure.
Fig. 6 is single version that the embodiment of the present invention the provides second portion failed schematic flow sheet of upgrading while upgrading for the first time, as shown in Figure 6, in edition upgrading process, if while carrying out the step D of above-described embodiment 2, upgrading is interrupted, carry out version and extremely start, now the version in storer to be distributed as length be that the complete effective P1(of L1 is NP1 described in step C) and the length invalid P2 of damage that is L2.Download package contains after UP1 and the two-part version file to be upgraded of UP2, carry out version and recover upgrading, carry out successively steps A and the step B of above-described embodiment 1, UP1 is saved to the storage area that damages invalid P2 place, realize the upgrading of P1, on storer, preserve NP1 as shown in the figure, then UP2 is saved to the storage area at complete effective P1 place, realize the upgrading of P2, on storer, preserve NP2 as shown in the figure.
Fig. 7 is the single version update device block diagram that the embodiment of the present invention provides, and as shown in Figure 7, comprises the storage unit for storage version, for the edition upgrading unit of edition upgrading, for detection of the version detection unit of release status.
Before version starts, whether version detection unit inspection separate, stored is complete effective at first and the second portion of the version of storage unit, and wherein said first is stored in first area, and described second portion is stored in second area.When version is complete when effective, normally start and edition upgrading, otherwise carry out abnormal start and version recovers to upgrade.During edition upgrading, edition upgrading unit is stored to described second area by the first of redaction, upgrades its version information sign, realize first's upgrading, and the second portion of redaction is stored to described first area, and upgrade its version information sign, realize second portion upgrading.After restarting, the version of the new upgrading of operation.In edition upgrading process, if first upgrades unsuccessfully, the first of described edition upgrading unit by using original version carries out version startup and recovers upgrading processing, be after version starts, the first of redaction is saved to second area, and upgrade its version information sign, then the second portion of redaction is saved to first area, and upgrade its version information sign; If second portion is upgraded unsuccessfully, utilize the first of redaction to carry out version startup and recover upgrading processing, be after version starts, the first of redaction is saved to first area, and upgrade its version information sign, again the second portion of redaction is saved to second area, and upgrades its version information sign.Wherein, described version is at least divided into above-mentioned first and second portion, and described first at least has version and starts and recover upgrade function, and described second portion has other business and the function of the version outside described first.
In sum, in sum, the present invention has following technique effect:
1, the present invention has realized product each stage in upgrading, in storer, all preserve one and can start and carry out version P1 or the NP1 that version recovers upgrading, thereby guarantee when abnormal interruption appears in edition upgrading, still can start and carry out version and recover upgrading, guarantee the reliability of product up-gradation, reduced the O&M cost of product.
2, product adopts single software version design, makes product storer only need to preserve single version, has reduced the demand of storer, has reduced the holistic cost of product.
Although above the present invention is had been described in detail, the invention is not restricted to this, those skilled in the art of the present technique can carry out various modifications according to principle of the present invention.Therefore, all modifications of doing according to the principle of the invention, all should be understood to fall into protection scope of the present invention.
Claims (10)
1. a single version upgrade method, is characterized in that, comprising:
Single version is at least divided into separate first and second portion, and described first is stored in to first area, described second portion is stored in to second area;
When carrying out edition upgrading, the first of redaction is stored to described second area, upgrade its version information sign, realize first's upgrading;
The second portion of redaction is stored to described first area, upgrades its version information sign, realize second portion upgrading.
2. method according to claim 1, is characterized in that, described first at least has version and starts and recover upgrade function, and described second portion has other business and the function of the version outside described first.
3. method according to claim 1 and 2, is characterized in that, also comprises:
If first upgrades unsuccessfully, utilize the first of original version to carry out version startup, and recover upgrading processing after version starts.
4. method according to claim 3, it is characterized in that, the step of described recovery upgrading processing comprises: the first of redaction is saved to second area, and upgrades its version information sign, again the second portion of redaction is saved to first area, and upgrades its version information sign.
5. method according to claim 1 and 2, is characterized in that, also comprises:
If second portion is upgraded unsuccessfully, utilize the first of redaction to carry out version startup, and recover upgrading processing after version starts.
6. method according to claim 5, it is characterized in that, the step of described recovery upgrading processing comprises: the first of redaction is saved to first area, and upgrades its version information sign, again the second portion of redaction is saved to second area, and upgrades its version information sign.
7. according to the method described in claim 4 or 6, it is characterized in that, before version starts, detect version first and second portion whether complete effectively.
8. a single version update device, is characterized in that, comprising:
Storage unit, for being stored in respectively first area and second area by the separate first of single version and second portion;
Edition upgrading unit, during for edition upgrading, is stored to described second area by the first of redaction, upgrade its version information sign, realize first's upgrading, and the second portion of redaction is stored to described first area, upgrade its version information sign, realize second portion upgrading.
9. device according to claim 8, it is characterized in that, described edition upgrading unit is also when upgrading unsuccessfully when first, utilize the first of original version to carry out version startup and recover upgrading processing, when second portion is upgraded unsuccessfully, utilize the first of redaction to carry out version startup and recover upgrading processing, wherein, described first at least has version and starts and recover upgrade function, and described second portion has other business and the function of the version outside described first.
10. device according to claim 9, is characterized in that, also comprises:
Version detection unit, for before version starts, whether the first and the second portion that detect version be complete effectively.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201210370432.2A CN103713911B (en) | 2012-09-28 | 2012-09-28 | A kind of single version upgrade method and device |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201210370432.2A CN103713911B (en) | 2012-09-28 | 2012-09-28 | A kind of single version upgrade method and device |
Publications (2)
Publication Number | Publication Date |
---|---|
CN103713911A true CN103713911A (en) | 2014-04-09 |
CN103713911B CN103713911B (en) | 2017-11-10 |
Family
ID=50406918
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201210370432.2A Active CN103713911B (en) | 2012-09-28 | 2012-09-28 | A kind of single version upgrade method and device |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN103713911B (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106375857A (en) * | 2016-10-13 | 2017-02-01 | 青岛海信宽带多媒体技术有限公司 | Optical fiber set-top box upgrading method |
CN106909428A (en) * | 2017-03-31 | 2017-06-30 | 广东欧珀移动通信有限公司 | Software updating control method, device and electronic equipment |
CN110943871A (en) * | 2019-12-27 | 2020-03-31 | 杭州迪普科技股份有限公司 | Resource interval adjusting method and device |
CN111831297A (en) * | 2019-04-17 | 2020-10-27 | 中兴通讯股份有限公司 | Zero-difference upgrading method and device |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030225986A1 (en) * | 2002-04-23 | 2003-12-04 | Casio Computer Co., Ltd. | Program install method, file renewal method, program and computer system |
CN101078993A (en) * | 2007-03-13 | 2007-11-28 | 中兴通讯股份有限公司 | Method for on-line upgrading of edition in terminal product without interrupting the operation |
CN101639785A (en) * | 2009-09-02 | 2010-02-03 | 中兴通讯股份有限公司 | Method and device for software updating |
CN101826027A (en) * | 2010-05-28 | 2010-09-08 | 深圳市融创天下科技发展有限公司 | Embedded system and updating method thereof |
CN102081539A (en) * | 2011-01-12 | 2011-06-01 | 苏州汉辰数字多媒体有限公司 | Reliable software upgrade method for dual-mode terminal |
CN102110000A (en) * | 2009-12-25 | 2011-06-29 | 康佳集团股份有限公司 | Method, device and equipment for controlling software for auto-updating |
CN102169439A (en) * | 2010-02-26 | 2011-08-31 | 英业达股份有限公司 | Data transmission system |
-
2012
- 2012-09-28 CN CN201210370432.2A patent/CN103713911B/en active Active
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030225986A1 (en) * | 2002-04-23 | 2003-12-04 | Casio Computer Co., Ltd. | Program install method, file renewal method, program and computer system |
CN101078993A (en) * | 2007-03-13 | 2007-11-28 | 中兴通讯股份有限公司 | Method for on-line upgrading of edition in terminal product without interrupting the operation |
CN101639785A (en) * | 2009-09-02 | 2010-02-03 | 中兴通讯股份有限公司 | Method and device for software updating |
CN102110000A (en) * | 2009-12-25 | 2011-06-29 | 康佳集团股份有限公司 | Method, device and equipment for controlling software for auto-updating |
CN102169439A (en) * | 2010-02-26 | 2011-08-31 | 英业达股份有限公司 | Data transmission system |
CN101826027A (en) * | 2010-05-28 | 2010-09-08 | 深圳市融创天下科技发展有限公司 | Embedded system and updating method thereof |
CN102081539A (en) * | 2011-01-12 | 2011-06-01 | 苏州汉辰数字多媒体有限公司 | Reliable software upgrade method for dual-mode terminal |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106375857A (en) * | 2016-10-13 | 2017-02-01 | 青岛海信宽带多媒体技术有限公司 | Optical fiber set-top box upgrading method |
CN106375857B (en) * | 2016-10-13 | 2019-07-09 | 青岛海信宽带多媒体技术有限公司 | The upgrade method of optical fiber set-top box |
CN106909428A (en) * | 2017-03-31 | 2017-06-30 | 广东欧珀移动通信有限公司 | Software updating control method, device and electronic equipment |
CN111831297A (en) * | 2019-04-17 | 2020-10-27 | 中兴通讯股份有限公司 | Zero-difference upgrading method and device |
CN110943871A (en) * | 2019-12-27 | 2020-03-31 | 杭州迪普科技股份有限公司 | Resource interval adjusting method and device |
CN110943871B (en) * | 2019-12-27 | 2022-11-01 | 杭州迪普科技股份有限公司 | Resource interval adjusting method and device |
Also Published As
Publication number | Publication date |
---|---|
CN103713911B (en) | 2017-11-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN104461786B (en) | The restoration methods of android system and the recovery system of android system | |
CN103488498B (en) | Computer booting method and computer | |
JP5075736B2 (en) | System failure recovery method and system for virtual server | |
CN103890736A (en) | Message reconciliation during disaster recovery | |
CN109491698B (en) | System updating method and device based on hot patch | |
CN102262574B (en) | Boot protecting method and device of operating system | |
CN104217137A (en) | Method and device for identifying whether intelligent terminal system is changed | |
CN103092712A (en) | Method and device for recovering interrupt tasks | |
CN102799499B (en) | Method and vehicle-mounted Android equipment that vehicle-mounted Android device systems recovers | |
CN101977127B (en) | SNMP (Simple Network Management Protocol) based equipment configuration roll back method and SNMP network management equipment | |
CN105630632A (en) | Virtual machine recovery method and virtual machine management device | |
CN109358893A (en) | A kind of the online upgrading method, apparatus and system of FPGA program | |
CN103713911A (en) | Single version upgrading method and single version upgrading device | |
CN104268468A (en) | Protecting method and system of dynamic link library of Android system | |
CN104461594A (en) | Updating method and device of embedded operating system | |
CN104049999A (en) | Automatic storage device repair system based on network and method thereof | |
CN105550071B (en) | System file upgrades and detection method, communication equipment | |
CN105303103A (en) | Method for protecting service process in mobile terminal and mobile terminal | |
CN102843400A (en) | method and system for downloading file | |
CN104850556A (en) | Method and device for data processing | |
CN104317672A (en) | System file repairing method, device and system | |
CN102541682A (en) | Method for restoring abnormal programs in embedded system quickly and automatically | |
CN102262573B (en) | Operating system (OS) start-up protecting method and device | |
CN103763336A (en) | Software update method oriented to complex network architecture | |
CN104461757A (en) | Method and device for restoring virtual machines |
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 |