A vehicle identity verification method, device, apparatus and storage medium

Abstract

Embodiments of the present application disclose a vehicle identity verification method, device and equipment, and a storage medium. The method comprises the following steps: receiving a verification request sent by a target vehicle through an electronic vehicle identification (eVIN) application end and an eVIN server end, wherein the verification request comprises an eVIN certificate of the target vehicle, first verification data and a signature value, the eVIN certificate is generated by an eVIN issuing end according to an eVIN code of the target vehicle, the eVIN is generated by the eVIN issuing end according to a vehicle identification (VIN) code of the target vehicle, and the signature value is obtained by encrypting the first verification data by a private key corresponding to the eVIN certificate of the target vehicle; decrypting the signature value according to a public key of the eVIN certificate to obtain second verification data; and obtaining an identity verification result of the target vehicle by comparing the first verification data with the second verification data. The present application uses the eVIN certificate to replace the VIN, realizes online identification of the identity of the vehicle without leaking the private information of the vehicle, and improves the security of the identity information of the vehicle.

Description

Technical Field

[0001] This application belongs to the field of vehicle networking technology, and in particular relates to a vehicle authentication method, device, equipment and storage medium. Background Technology

[0002] With the development of communication technology, the Internet of Vehicles (IoV) is becoming increasingly intelligent. The IoV is a huge interactive network composed of information such as vehicle identity, location, speed, and route. The confidentiality, authenticity, integrity, and non-repudiation of data communication in the IoV need to be guaranteed.

[0003] Currently, the vehicle identification mechanism in the vehicle network generally uses the vehicle identification number (VIN) as the vehicle's identity information. The VIN is associated with the vehicle's classification attribute information to complete data communication in the vehicle network.

[0004] The VIN code-based authentication mechanism requires the transmission of the VIN code, but the VIN code can be easily intercepted during transmission, leading to vehicle data leakage and poor security. Summary of the Invention

[0005] This application provides a vehicle identity verification method, apparatus, device, and storage medium, which can improve the security of vehicle identity information.

[0006] In a first aspect, embodiments of this application provide a vehicle authentication method applied to an Electronic Vehicle Identification Number (eVIN) issuing terminal, the method comprising:

[0007] The system receives a verification request sent by the target vehicle through the eVIN application and eVIN server. The verification request includes the target vehicle's eVIN certificate, first verification data, and signature value. The eVIN certificate is generated by the eVIN issuer based on the target vehicle's vehicle identification eVIN code, the eVIN code is generated by the eVIN issuer based on the target vehicle's VIN code, and the signature value is obtained by the target vehicle encrypting the first verification data using the private key corresponding to the eVIN certificate.

[0008] The signature value is decrypted using the public key in the eVIN certificate to obtain the second verification data;

[0009] By comparing the first verification data with the second verification data, the first identity verification result of the target vehicle is obtained.

[0010] In one possible implementation, the verification request also includes the encrypted VIN code of the target vehicle, and the eVIN certificate includes the eVIN code; the method also includes:

[0011] When the first authentication result is successful, the correspondence between the eVIN code and the VIN code is compared with the target correspondence between the eVIN code and the VIN code of the target vehicle to obtain the second authentication result of the target vehicle.

[0012] In one possible implementation, the eVIN certificate includes an eVIN code, which is generated by the eVIN issuer based on the VIN code and a first random number. The method further includes:

[0013] Based on the correspondence between eVIN code and VIN code, determine the VIN code corresponding to the eVIN code;

[0014] Generate an identity information index value based on the VIN code;

[0015] Send the identity information index value to the eVIN application so that the eVIN application can determine the customer category of the target vehicle based on the identity information index value.

[0016] In one possible implementation, the identity information index value includes the application identifier and VIN code in the eVIN application, as well as a second random number used to encrypt the identifier and VIN code of the target application.

[0017] In one possible implementation, before receiving the verification request sent by the target vehicle through the eVIN application and eVIN server, the method further includes:

[0018] Receive eVIN application request sent by eVIN registration and issuing terminal. eVIN application request is generated based on digital identity application request and VIN code of target vehicle when eVIN registration and issuing terminal receives digital identity application request sent by target vehicle. eVIN application request includes VIN code.

[0019] Generate an eVIN code based on the VIN code and the first random number;

[0020] Generate an eVIN certificate based on the eVIN code; the eVIN certificate includes the eVIN code.

[0021] The eVIN certificate is sent to the target vehicle through the eVIN registration and issuance terminal.

[0022] In one possible implementation, the method also includes:

[0023] Generate the target correspondence between the VIN code and the eVIN code.

[0024] Secondly, embodiments of this application provide a vehicle authentication method, applied to a target vehicle, the method comprising:

[0025] The first verification data is encrypted using the private key corresponding to the eVIN certificate to obtain the signature value;

[0026] A verification request is generated based on the eVIN certificate, the first verification data, and the signature value. The verification request includes the target vehicle's eVIN certificate, the first verification data, and the signature value. The eVIN certificate is generated by the eVIN issuer based on the target vehicle's eVIN code, and the eVIN code is generated by the eVIN issuer based on the target vehicle's VIN code.

[0027] The eVIN application and eVIN server send verification requests to the eVIN issuer so that the eVIN issuer can use the public key in the eVIN certificate to decrypt the signature value, obtain the second verification data, and compare the first verification data with the second verification data to obtain the first identity verification result of the target vehicle.

[0028] In one possible implementation, before generating the verification request based on the eVIN certificate, the first verification data, and the signature value, the method further includes:

[0029] Receive the eVIN certificate sent by the eVIN issuing end through the eVIN registration and issuing end.

[0030] Thirdly, embodiments of this application provide a vehicle identity verification system, characterized in that the system includes:

[0031] The target vehicle is used to encrypt the first verification data using the private key corresponding to the eVIN certificate to obtain a signature value; it is also used to generate a verification request based on the eVIN certificate, the first verification data, and the signature value. The verification request includes the target vehicle's eVIN certificate, the first verification data, and the signature value. The eVIN certificate is generated by the eVIN issuer based on the target vehicle's eVIN code, and the eVIN code is generated by the eVIN issuer based on the target vehicle's VIN code; it is also used to send the verification request to the eVIN issuer through the eVIN application and eVIN server.

