CN107436783B - Differential upgrading method for mobile terminal, storage medium and mobile terminal - Google Patents
Differential upgrading method for mobile terminal, storage medium and mobile terminal Download PDFInfo
- Publication number
- CN107436783B CN107436783B CN201710575496.9A CN201710575496A CN107436783B CN 107436783 B CN107436783 B CN 107436783B CN 201710575496 A CN201710575496 A CN 201710575496A CN 107436783 B CN107436783 B CN 107436783B
- Authority
- CN
- China
- Prior art keywords
- backup
- partition
- file
- upgrading
- mobile terminal
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/658—Incremental updates; Differential updates
Abstract
The invention discloses a differential upgrading method for a mobile terminal, a storage medium and the mobile terminal, wherein the method comprises the following steps: when the difference is upgraded, backing up the source data block of the system partition to the cache partition; if abnormal power failure restart occurs in the upgrading process, backing up the source data blocks which are not backed up in the system partition to the cache partition; and when the backup is finished, releasing the backup file which is not configured with the unique identifier in the cache partition, and continuing to perform differential upgrading. The method generates the unique identifier through the backup file of the source data block which is not backed up in the differential upgrading process, re-verifies the source data block in the system partition when abnormal power failure restarting is sent in the upgrading process, releases the backup file saved in the cache partition in the verification process when the backup is finished, and reserves the file configured with the unique identifier. Therefore, the backup files saved in the verification process are deleted, the occupation of cache partition cache is reduced, the backup files required by differential upgrading are reserved, and the requirement of continuous upgrading after power failure is met.
Description
Technical Field
The invention relates to the technical field of intelligent terminals, in particular to a differential upgrading method for a mobile terminal, a storage medium and the mobile terminal.
Background
The Android mobile phone upgrade is carried out in a differential upgrade (Block-ota) mode. Block-ota is upgraded by differencing the source data blocks of the system partition of the handset, moving or filling in new data blocks. Before the data block is modified, the backup of the source data block on the system partition needs to be stored in the cache partition, so that the condition that the data block on the system partition is only partially upgraded due to the fact that a mobile phone is accidentally powered off (for example, a battery is pulled out and the like) in the upgrading process is avoided, and the data block cannot be upgraded continuously after being powered on again.
However, in the existing differential upgrading method, when power is lost in the upgrading process and the upgrading is continued after restarting, excessive useless backup files can be generated, and a large amount of cache partition space is consumed. Moreover, the cache partition of the mobile terminal is generally only hundreds of megabytes, so that when the space of the cache partition is insufficient, a new backup file cannot be stored, and the problem of failure in upgrading is caused.
Thus, the prior art has yet to be improved and enhanced.
Disclosure of Invention
The technical problem to be solved by the present invention is to provide a differential upgrade method for a mobile terminal, a storage medium and a mobile terminal, aiming at the defects of the prior art, so as to solve the problem that the upgrade fails due to insufficient storage space of a cache partition caused by a large amount of useless backup files generated in the prior differential upgrade process.
In order to solve the technical problems, the technical scheme adopted by the invention is as follows:
a differential upgrade method, comprising:
when differential upgrading is carried out, backing up a source data block of a system partition to a cache partition, and generating a unique identifier for a backup file;
if abnormal power failure restart occurs in the upgrading process, backing up source data blocks which are not backed up before power failure in the system partition to the cache partition;
and when the backup is finished, releasing the backup file which is not configured with the unique identifier in the cache partition, and continuing to perform differential upgrading.
The differential upgrade method for the mobile terminal, wherein, when performing differential upgrade, backing up a source data block of a system partition to a cache partition, and generating a unique identifier for a backup file specifically includes:
when the difference is upgraded, backing up a source data block of the system partition to the cache partition through a stash instruction, and creating an empty file;
naming the empty file by adopting the name of the backup file, and setting a first suffix for the empty file so as to enable the empty file to be used as the unique identifier of the backup file.
The differential upgrading method for the mobile terminal is characterized in that when the backup is completed, the method further comprises the following steps of releasing the backup file which is not configured with the unique identifier in the cache partition, and continuing to perform differential upgrading:
and when the upgrading is finished, executing a free instruction to release the backup file configured with the unique identifier and the unique identifier corresponding to the backup file.
The differential upgrade method for the mobile terminal, wherein the backing up the source data block of the system partition to the cache partition during differential upgrade further comprises:
when the difference is upgraded, backing up a source data block of the system partition to the cache partition through an imgdiff/bsdiff/move instruction, and creating an empty file;
naming the empty file by adopting the name of the backup file, and setting a second suffix for the empty file.
The differential upgrading method for the mobile terminal is characterized in that when the backup is completed, the method further comprises the following steps of releasing the backup file which is not configured with the unique identifier in the cache partition, and continuing to perform differential upgrading:
and when the upgrading is completed, automatically releasing the empty file with the second suffix and the corresponding backup file.
The differential upgrading method for the mobile terminal, wherein if abnormal power failure and restart occur in the upgrading process, backing up the source data blocks which are not backed up in the system partition to the cache partition specifically comprises the following steps:
if abnormal power failure restart occurs in the upgrading process, sequentially executing each push instruction;
when the push instruction is a successfully executed instruction, skipping the push instruction;
and if the stash instruction is an instruction which is not successfully executed, executing the stash instruction to backup a source data block corresponding to the stash instruction to the cache partition.
The differential upgrading method for the mobile terminal is characterized in that when the backup is completed, the backup file which is not configured with the unique identifier in the cache partition is released, and the differential upgrading is continuously carried out specifically as follows:
and when the backup is finished, executing a free instruction to release the backup file which is not configured with the unique identifier in the cache partition, and continuing to perform differential upgrading.
The differential upgrading method for the mobile terminal, wherein if an abnormal power outage restart occurs in the upgrading process, backing up the source data block that is not backed up in the system partition to the cache partition may specifically include:
when abnormal power-off restarting occurs, reading an upgrading identifier in a nonvolatile memory, and judging whether differential upgrading is completed or not according to the upgrading identifier;
if the differential upgrade is not completed, backing up the source data blocks which are not backed up in the system partition to the cache partition.
A storage medium storing a plurality of instructions adapted to be loaded by a processor and to perform a differential upgrade method for a mobile terminal as described in any one of the above.
A mobile terminal, comprising:
a processor adapted to implement instructions; and
a storage device adapted to store a plurality of instructions adapted to be loaded by a processor and to perform a differential upgrade method for a mobile terminal as described in any one of the above.
Has the advantages that: compared with the prior art, the invention provides a differential upgrading method for a mobile terminal, a storage medium and the mobile terminal, wherein the method comprises the following steps: when the difference is upgraded, backing up the source data block of the system partition to the cache partition; if abnormal power failure restart occurs in the upgrading process, backing up the source data blocks which are not backed up in the system partition to the cache partition; and when the backup is finished, releasing the backup file which is not configured with the unique identifier in the cache partition, and continuing to perform differential upgrading. The method generates a unique identifier for the backup file of the backed-up source data block in the differential upgrading process, re-verifies the source data block in the system partition when abnormal power failure restarting occurs in the upgrading process, releases the backup file saved in the cache partition in the verification process when the backup is finished, and reserves the file configured with the unique identifier. Therefore, the backup files saved in the verification process can be deleted, the temporary use of cache partition cache is reduced, the backup files required by differential upgrading are reserved, and the requirement of continuous upgrading after power failure is met.
Drawings
Fig. 1 is a flowchart of a differential upgrade method for a mobile terminal according to a preferred embodiment of the present invention.
Fig. 2 is a schematic structural diagram of a preferred embodiment of the mobile terminal according to the present invention.
Detailed Description
The present invention provides a differential upgrade method for a mobile terminal, a storage medium and a mobile terminal, and in order to make the purpose, technical scheme and effect of the present invention clearer and clearer, the present invention is further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
As used herein, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may also be present. Further, "connected" or "coupled" as used herein may include wirelessly connected or wirelessly coupled. As used herein, the term "and/or" includes all or any element and all combinations of one or more of the associated listed items.
It will be understood by those skilled in the art that, unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the prior art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
The invention will be further explained by the description of the embodiments with reference to the drawings.
Referring to fig. 1, fig. 1 is a flowchart illustrating a differential upgrade method for a mobile terminal according to a preferred embodiment of the present invention. The method comprises the following steps:
s100, when the differential upgrading process is carried out, backing up source data blocks of the system partition to a cache partition, and generating a unique identifier for a backup file;
s200, if abnormal power failure restart occurs in the upgrading process, backing up source data blocks which are not backed up before power failure in the system partition to the cache partition;
and S300, when the backup is finished, releasing the backup file which is not configured with the unique identifier in the cache partition, and continuing to perform differential upgrading.
In this embodiment, a unique identifier is generated for a backup file of a backed-up source data block in the differential upgrade process, the source data block in a system partition is re-verified when an abnormal power failure restart occurs in the upgrade process, the backup file saved in a cache partition in the verification process is released when the backup is completed, and the file configured with the unique identifier is reserved. Therefore, the backup files saved in the verification process can be deleted, the temporary use of cache partition cache is reduced, the backup files required by differential upgrading are reserved, and the requirement of continuous upgrading after power failure is met.
Specifically, in the step S100, the differential Block-ota upgrade is upgraded by means of patching, and the source data Block is saved in a recovery directory of the cache partition before patching, that is, a backup file is generated in the/cache/recovery directory. And when the abnormal power failure restart occurs in the upgrading process, selecting to print the patch again on the backup file, and then writing back to the system partition to complete the upgrading.
The Block-ota writes the upgrade process in the system.transfer.list file in the upgrade package by means of commands, which include six commands of push, free, imgdiff, bsdiff, move, new. The push command is used for storing the backup file into the cache partition, and deleting the backup file through the free command so as to avoid occupying the space of the cache partition all the time. The imgdiff/bsdiff command is used for differential upgrade and the move command is used for moving replication. And the Imgdiff/bsdiff/move command can automatically save the backup file to the cache partition in the operation process, and automatically delete the backup file after the command is successfully executed.
The Block-ota upgrade comprises two stages, namely a Block _ image _ verify stage and a Block _ image _ update stage. The block _ image _ verify phase executes each command in the system.transfer.list in sequence to verify whether a source data block or a backup file on a system partition is valid or not, so as to judge whether the upgrade can be continued or not, but the true upgrade operation cannot be performed. And the block _ image _ update stage sequentially executes commands of system.
In this embodiment, the differential upgrade refers to a block _ image _ update stage, and upgrades by sequentially executing system.
Illustratively, when the differential upgrade is performed, backing up the source data block of the system partition to the cache partition, and generating a unique identifier for the backup file specifically includes:
s101, when differential upgrading is carried out, backing up a source data block of a system partition to a cache partition through a stash instruction, and creating an empty file;
s102, naming the empty file by adopting the name of the backup file, and setting a first suffix for the empty file so as to enable the empty file to be used as the unique identifier of the backup file.
Specifically, in the block _ image _ update stage, an empty file with the same name but with an explicit _ starting suffix (denoted as a first suffix) is created for the backup file saved by the stack command, and the empty file serves as a unique identifier of the backup file and is used for indicating the backup file. Meanwhile, when a free command is encountered in the block _ image _ update stage, the backup file and the empty file which has the same name as the backup file and has the application _ starting suffix are deleted at the same time.
In step S200, if an abnormal power outage restart occurs during the upgrading process, re-executing the block _ image _ verify phase, and re-executing each stack instruction in sequence, and backing up the source data block that is not backed up to the cache partition.
For example, if an abnormal power outage restart occurs during the upgrade process, backing up the source data block that is not backed up in the system partition to the cache partition specifically includes:
s201, if abnormal power failure restart occurs in the upgrading process, executing each stash in sequence;
s202, when the push instruction is a successfully executed instruction, skipping the push instruction;
s203, if the push instruction is an instruction which is not successfully executed, executing the push instruction to backup the source data block corresponding to the push instruction to the cache partition.
Specifically, a unique identifier is configured for a backup file generated by each stack instruction executed in the block _ image _ verify stage, that is, an empty file with the same name and the extension _ start suffix is generated. Therefore, the block _ image _ update stage and the block _ image _ verify stage are separated from each other by the backup file generated by the state instruction.
In an embodiment of the present invention, if an abnormal power outage restart occurs during an upgrade process, backing up a source data block that is not backed up in a system partition to a cache partition may specifically include:
s10, when abnormal power-off restarting occurs, reading an upgrade identifier in a nonvolatile memory, and judging whether the differential upgrade is completed according to the upgrade identifier;
and S20, if the differential upgrade is not completed, backing up the source data blocks which are not backed up in the system partition to the cache partition.
Specifically, the upgrade identifier may be set when a Block-ota upgrade is performed, and is used to indicate an upgrade process identifier. The upgrade flag may be 1 and 0, where 1 indicates that the upgrade is not completed and 0 indicates that the upgrade is completed. That is, when an abnormal power outage restart occurs, if the upgrade flag in the nonvolatile memory is read to be 1, it is determined that the differential upgrade is not completed; and if the upgrade identifier in the nonvolatile memory is read to be 0, judging that the differential upgrade is finished.
In the step S300, the releasing of the backup file not configured with the unique identifier in the cache partition means that the backup file not configured with the unique identifier in the cache partition is released by executing a free instruction at the block _ image _ verify stage. When the free instruction encounters a backup file that has a file with the same name but with the duplicate _ start suffix, the backup file is skipped over without being deleted for subsequent upgrades. Therefore, when the block _ image _ verify stage is finished, only the backup files which are used in the last power failure and the empty files which have the same name but are provided with the explicit _ start suffix are reserved in the cache partition, but not all the backup files, so that the occupation of the cache space is reduced.
In an embodiment of the present invention, in the block _ image _ update stage, the imgdiff, bsdiff, and/or move commands may also backup the source data block on the system.img to be upgraded to the/cache/recovery directory before the upgrade action is performed. After the abnormal power failure is restarted, when the Block _ image _ verify stage is executed, because the Block-ota after the restart cannot determine whether the backup file is backed up by a stack command or automatically backed up by imgdiff/bsdiff/move and other operations, the backup file cannot be deleted. Thus, the backup files generated by imgdiff, bsdiff and/or move commands under the/cache/recovery still exist after the upgrade is completed. Then, if the mobile terminal is powered off again when the subsequent imgdiff/bsdiff/move and other operations are performed, the backup files related to the imgdiff/bsdiff/move operation exist all the time, and the problem that the space of the cache partition is insufficient along with the increase of the power-off times is solved.
Correspondingly, the step S100 of backing up the source data block of the system partition to the cache partition during the differential upgrade further includes:
h10, when differential upgrading, sequentially executing the backup of the source data blocks of the system partition to the cache partition through imgdiff/bsdiff/move instructions, and creating an empty file;
h20, naming the empty file by adopting the name of the backup file, and setting a second suffix for the empty file.
The step S300, when the backup is completed, releasing the backup file not configured with the unique identifier in the cache partition, and after the differential upgrade is continuously performed, further includes:
and S400a, automatically releasing the empty file with the second suffix and the corresponding backup file after differential upgrading.
Specifically, in the step H10, the upgrade stage referred to when upgrading differentially is the block _ image _ update stage. Creating an empty file refers to creating a file with the suffix of the same name and with the suffix of the implict _ start for the backup file automatically saved by the imgdiff/bsdiff/move command, so as to distinguish the file with the suffix of the same name and with the first suffix saved by the hash command. Thus, in the Block _ image _ update stage, Block-ota can know whether the backup file used by the imgdiff/bsdiff/move command is saved before the power failure (a file with the same name but with the. implict _ start suffix exists) or saved by the power failure prestate command (a file with the same name but with the. explicit _ start suffix exists).
Accordingly, in the step S401a, after the upgrade is successful, the backup file saved for the imgdiff/bsdiff/move command may be automatically deleted, and the file saved for the push command may be deleted when the free command is executed. Therefore, the backup file can be deleted after being used up, and the space of the cache is not occupied any more.
The present invention also provides a storage medium storing a plurality of instructions adapted to be loaded by a processor and to perform a differential upgrade method for a mobile terminal as set forth in any of the above
The present invention also provides a mobile terminal, as shown in fig. 2, which includes at least one processor (processor)20 (one processor 20 is taken as an example in fig. 2); a display screen 21; and a memory (memory)22, and may further include a communication Interface (Communications Interface)23 and a bus 24. The processor 20, the display 21, the memory 22 and the communication interface 23 can communicate with each other through the bus 24. The display screen 21 is configured to display a user guidance interface preset in the initial setting mode. The communication interface 23 may transmit information. The processor 20 may call logic instructions in the memory 22 to perform the methods in the embodiments described above.
Furthermore, the logic instructions in the memory 22 may be implemented in software functional units and stored in a computer readable storage medium when sold or used as a stand-alone product.
The memory 22, which is a computer-readable storage medium, may be configured to store a software program, a computer-executable program, such as program instructions or modules corresponding to the methods in the embodiments of the present disclosure. The processor 30 executes the functional application and data processing, i.e. implements the method in the above-described embodiments, by executing the software program, instructions or modules stored in the memory 22.
The memory 22 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the terminal device, and the like. Further, the memory 22 may include a high speed random access memory and may also include a non-volatile memory. For example, a variety of media that can store program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk, may also be transient storage media.
In addition, the specific processes loaded and executed by the storage medium and the instruction processors in the mobile terminal are described in detail in the method, and are not stated herein.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (8)
1. A differential upgrade method for a mobile terminal, comprising:
when differential upgrading is carried out, backing up a source data block of a system partition to a cache partition, and generating a unique identifier for a backup file;
if abnormal power failure restart occurs in the upgrading process, backing up source data blocks which are not backed up before power failure in the system partition to the cache partition;
when the backup is finished, releasing the backup files which are not configured with the unique identifier in the cache partition, and continuing to perform differential upgrading;
when the difference is upgraded, backing up the source data block of the system partition to the cache partition, and generating a unique identifier for the backup file specifically includes:
when the difference is upgraded, backing up a source data block of the system partition to the cache partition through a stash instruction, and creating an empty file;
naming the empty file by adopting the name of the backup file, and setting a first suffix for the empty file so as to enable the empty file to be used as the unique identifier of the backup file;
when the difference is upgraded, backing up a source data block of the system partition to the cache partition through an imgdiff/bsdiff/move instruction, and creating an empty file;
naming the empty file by adopting the name of the backup file, and setting a second suffix for the empty file.
2. The differential upgrade method for a mobile terminal according to claim 1, wherein when the backup is completed, the method further comprises, after releasing the backup file that is not configured with the unique identifier in the cache partition and continuing to perform differential upgrade:
and when the upgrading is finished, executing a free instruction to release the backup file configured with the unique identifier and the unique identifier corresponding to the backup file.
3. The differential upgrade method for a mobile terminal according to claim 1, wherein when the backup is completed, the method further comprises, after releasing the backup file that is not configured with the unique identifier in the cache partition and continuing to perform differential upgrade:
and when the upgrading is completed, automatically releasing the empty file with the second suffix and the corresponding backup file.
4. The differential upgrade method for a mobile terminal according to claim 1, wherein if an abnormal power outage restart occurs during the upgrade process, backing up the source data blocks that are not backed up in the system partition to the cache partition specifically comprises:
if abnormal power failure restart occurs in the upgrading process, sequentially executing each push instruction;
when the push instruction is a successfully executed instruction, skipping the push instruction;
and if the stash instruction is an instruction which is not successfully executed, executing the stash instruction to backup a source data block corresponding to the stash instruction to the cache partition.
5. The differential upgrade method for a mobile terminal according to claim 1, wherein when the backup is completed, releasing the backup file that is not configured with the unique identifier in the cache partition, and continuing the differential upgrade specifically comprises:
and when the backup is finished, executing a free instruction to release the backup file which is not configured with the unique identifier in the cache partition, and continuing to perform differential upgrading.
6. The differential upgrade method for a mobile terminal according to claim 1, wherein if an abnormal power outage restart occurs during the upgrade process, backing up a source data block that is not backed up in a system partition to a cache partition specifically includes:
when abnormal power-off restarting occurs, reading an upgrading identifier in a nonvolatile memory, and judging whether differential upgrading is completed or not according to the upgrading identifier;
if the differential upgrade is not completed, backing up the source data blocks which are not backed up in the system partition to the cache partition.
7. A storage medium storing a plurality of instructions adapted to be loaded by a processor and to perform the differential upgrade method for a mobile terminal according to any one of claims 1-6.
8. A mobile terminal, characterized in that it comprises:
a processor adapted to implement instructions; and
a storage device adapted to store a plurality of instructions adapted to be loaded by a processor and to perform the differential upgrade method for a mobile terminal according to any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710575496.9A CN107436783B (en) | 2017-07-14 | 2017-07-14 | Differential upgrading method for mobile terminal, storage medium and mobile terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710575496.9A CN107436783B (en) | 2017-07-14 | 2017-07-14 | Differential upgrading method for mobile terminal, storage medium and mobile terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107436783A CN107436783A (en) | 2017-12-05 |
| CN107436783B true CN107436783B (en) | 2021-04-20 |
Family
ID=60460203
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710575496.9A Active CN107436783B (en) | 2017-07-14 | 2017-07-14 | Differential upgrading method for mobile terminal, storage medium and mobile terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107436783B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113691845B (en) * | 2021-08-19 | 2023-08-18 | 杭州国芯科技股份有限公司 | Power-off protection method for digital set top box partition upgrade |
| CN114598493B (en) * | 2022-01-14 | 2023-09-05 | 浙江省通信产业服务有限公司 | Network traffic collection method |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH07160561A (en) * | 1993-12-03 | 1995-06-23 | Fuji Xerox Co Ltd | File managing device |
| CN101547469A (en) * | 2008-03-24 | 2009-09-30 | 华为技术有限公司 | Method, system and device for transmitting data |
| CN101697133A (en) * | 2009-10-26 | 2010-04-21 | 中兴通讯股份有限公司 | Software upgrading method, software upgrading system and client |
| CN102693145A (en) * | 2012-05-31 | 2012-09-26 | 红石阳光（北京）科技有限公司 | Differential upgrading method for embedded system |
| CN103473099A (en) * | 2013-09-13 | 2013-12-25 | 惠州Tcl移动通信有限公司 | Software upgrading method and system for mobile terminal |
| CN103823701A (en) * | 2014-03-10 | 2014-05-28 | 北京壹平台科技有限公司 | Mobile terminal product version automatic update control method |
| CN105094875A (en) * | 2014-05-19 | 2015-11-25 | 中兴通讯股份有限公司 | Software upgrading method and device |
| CN105867922A (en) * | 2016-03-29 | 2016-08-17 | 乐视控股（北京）有限公司 | Differential upgrade method and system |
| CN105867962A (en) * | 2015-12-07 | 2016-08-17 | 乐视移动智能信息技术（北京）有限公司 | System upgrading method and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP3968207B2 (en) * | 2000-05-25 | 2007-08-29 | 株式会社日立製作所 | Data multiplexing method and data multiplexing system |
-
2017
- 2017-07-14 CN CN201710575496.9A patent/CN107436783B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH07160561A (en) * | 1993-12-03 | 1995-06-23 | Fuji Xerox Co Ltd | File managing device |
| CN101547469A (en) * | 2008-03-24 | 2009-09-30 | 华为技术有限公司 | Method, system and device for transmitting data |
| CN101697133A (en) * | 2009-10-26 | 2010-04-21 | 中兴通讯股份有限公司 | Software upgrading method, software upgrading system and client |
| CN102693145A (en) * | 2012-05-31 | 2012-09-26 | 红石阳光（北京）科技有限公司 | Differential upgrading method for embedded system |
| CN103473099A (en) * | 2013-09-13 | 2013-12-25 | 惠州Tcl移动通信有限公司 | Software upgrading method and system for mobile terminal |
| CN103823701A (en) * | 2014-03-10 | 2014-05-28 | 北京壹平台科技有限公司 | Mobile terminal product version automatic update control method |
| CN105094875A (en) * | 2014-05-19 | 2015-11-25 | 中兴通讯股份有限公司 | Software upgrading method and device |
| CN105867962A (en) * | 2015-12-07 | 2016-08-17 | 乐视移动智能信息技术（北京）有限公司 | System upgrading method and device |
| CN105867922A (en) * | 2016-03-29 | 2016-08-17 | 乐视控股（北京）有限公司 | Differential upgrade method and system |
Non-Patent Citations (2)
| Title |
|---|
| "Android recovery分析（二）---增量升级包的编译流程";mrcc_yy;《https://blog.csdn.net/mrcc_yy/article/details/51620492?biz_id=102&utm_term=block-ota&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduweb~default-4-51620492&spm=1018.2118.3001.4187》;20160609;第1-8页 * |
| "Android手机软件升级技术综述";黄超 等;《科技展望》;20160720(第20期);第10页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107436783A (en) | 2017-12-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP5113700B2 (en) | Firmware update apparatus and method | |
| US8539471B2 (en) | Updating firmware of an electronic device | |
| CN103455354B (en) | Method and equipment for preventing hardware update from failing | |
| US20110004871A1 (en) | Embedded electronic device and firmware updating method thereof | |
| CN101026848B (en) | Mobile terminal and software update method | |
| CN111796856B (en) | Differential upgrading method and device, storage medium and computer equipment | |
| US20070055969A1 (en) | System and method for updating firmware | |
| CN103970557B (en) | The method and storage device of storage device activation system | |
| WO2011024688A1 (en) | Firmware update system, and information apparatus, as well as program | |
| CN101923473B (en) | Embedded electronic device and method for updating firmware thereof | |
| CN102334100A (en) | Program update device, program update method, and information processing device | |
| CN109086078B (en) | Android system upgrading method and device, server and mobile terminal | |
| US20100268867A1 (en) | Method and apparatus for updating firmware as a background task | |
| CN111142911B (en) | Embedded system with abnormal recovery function and upgrading method thereof | |
| CN102521289B (en) | File synchronization method, device and system | |
| CN100487648C (en) | File update system and boot management system of mobile communication terminal,and its method | |
| WO2022095758A1 (en) | Terminal upgrade method and terminal | |
| CN107436783B (en) | Differential upgrading method for mobile terminal, storage medium and mobile terminal | |
| WO2023169035A1 (en) | Operating system upgrade method, electronic device, and storage medium | |
| CN106775874B (en) | System upgrading method of terminal equipment | |
| CN110908722B (en) | Method and device applied to starting of operating system, electronic equipment and storage medium | |
| CN113032183A (en) | System management method, device, computer equipment and storage medium | |
| KR100832269B1 (en) | Program update method and system for wireless communication terminal | |
| CN103019773A (en) | System update power failure protection method and system, and mobile terminal | |
| CN110597532A (en) | Data acquisition module, firmware upgrading method thereof and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |