Security authentication system and method for data transmission of vehicle-mounted equipment

Abstract

The invention discloses a security authentication system and method for data transmission of vehicle-mounted equipment, and the system comprises an identity authentication module which is used for issuing digital certificates to the vehicle-mounted equipment and a remote data center through a public key infrastructure system, and achieving the identity authentication; the data encryption module is used for encrypting the transmitted data by using a secure socket layer or transport layer security protocol to ensure the confidentiality of the data; the data integrity verification module is used for performing abstract calculation on the data by using a hash function in a data transmission process to generate a data fingerprint; the access control module is used for implementing a strict access control strategy in the remote data center and limiting the access authority to the vehicle data; and the log auditing module is used for deploying a log auditing system in the vehicle-mounted equipment and the remote data center and recording all operations and behaviors related to security authentication. According to the invention, the vehicle-mounted equipment can be ensured to have high security during data transmission.

Description

Technical Field

[0001] The present invention relates to the technical field of vehicle-mounted device data transmission, and in particular to a security authentication system and method for vehicle-mounted device data transmission. Background Art

[0002] The authentication mechanism for secure remote transmission of vehicle-mounted device data is a key step in ensuring the authenticity of the identities of both parties in communication and the integrity of data. The following are the existing technologies for secure remote transmission of vehicle-mounted device data authentication mechanisms: 1. Public Key Infrastructure (PKI) and Digital Certificates: The PKI system provides identity authentication for both communicating parties through digital certificates. In the remote transmission of data from vehicle-mounted devices, both the vehicle and the remote server will have digital certificates issued by a trusted third party (such as a certificate authority). These certificates contain public keys, certificate holder information, issuing authority information, etc., and are signed with private keys to ensure their authenticity and integrity. When establishing a connection, the communicating parties will exchange digital certificates and verify the certificates using the public key. If the verification is successful, the identity of the other party is confirmed to be authentic, and subsequent data transmission can be carried out.

[0003] 2. HTTPS TLS / SSL handshake protocol: The TLS / SSL protocol provides the ability to communicate securely in an open network. In the remote transmission of vehicle-mounted device data, the TLS / SSL handshake protocol is used to establish an encrypted communication channel between the vehicle and the remote server. During the handshake process, the two parties will exchange information such as certificates and keys, and negotiate a session key for subsequent data encryption and decryption. This process ensures the confidentiality, integrity and authenticity of the communication.

[0004] 3. Dynamic token authentication: Dynamic token authentication is a time-based or event-based authentication mechanism. In the remote transmission of vehicle-mounted device data, the vehicle or remote server can generate a dynamic token containing information such as timestamp and random number, and send it to the other party together with the request. After receiving the request, the receiver will verify the validity of the token (such as checking whether the timestamp has expired, whether the random number matches, etc.) to confirm the authenticity of the request. If the verification is successful, subsequent data transmission is allowed.

[0005] The authentication mechanism for remote secure transmission of vehicle-mounted device data is a complex system that requires consideration of multiple factors, including authentication efficiency, authentication security, and authentication reliability.

[0006] There are some potential disadvantages of public key infrastructure (PKI) and digital certificate authentication: 1. Reliance on third-party trust: The PKI system relies on a third-party certificate authority (CA) to issue and manage digital certificates. However, if the CA itself has security issues or is attacked, all certificates it issues will lose trust. In addition, the CA may abuse its power to issue insecure certificates or refuse to issue legitimate certificates, which will also threaten the security of the PKI system.

[0007] 2. Difficulty in key management: In a PKI system, the security of private keys is of vital importance. However, the loss, disclosure or theft of private keys may lead to serious security issues. In addition, the management and distribution of private keys also need to be handled with caution to ensure that only authorized users can access and use private keys.

