A device calibration verification method, device calibration verification system and related apparatus

Abstract

The application provides a device calibration verification method, comprising: obtaining a calibration mark and a fuse mark; performing logical judgment according to the calibration mark and the fuse mark, and determining a first calibration mark and a first fuse mark after logical operation; after the device completes the fuse, reading the first calibration mark, adding a preset difference value to the first fuse mark, and assigning the value to the first fuse mark to obtain a current fuse mark; determining a security mark according to the first calibration mark and the current fuse mark; and when the security mark is in a writable state, performing device calibration verification according to the value of the security mark. The application determines the most suitable security mechanism for the current electronic device by judging the state of the fuse operation and the calibration operation, so that the software data signature no longer depends on the fuse key of the manufacturer, and the generation process of the electronic device does not depend on the fixed fuse and calibration sequence. The application also provides a device calibration verification system, a computer readable storage medium and an electronic device, which have the above beneficial effects.

Description

Technical Field

[0001] This application relates to the field of electronic equipment security, and in particular to a device calibration and verification method, a device calibration and verification system, and related devices. Background Technology

[0002] After all hardware components have been calibrated and software versions upgraded before the device leaves the factory, and it is confirmed that it meets commercial standards, a fuse key file will be written into the device's designated storage using electronic fuse security technology. This file contains a fuse key bound to the hardware code. Subsequently, when the device starts up, it uses this unique key to verify the data in the device's storage to ensure that the data has not been tampered with, thereby achieving the purpose of protecting the device's security.

[0003] Each manufacturer uses one or more fuse keys for batches or multiple batches of devices to maximize the protection of device data from external modification or damage. If data is corrupted or maliciously modified, preventing normal data import, the device will malfunction, thus preventing the leakage of user personal data. However, the encryption and signing keys used to save data to the device are provided by the software vendor, while the fuse keys are provided by the device manufacturer. If the software vendor provides the software data to the device manufacturer, inconsistencies in the keys after the fuse will prevent the device from verifying the software data, especially calibration data, after startup. This will render the device unable to use its communication functions, severely impacting device applications. Summary of the Invention

[0004] The purpose of this application is to provide a device calibration and verification method, a device calibration and verification system, a computer-readable storage medium, and an electronic device that can ensure that calibration data can still be imported normally after fuses are applied to devices from different manufacturers.

[0005] To address the aforementioned technical problems, this application provides a device calibration and verification method, the specific technical solution of which is as follows:

[0006] Obtain the calibration mark and fuse mark;

[0007] Perform logical judgment based on the calibration mark and the fuse mark to determine the first calibration mark and the first fuse mark after logical operation;

[0008] After the device completes the fuse operation, the first calibration mark is read, a preset difference is added, and the value is assigned to the first fuse mark to obtain the current fuse mark;

[0009] A safety identifier is determined based on the first calibration mark and the current fuse mark;

[0010] When the security identifier is in a writable state, device calibration verification is performed based on the value of the security identifier.

[0011] Optionally, before obtaining the calibration mark and fuse mark, the following steps are also included:

[0012] Perform device calibration on the device, and initialize both the initial calibration mark and the initial fuse mark to the first preset value.

[0013] Optionally, performing logical judgment based on the calibration mark and the fuse mark to determine the first calibration mark and the first fuse mark after logical operation includes:

[0014] Determine whether the calibration mark is a first preset value;

[0015] If the calibration mark is not the first preset value, no operation is performed;

[0016] If the calibration mark is a first preset value, determine whether the fuse mark is a first preset value;

[0017] If the fuse mark is not the first preset value, then the preset difference is added to the fuse mark and then assigned to the calibration mark to obtain the first calibration mark and the first fuse mark;

[0018] If the fuse mark is a first preset value, the preset difference is added to the calibration mark to obtain the first calibration mark.

[0019] Optionally, determining the safety identifier based on the first calibration mark and the current fuse mark includes:

[0020] If the current fuse flag is a first preset value, set the security flag to software state;

