A method, system and storage medium for on-board diagnostic safety authentication

Abstract

This invention discloses an on-board diagnostic security authentication method, system, and storage medium, comprising: a user registering through a cloud server to obtain an identity code; the cloud server creating a public key and a private key pair for the target vehicle using an asymmetric algorithm; the user logging into the cloud server through a diagnostic tool to verify the identity code and obtain access to the target vehicle; requesting a seed from the vehicle through the diagnostic tool, and generating a signature using the public key based on the seed hash value, the identity code, and the vehicle identification number; the vehicle end verifying the signature using the private key, and enabling or disabling diagnostic routing based on the verification result.

Description

Technical Field

[0001] This invention relates to the technical field of user vehicle diagnostic data permission verification methods based on asymmetric encryption, specifically to a vehicle diagnostic security authentication method, system, and storage medium. Background Technology

[0002] In recent years, the intelligent and connected vehicle industry has been developing rapidly. In order to quickly adapt to user and scenario needs, there are more and more cases of accessing vehicle data, changing vehicle configurations and parameters through vehicle diagnostic interfaces. However, writing data through vehicle diagnostic interfaces faces the risk of unauthorized access and tampering.

[0003] The vehicle itself defines a lot of data that can be accessed through the diagnostic interface. For example, the 0x22 service can read the vehicle's basic parameters and some key controller information. The 0x2E service can rewrite the content of certain parameters; the 0x31 service can manipulate the ECU to perform certain actions; and the 0x2F service can manipulate the ECU's I / O interface. To prevent the ECU from being accessed by unauthorized users or maliciously, this patent invention proposes a user permission verification method based on asymmetric encryption. By setting user IDs and access permissions, and using cloud-vehicle asymmetric encryption verification, each time the vehicle is accessed through the diagnostic interface, user permissions must be verified before access can be granted, thereby ensuring the security of diagnostic data. Summary of the Invention

[0004] To address at least one of the aforementioned technical problems, embodiments of the present invention provide an on-board diagnostic security authentication method, comprising: a user registering through a cloud server to obtain an identity code, and storing the user's identity code on the cloud server; the cloud server creating a public key and private key pair for a target vehicle using an asymmetric algorithm, pre-embedding the public key in the target vehicle, and storing the private key on the cloud server; the user logging into the cloud server through a diagnostic tool to verify the identity code and obtain access to the target vehicle; requesting a first seed from the vehicle through the diagnostic tool, the diagnostic tool calculating the seed hash value of the first seed, and comparing the seed hash value with the identity code. The diagnostic tool generates a second seed by concatenating the vehicle identification number (VIN) and using a shift algorithm. The diagnostic tool sends the second seed to the cloud server. The cloud server encrypts the second seed with its private key to generate a first key and sends the first key to the diagnostic tool. The diagnostic tool sends the first key to the target vehicle. The target vehicle responds by decrypting the received first key with its public key to generate a third seed. The target vehicle then concatenates the first seed, the VIN, and the identification code and generates a fourth seed using a shift algorithm. The third and fourth seeds are compared. If the third and fourth seeds are the same, the diagnostic routing function is enabled; otherwise, the diagnostic routing function is disabled.

[0005] Preferably, the asymmetric algorithm uses either the ECDSA algorithm or the RSA algorithm.

[0006] Preferably, the cloud server verifies whether a user is a legitimate employee of the company by verifying the user's identity. Once the user's identity is verified, the cloud server generates an identity code.

[0007] Preferably, the cloud server verifies the user's identity by generating a dynamic password based on identity encoding.

[0008] Preferably, the cloud server verifies the user's identity code and verifies the user's access rights to the target vehicle. When the user has access rights to the target vehicle, the diagnostic tool requests the first seed from the vehicle.

[0009] Preferably, the public key is pre-embedded in the target vehicle's central gateway or central domain controller.

