CN101169719A - Method and system for implementing data upgrading and upgraded client terminal - Google Patents
Method and system for implementing data upgrading and upgraded client terminal Download PDFInfo
- Publication number
- CN101169719A CN101169719A CNA2007101882714A CN200710188271A CN101169719A CN 101169719 A CN101169719 A CN 101169719A CN A2007101882714 A CNA2007101882714 A CN A2007101882714A CN 200710188271 A CN200710188271 A CN 200710188271A CN 101169719 A CN101169719 A CN 101169719A
- Authority
- CN
- China
- Prior art keywords
- version
- family
- upgrading
- legacy
- upgraded
- 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
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method for realizing data update for updating from an old version to a new version. The method comprises determining a version family in which the new version and the old version locate according to the pre-divided version family, wherein the version family supports the direct over-version data update therein; determining an update path from the old version to the new version according to the version family in which the new version and the old version locate and over-version supporting direct data update in the version family and the version supporting strategy among the version families; and performing data update according to the update path. The embodiment of the invention also discloses a system and an update client-side. The invention can improve the performance of data update.
Description
Technical field
The present invention relates to computer realm, particularly a kind of method, system and updating client of realizing the data upgrading.
Background technology
Usually, edition upgrading comprises software upgrading and two partial contents of data upgrading.Such as, the user may be for reasons such as fixed software leak (BUG) or enhancing software functions, the software that needs use manufacturer's the original upgrading of new edition oneself, and the complicated software system that differs greatly for running environment, such as, the communication software system generally need dispose correspondingly data according to running environment.That is to say, the new supporting data of software may change at aspects such as content and forms, such as, the increasing, delete, change etc. of tables of data, cause the data of old software directly in new software, not use, therefore need in upgrade software, carry out corresponding upgrading, thereby avoid the user after finishing software upgrading, to reset Configuration Data again data.
Introduce a kind of method that realizes the data upgrading below, the principle of this method is: when the exploitation redaction, each redaction is only considered the data upgrading at previous release, thereby carrying out data when upgrading, if relate to the data upgrading of crossing over a plurality of versions, the employing method of upgrading in proper order then, carry out the data upgrading successively, such as, the existing V1 in market, 9 versions such as V2...V9.If there is the V1 version need be upgraded to V10, adopt mode as shown in Figure 1 so, promptly V1 must be upgraded to V2 earlier, is upgraded to V3...V10 more successively, thereby this method needs the data upgrading number of times of execution more when crossing over a plurality of version, and speed is slower.
And, because the variation to some data in the intermediate releases does not have transitivity, thereby may produce incorrect updating result, such as, the V1 version has a tables of data t1, deleted this table among the V2, again t1 has been increased among the V3, the result of order upgrading is exactly that data among the t1 have all been lost so.
As seen, realize the method for data upgrading at present, updating speed causes loss of data more slowly and easily, thereby data upgrading poor-performing.
Summary of the invention
In view of this, the embodiment of the invention provides a kind of method that realizes the data upgrading, and this method can improve data upgrading performance.
The embodiment of the invention also provides a kind of system that realizes the data upgrading, and this system can improve data upgrading performance.
The embodiment of the invention also provides a kind of updating client, and this client can improve data upgrading performance.
For achieving the above object, the technical scheme of the embodiment of the invention specifically is achieved in that
A kind of method that realizes the data upgrading is used for being upgraded to redaction from legacy version, and this method comprises:
According to the version family that divides in advance, determine the version family at described new, legacy version place, support the immediate data of cross-version to upgrade in the described version family;
According to supporting the immediate data upgrading of cross-version and the Version Support Policy between version family in the version family at described new, legacy version place, the described version family, determine to be upgraded to the upgrading path of redaction from legacy version;
According to described upgrading path, carry out the data upgrading.
A kind of system that realizes the data upgrading, this system comprises:
Updating client is used for according to the version family that divides in advance, determines the version family at described new, legacy version place, supports the immediate data of cross-version to upgrade in the described version family; According to supporting the immediate data upgrading of cross-version and the Version Support Policy between version family in the version family at described new, legacy version place, the described version family, determine to be upgraded to the upgrading path of redaction from legacy version;
Subsystem to be upgraded is used for according to described upgrading path, carries out the data upgrading.
A kind of updating client, this updating client comprises:
Version family determination module is used for according to the version family that divides in advance, determines the version family at described new, legacy version place, supports the immediate data of cross-version to upgrade in the described version family;
The upgrading path determination module, Version Support Policy between the version family that supports the immediate data upgrading of cross-version in the version family at new, the legacy version place that obtains according to described version family determination module, the described version family and set in advance determines to be upgraded to from legacy version the upgrading path of redaction.
As seen from the above technical solution, method, system and the updating client of the realization edition upgrading that the embodiment of the invention provides, adopted with version family is the data upgrading mode of unit, in same version family, support the immediate data upgrading of cross-version, thereby can effectively reduce the number of times that cross-version is upgraded, improve updating speed, and since in same version family the version support directly upgrade, thereby can avoid the problem of loss of data.
Description of drawings
Fig. 1 is the synoptic diagram of data upgrading in the prior art;
Fig. 2 is the synoptic diagram of data upgrading in the first embodiment of the invention;
Fig. 3 is the synoptic diagram of data upgrading in the second embodiment of the invention;
The data updating method process flow diagram of Fig. 4 for adopting in the embodiment of the invention;
The data upgrade-system structural representation of Fig. 5 for adopting in the embodiment of the invention.
Embodiment
For making purpose of the present invention, technical scheme and advantage clearer, below with reference to the accompanying drawing embodiment that develops simultaneously, the present invention is described in further detail.
The method of realization data that present embodiment provides upgrading comprises: according to the version family that divides in advance, determine the version family at described new, legacy version place, support the immediate data of cross-version to upgrade in the described version family; According to supporting the immediate data upgrading of cross-version and the Version Support Policy between version family in the version family at described new, legacy version place, the described version family, determine to be upgraded to the upgrading path of redaction from legacy version; According to described upgrading path, carry out the data upgrading.Here, the Version Support Policy between version family comprises: in adjacent two version families, at least one version that comprises first version in the more recent version family is supported from the immediate data upgrading than last version of legacy version family.The invention will be further described for example for following mask body.
Fig. 2 is a process synoptic diagram of realizing the data upgrading in the first embodiment of the invention.Wherein, band arrow solid line is represented to support to stride the immediate data upgrading path of a plurality of versions in the version family, and is with the arrow dotted line to represent the data upgrading path of supporting between version family.As shown in Figure 2,6 versions in the present embodiment are divided into two version families, and support to stride the direct upgrading of a plurality of versions in same version family, such as, support the direct upgrading of version 1 to version 3.Here, the partition strategy of version family is to divide according to difference size new, legacy version, such as, when the exploitation edition 4, the data of finding edition 4 and version 3, version 2 and version 1 have bigger variation at aspects such as structure, contents, thereby with edition 4 first version, thereby realize the division of version family as redaction family.And in exploitation during version 3, when finding that the data variation of version 3 and version 2 and version 1 is little, then consider to upgrade at the data of version 1 and version 2 and dispose corresponding data ROMPaq, to realize the direct upgrading in the same version family.Certainly, also can adopt other partition strategy, divide such as waiting according to number of versions.
In the present embodiment, Version Support Policy between version family is: in adjacent two version families, any one version of more recent version family is all supported the direct upgrading than last version of legacy version family, and as shown in Figure 2, the edition 4 in the version family 2,5 and 6 is all supported the direct upgrading of version 3.In the present embodiment, version 3 is last version in the version family 1.Present embodiment can be at exploitation edition 4,5 and 6 o'clock, according to new, the legacy version family that have marked off, considers to upgrade at the immediate data of version 3 and disposes corresponding data ROMPaq.
In the present embodiment, upgrading for cross-version family, be upgraded to version 6 such as version 2, the upgrading path that adopts is: earlier version 2 is upgraded to the latest edition in the same version family, it is version 3, then because version 3 is supported the direct upgrading of version 6, thereby directly be upgraded to version 6 by version 3 and get final product, promptly version 2-＞version 3-＞version 6.
Certainly, Version Support Policy between version family also can be: in adjacent two version families, have only the direct upgrading of first version support of more recent version family than last version of legacy version family, Fig. 3 is a process synoptic diagram of realizing the data upgrading in the second embodiment of the invention.Equally, band arrow solid line is represented to support to stride the immediate data upgrading path of a plurality of versions in the version family, and is with the arrow dotted line to represent the data upgrading path of supporting between version family.As shown in Figure 3, the edition 4 in the version family 2 is supported the direct upgrading of version 3.In this case equally when version 2 is upgraded to version 6, the upgrading path that adopts is: earlier version 2 is upgraded to the latest edition in the same version family, it is version 3, then directly be upgraded to first version of adjacent redaction family from version 3, it is edition 4, at last, directly be upgraded to version 6 from edition 4 again, promptly version 2-＞version 3-＞edition 4-＞version 6.
In addition, Version Support Policy between version family can also be: in adjacent two version families, first version of more recent version family and the part version of more recent version family are supported the direct upgrading than last version of legacy version family, such as, the edition 4 of version family 2 and version 5 are supported the direct upgrading of the version 3 of version family 1 among Fig. 2.
In the present embodiment, because a plurality of versions have been carried out the division of version family and can reduce the version of going through when data are upgraded based on the direct escalation policy of dividing, thereby saved the data updating time, and owing to when dividing version family, considered data variation difference, thereby can avoid the problem of the loss of data that causes owing to data variation is excessive.
The method flow synoptic diagram that Fig. 4 upgrades for the data that adopt in the second embodiment of the invention.In the present embodiment, each version provides independent data ROMPaq, this data ROMPaq support is converted to the redaction data to the legacy data in the same version family, the data of last version of data ROMPaq support upgrading legacy version family of first version in version family.As shown in Figure 4, mainly may further comprise the steps:
Step 401: updating client is to the version number of system queries to be upgraded system to be upgraded.
In the present embodiment, updating client obtains the version information of system to be upgraded by to system queries to be upgraded, and the version information of upgrade-system shows as the form of version number.
Step 402: system to be upgraded is to the version number of updating client retrieval system.
Step 403: updating client is determined version family new, the legacy version place according to new, old edition this shop and according to the version family that divides in advance.
In the present embodiment, the data ROMPaq of a version is supported the direct upgrading from any lowest version of same version family to this version.This division is identical with the method for embodiment one and embodiment two, does not give unnecessary details one by one here.
Step 404: updating client is determined upgrading path according to supporting the immediate data upgrading of cross-version and the Version Support Policy between version family in the version family at described new, legacy version place, the described version family.
In the present embodiment, suppose that the Version Support Policy between version family is: in adjacent two version families, the data ROMPaq of first version of more recent version family is supported from the immediate data upgrading than last version of legacy version family, thereby the method for definite upgrading path is: when newly, when the version family at old edition this shop place is same version family, the upgrading path of determining is the path of directly upgrading, otherwise, the upgrading path of determining is for directly being upgraded to last version of this version family earlier from legacy version, be upgraded to first version of adjacent redaction family again, by that analogy, progressively be upgraded to latest edition, in second embodiment, version 2 is to the upgrading path of version 6.
Step 405: the data ROMPaq that updating client selects upgrading path to need.
In the present embodiment, the data ROMPaq can be separated execution with the software of redaction as independent program file.Such as, from the version 2 to the version, 6 carry out data when upgrading at needs, the data ROMPaq of selecting from the version 2 to the version 3 the data ROMPaq and from the version 3 to the version 6 data ROMPaq.
Step 406: updating client issues the data ROMPaq to system to be upgraded.
In the present embodiment, select earlier to issue the data ROMPaq that in the data escalation process, should use to system to be upgraded again by updating client, can certainly directly issue all data ROMPaq, select the data ROMPaq that to use in the data escalation process by system to be upgraded voluntarily to system to be upgraded.
Step 407: system to be upgraded carries out the data ROMPaq successively according to upgrading path.
In the present embodiment, system to be upgraded finishes the data upgrading by carrying out the data ROMPaq.
Step 408: system to be upgraded sends data upgrading response to updating client.
In the present embodiment, updating client knows that by data upgrading response versions of data converts.
Step 409: updating client is to the new software of system downloads to be upgraded.
Step 410: updating client sends to system to be upgraded restarts the system software indication.
Step 411: system to be upgraded moves new software, directly uses the data after upgrading.
In the present embodiment, behind the data escalation process of first execution in step 406～step 408, the software upgrade process of execution in step 409～step 410 also can adopt opposite execution sequence certainly again.
Certainly, for first embodiment of the invention, Version Support Policy between version family is: in adjacent two version families, the data ROMPaq of all versions of more recent version family is supported from the immediate data upgrading than last version of legacy version family, in this case, the method of determining upgrading path is: when newly, when the version family at old edition this shop place is same version family, the upgrading path of determining is the path of directly upgrading, otherwise, the upgrading path of determining is: last version that directly is upgraded to this version family earlier from legacy version, when latest edition is not in adjacent version family, directly be upgraded to last version of adjacent redaction family, in adjacent version family, directly be upgraded to latest edition again up to latest edition, such as, the version 2 among first embodiment is to the upgrading path of version 6.
Data ROMPaq in the present embodiment is a single program, can certainly be as the part in the new software, updating client to system downloads to be upgraded behind the new software, from new software, select the data ROMPaq that should use in the data escalation process voluntarily according to upgrading path by system to be upgraded.
The system architecture synoptic diagram that Fig. 5 upgrades for the data that adopt in the embodiment of the invention.Referring to Fig. 5, this system comprises:
Updating client 510 according to the version family that divides in advance, is determined the version family at described new, legacy version place, supports the immediate data of cross-version to upgrade in the same described version family; According to supporting the immediate data upgrading of cross-version and the Version Support Policy between version family in the version family at new, legacy version place, the described version family, determine to be upgraded to the upgrading path of redaction from legacy version.
Particularly, subsystem 520 to be upgraded comprises:
Updating client 510 comprises:
Version family determination module 511 according to the version family that divides in advance, is determined the version family at described new, legacy version place, supports the immediate data of cross-version to upgrade in the same described version family.
Upgrading path determination module 512, Version Support Policy between the version family that supports the immediate data upgrading of cross-version in the version family at new, the legacy version place that obtains according to version family determination module 511, the described version family and set in advance determines to be upgraded to from legacy version the upgrading path of redaction.
Wherein, upgrading path determination module 512 comprises:
The above is preferred embodiment of the present invention only, is not to be used to limit protection scope of the present invention.All any modifications of being done within the spirit and principles in the present invention, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (11)
1. a method that realizes the data upgrading is used for being upgraded to redaction from legacy version, it is characterized in that this method comprises:
According to the version family that divides in advance, determine the version family at described new, legacy version place, support the immediate data of cross-version to upgrade in the described version family;
According to supporting the immediate data upgrading of cross-version and the Version Support Policy between version family in the version family at described new, legacy version place, the described version family, determine to be upgraded to the upgrading path of redaction from legacy version;
According to described upgrading path, carry out the data upgrading.
2. method according to claim 1, it is characterized in that, dividing described version family comprises: during each version between described legacy version of exploitation and described redaction, according to the partition strategy that sets in advance, whether the version of judging exploitation belongs to same version family with previous release, when the version of judging exploitation and previous release do not belong to same version family, with the version of exploitation as first version in the redaction family.
3. method according to claim 1, it is characterized in that, Version Support Policy between described version family comprises: in adjacent two version families, at least one version that comprises first version in the more recent version family is supported from the immediate data upgrading than last version of legacy version family.
4. method according to claim 1 is characterized in that, the Version Support Policy between described version family comprises: in adjacent two version families, first version in the more recent version family supports from the immediate data upgrading than last version of legacy version family,
Describedly determine that the upgrading path that is upgraded to redaction from legacy version comprises: when version family new, the legacy version place is same version family, the upgrading path of determining is: the path of directly upgrading from the legacy version to the redaction, otherwise, the upgrading path of determining is: last version that directly is upgraded to same version family earlier from described legacy version, directly be upgraded to first version of adjacent more recent version family again, by that analogy, progressively be upgraded to described redaction.
5. method according to claim 1 is characterized in that, the Version Support Policy between described version family comprises: in adjacent two version families, all versions in the more recent version family support from the immediate data upgrading than last version of legacy version family,
Describedly determine that the upgrading path that is upgraded to redaction from legacy version comprises: when version family new, the legacy version place is same version family, the upgrading path of determining is: the path of directly upgrading from the legacy version to the redaction, otherwise, the upgrading path of determining is: last version that directly is upgraded to same version family earlier from legacy version, when described redaction is not in adjacent more recent version family, directly be upgraded to last version of adjacent redaction family, in adjacent more recent version family, directly be upgraded to described redaction up to described redaction again.
6. method according to claim 1 is characterized in that, describedly carries out data upgradings and comprises:
According to each version that experiences in the described upgrading path, carry out the data ROMPaq that described each version uses successively.
7. system that realizes data upgradings is characterized in that this system comprises:
Updating client is used for according to the version family that divides in advance, determines the version family at described new, legacy version place, supports the immediate data of cross-version to upgrade in the described version family; According to supporting the immediate data upgrading of cross-version and the Version Support Policy between version family in the version family at described new, legacy version place, the described version family, determine to be upgraded to the upgrading path of redaction from legacy version;
Subsystem to be upgraded is used for according to described upgrading path, carries out the data upgrading.
8. system according to claim 7 is characterized in that, described updating client comprises:
Version family determination module is used for according to the version family that divides in advance, determines the version family at described new, legacy version place, supports the immediate data of cross-version to upgrade in the described version family;
The upgrading path determination module, Version Support Policy between the version family that supports the immediate data upgrading of cross-version in the version family at new, the legacy version place that obtains according to described version family determination module, the described version family and set in advance determines to be upgraded to from legacy version the upgrading path of redaction.
9. system according to claim 7 is characterized in that, described subsystem to be upgraded comprises:
Acquisition module is used for obtaining the employed data ROMPaq of each version of described upgrading path;
Execution module, each version that is used for experiencing according to described upgrading path is carried out described each edition data ROMPaq that described acquisition module obtains successively.
10. a updating client is characterized in that, this updating client comprises:
Version family determination module is used for according to the version family that divides in advance, determines the version family at described new, legacy version place, supports the immediate data of cross-version to upgrade in the described version family;
The upgrading path determination module, Version Support Policy between the version family that supports the immediate data upgrading of cross-version in the version family at new, the legacy version place that obtains according to described version family determination module, the described version family and set in advance determines to be upgraded to from legacy version the upgrading path of redaction.
11. updating client according to claim 10 is characterized in that, described upgrading path determination module comprises:
First performance element, the Version Support Policy that is used between version family is adjacent two version families, all versions in the more recent version family are supported from than the immediate data upgrading of last version of legacy version family the time, when newly, when the version family at legacy version place is same version family, the upgrading path of determining is: the path of directly upgrading from the legacy version to the redaction, otherwise, the upgrading path of determining is: last version that directly is upgraded to same version family earlier from described legacy version, directly be upgraded to first version of adjacent more recent version family again, by that analogy, progressively be upgraded to described redaction;
Second performance element, the Version Support Policy that is used between version family is adjacent two version families, all versions in the more recent version family are supported from than the immediate data upgrading of last version of legacy version family the time, when newly, when the version family at legacy version place is same version family, the upgrading path of determining is: the path of directly upgrading from the legacy version to the redaction, otherwise, the upgrading path of determining is: last version that directly is upgraded to same version family earlier from legacy version, when described redaction is not in adjacent more recent version family, directly be upgraded to last version of adjacent redaction family, in adjacent more recent version family, directly be upgraded to described redaction up to described redaction again.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2007101882714A CN100517226C (en) | 2007-11-30 | 2007-11-30 | Method and system for implementing data upgrading and upgraded client terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2007101882714A CN100517226C (en) | 2007-11-30 | 2007-11-30 | Method and system for implementing data upgrading and upgraded client terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101169719A true CN101169719A (en) | 2008-04-30 |
| CN100517226C CN100517226C (en) | 2009-07-22 |
Family
ID=39390358
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2007101882714A Active CN100517226C (en) | 2007-11-30 | 2007-11-30 | Method and system for implementing data upgrading and upgraded client terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100517226C (en) |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101815151A (en) * | 2009-02-25 | 2010-08-25 | 佳能株式会社 | Firmware updating device and firmware update |
| CN101968741A (en) * | 2009-07-27 | 2011-02-09 | 阿里巴巴集团控股有限公司 | Method, server and system for data update |
| CN101673205B (en) * | 2009-09-28 | 2012-07-04 | 杭州华三通信技术有限公司 | Interface board upgrading method and system |
| CN105320548A (en) * | 2015-11-30 | 2016-02-10 | 小米科技有限责任公司 | Terminal system updating method and device |
| CN106470114A (en) * | 2015-08-20 | 2017-03-01 | 青岛海信移动通信技术股份有限公司 | A kind of collocation method of OTA AKU and device |
| CN106470227A (en) * | 2015-08-20 | 2017-03-01 | 青岛海信移动通信技术股份有限公司 | A kind of collocation method of OTA AKU and device |
| WO2017088547A1 (en) * | 2015-11-27 | 2017-06-01 | 中兴通讯股份有限公司 | Data upgrading method and apparatus |
| CN106850800A (en) * | 2017-01-24 | 2017-06-13 | 腾讯科技（深圳）有限公司 | Method and client that a kind of download path determines |
| CN106843984A (en) * | 2017-02-13 | 2017-06-13 | 东软集团股份有限公司 | The update method and device of application database |
| WO2018006677A1 (en) * | 2016-07-06 | 2018-01-11 | 中兴通讯股份有限公司 | Smart upgrade method, server, terminal and system |
| CN111475185A (en) * | 2020-03-11 | 2020-07-31 | 苏州浪潮智能科技有限公司 | Method and system for stably upgrading BMC (baseboard management controller) image across large versions |
| CN111684416A (en) * | 2018-02-16 | 2020-09-18 | 日立汽车***株式会社 | Vehicle control device and program update system |
| CN115328773A (en) * | 2022-08-04 | 2022-11-11 | 北京志凌海纳科技有限公司 | Test method for software version upgrading combined with after-sale system |
-
2007
- 2007-11-30 CN CNB2007101882714A patent/CN100517226C/en active Active
Cited By (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101815151A (en) * | 2009-02-25 | 2010-08-25 | 佳能株式会社 | Firmware updating device and firmware update |
| CN101815151B (en) * | 2009-02-25 | 2012-11-28 | 佳能株式会社 | Firmware updating apparatus and firmware updating method |
| US8612965B2 (en) | 2009-02-25 | 2013-12-17 | Canon Kabushiki Kaisha | Firmware updating apparatus, firmware updating method, and storage medium |
| CN101968741A (en) * | 2009-07-27 | 2011-02-09 | 阿里巴巴集团控股有限公司 | Method, server and system for data update |
| CN101673205B (en) * | 2009-09-28 | 2012-07-04 | 杭州华三通信技术有限公司 | Interface board upgrading method and system |
| CN106470227B (en) * | 2015-08-20 | 2019-09-10 | 青岛海信移动通信技术股份有限公司 | A kind of configuration method and device of OTA upgrade package |
| CN106470114A (en) * | 2015-08-20 | 2017-03-01 | 青岛海信移动通信技术股份有限公司 | A kind of collocation method of OTA AKU and device |
| CN106470227A (en) * | 2015-08-20 | 2017-03-01 | 青岛海信移动通信技术股份有限公司 | A kind of collocation method of OTA AKU and device |
| WO2017088547A1 (en) * | 2015-11-27 | 2017-06-01 | 中兴通讯股份有限公司 | Data upgrading method and apparatus |
| CN105320548B (en) * | 2015-11-30 | 2019-02-15 | 小米科技有限责任公司 | Terminal system upgrade method and device |
| CN105320548A (en) * | 2015-11-30 | 2016-02-10 | 小米科技有限责任公司 | Terminal system updating method and device |
| WO2018006677A1 (en) * | 2016-07-06 | 2018-01-11 | 中兴通讯股份有限公司 | Smart upgrade method, server, terminal and system |
| CN106850800A (en) * | 2017-01-24 | 2017-06-13 | 腾讯科技（深圳）有限公司 | Method and client that a kind of download path determines |
| CN106843984A (en) * | 2017-02-13 | 2017-06-13 | 东软集团股份有限公司 | The update method and device of application database |
| CN111684416A (en) * | 2018-02-16 | 2020-09-18 | 日立汽车***株式会社 | Vehicle control device and program update system |
| CN111684416B (en) * | 2018-02-16 | 2023-09-29 | 日立安斯泰莫株式会社 | Vehicle control device and program update system |
| CN111475185A (en) * | 2020-03-11 | 2020-07-31 | 苏州浪潮智能科技有限公司 | Method and system for stably upgrading BMC (baseboard management controller) image across large versions |
| CN115328773A (en) * | 2022-08-04 | 2022-11-11 | 北京志凌海纳科技有限公司 | Test method for software version upgrading combined with after-sale system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN100517226C (en) | 2009-07-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100517226C (en) | Method and system for implementing data upgrading and upgraded client terminal | |
| US8645945B2 (en) | Method and apparatus for dynamic middleware assembly | |
| US9301164B2 (en) | Method, system, and terminal for performing system update between mobile communication terminals | |
| US7555640B2 (en) | Mobile electronic device with fragmented device settings | |
| CN102650947B (en) | Continuous increment over-the-air upgrade method of Android handheld equipment | |
| EP3001309A1 (en) | Application migration method, device and system for mobile terminal | |
| CN108279922A (en) | Differential file generation method, upgrade method and system based on the differential file | |
| CN111078318A (en) | Method, device and system for processing configuration file and storage medium | |
| US8935688B2 (en) | Methods for facilitating updates at an information handling device | |
| WO1999066399A9 (en) | Method to reflect bios setup changes into acpi machine language | |
| CN113821235B (en) | Operating system data updating method, device, storage medium and program product | |
| US9367299B2 (en) | Preventing application downgrade in an application store | |
| CN113821221B (en) | Method, apparatus and storage medium for installing operating system | |
| CN109150608A (en) | Interface service upgrade method and system for voice dialogue platform | |
| CN109885332A (en) | Image quality chip software upgrade method, device, display equipment and storage medium | |
| US9934044B2 (en) | Methods for customizing an operating system at an information handling device | |
| US7533374B2 (en) | Adaptively storing system code in non-volatile storage | |
| US10521216B2 (en) | Unified extensible firmware interface updates | |
| CN104657164A (en) | Method and device for updating and processing software | |
| US9182970B2 (en) | Methods for creating device preload via manufacturing and cloud content | |
| WO2015176498A1 (en) | Software upgrade method, mobile terminal and computer storage medium | |
| CN106502750A (en) | OTA upgrade methods and Bluetooth chip | |
| CN102123372B (en) | Method and system for dynamically loading subchannel content of information terminal | |
| CN105740006A (en) | Cross-platform service providing method of wearable intelligent device based on transparent computing | |
| CN104778068A (en) | Management system and management method of software installation package for mobile terminal |
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 |