[0021] If the current fuse marker is not the first preset value, the first calibration marker is set to the first preset value, and the safety indicator is set to fuse status.

[0022] If neither the current fuse mark nor the first calibration mark is a first preset value, determine whether the first calibration mark is greater than the current fuse mark;

[0023] If so, set the safety indicator to the fuse state;

[0024] If not, set the security identifier to a special state and set the security identifier to a non-writable state.

[0025] Optionally, when the security identifier is in a writable state, device calibration verification is performed based on the value of the security identifier;

[0026] If the security indicator is in a fuse state, activate the security control verification procedure, read the fuse key, and verify the calibration data;

[0027] If the security identifier is in software state, enable the security control verification program, read the software key, and verify the calibration data.

[0028] If the security identifier is in a special state, the security control verification procedure is turned off.

[0029] Optionally, when the security identifier is in a writable state, the device calibration verification performed based on the value of the security identifier further includes:

[0030] Determine if the fuse key and the software key are consistent;

[0031] If they match, clear the first calibration mark and set the safety indicator to fuse status.

[0032] This application also provides a device calibration and verification system, including:

[0033] The marker acquisition module is used to acquire calibration markers and fuse markers;

[0034] The logic calculation module is used to perform logical judgments based on the calibration mark and the fuse mark to determine the first calibration mark and the first fuse mark after logical operation;

[0035] The marker update module is used to read the first calibration marker after the device completes the fuse operation, add a preset difference value, and then assign it to the first fuse marker to obtain the current fuse marker.

[0036] The security control module is used to determine a security identifier based on the first calibration mark and the current fuse mark, and to perform device calibration verification based on the value of the security identifier when the security identifier is in a writable state.

[0037] Optional, also includes:

[0038] The key verification module is used to determine whether the fuse key and the software key are consistent; if they are consistent, the first calibration flag is cleared and the security identifier is set to fuse status.

[0039] This application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described above.

[0040] This application also provides an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the method described above when it invokes the computer program in the memory.

[0041] This application provides a device calibration verification method, comprising: acquiring a calibration mark and a fuse mark; performing logical judgment based on the calibration mark and the fuse mark to determine a first calibration mark and a first fuse mark after logical operation; after the device completes fuse operation, reading the first calibration mark, adding a preset difference, and assigning the value to the first fuse mark to obtain a current fuse mark; determining a security identifier based on the first calibration mark and the current fuse mark; and performing device calibration verification based on the value of the security identifier when the security identifier is in a writable state.

[0042] This application identifies calibration operations and fuse operations using calibration marks and fuse marks respectively, and uses corresponding logical judgments based on the calibration marks and fuse marks in the current state of the electronic device. By judging the state of the fuse operation and calibration operation, the most suitable security mechanism for the current electronic device is determined, thereby achieving the effect of automatically adjusting the security mechanism and ensuring the effective import of calibration data. This makes the software data signature no longer dependent on the manufacturer's fuse key, and the generation process of the electronic device does not depend on a fixed fuse and calibration order.

[0043] This application also provides a device calibration and verification system, a computer-readable storage medium, and an electronic device, which have the above-mentioned beneficial effects, and will not be elaborated here. Attached Figure Description

[0044] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0045] Figure 1 A flowchart illustrating a device calibration and verification method provided in this application embodiment;

[0046] Figure 2 A flowchart illustrating another device calibration and verification method provided in this application embodiment;

[0047] Figure 3 This is a schematic diagram of a device calibration and verification system provided in an embodiment of this application. Detailed Implementation

[0048] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0049] Please refer to Figure 1 , Figure 1 A flowchart illustrating a device calibration and verification method provided in this application embodiment.

[0050] S101: Obtain calibration marks and fuse marks;

[0051] This step aims to obtain the calibration mark and fuse mark. Before performing this step, the device can be calibrated to initialize both the calibration mark and fuse mark to a first preset value. It is important to note that initialization is only performed upon the first power-on of the software or after a software re-download; subsequent power-ons do not require re-initialization. After performing data calibration, the calibration mark and fuse mark required for this step will be obtained. The first preset value is not limited here; it can typically be set to 0 or determined by those skilled in the art. In this embodiment, both the initial calibration mark and the initial fuse mark are used to assist in indicating the status of the electronic device during the data calibration process. Generally, the initial calibration mark increments by 1 for each calibration, and similarly, the initial fuse mark increments by 1 for each fuse failure.

