CN112463192A - High-pass platform private image upgrading method and terminal - Google Patents
High-pass platform private image upgrading method and terminal Download PDFInfo
- Publication number
- CN112463192A CN112463192A CN202011375051.4A CN202011375051A CN112463192A CN 112463192 A CN112463192 A CN 112463192A CN 202011375051 A CN202011375051 A CN 202011375051A CN 112463192 A CN112463192 A CN 112463192A
- Authority
- CN
- China
- Prior art keywords
- target
- file
- version information
- image
- target folder
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 42
- 230000006870 function Effects 0.000 claims description 11
- 238000004590 computer program Methods 0.000 claims description 8
- 238000005192 partition Methods 0.000 description 12
- 238000009434 installation Methods 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 238000011900 installation process Methods 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Images
Classifications
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a high-pass platform private image upgrading method and a terminal, wherein whether a preset target folder contains a target version information file or not is judged, if yes, the target version information file in the target folder is obtained, whether the target version information file is the same as a default version information file stored in a default path or not is judged, if yes, a subsystem image file corresponding to the target version information file in the target folder is loaded, if the target folder does not contain the target version information file or the target version information file is different from the default version information file, each file in the target folder is deleted firstly, and then the default version information file is copied into the target folder. According to the invention, by setting the mirror image file of the storage subsystem of the target folder, the NON-HLOS.
Description
Technical Field
The invention relates to the field of system upgrading, in particular to a high-pass platform private image upgrading method and a high-pass platform private image upgrading terminal.
Background
High-pass platform private image refers to the wcnss, modem, adsp, etc. subsystem image that the NON-hlos. In the existing high-pass private image compiling process, each subsystem image is packaged in an NON-hlos.bin, then the NON-hlos.bin writes a modem partition of an Android terminal, and in the starting process of the Android terminal, each subsystem image in the NON-hlos.bin is installed in a/vector/firmware _ mnt/image path, as shown in fig. 4, Kernel loads the images to a DDR (Double Data Rate SDRAM, Double Rate synchronous dynamic random access memory) through a PIL (Peripheral image loader) driver, so that a CPU can directly address the images, and then starts each subsystem.
In order to protect the security and integrity of the Device, most manufacturers have added dm-verity technology, which is a target Device type under the Device mapper architecture and is used to guarantee the integrity of the Device or Device partition, and refer to fig. 5, which is a typical architecture of dm-verity, the dm-verity can protect the system partition, the vendor partition, and the like, and make the state of the system partition, the vendor partition, and the like, not be modified.
However, a situation that one or more of the subsystems have problems and need to be updated is often encountered, for example, WiFi or bluetooth has problems, theoretically, only the wcnss subsystem image in NON-hlos.bin needs to be updated, but because NON-hlos.bin writes a partition with a partition name of "modem", no separate subsystem partition exists in the partition, and the subsystems are packaged and written into the "modem" partition together; moreover, the system uses a dm-verity technology, the/vendor/firmware _ mnt/image directory only has read-only permission, and vendor partition data is not modified, so that private images of high-pass subsystems such as wcnss, modem, and adsp cannot be upgraded independently, the subsystem images are packed together in a NON-hlos.bin for upgrading, and the size of an upgrade package is increased.
Disclosure of Invention
The technical problem to be solved by the invention is as follows: the high-pass platform private image upgrading method and the terminal can realize the independent upgrading of a high-pass platform subsystem.
In order to solve the technical problems, the invention adopts a technical scheme that:
a high-pass platform private image upgrading method comprises the following steps:
s1, judging whether the preset target folder contains the target version information file, if so, executing S2, otherwise, executing S3;
s2, acquiring a target version information file in the target folder, and judging whether the target version information file is the same as a default version information file stored in a default path, if so, executing S4, otherwise, executing S3;
s3, copying the default version information file into the target folder as a target version information file;
and S4, loading the subsystem mirror image file corresponding to the target version information file in the target folder.
In order to solve the technical problem, the invention adopts another technical scheme as follows:
a high-pass platform private image upgrading terminal comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, wherein the processor executes the computer program to realize the following steps:
s1, judging whether the preset target folder contains the target version information file, if so, executing S2, otherwise, executing S3;
s2, acquiring a target version information file in the target folder, and judging whether the target version information file is the same as a default version information file stored in a default path, if so, executing S4, otherwise, executing S3;
s3, copying the default version information file into the target folder as a target version information file;
and S4, loading the subsystem mirror image file corresponding to the target version information file in the target folder.
The invention has the beneficial effects that: setting a target folder, firstly judging whether the target folder contains a target version information file, if not, indicating that the loading of the image file is not carried out after the starting for the first time, if the target folder contains the target version information file but is different from a default version information file in a default path, indicating that the updating of the whole package occurs, at the moment, deleting each file in the target folder, then copying the default version information file into the target folder, ensuring the normal loading of the system image file, if the version information file is the same, indicating that the updating of the whole package is not carried out and the starting for the first time is not carried out, at the moment, obtaining the subsystem image file in the target folder for loading, and realizing the independent updating and upgrading of the subsystem.
Drawings
FIG. 1 is a flowchart illustrating steps of a method for upgrading a private image of a high-pass platform according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a high-pass platform private image upgrading terminal according to an embodiment of the present invention;
FIG. 3 is a flowchart of a method for upgrading a private image of a high-pass platform in a specific scenario according to an embodiment of the present invention;
FIG. 4 is a diagram illustrating loading of a directory by a mirror file at startup according to the prior art;
FIG. 5 is a diagram illustrating a dm-visibility exemplary architecture of the prior art;
description of reference numerals:
1. a high-pass platform private mirror image upgrading terminal; 2. a processor; 3. a memory.
Detailed Description
In order to explain technical contents, achieved objects, and effects of the present invention in detail, the following description is made with reference to the accompanying drawings in combination with the embodiments.
Referring to fig. 1 and fig. 3, a method for upgrading a private image of a high-pass platform includes the steps of:
s1, judging whether the preset target folder contains the target version information file, if so, executing S2, otherwise, executing S3;
s2, acquiring a target version information file in the target folder, and judging whether the target version information file is the same as a default version information file stored in a default path, if so, executing S4, otherwise, executing S3;
s3, copying the default version information file into the target folder as a target version information file;
and S4, loading the subsystem mirror image file corresponding to the target version information file in the target folder.
From the above description, the beneficial effects of the present invention are: setting a target folder, firstly judging whether the target folder contains a target version information file, if not, indicating that the loading of the image file is not carried out after the starting for the first time, if the target folder contains the target version information file but is different from a default version information file in a default path, indicating that the updating of the whole package occurs, at the moment, deleting each file in the target folder, then copying the default version information file into the target folder, ensuring the normal loading of the system image file, if the version information file is the same, indicating that the updating of the whole package is not carried out and the starting for the first time is not carried out, at the moment, obtaining the subsystem image file in the target folder for loading, and realizing the independent updating and upgrading of the subsystem.
Further, the preset process of generating the target folder in S1 is as follows:
creating a target folder and acquiring a target path of the target folder;
and setting a firmware _ class.path parameter in cmdlene as the target path so as to read the target folder in the boot process.
As can be seen from the above description, the firmware _ class _ path parameter in the Kernel command line cmdlet is set as the target path, and the Kernel can automatically read the relevant parameter in the cmdlet when the computer is started, so that the operation of reading the target folder can be performed in the starting process.
Further, the S1 is preceded by:
acquiring an APK file, and installing the subsystem mirror image file to the target folder through the APK file;
or acquiring an OTA data packet in an OTA mode, and storing the OTA data packet to the target folder, wherein the OTA data packet comprises a subsystem mirror image file.
As can be seen from the above description, the method for acquiring the image file required for upgrading is enriched by acquiring the image file of the subsystem through APK package installation or OTA (Over the Air, Over the Air technology), and the image file of the subsystem is installed in the target folder, so that the image file of the subsystem can be read in the installation process.
Further, the S4 specifically includes:
judging whether the target folder contains a subsystem image file, if so, loading the subsystem image file through an image request function;
otherwise, judging whether a prepared image file is stored in the default path, if so, loading the prepared image file through an image request function; otherwise, prompting that the loading of the image file fails, wherein the prepared image file is a subsystem image file installed through the default image file.
According to the description, if the target folder does not contain the subsystem image file, the image file is not updated, the default image file is loaded, the situation that the startup fails due to the fact that the image file is not loaded is avoided, and normal operation of the system is guaranteed.
Further, the default image file is NON-HLOS.
As can be seen from the above description, the default image file is a combination of subsystems such as wcnss, modem, and adsp, and the image files of all the subsystems are updated when the default image file is loaded, so that the normal operation of the system is ensured.
Referring to fig. 2, a high-pass platform private image upgrade terminal includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the following steps when executing the computer program:
s1, judging whether the preset target folder contains the target version information file, if so, executing S2, otherwise, executing S3;
s2, acquiring a target version information file in the target folder, and judging whether the target version information file is the same as a default version information file stored in a default path, if so, executing S4, otherwise, executing S3;
s3, copying the default version information file into the target folder as a target version information file;
and S4, loading the subsystem mirror image file corresponding to the target version information file in the target folder.
The invention has the beneficial effects that: setting a target folder, firstly judging whether the target folder contains a target version information file, if not, indicating that the loading of the image file is not carried out after the starting for the first time, if the target folder contains the target version information file but is different from a default version information file in a default path, indicating that the updating of the whole package occurs, at the moment, deleting each file in the target folder, then copying the default version information file into the target folder, ensuring the normal loading of the system image file, if the version information file is the same, indicating that the updating of the whole package is not carried out and the starting for the first time is not carried out, at the moment, obtaining the subsystem image file in the target folder for loading, and realizing the independent updating and upgrading of the subsystem.
Further, the preset process of generating the target folder in S1 is as follows:
creating a target folder and acquiring a target path of the target folder;
and setting a firmware _ class.path parameter in cmdlene as the target path so as to read the target folder in the boot process.
As can be seen from the above description, the firmware _ class _ path parameter in the Kernel command line cmdlet is set as the target path, and the Kernel can automatically read the relevant parameter in the cmdlet when the computer is started, so that the operation of reading the target folder can be performed in the starting process.
Further, the S1 is preceded by:
acquiring an APK file, and installing the subsystem mirror image file to the target folder through the APK file;
or acquiring an OTA data packet in an OTA mode, and storing the OTA data packet to the target folder, wherein the OTA data packet comprises a subsystem mirror image file.
As can be seen from the above description, the method for acquiring the image file required for upgrading is enriched by acquiring the image file of the subsystem through APK package installation or OTA (Over the Air, Over the Air technology), and the image file of the subsystem is installed in the target folder, so that the image file of the subsystem can be read in the installation process.
Further, the S4 specifically includes:
judging whether the target folder contains a subsystem image file, if so, loading the subsystem image file through an image request function;
otherwise, judging whether a prepared image file is stored in the default path, if so, loading the prepared image file through an image request function; otherwise, prompting that the loading of the image file fails, wherein the prepared image file is a subsystem image file installed through the default image file.
According to the description, if the target folder does not contain the subsystem image file, the image file is not updated, the default image file is loaded, the situation that the startup fails due to the fact that the image file is not loaded is avoided, and normal operation of the system is guaranteed.
Further, the default image file is NON-HLOS.
As can be seen from the above description, the default image file is a combination of subsystems such as wcnss, modem, and adsp, and the image files of all the subsystems are updated when the default image file is loaded, so that the normal operation of the system is ensured.
Referring to fig. 1, a first embodiment of the present invention is:
a high-pass platform private image upgrading method comprises the following steps:
s1, obtaining an APK file, and installing the subsystem image file to the target folder through the APK file;
or, acquiring an OTA data packet in an OTA mode, and storing the OTA data packet to the target folder, wherein the OTA data packet comprises a subsystem mirror image file;
in an optional implementation mode, the default image file NON-HLOS.bin is saved to the default path in an OTA mode, or the default image file NON-HLOS.bin is programmed in the default path by utilizing a programming tool;
s2, judging whether the preset target folder contains the target version information file, if so, executing S3, otherwise, executing S4;
the preset process of generating the target folder comprises the following steps:
creating a target folder and acquiring a target path of the target folder;
setting a firmware _ class.path parameter in cmdlene as the target path so as to read the target folder in the starting process;
s3, acquiring a target version information file in the target folder, and judging whether the target version information file is the same as a default version information file stored in a default path, if so, executing S5, otherwise, executing S4;
s4, judging whether the target folder stores files or not, if so, deleting the files in the target folder, copying the default version information files into the target folder to serve as target version information files, and if not, directly copying the default version information files into the target folder to serve as target version information files;
s5, loading a subsystem mirror image file corresponding to the target version information file in the target folder;
the method specifically comprises the following steps: judging whether the target folder contains a subsystem image file, if so, loading the subsystem image file through an image request function; otherwise, judging whether a prepared image file is stored in the default path, if so, loading the prepared image file through an image request function; otherwise, prompting that the loading of the mirror image file fails; the preparation image file is the image file of each subsystem installed under the default path after loading the NON-HLOS.
Regarding S2 and S3:
(1) in the first startup process after the default image file NON-HLOS.bin is updated in a first programming or OTA mode, the image file NON-HLOS.bin is installed, each subsystem image file is installed in a default path, and after the installation is completed, each subsystem image file and one version information file are included in the default path; because the target folder is empty due to the first programming, the version information file in the default path is copied into the target folder; when the system starting process is carried out to the step of loading the subsystem mirror image, the loading subsystem adopts the subsystem mirror image in the default path because the target folder does not have the corresponding subsystem mirror image;
(2) when the NON-HLOS-bin is programmed again or the whole mirror image file of the NON-HLOS-bin is updated in an OTA mode in the starting process, the NON-HLOS-bin is installed, all the subsystem mirror images and the version information files in the NON-HLOS-bin are installed in a default path, the version information files in the default path and the target folder are inconsistent at the moment, all the files in the target folder are deleted, the version information files in the default path are copied into the target folder, and when a system is started to load the subsystem mirror images, the subsystem mirror images under the default path are loaded because the target folder does not have the corresponding subsystem mirror images;
(3) when a starting process is carried out after a certain subsystem mirror image or a plurality of subsystem mirror images are upgraded to a target file in an APK mode or an OTA mode, the default path is consistent with the judgment version information file in the target path, and the file in the target file cannot be deleted; when the subsystem mirror image is loaded by the system, the subsystem mirror image in the target file is preferentially loaded because the target file has the corresponding subsystem mirror image, so that the subsystem is independently updated.
Referring to fig. 3, the second embodiment of the present invention is:
the high-pass platform private image upgrading method is applied to an actual scene:
take the image file of the wcnss subsystem installed as an example (called as the wcnss image file in this embodiment):
s1, receiving the wcnss image file packaged by the OTA and storing the wcnss image file in a target folder, or receiving a special APK and installing the wcnss image file under the target folder through the special APK;
s2, judging whether the target folder contains the target version information file, if so, executing S3, otherwise, executing S4;
s3, acquiring a target version information file in the target folder, and judging whether the target version information file is the same as a default version information file stored in a default path, if so, executing S5, otherwise, executing S4;
s4, deleting all files in the target folder, and copying the default version information file into the target folder as a target version information file;
deleting all files in the target folder, and preventing the mirror image files in the target folder from being preferentially loaded from influencing the update of the NON-HLOS.
S5, loading the wcnss mirror image file in the target folder;
in this embodiment, S5 specifically includes:
(1) searching whether a mirror image meeting the requirement exists in a corresponding segment in the kernel, traversing the mirror image of the builtin _ fw segment, comparing whether the names of the mirror images are the same or not, and if so, indicating that the mirror images are matched;
(2) searching whether a mirror image loaded last time exists in cache, namely searching mirror image information on a linked list of a global variable fw _ cache, wherein the information of the mirror image loaded before can be automatically stored on the head of the linked list of the fw _ cache;
(3) reading corresponding mirror images in a file interface in a kernel directly, and searching each path in an fw _ path array, wherein the 1 st variable (fw _ path _ para) of the array can be used for a user to transmit a customized path, and the method is that a parameter (firmware _ class.path value) in a cmdline mode is given to the variable (fw _ path _ para); the value of the firmware _ class _ path parameter is set as a target path, the system code transmits the target path corresponding to the firmware _ class _ path to the fw _ path _ para parameter, so that the value of the fw _ path _ para is a target directory, the loading sequence of the fw _ path _ para is the first variable in the array loaded by the Kernel in the step, and the loaded path is the target path by the way of switching the path earlier than the way of the uevent
(4) And loading a corresponding mirror image by using the Uevent interface, reporting the Uevent event to the user space, and then waiting for the mirror image loading to be completed. At present, a high-pass platform loads a mirror image by calling a mirror image request function of Kernel, then finding mirror images of subsystems under a path prestored by a system and loading the mirror images to DDR.
Referring to fig. 2, a third embodiment of the present invention is:
a high-pass platform private image upgrading terminal 1 comprises a processor 2, a memory 3 and a computer program which is stored on the memory 3 and can run on the processor 2, and the processor 2 executes the computer program to realize the steps of the first embodiment or the second embodiment.
In summary, the invention provides a high-pass platform private image upgrading method and a terminal, by changing corresponding parameters in cmdline, the image file in a target folder is preferentially read in the process of starting and loading, and a subsystem image file is placed in the target folder to realize independent updating of a subsystem; in order to prevent the NON-HLOS-bin file from being updated but not loaded in the process of loading the subsystem image file, a version information file is set, if the loading of the NON-HLOS-bin file is completed, the version information file in the default path where the NON-HLOS-bin file is located and in the target folder is synchronously updated, if the NON-HLOS-bin file is downloaded but not loaded, only the version information file in the default path is updated, at the moment, the situation different from the version information file in the target folder occurs in the default path, if the situation occurs, all files in the target folder are deleted, the situation that the image file in the target folder is preferentially loaded according to the setting of relevant parameters of cmline when the system is started is avoided, namely, the system detects that the target folder is empty, the image file in the default path, namely the NON-HLOS-bin file is automatically acquired to be loaded, the method and the device have the advantages that the effect of updating the subsystem independently is achieved, meanwhile, the whole update of the NON-HLOS binding file is not influenced, the acquisition of the subsystem image file can be achieved through an OTA or APK installation mode, the mode of acquiring the image file is expanded, and the use experience of a user is improved.
The above description is only an embodiment of the present invention, and not intended to limit the scope of the present invention, and all equivalent changes made by using the contents of the present specification and the drawings, or applied directly or indirectly to the related technical fields, are included in the scope of the present invention.
Claims (10)
1. A high-pass platform private image upgrading method is characterized by comprising the following steps:
s1, judging whether the preset target folder contains the target version information file, if so, executing S2, otherwise, executing S3;
s2, acquiring a target version information file in the target folder, and judging whether the target version information file is the same as a default version information file stored in a default path, if so, executing S4, otherwise, executing S3;
s3, copying the default version information file into the target folder as a target version information file;
and S4, loading the subsystem mirror image file corresponding to the target version information file in the target folder.
2. The high-pass platform private image upgrading method according to claim 1, wherein the preset process of generating the target folder in S1 is as follows:
creating a target folder and acquiring a target path of the target folder;
and setting a firmware _ class.path parameter in cmdlene as the target path so as to read the target folder in the boot process.
3. The high-pass platform private image upgrading method according to claim 1, wherein the S1 is preceded by:
acquiring an APK file, and installing the subsystem mirror image file to the target folder through the APK file;
or acquiring an OTA data packet in an OTA mode, and storing the OTA data packet to the target folder, wherein the OTA data packet comprises a subsystem mirror image file.
4. The high-pass platform private image upgrading method according to claim 1, wherein the S4 specifically is:
judging whether the target folder contains a subsystem image file, if so, loading the subsystem image file through an image request function;
otherwise, judging whether a prepared image file is stored in the default path, if so, loading the prepared image file through an image request function; otherwise, prompting that the loading of the image file fails, wherein the prepared image file is a subsystem image file installed through the default image file.
5. The high-pass platform private image upgrading method of claim 4, wherein the default image file is NON-HLOS.
6. A high-pass platform private image upgrading terminal, comprising a memory, a processor and a computer program stored on the memory and operable on the processor, wherein the processor executes the computer program to implement the following steps:
s1, judging whether the preset target folder contains the target version information file, if so, executing S2, otherwise, executing S3;
s2, acquiring a target version information file in the target folder, and judging whether the target version information file is the same as a default version information file stored in a default path, if so, executing S4, otherwise, executing S3;
s3, copying the default version information file into the target folder as a target version information file;
and S4, loading the subsystem mirror image file corresponding to the target version information file in the target folder.
7. The high-pass platform private image upgrading terminal according to claim 6, wherein the preset process of generating the target folder in the S1 is as follows:
creating a target folder and acquiring a target path of the target folder;
and setting a firmware _ class.path parameter in cmdlene as the target path so as to read the target folder in the boot process.
8. The high-pass platform private image upgrading terminal according to claim 6, wherein the S1 is preceded by:
acquiring an APK file, and installing the subsystem mirror image file to the target folder through the APK file;
or acquiring an OTA data packet in an OTA mode, and storing the OTA data packet to the target folder, wherein the OTA data packet comprises a subsystem mirror image file.
9. The high-pass platform private image upgrading terminal according to claim 6, wherein the S4 is specifically:
judging whether the target folder contains a subsystem image file, if so, loading the subsystem image file through an image request function;
otherwise, judging whether a prepared image file is stored in the default path, if so, loading the prepared image file through an image request function; otherwise, prompting that the loading of the image file fails, wherein the prepared image file is a subsystem image file installed through the default image file.
10. The high-pass platform private image upgrade terminal according to claim 9, wherein the default image file is NON-hlos.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011375051.4A CN112463192A (en) | 2020-11-30 | 2020-11-30 | High-pass platform private image upgrading method and terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011375051.4A CN112463192A (en) | 2020-11-30 | 2020-11-30 | High-pass platform private image upgrading method and terminal |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112463192A true CN112463192A (en) | 2021-03-09 |
Family
ID=74804943
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011375051.4A Pending CN112463192A (en) | 2020-11-30 | 2020-11-30 | High-pass platform private image upgrading method and terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112463192A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080189340A1 (en) * | 2007-02-01 | 2008-08-07 | David Randall Blea | Apparatus, system, and method for synchronizing a remote database |
| CN103281689A (en) * | 2013-04-28 | 2013-09-04 | 华为技术有限公司 | Method for network switching and version upgrading and terminal equipment |
| CN105446769A (en) * | 2015-11-03 | 2016-03-30 | 广东欧珀移动通信有限公司 | Mirror image file update processing method and apparatus and terminal device |
| CN110750286A (en) * | 2019-10-17 | 2020-02-04 | 福州汇思博信息技术有限公司 | Management method, device, system, equipment and medium for upgrading Mbn through OTA |
| CN111078312A (en) * | 2019-12-03 | 2020-04-28 | 维沃移动通信有限公司 | MBN loading method and electronic equipment |
-
2020
- 2020-11-30 CN CN202011375051.4A patent/CN112463192A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080189340A1 (en) * | 2007-02-01 | 2008-08-07 | David Randall Blea | Apparatus, system, and method for synchronizing a remote database |
| CN103281689A (en) * | 2013-04-28 | 2013-09-04 | 华为技术有限公司 | Method for network switching and version upgrading and terminal equipment |
| CN105446769A (en) * | 2015-11-03 | 2016-03-30 | 广东欧珀移动通信有限公司 | Mirror image file update processing method and apparatus and terminal device |
| CN110750286A (en) * | 2019-10-17 | 2020-02-04 | 福州汇思博信息技术有限公司 | Management method, device, system, equipment and medium for upgrading Mbn through OTA |
| CN111078312A (en) * | 2019-12-03 | 2020-04-28 | 维沃移动通信有限公司 | MBN loading method and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105867947B (en) | Data processing method and device after preset application program updating | |
| US9454356B2 (en) | Method of and terminal for updating library file in system application | |
| US7689983B2 (en) | Information processing method and apparatus and recording medium | |
| US7644406B2 (en) | Update system capable of updating software across multiple FLASH chips | |
| CN104572229B (en) | The firmware upgrade method and device for upgrading firmware of embedded system | |
| KR100584338B1 (en) | Method and system for updating software | |
| US5537596A (en) | Method and apparatus for overriding resource maps in a computer system | |
| US20230393840A1 (en) | File update method and apparatus, device and storage medium | |
| KR101555210B1 (en) | Apparatus and method for downloadin contents using movinand in portable terminal | |
| WO2021143845A1 (en) | Extended system partitioning method and apparatus, storage medium, and computer device | |
| WO2022262754A1 (en) | Operating system data updating method and device, storage medium, and program product | |
| CN104007992A (en) | Methods and devices for program updating and starting | |
| TWI383296B (en) | Storage device and method for data writing for data using internal storage operations | |
| US20100031246A1 (en) | Updating Content Without Using a Mini Operating System | |
| CN113867768A (en) | Operating system processing method and device, electronic equipment and storage medium | |
| CN106293790A (en) | Application program updating method and apparatus based on Firefox operating system | |
| CN112463192A (en) | High-pass platform private image upgrading method and terminal | |
| US9448782B1 (en) | Reducing a size of an application package | |
| US7490232B2 (en) | Disk device using disk to rewrite firmware and firmware determination method | |
| CN114567628B (en) | OTA upgrading method and device | |
| US20220073018A1 (en) | Vehicle device | |
| CN111679848A (en) | Software updating method and terminal | |
| WO2001050261A2 (en) | Updating non volatile memory in a data processing system | |
| KR20070081868A (en) | Method for updating software efficiently in mobile communication system | |
| WO2019237222A1 (en) | System upgrading method, smart device, and server |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210309 |