[0032] The eVIN issuing terminal is used to receive verification requests; it is also used to decrypt the signature value using the public key in the eVIN certificate to obtain the second verification data; and it is also used to compare the first verification data with the second verification data to obtain the first identity verification result of the target vehicle.

[0033] In one possible implementation, the system also includes an eVIN registration and issuance terminal; the target vehicle is also used to send a digital identity application request to the eVIN registration and issuance terminal;

[0034] The eVIN registration and issuance terminal is used to receive digital identity application requests sent by the target vehicle; it is also used to generate an eVIN application request based on the digital identity application and the VIN code of the target vehicle, the eVIN application request including the VIN code; and it is also used to send the eVIN application request to the eVIN issuing terminal.

[0035] The eVIN issuing terminal is also used to receive eVIN application requests, generate an eVIN code based on the VIN code and a first random number, generate an eVIN certificate based on the eVIN code (the eVIN certificate includes the eVIN code), and send the eVIN certificate to the target vehicle through the eVIN registration and issuing terminal.

[0036] The target vehicle is also used to receive the eVIN certificate.

[0037] Fourthly, embodiments of this application provide a vehicle authentication device applied to an eVIN issuing terminal, the device comprising:

[0038] The receiving module is used to receive the verification request sent by the target vehicle through the eVIN application and the eVIN server. The verification request includes the target vehicle's eVIN certificate, first verification data and signature value. The eVIN certificate is generated by the eVIN issuer based on the target vehicle's eVIN code, the eVIN code is generated by the eVIN issuer based on the target vehicle's VIN code, and the signature value is obtained by the target vehicle encrypting the first verification data using the private key corresponding to the eVIN certificate.

[0039] The decryption module is used to decrypt the signature value using the public key in the eVIN certificate to obtain the second verification data.

[0040] The comparison module is used to compare the first verification data with the second verification data to obtain the first identity verification result of the target vehicle.

[0041] Fifthly, embodiments of this application provide a vehicle authentication device applied to a target vehicle, characterized in that the device comprises:

[0042] The encryption module is used to encrypt the first verification data using the private key corresponding to the eVIN certificate to obtain the signature value;

[0043] The generation module is used to generate a verification request based on the eVIN certificate, the first verification data, and the signature value. The verification request includes the eVIN certificate of the target vehicle, the first verification data, and the signature value. The eVIN certificate is generated by the eVIN issuer based on the eVIN code of the target vehicle, and the eVIN code is generated by the eVIN issuer based on the VIN code of the target vehicle.

[0044] The sending module is used to send a verification request to the eVIN issuing end through the eVIN application and eVIN server, so that the eVIN issuing end can decrypt the signature value using the public key in the eVIN certificate to obtain the second verification data, and compare the first verification data with the second verification data to obtain the first identity verification result of the target vehicle.

[0045] In a sixth aspect, embodiments of this application provide an electronic device, the device comprising: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, it implements the method as described in the first aspect, any possible implementation of the first aspect, the second aspect, or any possible implementation of the second aspect.

[0046] In a seventh aspect, embodiments of this application provide a computer-readable storage medium storing computer program instructions that, when executed by a processor, implement the methods described in the first aspect, any possible implementation of the first aspect, the second aspect, or any possible implementation of the second aspect.

[0047] Eighthly, embodiments of this application provide a computer program product in which instructions, when executed by a processor of an electronic device, cause the electronic device to perform a method as described in the first aspect, any possible implementation of the first aspect, the second aspect, or any possible implementation of the second aspect.

[0048] This application provides a vehicle authentication method, apparatus, device, and storage medium. When authentication of a target vehicle is required, the eVIN issuing terminal receives an authentication request sent by the target vehicle through the eVIN application and eVIN server. The authentication request includes the target vehicle's eVIN certificate, first authentication data, and signature value. Then, the eVIN issuing terminal decrypts the signature value using the public key in the eVIN certificate to obtain second authentication data. Finally, the eVIN issuing terminal compares the first authentication data with the second authentication data to obtain the first authentication result of the target vehicle. The eVIN certificate is generated by the eVIN issuing terminal based on the target vehicle's eVIN code, and the eVIN code is generated by the eVIN issuing terminal based on the target vehicle's VIN code. Transmitting the eVIN certificate during the authentication process replaces directly transmitting the VIN code representing vehicle identity information, thereby preventing the VIN code from being intercepted. This achieves online vehicle identification without disclosing vehicle privacy information, improving the security of vehicle identity information. Attached Figure Description

[0049] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0050] Figure 1 This is a schematic diagram of a vehicle identity verification system provided in an embodiment of this application;

[0051] Figure 2 This is a schematic diagram of another vehicle authentication system provided in an embodiment of this application;

[0052] Figure 3 This application provides a schematic flowchart of a vehicle authentication method.

[0053] Figure 4 A schematic diagram of another vehicle authentication method provided in the application embodiment;

[0054] Figure 5 This is a schematic diagram of a vehicle authentication device provided in an embodiment of this application;

[0055] Figure 6 This is a schematic diagram of a vehicle authentication device provided in an embodiment of this application;

[0056] Figure 7 This is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0057] The features and exemplary embodiments of various aspects of this application will now be described in detail. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only configured to explain this application and are not configured to limit this application. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples of this application.

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

[0059] With the development of communication technology, the Internet of Vehicles (IoV) is becoming increasingly intelligent. The IoV is a vast interactive network composed of vehicle identity, location, speed, and route information. The confidentiality, authenticity, integrity, and non-repudiation of data communication within the IoV must be guaranteed. Currently, vehicle authentication mechanisms in the IoV generally use the vehicle's VIN (Vehicle Identification Number) as vehicle identification information, associating the VIN with vehicle classification attribute information to complete data communication. However, VIN-based authentication mechanisms require the transmission of the VIN, which is easily intercepted during transmission, leading to vehicle data leakage and poor security.

[0060] This application provides a vehicle authentication method, apparatus, device, and storage medium. When authentication of a target vehicle is required, the eVIN issuing terminal receives an authentication request sent by the target vehicle through the eVIN application and eVIN server. The authentication request includes the target vehicle's eVIN certificate, first authentication data, and signature value. Then, the eVIN issuing terminal decrypts the signature value using the public key in the eVIN certificate to obtain second authentication data. Finally, the eVIN issuing terminal compares the first authentication data with the second authentication data to obtain the first authentication result of the target vehicle. The eVIN certificate is generated by the eVIN issuing terminal based on the target vehicle's eVIN code. Transmitting the eVIN certificate during the authentication process replaces the direct transmission of the VIN code representing vehicle identity information, thereby preventing the VIN code from being intercepted. This achieves online vehicle identification without disclosing vehicle privacy information, improving the security of vehicle identity information.