[0008] Disadvantages of TLS / SSL handshake protocol: 1. HTTPS uses TLS / SSL protocol to encrypt its communication content. The HTTPS handshake process is an important security step used to establish a secure connection between the client and the server. This process includes identity authentication, encryption algorithm negotiation, and key exchange. Therefore, when establishing a new HTTPS connection, handshake and key exchange are required, which greatly affects the efficiency of transmission.

[0009] Dynamic token authentication, as a time- or event-based authentication mechanism, provides strong security protection, but it also has some disadvantages: 1. Synchronization problem: Dynamic tokens are usually bound to time or events, which requires that the time between the client (such as the user's device) and the server must be synchronized. When the time error exceeds a certain range, the token may become invalid, affecting the user experience and service availability.

[0010] 2. Dependence on hardware devices: Dynamic tokens usually require users to have a specific hardware device, which increases the burden on users. Summary of the invention

[0011] In view of the above technical problems, the present invention provides a security authentication system and method for vehicle-mounted device data transmission.

[0012] The present invention is implemented by adopting the following technical scheme: a security authentication system for vehicle-mounted device data transmission, including an identity authentication module, a data encryption module, a data integrity verification module, an access control module and a log audit module, wherein: The identity authentication module is used to issue digital certificates to vehicle-mounted devices and remote data centers using the public key infrastructure system to achieve identity authentication; Data encryption module, used to encrypt the transmitted data using the secure socket layer or transport layer security protocol to ensure the confidentiality of the data; The data integrity check module is used to calculate the data summary using the hash function during data transmission to generate the data fingerprint; Access control module, which is used to implement strict access control policies in remote data centers to limit access rights to vehicle data; The log audit module is used to deploy the log audit system in vehicle-mounted devices and remote data centers to record all operations and behaviors related to security authentication.

[0013] Furthermore, when the vehicle-mounted device and the remote data center establish a connection, the identity authentication module exchanges digital certificates with each other to verify the identity of the other party, and uses digital signature technology to ensure the authenticity of the identity information during the transmission process.

[0014] Furthermore, the data encryption module adopts a combination of symmetric encryption algorithm and asymmetric encryption algorithm to improve encryption efficiency and security, and regularly replaces encryption keys to prevent security risks caused by key leakage.

[0015] Furthermore, the data integrity verification module transmits the data fingerprint together with the original data. After receiving the data, the receiver recalculates the data fingerprint and compares it with the received data fingerprint to ensure that the data has not been tampered with during transmission.

[0016] Furthermore, the access control module adopts a role-based access control strategy to ensure that only authorized users or systems can access vehicle data, and regularly reviews and updates the access control strategy to address potential security risks.

[0017] Furthermore, the log audit module regularly audits and analyzes logs to discover potential security risks and attack behaviors, and retains log information for verification and tracing, providing strong support for security incident investigations.

[0018] A method for secure authentication of vehicle-mounted device data transmission is implemented based on the above-mentioned secure authentication system for vehicle-mounted device data transmission, and comprises the following steps: S1: Certificate application and replacement; S2: Vehicle equipment and service platform certification; S3: Communication authentication between vehicle-mounted devices.

[0019] Furthermore, step S1 includes the following sub-steps: S11: The vehicle-mounted device calls Auth_SDK to initiate a TLS connection to the CA management center through the pre-made root certificate and pre-made certificate; S12: Auth_SDK generates user private key and certificate request information; S13: Auth_SDK uses the certificate request information to initiate a registration and certificate request to the CA management center; S14: The CA management center receives the request to verify the device and then calls the PKI service to issue a certificate; S15: The CA management center sends the signed device certificate file to Auth_SDK, and Auth_SDK receives the certificate and saves the certificate file.

[0020] Furthermore, step S2 includes the following sub-steps: S21: The vehicle-mounted device calls Auth_SDK to obtain the certificate and private key; S22: The vehicle-mounted device application uses the certificate to initiate a TLS two-way authentication connection with the business management platform; S23: After the connection authentication is passed, the vehicle-mounted device initiates a dynamic registration request; S24: After registration, the vehicle-mounted device initiates a login request, and the service management platform verifies the login request and returns the login request verification result; S25: After the vehicle-mounted device logs in successfully, normal business data communication transmission begins.

[0021] Furthermore, step S3 includes the following sub-steps: S31: The first vehicle-mounted device application initializes the Auth_SDK authentication component and obtains a digital certificate; S32: The first vehicle-mounted device sends the digital certificate to the second vehicle-mounted device, and requests a random number from the second vehicle-mounted device; S33: The second vehicle-mounted device calls its Auth_SDK authentication component to verify the digital certificate sent by the first vehicle-mounted device and returns a random number; S34: The first vehicle-mounted device calls the Auth_SDK authentication component to sign the random number, and sends the signature result to the second vehicle-mounted device for authentication; S35: The second vehicle-mounted device calls its Auth_SDK authentication component and uses the cached digital certificate to authenticate the random number. If the authentication is successful, the first vehicle-mounted device is allowed to access the device's services.

[0022] The beneficial effects of the present invention are as follows: the present invention utilizes multiple security technologies such as encrypted transmission, certificate-based two-way identity authentication and data integrity verification to ensure the confidentiality, integrity and credibility of vehicle diagnostic data during transmission.

[0023] The present invention adopts advanced security authentication technology to ensure that the vehicle-mounted equipment has a high degree of security when transmitting data, effectively preventing the data from being stolen, tampered with or forged, thereby protecting the privacy and interests of the vehicle and the user.

[0024] The present invention can reduce the repair and replacement costs caused by system crash or data leakage by ensuring the security of data transmission, thereby reducing the overall maintenance cost.

[0025] The present invention can realize automation and intelligence of the production process and improve production efficiency and quality through data transmission and monitoring of the vehicle-mounted equipment. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the structures shown in these drawings without paying creative work.

[0027] Figure 1 is a system block diagram of the present invention; Figure 2 Flow chart for certificate application and replacement; Figure 3 Provide a flow chart for vehicle-mounted equipment and business platform certification; Figure 4 This is the flow chart for communication authentication between vehicle-mounted devices. DETAILED DESCRIPTION

[0028] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Generally, the components of the embodiments of the present invention described and shown in the drawings here can be arranged and designed in various different configurations.

[0029] It should be noted that similar reference numerals and letters denote similar items in the following drawings, and therefore, once an item is defined in one drawing, further definition and explanation thereof is not required in subsequent drawings.

[0030] Some embodiments of the present invention are described in detail below in conjunction with the accompanying drawings. In the absence of conflict, the following embodiments and features in the embodiments can be combined with each other.

[0031] See also Figure 1 A security authentication system for vehicle-mounted device data transmission includes an identity authentication module, a data encryption module, a data integrity verification module, an access control module and a log audit module, wherein: The identity authentication module uses the public key infrastructure (PKI) system to issue digital certificates to the vehicle-mounted device and the remote data center to achieve identity authentication. When establishing a connection, the vehicle-mounted device and the remote data center exchange digital certificates to verify each other's identity and use digital signature technology to ensure the authenticity of identity information during transmission. Identity authentication is a key technology in network security, used to confirm the true identity of the user to ensure that only legitimate users can access the system or service.

[0032] The data encryption module uses the Secure Sockets Layer (SSL) or Transport Layer Security (TLS) protocol to encrypt the transmitted data to ensure the confidentiality of the data. A combination of symmetric encryption algorithms (such as AES) and asymmetric encryption algorithms (such as RSA) is used to improve encryption efficiency and security, and encryption keys are replaced regularly to prevent security risks caused by key leakage. Data encryption technology is one of the important means to protect data security. By adopting appropriate encryption algorithms and key management strategies, the confidentiality and integrity of data during transmission and storage can be ensured, providing security protection for various application scenarios.

[0033] The data integrity verification module uses a hash function (such as SHA-256) to perform summary calculations on the data during data transmission to generate a data fingerprint. The data fingerprint is transmitted together with the original data. After receiving the data, the receiver recalculates the data fingerprint and compares it with the received data fingerprint to ensure that the data has not been tampered with during transmission. Data integrity verification is the process of ensuring that data maintains its originality, accuracy, and consistency during transmission, storage, and processing.

[0034] Access control module implements strict access control policies in remote data centers to limit access to vehicle data. Role-based access control (RBAC) policies are adopted to ensure that only authorized users or systems can access vehicle data, and access control policies are reviewed and updated regularly to address potential security risks. Access control is a security mechanism used to determine which users or systems have access to which resources. Through access control, the system can prevent unauthorized access and protect the integrity and security of resources.

[0035] Log audit module deploys log audit system in vehicle-mounted equipment and remote data center to record all operations and behaviors related to security authentication. Regularly audit and analyze logs to discover potential security risks and attack behaviors, and retain log information for verification and tracing, providing strong support for security incident investigation. Log audit refers to the centralized collection of various types of information such as system security events, user access records, system operation logs, system operation status, etc. in the information system, combined with rich log statistics summary and correlation analysis functions, to achieve a comprehensive audit of information system logs.

[0036] The present invention also provides a method for secure authentication of vehicle-mounted device data transmission, which is implemented based on the above-mentioned secure authentication system for vehicle-mounted device data transmission and mainly includes the following process: S1: Certificate application and replacement; S2: Vehicle equipment and service platform certification; S3: Communication authentication between vehicle-mounted devices.

[0037] For details, see Figure 2 , certificate application and replacement mainly include: 1. The vehicle-mounted equipment is factory-integrated with root certificates, pre-installed certificates and private keys.

[0038] 2. When the vehicle-mounted device is started, the vehicle-mounted device software calls the Auth_SDK authentication component initialization interface.

[0039] 3. The on-board Auth_SDK authentication component verifies the status of the current certificate.

[0040] 4. If the current certificate is pre-set or the certificate renewal threshold is reached, apply for the certificate online.

[0041] 5. The vehicle-mounted Auth_SDK authentication component generates a key pair (the component uses the software cryptographic module to securely store the private key) and generates a CSR certificate application.

[0042] 6. The vehicle-mounted Auth_SDK authentication component uses the pre-set certificate to establish an SSL two-way secure connection with the trust center and sends the certificate application message to the CA management center; (the pre-set certificate is solidified in the vehicle-mounted Auth_SDK authentication component).

[0043] 7. After receiving the certificate application message, the CA management center verifies the device identification code according to the whitelist, issues the certificate, and returns it to the device.

[0044] 8. When the device Auth_SDK authentication component imports the certificate, verify the certificate: a. Verify whether the certificate subject serial number matches the device; b. Verify that the certificate and key match; c. Verify whether the certificate is issued by this CA.

[0045] 9. After the certificate is successfully imported, the initialization operation is completed.

[0046] See also Figure 3 , vehicle equipment and business platform certification mainly includes: 1. When the vehicle-mounted device is started, the vehicle-mounted device application calls the Auth_SDK authentication component initialization interface.

[0047] 2. The in-vehicle Auth_SDK authentication component verifies the certificate status and returns the certificate and private key.

[0048] 3. The vehicle-mounted device application uses the certificate to initiate a TLS two-way authentication connection with the business management platform.

[0049] 4. After the connection authentication is passed, if the device needs to be dynamically registered, the device initiates a dynamic registration request (depending on the device, the request can carry parameters such as the device's unique identification code, user name, password, etc.).

[0050] 5. The business management platform whitelists or manually verifies the device registration request and returns the registration verification result.

[0051] 6. If dynamic registration is successful or no registration is required, the device initiates a login request normally (the login request can carry parameters such as device identification code, user name, password, etc.).

[0052] 7. The business management platform verifies the login request and returns the login request verification result (the result can carry authentication code, token and other data as identity identification credentials for subsequent business requests).

[0053] 8. After the device logs in successfully, normal business data communication transmission begins.

[0054] See also Figure 4 , the communication certification between vehicle-mounted devices mainly includes: 1. When vehicle-mounted device 1 needs to connect to and access vehicle-mounted device 2, the device 1 application initializes the Auth_SDK authentication component and obtains a digital certificate.

[0055] 2. After the Auth_SDK authentication group verifies the device identification code, it returns a digital certificate.

[0056] 3. Device 1 sends the digital certificate to device 2 and requests a random number from device 2.

[0057] 4. Device 2 with a pre-set root certificate calls its Auth_SDK authentication component to verify the digital certificate sent by device 1. After the verification is passed, a random number is returned to device 1.

[0058] a) Device 2 Auth_SDK authentication component uses the built-in CA certificate chain to verify whether the device 1 certificate has been tampered with and whether it is issued by the specified CA; b) Verify that the validity period of the certificate is valid.