[0052] S102: Perform logical judgment based on the calibration mark and the fuse mark to determine the first calibration mark and the first fuse mark after logical operation;

[0053] This step requires judgment based on the calibration mark and fuse mark. Logical operations are then performed to determine the first calibration mark and the first fuse mark after the logical operation.

[0054] One feasible implementation method is as follows:

[0055] Step 1: Determine if the calibration mark is the first preset value; if not, do not perform the operation; if yes, proceed to Step 2.

[0056] Step 2: Determine whether the fuse mark is the first preset value; if not, proceed to step 3; if yes, proceed to step 4.

[0057] The third step is to add the preset difference to the fuse mark and then assign it to the calibration mark to obtain the first calibration mark and the first fuse mark.

[0058] Step 4: Add the preset difference to the calibration mark to obtain the first calibration mark.

[0059] Taking a first preset value of 0 and a preset difference value of 1 as an example, this step actually involves logically judging whether the fuse mark and the calibration mark are 0, and only performing the corresponding operation when the calibration mark is 0. If the fuse mark is 0 at this time, the calibration mark is incremented by 1 to become the first calibration mark. If the fuse mark is not 0 at this time, the fuse mark is incremented by 1 and then assigned to the calibration mark.

[0060] S103: After the device completes the fuse operation, the first calibration mark is read, a preset difference is added, and the value is assigned to the first fuse mark to obtain the current fuse mark;

[0061] S104: Determine a safety indicator based on the first calibration mark and the current fuse mark;

[0062] This step aims to determine the safety indicator, which is initially empty. This step requires determining the safety indicator based on the current fuse mark and the first calibration mark. Specifically, logical judgments are performed based on the specific values ​​of the current fuse mark and the first standard mark to determine the safety indicator.

[0063] Specifically, when the security indicator includes three states: software status, fuse loaded, and special indicator, this step can include the following logical judgment process:

[0064] If the current fuse flag is the first preset value, set the security flag to software status;

[0065] If the current fuse flag is not the first preset value, the first calibration flag is set to the first preset value, and the safety indicator is set to fuse status.

[0066] If neither the current fuse mark nor the first calibration mark is a first preset value, determine whether the first calibration mark is greater than the current fuse mark;

[0067] If so, set the safety indicator to fuse status;

[0068] If not, set the security flag to a special state and set the security flag to a write-unwritable state.

[0069] In addition, if the fuse flag is not 1 or not 2, it indicates that the fuse is not working or the fuse is unreliable. In this case, the safety flag can be set to software status.

[0070] Since the fuse mark can only be 1 under normal circumstances, the first calibration mark is usually greater than the current fuse mark. However, if the first calibration mark is less than the fuse mark, it means that the device calibration process of the electronic device has malfunctioned. In this case, the safety indicator can be set to a special state, and changing the safety indicator state is prohibited. Of course, those skilled in the art can also set other safety indicator states to indicate the calibration verification method for subsequent steps.

[0071] S105: When the security identifier is in a writable state, perform device calibration verification based on the value of the security identifier.

[0072] This step requires performing the corresponding calibration verification based on the specific value of the security identifier in step S104. Specifically, if the security identifier is in a fuse state, that is, consistent with the initial state of the security identifier, the security control verification program is activated to read the fuse key and verify the data to be calibrated. If the security identifier is in a software state, it indicates that preparation is complete, and the security control verification program can be activated to read the software key and verify the data to be calibrated.

[0073] However, if the security identifier is in a special state, it indicates that the security identifier is in a non-writable state. In this case, the security control verification program will be shut down directly, and the device calibration verification will no longer be performed.