[0061] To facilitate understanding, the terminology used in the embodiments of this application will be explained below.

[0062] The VIN code refers to the Vehicle Identification Number, also known as a car's ID number. It is determined according to national vehicle management standards and includes information such as the vehicle's manufacturer, year, model, body style and code, engine code, and assembly location.

[0063] eVIN is an electronic identification number issued to a vehicle based on cryptographic technology.

[0064] The eVIN issuing terminal is the terminal of the organization responsible for issuing eVINs to connected vehicles; it mainly refers to the terminal of the authoritative VIN code management organization.

[0065] The eVIN registration and issuance terminal is responsible for verifying the identity of connected vehicles. After the verification is approved, an eVIN certificate is issued to the connected vehicle. It mainly refers to the terminal of the original equipment manufacturer (OME) car company.

[0066] eVIN application terminal refers to the terminal of the organization that provides various eVIN applications for vehicle networking, such as charging pile applications and ETC toll collection.

[0067] The eVIN server connects to the eVIN issuing end and provides vehicle authentication services for various eVIN applications.

[0068] Asymmetric key algorithms consist of two keys: a public key and a private key. The public and private keys are a pair; if data is encrypted with the public key, it can only be decrypted with the corresponding private key; conversely, if data is encrypted with the private key, it can only be decrypted with the corresponding public key.

[0069] Digital signature: Encrypting data using a private key in an asymmetric key algorithm.

[0070] A digital certificate is a trusted digital document digitally signed by a nationally recognized, authoritative, credible, and impartial third-party certificate authority. The content of a digital certificate includes: certificate serial number, certificate holder name, certificate issuer name, certificate validity period, public key, and the certificate issuer's digital signature.

[0071] eVIN Certificate: A digital certificate whose certificate holder name is set to eVIN.

[0072] This application provides a vehicle identity verification system, such as... Figure 1As shown, the system 100 may include a target vehicle, an eVIN application, an eVIN server, and an eVIN issuing terminal. The target vehicle stores an eVIN certificate representing its identity information. The eVIN certificate is generated by the eVIN issuing terminal based on the target vehicle's eVIN code. When identity verification of the target vehicle is required, the target vehicle uses the private key corresponding to the pre-stored eVIN certificate to encrypt first verification data, obtaining a signature value. Based on the eVIN certificate, the first verification data, and the signature value, a verification request is generated and sent to the eVIN application. After receiving the verification request, the eVIN application sends a verification request to the eVIN server. After receiving the verification request, the eVIN server sends a verification request to the eVIN issuing terminal. The eVIN issuing terminal receives the verification request, uses the public key in the eVIN certificate to decrypt the signature value, obtaining second verification data, and compares the first verification data with the second verification data to obtain the first identity verification result of the target vehicle.

[0073] In the vehicle identity verification system provided in this application embodiment, the eVIN certificate is generated by the eVIN issuing end based on the vehicle identification VIN code of the target vehicle. The eVIN certificate is transmitted during the identity verification process, which replaces the direct transmission of the VIN code representing vehicle identity information, thereby avoiding the interception of the VIN code and improving the security of vehicle identity information.

[0074] In some embodiments, the vehicle authentication system 100 may further include an eVIN registration and issuance terminal, which stores the VIN code of the target vehicle; the target vehicle sends a digital identity application request to the eVIN registration and issuance terminal; the eVIN registration and issuance terminal receives the digital identity application request, generates an eVIN application request based on the digital identity application request and the VIN code of the target vehicle, the eVIN application request including the VIN code, and sends the eVIN application request to the eVIN issuing terminal; after receiving the eVIN application request, the eVIN issuing terminal generates an eVIN code based on the VIN code and a first random number, then generates an eVIN certificate based on the eVIN code, the eVIN certificate including the eVIN code, and then sends the eVIN certificate to the target vehicle through the eVIN registration and issuance terminal; the target vehicle receives the eVIN certificate.

[0075] The system provided in this application generates an eVIN certificate for the target vehicle, allowing the system to authenticate the vehicle based on the eVIN certificate, replacing the direct transmission of the VIN code representing vehicle identity information. This avoids the VIN code being intercepted and improves the security of vehicle identity information. Furthermore, the system provided in this application can generate an eVIN certificate for any vehicle with a VIN code, demonstrating strong versatility.

[0076] The following will combine Figure 3This application provides a detailed description of a vehicle authentication method based on its embodiments.

[0077] like Figure 3 As shown, the method may include the following steps:

[0078] S310, the target vehicle uses the private key corresponding to the eVIN certificate to encrypt the first verification data to obtain the signature value.

[0079] The target vehicle can be any vehicle with an eVIN certificate. The eVIN certificate is generated by the eVIN issuer based on the target vehicle's vehicle identification eVIN code. The eVIN code is generated by the eVIN issuer based on the target vehicle's VIN code. The first verification data can be a random number generated by the target vehicle.

[0080] The target vehicle pre-generates a private key. In scenarios where identity verification of the target vehicle is required, such as vehicle real-name authentication, electronic signature verification, and application registration or login, the target vehicle generates a random number and encrypts the random number using the private key to obtain the signature value.

[0081] S320: The target vehicle generates a verification request based on the eVIN certificate, the first verification data, and the signature value.

[0082] The target vehicle combines the eVIN certificate, first verification data, and signature value to obtain a verification request.

[0083] S330, the target vehicle sends a verification request to the eVIN application.

[0084] The eVIN application client has an application installed. When using the application client, the identity information of the target vehicle must be verified first. The target vehicle is connected to the eVIN application client.

[0085] The target vehicle sends a verification request to the eVIN application.

[0086] In one example, when an application related to a device that charges electric vehicles needs to charge a target vehicle, the target vehicle sends a verification request to the eVIN application that has the application related to the device that charges electric vehicles installed.

[0087] S340, the eVIN application sends a verification request to the eVIN server.

