CN110032377B - Communication module software upgrading method and system and communication module - Google Patents
Communication module software upgrading method and system and communication module Download PDFInfo
- Publication number
- CN110032377B CN110032377B CN201910207145.1A CN201910207145A CN110032377B CN 110032377 B CN110032377 B CN 110032377B CN 201910207145 A CN201910207145 A CN 201910207145A CN 110032377 B CN110032377 B CN 110032377B
- Authority
- CN
- China
- Prior art keywords
- firmware
- file
- target
- source
- firmware file
- 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
- 238000004891 communication Methods 0.000 title claims abstract description 35
- 238000000034 method Methods 0.000 title claims abstract description 32
- 238000005192 partition Methods 0.000 claims abstract description 48
- 238000012795 verification Methods 0.000 claims description 7
- 238000004519 manufacturing process Methods 0.000 claims description 3
- 238000002372 labelling Methods 0.000 claims 1
- 238000010586 diagram Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000004590 computer program Methods 0.000 description 2
- 238000011084 recovery Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
- G06F8/63—Image based installation; Cloning; Build to order
-
- 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)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a communication module software upgrading method, a system and a communication module, wherein each file to be upgraded is put into the same firmware, and a differential packet of the whole firmware is generated according to source file firmware and target file firmware before upgrading, namely, the differential packet is generated aiming at a bottom binary code of the whole firmware; and when the module is upgraded, generating a target firmware file of the whole firmware according to the differential packet and the current firmware file of the equipment, storing the target firmware file into a designated partition, and writing a new firmware file in the designated partition into the original system firmware during upgrading. Because the whole firmware is programmed, even if the power-down condition occurs in the programming process, the system cannot be restarted, only the firmware files in the appointed partition are required to be programmed again to the original firmware position, the complex file system is not required to be read, identified and re-programmed, the condition that the file system cannot be identified after the power-down is avoided, and the crash phenomenon of the module system is avoided.
Description
Technical Field
The present invention relates to a software upgrade technology, and in particular, to a communication module software upgrade technology.
Background
The existing file system adopts an unordered block image file system (Unsorted Block IMAGE FILE SYSTEM, UBIFS) file system, which is called UBI file system for short. The differential upgrading scheme is a differential packet generated for the difference of each file in the file system, and realizes upgrading by updating each file in the file system.
The inventor of the invention discovers that the existing FOTA upgrading mode has the condition of easy crash after power failure. In the process of upgrading files one by one, if the system is restarted under the condition of abnormal power failure, because the current upgraded file is changed, the condition that the file system cannot be mounted easily occurs when the system is restarted, and the condition of the system crash is caused, so that the system cannot be recovered and started. A great deal of work is added which requires maintenance personnel to go to the site for support.
Disclosure of Invention
The invention aims to provide a communication module software upgrading method, a system and a communication module, so that the communication module cannot fail even if power is lost in the upgrading process, and the stability of module software upgrading is improved.
In order to solve the above technical problems, an embodiment of the present invention provides a method for upgrading communication module software, including:
the service side puts each source file of the file to be upgraded into the same firmware, puts each target file of the file to be upgraded into the same firmware, and generates a whole firmware file difference packet according to the original firmware file and the target firmware file;
after receiving the firmware file differential packet, the terminal side generates a new firmware file from the firmware file differential packet and the firmware file of the current device, writes the generated new firmware file into a designated partition, and integrally upgrades the current firmware file according to the firmware file of the designated partition.
The embodiment of the invention also provides a communication module software upgrading system, which comprises:
the differential packet generation module is used for placing each source file of the file to be upgraded into the same firmware, placing each target file of the file to be upgraded into the same firmware, and generating the whole firmware file differential packet according to the original firmware file and the target firmware file.
The embodiment of the invention also provides a communication module, which comprises:
The new file generation module is used for generating a new firmware file from the firmware file differential packet and the firmware file of the current equipment after the module receives the firmware file differential packet, and programming the generated new firmware file into the designated partition;
And the upgrading module is used for integrally upgrading the current firmware file according to the firmware file of the appointed partition.
Compared with the prior art, the embodiment of the invention generates the differential packet of the whole firmware according to the source file firmware before upgrading and the target file firmware after upgrading by putting various files to be upgraded into the same firmware, namely, generates the differential packet aiming at the bottom layer code (binary code) of the whole firmware; when the module is upgraded, a target firmware file of the whole firmware is generated according to the differential packet and the current firmware file of the equipment, the target firmware file is stored in a designated partition, and when the module is upgraded, a new firmware file in the designated partition is programmed into the original firmware, so that the whole firmware file is integrally upgraded. Because the whole firmware is programmed, even if the power-down condition occurs in the programming (upgrading) process, the system cannot be restarted, only the firmware files in the appointed partition are required to be programmed again to the original firmware position, the complex file system is not required to be read, identified and re-programmed, the condition that the file system cannot be identified after the power-down is avoided, and the crash phenomenon of the module system is avoided.
As a further improvement, in the step of generating the whole firmware file differential packet according to the original firmware file and the target firmware file, the generated file differential packet at least includes: source firmware version information, target firmware version information;
the source firmware version information at least comprises: source firmware file size, source firmware file version number, source firmware file check value;
The target firmware version information includes at least: target firmware file size, target firmware file version number, target firmware file check value.
As a further improvement, before the differentiating the firmware file and the firmware file of the current device generate the new firmware file, the method further includes: checking whether the version information of the firmware file of the current device is consistent with the version information of the source firmware stored in the file differential packet, and if so, executing the step of generating a new firmware file by the firmware file differential packet and the firmware file of the current device;
As a further improvement, before the generated new firmware file is programmed to the designated partition, the method further comprises: and checking whether the check value of the generated new firmware file is consistent with the check value of the target firmware file in the file difference packet, and if so, executing the step of programming the generated new firmware file to the designated partition. And through double verification, the accuracy of software upgrading is ensured.
As a further improvement, before the whole firmware file differential package is generated according to the original firmware file and the target firmware file, the method further comprises the following steps:
generating a first mirror image file of the source firmware for the source firmware file;
Generating a source firmware second image file from the source firmware first image file and the source firmware version information;
generating a first mirror image file of the target firmware for the target firmware file;
generating a target firmware second image file by the target firmware first image file and the target firmware version information;
In the step of generating the whole firmware file differential packet according to the original firmware file and the target firmware file, the differential packet is generated according to the source firmware second image file and the target firmware second image file.
Therefore, the source firmware file size, the source firmware file version number, the source firmware file check value, the target firmware file size and the target firmware file version number can be respectively contained in the source firmware image file and the target firmware image file, so that when a differential packet is generated, the source firmware version information and the target firmware version information can be contained.
Drawings
FIG. 1 is a flow chart of a method for upgrading communication module software according to a first embodiment of the present invention;
FIG. 2 is a schematic diagram of the UBI file system according to a first embodiment of the present invention;
FIG. 3 is a schematic diagram of a differential packet file structure according to a first embodiment of the present invention;
Fig. 4 is a block diagram of a communication module software upgrade system according to a second embodiment of the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present application more apparent, embodiments of the present application will be described in detail below with reference to the accompanying drawings. However, those of ordinary skill in the art will understand that in various embodiments of the present application, numerous technical details have been set forth in order to provide a better understanding of the present application. The technical solutions claimed in the claims of the present application can be realized without these technical details and various changes and modifications based on the following embodiments.
The first embodiment of the invention relates to a communication module software upgrading method, in the embodiment, a service side puts each source file of a file to be upgraded into the same firmware, puts each target file of the file to be upgraded into the same firmware, and generates a whole firmware file difference packet according to an original firmware file and a target firmware file; after receiving the firmware file differential packet, the terminal side (i.e. the communication module) generates a new firmware file from the firmware file differential packet and the firmware file of the current device, writes the generated new firmware file into a designated partition, and integrally upgrades the current firmware file according to the firmware file of the designated partition.
The method comprises the steps that various files to be upgraded are put into the same firmware, and a differential packet of the whole firmware is generated according to source file firmware before upgrading and target file firmware after upgrading, namely, a differential packet is generated aiming at a bottom layer code (binary code) of the whole firmware; when the module is upgraded, a target firmware file of the whole firmware is generated according to the differential packet and the current firmware file of the equipment, the target firmware file is stored in a designated partition, and when the module is upgraded, a new firmware file in the designated partition is programmed into the original firmware, so that the whole firmware file is integrally upgraded. Because the whole firmware is programmed, even if the power-down condition occurs in the programming (upgrading) process, the system cannot be restarted, only the firmware files in the appointed partition are required to be programmed again to the original firmware position, the complex file system is not required to be read, identified and re-programmed, the condition that the file system cannot be identified after the power-down is avoided, and the crash phenomenon of the module system is avoided.
A specific communication module software upgrade flow is shown in fig. 1.
In step 101, the service side places various source files of the file to be upgraded into the same firmware partition (firmware partition a), and places various target files of the file to be upgraded into the same firmware partition (firmware partition B).
The files to be upgraded can specifically comprise kernel image files, linux application files, modem files and the like.
In step 102, image files are generated for the source firmware file (i.e., the bottom file of the firmware storing the source file, i.e., the binary file) and the target firmware file (i.e., the bottom file of the firmware storing the target file, i.e., the binary file), respectively.
Specifically, in step 102-1, a source firmware first image file is generated for the source firmware file. The first image file may be a rootfs image file generated through squashfs file system. Specifically, a read-only squashfs file system can be adopted, a mksquashfs command is used for generating a rootfs image file, and an LZO compression algorithm is adopted during packaging.
102-2, Generating a source firmware second image file by using the source firmware first image file and the source firmware version information; the second image may be UBI (Unsorted Block Images) images. The source firmware version information includes: source firmware file size, source firmware file version number, source firmware file check value (e.g., MD5 value).
Specifically, the UBI file system is split into two volumes (volume 1 and volume 2), as shown in fig. 2. First, firmware version information (version number) is added at the end of a first image file (rootfs image file) of a source firmware to form a volume 1. The volume 1 and source firmware file size information are packaged into a UBI image file (second image file). Size information of the first image file of the source firmware is in volume 2 of the UBI image file.
102-3, Generating a first mirror image file of the target firmware for the target firmware file; in the same manner as in step 102-1.
102-4, Generating a target firmware second image file by using the target firmware first image file and the target firmware version information; in the same manner as in step 102-2.
The source firmware file size, the source firmware file version number, the source firmware file verification value, the target firmware file size and the target firmware file version number can be respectively contained in the source firmware image file and the target firmware image file through twice image file production, so that when differential packets are generated, the source firmware version information and the target firmware version information can be contained for verification at a terminal side.
In step 103, a whole firmware file differential packet is generated according to the source firmware second image file and the target firmware second image file. The generated file difference packet at least comprises: source firmware version information, target firmware version information; the source firmware version information at least comprises: source firmware file size, source firmware file version number, source firmware file check value; the target firmware version information includes at least: target firmware file size, target firmware file version number, target firmware file check value.
Specifically, a HDIFFPATCH difference algorithm may be used to obtain a difference file, where the source file for creating the difference packet is the volume 1 portion in the second image file of the source firmware, and the destination file is the volume 1 portion in the second image file of the destination component. The header of the generated differential packet file is attached with the following information: the mac number, source firmware version information, target firmware version information, and differential package file structure are shown in fig. 3.
In step 104, the terminal side (i.e., the wireless communication module) downloads the differential file packet. The downloading mode may include:
(1) The downloading mode of the network mainly comprises the downloading mode of https and OTA (Over-the-Air Technology) on the Air.
(2) The local is sent to the terminal side through USB.
In step 105, it is checked whether the firmware file version information of the current device is consistent with the source firmware version information stored in the file differential packet, if so, step 106 is entered, if not, the generation of the new firmware file fails, and error information is returned.
Specifically, 105-1, reading source firmware version information and target firmware version information in the differential packet file; 105-2, obtaining firmware version information of the current version of the device and an MD5 value of a firmware volume 0 mirror image; 105-3, is the source firmware version information, the target firmware version information, and the source firmware image MD5 value and the target firmware image MD5 value obtained above compared to agree? If so, step 106 is entered, and if not, generation of the new firmware file fails.
In step 106, the firmware file differential packet is compared with the firmware file of the current device to generate a new firmware file. Specifically, a target firmware image file may be generated using the HDIFFPATCH algorithm.
In step 107, it is checked whether the verification value of the generated new firmware file is consistent with the verification value of the target firmware file in the file difference packet. Specifically, whether the MD5 value of the target image is consistent with the MD5 value information of the target version in the differential file can be checked. If so, go to step 108; if the new firmware files are inconsistent, the generation of the new firmware files fails, and error information is returned.
In step 108, the generated new firmware file is burned into the module-specific partition. The designated partition is pre-designated, holding a firmware file for storing upgrades. By the double check of step 105 and step 107, the accuracy of the software upgrade can be effectively ensured.
In step 109, the current firmware file is updated integrally according to the firmware file of the specified partition. The firmware files in the appointed partition are burnt into the firmware stored in the current file to replace the current firmware file.
Specifically, before the entire upgrade of the current firmware file, an upgrade flag is written in a certain partition. And then, restarting the system to enter a recovery mode, and programming the target version in the recovery mode. And after the upgrading is finished, the upgrading mark is cleared.
In the upgrading process, if power failure occurs, the communication module is restarted, and if the upgrading mark is found in the starting process, the whole current firmware file is upgraded directly according to the firmware file of the designated partition. The complex file system is not required to be read, identified and re-written, the situation that the file system cannot be identified after power failure is avoided, and further the crash phenomenon of the module system is avoided.
Or in this embodiment, the system may be prompted to upgrade the current firmware file according to the firmware file of the designated partition again by setting other conditions without setting the upgrade flag.
The second embodiment of the present invention relates to a communication module software upgrade system, as shown in fig. 4, including a service side software upgrade system 401 and a communication module side upgrade system 402.
The software upgrade system 401 of the service side includes:
The differential packet generation module is used for placing each source file of the file to be upgraded into the same firmware, placing each target file of the file to be upgraded into the same firmware, and generating the whole firmware file differential packet according to the original firmware file and the target firmware file. The file differential packet generated by the differential packet generating module at least comprises the following components: source firmware version information, target firmware version information; the source firmware version information at least comprises: source firmware file size, source firmware file version number, source firmware file check value; the target firmware version information includes at least: target firmware file size, target firmware file version number, target firmware file check value. So that the terminal side (communication module side) can verify based on the source firmware version information and the target firmware version information.
And the first image file generation module is used for generating the source firmware first image file from the source firmware file.
And the second image file generating module is used for generating the source firmware first image file and the source firmware version information into a source firmware second image file.
The first image file generating module is further used for generating the target firmware file into a target firmware first image file.
The second image file generating module is further configured to generate the target firmware first image file and the target firmware version information into a target firmware second image file.
And the differential packet generation module generates the differential packet according to the source firmware second image file and the target firmware second image file.
The upgrade system 402 on the communication module side includes:
and the new file generation module is used for generating a new firmware file from the firmware file differential packet and the firmware file of the current equipment after the module receives the firmware file differential packet, and programming the generated new firmware file to the appointed partition.
And the upgrading module is used for integrally upgrading the current firmware file according to the firmware file of the appointed partition.
And the first verification module is used for verifying whether the firmware file version information of the current equipment is consistent with the source firmware version information stored in the received file differential packet, and if so, the new file generation module is instructed to generate a new firmware file by the firmware file differential packet and the firmware file of the current equipment.
And the second checking module is used for checking whether the check value of the generated new firmware file is consistent with the check value of the target firmware file in the file differential packet, and if so, indicating the production module to burn the generated new firmware file into the appointed partition.
The marking module is used for marking an upgrade mark before the upgrade module integrally upgrades the current firmware file, and erasing the upgrade mark after the upgrade module integrally upgrades the current firmware file;
And the starting module is used for indicating the upgrading module to integrally upgrade the current firmware file according to the firmware file of the appointed partition when the upgrading mark is found when the communication module is started.
The method comprises the steps that various files to be upgraded are put into the same firmware, and a differential packet of the whole firmware is generated according to source file firmware before upgrading and target file firmware after upgrading, namely, a differential packet is generated aiming at a bottom layer code (binary code) of the whole firmware; when the module is upgraded, a target firmware file of the whole firmware is generated according to the differential packet and the current firmware file of the equipment, the target firmware file is stored in a designated partition, and when the module is upgraded, a new firmware file in the designated partition is programmed into the original firmware, so that the whole firmware file is integrally upgraded. Because the whole firmware is programmed, even if the power-down condition occurs in the programming (upgrading) process, the system cannot be restarted, only the firmware files in the appointed partition are required to be programmed again to the original firmware position, the complex file system is not required to be read, identified and re-programmed, the condition that the file system cannot be identified after the power-down is avoided, and the crash phenomenon of the module system is avoided.
In specific implementation, the software upgrading system of the service side of the present embodiment includes at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform a software upgrade method as mentioned in the first embodiment.
The communication module side comprises at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform a software upgrade method as mentioned in the first embodiment.
A third embodiment of the present invention relates to a computer-readable storage medium storing a computer program. The computer program implements the above-described method embodiments when executed by a processor.
That is, it will be understood by those skilled in the art that all or part of the steps in implementing the methods of the embodiments described above may be implemented by a program stored in a storage medium, where the program includes several instructions for causing a device (which may be a single-chip microcomputer, a chip or the like) or a processor (processor) to perform all or part of the steps in the methods of the embodiments of the application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
It will be understood by those of ordinary skill in the art that the foregoing embodiments are specific examples of carrying out the invention and that various changes in form and details may be made therein without departing from the spirit and scope of the invention.
Claims (7)
1. A method for upgrading communication module software, comprising:
the service side puts each source file of the file to be upgraded into the same firmware, puts each target file of the file to be upgraded into the same firmware, and generates a whole firmware file difference packet according to the original firmware file and the target firmware file;
After receiving the whole firmware file differential packet, the terminal side generates a whole new firmware file from the whole firmware file differential packet and the firmware file of the current device, writes the generated whole new firmware file into a designated partition, and writes the whole new firmware file in the designated partition into the original firmware during upgrading so as to upgrade the whole current firmware file according to the firmware file of the designated partition;
Before the step of integrally upgrading the current firmware file according to the firmware file of the designated partition, the method further comprises the following steps: labeling an upgrade mark;
after the whole upgrading of the current firmware file is finished according to the firmware file of the appointed partition, the upgrading mark is erased;
When the communication module is started, if the upgrading mark is found, executing the step of integrally upgrading the current firmware file according to the firmware file of the designated partition;
the file difference packet at least comprises: source firmware version information, target firmware version information;
the source firmware version information at least comprises: source firmware file size, source firmware file version number, source firmware file check value;
The target firmware version information includes at least: target firmware file size, target firmware file version number, target firmware file check value.
2. The method for upgrading communication module software according to claim 1, wherein before differentiating the firmware file with the firmware file of the current device to generate the new firmware file, further comprising: checking whether the version information of the firmware file of the current device is consistent with the version information of the source firmware stored in the file differential packet, and if so, executing the step of generating a new firmware file by the firmware file differential packet and the firmware file of the current device;
before the generated new firmware file is programmed into the designated partition, the method further comprises the following steps: and checking whether the check value of the generated new firmware file is consistent with the check value of the target firmware file in the file difference packet, and if so, executing the step of programming the generated new firmware file to the designated partition.
3. The method for upgrading communication module software according to claim 1, wherein before generating the entire firmware file differential package according to the original firmware file and the target firmware file, the method further comprises:
generating a first mirror image file of the source firmware for the source firmware file;
Generating a source firmware second image file from the source firmware first image file and the source firmware version information;
generating a first mirror image file of the target firmware for the target firmware file;
generating a target firmware second image file by the target firmware first image file and the target firmware version information;
In the step of generating the whole firmware file differential packet according to the original firmware file and the target firmware file, the differential packet is generated according to the source firmware second image file and the target firmware second image file.
4. A method of upgrading software of a communication module according to claim 3, wherein the first image file is a rootfs image file generated by squashfs file system, and the second image file is a UBI image file.
5. A communication module software upgrade system, comprising:
the differential packet generation module is used for placing each source file of the file to be upgraded into the same firmware, placing each target file of the file to be upgraded into the same firmware, and generating a whole firmware file differential packet according to the original firmware file and the target firmware file;
The new file generating module is used for generating a whole new firmware file by the whole firmware file differential packet and the firmware file of the current equipment after the whole firmware file differential packet is received by the terminal side, and programming the generated whole new firmware file to a designated partition;
The upgrading module is used for programming the whole new firmware file in the appointed partition into the original firmware when upgrading, so as to integrally upgrade the current firmware file according to the firmware file of the appointed partition;
The marking module is used for marking an upgrade mark before the upgrade module integrally upgrades the current firmware file, and erasing the upgrade mark after the upgrade module integrally upgrades the current firmware file;
the starting module is used for indicating the upgrading module to integrally upgrade the current firmware file according to the firmware file of the appointed partition when the upgrading mark is found out when the communication module is started;
the file difference packet at least comprises: source firmware version information, target firmware version information;
the source firmware version information at least comprises: source firmware file size, source firmware file version number, source firmware file check value;
The target firmware version information includes at least: target firmware file size, target firmware file version number, target firmware file check value.
6. The communication module software upgrade system of claim 5, further comprising:
The first image file generation module is used for generating a first image file of the source firmware from the source firmware file;
The second image file generating module is used for generating a source firmware second image file from the source firmware first image file and the source firmware version information;
The first image file generation module is further used for generating a target firmware first image file from the target firmware file;
The second image file generating module is further used for generating a target firmware second image file from the target firmware first image file and the target firmware version information;
And the differential packet generation module generates the differential packet according to the source firmware second image file and the target firmware second image file.
7. The communication module software upgrade system of claim 5, further comprising:
The first verification module is used for verifying whether the version information of the firmware file of the current device is consistent with the version information of the source firmware stored in the file differential packet, and if so, the new file generation module is instructed to generate a new firmware file by the firmware file differential packet and the firmware file of the current device;
And the second checking module is used for checking whether the check value of the generated new firmware file is consistent with the check value of the target firmware file in the file differential packet, and if so, indicating the production module to burn the generated new firmware file into the appointed partition.
Priority Applications (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910207145.1A CN110032377B (en) | 2019-03-19 | 2019-03-19 | Communication module software upgrading method and system and communication module |
| PCT/CN2019/080526 WO2020186551A1 (en) | 2019-03-19 | 2019-03-29 | Communication module software upgrading method and system, and communication module |
| CN201980094458.9A CN113767365A (en) | 2019-03-19 | 2019-03-29 | Communication module software upgrading method and system and communication module |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910207145.1A CN110032377B (en) | 2019-03-19 | 2019-03-19 | Communication module software upgrading method and system and communication module |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110032377A CN110032377A (en) | 2019-07-19 |
| CN110032377B true CN110032377B (en) | 2024-06-07 |
Family
ID=67236224
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910207145.1A Active CN110032377B (en) | 2019-03-19 | 2019-03-19 | Communication module software upgrading method and system and communication module |
| CN201980094458.9A Pending CN113767365A (en) | 2019-03-19 | 2019-03-29 | Communication module software upgrading method and system and communication module |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201980094458.9A Pending CN113767365A (en) | 2019-03-19 | 2019-03-29 | Communication module software upgrading method and system and communication module |
Country Status (2)
| Country | Link |
|---|---|
| CN (2) | CN110032377B (en) |
| WO (1) | WO2020186551A1 (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111638898A (en) * | 2020-06-05 | 2020-09-08 | 泸州禾苗通信科技有限公司 | Cloud verification method for absolute consistency of firmware version upgrading of FOTA |
| CN112181471A (en) * | 2020-10-16 | 2021-01-05 | 北京紫光展锐通信技术有限公司 | Differential upgrading method and device, storage medium and computer equipment |
| CN112328269B (en) * | 2020-11-26 | 2024-03-15 | 广东小天才科技有限公司 | Method for mounting ubifs mirror image software, intelligent device, electronic device and storage medium |
| CN112433750A (en) * | 2020-12-17 | 2021-03-02 | 潍柴动力股份有限公司 | Vehicle-mounted terminal application program upgrading method, device, equipment, medium and product |
| CN112631633A (en) * | 2021-01-07 | 2021-04-09 | 南方电网数字电网研究院有限公司 | Function module upgrading method and device based on double-core intelligent electric meter |
| CN115469910B (en) * | 2022-11-15 | 2023-02-03 | 浙江日风电气股份有限公司 | Photovoltaic inverter firmware updating method, device, system and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2356564A1 (en) * | 2008-11-10 | 2011-08-17 | Nokia Corporation | Method and apparatus for updating firmware |
| CN102724308A (en) * | 2012-06-13 | 2012-10-10 | 腾讯科技（深圳）有限公司 | Software update method and software update system |
| CN104391728A (en) * | 2014-12-12 | 2015-03-04 | 北京奇虎科技有限公司 | Software upgrading delta pack acquiring method, corresponding upgrading method and device |
| CN105138347A (en) * | 2015-07-17 | 2015-12-09 | 广东欧珀移动通信有限公司 | Difference upgrade patch generating method, software upgrading method and corresponding apparatus |
| CN105487907A (en) * | 2015-12-07 | 2016-04-13 | 青岛海信电器股份有限公司 | Difference package manufacturing method and device |
| CN109002312A (en) * | 2018-09-10 | 2018-12-14 | 京信通信***（中国）有限公司 | Method for upgrading software, device and upgrade server and equipment |
| CN109375939A (en) * | 2018-12-17 | 2019-02-22 | 蜂巢(武汉)微***技术有限公司 | A kind of onboard system firmware on line upgrading method |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9575741B2 (en) * | 2014-03-20 | 2017-02-21 | Google Technology Holdings LLC | Methods and devices for wireless device-to-device software upgrades |
| CN104184814A (en) * | 2014-08-25 | 2014-12-03 | 中山市永衡日用制品有限公司 | Method and system for generating and compounding embedded firmware differential upgrading file |
| CN105511911B (en) * | 2015-11-27 | 2019-02-12 | 青岛海信移动通信技术股份有限公司 | The generation method and device of system firmware upgrade package |
| CN105373410B (en) * | 2015-12-22 | 2019-04-30 | 京信通信***（中国）有限公司 | Base station software difference upgrade method and its device |
| CN107391145A (en) * | 2017-07-27 | 2017-11-24 | 中兴通讯股份有限公司 | AKU preparation method and device, the method and device of upgrade file |
| CN109240720B (en) * | 2018-08-23 | 2021-11-26 | 瑞芯微电子股份有限公司 | Firmware upgrading method of android system and storage device |
-
2019
- 2019-03-19 CN CN201910207145.1A patent/CN110032377B/en active Active
- 2019-03-29 CN CN201980094458.9A patent/CN113767365A/en active Pending
- 2019-03-29 WO PCT/CN2019/080526 patent/WO2020186551A1/en active Application Filing
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2356564A1 (en) * | 2008-11-10 | 2011-08-17 | Nokia Corporation | Method and apparatus for updating firmware |
| CN102724308A (en) * | 2012-06-13 | 2012-10-10 | 腾讯科技（深圳）有限公司 | Software update method and software update system |
| CN104391728A (en) * | 2014-12-12 | 2015-03-04 | 北京奇虎科技有限公司 | Software upgrading delta pack acquiring method, corresponding upgrading method and device |
| CN105138347A (en) * | 2015-07-17 | 2015-12-09 | 广东欧珀移动通信有限公司 | Difference upgrade patch generating method, software upgrading method and corresponding apparatus |
| CN105487907A (en) * | 2015-12-07 | 2016-04-13 | 青岛海信电器股份有限公司 | Difference package manufacturing method and device |
| CN109002312A (en) * | 2018-09-10 | 2018-12-14 | 京信通信***（中国）有限公司 | Method for upgrading software, device and upgrade server and equipment |
| CN109375939A (en) * | 2018-12-17 | 2019-02-22 | 蜂巢(武汉)微***技术有限公司 | A kind of onboard system firmware on line upgrading method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113767365A (en) | 2021-12-07 |
| CN110032377A (en) | 2019-07-19 |
| WO2020186551A1 (en) | 2020-09-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110032377B (en) | Communication module software upgrading method and system and communication module | |
| WO2015070521A1 (en) | Method for making ubi format system file into factory burnt image file | |
| CN107506219A (en) | A kind of general version upgrade method based on android system | |
| CN103455354B (en) | Method and equipment for preventing hardware update from failing | |
| CN109189405B (en) | Method and system for verifying Flash data consistency of program | |
| US8601464B2 (en) | Memory online update system and method | |
| US9442840B2 (en) | Virtual boundary codes in a data image of a read-write memory device | |
| CN105280240A (en) | Nand Flash parameter reading method | |
| CN109800005B (en) | Client hot update method and device | |
| CN108205446A (en) | Firmware restorative procedure and device | |
| CN111400267B (en) | Method and device for recording logs | |
| CN110874239A (en) | Air firmware differential upgrading method and device for electronic equipment | |
| CN104427119A (en) | Communication terminal and nonvolatile data processing method of communication terminal | |
| CN102650949A (en) | Method and device for upgrading firmware of storage equipment | |
| CN104133699A (en) | Equipment system software updating method and equipment system software updating system | |
| CN110007941A (en) | A kind of the MCU firmware and upgrade method of Intelligent refuse classification recovery system | |
| CN111966369B (en) | Method for manufacturing and verifying off-line burning mirror image of NAND memory | |
| CN111142922B (en) | Application program updating method, device, terminal and server | |
| CN104133743A (en) | Method and device for burning file into EMMC (Embedded MultiMedia Card) | |
| CN106293622A (en) | A kind of self-healing over-the-air upgrade method of power-off and device | |
| CN103399804A (en) | Method and system for repairing remote package files | |
| CN107479924A (en) | Software upgrading method of calibration based on android system | |
| CN107783778B (en) | Increment upgrading method based on characteristic value table look-up method | |
| CN114003266B (en) | Method and device for generating multiple differential packets based on Android flash firmware | |
| CN115469812A (en) | Waiting time setting method based on firmware burning and burning system |
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 |