[0059] 5. Device 1 calls the Auth_SDK authentication component to sign the random number.

[0060] 6. Device 1 sends the signature result to device 2 for authentication.

[0061] 7. Device 2 calls its Auth_SDK authentication component and uses the cached digital certificate to authenticate the random number. If the authentication passes, device 1 is allowed to access the device's services.

[0062] In addition, in order to prevent the key leakage of the vehicle-mounted device Auth_SDK authentication component and prevent illegal copying of the vehicle-mounted device Auth_SDK authentication component, it is not advisable to set a too long validity period for the certificate. Considering the security of the device certificate, the validity period of the certificate is designed as follows: 1. The device certificate is valid for 12 months.

[0063] 2. When the certificate is valid for 2 months or has expired, the device Auth_SDK authentication component automatically updates the certificate.

[0064] 3. After the new certificate is imported and verified, delete the old certificate.

[0065] The present invention can ensure that the vehicle-mounted equipment has a high degree of security when transmitting data by adopting advanced security authentication technology, effectively preventing data from being stolen, tampered with or forged, thereby protecting the privacy and interests of vehicles and users. By ensuring the security of data transmission, the repair and replacement costs caused by system crashes or data leaks can be reduced, thereby reducing the overall maintenance cost. Through the data transmission and monitoring of vehicle-mounted equipment, the automation and intelligence of the production process can be realized, and the production efficiency and quality can be improved.