[0088] The eVIN server provides eVIN verification services for each eVIN application. The eVIN application receives the verification request sent by the target vehicle and sends the verification request to the eVIN server.

[0089] S350, the eVIN server sends a verification request to the eVIN issuer.

[0090] After receiving the verification request from the eVIN application, the eVIN server sends a verification request to the eVIN issuer.

[0091] In some embodiments, the eVIN application is pre-registered with the eVIN server. When the eVIN application sends a verification request to the eVIN server, it carries the eVIN application's credentials. After receiving the verification request from the eVIN application, the eVIN server first verifies the eVIN application's credentials. If the verification is successful, it indicates that the eVIN application is valid. Then, it sends a verification request to the eVIN issuer.

[0092] The method provided in this application embodiment only sends a verification request to the eVIN issuing end when the eVIN application is verified to be valid, thereby avoiding forwarding verification requests sent by invalid eVIN applications to the eVIN issuing end and preventing data leakage.

[0093] S360, the eVIN issuer uses the public key in the eVIN certificate to decrypt the signature value and obtain the second verification data.

[0094] The eVIN certificate carries a public key. The eVIN issuer uses the public key carried in the eVIN certificate to decrypt the signature value and obtain the second verification data.

[0095] In some embodiments, the eVIN server is pre-registered with the eVIN issuer. When the eVIN server sends a verification request to the eVIN issuer, it carries the eVIN server's credentials. After receiving the verification request, the eVIN issuer first verifies the eVIN server's credentials. If the verification passes, it indicates that the eVIN server is valid. Then, it uses the public key in the eVIN certificate to decrypt the signature value to obtain the second verification data.

[0096] The method provided in this application embodiment verifies the identity information of the target vehicle only when the eVIN issuing terminal verifies that the eVIN server is valid, thus avoiding data leakage.

[0097] S370, the eVIN issuer compares the first verification data with the second verification data to obtain the first identity verification result of the target vehicle.

[0098] The eVIN issuer compares the first verification data with the second verification data. When the first verification data and the second verification data are the same, the first identity verification result of the target vehicle is successful; when the first verification data and the second verification data are different, the first identity verification result of the target vehicle is unsuccessful.

[0099] In some embodiments, after obtaining the first authentication result, the eVIN issuing terminal also sends the first authentication result to the target vehicle through the eVIN server and the eVIN application terminal.

[0100] The method provided in this application embodiment, when requiring identity verification of a target vehicle, involves the eVIN issuing terminal receiving a verification request sent by the target vehicle through the eVIN application and eVIN server. The verification request includes the target vehicle's eVIN certificate, first verification data, and a signature value. Then, the eVIN issuing terminal decrypts the signature value using the public key in the eVIN certificate to obtain second verification data. Finally, the eVIN issuing terminal compares the first verification data with the second verification data to obtain the target vehicle's first identity verification result. The eVIN certificate is generated by the eVIN issuing terminal based on the target vehicle's eVIN code, and the eVIN code is generated by the eVIN issuing terminal based on the target vehicle's VIN code. Transmitting the eVIN certificate during the identity verification process replaces the direct transmission of the VIN code representing vehicle identity information, thereby preventing the VIN code from being intercepted. This achieves online vehicle identification without disclosing vehicle privacy information, improving the security of vehicle identity information.

[0101] In some embodiments, the verification request may further include the encrypted VIN code of the target vehicle, and the eVIN certificate includes the eVIN code; the vehicle authentication method may also include the following steps:

[0102] When the first authentication result is successful, the correspondence between the eVIN code and the VIN code is compared with the target correspondence between the eVIN code and the VIN code of the target vehicle to obtain the second authentication result of the target vehicle.

[0103] After generating the eVIN code based on the VIN code, the eVIN issuing terminal stores the correspondence between the VIN code and the eVIN code of the target vehicle.

[0104] In the scenario of authenticating a target vehicle, the target vehicle encrypts its own VIN code to obtain the encrypted VIN code. The VIN code, eVIN certificate, first verification data, and signature value are combined to generate an authentication request. Upon receiving the authentication request, the eVIN issuer decrypts the encrypted VIN code to obtain the VIN code. If the first authentication result is successful, the eVIN issuer compares the target vehicle's sent eVIN code with the stored VIN code-eVIN code correspondence. If the target vehicle's sent eVIN code matches the stored VIN code-eVIN code correspondence, the target vehicle's second authentication result is successful; otherwise, the target vehicle's second authentication result is unsuccessful.

[0105] In the verification request provided in this application embodiment, the VIN code is encrypted, which can protect the security of the VIN code during transmission.

[0106] In some embodiments, the eVIN certificate includes an eVIN code, which is generated by the eVIN issuer based on the VIN code and a first random number. The vehicle authentication method may further include the following steps:

[0107] First, based on the correspondence between the eVIN code and the VIN code, determine the VIN code corresponding to the eVIN code.

[0108] Multiple applications on the eVIN application side are registered on the eVIN server. When a user uses application A among these applications for the first time, application A registers an account for the target vehicle, and the eVIN application side records the target vehicle's VIN code. When the user uses application B among these applications, the target vehicle sends a login request without registration through the eVIN application side. After receiving the login request without registration, the eVIN issuing terminal determines the VIN code corresponding to the eVIN code based on the mapping relationship between eVIN codes and VIN codes recorded in the eVIN issuing terminal's database.

[0109] Secondly, an identity information index value is generated based on the VIN code.

[0110] The eVIN issuing terminal generates an identity information index value based on the VIN code. The identity information index value is generated from the VIN code of the target vehicle and includes the VIN code, which cannot be reversed.

[0111] In some embodiments, the target vehicle sends a verification request to the eVIN application. Upon receiving the verification request, the eVIN application combines the identifier of the target application with the verification request and sends it to the eVIN issuing end. The target application is an application registered with the eVIN server but not previously registered by the user. The eVIN issuing end uses a second random number to encrypt the identifier and VIN code of the target application to obtain an identity information index value.

[0112] In one example, the identifier of the target application, the VIN code of the target vehicle, and a second random number are combined and hashed using algorithms to generate an identity information index value.

[0113] Next, the eVIN issuing end sends the identity information index value to the eVIN application end through the eVIN server.