[0010] On the other hand, an in-vehicle diagnostic security authentication system is provided, comprising: a cloud server, a diagnostic tool, and a vehicle terminal. The cloud server verifies the user's identity based on the user's registration information to generate a user identity code, and stores the user identity code in the cloud server. The cloud server uses an asymmetric algorithm to create a public key and private key pair for the target vehicle, pre-embedding the public key in the vehicle terminal and storing the private key in the cloud server. The diagnostic tool connects to both the cloud server and the vehicle terminal's diagnostic interface. The user logs into the cloud server through the diagnostic tool to verify the identity code and obtain vehicle terminal access permissions for the target vehicle. The user requests a first seed from the vehicle terminal through the diagnostic tool, and the diagnostic tool calculates the first seed. The diagnostic tool generates a seed hash value, concatenates it with the identification code and vehicle identification number (VIN), and then uses a shift algorithm to generate a second seed. The diagnostic tool sends the second seed to the cloud server. The cloud server encrypts the second seed with its private key to generate a first key, which is then sent to the diagnostic tool. The diagnostic tool sends the first key to the vehicle. The vehicle responds by decrypting the received first key with its public key to generate a third seed. The vehicle then concatenates the first seed, VIN, and identification code and uses a shift algorithm to generate a fourth seed. The vehicle compares the third and fourth seeds. If the third and fourth seeds are the same, the diagnostic routing function is enabled; otherwise, the diagnostic routing function is disabled.

[0011] On the other hand, a computer-readable storage medium is provided, including computer program instructions that are implemented by a processor at runtime as described in the preceding embodiments of the vehicle diagnostic safety authentication method.

[0012] The vehicle diagnostic security authentication method of this invention has the following technical effects: it uses an asymmetric encryption algorithm, combined with a diagnostic instrument and a cloud server, and uses dynamic passwords, level-based permission verification, and gateway unified authentication of user permissions to achieve the authentication of diagnostic user permissions. It can meet regulatory requirements, has high security, and can effectively prevent vehicles from being accessed by unauthorized users. Attached Figure Description

[0013] To better understand the above and other objects, features, advantages, and functions of the present invention, reference can be made to the embodiments shown in the accompanying drawings. The same reference numerals in the drawings refer to the same parts. Those skilled in the art should understand that the drawings are intended to schematically illustrate preferred embodiments of the invention and do not limit the scope of the invention in any way; the parts in the drawings are not drawn to scale.

[0014] Figure 1 A flowchart illustrating an on-board diagnostic safety certification method according to an embodiment of the present invention is shown;

[0015] Figure 2 A schematic diagram illustrating an application scenario of the on-board diagnostic safety certification method according to an embodiment of the present invention is shown. Detailed Implementation

[0016] The exemplary embodiments of this disclosure are described below with reference to the accompanying drawings, including various details of the embodiments to aid understanding, and should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this disclosure. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0017] The term "comprising" and its variations as used herein signify open inclusion, i.e., "including but not limited to". Unless otherwise stated, the term "or" means "and / or". The term "based on" means "at least partially based on". The terms "one example embodiment" and "one embodiment" mean "at least one example embodiment". The term "another embodiment" means "at least one additional embodiment". The terms "first", "second", etc., may refer to different or the same objects. Other explicit and implicit definitions may also be included below.

[0018] In order to at least partially solve one or more of the above-mentioned problems and other potential problems, embodiments of the present disclosure propose an on-board diagnostic safety authentication method, including: step S1, whereby a user registers through a cloud server to obtain an identity code and stores the user's identity code in the cloud server.

[0019] Specifically, the cloud server generates an identity code upon receiving a user's registration request. This identity code is used to uniquely identify the user.

[0020] In some embodiments, the cloud server verifies whether a user is a legitimate employee of the company by verifying the user's identity. Once the user's identity is verified, the cloud server generates an identity code.

[0021] Specifically, the cloud server includes pre-stored user identity information. Users apply for identity authentication by uploading their identity information to pass the registration review and obtain an identity code.

[0022] In some embodiments, the cloud server verifies the user's identity by generating a dynamic password based on identity encoding.

[0023] Specifically, the cloud server assigns a unique identity code (such as QWER12345) and an 8-digit dynamic password to each verified legitimate user. For example, a user needs to register as a legitimate user in the cloud server backend. The cloud server backend verifies the user's identity (such as whether they are a legitimate employee of the company, and whether they should have such permissions according to their job responsibilities). After the user's identity is verified, they will receive a unique identity DID and will receive a verification code periodically or as needed via a mobile device.