[0066] For the aforementioned embodiments, for the sake of simplicity, they are all described as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the order of the actions described, because according to the present application, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are preferred embodiments, and the actions involved are not necessarily required by the present application.

[0067] The above embodiments describe the basic principles and main features of the present invention and the advantages of the present invention. It should be understood by those skilled in the art that the present invention is not limited by the above embodiments, and the above embodiments and descriptions are only for explaining the principles of the present invention. Without departing from the spirit and scope of the present invention, the modifications and changes made by those skilled in the art shall be within the scope of protection of the appended claims of the present invention without departing from the spirit and scope of the present invention.

Claims

1. A security authentication system for vehicle-mounted device data transmission, characterized in that: It includes identity authentication module, data encryption module, data integrity verification module, access control module and log audit module, among which: The identity authentication module is used to issue digital certificates to vehicle-mounted devices and remote data centers using the public key infrastructure system to achieve identity authentication; Data encryption module, used to encrypt the transmitted data using the secure socket layer or transport layer security protocol to ensure the confidentiality of the data; The data integrity check module is used to calculate the data summary using the hash function during data transmission to generate the data fingerprint; Access control module, which is used to implement strict access control policies in remote data centers to limit access rights to vehicle data; The log audit module is used to deploy the log audit system in vehicle-mounted devices and remote data centers to record all operations and behaviors related to security authentication.

