Vehicle filling certificate key file verification system, method, electronic equipment and vehicle

The multi-stage verification mechanism addresses the shortcomings in the vehicle certificate key file loading and verification process, ensuring vehicle information security and verifying the integrity, validity, and matching of the certificate key file, thereby ensuring the security of vehicle communication with external parties.

CN123122846APending Publication Date: 2026-11-17CHONGQING CHANGAN TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611525934.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-29
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In existing technologies, the loading and verification of vehicle certificate key files only involves a one-time or simple verification, which fails to detect problems with the certificate key files, leading to potential risks to vehicle information security.

Method used

A multi-stage verification mechanism is adopted, including local hash verification, certificate key matching verification, and certificate key vehicle matching verification. The certificate key management verification module of the vehicle domain controller performs multi-stage verification through the cloud certificate issuance server to ensure the integrity, validity and matching of the certificate key file.

Benefits of technology

It achieves full lifecycle coverage verification of certificate key files, discovers and handles potential problems, ensures the security of vehicle communication with the outside world, and avoids information leakage and communication failure.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123122846A_ABST
    Figure CN123122846A_ABST
Patent Text Reader

Abstract

This invention relates to a vehicle certificate key file verification system, method, electronic device, and vehicle, comprising: a cloud certificate issuance server configured to generate a vehicle certificate key file; performing hash calculation on the certificate key file to obtain a hash checksum; sending the certificate key file and the hash checksum as a certificate key pair to a production line certificate key filling device; the production line certificate key filling device configured to store the certificate key pair as a local certificate key pair in each domain controller; and a certificate key management and verification module configured to obtain verification instructions and perform multi-stage verification based on the local certificate key pair and the certificate key pair; the multi-stage verification includes multiple verification stages executed sequentially, and the verification instructions include a verification scenario identifier, which corresponds to at least one verification stage; the verification instructions are sent by the production line certificate key filling device or generated locally. This invention ensures vehicle information security.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of vehicle information security technology, specifically to a vehicle certificate key file verification system, method, electronic device, and vehicle. Background Technology

[0002] With the continuous improvement of the electrification, intelligence and connectivity of automobiles, automobiles have become a comprehensive application of big data, vehicle networking, multi-dimensional sensors, artificial intelligence and new communication technologies represented by 4G / 5G and intelligent terminals.

[0003] During production, verification, and after-sales use, vehicles require extensive communication and interaction with external systems, carrying increasing amounts of user privacy data, vehicle driving data, and control command information. This includes tasks such as uploading vehicle diagnostic information to the cloud, uploading intelligent driving information to the cloud, remote vehicle control, and intelligent parking. Against this backdrop, automotive information security and data security have become crucial issues that the industry must collectively address. Among these, the vehicle's certificate key file is fundamental to ensuring secure communication between the vehicle and external systems.

[0004] However, currently, in the process of loading and verifying vehicle certificate key files, only a one-time or simple verification is performed on the certificate key file, which fails to detect any problems. This leads to potential risks to vehicle information security when the vehicle uses the certificate key file to communicate with the outside world. Summary of the Invention

[0005] One objective of this invention is to provide a vehicle certificate key file verification system to address the current problem that, in the process of installing and verifying vehicle certificate key files, only a one-time or simple verification is usually performed, which fails to detect problems in the certificate key file and leads to potential information security risks when the vehicle uses the certificate key file to communicate with the outside world. A second objective is to provide a vehicle certificate key file verification method. A third objective is to provide an electronic device. A fourth objective is to provide a vehicle.

[0006] To achieve the above objectives, the technical solution adopted by the present invention is as follows: A vehicle certificate key file verification system, the system comprising a cloud certificate issuance server, production line certificate key filling equipment, and certificate key management and verification modules for each domain controller in the vehicle: The cloud certificate issuing server is configured to generate a certificate key file for the vehicle; perform a hash calculation on the certificate key file to obtain a hash checksum; and send the certificate key file and the hash checksum as a certificate key pair to the production line certificate key filling equipment. The production line certificate key filling device is configured to fill the certificate key pair as a local certificate key pair into each of the domain controllers; The certificate key management verification module is configured to obtain a verification instruction and perform multi-stage verification based on the local certificate key pair and the certificate key pair; the multi-stage verification includes multiple verification stages executed sequentially, the verification instruction includes a verification scenario identifier, and the verification scenario identifier has at least one corresponding verification stage; the verification instruction is sent by the production line certificate key filling device or generated locally.

[0007] A method for verifying vehicle certificate key files is provided, applied to a vehicle certificate key file verification system. The system includes a cloud-based certificate issuance server, a production line certificate key file installation device, and certificate key management and verification modules for each domain controller within the vehicle. The cloud-based certificate issuance server is configured to generate vehicle certificate key files. A hash checksum is obtained by hashing the certificate key file. The certificate key file and the hash checksum are sent as a certificate key pair to the production line certificate key file installation device. The production line certificate key file installation device is configured to install the certificate key pair as a local certificate key pair to each of the domain controllers. The method includes: Obtain the verification command; A multi-stage verification is performed based on the local certificate key pair and the certificate key pair; the multi-stage verification includes multiple verification stages executed sequentially, the verification instruction includes a verification scenario identifier, and the verification scenario identifier has at least one corresponding verification stage; the verification instruction is sent by the production line certificate key filling device or generated locally.

[0008] An electronic device includes: a processor; and a memory for storing processor-executable instructions. The processor is configured to execute the instructions to implement the vehicle filling certificate key file verification method described above.

[0009] A computer-readable storage medium, when the instructions in the storage medium are executed by the processor of a mobile terminal, enables the mobile terminal to perform the above-described vehicle filling certificate key file verification method.

[0010] A vehicle comprising the aforementioned electronic equipment.