[0114] The eVIN issuer sends the identity information index value to the eVIN server, and the eVIN server forwards the identity information index value to the eVIN application.

[0115] Finally, the eVIN application determines the customer category of the target vehicle based on the identity information index value.

[0116] The target vehicle can be categorized as either an existing customer or a new customer. Existing customers indicate that the target vehicle has already been registered using the eVIN code.

[0117] After receiving the identity information index value, the eVIN application retrieves the target vehicle's account based on the identity information index value. The eVIN application account uses the same parameters (application identifier, vehicle VIN code, and a second random number) and password algorithm to generate identity information index values ​​for all existing customers. When the identity information index value pre-stored by the eVIN application includes the target vehicle's identity information index value, the target vehicle is considered an existing customer and is granted permission to log in to the target application. Therefore, users can log in to the target vehicle's account in the target application without registration.

[0118] The method provided in this application embodiment involves multiple applications registered on the eVIN server. When a user logs into one of the unregistered target applications, the target vehicle first sends a login request without registration. When the target application determines that the target vehicle is an existing customer, the user can log in to the target application without registration, thus improving the user experience.

[0119] In some embodiments, before S310: receiving the verification request sent by the target vehicle through the eVIN application and eVIN server, such as Figure 4 As shown, the method also includes the following steps:

[0120] S410, the target vehicle generates a digital identity application request based on the target key.

[0121] The target key may include a public key and a private key. The target vehicle generates a public key and a private key, and generates a digital identity application request based on the public key and the private key.

[0122] S420, the eVIN registration issuer receives the digital identity application request sent by the target vehicle.

[0123] S430, the eVIN registration and issuance terminal generates an eVIN application request based on the digital identity application request and the VIN code of the target vehicle.

[0124] The eVIN registration and issuance terminal combines the digital identity application request and the VIN code of the target vehicle to obtain the eVIN application request, and then sends the eVIN application request to the eVIN issuing terminal.

[0125] The eVIN request includes the VIN code.

[0126] S440, the eVIN issuing terminal receives the eVIN application request sent by the eVIN registration and issuing terminal.

[0127] Compare the VIN code in the eVIN request with at least one pre-stored VIN code. If the VIN code in the eVIN request matches one of the at least one pre-stored VIN codes,

[0128] S450, the eVIN issuing terminal generates an eVIN code based on the VIN code and the first random number.

[0129] The eVIN issuer compares the VIN code in the eVIN request with at least one pre-stored VIN code. When the VIN code in the eVIN request is the same as one of the pre-stored VIN codes, it generates an eVIN code by hashing the VIN code in the eVIN request and a first random number.

[0130] In one example, the first random number may include at least one set of random numbers, and the eVIN issuer generates the eVIN code using the following formula:

[0131] Among them, random number a, random number b, and random number c can be the same random number or different random numbers.

[0132] S460, the eVIN issuing terminal generates an eVIN certificate based on the eVIN code.

[0133] The eVIN issuing terminal issues digital certificates by filling the eVIN code into the certificate name field, thus obtaining the eVIN certificate, which includes the eVIN code.

[0134] S470, the eVIN issuing end sends the eVIN certificate to the eVIN registration and issuing end.

[0135] S480, the eVIN registration and issuance terminal sends the eVIN certificate to the target vehicle.

[0136] After receiving the eVIN certificate, the eVIN registration and issuance terminal sends the eVIN certificate to the target vehicle.

[0137] S490, the target vehicle receives the eVIN certificate.

[0138] The target vehicle receives and stores the eVIN certificate. The eVIN certificate is generated based on the target vehicle's VIN code. The VIN code represents the target vehicle's identity information, so the eVIN certificate can also represent the target vehicle's identity information and is used for the target vehicle's authentication.

[0139] The method provided in this application generates an eVIN certificate for the target vehicle, which can be used to authenticate the target vehicle. This replaces the existing method of directly transmitting the VIN code representing vehicle identity information during authentication, thereby preventing the VIN code from being intercepted and improving the security of vehicle identity information. Moreover, the method provided in this application can generate an eVIN certificate for any vehicle with a VIN code, making it highly versatile.

[0140] In some embodiments, after the eVIN certificate is generated based on the eVIN code at the S460: eVIN issuing end, the method may further include the following steps:

[0141] Generate the target correspondence between the VIN code and the eVIN code.

[0142] The eVIN issuing terminal generates and stores the target vehicle's VIN code and the target eVIN code to correspond.

[0143] The method provided in this application generates a target correspondence between the VIN code and eVIN code of a target vehicle. Since each target vehicle's VIN code is unique, the target correspondence between the VIN code and eVIN code of each target vehicle is also unique. The target vehicle can be authenticated based on the target correspondence between the VIN code and eVIN code, providing a basis for authenticating any vehicle with an eVIN certificate.

[0144] This application also provides a vehicle authentication device, applied to the eVIN issuing terminal, such as... Figure 5 As shown, the device 500 includes a receiving module 510, a decryption module 520, and a comparison module 530.

[0145] The receiving module 510 is used to receive a verification request sent by the target vehicle through the eVIN application terminal and the eVIN server terminal. The verification request includes the target vehicle's eVIN certificate, first verification data, and signature value. The eVIN certificate is generated by the eVIN issuing terminal based on the target vehicle's eVIN code, the eVIN code is generated by the eVIN issuing terminal based on the target vehicle's VIN code, and the signature value is obtained by the target vehicle encrypting the first verification data using the private key corresponding to the eVIN certificate.

[0146] The decryption module 520 is used to decrypt the signature value using the public key in the eVIN certificate to obtain the second verification data.

[0147] The comparison module 530 is used to compare the first verification data with the second verification data to obtain the first identity verification result of the target vehicle.

[0148] The apparatus provided in this application embodiment receives a verification request sent by a target vehicle through an eVIN application and an eVIN server. The verification request includes the target vehicle's eVIN certificate, first verification data, and a signature value. Then, the signature value is decrypted using the public key in the eVIN certificate to obtain second verification data. Finally, the first verification data and the second verification data are compared to obtain the first identity verification result of the target vehicle. The eVIN certificate is generated by the apparatus based on the target vehicle's vehicle identification number (VIN). Transmitting the eVIN certificate during the identity verification process replaces the direct transmission of the VIN code representing vehicle identity information, thereby preventing the VIN code from being intercepted and improving the security of vehicle identity information.