2. A security authentication system for vehicle-mounted device data transmission as claimed in claim 1, characterized in that: The identity authentication module exchanges digital certificates with the on-board device and the remote data center when establishing a connection, verifies the identity of the other party, and uses digital signature technology to ensure the authenticity of the identity information during the transmission process.

3. A security authentication system for vehicle-mounted device data transmission as claimed in claim 2, characterized in that: The data encryption module adopts a combination of symmetric encryption algorithm and asymmetric encryption algorithm to improve encryption efficiency and security, and regularly replaces encryption keys to prevent security risks caused by key leakage.

4. A security authentication system for vehicle-mounted device data transmission as claimed in claim 3, characterized in that: The data integrity verification module transmits the data fingerprint together with the original data. After receiving the data, the receiver recalculates the data fingerprint and compares it with the received data fingerprint to ensure that the data has not been tampered with during transmission.

5. A security authentication system for vehicle-mounted device data transmission as claimed in claim 4, characterized in that: The access control module adopts a role-based access control strategy to ensure that only authorized users or systems can access vehicle data, and regularly reviews and updates the access control strategy to address potential security risks.

6. A security authentication system for vehicle-mounted device data transmission as claimed in claim 5, characterized in that: The log audit module regularly audits and analyzes logs to discover potential security risks and attack behaviors, and retains log information for verification and tracing, providing strong support for security incident investigations.