[0011] The beneficial effects of this invention are: In this embodiment of the invention, the vehicle certificate key file verification system may include a cloud certificate issuance server, a production line certificate key filling device, and certificate key management and verification modules for each domain controller in the vehicle. The cloud certificate issuance server is configured to generate vehicle certificate key files and perform hash calculations to obtain hash verification codes. The certificate key file and hash verification codes are then sent as a certificate key pair to the production line certificate key filling device. The production line certificate key filling device can store the certificate key pair as a local certificate key pair in each domain controller of each vehicle. When the domain controller's certificate key management and verification module receives a verification command sent by the production line certificate key filling device or generated locally, it performs multi-stage verification based on the local certificate key pair and the certificate key file. The multi-stage verification may include sequentially executed verification stages such as local hash verification, certificate key matching verification, and certificate key vehicle matching verification. The verification command may include a verification scenario identifier, which corresponds to at least one verification stage. Since multiple verification stages cover the entire lifecycle of the certificate key file, problems with the certificate key file can be detected and addressed accordingly. Thus, the vehicle can use the certificate key file to communicate securely with the outside world, ensuring vehicle information security. Attached Figure Description

[0012] Figure 1 This is a schematic diagram of a vehicle filling certificate key file verification system provided in an embodiment of the present invention; Figure 2 This is a diagram illustrating the architecture of a vehicle-side filling certificate key lifecycle verification system provided in this embodiment of the invention. Figure 3 This is a flowchart illustrating a multi-stage, multi-domain control verification process for a vehicle-side certificate key management and verification module provided in this embodiment of the invention. Figure 4 This is a flowchart of an adaptive switching verification process for the vehicle-side master domain controller provided in an embodiment of the present invention; Figure 5 This invention provides an automatic or proactive multi-stage, multi-domain control verification process for users and after-sales service. Figure 6 This is a flowchart illustrating the steps of a vehicle filling certificate key file verification method provided in an embodiment of the present invention; Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0013] The embodiments of the present invention will be described below with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. It should be understood that the preferred embodiments are only for illustrating the present invention and not for limiting the scope of protection of the present invention.