[0024] In step S2, the cloud server uses an asymmetric algorithm to create a public key and a private key pair for the target vehicle. The public key is pre-embedded in the target vehicle, and the private key is stored in the cloud server.

[0025] Specifically, the private key generated by the cloud server is used to generate the digital signature, and the public key is used to verify the digital signature. The public key is embedded in the target vehicle's terminal; the private key is stored separately by the IT system and its security is ensured.

[0026] In some embodiments, the public key is pre-embedded in the target vehicle's central gateway or central domain controller.

[0027] Specifically, the central gateway enables cross-domain data exchange through a hybrid (CAN + Ethernet) interface. The public key is pre-embedded in the gateway's security module, supporting national cryptographic algorithms such as SM2 / SM4 to encrypt and verify V2X communication data.

[0028] Under the "central computing + regional control" architecture, the central domain controller connects to the regional controller through high-speed interfaces such as PCIe 5.0 and CXL. The public key storage is combined with the hardware security module (HSM) and TSN Ethernet to achieve low-latency key distribution.

[0029] In some embodiments, the asymmetric algorithm may be either ECDSA or RSA.

[0030] Specifically, the ECDSA and RSA algorithms can be used for permission verification to meet confidentiality requirements while avoiding excessive computing power requirements that would increase the computing cost of permission verification.

[0031] In another embodiment, the asymmetric algorithm can also use DSA (Digital Signature Algorithm), which is based on the discrete logarithm problem to achieve digital signature and verification. It has a shorter key length than RSA but is less efficient; or the ElGamal algorithm, which is also based on discrete logarithms, has security close to RSA, but lower encryption efficiency.

[0032] Step S3: The user logs into the cloud server through the diagnostic tool to verify the identity code and obtain access to the target vehicle.

[0033] Specifically, the cloud server receives the user's authentication request through the diagnostic tool and determines whether the user has access to the target vehicle by verifying the user's identity code.

[0034] In some embodiments, users can obtain access to the target vehicle by submitting an application after logging into the cloud server through a diagnostic tool.

[0035] In some embodiments, the cloud server verifies the identity code to check the user's access rights to the target vehicle. When the user has access rights to the target vehicle, the diagnostic tool requests the first seed from the vehicle.

[0036] Specifically, when diagnostic permissions for the target vehicle are only granted to specific users, the user information for granting permissions is stored in a cloud server. The user requests access permission verification from the cloud server through the diagnostic tool to obtain access permission to the target vehicle. That is, when the user's identity code passes the access permission verification, the user has access permission to the target vehicle; when the user's identity code fails the access permission verification, the user does not have access permission to the target vehicle, and the diagnostic tool cannot send a request to the target vehicle.

[0037] Step S4: The diagnostic tool requests a first seed from the vehicle. The diagnostic tool calculates the seed hash value of the first seed, and then uses a shift algorithm to generate a second seed after concatenating the seed hash value with the identification code and the vehicle identification number. The diagnostic tool then sends the second seed to the cloud server.

[0038] Specifically, after logging into the cloud server on the diagnostic tool and obtaining backend access authentication from the cloud server, the user requests a seed from the target vehicle through the diagnostic tool. The target vehicle sends a first seed of several bytes (e.g., more than 8 bytes) to the diagnostic tool. The diagnostic tool calculates the SHA256 hash value of the first seed, concatenates the seed hash value with the user's identity code and vehicle identification number, and then transforms it through a shift algorithm to form a new second seed. The second seed is then sent to the cloud server.

[0039] In step S5, the cloud server uses its private key to encrypt the second seed to generate the first key, and then sends the first key to the diagnostic instrument.

[0040] Specifically, the cloud server uses a private key for signing, and the signing process involves encrypting the second seed with the private key to generate the first key.

[0041] In step S6, the diagnostic tool sends the first key to the target vehicle. The target vehicle responds to the received first key by decrypting it with the public key to generate the third seed. The target vehicle then concatenates the first seed, the vehicle identification number (VIN), and the identification code and uses a shift algorithm to generate the fourth seed.