[0149] In some embodiments, the verification request may also include the encrypted VIN code of the target vehicle, and the eVIN certificate includes the eVIN code, which is generated by the eVIN issuer based on the VIN code and a first random number.

[0150] The comparison module 530 can also be used to compare the correspondence between the eVIN code and the VIN code with the target correspondence between the eVIN code and the VIN code of the target vehicle when the first authentication result is successful, in order to obtain the second authentication result of the target vehicle.

[0151] In the verification request provided in this application embodiment, the VIN code is encrypted, which can protect the security of the VIN code during transmission.

[0152] The device 500 may also include a generation module 540 and a transmission module 550.

[0153] The generation module 540 is used to generate an identity information index value based on the VIN code.

[0154] The identity information index value may include the application identifier and VIN code in the eVIN application, as well as a second random number used to encrypt the identifier and VIN code of the target application.

[0155] The sending module 550 is used to send the identity information index value to the eVIN application terminal so that the eVIN application terminal can determine the customer category of the target vehicle based on the identity information index value.

[0156] The device provided in this application embodiment allows multiple applications to be registered on the eVIN server. When a user logs in to one of the target applications that has not been registered, the target vehicle first sends a login request without registration. When the target application determines that the target vehicle is an existing customer, the user can log in to the target application without registration, thereby improving the user experience.

[0157] In some embodiments, the receiving module 510 can also be used to receive an eVIN application request sent by the eVIN registration and issuing terminal.

[0158] An eVIN application request is generated based on the digital identity application request and the VIN code of the target vehicle when the eVIN registration and issuing terminal receives the digital identity application request sent by the target vehicle. The eVIN application request includes the VIN code.

[0159] The device 500 may also include a generation module 540 and a transmission module 550.

[0160] The generation module 540 is used to generate an eVIN code based on the VIN code and a first random number; it is also used to generate an eVIN certificate based on the eVIN code, wherein the eVIN certificate includes the eVIN code.

[0161] The sending module 550 is used to send the eVIN certificate to the target vehicle through the eVIN registration issuer.

[0162] The apparatus provided in this application generates an eVIN certificate for the target vehicle, enabling vehicle authentication based on the eVIN certificate. This replaces the existing method of directly transmitting the VIN code representing vehicle identity information during authentication, thereby preventing the VIN code from being intercepted and improving the security of vehicle identity information. Furthermore, the method provided in this application can generate an eVIN certificate for any vehicle with a VIN code, demonstrating strong versatility.

[0163] In some embodiments, the apparatus 500 may further include a generation module 540.

[0164] The generation module 540 is used to generate the target correspondence between the VIN code and the eVIN code.

[0165] The apparatus provided in this application generates a target correspondence between the VIN code and eVIN code of a target vehicle. Since each target vehicle's VIN code is unique, the target correspondence between the VIN code and eVIN code of each target vehicle is also unique. The target vehicle can be authenticated based on the target correspondence between the VIN code and eVIN code, providing a basis for authenticating any vehicle with an eVIN certificate.

[0166] The vehicle authentication device provided in this application embodiment performs... Figure 3 and Figure 4 The various steps executed by the eVIN issuing terminal, and the technical effects that improve the security of vehicle identity information, will not be elaborated here for the sake of brevity.

[0167] This application also provides another vehicle authentication device, applied to a target vehicle, such as... Figure 6As shown, the device 600 may include an encryption module 610, a generation module 620, and a sending module 630.

[0168] The encryption module 610 is used to encrypt the first verification data using the private key corresponding to the eVIN certificate to obtain the signature value.

[0169] The generation module 620 is used to generate a verification request based on the eVIN certificate, the first verification data, and the signature value. The verification request includes the eVIN certificate of the target vehicle, the first verification data, and the signature value. The eVIN certificate is generated by the eVIN issuer based on the eVIN code of the target vehicle, and the eVIN code is generated by the eVIN issuer based on the VIN code of the target vehicle.

[0170] The sending module 630 is used to send verification requests to the eVIN issuing end through the eVIN application and eVIN server.

[0171] The public key in the eVIN certificate is used to decrypt the signature value at the eVIN issuing end to obtain the second verification data. The first verification data and the second verification data are compared to obtain the first identity verification result of the target vehicle.

[0172] The device eVIN application terminal and eVIN server provided in this application send a verification request to the eVIN issuing terminal. The verification request includes the target vehicle's eVIN certificate, first verification data and signature value. The eVIN certificate is transmitted during the identity verification process, which replaces the direct transmission of the VIN code representing the vehicle's identity information, thereby avoiding the interception of the VIN code and improving the security of the vehicle's identity information.

[0173] In some embodiments, the device 600 may further include a receiving module 640.

[0174] The receiving module 640 is used to receive the eVIN certificate sent by the eVIN issuing end through the eVIN registration and issuing end.

[0175] The device provided in this application embodiment receives an eVIN certificate, which is generated based on the VIN code of the target vehicle. The VIN code represents the identity information of the target vehicle, so the eVIN certificate can also represent the identity information of the target vehicle and is used for the identity verification of the target vehicle, providing a basis for the identity verification of the target vehicle.

[0176] The vehicle authentication device provided in this application embodiment performs... Figure 3 and Figure 4 The various steps executed on the target vehicle, and the technical effects that improve the security of vehicle identity information, will not be elaborated here for the sake of brevity.

[0177] Figure 7A schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application is shown.

[0178] An electronic device may include a processor 701 and a memory 702 storing computer program instructions.

[0179] Specifically, the processor 701 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0180] Memory 702 may include mass storage for data or instructions. For example, and not limitingly, memory 702 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 702 may include removable or non-removable (or fixed) media. Where appropriate, memory 702 may be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, memory 702 is non-volatile solid-state memory.

[0181] Memory may include read-only memory (ROM), random access memory (RAM), disk storage media devices, optical storage media devices, flash memory devices, and electrical, optical, or other physical / tangible memory storage devices. Therefore, typically, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the methods according to one aspect of this disclosure.

[0182] The processor 701 implements any of the vehicle authentication methods described in the above embodiments by reading and executing computer program instructions stored in the memory 702.

[0183] In one example, the electronic device may also include a communication interface 703 and a bus 710. For example, Figure 7 As shown, the processor 701, memory 702, and communication interface 703 are connected through bus 710 and complete communication with each other.