[0014] It should be noted that the embodiments of the present invention may involve the use of user data. In practical applications, user-specific personal data may be used in the scheme described herein within the scope permitted by applicable laws and regulations, provided that it complies with the applicable laws and regulations of the country (e.g., with the user's explicit consent, with the user being properly notified, etc.).

[0015] Reference Figure 1 The diagram shows a structural schematic of a vehicle filling certificate key file verification system provided in an embodiment of the present invention. The system includes a cloud certificate issuance server 101, a production line certificate key filling device 102, and a certificate key management and verification module 103 for each domain controller in the vehicle.

[0016] The cloud certificate issuing server 101 is configured to generate a certificate key file for the vehicle; perform a hash calculation on the certificate key file to obtain a hash check code; and send the certificate key file and the hash check code as a certificate key pair to the production line certificate key filling device.

[0017] In this embodiment of the invention, the cloud-based certificate issuance server is the authoritative issuing center for certificate key files, responsible for generating, issuing, and managing vehicle certificate key files. The certificate key files may include unique public key certificates, private key files, and intermediate certificate chains for each domain controller of the vehicle. Specifically, when generating the certificate key files, the cloud-based certificate issuance server can perform hash calculations on the certificate key files using a preset hash algorithm to obtain a hash checksum. This hash checksum can be used to verify the integrity of the certificate key files. Subsequently, the certificate key files and the hash checksum can be used as a certificate key pair and sent to the production line certificate key filling equipment through a secure channel.

[0018] The production line certificate key filling device 102 is configured to fill the certificate key pair as a local certificate key pair into each of the domain controllers.

[0019] In this embodiment of the invention, the production line certificate key filling device is responsible for writing the certificate key pairs sent by the cloud certificate issuance server into each domain controller of the vehicle and triggering the verification process. Specifically, the certificate key pairs can be filled into the local storage directory of the certificate key management and verification module of each domain controller as local certificate key pairs through the vehicle diagnostic interface. Subsequently, filling completion and start verification commands can be sent to the certificate key management and verification module to trigger the certificate key management and verification module to perform multi-stage verification.

[0020] The certificate key management verification module 103 is configured to obtain a verification instruction and perform multi-stage verification based on the local certificate key pair and the certificate key pair; the multi-stage verification includes multiple verification stages executed sequentially, the verification instruction includes a verification scenario identifier, and the verification scenario identifier has at least one corresponding verification stage; the verification instruction is sent by the production line certificate key filling device or generated locally.

[0021] In this embodiment of the invention, the vehicle may include multiple domain controllers. Specifically, a domain controller is a unit in the vehicle that is responsible for functional domains such as intelligent driving domain, cockpit domain, and power domain. It has independent computing and storage capabilities, and each domain controller can communicate with each other.

[0022] The domain controller's certificate key management and verification module can receive verification instructions, which carry a verification scenario identifier. The verification scenario identifier may include at least one of the following: production line filling verification scenario identifier, user and after-sales verification scenario identifier.

[0023] In one embodiment of the present invention, a verification instruction including a production line filling verification scenario identifier is generated when the production line certificate key filling device fills the certificate key pair as a local certificate key pair into each domain controller and sends it to the certificate key management verification module. A verification instruction including a user and after-sales verification scenario identifier is generated when the certificate key management verification module detects a vehicle power-on event or when the vehicle's infotainment interface is triggered. For example, after a user starts the vehicle, the certificate key management verification module will detect the vehicle power-on event, at which time it can trigger the generation of a verification instruction including a user and after-sales verification scenario identifier. Alternatively, after-sales personnel can actively click the "Certificate Status Query" function on the infotainment interface to trigger the generation of a verification instruction including a user and after-sales verification scenario identifier.

[0024] Subsequently, the certificate key management verification module can perform multi-stage verification based on verification instructions, using the locally stored local certificate key pair and the certificate key pair from the cloud certificate issuing server. This multi-stage verification can include multiple verification phases, such as local hash verification (first-stage verification), certificate key matching verification (second-stage verification), and certificate key-vehicle matching verification (third-stage verification). These phases are executed sequentially, with the next phase only proceeding after the previous one has passed. It's important to note that different verification scenario identifiers require different verification phases. For example, the production line filling verification scenario requires all verification phases, while the user and after-sales verification scenario only requires certificate key matching verification and certificate key-vehicle matching verification.

[0025] After successful verification in multiple verification stages, the certificate key management verification module can determine that the current certificate key file is secure and usable, and the vehicle can subsequently use the certificate key file to communicate securely with the outside world.

[0026] In this embodiment of the invention, the vehicle certificate key file verification system may include a cloud certificate issuance server, a production line certificate key filling device, and certificate key management and verification modules for each domain controller in the vehicle. The cloud certificate issuance server is configured to generate vehicle certificate key files and perform hash calculations to obtain hash verification codes. The certificate key file and hash verification codes are then sent as a certificate key pair to the production line certificate key filling device. The production line certificate key filling device can store the certificate key pair as a local certificate key pair in each domain controller of each vehicle. When the domain controller's certificate key management and verification module receives a verification command sent by the production line certificate key filling device or generated locally, it performs multi-stage verification based on the local certificate key pair and the certificate key file. The multi-stage verification includes sequentially executed verification stages such as local hash verification, certificate key matching verification, and certificate key vehicle matching verification. The verification command may include a verification scenario identifier, which corresponds to at least one verification stage. Since multiple verification stages cover the entire lifecycle of the certificate key file, problems with the certificate key file can be detected and addressed accordingly. Thus, the vehicle can use the certificate key file to communicate securely with the outside world, ensuring vehicle information security.

[0027] In one embodiment of the present invention, the certificate key management and verification module is configured as follows: When the verification scenario identifier in the verification instruction is the production line filling verification scenario identifier, the local hash verification, the certificate key matching verification, and the certificate key vehicle matching verification are executed sequentially. When the verification scenario identifier in the verification instruction is a user and an after-sales verification scenario identifier, the certificate key matching verification and the certificate key vehicle matching verification are executed sequentially.

[0028] In this embodiment of the invention, after receiving a verification instruction, the certificate key management verification module determines the current verification scenario based on the verification scenario identifier carried in the verification instruction, and then determines the verification stage to be executed.

[0029] Specifically, when the verification scenario is identified as the production line filling verification scenario, it indicates that the vehicle is currently in the production line filling stage. The certificate key file has just been filled into the various domain controllers of the vehicle and needs to be fully verified. Therefore, the three verification stages—local hash verification, certificate key matching verification, and certificate key vehicle matching verification—are executed sequentially. When the verification scenario is identified as the user and after-sales verification scenario, it indicates that the vehicle is currently in the user's daily use or after-sales maintenance stage. Since the local hash verification is completed during the production line filling stage, and the certificate key file is usually not damaged or tampered with after filling, to improve verification efficiency, the local hash verification can be skipped, and only the certificate key matching verification and certificate key vehicle matching verification stages are executed sequentially. In this way, the verification effect can be guaranteed while reducing user waiting time, thereby ensuring user experience. In the user and after-sales scenarios, both automatic and manual triggering modes are supported to trigger multi-stage verification to adapt to different usage needs.

[0030] In one embodiment of the present invention, the local certificate key pair includes a local certificate key file; the certificate key management and verification module is configured to: When performing the local hash verification, the local certificate key file is hashed to obtain the local hash verification code; When the local hash check code matches the hash check code, the local hash check is determined to be successful. If the local hash check code is inconsistent with the hash check code, it is determined that the local hash check has failed.

[0031] In this embodiment of the invention, the local certificate key pair may include a local certificate key file. When performing local hash verification, the domain controller's certificate key management and verification module performs hash calculation on the local certificate key file to obtain a local hash verification code, and compares this local hash verification code with the hash verification code of the cloud certificate issuing server. If they match, the local hash verification is considered successful; if they do not match, the local hash verification is considered to have failed. Since the local hash verification can be completed locally on the domain controller without communication with the cloud certificate issuing server, and it can promptly detect whether the certificate key file has been damaged or tampered with during the installation process, it ensures that the certificate key file installed on the domain controller is consistent with the certificate key file on the cloud certificate issuing server, thus guaranteeing the integrity of the certificate key file.

[0032] In one embodiment of the present invention, the certificate key management and verification module is configured as follows: When performing the certificate key matching verification, a two-way authentication secure connection is established between the local certificate key file and the cloud certificate issuing server. When the two-way authentication secure connection is successfully established, it is determined that the certificate key matching verification is successful; When the establishment of the two-way authentication secure connection fails, it is determined that the certificate key matching verification has failed.

[0033] In this embodiment of the invention, when performing certificate key matching verification, the certificate key management and verification module establishes a two-way authentication secure connection with the cloud certificate issuing server through the local certificate key file. If the two-way authentication secure connection is successfully established, the certificate key matching verification is considered successful; if the two-way authentication secure connection fails to be established, the certificate key matching verification is considered to have failed. Because the certificate key file is verified for forgery and validity by communicating with the cloud certificate issuing server, the validity of the certificate key file is ensured, preventing communication failures due to expired or forged certificate key files. Furthermore, since the certificate key matching verification is performed after the local hash verification is successful, the certificate key file participating in the verification is guaranteed to be complete, preventing invalid verification due to damaged or tampered certificate key files, thus saving network resources.

[0034] In one embodiment of the present invention, the certificate key management and verification module is configured as follows: When performing the certificate key vehicle matching verification, the vehicle identification number of the vehicle and the certificate verification information of each domain controller of the vehicle are obtained; the certificate verification information includes the local hash verification code of each domain controller. The vehicle identification code and the certificate verification information are sent to the cloud certificate issuing server through the successfully established two-way authentication secure connection. The cloud certificate issuing server obtains the hash verification code corresponding to the vehicle identification code and compares the local hash verification code with the hash verification code to obtain the comparison result. Receive the comparison result sent by the cloud certificate issuing server; When the comparison result shows that the local hash check code matches the hash check code, it is determined that the certificate key vehicle matching verification is successful. If the comparison result shows that the local hash check code is inconsistent with the hash check code, it is determined that the certificate key vehicle matching verification has failed.

[0035] In this embodiment of the invention, when performing certificate key vehicle matching verification, the certificate key management verification module can obtain the vehicle identification number (VIN) or other identifiers that can uniquely identify the vehicle, as well as the certificate verification information of each domain controller of the vehicle. The certificate verification information may include the local hash checksum of each domain controller. Subsequently, the vehicle identification number and certificate verification information are sent to the cloud certificate issuing server through a successfully established two-way authentication secure connection. The cloud certificate issuing server can then query the hash checksum corresponding to the vehicle identification number in its database, compare this hash checksum with the local hash checksum, obtain the comparison result, and send it to the certificate key management verification module. If the comparison result shows that the local hash checksum matches the local hash checksum, the certificate key vehicle matching verification is considered successful; if the comparison result shows that the local hash checksum does not match the local hash checksum, the certificate key vehicle matching verification is considered unsuccessful. By comparing the vehicle identification number (VIN) with the local hash checksum of each domain controller via a cloud-based certificate issuance server, it can be determined whether the certificate key file is associated with the vehicle's unique VIN. This establishes a closed-loop verification process: the certificate key file is sent from the cloud certificate issuance server to the vehicle, and the verification is performed using the certificate key file against the cloud certificate issuance server. Furthermore, since verification is achieved by transmitting the checksum hash instead of the certificate key file, the leakage of security information is effectively prevented.

[0036] In one embodiment of the present invention, the domain controller includes a primary domain controller, which establishes a two-way authentication secure connection with the cloud certificate issuing server through the certificate key management and verification module of the primary domain controller, and sends the certificate verification information to the cloud certificate issuing server through the successfully established two-way authentication secure connection; the certificate key management and verification module of the primary domain controller is configured to: If the local hash verification fails or the certificate key matching verification fails, the target domain controller is determined by traversing the preset domain controller order configuration table. Send the verification instruction to the certificate key management verification module of the target domain controller to re-execute the local hash verification and the certificate key matching verification through the target domain controller; When both the local hash verification and the certificate key matching verification are successful, the target domain controller is designated as the new primary domain controller, and the certificate key vehicle matching verification is performed through the certificate key management verification module of the new primary domain controller. If the local hash verification fails or the certificate key matching verification fails, and the preset domain controller sequence configuration table has been traversed, then the multi-stage verification is determined to have failed.

[0037] In this embodiment of the invention, the domain controller on the vehicle may include a master domain controller. The certificate key management and verification module of the master domain controller is responsible for establishing a two-way authentication secure connection with the cloud certificate issuance server and sending verification information to the cloud certificate issuance server through the two-way authentication secure connection.

[0038] A preset domain controller sequence configuration table can be pre-stored in the vehicle. This table stores the identifiers of domain controllers that can serve as primary domain controllers. When the primary domain controller's local hash verification or certificate key matching verification fails, the primary domain controller can traverse the preset domain controller sequence configuration table to determine the target domain controller and send a verification command to the target domain controller's certificate key management verification module. The target domain controller then re-executes the local hash verification and certificate key matching verification stages. If both verification stages are successful, the target domain controller can be designated as the new primary domain controller, and the new primary domain controller will perform the certificate key vehicle matching verification. If both verification stages fail, the system continues to traverse the next domain controller in the preset domain controller sequence configuration table as the target domain controller, until the target domain controller can complete both the local hash verification and certificate key matching verification stages, or the entire preset domain controller sequence configuration table has been traversed.

[0039] If, after traversing the entire preset domain controller sequence configuration table, a target domain controller that can serve as the primary domain controller still cannot be found, then the multi-stage verification has failed. Since this embodiment of the invention allows unified communication between the primary domain controller and the cloud certificate issuance server, it eliminates the need for each domain controller to communicate separately with the cloud certificate issuance server. Because only the primary domain controller needs to perform certificate key matching verification and certificate key vehicle matching verification, the number of connection verifications to the cloud certificate issuance server (which is twice the number of domain controllers) can be reduced to a maximum of two. This significantly reduces network resource consumption, decreases the complexity of vehicle-side network management, improves system stability, and avoids the problem of overall verification failure due to mismatched certificate key files of a single domain controller.

[0040] In one embodiment of the present invention, the certificate key management verification module is configured to return a verification result to the production line certificate key filling device after completing the multi-stage verification; the production line certificate key filling device is configured to update the filling status record according to the verification result; the filling status record includes at least one of filling success, filling failure, and failure stage identifier and failure domain controller identifier corresponding to filling failure.

[0041] In this embodiment of the invention, after completing the multi-stage verification, the certificate key management verification module can return the verification result to the production line certificate key filling equipment. The production line certificate key filling equipment can then update the filling status record according to the verification result. The filling status record includes at least one of filling success, filling failure, and failure stage identifier and failure domain controller identifier corresponding to the filling failure. Subsequently, relevant personnel can obtain the latest filling status record of each domain controller of the vehicle. Furthermore, when filling fails, it can quickly locate which domain controller or which verification stage of the vehicle has a problem, thereby conducting targeted problem investigation or refilling, preventing problematic vehicles from flowing into subsequent stages, and improving the quality control efficiency and traceability of vehicle filling.

[0042] In summary, the present invention provides a vehicle certificate key file verification system. This system can comprehensively ensure the integrity, validity, and vehicle compatibility of the certificate key file through a multi-stage, multi-domain, and multi-dimensional verification mechanism during and after the vehicle certificate key file is installed. This solves the problems of missing verification links, inconsistencies between production line and after-sales processes, and lack of vehicle matching verification in related technical solutions.

[0043] To achieve the above objectives, the system's verification mechanism employs a multi-stage verification process, including local hash verification, certificate key matching verification, and certificate key vehicle matching verification. Local hash verification involves performing a hash operation on the packaged certificate key file using a pre-set hash checksum. Certificate key matching verification involves the certificate key management verification module establishing a two-way secure connection with the cloud certificate issuance server using the saved certificate key file to verify the validity of the certificate key file itself. Certificate key vehicle matching verification involves sending the local vehicle VIN and the locally saved hash checksum to the cloud certificate issuance server for verification, forming a closed-loop verification process from the cloud certificate issuance server issuing the certificate to the vehicle using the certificate key file and confirming with the cloud certificate issuance server. Furthermore, the system incorporates a master domain controller adaptive switching mechanism, collecting verification information (locally saved hash checksums) from each domain controller and performing unified multi-stage verification with the cloud certificate issuance server. The system also supports various verification scenarios, including production line filling verification, automated user verification and alarm scenarios, and after-sales proactively triggered verification scenarios.

[0044] Specifically, the core mechanism of the system includes the following steps: A multi-stage closed-loop verification mechanism: The verification process includes the following steps: the certificate key file and hash checksum sent by the cloud certificate issuing server; the vehicle storing the certificate key file and verifying its integrity locally; the vehicle connecting to the cloud certificate issuing server to verify the validity of the certificate key file; and the vehicle connecting to the cloud certificate issuing server to verify the compatibility of the certificate key with the vehicle. Thus, from the cloud certificate issuing server issuing the certificate key file to the vehicle using the certificate key file and confirming it with the cloud certificate issuing server, a closed-loop data flow verification is formed. Furthermore, the correctness verification throughout the entire process directly verifies the hash checksum, preventing the leakage of security information.

[0045] Multi-domain controller adaptive unified verification mechanism: To avoid each domain controller interacting separately with the cloud certificate issuance server, which would increase network management complexity and network resource consumption, a single master domain controller is used to communicate with the cloud certificate issuance server. At the same time, a master domain controller adaptive switching mechanism is added to solve the problem that the failure of a single domain controller certificate key file verification will cause the whole system to fail to verify.

[0046] User-automated or after-sales proactive multi-scenario verification mechanism: To prevent certificate key files from being damaged or tampered with during storage, two verification processes are set up: automatic triggering and proactive triggering. In the user-automated verification scenario, the vehicle-side certificate key management verification module listens for power-on events and automatically initiates multi-domain control and multi-stage verification. If the verification fails, the verification result is displayed on the vehicle's infotainment interface as an alert. In the after-sales proactive triggering scenario, after-sales personnel can proactively trigger verification and issue alerts based on the vehicle's infotainment interface, while simultaneously writing failure logs to the local diagnostic storage area for after-sales equipment to read.

[0047] To enable those skilled in the art to better understand the embodiments of the present invention, the following description uses an overall example.

[0048] Reference Figure 2 This is an architecture diagram of a vehicle-side filling certificate key lifecycle verification system provided in this embodiment of the invention. The working content of each module in the system includes: The cloud-based certificate issuance server sends the certificate key file and corresponding hash checksum to the production line certificate key loading device. After the production line certificate key loading device loads the certificate key file and corresponding hash checksum to each domain controller, it sends a verification command and hash checksum to the certificate key management verification module of the master domain controller. Based on the verification command, the master domain controller's certificate key management verification module performs one-stage verification, two-stage verification, and three-stage verification in sequence. During this process, it can establish a connection based on the certificate key file and send the hash checksum and VIN code of the certificate key files of all domain controllers to the cloud-based certificate issuance server. The cloud-based certificate issuance server responds to the second-stage and third-stage verification requests initiated by the master domain controller and returns the verification results. Based on the verification results, if the master domain controller determines that the three-stage verification is successful, it returns a success flag; otherwise, it returns the reason for the verification failure of each domain controller to the production line certificate key loading device.

[0049] Reference Figure 3 This is a flowchart illustrating a multi-stage, multi-domain control verification process for a vehicle-side certificate key management and verification module provided in this embodiment of the invention. The module performs multi-stage verification, including a three-stage closed-loop verification process: local hash verification, certificate key matching verification, and certificate key and vehicle matching verification. This is applicable to production line filling verification scenarios where all three verification stages need to be executed. The specific process includes: The cloud-based certificate issuance server sends the certificate key file and corresponding hash checksum to the production line certificate key loading device. After the production line certificate key loading device loads the certificate key file and corresponding hash checksum to each domain controller, it sends a verification command and hash checksum to the certificate key management verification module of the main domain controller. Based on the verification command, the certificate key management verification module of the main domain controller begins to execute the first stage of local hash verification: it performs a hash operation on the locally stored certificate key file using the same hash algorithm as the cloud-based certificate issuance server to obtain a local hash checksum, and compares it with the hash checksum issued by the production line certificate key loading device. If they match, the local hash verification passes, and the process proceeds to the second stage of certificate key matching verification; if they do not match, the verification fails, a reason for the verification failure is returned to the production line certificate key loading device, and the verification process is terminated.

[0050] After the local hash verification passes, the certificate key management verification module of the main domain controller establishes a two-way authentication secure connection with the cloud certificate issuing server based on the certificate key file. If the connection is established successfully, the certificate key matching verification passes and the second stage of certificate key vehicle matching verification begins. If the connection fails to be established, the verification fails, and the reason for the verification failure is returned to the certificate key filling equipment on the production line, terminating the verification process.

[0051] After the second-stage certificate key matching verification passes, the master domain controller's certificate key management verification module collects the hash checksums sent by domain controllers N+1, N+2, N+3, etc., and combines them with the local Vehicle Identification Number (VIN). Through the successfully established two-way authentication secure connection, it sends the hash checksums and VINs of each domain controller's certificate key file to the cloud certificate issuance server. The cloud certificate issuance server queries the corresponding hash checksum based on the VIN and compares them to obtain the verification result. It then returns the verification results from the second and third stages to the master domain controller. If the verification results match, the certificate key vehicle matching verification passes; if the verification results do not match, the verification fails, and the reason for the failure is returned to the production line certificate key filling equipment, terminating the verification process.

[0052] Reference Figure 4 This is a flowchart of a vehicle-side master domain controller adaptive switching verification process provided in an embodiment of the present invention. The master domain controller adaptive switching process may specifically include: The cloud-based certificate issuance server generates the vehicle's certificate key file and calculates the corresponding hash checksum. It then sends the certificate key file and hash checksum to the production line certificate key filling device through a secure channel. After writing the certificate key file into each domain controller, the production line certificate key filling device sends a verification command and hash checksum to the certificate key management and verification module of Domain Controller 1 (the primary domain controller).

[0053] After receiving the verification command, the certificate key management verification module of domain controller 1 begins to execute the first and second phases of verification (local hash verification and certificate key matching verification). If both phases of verification are successful, domain controller 1 becomes the primary domain controller and enters the third phase of verification; if either the first or second phase of verification fails, the primary domain controller adaptive failover process is initiated.

[0054] If the first-stage or second-stage verification of domain controller 1 fails, domain controller 1 determines the next target domain controller (domain controller N) according to the preset domain controller sequence configuration table, and sends a verification command to the vehicle-side certificate key management verification module of domain controller N. Domain controller N then re-executes the first and second-stage verifications. If domain controller N fails the verification, it is confirmed as a failure, N=N+1, and the process continues to traverse the next domain controller N+1 in the preset domain controller sequence configuration table, repeating the above verification steps until the first and second-stage verifications of a certain domain controller in the preset domain controller sequence configuration table are successful.

[0055] If the first and second phase verifications of domain controller N are successful, domain controller N will be designated as the new primary domain controller. Subsequently, the new primary domain controller will collect the hash checksums of other domain controllers N+1 to M, and uniformly perform the third phase verification. The vehicle identification number and the hash checksums of each domain controller will be sent to the cloud certificate issuance server for comparison through the established two-way authentication secure connection.

[0056] Reference Figure 5 This invention provides an automatic or proactive multi-stage, multi-domain control verification process for users and after-sales service, which may include the following: When a user starts the vehicle, the startup module sends a startup signal to the vehicle-side multi-domain control certificate key management and verification module. Upon detecting the vehicle power-on event, the certificate key management and verification module automatically generates a verification command including user and after-sales verification scenario identifiers. Based on the verification command, the certificate key management and verification module interacts with the cloud certificate issuance server to perform the second and third phases of verification and returns the verification results for the second and third phases. If after-sales personnel actively click the "Certificate Status Inquiry" function on the vehicle's infotainment display, it triggers the generation of a verification command including user and after-sales verification scenario identifiers and sends it to the certificate key management and verification module. Based on the verification command, the certificate key management and verification module interacts with the cloud certificate issuance server to perform multi-phase verification and returns the multi-phase verification results to the vehicle's infotainment display for display.

[0057] Applying the embodiments of this invention can achieve at least the following beneficial effects: It introduces a multi-stage progressive closed-loop verification mechanism, overcoming the shortcomings of related technologies that only perform one-time or simple verifications, forming a closed loop for certificate key file verification. This ensures the accuracy of the certificate key file in multiple ways at different stages and prevents its leakage, providing a fundamental guarantee for secure communication between the vehicle and the cloud. It introduces a multi-domain controller adaptive unified verification mechanism, reducing the number of cloud connection verifications from twice the number of domain controllers to a maximum of two (only the main domain controller performs the second and third stage verifications), significantly reducing network resource consumption, reducing the complexity of vehicle-side network management, and improving system stability. It also avoids the problem of overall verification failure due to mismatched certificate keys of a single domain controller. It introduces automated user / after-sales verification, covering the entire process of certificate key file verification, including production line, user, and after-sales services. Each time a user starts the vehicle, the certificate key file is automatically verified and displayed and alerted on the vehicle's interface, facilitating timely and rapid assessment of the vehicle's status. For after-sales troubleshooting, it enables rapid problem investigation and resolution. Without requiring modifications to existing production line equipment, the production line certificate key filling equipment only needs to have certificate key file distribution and result recording functions, without any additional intrusive operations. The verification process in this embodiment interacts with the cloud certificate issuance server through a standardized interface, is compatible with existing filling systems, and facilitates integration with various cloud security service platforms.

[0058] Reference Figure 6 This document illustrates a flowchart of a vehicle certificate key file verification method provided in an embodiment of the present invention. The method is applied to a vehicle certificate key file verification system, which includes a cloud certificate issuance server, a production line certificate key file installation device, and certificate key management and verification modules for each domain controller in the vehicle. The cloud certificate issuance server is configured to generate vehicle certificate key files. A hash checksum is obtained by hashing the certificate key file. The certificate key file and the hash checksum are sent as a certificate key pair to the production line certificate key file installation device. The production line certificate key file installation device is configured to install the certificate key pair as a local certificate key pair to each of the domain controllers. The method specifically includes the following steps: Step 601, obtain the verification command; Step 602: Perform multi-stage verification based on the local certificate key pair and the certificate key pair; the multi-stage verification includes multiple verification stages executed sequentially, the verification instruction includes a verification scenario identifier, and the verification scenario identifier has at least one corresponding verification stage; the verification instruction is sent by the production line certificate key filling device or generated locally.

[0059] In one embodiment of the present invention, the verification stage includes at least one of local hash verification, certificate key matching verification, and certificate key vehicle matching verification; the verification scenario identifier includes at least one of production line filling verification scenario identifier and user and after-sales verification scenario identifier.

[0060] In one embodiment of the present invention, the verification instruction including the production line filling verification scenario identifier is generated when the production line certificate key filling device fills the certificate key pair as a local certificate key pair into each of the domain controllers and sent to the certificate key management verification module; the verification instruction including the user and after-sales verification scenario identifier is generated when the certificate key management verification module detects the power-on event of the vehicle or the vehicle's in-vehicle interface is triggered.

[0061] In one embodiment of the present invention, step 602 includes: When the verification scenario identifier in the verification instruction is the production line filling verification scenario identifier, the local hash verification, the certificate key matching verification, and the certificate key vehicle matching verification are executed sequentially. When the verification scenario identifier in the verification instruction is a user and an after-sales verification scenario identifier, the certificate key matching verification and the certificate key vehicle matching verification are executed sequentially.

[0062] In one embodiment of the present invention, the local certificate key pair includes a local certificate key file; step 602 includes: When performing the local hash verification, the local certificate key file is hashed to obtain the local hash verification code; When the local hash check code matches the hash check code, the local hash check is determined to be successful. If the local hash check code is inconsistent with the hash check code, it is determined that the local hash check has failed.

[0063] In one embodiment of the present invention, step 602 includes: When performing the certificate key matching verification, a two-way authentication secure connection is established between the local certificate key file and the cloud certificate issuing server. When the two-way authentication secure connection is successfully established, it is determined that the certificate key matching verification is successful; When the establishment of the two-way authentication secure connection fails, it is determined that the certificate key matching verification has failed.

[0064] In one embodiment of the present invention, step 602 includes: When performing the certificate key vehicle matching verification, the vehicle identification number of the vehicle and the certificate verification information of each domain controller of the vehicle are obtained; the certificate verification information includes the local hash verification code of each domain controller. The vehicle identification code and the certificate verification information are sent to the cloud certificate issuing server through the successfully established two-way authentication secure connection. The cloud certificate issuing server obtains the hash verification code corresponding to the vehicle identification code and compares the local hash verification code with the hash verification code to obtain the comparison result. Receive the comparison result sent by the cloud certificate issuing server; When the comparison result shows that the local hash check code matches the hash check code, it is determined that the certificate key vehicle matching verification is successful. If the comparison result shows that the local hash check code is inconsistent with the hash check code, it is determined that the certificate key vehicle matching verification has failed.

[0065] In one embodiment of the present invention, the domain controller includes a primary domain controller, which establishes a two-way authentication secure connection with the cloud certificate issuing server through the certificate key management and verification module of the primary domain controller, and sends the certificate verification information to the cloud certificate issuing server through the successfully established two-way authentication secure connection; step 602 includes: If the local hash verification fails or the certificate key matching verification fails, the target domain controller is determined by traversing the preset domain controller order configuration table. Send the verification instruction to the certificate key management verification module of the target domain controller to re-execute the local hash verification and the certificate key matching verification through the target domain controller; When both the local hash verification and the certificate key matching verification are successful, the target domain controller is designated as the new primary domain controller, and the certificate key vehicle matching verification is performed through the certificate key management verification module of the new primary domain controller. If the local hash verification fails or the certificate key matching verification fails, and the preset domain controller sequence configuration table has been traversed, then the multi-stage verification is determined to have failed.

[0066] In one embodiment of the present invention, the method further includes: After completing the multi-stage verification, the verification result is returned to the production line certificate key filling device; the production line certificate key filling device is configured to update the filling status record according to the verification result; the filling status record includes at least one of filling success, filling failure, and failure stage identifier and failure domain controller identifier corresponding to filling failure.

[0067] It should be noted that, for the sake of simplicity, the method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments of the present invention are not limited to the described order of actions, because according to the embodiments of the present invention, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions involved are not necessarily essential to the embodiments of the present invention.

[0068] As the method embodiments are basically similar to the system embodiments, the description is relatively simple, and relevant parts can be found in the description of the system embodiments.

[0069] This invention also provides an electronic device, such as... Figure 7 As shown, it includes a processor 1001, a device interface 1002, a memory 1003, and a bus 1004; Memory 1003 is used to store computer programs; The processor 1001 executes the above steps when executing the program stored in the memory 1003.

[0070] The bus mentioned in the above electronic devices can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not mean that there is only one bus or one type of bus.

[0071] The memory may include random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.

[0072] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0073] The present invention also provides a storage medium that, when the instructions in the storage medium are executed by the processor of an electronic device, enables the electronic device to execute the vehicle filling certificate key file verification method of the foregoing embodiments.