[0074] In this embodiment, both the initial calibration mark and the first calibration mark are calibration marks used to distinguish calibration marks in different stages of the process. Similarly, both the initial fuse mark and the current fuse mark are also fuse marks. In practical applications of this application, calibration marks can be uniformly replaced by an indicative term, and an attribute value can be added to this indicative term to serve as the specific value of the calibration mark. Similarly, fuse marks can also be adopted in the same way, which will not be elaborated here.

[0075] This application embodiment uses calibration marks and fuse marks to acutely identify calibration operations and fuse operations respectively, and uses corresponding logical judgments based on the calibration marks and fuse marks in the current state of the electronic device. By judging the state of the fuse operation and calibration operation, the most used security mechanism of the current electronic device is determined, thereby achieving the effect of automatically adjusting the security mechanism and ensuring the effective import of calibration data. This makes the software data signature no longer dependent on the manufacturer's fuse key, and the generation process of the electronic device does not depend on a fixed fuse and calibration order.

[0076] Based on this embodiment, as a preferred embodiment, when the security identifier is in a writable state, during the device calibration verification based on the value of the security identifier, it can be further determined whether the fuse key and the software key are consistent. If they are consistent, the first calibration mark is cleared and the security identifier is set to the fuse state.

[0077] To better describe the method provided in this application, a specific calibration data verification process is used to illustrate this application below. In this context, O_flag represents the calibration flag, F_flag represents the fuse flag, and Sec_disable represents the security flag. Sec_disable = NONE indicates the security flag is in fuse mode, Sec_disable = READY indicates the security flag is in software mode, and Sec_disable = ENHANCED indicates the security flag is in a special state. Taking a first flag value of 0 and a preset difference value of 1 as an example, the flowchart of another calibration data verification method corresponding to this application can be as follows: Figure 2 As shown.

[0078] refer to Figure 2 As shown in the process, for customer A, if they need software calibration data provided by the manufacturer, the customer performs the fuse operation.

[0079] Since the manufacturer performed data calibration, it has been determined that calibration has been completed, so the calibration flag O_flag is set to 1.

[0080] If the customer receives the software but has not yet fused the fuse, the fuse flag F_flag is 0, while the calibration flag O_flag is not 0. Therefore, the security flag Sec_disable is set to "ready to complete." Correspondingly, the security flag is now in a writable state, enabling the security control verification program to read the software key and verify the calibration data.

[0081] If the customer has already fused the fuse, since the calibration flag O_flag is 1, the value of the calibration flag O_flag is read and incremented by 1 and assigned to the fuse flag F_flag. At this time, the fuse flag F_flag is 2, that is, the calibration flag O_flag is less than the fuse flag F_flag. The security flag is set to a special state and cannot be written to, and the security control verification program is closed.

[0082] For customer B, the calibration and fuse installation are handled by the customer themselves, and the process is as follows:

[0083] If calibration is performed first, the calibration flag O_flag is 1. At this point, there is no fuse yet, i.e., the fuse flag F_flag is 0, but the calibration flag O_flag is not 0. The security flag Sec_disable is set to complete, the security control verification program is enabled, the software key is read, and the calibration data is verified.

[0084] If the customer finds that the previous calibration data is incorrect, continue the calibration. The calibration flag O_flag remains unchanged or is incremented by 1, but the fuse flag F_flag remains 0. The execution process is the same as above.

[0085] The customer initiates fuse activation, reads the calibration flag O_flag, increments it by 1, and assigns it to the fuse flag, resulting in a fuse flag F_flag value of 2. At this point, the calibration flag O_flag is always less than the fuse flag F_flag. The security flag is set to a special state and cannot be written to, and the security control verification program is disabled.

[0086] If the customer uses the same key for fuses and calibration, set the security flag to fuse status. At this time, the security control verification program is activated to read the fuse key and verify the calibration data.

[0087] Compared to Customer A and Customer B, regardless of who performs the fuse and calibration operations, the current status of the fuse and calibration operations can be judged using the corresponding safety indicators. The corresponding verification can be performed according to the markings of the safety indicators, or the calibration verification can be stopped. The execution order of calibration and fuse is no longer strictly required, so that calibration data can still be imported normally after fuse operations are performed by different equipment manufacturers, avoiding abnormal calibration data import.