[0184] The communication interface 703 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.

[0185] Bus 710 includes hardware, software, or both, that couples components of an online data traffic metering device together. For example, and not limitingly, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 310 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, any suitable bus or interconnect is contemplated herein.

[0186] The electronic device can execute the vehicle authentication method in the embodiments of this application, thereby achieving a combination Figure 3 and Figure 4 The description refers to the vehicle authentication method performed by the eVIN issuer or the target vehicle.

[0187] Furthermore, in conjunction with the vehicle authentication methods in the above embodiments, this application embodiment can provide a computer-readable storage medium for implementation. This computer-readable storage medium stores computer program instructions; when executed by a processor, these computer program instructions implement any one of the vehicle authentication methods executed by the eVIN issuing end or the target vehicle in the above embodiments.

[0188] In conjunction with the vehicle authentication methods described in the above embodiments, this application can provide a computer program product for implementation. When the instructions in the computer program product are executed by the processor of an electronic device, they implement any of the vehicle authentication methods executed by the eVIN issuing end or the target vehicle in the above embodiments.

[0189] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0190] The functional blocks shown in the above-described structural diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0191] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0192] The above description is merely a specific implementation of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

Claims

1. A vehicle authentication method, applied to an electronic vehicle identification number (eVIN) issuing terminal, characterized in that, The method includes: The system receives a verification request sent by the target vehicle through the eVIN application and eVIN server. The verification request includes the target vehicle's eVIN certificate, first verification data, and a signature value. The eVIN certificate is generated by the eVIN issuer based on the target vehicle's eVIN code. The eVIN code is generated by the eVIN issuer based on the target vehicle's vehicle identification number (VIN). The signature value is obtained by the target vehicle encrypting the first verification data using the private key corresponding to the eVIN certificate. The signature value is decrypted using the public key in the eVIN certificate to obtain the second verification data; By comparing the first verification data with the second verification data, the first identity verification result of the target vehicle is obtained; The receipt of the verification request sent by the target vehicle through the eVIN application and eVIN server includes: The system receives a verification request sent by the eVIN server when the eVIN application's credentials are verified. The verification request is sent by the target vehicle to the eVIN application. When the eVIN application sends the verification request to the eVIN server, it carries the eVIN application's credentials. The eVIN application is pre-registered with the eVIN server. After receiving the verification request sent by the eVIN application, the eVIN server first verifies the eVIN application's credentials. Before decrypting the signature value using the public key in the eVIN certificate to obtain the second verification data, the method further includes: When receiving the verification request sent by the eVIN server, the eVIN server's credentials are carried, and the eVIN server is pre-registered with the eVIN issuing end; Verify the eVIN server's credentials; The step of decrypting the signature value using the public key in the eVIN certificate to obtain the second verification data includes: When the eVIN server verifies the credentials, it uses the public key in the eVIN certificate to decrypt the signature value and obtain the second verification data.

2. The method according to claim 1, characterized in that, The verification request also includes the encrypted VIN code of the target vehicle, and the eVIN certificate includes the eVIN code; the method further includes: When the first authentication result is successful, the correspondence between the eVIN code and the VIN code is compared with the target correspondence between the eVIN code and the VIN code of the target vehicle to obtain the second authentication result of the target vehicle.

3. The method according to claim 1, characterized in that, The eVIN certificate includes an eVIN code, which is generated by the eVIN issuing end based on the eVIN code and a first random number. The method further includes: Based on the correspondence between the eVIN code and the VIN code, determine the VIN code corresponding to the eVIN code; Based on the VIN code, generate an identity information index value; The identity information index value is sent to the eVIN application terminal so that the eVIN application terminal can determine the customer category of the target vehicle based on the identity information index value.

4. The method according to claim 3, characterized in that, The identity information index value includes the identifier of the target application in the eVIN application terminal, the VIN code, and a second random number used to encrypt the identifier of the target application and the VIN code.

5. The method according to claim 1, characterized in that, Before receiving the verification request sent by the target vehicle through the eVIN application and eVIN server, the method further includes: The system receives a digital identity application request sent by the eVIN registration and issuing terminal. The eVIN application request is generated based on the digital identity application request and the VIN code of the target vehicle when the eVIN registration and issuing terminal receives the digital identity application request sent by the target vehicle. The eVIN application request includes the VIN code. The eVIN code is generated based on the VIN code and the first random number; The eVIN certificate is generated based on the eVIN code, and the eVIN certificate includes the eVIN code; The eVIN certificate is sent to the target vehicle through the eVIN registration and issuance terminal.

6. The method according to claim 5, characterized in that, The method further includes: Generate the target correspondence between the VIN code and the eVIN code.

7. A vehicle authentication method, applied to a target vehicle, characterized in that, The method includes: The first verification data is encrypted using the private key corresponding to the eVIN certificate to obtain the signature value; A verification request is generated based on the eVIN certificate, the first verification data, and the signature value. The verification request includes the eVIN certificate of the target vehicle, the first verification data, and the signature value. The eVIN certificate is generated by the eVIN issuing end based on the eVIN code of the target vehicle, and the eVIN code is generated by the eVIN issuing end based on the VIN code of the target vehicle. The verification request is sent to the eVIN issuing end through the eVIN application and eVIN server, so that the eVIN issuing end can decrypt the signature value using the public key in the eVIN certificate to obtain the second verification data, and compare the first verification data with the second verification data to obtain the first identity verification result of the target vehicle. Sending the verification request to the eVIN issuing end through the eVIN application and eVIN server includes: A verification request is sent to the eVIN application, so that the eVIN application carries its credentials when sending the verification request to the eVIN server. The eVIN application is pre-registered with the eVIN server. After receiving the verification request from the eVIN application, the eVIN server first verifies the eVIN application's credentials. When the eVIN application's credentials are verified successfully, the eVIN server sends the verification request to the eVIN issuing end, so that the eVIN issuing end carries its own credentials when receiving the verification request from the eVIN server. The eVIN server is pre-registered with the eVIN issuing end. The eVIN server then verifies its own credentials. When the eVIN server's credentials are verified successfully, the signature value is decrypted using the public key in the eVIN certificate to obtain the second verification data.