[0042] Specifically, the target vehicle uses public key verification for signature verification. The process of verifying the name involves receiving the first key through a diagnostic tool, decrypting the first key using the public key to generate the third seed, and then using a shift algorithm to generate the fourth seed from the first seed, the vehicle identification number (VIN), and the identity code.

[0043] Step S7: Compare the third seed and the fourth seed. If the third seed and the fourth seed are the same, enable the diagnostic routing function. If the third seed and the fourth seed are different, disable the diagnostic routing function.

[0044] Specifically, the results of the third and fourth seeds are compared. If they are the same, the user identity verification is passed, the user is identified as a legitimate user, and the diagnostic routing function is enabled to send the diagnostic request to the relevant controllers. Otherwise, the user is identified as an illegitimate user, the diagnostic routing function is disabled, and the diagnostic request is refused to be forwarded.

[0045] On the other hand, an in-vehicle diagnostic security authentication system is provided, including a cloud server, a diagnostic tool, and a vehicle terminal. The cloud server verifies the user's identity based on the user's registration information to generate a user identity code, and stores the user identity code in the cloud server. The cloud server uses an asymmetric algorithm to create a public key and private key pair for the target vehicle. The public key is pre-embedded in the vehicle terminal of the target vehicle, and the private key is stored in the cloud server. The diagnostic tool is connected to both the cloud server and the vehicle terminal's diagnostic interface. The user logs into the cloud server through the diagnostic tool to verify the identity code and obtain vehicle terminal access permissions for the target vehicle. The user requests a first seed from the vehicle terminal through the diagnostic tool, and the diagnostic tool calculates the first seed. The diagnostic tool generates a seed hash value, concatenates it with the identification code and vehicle identification number (VIN), and then uses a shift algorithm to generate a second seed. The diagnostic tool sends the second seed to the cloud server. The cloud server encrypts the second seed with its private key to generate a first key, which is then sent to the diagnostic tool. The diagnostic tool sends the first key to the vehicle. The vehicle responds by decrypting the received first key with its public key to generate a third seed. The vehicle then concatenates the first seed, VIN, and identification code and uses a shift algorithm to generate a fourth seed. The vehicle compares the third and fourth seeds. If the third and fourth seeds are the same, the diagnostic routing function is enabled; otherwise, the diagnostic routing function is disabled.

[0046] Specifically, the cloud server includes a user access control module, a key generation module, and a signature generation module. The user access control module is used to verify user identity, generate user identification codes, and the corresponding passwords. It also stores user identity information and user identification codes.

[0047] The key generation module is used to generate a public and private key pair based on each vehicle. Each vehicle's public and private key pair is unique. When the cloud server generates multiple public and private key pairs based on multiple vehicles, there is a one-to-one correspondence between the multiple vehicles and the multiple public and private key pairs.

[0048] The signature generation module receives the second seed through the diagnostic instrument and generates a signature based on the second seed using the private key for verification of diagnostic permissions.

[0049] The diagnostic tool is used to connect the cloud server and the vehicle. The diagnostic tool includes a login interface that provides users with access to the cloud server, a seed computing module for calculating diagnostic permissions, and a diagnostic module for accessing and collecting diagnostic data from the vehicle.

[0050] The vehicle-mounted central gateway or central domain controller is configured to store public keys. The vehicle-mounted system also includes a seed generation module. This module receives the first seed request from the diagnostic tool in response to an access permission approval command output by the cloud server. The vehicle-mounted system also includes a verification module for diagnostic permission verification. This module is configured to decrypt the first key using the public key to generate a third seed. The vehicle-mounted system concatenates the first seed, the vehicle identification number (VIN), and the identification code, then uses a shift algorithm to generate a fourth seed. The vehicle-mounted system compares the third and fourth seeds to verify diagnostic permissions. If the results of the third and fourth seeds are the same, the identity verification passes, the user is identified as a legitimate user, and the diagnostic routing function is enabled, sending the diagnostic request to the relevant controllers. Otherwise, the user is identified as an illegitimate user, the diagnostic routing function is disabled, and the diagnostic request is refused to be forwarded.