[0088] The following describes the equipment calibration and verification system provided in the embodiments of this application. The equipment calibration and verification system described below can be referred to in correspondence with the equipment calibration and verification method described above.

[0089] See Figure 3 , Figure 3 This application provides a schematic diagram of a device calibration and verification system, which includes:

[0090] The marker acquisition module is used to acquire calibration markers and fuse markers;

[0091] The logic calculation module is used to perform logical judgments based on the calibration mark and the fuse mark to determine the first calibration mark and the first fuse mark after logical operation;

[0092] The marker update module is used to read the first calibration marker after the device completes the fuse operation, add a preset difference value, and then assign it to the first fuse marker to obtain the current fuse marker.

[0093] The security control module is used to determine a security identifier based on the first calibration mark and the current fuse mark, and to perform device calibration verification based on the value of the security identifier when the security identifier is in a writable state.

[0094] Based on the above embodiments, as a preferred embodiment, it further includes:

[0095] An initialization module is used to perform device calibration on the device, and initialize the initial calibration mark and the initial fuse mark to a first preset value.

[0096] Based on the above embodiments, as a preferred embodiment, the logic calculation module includes:

[0097] The determination unit is used to determine whether the calibration mark is a first preset value;

[0098] The logic operation unit is configured to: if the calibration mark is not a first preset value, not perform any operation; if the calibration mark is a first preset value, determine whether the fuse mark is a first preset value; if the fuse mark is not a first preset value, add the preset difference to the fuse mark and assign it to the calibration mark to obtain a first calibration mark and a first fuse mark; if the fuse mark is a first preset value, add the preset difference to the calibration mark to obtain a first calibration mark.

[0099] Based on the above embodiments, as a preferred embodiment, the security control module includes:

[0100] The first safety identifier setting unit is configured to set the safety identifier to a software state if the current fuse identifier is a first preset value; and to set the safety identifier to a fuse state if the current fuse identifier is not a first preset value and the first calibration identifier is a first preset value.

[0101] The second security identifier setting unit is used to determine whether the first calibration mark is greater than the current fuse mark if neither the current fuse mark nor the first calibration mark is a first preset value; if yes, set the security identifier to a fuse state; if no, set the security identifier to a special state and set the security identifier to an unwritable state.

[0102] Based on the above embodiments, as a preferred embodiment, the security control module includes:

[0103] The verification unit is configured to, if the security identifier is in a fuse state, activate the security control verification program, read the fuse key, and verify the calibration data; if the security identifier is in a software state, activate the security control verification program, read the software key, and verify the calibration data.

[0104] The non-verification unit is used to shut down the security control verification procedure if the security identifier is in a special state.

[0105] Based on the above embodiments, as a preferred embodiment, it further includes:

[0106] The key verification module is used to determine whether the fuse key and the software key are consistent; if they are consistent, the first calibration flag is cleared and the security identifier is set to fuse status.

[0107] This application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed, can perform the steps provided in the above embodiments. The storage medium may include various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0108] This application also provides an electronic device that may include a memory and a processor. The memory stores a computer program, and when the processor calls the computer program in the memory, it can implement the steps provided in the above embodiments. Of course, the electronic device may also include various network interfaces, power supplies, and other components.

[0109] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. As the system provided in the embodiments corresponds to the method provided in the embodiments, the description is relatively simple; relevant parts can be found in the method section.

[0110] This document uses specific examples to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are only for the purpose of helping to understand the method and core ideas of this application. It should be noted that those skilled in the art can make several improvements and modifications to this application without departing from the principles of this application, and these improvements and modifications also fall within the protection scope of the claims of this application.

[0111] It should also be noted that, in this specification, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

Claims