[0074] As the device embodiment is basically similar to the method embodiment, the description is relatively simple, and relevant parts can be found in the description of the method embodiment.

[0075] The algorithms and displays provided herein are not inherently related to any particular computer, virtual device, or other equipment. The structure required to construct such a device is readily apparent from the above description. Furthermore, this invention is not directed to any particular programming language. It should be understood that the contents of the invention described herein can be implemented using various programming languages, and the above description of specific languages ​​is for the purpose of disclosing the best mode of implementation of the invention.

[0076] Numerous specific details are set forth in the specification provided herein. However, it will be understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures, and techniques have not been shown in detail so as not to obscure the understanding of this specification.

[0077] Similarly, it should be understood that, in order to simplify the invention and aid in understanding one or more of the various inventive aspects, in the above description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof. However, this method of disclosure should not be construed as reflecting an intention that the claimed invention requires more features than expressly recited in each claim. Rather, as reflected in the following claims, inventive aspects lie in fewer than all features of a single foregoing disclosed embodiment. Therefore, the claims following the detailed description are hereby expressly incorporated into this detailed description, wherein each claim itself is a separate embodiment of the invention.

[0078] Those skilled in the art will understand that modules in the device of the embodiments can be adaptively changed and placed in one or more devices different from that embodiment. Modules, units, or components in the embodiments can be combined into a single module, unit, or component, and further, they can be divided into multiple sub-modules, sub-units, or sub-components. Except where at least some of such features and / or processes or units are mutually exclusive, any combination can be used to combine all features disclosed in this specification (including the accompanying claims, abstract, and drawings) and all processes or units of any method or device so disclosed. Unless expressly stated otherwise, each feature disclosed in this specification (including the accompanying claims, abstract, and drawings) may be replaced by an alternative feature that serves the same, equivalent, or similar purpose.