[0051] On the other hand, a computer-readable storage medium is provided, including computer program instructions that are implemented by a processor at runtime as described in the preceding embodiments of the vehicle diagnostic safety authentication method.

[0052] Specifically, computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules or other data). Computer-readable storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer.

[0053] The various embodiments of this disclosure have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen to best explain the principles, practical application, or technical improvements to the embodiments in the market, or to enable others skilled in the art to understand this document.

Claims

1. An on-board diagnosis security authentication method characterized by comprising: The application comprises the following steps: A user registers with a cloud server to obtain an identity code, and the cloud server stores the user's identity code; The cloud server creates a pair of public and private keys for a target vehicle using an asymmetric algorithm, and pre-embeds the public key in the target vehicle and stores the private key in the cloud server; The user logs in to the cloud server through a diagnostic instrument to verify the identity code to obtain access permission to the target vehicle; The diagnostic instrument requests a first seed from the vehicle, calculates a seed hash value of the first seed, and generates a second seed by splicing the seed hash value with the identity code and the vehicle identification number using a shift algorithm, and sends the second seed to the cloud server; The cloud server encrypts the second seed using the private key to generate a first secret key, and sends the first secret key to the diagnostic instrument; The diagnostic instrument sends the first secret key to the target vehicle, and the target vehicle decrypts the first secret key using the public key to generate a third seed, and generates a fourth seed by splicing the first seed, the vehicle identification number, and the identity code using a shift algorithm; The third seed and the fourth seed are compared, and when they are the same, the diagnostic routing function is enabled, and when they are different, the diagnostic routing function is disabled.

2. The method of claim 1, wherein, The asymmetric algorithm uses any one of the ECDSA algorithm and the RSA algorithm.

3. The method of claim 1, wherein, The cloud server determines whether the user is a legal employee of the company by verifying the user's identity, and generates an identity code when the user's identity is verified.

4. The method of claim 3, wherein, The cloud server verifies the user's identity by generating a dynamic password based on the identity code.

5. The method of claim 4, wherein, The cloud server verifies the user's access permission to the target vehicle by verifying the identity code, and the diagnostic instrument requests a first seed from the vehicle when the user has access permission to the target vehicle.

6. The method of claim 1, wherein, The public key is pre-embedded in the central gateway or central domain control of the target vehicle.

7. An on-board diagnosis security authentication system characterized by comprising: The application comprises the following steps: The cloud server, the diagnostic instrument, and the vehicle end, the cloud server is used to verify the user's identity according to the user's registration information to generate a user's identity code, and the cloud server stores the user's identity code, the cloud server creates a pair of public and private keys for a target vehicle using an asymmetric algorithm, and pre-embeds the public key in the vehicle end of the target vehicle and stores the private key in the cloud server, the diagnostic instrument is connected to the cloud server and the vehicle end diagnostic interface of the target vehicle, the user logs in to the cloud server through the diagnostic instrument to verify the identity code to obtain access permission to the vehicle end of the target vehicle, the diagnostic instrument requests a first seed from the vehicle end through the diagnostic instrument, the diagnostic instrument calculates a seed hash value of the first seed, and generates a second seed by splicing the seed hash value with the identity code and the vehicle identification number using a shift algorithm, and sends the second seed to the cloud server, the cloud server encrypts the second seed using the private key to generate a first secret key, and sends the first secret key to the diagnostic instrument, the diagnostic instrument sends the first secret key to the vehicle end, the vehicle end decrypts the first secret key using the public key to generate a third seed, the vehicle end generates a fourth seed by splicing the first seed, the vehicle identification number, and the identity code using a shift algorithm, and the vehicle end compares the third seed and the fourth seed, and when they are the same, the diagnostic routing function is enabled, and when they are different, the diagnostic routing function is disabled.

8. A computer-readable storage medium, characterized in that, Computer program instructions, when executed by a processor, implement the vehicle diagnostic safety certification method as claimed in any one of claims 1-6.

Images