CN103713911B - A kind of single version upgrade method and device - Google Patents
A kind of single version upgrade method and device Download PDFInfo
- Publication number
- CN103713911B CN103713911B CN201210370432.2A CN201210370432A CN103713911B CN 103713911 B CN103713911 B CN 103713911B CN 201210370432 A CN201210370432 A CN 201210370432A CN 103713911 B CN103713911 B CN 103713911B
- Authority
- CN
- China
- Prior art keywords
- version
- upgrading
- area
- redaction
- product
- 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
Abstract
The invention discloses a kind of single version upgrade method and device, it is related to communication technology products field, methods described includes：Single version is at least divided into separate Part I and Part II, and the Part I is stored in first area, the Part II is stored in second area；When carrying out edition upgrading, the Part I of redaction is stored to the second area, and updates its version information mark, realizes that Part I upgrades；The Part II of redaction is stored to the first area, and updates its version information mark, realizes that Part II upgrades.The present invention realizes single version and reliably upgraded, and reduces memory usage space, so as to reduce the cost of product.
Description
Technical field
The present invention relates to communication technology products field, the reliable upgrade method of more particularly to a kind of single version and related dress
Put.
Background technology
With the fast development of the Internet broadband technology, the demand as the home gateway of home broadband access door is got over
Come it is bigger, and as the expansion of telecommunications broadband services, home gateway software version carry out software version online by remote network management
The chance of upgrading renewal also gradually increases, it is desirable to be able to provides safe and reliable upgrading scheme, ensures the reliability of device upgrade.
Currently in order to ensureing the reliability of family gateway equipment upgrading, the method for the double versions of home gateway generally use or size version is come
Realize.Wherein, double versions are two completely the same software versions of preservation in family's gateway memory, and one is operation version
This, another is backup version, version to be upgraded is saved in into backup version region during edition upgrading, operation version is not by shadow
Ring, after abnormal interrupt is upgraded, operation version still can be with normal operation, and continues edition upgrading, after upgrading successfully, with
The version newly upgraded is operation version, and old operation version is transformed into as backup version.And size versioning scheme is then in home network
The Central Shanxi Plain preserves an operation version（Big version, possesses full release function）With a secure version（Small version, only support software
Edition upgrading is with recovering function）, during edition upgrading, itself edition upgrading is carried out by operation version, secure version keeps constant,
After edition upgrading abnormal interrupt, operation version is damaged, then home gateway can start from secure version, and completes to run version
This recovery upgrading, after recovery upgrades successfully, home gateway is still from operation version startup optimization.
As Home Gateway Technology is more and more ripe, and operator requires more and more higher to operation maintenance cost control,
Although the amount of purchase of home gateway is increasing, procurement price is to reduce year by year, and to product quality and O＆M cost
Higher requirement is proposed, therefore, it is necessary to home gateway product can ensure that it is reliable and safe for operation that product up-gradation is safeguarded
Meanwhile reduce product cost.
It was found from the realization of double versions and size version, double versions are required for preserving two versions on product with size version
This document, in addition to running version, it is also necessary to a backup version or secure version, and backup version or secure version are in product
Never used in normal course of operation, but still to take sizable storage space, add the cost of product.
The content of the invention
It is an object of the invention to provide a kind of single version upgrade method and device, and the present invention is by version each several part work(
It can be grouped, and upgrading is controlled by packet, realized the reliable upgrading of single operation version, the storage of product can be reduced
Device takes, and reaches the purpose for reducing product cost.
According to an aspect of the present invention, there is provided a kind of single version upgrade method, including：
Single version is at least divided into separate Part I and Part II, and the Part I is stored in
One region, the Part II is stored in second area；
When carrying out edition upgrading, the Part I of redaction is stored to the second area, updates its version information
Mark, realize that Part I upgrades；
The Part II of redaction is stored to the first area, its version information mark is updated, realizes Part II
Upgrading.
Preferably, at least there is the Part I version to start and recover upgrade function, and the Part II has institute
State the other business and function of the version outside Part I.
Preferably, in addition to：
If Part I upgrading failure, version startup is carried out using the Part I of original version, and after version startup
Carry out recovery upgrading processing.The step of recovery upgrading processing, includes：The Part I of redaction is preserved to second area,
And its version information mark is updated, then the Part II of redaction is preserved to first area, and update its version information mark.
Preferably, in addition to：
If Part II upgrading failure, version startup is carried out using the Part I of redaction, and after version startup
Carry out recovery upgrading processing.The step of recovery upgrading processing, includes：The Part I of redaction is preserved to first area,
And its version information mark is updated, then the Part II of redaction is preserved to second area, and update its version information mark.
Preferably, in addition to, before version startup, detect version Part I and whether Part II is complete effectively.
According to another aspect of the present invention, there is provided a kind of single version update device, including：
Memory cell, for the separate Part I and Part II of single version to be stored respectively in into first area
And second area；
Edition upgrading unit, during for edition upgrading, the Part I of redaction is stored to the second area, renewal
Its version information is identified, and realizes that Part I upgrades, and the Part II of redaction is stored to the first area, updates it
Version information identifies, and realizes that Part II upgrades.
Preferably, the edition upgrading unit is additionally operable to, when Part I upgrades failure, utilize first of original version
Divide and carry out version startup and recover upgrading processing, when Part II upgrades failure, utilize the Part I progress version of redaction
This startup and recovery upgrading processing, wherein, the Part I at least has version startup and recovers upgrade function, and described second
Part has the other business and function of the version outside the Part I.
Preferably, in addition to：
Whether version detection unit, Part I and Part II for before version starts, detecting version completely have
Effect.
Compared with prior art, the beneficial effects of the present invention are：
1st, the present invention realizes reliable upgrading when product only preserves single version, reduces the space size of product memory,
Reduce the integral device cost of product；
2nd, the present invention realizes the reliable upgrading of single plate this product, and when upgrading is interrupted, equipment still is able to carry out extensive
Multiple upgrading, reduces product up-gradation and the cost of after-sales service.
Brief description of the drawings
Fig. 1 is single version upgrade method theory diagram provided in an embodiment of the present invention；
Fig. 2 is single version upgrading complete operation flow chart provided in an embodiment of the present invention；
Fig. 3 is the subnormal upgrading schematic flow sheet of single version first provided in an embodiment of the present invention；
Fig. 4 is the schematic flow sheet upgraded again after the first subnormal upgrading of single version provided in an embodiment of the present invention；
Fig. 5 is the flow signal of Part I upgrading failure when single version provided in an embodiment of the present invention upgrades for the first time
Figure；
Fig. 6 is the flow signal of Part II upgrading failure when single version provided in an embodiment of the present invention upgrades for the first time
Figure；
Fig. 7 is single version update device block diagram provided in an embodiment of the present invention.
Embodiment
Below in conjunction with accompanying drawing to a preferred embodiment of the present invention will be described in detail, it will be appreciated that described below is excellent
Select embodiment to be merely to illustrate and explain the present invention, be not intended to limit the present invention.
P1 and P2 as described below are respectively actually stored in version Part I and Part II in product memory, D1
It is respectively P1 and the P2 first area at place and second area on product memory with D2, UP1 and UP2 are respectively version to be upgraded
The Part I and Part II of this document, NP1 and NP2 are respectively the redaction being saved in after edition upgrading in product memory
Part I and Part II, ND1 and ND2 are respectively the first area and second of NP1 and NP2 where go product memory
Region, L1, L2 are respectively version P1 length corresponding with P2.
The reliability that the present invention upgrades from product version, and product cost etc. consideration and design are reduced, by single version
At least it is divided into two parts P1 and P2, wherein, P1 is at least extensive by the version core and product version that can ensure product normal operation
The related funtion part composition of multiple upgrading, ensure that version is carried out when the normal startup optimization of product starts extremely with product to be recovered to rise
Level；P2 is made up of other business functions beyond product version P1, and complete product version is formed together with P1.Product version
P1 and P2 there is each independent version information to identify, preserve respective type, deposit position, size, integrality with effectively
The information such as property.
Product version is independently preserved first area D1 and second area D2 on a memory by P1 and P2 two parts,
P1 and P2 during startup in searching storage, and P1 and P2 validity are verified, as P1 and P2 all effective, product startup optimization
Complete product function.When only P1 is effective, product launches into version and recovers upgrade mode, until completing product version P1
Upgrade with the two-part recoveries of P2.During product up-gradation, the Part I UP1 of version file to be upgraded is first saved in product storage
It is used for the D2 for preserving P2 on device, UP1 is stored in the D2, i.e., new first area ND1 on memory of memory after success（That is D2）
Save the Part I NP1 newly upgraded；The Part II UP2 of version to be upgraded is saved on product memory again afterwards and used
UP2 preserves D1, i.e., new second area ND2 on memory on a memory after the D1 for preserving P1, success（That is D1）Preserve
The Part II NP2 of new upgrading.One can be all preserved at any moment of product up-gradation process, on product memory completely
It can start and carry out P1 or NP1 that version recovers upgrading, so as to ensure that when product version escalation process interrupts, still can
Enough start and continue to complete the recovery of product version, it is achieved thereby that the reliable upgrading of single version.Especially, when P1 length not
During length more than P2, reliable upgrading can be realized in the product storage space of minimum.When P1 length is more than P2 length
, it is necessary to realize reliable upgrading in the storage space of 2 times of more than P1 length when spending.
Fig. 1 is single version upgrade method theory diagram provided in an embodiment of the present invention, as shown in figure 1, step includes：
Step 101, single version is at least divided into separate Part I P1 and Part II P2, and by described first
Part P1 is stored in first area D1, and the Part II P2 is stored in into second area D2.
Step 102, when carrying out edition upgrading, the Part I UP1 of redaction is stored to the second area D2, more
New its version information mark, realizes that Part I P1 upgrades, that is, in the new first area ND1 of product memory after upgrading successfully
Preserve new Part I NP1.
Step 103, the Part II UP2 of redaction stored to the first area D1, updates its version information mark,
Realize that Part II P2 upgrades, that is, the new second area ND2 after upgrading successfully in product memory preserves new Part II
NP2。
Furtherly, the single version is at least divided into Part I and Part II, and there is wherein Part I version to open
Dynamic and version recovers the function of upgrading, and Part II is made up of other parts outside the Part I of version.The Part I and
Part II has each independent version information mark, and is stored separately on product memory.During edition upgrading, first upgrade
Part I is to the Part II memory block of memory, and version information mark corresponding to updating, then upgrades Part II to depositing
The Part I memory block of reservoir, and version information mark corresponding to renewal.During edition upgrading, product memory is in office
One moment at least ensured to preserve the Part I of a version on product memory, accordingly even when going out during edition upgrading
Always preserving portion now during the abnormal interrupt such as power-off, on product memory can start and support version to recover first of upgrading
Point, it can be ensured that after abnormal interrupt occurs in product version escalation process, still product can be carried out by the Part I
Start and continue to complete the recovery upgrading of product version.
Fig. 2 is single version provided in an embodiment of the present invention upgrading complete operation flow chart, as shown in Fig. 2 individually below with
Product normally starts and the present invention is explained in detail exemplified by failing for edition upgrading success, product up-gradation.
Embodiment 1：Product version normally starts and carries out edition upgrading success
The first step, normal startup
Version P1 and P2, and the version information mark of each several part are preserved in product memory, product is on startup
The P1 and P2 preserved on checksum memory, and corresponding version information mark are searched for and checked, is confirming the shape of version each several part
After state is normal, product startup optimization by P1 parts.
Second step, version are downloaded
In edition upgrading, version file to be upgraded is downloaded in product internal memory, and checks verification version to be upgraded
UP1 parts and the state of UP2 parts, after being verified, carry out edition upgrading.
3rd step, edition upgrading
Step A：The UP1 of version to be upgraded is saved in the storage region D2 of P2 in product memory, will be newly first
Part NP1 is stored in storage region ND1, and updates corresponding version information mark.
Step B：The UP2 of version to be upgraded is saved in the storage region D1 of P1 in product memory, will be newly second
Part NP2 is stored in storage region ND2, and updates corresponding version information mark.
After the UP1 and UP2 of version to be upgraded are saved in memory respectively, i.e., upgraded version is preserved on memory
After NP1 and NP2, edition upgrading is completed.
4th step, restarting
After edition upgrading success, product searches for and checked the NP1 and NP2 preserved on checksum memory in restarting,
And corresponding version information mark, after confirming that each several part state is normal, software version that product is newly upgraded by NP1 parts startup optimization
This.
Embodiment 2：Product version upgrading failure
The first step, normal startup
Version P1 and P2, and the version information mark of each several part are preserved in product memory, product is on startup
The P1 and P2 preserved on checksum memory, and corresponding version information mark are searched for and checked, is confirming the shape of version each several part
After state is normal, product startup optimization by P1 parts.
Second step, version are downloaded
In edition upgrading, version file to be upgraded is downloaded in product internal memory, and checks verification version to be upgraded
UP1 parts and the state of UP2 parts, after being verified, carry out edition upgrading.
3rd step, interrupted in escalation process because power-off causes to upgrade
Step C：The UP1 of version to be upgraded is saved in the storage region D2 of P2 in product memory, will be newly first
Part NP1 is stored in storage region ND1, and updates corresponding version information mark.
When the abnormal conditions such as occurring powering off during performing step C, the P1 of the version preserved originally in product memory
It is complete and P2 has been damaged, when product is again started up, can detect that P2 has been damaged, and P1 be still it is complete effective, therefore,
Product is started by P1 and recovers upgrade status automatically into version, and is gone to the 4th and continued executing with.
When step C upgradings are normal, following step D is continued executing with.
Step D：The UP2 of version to be upgraded is saved in the storage region D1 of P1 in product memory, will be newly second
Part NP2 is stored in storage region ND2, and updates corresponding version information mark.
When the abnormal conditions such as occurring powering off during performing step D, the version of the original preservation in product memory
P1 has been damaged, but product has saved new Part I NP1 during step C, when product is again started up, can be examined
P1 is measured to have damaged, but the NP1 newly preserved is completely effective, and therefore, product, which is started by NP1 and enters version, recovers upgrade status,
And go to the 4th step and continue executing with.
When step D upgradings are normal, the 5th following step is continued executing with, that is to say, that in the UP1 and UP2 of version to be upgraded
After being saved in memory respectively, i.e., the NP1 and NP2 of upgraded version are preserved on memory, edition upgrading is completed, and goes to the 5th
Step restarting.
4th step, version recover upgrading
When product interrupts in step C, the P2 of the version preserved in product memory is because breakdown during upgrading is bad, but version
This P1 is completely effective, and product is actuated for following version by P1 and recovers upgrade step：First the UP1 of version to be upgraded is saved in
The P2 damaged in product memory storage region D2（I.e. NP1 is stored in ND1）, and update corresponding version information mark；
The UP2 of version to be upgraded is saved in the storage region D1 of P1 in product memory again（I.e. NP2 is stored in ND2）, and more cenotype
The version information mark answered.
When product interrupts in step D, the version P1 in product memory has been damaged, but product in step C
NP1 is saved through new, product is actuated for following version by NP1 and recovers upgrade step：First the UP1 of version to be upgraded is saved in
The P1 damaged in product memory storage region D1（I.e. NP1 is stored in ND1）, and update corresponding version information mark；
The UP2 of version to be upgraded is saved in product memory Central Plains P2 again（Recover the NP1 parts started）Storage region D2（I.e.
NP2 is stored in ND2）, and update corresponding version information mark.
It is normal such as to recover upgrading, goes to the progress of the 5th step, such as exception still occurs, go to the 3rd step and continue.
5th step, restarting
After edition upgrading success, product searches for and checked the NP1 and NP2 preserved on checksum memory in restarting,
And corresponding version information mark, after confirming that each several part state is normal, software version that product is newly upgraded by NP1 parts startup optimization
This.
Fig. 3 is the subnormal upgrading schematic flow sheet of single version first provided in an embodiment of the present invention, as shown in figure 3, version
The prototype version being distributed before upgrading in memory has the P1 that length is L1 and P2 two parts that length is L2, when exist comprising
During the two-part version files to be upgraded of UP1 and UP2, the UP1 and UP2 are downloaded to internal memory.It is above-mentioned by performing successively
The step A and step B of embodiment 1, preserve the storage region to where P2 by UP1, realize P1 upgrading, i.e., preserved on memory
There is NP1 as shown in the figure, then UP2 is preserved into the storage region to where P1, realize P2 upgrading, i.e., preserved on memory just like figure
Shown NP2.
Fig. 4 is the schematic flow sheet upgraded again after the first subnormal upgrading of single version provided in an embodiment of the present invention, such as
Shown in Fig. 4, when the version upgraded once upgrades again, its upgrading flow is similar with the flow shown in Fig. 3, no longer superfluous herein
State.
Fig. 5 is the flow signal of Part I upgrading failure when single version provided in an embodiment of the present invention upgrades for the first time
Figure, as shown in figure 5, during edition upgrading, if perform the step C of above-described embodiment 2, upgrading is interrupted, then it is different to carry out version
Often start, now the version in memory is distributed as the complete effective P1 that length is L1 and the damage that length is L2 is invalid
P2.After download package is containing the two-part version file to be upgraded of UP1 and UP2, carries out version and recover upgrading, i.e., perform successively above-mentioned
The step A and step B of embodiment 1, UP1 is preserved to the storage region damaged where invalid P2, P1 upgrading is realized, that is, deposits
NP1 as shown in the figure is preserved on reservoir, then UP2 is preserved to the storage region where complete effective P1, realizes P2 upgrading,
NP2 as shown in the figure is preserved on memory.
Fig. 6 is the flow signal of Part II upgrading failure when single version provided in an embodiment of the present invention upgrades for the first time
Figure, as shown in fig. 6, during edition upgrading, if perform the step D of above-described embodiment 2, upgrading is interrupted, then it is different to carry out version
Often start, now the version in memory is distributed as the complete effective P1 that length is L1（NP1 i.e. described in step C）And length
For the invalid P2 of L2 damage.After download package is containing the two-part version file to be upgraded of UP1 and UP2, carries out version and recover to rise
Level, i.e., the step A and step B of above-described embodiment 1 are performed successively, UP1 is preserved to the storage region damaged where invalid P2,
P1 upgrading is realized, i.e., NP1 as shown in the figure is preserved on memory, then UP2 is preserved to the storage where complete effective P1
Region, P2 upgrading is realized, i.e., NP2 as shown in the figure is preserved on memory.
Fig. 7 is single version update device block diagram provided in an embodiment of the present invention, as shown in fig. 7, comprises being used for storage version
Memory cell, for the edition upgrading unit of edition upgrading, for detecting the version detection unit of release status.
Before version startup, the detection of version detection unit is stored separately in the Part I and second of the version of memory cell
Whether part is complete effectively, wherein the Part I is stored in first area, the Part II is stored in second area.When
When version is completely effective, normally startup and edition upgrading are carried out, otherwise carries out abnormal startup and version recovery upgrading.Edition upgrading
When, edition upgrading unit stores the Part I of redaction to the second area, updates its version information mark, realizes the
Part upgrading, and the Part II of redaction is stored to the first area, its version information mark is updated, realizes second
Part upgrades.After restarting, the version newly upgraded is run.During edition upgrading, if Part I upgrading failure, described
Edition upgrading unit carries out version startup using the Part I of original version and recovers upgrading processing, i.e., will be new after version starts
The Part I of version is preserved to second area, and update its version information mark, then by the Part II of redaction preserve to
First area, and update its version information mark；If Part II upgrading failure, version is carried out using the Part I of redaction
This startup and recovery upgrading processing, i.e., after version starts, the Part I of redaction is preserved to first area, and update its version
This message identification, then the Part II of redaction is preserved to second area, and update its version information mark.Wherein, it is described
Version is at least divided into above-mentioned Part I and Part II, and at least there is the Part I version to start and recover upgrading work(
Can, the Part II has the other business and function of the version outside the Part I.
In summary, in summary, the present invention has following technique effect：
1st, the present invention realizes each stage of the product in upgrading, and all preserving one in memory can start and carry out
Version recovers the version P1 or NP1 of upgrading, so as to ensure, when abnormal interrupt occurs in edition upgrading, to remain able to start and carry out
Version recovers upgrading, ensure that the reliability of product up-gradation, reduces the O＆M cost of product.
2nd, product is designed using single software version, is made product memory only need to preserve single version, is reduced storage
The demand of device, reduce the holistic cost of product.
Although the present invention is described in detail above, the invention is not restricted to this, those skilled in the art of the present technique
Various modifications can be carried out according to the principle of the present invention.Therefore, all modifications made according to the principle of the invention, all should be understood to
Fall into protection scope of the present invention.
Claims (10)
- A kind of 1. single version upgrade method, it is characterised in that including：Single version is at least divided into separate Part I and Part II, and by the current version Part I of single version First area is stored in, the current version Part II of single version is stored in second area；When carrying out edition upgrading, redaction Part I is stored to described second where the current version Part II Region, the version information mark of the second area is updated, realizes that Part I upgrades；After Part I upgrading is realized, redaction Part II is stored to where the current version Part I described in First area, the version information mark of the first area is updated, realizes that Part II upgrades.
- 2. according to the method for claim 1, it is characterised in that at least there is the Part I version to start and recover to rise Level function, the Part II have the other business and function of the version outside the Part I.
- 3. method according to claim 1 or 2, it is characterised in that also include：If Part I upgrading failure, version startup is carried out using current version Part I, and carried out after version startup Recover upgrading processing.
- 4. according to the method for claim 3, it is characterised in that described the step of recovering upgrading processing includes：By redaction Part I is preserved to second area, and updates its version information mark, then redaction Part II is preserved to first area, And update its version information mark.
- 5. method according to claim 1 or 2, it is characterised in that also include：If Part II upgrading failure, using redaction Part I carry out version startup, and version startup after carry out it is extensive Multiple upgrading processing.
- 6. according to the method for claim 5, it is characterised in that described the step of recovering upgrading processing includes：By redaction Part I is preserved to first area, and updates its version information mark, then redaction Part II is preserved to second area, And update its version information mark.
- 7. the method according to claim 4 or 6, it is characterised in that before version startup, detect version Part I and the Whether two parts are complete effectively.
- A kind of 8. single version update device, it is characterised in that including：Memory cell, for storing the separate current version first of single version respectively in its first area and second area Part and current version Part II；Edition upgrading unit, during for edition upgrading, redaction Part I is stored to the current version Part II institute The second area, update the version information mark of the second area, realize that Part I upgrades, and realizing first After part upgrades, redaction Part II is stored to the first area where the current version Part I, renewal The version information mark of the Part I, realizes that Part II upgrades.
- 9. device according to claim 8, it is characterised in that the edition upgrading unit is additionally operable to when Part I upgrades During failure, carry out version startup using current version Part I and recover upgrading processing, when Part II upgrades failure, profit Version startup is carried out with redaction Part I and recovers upgrading processing, wherein, the Part I at least there is version to start With recovery upgrade function, the Part II has the other business and function of the version outside the Part I.
- 10. device according to claim 9, it is characterised in that also include：Whether version detection unit is complete effectively for before version starts, detecting version Part I and Part II.
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 CN103713911A (en) | 2014-04-09 |
| CN103713911B true 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) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
| CN111831297B (en) * | 2019-04-17 | 2021-10-26 | 中兴通讯股份有限公司 | Zero-difference upgrading method and device |
| CN110943871B (en) * | 2019-12-27 | 2022-11-01 | 杭州迪普科技股份有限公司 | Resource interval adjusting method and device |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2003316595A (en) * | 2002-04-23 | 2003-11-07 | Casio Comput Co Ltd | Installation method, file updating method, its program and computer system |
-
2012
- 2012-09-28 CN CN201210370432.2A patent/CN103713911B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103713911A (en) | 2014-04-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102238093B (en) | Service interruption prevention method and device | |
| CN103092712B (en) | A kind of tasks interrupt restoration methods and equipment | |
| US7047448B2 (en) | Software self-repair toolkit for electronic devices | |
| EP3147782A1 (en) | Method and device for upgrading software | |
| CN107291516A (en) | A kind of firmware upgrade method and system | |
| CN109491698B (en) | System updating method and device based on hot patch | |
| CN103713911B (en) | A kind of single version upgrade method and device | |
| CN104461786B (en) | The restoration methods of android system and the recovery system of android system | |
| CN104918114B (en) | A kind of operating system update method and device | |
| CN104679611B (en) | Data resource clone method and device | |
| CN103890736A (en) | Message reconciliation during disaster recovery | |
| US20070220506A1 (en) | Software update method, update management program and information processing apparatus | |
| US7818622B2 (en) | Method for recovering data processing system failures | |
| CN104217137A (en) | Method and device for identifying whether intelligent terminal system is changed | |
| CN102411523A (en) | Method and device for storing file backups and backup method for file systems | |
| CN101639785A (en) | Method and device for software updating | |
| CN103034803B (en) | Dress software prompt system by mistake | |
| CN102541595A (en) | Method and device for upgrading intelligent device and intelligent device | |
| CN108322540A (en) | Customized data lead-in method, terminal and computer readable storage medium | |
| CN102339264B (en) | A kind of satellite borne electronic system equipment plug and play control method and system | |
| CN105573788B (en) | The method and apparatus of patch processing and the method and apparatus for generating patch | |
| CN103544151B (en) | The method and system of data processing in Linux system | |
| CN102073523B (en) | Realize the method and device of software version synchronization | |
| CN106055372A (en) | Method and device for uninstalling application | |
| CN117056115A (en) | Application program repairing method and device, storage medium and electronic equipment |
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 |