[0079] The various component embodiments of the present invention can be implemented in hardware, or as software modules running on one or more processors, or a combination thereof. Those skilled in the art will understand that microprocessors or digital signal processors (DSPs) can be used in practice to implement some or all of the functions of some or all of the components in the sorting device according to the present invention. The present invention can also be implemented as a device or apparatus program for performing part or all of the methods described herein. Such a program implementing the present invention can be stored on a computer-readable medium, or can be in the form of one or more signals. Such signals can be downloaded from an Internet website, provided on a carrier signal, or provided in any other form.

[0080] It should be noted that the above embodiments are illustrative of the invention and not restrictive, and that those skilled in the art can devise alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses should not be construed as limiting the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention can be implemented by means of hardware comprising several different elements and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by the same item of hardware. The use of the words first, second, and third, etc., does not indicate any order. These words can be interpreted as names.

[0081] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the devices, apparatuses, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0082] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

[0083] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

[0084] It should be noted that the various data-related processes in the embodiments of this application are carried out in compliance with the relevant data protection laws and policies of the country where the location is located, and with the authorization granted by the owner of the corresponding device.

Claims

1. A vehicle filling certificate key file verification system, characterized in that, The system includes a cloud-based certificate issuance server, a production line certificate key filling device, and a certificate key management and verification module for each domain controller in the vehicle. The cloud certificate issuing server is configured to generate the vehicle's certificate key file; The certificate key file is hashed to obtain a hash checksum; the certificate key file and the hash checksum are sent as a certificate key pair to the production line certificate key filling equipment. The production line certificate key filling device is configured to fill the certificate key pair as a local certificate key pair into each of the domain controllers; The certificate key management verification module is configured to obtain a verification instruction and perform multi-stage verification based on the local certificate key pair and the certificate key pair. The multi-stage verification includes multiple verification stages executed sequentially. The verification instruction includes a verification scenario identifier, and the verification scenario identifier has at least one corresponding verification stage. The verification instruction is sent by the production line certificate key filling device or generated locally.

