Calibration file management method
Patent Information
- Application Number
- CN202510399933.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-03-31
- Publication Date
- 2026-10-02
AI Technical Summary
[0004]本发明的目的在于提供一种校准文件管理方法,以解决现有技术中存在的新的指纹模组和旧的校准文件错配的问题以及因错配可能引起的安全性问题
[0018]与现有技术相比,本发明提供的一种校准文件管理方法,所述校准文件管理方法包括开机子方法,所述开机子方法包括:获取指纹芯片的序列号;基于所述序列号计算校准文件密钥;其中,所述序列号不同时,计算得到的所述校准文件密钥不同;获取所述校准文件中的密文数据,所述密文数据基于所述校准子方法生成并存储;基于所述校准文件密钥对所述密文数据进行解码,得到明文数据;以及,校验所述明文数据,校验结果用于参与最终的有效性判断。如此配置,当指纹模组更换时,序列号发生变化,进而影响所述密文数据的解码过程,通过验证解码结果,可以获得当前的指纹模组与当前的校准文件是否匹配的信息。所述校准文件管理方法从流程上规避了更换所述指纹模组时可能忘记更新校准文件的风险,解决了现有技术中存在的新的指纹模组和旧的校准文件错配的问题以及因错配可能引起的安全性问题;同时也加强校准数据的适用性,保证校准基准的最佳去噪能力。
Smart Images

