Wrapping computer software applications
US-2015370553-A1 · Dec 24, 2015 · US
US9367303B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9367303-B2 |
| Application number | US-201414440514-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 25, 2014 |
| Priority date | Jul 8, 2013 |
| Publication date | Jun 14, 2016 |
| Grant date | Jun 14, 2016 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method of generating a Firmware Over-The-Air (FOTA) upgrade package is disclosed, comprising: determining whether a file having a same filename or being similar as a file in a software package of a new version exists in a software package of an old version; when there exists a file having a same filename or a similar file, generating a difference file between the file in the software package of the old version and the file in the software package of the new version and adding the difference file into the FOTA upgrade package, and when there doesn't exist a file having a same filename or a similar file, adding the file in the software package of the new version into the FOTA upgrade package. An FOTA upgrading method, a server, and a mobile terminal are also disclosed.
Opening claim text (preview).
What is claimed is: 1. A method of generating a Firmware Over-The-Air (FOTA) upgrade package, comprising the following steps of: determining, by a server, whether a first file in a software package of an old version has a same filename as that of a second file in a software package of a new version by scanning, by the server, filenames and file attributes of files in the software package of the old version and the software package of the new version to obtain type file lists of the software package of the old version and type file lists of the software package of the new version, wherein each of the type file lists comprises filenames of files of a same type; when the first file has the same filename as that of the second file, then generating, by the server, a first difference file between the first file in the software package of the old version and the second file in the software package of the new version and adding, by the server, the first difference file into the FOTA upgrade package; and when the first file doesn't have the same filename as that of the second file, then continuing to determine whether the first file in the software package of the old version is similar to the second file in the software package of the new version, a determination of whether the existing file in the old version is similar to the file in the new version being made by determining whether the existing file and the file in the new version are of the same type and whether a difference between a volume of the difference file and a volume of either the existing file or the file in the new version, whichever is smaller, is smaller than a predetermined value; and when the first file is similar to the second file, then generating, by the server, a second difference file between the first file in the software package of the old version and the second file in the software package of the new version and adding, by the server, the second difference file into the FOTA upgrade package; and when the first file is not similar to the second file, then adding the second file in the software package of the new version into the FOTA upgrade package, wherein the FOTA upgrade package is used to upgrade software of a mobile terminal from the old version of the software package into the new version of the software package. 2. The method of claim 1 , wherein the step of determining, by the server, whether the first file in the software package of the old version has the same filename as that of the second file in the software package of the new version specifically comprises the following steps of: determining, by the server, whether traversing of a current type file list in the software package of the new version has been finished; and when the answer is “yes”, continuing to determine whether traversing of a next type file list in the software package of the new version has been finished, and otherwise, when the answer is “no”, acquiring a filename having not been traversed from the current type file list in the software package of the new version; determining, by the server, whether traversing of a current type file list in the software package of the old version has been finished; and when the answer is “yes”, continuing to determine whether traversing of the current type file list in the software package of the new version has been finished, and otherwise, when the answer is “no”, acquiring a first filename having not been traversed from the current type file list in the software package of the old version and determining whether the first filename is the same as the second filename having not been traversed that is acquired from the current type file list in the software package of the new version, and when the filenames are the same, then adding the corresponding filename into an old-and-new-coexisting list; and continuing to traverse the current type file list in the software package of the new version by the server after the corresponding filename has been added into the old-and-new-coexisting list. 3. The method of claim 2 , wherein the step of determining whether the first file in the software package of the old version is similar to the second file in the software package of the new version specifically comprises the following steps of: when the first filename having not been traversed that is acquired from the current type file list in the software package of the old version is not the same as the second filename having not been traversed that is acquired from the current type file list in the software package of the new version, then determining whether the first file corresponding to the first filename having not been traversed that is acquired from the current type file list in the software package of the old version is similar to the second file corresponding to the second filename having not been traversed that is acquired from the current type file list in the software package of the new version; when the first file is similar to the second file, then adding, by the server, the first filename having not been traversed that is acquired from the current type file list in the software package of the old version and the second filename having not been traversed that is acquired from the current type file list in the software package of the new version into a similar file list; continuing to traverse the current type file list in the software package of the new version by the server after the filenames have been added into the similar file list; and when the first file is not similar to the second file, then continuing to traverse the current type file list in the software package of the old version by the server. 4. The method of claim 3 , wherein the step of determining whether the first file corresponding to the first filename having not been traversed that is acquired from the current type file list in the software package of the old version is similar to the second file corresponding to the second filename having not been traversed that is acquired from the current type file list in the software package of the new version specifically comprises the following steps of: generating, by the server, the second difference file between the first file corresponding to the first filename having not been traversed that is acquired from the current type file list in the software package of the old version and the second file corresponding to the second filename having not been traversed that is acquired from the current type file list in the software package of the new version; further acquiring, by the server, a file of a smaller volume from the first file corresponding to the first filename having not been traversed that is acquired from the current type file list in the software package of the old version and the second file corresponding to the second filename having not been traversed that is acquired from the current type file list in the software package of the new version; and determining, by the server, whether a difference in volume between the second difference file and the file of the smaller volume is smaller than 50% of the file volume of the file of the smaller volume, and when the answer is “yes”, the first and second files are similar files, and otherwise, they are not similar files. 5. The method of claim 4 , wherein the step of, when the first file has the same filename as that of the second file, then generating, by the server, the first difference file between the first file in the software package of the old version and the second file in the software package of the new version specifically comprises the following steps of: scanning, by the server, filenames of files in the software package of the new version to obtain a file list of the software package of the new version; determining, by the server, whether traversing of
Updates (security arrangements therefor G06F21/57) · CPC title
Physics · mapped topic
Physics · mapped topic
Incremental updates; Differential updates · CPC title
using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.