2. The system according to claim 1, characterized in that, The verification phase includes at least one of local hash verification, certificate key matching verification, and certificate key vehicle matching verification; the verification scenario identifier includes at least one of production line filling verification scenario identifier and user and after-sales verification scenario identifier.

3. The system according to claim 2, characterized in that, The verification instruction, including the production line filling verification scenario identifier, is generated when the production line certificate key filling device fills the certificate key pair as a local certificate key pair into each of the domain controllers and sends it to the certificate key management verification module; the verification instruction, including the user and after-sales verification scenario identifier, is generated when the certificate key management verification module detects the power-on event of the vehicle or the vehicle's in-vehicle interface is triggered.

4. The system according to claim 3, characterized in that, The certificate key management and verification module is configured as follows: When the verification scenario identifier in the verification instruction is the production line filling verification scenario identifier, the local hash verification, the certificate key matching verification, and the certificate key vehicle matching verification are executed sequentially. When the verification scenario identifier in the verification instruction is a user and an after-sales verification scenario identifier, the certificate key matching verification and the certificate key vehicle matching verification are executed sequentially.

5. The system according to claim 3 or 4, characterized in that, The local certificate key pair includes a local certificate key file; the certificate key management and verification module is configured as follows: When performing the local hash verification, the local certificate key file is hashed to obtain the local hash verification code; When the local hash check code matches the hash check code, the local hash check is determined to be successful. If the local hash check code is inconsistent with the hash check code, it is determined that the local hash check has failed.

