CN111638898A - Cloud verification method for absolute consistency of firmware version upgrading of FOTA - Google Patents
Cloud verification method for absolute consistency of firmware version upgrading of FOTA Download PDFInfo
- Publication number
- CN111638898A CN111638898A CN202010507808.4A CN202010507808A CN111638898A CN 111638898 A CN111638898 A CN 111638898A CN 202010507808 A CN202010507808 A CN 202010507808A CN 111638898 A CN111638898 A CN 111638898A
- Authority
- CN
- China
- Prior art keywords
- abstract
- server
- upgrade package
- upgrade
- version
- 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 31
- 238000012795 verification Methods 0.000 title claims abstract description 23
- 238000004519 manufacturing process Methods 0.000 claims abstract description 4
- 238000012216 screening Methods 0.000 claims abstract description 4
- 238000005192 partition Methods 0.000 claims description 28
- 230000003993 interaction Effects 0.000 claims description 3
- 230000000977 initiatory effect Effects 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000007488 abnormal function Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001960 triggered 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
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/194—Calculation of difference between files
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Computational Linguistics (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Artificial Intelligence (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Bioethics (AREA)
- Computer Hardware Design (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a cloud verification method for absolute consistency of firmware versions upgraded by FOTA, which comprises the following steps: s1: manufacturing a firmware differential upgrade package from a source version to a target version, and uploading the upgrade package to a cloud server by an FOTA upgrade configuration administrator; s2: screening target equipment to be upgraded to form an upgrading group, and creating and starting an upgrading task; s3: the target equipment is registered to the cloud server and is on line, and the server conducts basic upgrading capability check and end cloud firmware version absolute consistency check on the target equipment. According to the invention, the absolute consistency check of the FOTA upgrade firmware version is raised from the traditional equipment side to the cloud side, so that various upgrade exceptions (such as incapability of starting, functional disorder and the like), flow and power loss and the like caused by sinking of a problem upgrade package (such as server upgrade package configuration error, damage or malicious tampering) to the equipment side can be avoided to the greatest extent.
Description
Technical Field
The invention relates to the technical field of FOTA upgrading, in particular to a cloud verification method for absolute consistency of FOTA upgrading firmware versions.
Background
When the FOTA is upgraded on the equipment side, theoretically, absolute consistency check needs to be performed first, wherein the absolute consistency check means whether the current running firmware version of the equipment is absolutely consistent with the source firmware version for making the FOTA upgrade package, and the absolute consistency means that not only are basic information such as version number, model number, manufacturer and the like consistent, but also the version must be compiled at the same time, so that the problem of upgrading cannot be solved to the maximum extent.
In the existing FOTA upgrading scheme, an upgrading packet is often downloaded into equipment, the equipment fails to perform absolute consistency verification on the current version and the upgrading packet, so that upgrading cannot be performed, and then the equipment repeatedly retries the process of downloading and verification failure according to the retry times defined by cloud upgrading, so that a large amount of equipment data flow and electric quantity are consumed; or some devices are not verified completely due to an incomplete verification mechanism, so that the upgrading package with problems (such as wrong configuration, damage or malicious tampering of the server upgrading package) is triggered to be upgraded, and the serious problems that the devices cannot be started or have abnormal functions are caused.
It is common practice for the above phenomenon that habitually this is considered normal and not a problem: the absolute consistency check should be performed before the device side is upgraded, and the work focus of the server side should be performed in the access authentication, registration connection management, management of uplink and downlink service data, management of upgrade groups and task flows, etc. of the mass devices. Therefore, when initiating or prompting FOTA upgrade, the server generally performs basic upgrade capability check on the device, such as checking whether the device power, the cell ID/signal quality, the available space, and the device version number meet the configuration requirements of the upgrade task, and ignores absolute consistency check on the version to be upgraded.
Disclosure of Invention
The technical problem to be solved by the invention is to provide a cloud verification method for absolute consistency of FOTA upgrade firmware versions, so as to solve the problems in the background art.
The invention is realized by the following technical scheme: a cloud verification method for absolute consistency of firmware versions upgraded by FOTA is characterized by comprising the following steps: the method comprises the following steps:
s1: manufacturing a firmware differential upgrade package from a source version to a target version, and uploading the upgrade package to a cloud server by an FOTA upgrade configuration administrator;
s2: screening target equipment to be upgraded to form an upgrading group, and creating and starting an upgrading task;
s3: the target equipment is registered in a cloud server and is on line, the server starts the check of basic upgrading capability and the check of the absolute consistency of the end cloud firmware version to the target equipment, if any check fails, the server does not start the equipment upgrading process, and informs an administrator or a user of the reason of the check failure, and the process is ended;
if the server passes the verification, an upgrade flow is started for the target equipment, the target equipment downloads the upgrade package, then the follow-up flows of target equipment upgrade package verification, upgrade package execution and the like are completed, the state interaction with the server is finally completed, and the server informs an administrator or a user of the final upgrade result.
As a preferred technical solution, the S1 includes the process:
the upgrade package is signed, the server needs to check the signature, the public key in the upgrade package is used for unlocking the signature, the abstract and an abstract algorithm are taken, the abstract comprises the abstract of the upgrade package and the abstract of the mirror image of each partition of the source version, the server recalculates the abstract of the upgrade package according to the abstract algorithm and compares the abstract with the abstract analyzed from the package, if the abstract is consistent with the abstract, the upgrade package is intact, and the abstract of each partition of the source version is credible;
if the upgrade package is not signed, the upgrade package is directly considered to be credible, and the mirror image abstracts of each partition of the current version in the upgrade package are directly extracted.
As a preferred technical solution, the S3 includes the process:
the server sends an abstract algorithm (such as SHA256 and the like) of each partition image file of the source version extracted from the upgrade package to the equipment side, the equipment side calculates an instant abstract of each partition image file of the current firmware version according to the abstract algorithm and sends the instant abstract to the cloud server, and the server compares the abstract with the abstract of each partition image file corresponding to the source version extracted from the upgrade package (the comparison principle is that if all the abstract are the same, the absolute consistency check is successful, otherwise, if one abstract is inconsistent, the absolute consistency check is failed);
or the server sends the abstracts and the algorithms of the image files of the partitions corresponding to the source version extracted from the upgrade package to the equipment side, the equipment side calculates the instant abstracts of the image files of the partitions of the current firmware version according to the abstracts and the algorithms and compares the instant abstracts with the abstracts sent by the server (the comparison principle is the same as the above), and the comparison result is returned to the server side.
The invention has the beneficial effects that: by raising the absolute consistency check of the FOTA upgrade firmware version from the traditional equipment side to the cloud, various upgrade exceptions (such as incapability of starting up, functional disorder and the like), flow and power loss and the like caused by sinking of a problem upgrade package (such as server upgrade package configuration error, damage or malicious tampering and the like) to the equipment side can be avoided to the greatest extent.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a flow chart of the method of the present invention.
Detailed Description
Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the accompanying drawings are illustrative only for the purpose of explaining the present invention, and are not to be construed as limiting the present invention.
In the description of the present invention, it is to be understood that the terms "center", "upper", "lower", "front", "rear", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", etc., indicate orientations or positional relationships based on those shown in the drawings, and are only for convenience of description and simplicity of description, and do not indicate or imply that the devices or elements referred to must have a particular orientation, be constructed and operated in a particular orientation, and thus, are not to be construed as limiting the present invention.
In the description of the present invention, it should be noted that unless otherwise explicitly stated or limited, the terms "mounted," "connected," and "disposed" are to be construed broadly and can, for example, be fixedly connected, disposed, detachably connected, disposed, or integrally connected and disposed. The specific meanings of the above terms in the present invention can be understood in specific cases to those skilled in the art.
As shown in fig. 1, the cloud verification method for FOTA upgrade firmware version absolute consistency according to the present invention is characterized in that: the method comprises the following steps:
s1: manufacturing a firmware differential upgrade package from a source version to a target version, and uploading the upgrade package to a cloud server by an FOTA upgrade configuration administrator;
s2: screening target equipment to be upgraded to form an upgrading group, and creating and starting an upgrading task;
s3: the target equipment is registered in a cloud server and is on line, the server starts the check of basic upgrading capability and the check of the absolute consistency of the end cloud firmware version to the target equipment, if any check fails, the server does not start the equipment upgrading process, and informs an administrator or a user of the reason of the check failure, and the process is ended;
if the verification is passed and the server passes the verification, an upgrading process is started for the target equipment, the target equipment downloads the upgrading packet, then the subsequent processes of target equipment upgrading packet verification, upgrading packet execution and the like are completed, the state interaction with the server is finally completed, and the server informs an administrator or a user of the final upgrading result.
In this embodiment, the S1 includes:
the upgrade package is signed, the server needs to check the signature, the public key in the upgrade package is used for unlocking the signature, the abstract and an abstract algorithm are taken, the abstract comprises the abstract of the upgrade package and the abstract of the mirror image of each partition of the source version, the server recalculates the abstract of the upgrade package according to the abstract algorithm and compares the abstract with the abstract analyzed from the package, if the abstract is consistent with the abstract, the upgrade package is intact, and the abstract of each partition of the source version is credible;
if the upgrade package is not signed, the upgrade package is directly considered to be credible, and the mirror image abstracts of each partition of the current version in the upgrade package are directly extracted.
In this embodiment, the S3 includes:
the server sends an abstract algorithm (such as SHA256 and the like) of each partition image file of the source version extracted from the upgrade package to the equipment side, the equipment side calculates an instant abstract of each partition image file of the current firmware version according to the abstract algorithm and sends the instant abstract to the cloud server, and the server compares the abstract with the abstract of each partition image file corresponding to the source version extracted from the upgrade package (the comparison principle is that if all the abstract are the same, the absolute consistency check is successful, otherwise, if one abstract is inconsistent, the absolute consistency check is failed);
or the server sends the abstracts and the algorithms of the image files of the partitions corresponding to the source version extracted from the upgrade package to the equipment side, the equipment side calculates the instant abstracts of the image files of the partitions of the current firmware version according to the abstracts and the algorithms and compares the instant abstracts with the abstracts sent by the server (the comparison principle is the same as the above), and the comparison result is returned to the server side.
The firmware upgrade package is specifically a differential file package from a source version to a target version, and is used for differentially upgrading equipment from a current version (source version) to the target version, when the upgrade package is manufactured through a tool, specific source version files and target version files need to be specified, the source version files and the target version files are generated through compiling and comprise one or more image files which can be burnt to each partition of the target equipment through a burning tool, when the upgrade package is required to be generated, abstracts (hash values) of the image files of each partition of the source version files and a specific abstraction algorithm need to be added into the upgrade package, and the upgrade package is uploaded to a cloud server by an FOTA upgrade task configuration manager.
The target equipment needs to be upgraded through the upgrade package, legal registration is needed to access the server and establish connection with the server before upgrading, the server is matched to perform basic upgrade capability check and absolute consistency check of the end cloud firmware version, the upgrade package can be downloaded from the server after the upgrade package is passed, and a subsequent upgrade process is executed, so that the problem that the upgrade package sinks to the target equipment side to the greatest extent, and upgrading cannot be performed or is abnormal.
The cloud server is a generic term, may also be called a cloud platform, an internet of things or an IOT platform, and may be an internet of things connection management platform mainstream in the industry, or may also be an application server or a management platform private to a user.
The server works by accurately checking the opposite-end cloud firmware version before initiating FOTA upgrade to the target equipment, so that the content of the currently running firmware version in the target equipment is absolutely consistent with the content of the source version selected when the upgrade package is made, and if and only if the version image file compiled at the same time meets the requirement, for example, under the condition that the firmware source code is not changed, two versions are respectively compiled, and although the version numbers of the two versions are completely the same as the firmware function, the content is different, so that the versions cannot pass the verification.
Before initiating FOTA upgrade, except that basic upgrade capability check items (electric quantity, signal strength, version number, available space and the like) of equipment need to meet requirements, the server also needs to require that a terminal cloud firmware version meets the absolute consistency check requirements provided by the invention, the server starts an upgrade process, related equipment can download an upgrade package for upgrade, otherwise, the server does not start the upgrade process, and informs a FOTA upgrade configuration manager of specific reasons for which each equipment cannot be upgraded in an interface display or other notification modes.
The invention can especially avoid the upgrade package sinking under the following 2 most secret discordance conditions:
1) the upgrade package is configured to the server, for various reasons, although the source code and the function corresponding to the source firmware version and the current firmware version of the target device are completely consistent, the upgrade package is not compiled at the same time, the upgrade package can be sunk to the device side in a conventional manner, but the device side verification cannot be passed usually, and then the device will retry the process of downloading and verification failure repeatedly according to the retry strategy configured by the upgrade task, resulting in a large amount of device data traffic and electric quantity consumption.
2) In the case that the current running firmware (partition image file) of the target device is tampered, for example, the current running firmware (partition image file) may be flushed with other versions due to a security flaw or by human tampering, the upgrade package cannot be prevented from sinking in the conventional manner, even if the upgrade package has no problem, the upgrade package cannot be verified on the device side generally, and the side effects are the same as those in 1).
The invention can help related enterprises to reduce the after-sale maintenance workload and the maintenance cost of the equipment to a great extent, and improve the operation management capability of the equipment.
The above description is only an embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that are not thought of through the inventive work should be included in the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope defined by the claims.
Claims (3)
1. A cloud verification method for absolute consistency of firmware versions upgraded by FOTA is characterized by comprising the following steps: the method comprises the following steps:
s1: manufacturing a firmware differential upgrade package from a source version to a target version, and uploading the upgrade package to a cloud server by an FOTA upgrade configuration administrator;
s2: screening target equipment to be upgraded to form an upgrading group, and creating and starting an upgrading task;
s3: the target equipment is registered in a cloud server and is on line, the server starts the check of basic upgrading capability and the check of the absolute consistency of the end cloud firmware version to the target equipment, if any check fails, the server does not start the equipment upgrading process, and informs an administrator or a user of the reason of the check failure, and the process is ended;
if the server passes the verification, an upgrade flow is started for the target equipment, the target equipment downloads the upgrade package, then the follow-up flows of target equipment upgrade package verification, upgrade package execution and the like are completed, the state interaction with the server is finally completed, and the server informs an administrator or a user of the final upgrade result.
2. The cloud verification method for FOTA upgrade firmware version absolute consistency according to claim 1, wherein the S1 includes a process of:
the upgrade package is signed, the server needs to check the signature, the public key in the upgrade package is used for unlocking the signature, the abstract and an abstract algorithm are taken, the abstract comprises the abstract of the upgrade package and the abstract of the mirror image of each partition of the source version, the server recalculates the abstract of the upgrade package according to the abstract algorithm and compares the abstract with the abstract analyzed from the package, if the abstract is consistent with the abstract, the upgrade package is intact, and the abstract of each partition of the source version is credible;
if the upgrade package is not signed, the upgrade package is directly considered to be credible, and the mirror image abstracts of each partition of the current version in the upgrade package are directly extracted.
3. The cloud verification method for FOTA upgrade firmware version absolute consistency according to claim 1, wherein: the S3 includes a process:
the server sends an abstract algorithm (such as SHA256 and the like) of each partition image file of the source version extracted from the upgrade package to the equipment side, the equipment side calculates an instant abstract of each partition image file of the current firmware version according to the abstract algorithm and sends the instant abstract to the cloud server, and the server compares the abstract with the abstract of each partition image file corresponding to the source version extracted from the upgrade package (the comparison principle is that if all the abstract are the same, the absolute consistency check is successful, otherwise, if one abstract is inconsistent, the absolute consistency check is failed);
or the server sends the abstracts and the algorithms of the image files of the partitions corresponding to the source version extracted from the upgrade package to the equipment side, the equipment side calculates the instant abstracts of the image files of the partitions of the current firmware version according to the abstracts and the algorithms and compares the instant abstracts with the abstracts sent by the server (the comparison principle is the same as the above), and the comparison result is returned to the server side.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010507808.4A CN111638898A (en) | 2020-06-05 | 2020-06-05 | Cloud verification method for absolute consistency of firmware version upgrading of FOTA |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010507808.4A CN111638898A (en) | 2020-06-05 | 2020-06-05 | Cloud verification method for absolute consistency of firmware version upgrading of FOTA |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111638898A true CN111638898A (en) | 2020-09-08 |
Family
ID=72328727
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010507808.4A Pending CN111638898A (en) | 2020-06-05 | 2020-06-05 | Cloud verification method for absolute consistency of firmware version upgrading of FOTA |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111638898A (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112383439A (en) * | 2020-11-24 | 2021-02-19 | 重庆前卫表业有限公司 | Air upgrading system and method for intelligent gas meter |
| CN112594587A (en) * | 2020-12-11 | 2021-04-02 | 泸州禾苗通信科技有限公司 | Full-weather intelligent module control device for street lamp |
| CN114039966A (en) * | 2021-10-18 | 2022-02-11 | 安徽泽峰物联科技有限公司 | Intelligent terminal based on LTE wireless communication technology and use method thereof |
| CN114090047A (en) * | 2021-11-27 | 2022-02-25 | 深圳市元征科技股份有限公司 | Software upgrading method and device |
| CN114637987A (en) * | 2022-05-18 | 2022-06-17 | 广州万协通信息技术有限公司 | Security chip firmware downloading method and system based on platform verification |
| WO2023024435A1 (en) * | 2021-08-25 | 2023-03-02 | 上海商汤智能科技有限公司 | Device registration method and apparatus, electronic device, storage medium, and computer program product |
| CN116149677A (en) * | 2022-11-30 | 2023-05-23 | 深圳市湘凡科技有限公司 | Method, device, equipment and medium for burning serial numbers |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012024963A1 (en) * | 2010-08-27 | 2012-03-01 | 华为终端有限公司 | Method, apparatus and system for processing firmware based on firmware over the air technology |
| CN106572372A (en) * | 2016-11-14 | 2017-04-19 | 青岛海信宽带多媒体技术有限公司 | Set-top box upgrading method and set-top box |
| CN110032377A (en) * | 2019-03-19 | 2019-07-19 | 芯讯通无线科技（上海）有限公司 | Communication module method for upgrading software, system and communication module |
| CN110134420A (en) * | 2019-05-22 | 2019-08-16 | 上海诺雅克电气有限公司 | Firmware upgrade method and system based on cloud platform |
| CN110929262A (en) * | 2019-11-20 | 2020-03-27 | 上海钧正网络科技有限公司 | Online upgrading method and system |
-
2020
- 2020-06-05 CN CN202010507808.4A patent/CN111638898A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012024963A1 (en) * | 2010-08-27 | 2012-03-01 | 华为终端有限公司 | Method, apparatus and system for processing firmware based on firmware over the air technology |
| CN106572372A (en) * | 2016-11-14 | 2017-04-19 | 青岛海信宽带多媒体技术有限公司 | Set-top box upgrading method and set-top box |
| CN110032377A (en) * | 2019-03-19 | 2019-07-19 | 芯讯通无线科技（上海）有限公司 | Communication module method for upgrading software, system and communication module |
| CN110134420A (en) * | 2019-05-22 | 2019-08-16 | 上海诺雅克电气有限公司 | Firmware upgrade method and system based on cloud platform |
| CN110929262A (en) * | 2019-11-20 | 2020-03-27 | 上海钧正网络科技有限公司 | Online upgrading method and system |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112383439A (en) * | 2020-11-24 | 2021-02-19 | 重庆前卫表业有限公司 | Air upgrading system and method for intelligent gas meter |
| CN112594587A (en) * | 2020-12-11 | 2021-04-02 | 泸州禾苗通信科技有限公司 | Full-weather intelligent module control device for street lamp |
| WO2023024435A1 (en) * | 2021-08-25 | 2023-03-02 | 上海商汤智能科技有限公司 | Device registration method and apparatus, electronic device, storage medium, and computer program product |
| CN114039966A (en) * | 2021-10-18 | 2022-02-11 | 安徽泽峰物联科技有限公司 | Intelligent terminal based on LTE wireless communication technology and use method thereof |
| CN114090047A (en) * | 2021-11-27 | 2022-02-25 | 深圳市元征科技股份有限公司 | Software upgrading method and device |
| CN114637987A (en) * | 2022-05-18 | 2022-06-17 | 广州万协通信息技术有限公司 | Security chip firmware downloading method and system based on platform verification |
| CN116149677A (en) * | 2022-11-30 | 2023-05-23 | 深圳市湘凡科技有限公司 | Method, device, equipment and medium for burning serial numbers |
| CN116149677B (en) * | 2022-11-30 | 2024-08-02 | 深圳市湘凡科技有限公司 | Method, device, equipment and medium for burning serial numbers |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111638898A (en) | Cloud verification method for absolute consistency of firmware version upgrading of FOTA | |
| US11966464B2 (en) | Security techniques for device assisted services | |
| US11405429B2 (en) | Security techniques for device assisted services | |
| US9652320B2 (en) | Device validation, distress indication, and remediation | |
| US11941390B2 (en) | End-point configuration and hardening for IoT devices | |
| US20210279049A1 (en) | Firmware upgrade method and apparatus | |
| EP2725836A1 (en) | Platform validation and management of wireless devices | |
| US10489145B2 (en) | Secure update of firmware and software | |
| US10044742B2 (en) | Verification of computer system prior to and subsequent to computer program installation | |
| CN112134692B (en) | Remote certification mode negotiation method and device | |
| EP3800860B1 (en) | Security techniques for device assisted services | |
| CN112073961B (en) | SIM card state updating method and device, terminal and readable storage medium | |
| CN116962149A (en) | Network fault detection method and device, storage medium and electronic equipment | |
| WO2020157369A1 (en) | Remote blockchain network agent for verifying and accepting patch requests from a patch initiator and method thereof | |
| AU2015221575A1 (en) | Device validation, distress indication, and remediation | |
| CN118312417A (en) | Debugging method, device, computer equipment, storage medium and program product |
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 |
Application publication date: 20200908 |