1. A method for calibrating and verifying equipment, characterized in that, include: Obtain the calibration mark and fuse mark; Perform logical judgment based on the calibration mark and the fuse mark to determine the first calibration mark and the first fuse mark after logical operation; After the device completes the fuse operation, the first calibration mark is read, a preset difference is added, and the value is assigned to the first fuse mark to obtain the current fuse mark; A safety identifier is determined based on the first calibration mark and the current fuse mark; When the security identifier is in a writable state, device calibration verification is performed based on the value of the security identifier. Specifically, performing logical judgments based on the calibration mark and the fuse mark to determine the first calibration mark and the first fuse mark after logical operation includes: Determine whether the calibration mark is a first preset value; If the calibration mark is not the first preset value, no operation is performed; If the calibration mark is a first preset value, determine whether the fuse mark is a first preset value; If the fuse mark is not the first preset value, then the preset difference is added to the fuse mark and then assigned to the calibration mark to obtain the first calibration mark and the first fuse mark; If the fuse mark is a first preset value, the preset difference is added to the calibration mark to obtain the first calibration mark.

2. The equipment calibration and verification method according to claim 1, characterized in that, Before obtaining the calibration mark and fuse mark, the following is also included: The device is initialized by setting the initial calibration flag and the initial fuse flag to the first preset value. When the device performs device calibration, the initial calibration mark is updated to the calibration mark, and the initial fuse mark is synchronously updated to the fuse mark.

3. The equipment calibration and verification method according to claim 1, characterized in that, Determining the safety identifier based on the first calibration mark and the current fuse mark includes: If the current fuse flag is a first preset value, set the security flag to software state; If the current fuse marker is not the first preset value, the first calibration marker is set to the first preset value, and the safety indicator is set to fuse status. If neither the current fuse mark nor the first calibration mark is a first preset value, determine whether the first calibration mark is greater than the current fuse mark; If so, set the safety indicator to the fuse state; If not, set the security identifier to a special state and set the security identifier to a non-writable state.

4. The equipment calibration and verification method according to claim 3, characterized in that, When the security identifier is in a writable state, performing device calibration verification based on the value of the security identifier includes: If the security indicator is in a fuse state, activate the security control verification procedure, read the fuse key, and verify the calibration data; If the security identifier is in software state, enable the security control verification program, read the software key, and verify the calibration data; If the security identifier is in a special state, the security control verification procedure is turned off.

5. The equipment calibration and verification method according to claim 1, characterized in that, When the security identifier is in a writable state, the device calibration verification performed based on the value of the security identifier further includes: Determine if the fuse key and the software key are consistent; If they match, clear the first calibration mark and set the safety indicator to fuse status.

6. A device calibration and verification system, characterized in that, include: The marker acquisition module is used to acquire calibration markers and fuse markers; The logic calculation module is used to perform logical judgments based on the calibration mark and the fuse mark to determine the first calibration mark and the first fuse mark after logical operation; The marker update module is used to read the first calibration marker after the device completes the fuse operation, add a preset difference value, and then assign it to the first fuse marker to obtain the current fuse marker. The security control module is used to determine a security identifier based on the first calibration mark and the current fuse mark, and to perform device calibration verification based on the value of the security identifier when the security identifier is in a writable state; The logic calculation module includes: The determination unit is used to determine whether the calibration mark is a first preset value; The logic operation unit is configured to: if the calibration mark is not a first preset value, not perform any operation; if the calibration mark is a first preset value, determine whether the fuse mark is a first preset value; if the fuse mark is not a first preset value, add the preset difference to the fuse mark and assign it to the calibration mark to obtain a first calibration mark and a first fuse mark; if the fuse mark is a first preset value, add the preset difference to the calibration mark to obtain a first calibration mark.

7. The equipment calibration and verification system according to claim 6, characterized in that, Also includes: The key verification module is used to determine whether the fuse key and the software key are consistent; If they match, clear the first calibration mark and set the safety indicator to fuse status.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the device calibration and verification method as described in any one of claims 1-5.

9. An electronic device, characterized in that, It includes a memory and a processor, wherein the memory stores a computer program, and the processor, when calling the computer program in the memory, implements the steps of the device calibration and verification method as described in any one of claims 1-5.

Images