6. The system according to claim 5, characterized in that, The certificate key management and verification module is configured as follows: When performing the certificate key matching verification, a two-way authentication secure connection is established between the local certificate key file and the cloud certificate issuing server. When the two-way authentication secure connection is successfully established, it is determined that the certificate key matching verification is successful; When the establishment of the two-way authentication secure connection fails, it is determined that the certificate key matching verification has failed.

7. The system according to claim 6, characterized in that, The certificate key management and verification module is configured as follows: When performing the certificate key vehicle matching verification, the vehicle identification number of the vehicle and the certificate verification information of each domain controller of the vehicle are obtained; the certificate verification information includes the local hash verification code of each domain controller. The vehicle identification code and the certificate verification information are sent to the cloud certificate issuing server through the successfully established two-way authentication secure connection. The cloud certificate issuing server obtains the hash verification code corresponding to the vehicle identification code and compares the local hash verification code with the hash verification code to obtain the comparison result. Receive the comparison result sent by the cloud certificate issuing server; When the comparison result shows that the local hash check code matches the hash check code, it is determined that the certificate key vehicle matching verification is successful. If the comparison result shows that the local hash check code is inconsistent with the hash check code, it is determined that the certificate key vehicle matching verification has failed.

8. The system according to claim 7, characterized in that, The domain controller includes a primary domain controller, which establishes a two-way authentication secure connection with the cloud certificate issuing server through its certificate key management and verification module, and sends certificate verification information to the cloud certificate issuing server through the successfully established two-way authentication secure connection; the certificate key management and verification module of the primary domain controller is configured as follows: If the local hash verification fails or the certificate key matching verification fails, the target domain controller is determined by traversing the preset domain controller order configuration table. Send the verification instruction to the certificate key management verification module of the target domain controller to re-execute the local hash verification and the certificate key matching verification through the target domain controller; When both the local hash verification and the certificate key matching verification are successful, the target domain controller is designated as the new primary domain controller, and the certificate key vehicle matching verification is performed through the certificate key management verification module of the new primary domain controller. If the local hash verification fails or the certificate key matching verification fails, and the preset domain controller sequence configuration table has been traversed, then the multi-stage verification is determined to have failed.