Figure CN122863597A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of fingerprint data processing technology, and in particular to a calibration file management method. Background Technology
[0002] In existing technologies, fingerprint module calibration files are encrypted using fixed encryption fields. When a fingerprint module is replaced, the old calibration file may still exist, making it easy to overlook the recalibration process and mistakenly apply the old calibration file to the new fingerprint module. In such machines, due to assembly tolerances and module inherent deviations, the old calibration data cannot effectively reduce noise. Severe noise deviations can even cause new inherent texture features in the processed image, increasing the risk of worse FAR (false acceptance rate) and FRR (false rejection rate) during fingerprint unlocking. Furthermore, if the replaced fingerprint module still uses the old calibration file, there is also a security risk.
[0003] Therefore, existing technologies suffer from a mismatch between new fingerprint modules and old calibration files, which may lead to security issues. Summary of the Invention
[0004] The purpose of this invention is to provide a calibration file management method to solve the problem of mismatch between new fingerprint modules and old calibration files in the prior art, as well as the security problems that may be caused by the mismatch.
[0005] To address the aforementioned technical problems, this invention provides a calibration file management method for managing calibration files applied to a fingerprint module. The calibration file management method includes a power-on sub-method and a calibration sub-method. The power-on sub-method includes: obtaining the serial number of a fingerprint chip; the fingerprint chip belonging to the fingerprint module; calculating a calibration file key based on the serial number; wherein, different serial numbers result in different calculated calibration file keys; obtaining encrypted data from the calibration file, the encrypted data being generated and stored based on the calibration sub-method; decoding the encrypted data based on the calibration file key to obtain plaintext data; and verifying the plaintext data, the verification result being used in the final validity determination.
[0006] Optionally, the power-on sub-method further includes: obtaining the ID of the fingerprint chip and a software-specified code.
[0007] The step of calculating the calibration file key based on the serial number includes: concatenating the serial number, the ID, and the software-specified encoding to obtain the calibration file key. Alternatively, the step of calculating the calibration file key based on the serial number includes: concatenating the ID and the software-specified encoding to obtain an intermediate string; and performing a first logical operation on the intermediate string and the serial number to obtain the calibration file key.
[0008] Optionally, the step of calculating the calibration file key based on the serial number includes: concatenating the ID and the software-specified encoding to obtain an intermediate string; and XORing the intermediate string and the serial number to calculate the calibration file key.
[0009] Optionally, the power-on sub-method further includes: if obtaining the calibration file fails, displaying an error message and / or disabling the fingerprint module.
[0010] Optionally, before decoding the encrypted data based on the calibration file key, the power-on sub-method further includes: calculating a first hash value of the serial number; obtaining a second hash value from the calibration file; and comparing the first hash value and the second hash value. If they are the same, proceed to the next step; otherwise, determine that the calibration file is invalid and skip the next step.
[0011] The first hash value is calculated based on the calibration file key obtained by the boot sub-method; the second hash value is calculated based on the calibration file key obtained by the calibration sub-method.
[0012] Optionally, the calculation steps for the first hash value and the second hash value are as follows: the calibration file key is split according to the first bit length and a second logical operation is performed, and the calculation result is configured as the first hash value or the second hash value.
[0013] Optionally, the step of verifying the plaintext data includes: calculating a first checksum based on the data body; and comparing whether the first checksum and the second checksum are the same, with the result used to generate the verification result; wherein the plaintext data includes the data body and the second checksum, and the second checksum is generated based on the calibration sub-method.
[0014] Optionally, the calculation steps for the first check code and the second check code include: splitting the data body according to the second bit length and performing a third logical operation, and configuring the calculation result as the first check code or the second check code.
[0015] Optionally, the calibration sub-method includes: obtaining the serial number; calculating the calibration file key based on the serial number; wherein, when the serial numbers are different, the calculated calibration file key is different; the fingerprint module acquires multiple images under preset environmental conditions, determines whether they meet the conditions of the reference image, if they do, sets the data subject based on the acquired images, otherwise, repeatedly acquires images until they meet the conditions of the reference image; the data subject performs symmetric encryption operation based on the calibration file key to obtain the ciphertext data; and constructs the calibration file based on the ciphertext data and stores it in a preset directory.
[0016] Optionally, the step of performing symmetric encryption operations on the data body based on the calibration file key to obtain the ciphertext data includes: calculating a second checksum based on the data body, and performing symmetric encryption operations on the data body and the second checksum together based on the calibration file key to obtain the ciphertext data.
[0017] The steps of constructing the calibration file based on the ciphertext data include: calculating a second hash value based on the calibration file key, wherein the ciphertext data and the second hash value are configured together as components of the calibration file; before decoding the ciphertext data based on the calibration file key, the power-on sub-method further includes: calculating a first hash value of the serial number; obtaining a second hash value from the calibration file; and comparing the first hash value and the second hash value. If they are the same, subsequent steps are performed; otherwise, the calibration file is directly determined to be invalid and subsequent steps are skipped. The steps of verifying the plaintext data include: calculating a first checksum based on the data body; and comparing whether the first checksum and the second checksum are the same, wherein the determination result is used to generate the verification result.
[0018] Compared with existing technologies, the present invention provides a calibration file management method, which includes a power-on sub-method. The power-on sub-method includes: obtaining the serial number of the fingerprint chip; calculating a calibration file key based on the serial number; wherein, the calculated calibration file key is different when the serial number is different; obtaining encrypted data in the calibration file, the encrypted data being generated and stored based on the calibration sub-method; decoding the encrypted data based on the calibration file key to obtain plaintext data; and verifying the plaintext data, the verification result being used in the final validity judgment. With this configuration, when the fingerprint module is replaced, the serial number changes, thus affecting the decoding process of the encrypted data. By verifying the decoding result, information on whether the current fingerprint module matches the current calibration file can be obtained. This calibration file management method avoids the risk of forgetting to update the calibration file when replacing the fingerprint module, solves the problem of mismatch between the new fingerprint module and the old calibration file in existing technologies, and addresses the security issues that may arise from this mismatch; it also enhances the applicability of the calibration data and ensures optimal noise reduction capability of the calibration benchmark. Attached Figure Description
[0019] Those skilled in the art will understand that the accompanying drawings are provided to better understand the invention and do not constitute any limitation on the scope of the invention. Wherein:
[0020] Figure 1 This is a flowchart illustrating a calibration file management method according to an embodiment of the present invention;
[0021] Figure 2 This is a data structure diagram of a calibration file according to an embodiment of the present invention;
[0022] Figure 3 This is a flowchart illustrating a power-on sub-method according to an embodiment of the present invention;
[0023] Figure 4 This is a schematic flowchart of a calibration sub-method according to an embodiment of the present invention.
[0024] in:
[0025] 1-Calibration file; 2-File header; 3-Plaintext data; 4-Ciphertext data; 5-Data body; 6-Second checksum; 7-Second hash value. Detailed Implementation
[0026] To make the objectives, advantages, and features of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that the drawings are all in a very simplified form and are not drawn to scale, and are only used to facilitate and clarify the explanation of the embodiments of this invention. Furthermore, the structures shown in the drawings are often part of the actual structures. In particular, different figures may emphasize different aspects and may sometimes use different scales.
[0027] As used in this invention, the singular forms “a,” “an,” and “the” include plural objects; the term “or” is generally used to mean “and / or”; the term “a number” is generally used to mean “at least one”; and the term “at least two” is generally used to mean “two or more”. Furthermore, the terms “first,” “second,” and “third” are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined as “first,” “second,” or “third” may explicitly or implicitly include one or at least two of that feature. “One end” and “the other end,” as well as “proximal end” and “distal end,” generally refer to two corresponding parts, including not only endpoints. The terms “installed,” “connected,” and “joined” should be interpreted broadly, for example, as a fixed connection, a detachable connection, or an integral part; a mechanical connection or an electrical connection; a direct connection or an indirect connection through an intermediate medium; or a connection within two elements or an interaction between two elements. Furthermore, as used in this invention, the phrase "one element is disposed on another element" generally only indicates that there is a connection, coupling, cooperation, or transmission relationship between the two elements, and the connection, coupling, cooperation, or transmission between the two elements can be direct or indirect through an intermediate element. It should not be construed as indicating or implying a spatial positional relationship between the two elements, i.e., one element can be located arbitrarily inside, outside, above, below, or to one side of the other element, unless otherwise explicitly stated. Those skilled in the art can understand the specific meaning of the above terms in this invention according to the specific circumstances.
[0028] The core idea of this invention is to provide a calibration file management method to solve the problem of mismatch between new fingerprint modules and old calibration files in the prior art, as well as the security problems that may be caused by the mismatch.
[0029] The following description refers to the accompanying drawings.
[0030] Please refer to Figure 1 This embodiment provides a calibration file management method for managing calibration files, which are applied to fingerprint modules. The calibration file management method includes a power-on sub-method S100 and a calibration sub-method S200.
[0031] In a preferred embodiment, the power-on sub-method includes:
[0032] S101, Obtain the serial number of the fingerprint chip. The fingerprint chip belongs to the fingerprint module.
[0033] S102, calculate the calibration file key based on the serial number; wherein, when the serial number is different, the calculated calibration file key is different.
[0034] S103, calculate the first hash value of the sequence number.
[0035] S104, Obtain the second hash value from the calibration file.
[0036] S105, compare the first hash value and the second hash value. If they are the same, proceed to the next step; otherwise, determine that the calibration file is invalid and skip the next step.
[0037] S106, Obtain the encrypted data in the calibration file, the encrypted data being generated and stored based on the calibration sub-method.
[0038] S107, Decode the ciphertext data based on the calibration file key to obtain plaintext data.
[0039] S108, the first check code is calculated based on the data subject.
[0040] S109, compare whether the first check code and the second check code are the same, and use the judgment result to participate in the generation of a verification result for the final validity judgment. For example, the judgment result can be directly used as the verification result; the judgment result can be used as part of the verification result; or the judgment result can be used in a specific logical judgment algorithm to obtain the verification result. Specifically, if they are the same, the verification is judged to pass; otherwise, the verification is judged to fail.
[0041] Steps S108 and S109 can also be understood as steps to verify the plaintext data.
[0042] For easier understanding, please refer to Figure 2In this embodiment, the calibration file 1 includes a file header 2 and encrypted data 4. The file header 2 includes the second hash value 7 and also includes: a version number, a random checksum, the calibration file key, calibration parameters (chip exposure time, exposure register value, and noise reduction parameters calculated by the algorithm), etc. The encrypted data 4 can be decrypted to obtain the plaintext data 3. The plaintext data 3 and the encrypted data 4 are converted through encryption and decryption. The plaintext data 3 includes a data body 5 and the second checksum 6. The data body 5 is configured according to the industry standard for fingerprint module calibration files, currently set to three calibration images: 1) an image captured by the flesh-colored rubber tip under high screen brightness, 2) an image captured by the black rubber tip under high screen brightness, and 3) an image captured by the black rubber tip under normal screen brightness. The specific acquisition, calculation, storage, data format, and operating logic can be understood by referring to industry standards in this field. When industry standards change subsequently, the data body 5 in this embodiment can also change accordingly.
[0043] It is understood that the above description is a detailed solution of a preferred embodiment of the present invention. In other embodiments, the steps of the power-on sub-method can be omitted. For example, the first hash value, the second hash value, and steps S103 to S105 may not be set to adapt to application requirements in different situations. In this case, the data structure of the calibration file will also change accordingly.
[0044] Please continue to refer to this. Figure 1 The calibration sub-method includes:
[0045] S201, Obtain the serial number.
[0046] S202, calculate the calibration file key based on the serial number; wherein, when the serial number is different, the calculated calibration file key is different.
[0047] S203, the fingerprint module acquires multiple images under preset environmental conditions and determines whether they meet the conditions of the reference image. If they do, the data subject is set based on the acquired images; otherwise, the images are repeatedly acquired until they meet the conditions of the reference image.
[0048] S204, a second check code is calculated based on the data body, and the data body and the second check code are jointly used to perform symmetric encryption operation based on the calibration file key to obtain the ciphertext data.
[0049] S205, a second hash value is calculated based on the calibration file key, and the ciphertext data and the second hash value are configured together as components of the calibration file.
[0050] S206, construct the calibration file based on the encrypted data and store it in a preset directory.
[0051] It is understood that the order of steps that are not logically related in the above power-on sub-method and calibration sub-method can be changed. For example, in step S205, the calculation of the second hash value based on the calibration file key can also be performed before the symmetric encryption operation.
[0052] In other embodiments, the steps of the calibration sub-method can be adaptively omitted based on the omission of the power-on sub-method steps.
[0053] Please refer to Figure 3 In a specific embodiment, the power-on sub-method includes: S1, powering on; S2, obtaining the serial number, the ID of the fingerprint chip, and the software-specified code, and generating the calibration file key; S3, determining whether a calibration file exists; if not, proceeding to step S8; if so, proceeding to step S4; S4, verifying the hash value and decrypting it using the calibration file key; S5, verifying the validity of the decrypted data; if valid, proceeding to step S6; otherwise, if invalid, proceeding to step S7; S6, loading calibration data and enabling the fingerprint function; S7, disabling the fingerprint function; S8, disabling the fingerprint function.
[0054] In other words, in one embodiment, the power-on sub-method further includes: obtaining the ID of the fingerprint chip and a software-specified code. The calibration file key is calculated based on the serial number, the ID, and the software-specified code.
[0055] In different schemes, the result of directly concatenating the three elements can be used as the calibration file key, or the ID and the software-specified code can be concatenated to obtain an intermediate string, and the intermediate string and the serial number can be subjected to a first logical operation to obtain the calibration file key. The first logical operation can be selected from calculations such as bitwise AND, bitwise OR, bitwise XOR, bitwise NAND, bitwise NOR, and accumulation. The bit length of the calculation result obtained from the first logical operation can be adaptively set according to the rules of the first operation logic.
[0056] In a preferred embodiment, the calibration file key is obtained by XORing the intermediate string and the serial number. This configuration makes the obtained calibration file key more random and unpredictable in real-world scenarios, thereby increasing system security. In this embodiment, the calibration file key is 64 bits long (the serial number is 64 bits, the ID is 32 bits, and the software-specified encoding is 32 bits).
[0057] In one embodiment, if obtaining the calibration file fails, an error message is displayed and / or the fingerprint module is disabled. Displaying an error message is similar to a pop-up notification in the system prompting the user to actively replace the calibration file. Disabling the fingerprint module, on higher-security products, prevents authentication failures due to incorrect calibration files or allows unauthorized users to successfully authenticate. Specific combinations of solutions can be configured according to actual needs and will not be described in detail here.
[0058] The purpose of setting step S105 is that if the calibration file is determined to be mismatched by the hash value, subsequent steps can be skipped, thereby reducing the workload of the relevant computing units and saving time in most cases.
[0059] The first hash value and the second hash value can be calculated using any hashing method, such as MD5, SHA-1, SHA-2, SHA-256, etc.
[0060] In a preferred embodiment, the calculation steps for the first hash value and the second hash value are as follows: the calibration file key is split according to a first bit length and subjected to a second logical operation. The resulting calculation is configured as either the first hash value or the second hash value. For example, splitting it into 8-bit segments and accumulating the results yields a 16-bit length. In other embodiments, the length of the result can be adaptively set according to the rules of the second logical operation. The second logical operation can also be selected from bitwise AND, bitwise OR, bitwise XOR, bitwise NAND, bitwise NOR, etc. This configuration simplifies the calculation steps while ensuring that hash values are less likely to collide, providing a prerequisite for the implementation of this method entirely or partially through simple logic circuits, and also saving the computational burden on computing modules such as MCUs.
[0061] The calculation methods for the first and second check codes can be selected according to actual needs. In a preferred embodiment, the calculation steps for the first and second check codes include: splitting the data body according to a second bit length, performing a third logical operation, and configuring the calculation result as either the first or the second check code. For example, splitting the data body into 4 bytes (32 bits), accumulating the results, and retaining only the 32-bit data of the calculation result. In other embodiments, the complete calculation result may not be truncated, and the length of the calculated result may be 64 bits or longer. In other embodiments, the length of the calculation result can be adaptively set according to the rules of the third logical operation. The third logical operation can also be selected from bitwise AND, bitwise OR, bitwise XOR, bitwise NAND, bitwise NOR, etc. This configuration comprehensively considers both computational complexity and the effectiveness of the verification code.
[0062] In step S109, after obtaining the verification result, the verification result is used to participate in the final validity judgment. For example, the verification result can be directly used as the result of the validity judgment; the verification result can be used as an input parameter for the validity judgment, etc. After obtaining the validity judgment result, the specific subsequent operations can also be set according to actual needs. For example, if the calibration file is invalid, you can choose to prompt an error, disable the fingerprint function, or immediately start the calibration sub-method; or a combination of the above schemes.
[0063] Please refer to Figure 4 The calibration sub-method includes: S11, powering on; S12, obtaining the serial number, the ID of the fingerprint chip, and the software-specified code, and generating the calibration file key; S13, determining whether to start the calibration process; if not, ending the process; otherwise, proceeding to step S14; S14, determining the calibration result, corresponding to step S203. If the calibration is successful, proceeding to step S15; otherwise, ending the process; S15, calculating and generating the calibration file and saving it.
[0064] The first hash value and the second hash value are calculated in the same way. The difference in naming is only to distinguish which sub-method is used to calculate them. The first check code and the second check code are also understood in the same way.
[0065] In step S203, the fingerprint module acquires multiple images under different environmental conditions or different acquisition conditions, and determines whether they meet the conditions of the reference image. For example, different ambient temperatures or screen brightness, different materials or patterns can be used to cover the corresponding acquisition head or lens, or an acquisition object with color difference can be selected. n images can be acquired, or n images can be acquired and merged into one. Based on the data of the acquired images, it is determined whether they meet expectations. For example, it can determine the average grayscale value, the distribution of grayscale values, the distribution and number of grayscale extreme values, etc.
[0066] In step S204, the symmetric encryption operation can also select any encryption algorithm, such as DES, 3DES, AES, or a self-developed encryption algorithm.
[0067] Specifically, after successful calibration, the calibration data is synchronously transmitted to the device. Therefore, it is not necessary to execute the boot sub-method again upon successful calibration; the boot sub-method is only required when restarting the device. Furthermore, if a subsequent successful calibration is performed, the data from the last successful calibration will be saved, overwriting the previous calibration data. No data is saved upon calibration failure.
[0068] In summary, this embodiment provides a calibration file management method. The calibration file management method includes a power-on sub-method, which includes: obtaining the serial number of the fingerprint chip; calculating a calibration file key based on the serial number; wherein, the calculated calibration file key is different when the serial number is different; obtaining encrypted data in the calibration file, the encrypted data being generated and stored based on the calibration sub-method; decoding the encrypted data based on the calibration file key to obtain plaintext data; and verifying the plaintext data, the verification result being used in the final validity judgment. With this configuration, when the fingerprint module is replaced, the serial number changes, thus affecting the decoding process of the encrypted data. By verifying the decoding result, information on whether the current fingerprint module matches the current calibration file can be obtained. This calibration file management method avoids the risk of forgetting to update the calibration file when replacing the fingerprint module, solves the problem of mismatch between the new fingerprint module and the old calibration file in the prior art, and addresses the security issues that may arise from this mismatch; it also enhances the applicability of the calibration data and ensures optimal noise reduction capability of the calibration benchmark.
[0069] The above description is only a description of preferred embodiments of the present invention and is not intended to limit the scope of the present invention in any way. Any changes or modifications made by those skilled in the art based on the above disclosure shall fall within the protection scope of the present invention.
Claims
1. A calibration file management method, characterized in that, The calibration file management method is used to manage calibration files applied to fingerprint modules. The calibration file management method includes a power-on sub-method and a calibration sub-method. The power-on sub-method includes: Obtain the serial number of the fingerprint chip; the fingerprint chip belongs to the fingerprint module; The calibration file key is calculated based on the serial number; wherein, different serial numbers result in different calculated calibration file keys. Obtain the encrypted data from the calibration file, the encrypted data being generated and stored based on the calibration sub-method; The ciphertext data is decoded based on the calibration file key to obtain plaintext data; and, The plaintext data is verified, and the verification result is used in the final validity determination.
2. The calibration document management method according to claim 1, characterized in that, The power-on sub-method further includes: obtaining the ID of the fingerprint chip and the software-specified code; The step of calculating the calibration file key based on the serial number includes: concatenating the serial number, the ID, and the software-specified encoding to obtain the calibration file key; Alternatively, the step of calculating the calibration file key based on the serial number includes: concatenating the ID and the software-specified encoding to obtain an intermediate string; and performing a first logical operation on the intermediate string and the serial number to obtain the calibration file key.
3. The calibration file management method according to claim 2, characterized in that, The steps for calculating the calibration file key based on the serial number include: concatenating the ID and the software-specified encoding to obtain an intermediate string; and XORing the intermediate string and the serial number to obtain the calibration file key.
4. The calibration document management method according to claim 1, characterized in that, The power-on sub-method further includes: if obtaining the calibration file fails, displaying an error message and / or disabling the fingerprint module.
5. The calibration document management method according to claim 1, characterized in that, Before decoding the encrypted data based on the calibration file key, the power-on sub-method further includes: Calculate the first hash value of the sequence number; Obtain the second hash value from the calibration file; and, Compare the first hash value and the second hash value. If they are the same, proceed to the next step; otherwise, determine that the calibration file is invalid and skip the next step. The first hash value is calculated based on the calibration file key obtained by the boot sub-method; the second hash value is calculated based on the calibration file key obtained by the calibration sub-method.
6. The calibration document management method according to claim 5, characterized in that, The calculation steps for the first hash value and the second hash value are as follows: The calibration file key is split according to the first bit length and subjected to the second logical operation. The result of the calculation is configured as either the first hash value or the second hash value.
7. The calibration document management method according to claim 1, characterized in that, The steps for verifying the plaintext data include: The first checksum is calculated based on the data subject; and, Compare whether the first check code and the second check code are the same, and the result is used to generate the check result. The plaintext data includes the data body and a second check code, the second check code being generated based on the calibration sub-method.
8. The calibration document management method according to claim 7, characterized in that, The calculation steps for the first check code and the second check code include: The data body is split according to the second bit length and subjected to the third logical operation. The result of the calculation is configured as the first check code or the second check code.
9. The calibration document management method according to claim 1, characterized in that, The calibration sub-method includes: Obtain the serial number; The calibration file key is calculated based on the serial number; wherein, different serial numbers result in different calculated calibration file keys. The fingerprint module acquires multiple images under preset environmental conditions and determines whether they meet the conditions of the reference image. If they do, the data subject is set based on the acquired images; otherwise, the images are acquired repeatedly until they meet the conditions of the reference image. The data body performs symmetric encryption based on the calibration file key to obtain the ciphertext data; and, The calibration file is constructed based on the encrypted data and stored in a preset directory.
10. The calibration document management method according to claim 9, characterized in that, The step of obtaining the ciphertext data by performing symmetric encryption operation on the data body based on the calibration file key includes: calculating a second check code based on the data body; and performing symmetric encryption operation on the data body and the second check code together based on the calibration file key to obtain the ciphertext data. The step of constructing the calibration file based on the ciphertext data includes: calculating a second hash value based on the calibration file key, wherein the ciphertext data and the second hash value are configured together as components of the calibration file; Before decoding the encrypted data based on the calibration file key, the power-on sub-method further includes: calculating a first hash value of the serial number; obtaining a second hash value from the calibration file; and comparing the first hash value and the second hash value. If they are the same, proceed to the next step; otherwise, determine that the calibration file is invalid and skip the next step. The steps for verifying the plaintext data include: calculating a first checksum based on the data subject; and comparing whether the first checksum and the second checksum are the same, with the result used to generate the verification result.