8. The method according to claim 7, characterized in that, Before generating the verification request based on the eVIN certificate, the first verification data, and the signature value, the method further includes: Receive the eVIN certificate sent by the eVIN issuing terminal through the eVIN registration and issuing terminal.

9. A vehicle identity verification system, characterized in that, The system includes: The target vehicle is used to encrypt first verification data using the private key corresponding to the eVIN certificate to obtain a signature value; it is also used to generate a verification request based on the eVIN certificate, the first verification data, and the signature value. The verification request includes the target vehicle's eVIN certificate, the first verification data, and the signature value. The eVIN certificate is generated by the eVIN issuing end based on the target vehicle's eVIN code, and the eVIN code is generated by the eVIN issuing end based on the target vehicle's VIN code; it is also used to send the verification request to the eVIN issuing end through the eVIN application end and the eVIN server end; the process of... The process of sending the verification request from the eVIN application and eVIN server to the eVIN issuing end includes: sending a verification request to the eVIN application so that the eVIN application carries its credentials when sending the verification request to the eVIN server; the eVIN application is pre-registered with the eVIN server; after receiving the verification request from the eVIN application, the eVIN server first verifies the credentials of the eVIN application; and when the credentials of the eVIN application are verified successfully, the eVIN server sends the verification request to the eVIN issuing end. The eVIN issuing terminal is configured to receive the verification request; further configured to decrypt the signature value using the public key in the eVIN certificate to obtain second verification data; further configured to compare the first verification data with the second verification data to obtain the first identity verification result of the target vehicle; further configured to receive the eVIN server's credentials carried when the eVIN server sends the verification request, and verify the eVIN server's credentials, wherein the eVIN server is pre-registered with the eVIN issuing terminal; the step of decrypting the signature value using the public key in the eVIN certificate to obtain the second verification data includes: when the eVIN server's credentials are verified successfully, decrypting the signature value using the public key in the eVIN certificate to obtain the second verification data.

10. The system according to claim 9, characterized in that, The system also includes an eVIN registration and issuance terminal; the target vehicle is also used to send a digital identity application request to the eVIN registration and issuance terminal. The eVIN registration and issuance terminal is used to receive a digital identity application request sent by the target vehicle; it is also used to generate an eVIN application request based on the digital identity application and the VIN code of the target vehicle, the eVIN application request including the VIN code; and it is also used to send the eVIN application request to the eVIN issuing terminal. The eVIN issuing terminal is also used to receive the eVIN application request, generate an eVIN code based on the VIN code and a first random number, generate an eVIN certificate based on the eVIN code, the eVIN certificate including the eVIN code, and send the eVIN certificate to the target vehicle through the eVIN registration and issuing terminal. The target vehicle is also used to receive the eVIN certificate.

11. A vehicle authentication device, applied to an eVIN issuing terminal, characterized in that, The device includes: The receiving module is used to receive a verification request sent by the target vehicle through the eVIN application terminal and the eVIN server terminal. The verification request includes the target vehicle's eVIN certificate, first verification data, and a signature value. The eVIN certificate is generated by the eVIN issuing terminal based on the target vehicle's vehicle identification eVIN code. The eVIN code is generated by the eVIN issuing terminal based on the target vehicle's VIN code. The signature value is obtained by the target vehicle encrypting the first verification data using the private key corresponding to the eVIN certificate. The decryption module is used to decrypt the signature value using the public key in the eVIN certificate to obtain the second verification data; The comparison module is used to compare the first verification data with the second verification data to obtain the first identity verification result of the target vehicle; The receiving module is specifically used to receive a verification request sent by the eVIN server when the eVIN application's credentials are verified successfully. The verification request is sent by the target vehicle to the eVIN application. When the eVIN application sends the verification request to the eVIN server, it carries the eVIN application's credentials. The eVIN application is pre-registered with the eVIN server. After the eVIN server receives the verification request sent by the eVIN application, it first verifies the eVIN application's credentials. The receiving module is also configured to receive the eVIN server's credentials carried when the eVIN server sends the verification request, wherein the eVIN server is pre-registered with the eVIN issuing end; and to verify the eVIN server's credentials. The decryption module is specifically used to decrypt the signature value using the public key in the eVIN certificate when the credential verification of the eVIN server is successful, in order to obtain the second verification data.

12. A vehicle authentication device, applied to a target vehicle, characterized in that, The device includes: The encryption module is used to encrypt the first verification data using the private key corresponding to the eVIN certificate to obtain the signature value; The generation module is used to generate a verification request based on the eVIN certificate, the first verification data, and the signature value. The verification request includes the eVIN certificate of the target vehicle, the first verification data, and the signature value. The eVIN certificate is generated by the eVIN issuing end based on the eVIN code of the target vehicle, and the eVIN code is generated by the eVIN issuing end based on the VIN code of the target vehicle. The sending module is used to send the verification request to the eVIN issuing end through the eVIN application end and the eVIN server end, so that the eVIN issuing end can decrypt the signature value using the public key in the eVIN certificate to obtain the second verification data, and compare the first verification data with the second verification data to obtain the first identity verification result of the target vehicle. The sending module is specifically used to send a verification request to the eVIN application, so that when the eVIN application sends the verification request to the eVIN server, it carries the eVIN application's credentials. The eVIN application is pre-registered with the eVIN server. After receiving the verification request from the eVIN application, the eVIN server first verifies the eVIN application's credentials. When the eVIN application's credentials are verified successfully, the eVIN server sends the verification request to the eVIN issuing end, so that when the eVIN issuing end receives the verification request from the eVIN server, it carries the eVIN server's credentials. The eVIN server is pre-registered with the eVIN issuing end. The eVIN server verifies the eVIN server's credentials. When the eVIN server's credentials are verified successfully, it uses the public key in the eVIN certificate to decrypt the signature value to obtain the second verification data.

13. An electronic device, characterized in that, The device includes: a processor and a memory storing computer program instructions; the processor, when executing the computer program instructions, implements the vehicle authentication method as described in any one of claims 1-6 or 7-8.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions that, when executed by a processor, implement the vehicle authentication method as described in any one of claims 1-6 or 7-8.

15. A computer program product, characterized in that, When the instructions in the computer program product are executed by the processor of the electronic device, the electronic device causes the electronic device to perform the vehicle authentication method as described in any one of claims 1-6 or 7-8.

Images