9. The system according to claim 8, characterized in that, The certificate key management verification module is configured to return the verification result to the production line certificate key filling equipment after completing the multi-stage verification. The production line certificate key filling device is configured to update the filling status record based on the verification result; the filling status record includes at least one of filling success, filling failure, and failure stage identifier and failure domain controller identifier corresponding to filling failure.

10. A method for verifying vehicle filling certificate key files, characterized in that, The system is applied to a vehicle filling certificate key file verification system, which includes a cloud certificate issuance server, a production line certificate key filling equipment, and a certificate key management and verification module for each domain controller in the vehicle. The cloud certificate issuing server is configured to generate the vehicle's certificate key file; The certificate key file is hashed to obtain a hash checksum; The certificate key file and the hash checksum are sent as a certificate key pair to the production line certificate key filling equipment; The production line certificate key filling device is configured to fill the certificate key pair as a local certificate key pair into each of the domain controllers; the method includes: Obtain the verification command; A multi-stage verification is performed based on the local certificate key pair and the certificate key pair; the multi-stage verification includes multiple verification stages executed sequentially, the verification instruction includes a verification scenario identifier, and the verification scenario identifier has at least one corresponding verification stage; the verification instruction is sent by the production line certificate key filling device or generated locally.

11. An electronic device, characterized in that, include: processor; Memory used to store processor-executable instructions; The processor is configured to execute the instructions to implement the vehicle filling certificate key file verification method as described in claim 10.

12. A computer-readable storage medium, characterized in that, When the instructions in the storage medium are executed by the processor of the mobile terminal, the mobile terminal is able to perform the vehicle filling certificate key file verification method as described in claim 10.

13. A vehicle, characterized in that, The vehicle includes the electronic equipment as described in claim 11.