7. A method for secure authentication of vehicle-mounted device data transmission, implemented based on a secure authentication system for vehicle-mounted device data transmission as claimed in any one of claims 1 to 6, characterized in that: The steps include: S1: Certificate application and replacement; S2: Vehicle equipment and service platform certification; S3: Communication authentication between vehicle-mounted devices.

8. A method for secure authentication of vehicle-mounted device data transmission as claimed in claim 7, characterized in that: Step S1 includes the following sub-steps: S11: The vehicle-mounted device calls Auth_SDK to initiate a TLS connection to the CA management center through the pre-made root certificate and pre-made certificate; S12: Auth_SDK generates user private key and certificate request information; S13: Auth_SDK uses the certificate request information to initiate a registration and certificate request to the CA management center; S14: The CA management center receives the request to verify the device and then calls the PKI service to issue a certificate; S15: The CA management center sends the signed device certificate file to Auth_SDK, and Auth_SDK receives the certificate and saves the certificate file.

9. A method for secure authentication of vehicle-mounted device data transmission as claimed in claim 8, characterized in that: Step S2 includes the following sub-steps: S21: The vehicle-mounted device calls Auth_SDK to obtain the certificate and private key; S22: The vehicle-mounted device application uses the certificate to initiate a TLS two-way authentication connection with the business management platform; S23: After the connection authentication is passed, the vehicle-mounted device initiates a dynamic registration request; S24: After registration, the vehicle-mounted device initiates a login request, and the service management platform verifies the login request and returns the login request verification result; S25: After the vehicle-mounted device logs in successfully, normal business data communication transmission begins.

10. A method for secure authentication of vehicle-mounted device data transmission as claimed in claim 9, characterized in that: Step S3 includes the following sub-steps: S31: The first vehicle-mounted device application initializes the Auth_SDK authentication component and obtains a digital certificate; S32: The first vehicle-mounted device sends the digital certificate to the second vehicle-mounted device, and requests a random number from the second vehicle-mounted device; S33: The second vehicle-mounted device calls its Auth_SDK authentication component to verify the digital certificate sent by the first vehicle-mounted device and returns a random number; S34: The first vehicle-mounted device calls the Auth_SDK authentication component to sign the random number, and sends the signature result to the second vehicle-mounted device for authentication; S35: The second vehicle-mounted device calls its Auth_SDK authentication component and uses the cached digital certificate to authenticate the random number. If the authentication is successful, the first vehicle-mounted device is allowed to access the device's services.

Images