Motor vehicle data security control methods, devices, computer-readable storage media and computer program products

Abstract

This invention provides a method, device, computer-readable storage medium, and computer program product for motor vehicle data security control. The method includes: an embedding authentication information step, in which authentication information is embedded in the first data to be transmitted generated at the data generation end based on zero-round-trip secure transmission technology; an adding reliable transmission identifier step, in which an anti-replay sequence number is added to the data to be transmitted and it is determined whether the data to be transmitted needs forward error correction; if so, forward error correction coding is added to the data to be transmitted; an encryption step, in which the data security level of the data to be transmitted is determined based on a preset data security level classification standard, and each piece of data to be transmitted is encrypted using an encryption algorithm matching the data security level; and an encapsulation step, in which the data to be transmitted is encapsulated and the encapsulated data packet is sent to the data receiving end. This embodiment can improve data transmission security, authentication efficiency, and reduce resource consumption.

Description

Technical Field

[0001] The present invention relates to the field of vehicle communication technology, and in particular to a method, device, computer-readable storage medium and computer program product for controlling motor vehicle data security. Background Technology

[0002] Currently, as a mobile communication node, the data generated by various sensors installed on motor vehicles all need to rely on the vehicle's network to interact with external networks. To prevent data from being stolen or tampered with during the interaction process, authentication and encryption during data interaction are particularly important.

[0003] Existing methods for vehicle-mounted data interaction mainly include the following: communication methods based on traditional bus security protocols, encrypted communication methods based on transport layer security protocols (DTLS or TLS), and application layer-based custom reliable transmission mechanisms (e.g., forward error correction or acknowledgment-based retransmission strategies). However, the inventors found in practical implementation that the timing coordination of the handshake authentication process before the formal session is insufficient in the above methods, leading to the separation of secure handshake authentication from reliable transmission processes. This results in excessively high latency in the transmission of the first application data packet, failing to meet the real-time requirements of the vehicle control closed loop. Moreover, traditional methods also have relatively poor security during data transmission. In addition, traditional methods use the same encryption method for all data, but in practice, even data that does not affect the normal operation of the system, such as log data, is encrypted using a high-security encryption method, which obviously leads to a waste of resources. Summary of the Invention

[0004] The technical problem to be solved by the embodiments of the present invention is to provide a method for controlling motor vehicle data security, which can improve data transmission security and reduce resource consumption.

[0005] A further technical problem to be solved by the embodiments of the present invention is to provide a motor vehicle data security control device that can improve data transmission security and reduce resource consumption.

[0006] A further technical problem to be solved by the embodiments of the present invention is to provide a computer-readable storage medium that can improve data transmission security and reduce resource consumption.

[0007] A further technical problem to be solved by the embodiments of the present invention is to provide a computer program product that can improve data transmission security and reduce resource consumption.

[0008] To address the aforementioned technical problems, this invention first provides the following technical solution: a method for controlling motor vehicle data security, comprising the following steps: The step of embedding identity authentication information involves embedding identity authentication information into the first data to be transmitted generated at the data generation end based on zero-round-trip secure transmission technology. The reliable transmission identifier step involves adding an anti-replay sequence number to the data to be transmitted and determining whether the data to be transmitted needs forward error correction. If so, forward error correction coding is added to the data to be transmitted. The encryption step involves determining the data security level of the data to be transmitted based on a preset data security level classification standard, and encrypting each piece of data to be transmitted using an encryption algorithm that matches the data security level; and The encapsulation step involves encapsulating the data to be transmitted and sending the encapsulated data packet to the data receiving end.

[0009] Furthermore, the identity authentication information includes a session key seed and a first authentication random number.

[0010] Furthermore, the anti-replay sequence number includes the serial number corresponding to the data to be transmitted and the timestamp information of the data to be transmitted.

[0011] Furthermore, determining the data security level of the data to be transmitted based on the preset data security level classification standard specifically means: determining the corresponding data security level based on the data type of the data to be transmitted. The data type includes at least: data carrying the identity authentication information, key instruction data, sensor data, log data, and response messages. The data security level includes a first security level corresponding to the data carrying the identity authentication information and the key instruction data, a second security level corresponding to the sensor data, and a third security level corresponding to the log data and response messages. The first security level corresponds to the requirement of encryption and authentication, the second security level corresponds to the requirement of authentication only, and the third security level is the requirement of no encryption and authentication.

[0012] Furthermore, the first piece of data to be transmitted generated by the data generation end is encrypted using the following method: A key random number is generated based on the first authentication random number and the serial number of the first data to be transmitted; the first authentication random number, the anti-replay sequence number, and the forward error correction code are used as first metadata; and The first piece of data to be transmitted, the session key seed, and the first metadata are encrypted together using a preset encryption and authentication algorithm based on a pre-stored shared key and the key random number to generate an authentication encrypted ciphertext and a real authentication tag associated with the authentication encrypted ciphertext. The shared key is derived from the data generating end and the data receiving end based on a master-slave competition mechanism before the vehicle leaves the factory and is bound to the identity information of the data generating end. The first data packet sent to the data receiving end includes: the first metadata, the real authentication tag, and the authentication encryption ciphertext.

[0013] Furthermore, the following method is used to encrypt each subsequent data to be transmitted generated at the data generation end: The data receiver receives a second authentication random number, which is generated and returned by the data receiver after receiving and verifying a data packet containing the authentication tag. A session key is generated based on the first authentication random number, the second authentication random number, and the session key seed; the serial number of the data to be transmitted is used as the session random number; and the anti-replay sequence number and the forward error correction code are used as the second metadata. Based on the data security level of the data to be transmitted, it is determined whether encryption and authentication are required. If both encryption and authentication are required, the encryption and authentication algorithm is used to encrypt the subsequent data to be transmitted and the second metadata together with the session key and the session random number to generate session encrypted ciphertext and a first real session tag associated with the session encrypted ciphertext. If only authentication is required, a preset authentication algorithm is used to calculate the second real session tag of the data to be transmitted and the second metadata. Subsequent data packets sent to the data receiving end include: the second metadata, the first real session tag, and the session encryption ciphertext; or, subsequent data packets sent to the data receiving end include: the second metadata, the data to be transmitted, and the second real session tag; or, subsequent data packets sent to the data receiving end include: the second metadata and the data to be transmitted.

[0014] Furthermore, the serial numbers of each of the data to be transmitted generated by the data generation end change sequentially and continuously. When adding the corresponding serial number to the data to be transmitted, it is also determined whether the data receiving end needs to respond based on the data to be transmitted and return response data. If so, a serial number corresponding to the response data is spaced between two adjacent data to be transmitted.

[0015] On the other hand, in order to solve the above-mentioned further technical problems, the embodiments of the present invention provide the following technical solutions: a motor vehicle data security control device, which is connected to the data generation end and the data receiving end of a motor vehicle respectively, includes a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor. When the processor executes the computer program, it implements the motor vehicle data security control method as described in any one of the above.

[0016] Furthermore, in order to solve the aforementioned technical problems, the embodiments of the present invention provide the following technical solution: a computer-readable storage medium, including a stored computer program, wherein, when the computer program is running, it controls the device where the computer-readable storage medium is located to execute the motor vehicle data security control method as described in any one of the above.

[0017] On the other hand, in order to solve the above-mentioned further technical problems, the embodiments of the present invention first provide the following technical solution: a computer program product, including a computer program, wherein when the computer program is executed by a processor, it implements the motor vehicle data security control method as described in any of the above.

[0018] After adopting the above technical solution, the embodiments of the present invention have at least the following beneficial effects: Based on zero-round-trip secure transmission technology, the embodiments of the present invention embed identity authentication information in the first data to be transmitted at the data generation end. This eliminates the need for additional round-trip interactions to complete the initialization of identity verification, significantly reducing data transmission latency and adapting to the timeliness requirements of motor vehicle data transmission. Simultaneously, embedding identity authentication information in the first data to be transmitted allows for rapid identity verification between the data generation end and the receiving end, improving data transmission security. Furthermore, adding an anti-replay sequence number to the data to be transmitted uniquely identifies each piece of data. The receiving end can effectively identify and reject repeatedly transmitted data packets by verifying the sequence number, preventing attackers from launching attacks by replaying already transmitted legitimate data. When data is determined to require forward error correction, corresponding codes are added. These codes can be flexibly selected based on the importance of the data (such as critical operating parameters or safety command data). In the event of packet loss or bit errors during data transmission, data error correction can be achieved without reverse requesting retransmission, reducing transmission redundancy and lowering transmission pressure. Furthermore, appropriate encryption algorithms are used for data of different security levels. This ensures high-strength encryption protection for core data (such as vehicle control commands and user privacy data), preventing data theft, cracking, leakage, or tampering, while also balancing the transmission efficiency of ordinary data, thus balancing data security and transmission performance. Finally, the data is encapsulated and integrated into a unified format data packet, standardizing the data transmission format and facilitating rapid identification and parsing of the data components by the receiving end. Attached Figure Description

[0019] Figure 1 This is a flowchart of an optional embodiment of the motor vehicle data security control method of the present invention.

[0020] Figure 2 This is a schematic block diagram of an optional embodiment of the motor vehicle data security control device of the present invention.

[0021] Figure 3 This is a functional block diagram of an optional embodiment of the motor vehicle data security control device of the present invention. Detailed Implementation

[0022] The present application will now be described in further detail with reference to the accompanying drawings and specific embodiments. It should be understood that the following illustrative embodiments and descriptions are only used to explain the present invention and are not intended to limit the present invention. Moreover, the embodiments and features in the embodiments of the present application can be combined with each other unless otherwise specified.

[0023] like Figure 1 As shown, an optional embodiment of the present invention provides a motor vehicle data security control method, comprising the following steps: S1: Embedding identity authentication information step, which embeds identity authentication information into the first data to be transmitted generated at the data generation end based on zero round-trip secure transmission technology; S2: Add reliable transmission identifier step, add anti-replay sequence number to the data to be transmitted and determine whether the data to be transmitted needs forward error correction. If so, add forward error correction code to the data to be transmitted. S3: Encryption step, determining the data security level of the data to be transmitted based on a preset data security level classification standard, and encrypting each piece of data to be transmitted using an encryption algorithm matching the data security level; and S4: Encapsulation step, encapsulate the data to be transmitted, and send the encapsulated data packet to the data receiving end.

[0024] This invention, based on zero-round-trip secure transmission technology, embeds authentication information into the first data to be transmitted at the data generation end. This eliminates the need for additional round-trip interactions to complete initial identity verification, significantly reducing data transmission latency and meeting the timeliness requirements of motor vehicle data transmission. Simultaneously, embedding authentication information in the first data to be transmitted allows for rapid identity verification between the data generation and receiving ends, improving data transmission security. Furthermore, adding an anti-replay sequence number to the data to be transmitted uniquely identifies each data item. The receiving end can verify the sequence number to effectively identify and reject duplicate data packets, preventing attackers from launching attacks by replaying previously transmitted legitimate data. This also allows for the addition of anti-replay sequence numbers when forward error correction is required. Adding corresponding codes allows for flexible selection based on the importance of the data (such as critical operating parameters and safety command data). In the event of packet loss or bit errors during data transmission, data error correction can be achieved without reverse requesting retransmission, reducing transmission redundancy and lowering transmission pressure. Furthermore, appropriate encryption algorithms are used for data of different security levels, ensuring high-strength encryption protection for core data (such as vehicle control commands and user privacy data) to prevent data theft, cracking, leakage, or tampering, while also ensuring transmission efficiency for ordinary data, balancing data security and transmission performance. Finally, the data is encapsulated and integrated into a unified format data packet, standardizing the data transmission format and facilitating rapid identification and parsing of each component of the data by the receiving end.

[0025] In an optional embodiment of the present invention, the authentication information includes a session key seed and a first authentication random number. In this embodiment, the authentication information includes a session key seed and a first authentication random number, wherein the receiving end can use the first authentication random number to achieve rapid identity verification between the data generating end and the receiving end, preventing unauthorized devices from forging the identity of the data generating end, while the session key seed can serve as the basis for generating the session key for subsequent data transmission, without the need for additional transmission of key-related information.

[0026] In an optional embodiment of the present invention, the anti-replay sequence number includes a serial number corresponding to the data to be transmitted and a timestamp information indicating the generation of the data to be transmitted. In this embodiment, by combining the serial number and timestamp information as the anti-replay sequence number, on the one hand, the serial number can consecutively number all data sent by the same data generating end, facilitating the receiving end to quickly identify repeatedly transmitted data packets and preventing attackers from launching replay attacks by repeatedly sending the same data packets; on the other hand, the timestamp information can record the precise time of data generation, further distinguishing similar data generated at different times. Even if the serial number is forged, the receiving end can verify the reasonableness of the timestamp and the current time, thereby significantly improving the reliability of anti-replay attacks.

[0027] In specific implementation, when the data receiving end 3 performs anti-replay verification, it can first perform timestamp verification to determine whether the actual transmission and reception time difference of each data packet is less than the preset effective time difference. If so, it can then perform serial number verification. Based on the local time of the data receiving end 3 and the effective time difference, an effective time segment is dynamically generated. The serial numbers of the data packets received within the effective time segment are used as verification sequences and the verification sequences are updated in real time. It is determined whether the serial number of each newly received data packet is within the current verification sequence. If so, the newly received data packet is discarded. Finally, forward error correction technology (FEC) can be used to correct data errors based on the forward error correction coding in the data packet. Once the error correction is completed, subsequent data processing is performed.

[0028] In addition, in practice, to reduce data usage, the timestamp information in the first data packet is the current timestamp, while the timestamp information in subsequent data packets is based on the time offset of the current timestamp.

[0029] In an optional embodiment of the present invention, determining the data security level of the data to be transmitted based on a preset data security level classification standard specifically refers to: determining the corresponding data security level based on the data type of the data to be transmitted. The data type includes at least: data carrying the identity authentication information, key instruction data, sensor data, log data, and response messages. The data security level includes a first security level corresponding to the data carrying the identity authentication information and the key instruction data, a second security level corresponding to the sensor data, and a third security level corresponding to the log data and response messages. The first security level requires encryption and authentication, the second security level requires only authentication, and the third security level requires no encryption or authentication. In this embodiment, different data security levels correspond to different data types. Data carrying identity authentication information requires authentication before use, while key instruction data is crucial for controlling important instructions; both types of data are extremely important and therefore require both encryption and authentication. Sensor data (e.g., camera data, radar data, satellite positioning data, temperature and humidity data, etc.) has moderate importance and requires authenticated transmission. Log data and response messages do not require encryption or authentication protection.

[0030] In an optional embodiment of the present invention, the first data to be transmitted generated by the data generation terminal 3 is encrypted using the following method: A key random number is generated based on the first authentication random number and the serial number of the first data to be transmitted; the first authentication random number, the anti-replay sequence number, and the forward error correction code are used as first metadata; and The first piece of data to be transmitted, the session key seed, and the first metadata are encrypted together using a preset encryption and authentication algorithm based on a pre-stored shared key and the key random number to generate an authentication encrypted ciphertext and a real authentication tag associated with the authentication encrypted ciphertext. The shared key is derived from the data generating end and the data receiving end based on a master-slave competition mechanism before the vehicle leaves the factory and is bound to the identity information of the data generating end. The first data packet sent to the data receiving end includes: the first metadata, the real authentication tag, and the authentication encryption ciphertext.

[0031] In this embodiment, the processing of the first data to be transmitted from the data generation end 3 requires encryption and authentication because it carries identity authentication information. During encryption, the shared key, the first authentication random number, and the serial number obtained through a master-slave competition mechanism before the vehicle leaves the factory are used together with a preset encryption and authentication algorithm to encrypt the corresponding data, thereby forming an authentication encrypted ciphertext and a real authentication tag. Finally, the first data packet used for authentication is formed by encapsulating the first metadata, the real authentication tag, and the authentication encrypted ciphertext. When the data receiving end 3 receives this data packet, it can also recalculate the actual authentication tag of the authentication encrypted ciphertext based on the shared key and the first authentication random number and serial number in the first metadata that it has saved in the same way. By comparing the actual authentication tag and the real authentication tag, it can be determined whether the data packet has been tampered with and its legality. If they are the same, the corresponding data is decrypted and obtained.

[0032] In specific implementation, the method for generating the shared key is as follows: First, the initialization phase: Data generation terminal 3 (ECU-A) and data receiving terminal 5 (ECU-B) start simultaneously and are in the same state; Each generation has a random delay time (e.g., 10ms for data generation end, 15ms for data receiving end). Subsequently, the competition phase: ECU-A sends a campaign statement (containing a random ID=1) after a 10ms delay. ECU-B sends a campaign statement (containing a random ID=2) after a 15ms delay. ECU-A sends a declaration first, followed by ECU-B. The two ECUs compare their IDs: 2 > 1 → ECU-B becomes the master device and ECU-A becomes the slave device. Final conflict resolution (if it occurs): If both parties have the same random delay (e.g., 10ms), sending the declaration at the same time will cause a conflict; After both sides detect a conflict, each generates a new random delay (e.g., ECU-A: 5ms, ECU-B: 20ms). If ECU-B has a longer delay, and ECU-A sends the declaration first, then ECU-A becomes the master device. The derived shared key (PSK) needs to be transmitted to the other end in encryption, and both ends must save it in appropriate secure storage hardware to prevent leakage: When transmitting the shared key (PSK), a 256-bit hash value of the PSK needs to be calculated first. Then, the hash value and the shared key (PSK) are merged and encrypted together. The encryption key is extracted from the firmware of both parties. The receiving end first decrypts the PSK, separates the shared key (PSK) and hash value, then calculates the hash value of the shared key (PSK) and compares it with the received hash value. If they are not equal, the competition process is executed again. The shared key can be updated randomly in subsequent processes, but it must be regenerated in a secure environment, strictly following the previous process. The shared key (PSK) needs to be bound to the addresses (such as IP, MAC, etc.) of both ends: when the data receiving end receives authentication data from the other end, it first obtains the address of the other end, and then indexes the corresponding shared key (PSK), which is required for authentication.

[0033] In an optional embodiment of the present invention, the following method is used to encrypt the subsequent data to be transmitted generated by the data generation terminal 3: The data receiving end 5 receives a second authentication random number, which is generated and returned by the data receiving end 5 after receiving and verifying a data packet containing the authentication tag. A session key is generated based on the first authentication random number, the second authentication random number, and the session key seed; the serial number of the data to be transmitted is used as the session random number; and the anti-replay sequence number and the forward error correction code are used as the second metadata. Based on the data security level of the data to be transmitted, it is determined whether encryption and authentication are required. If both encryption and authentication are required, the encryption and authentication algorithm is used to encrypt the subsequent data to be transmitted and the second metadata together with the session key and the session random number to generate session encrypted ciphertext and a first real session tag associated with the session encrypted ciphertext. If only authentication is required, a preset authentication algorithm is used to calculate the second real session tag of the data to be transmitted and the second metadata. Subsequent data packets sent to the data receiving end 5 may include: the second metadata, the first real session tag, and the session encryption ciphertext; or, subsequent data packets sent to the data receiving end may include: the second metadata, the data to be transmitted, and the second real session tag; or, subsequent data packets sent to the data receiving end may include: the second metadata and the data to be transmitted.

[0034] In this embodiment, for the processing of subsequent data to be transmitted from the data generation end 3, since the data types are diverse, it is necessary to determine whether encryption and authentication are required based on the data security level of the data to be transmitted. If encryption and authentication are required, the encryption process differs from the first data packet in that a session key is generated using the first authentication random number, the second authentication random number, and the session key seed. Simultaneously, the serial number is directly used as the session random number, and a preset encryption and authentication algorithm is used to encrypt the corresponding data, thereby forming a session encrypted ciphertext and a first real session tag. The data is then combined to form a data packet. If only authentication is required, the corresponding authentication algorithm is directly used to form a second real session tag, and the data is combined to form a data packet. If neither encryption nor authentication is required, the corresponding data is directly combined to form a data packet. When the data receiving end 5 receives the corresponding data packet, if the data packet requires decryption and authentication, a session key and a serial number in the second metadata are generated based on the first authentication random number, the second authentication random number, and the session key seed for decryption and authentication. If only authentication is required, the same authentication algorithm is used to calculate the second actual authentication tag, determine its legality, and complete the authentication process.

[0035] In an optional embodiment of the present invention, the serial numbers of each of the data to be transmitted generated by the data generating end change sequentially and continuously. When adding the corresponding serial number to the data to be transmitted, it is also determined whether the data receiving end needs to respond based on the data to be transmitted and return response data. If so, a serial number corresponding to the response data is spaced between two adjacent data to be transmitted. In this embodiment, since the encryption process for each subsequent data to be transmitted requires generating a corresponding random number based on the serial number of the data to be transmitted to encrypt and decrypt the data packet, it is necessary to ensure that the serial number corresponding to each data packet is unique. Therefore, in specific implementation, the generation rules for the serial number of each data packet are as follows: The serial number is initiated by the data generating end. When the data generating end 3 initiates a data packet with serial number 'a', if the data receiving end 5 needs to return a response data packet based on the data packet 'a' sent by the data generating end 3, the serial number of the data packet returned by the data generating end 3 is a+1. The serial number of the next data packet initiated by the data generating end 3 is a+2, that is, an interval of one serial number a+1. When the data generating end 3 initiates a data packet with serial number 'a', if the data receiving end 5 does not need to return a response data packet based on the data packet 'a' sent by the data generating end 3, the serial number of the next data packet initiated by the data generating end 3 is a+1.

[0036] In specific implementation, the encryption authentication algorithm can be the AEAD mode of the ChaCha20-Poly1305 encryption authentication algorithm model; the authentication algorithm can be the Poly1305 authentication algorithm, hash authentication algorithm, or CRC authentication algorithm, etc. Communication between the present invention embodiment and the data receiving end 5 is typically based on the CAN communication protocol or the UDP communication protocol.

[0037] In practice, the session key is generated according to the following formula: K_session=ChaCha20(KeySeed, Nonce_C XOR Nonce_S) (Formula 1); Where K_session represents the session key, KeySeed represents the session key seed, Nonce_C and Nonce_S represent the first authentication random number and the second authentication random number, respectively; XOR represents the XOR operation; and ChaCha20() represents the key generation method of the ChaCha20 encryption algorithm.

[0038] In addition, each time a data packet is sent to the data receiving end 3 to initiate a session, the corresponding session key is stored by the corresponding end, and the duration of each session generally does not exceed 60 seconds; after a single session is completed, the session key must be deleted by itself, and the first data packet containing the identity authentication information must be resent for authentication before another session can begin.

[0039] In addition, for each of the aforementioned data packets, various data packets can be encapsulated using protocol fields during transmission. The specific protocol fields are shown in the table below:

[0040] in: Ver represents the protocol version number. Both parties transmitting data should ensure that the protocol version number in the protocol field is the same. Type indicates the data type and encryption method of the main data (data to be transmitted) in the data packet. Different values ​​represent different data types, specifically: TYPE_CMD: Critical instruction data, which requires encryption and authentication, with optional forward error correction processing; TYPE_SENSOR: Sensor data: Authentication required; TYPE_LOG: Log data: No encryption or authentication required; TYPE_ACK: Response data: No encryption or authentication required; TYPE_AUTH_CMD: Data carrying identity authentication information, which needs to be encrypted and authenticated, with optional forward error correction processing; TYPE_CLOSE: Close session command, no encryption or authentication required; Flags represent bit control. By setting different values, the corresponding bit can be turned off when it is not needed in the corresponding protocol field, thereby reducing the transmission bandwidth. SessionID represents the session identifier; SeqNum represents the serial number; Milliseconds / TimestampOffset represents the current timestamp in milliseconds / the time offset based on the current timestamp; Seconds represents the current timestamp in seconds. In practice, Milliseconds and Seconds only exist in the first data packet. AuthNonce represents the authentication random number (first authentication random number and second authentication random number), which only exists in the first data packet and the return data packet of the data receiver 3 based on the first data packet sent by the data generator; FECParity represents the forward error correction coding used in forward error correction techniques; Ciphertext represents the ciphertext portion formed after the corresponding data is encrypted. For example, the authentication ciphertext formed after encrypting the first data to be transmitted, the session key seed, and the first metadata. DynamicMAC stands for Real Authentication Tag / First Real Session Tag / Second Real Session Tag, and its tag length can be selected according to the encryption strength.

[0041] In practice, the first metadata and the second metadata typically include the protocol header portion of the aforementioned protocol fields, excluding the Ciphertext and DynamicMAC fields.

[0042] On the other hand, such as Figure 2 As shown, this embodiment of the invention provides a motor vehicle data security control device 1, which is connected to a data generation terminal 3 and a data receiving terminal 5 of a motor vehicle, respectively. It includes a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor. When the processor executes the computer program, it implements the motor vehicle data security control method as described in any of the above embodiments.

[0043] For example, the computer program can be divided into one or more modules / units, which are stored in the memory 12 and executed by the processor 10 to complete the present invention. The one or more modules / units can be a series of computer program instruction segments capable of performing a specific function, which describe the execution process of the computer program in the motor vehicle data security control device 1. For example, the computer program can be divided into... Figure 3The functional modules in the motor vehicle data security control device 1 include the embedded identity authentication information module 41, the reliable transmission identifier addition module 42, the encryption module 43, and the encapsulation module 44, which respectively perform the above steps S1-S4.

[0044] The vehicle data security control device 1 can be a computing device such as a desktop computer, laptop, handheld computer, or cloud server. The vehicle data security control device 1 may include, but is not limited to, a processor 10 and a memory 12. Those skilled in the art will understand that the schematic diagram is merely an example of the vehicle data security control device 1 and does not constitute a limitation on the vehicle data security control device 1. It may include more or fewer components than shown, or combine certain components, or different components. For example, the vehicle data security control device 1 may also include input / output devices, network access devices, buses, etc.

[0045] The processor 10 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor. The processor 10 is the control center of the vehicle data security control device 1, connecting all parts of the vehicle data security control device 1 via various interfaces and lines.

[0046] The memory 12 can be used to store the computer programs and / or modules. The processor 10 implements various functions of the motor vehicle data security control device 1 by running or executing the computer programs and / or modules stored in the memory 12 and calling the data stored in the memory 12. The memory 12 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as image recognition function, image overlay function, etc.), etc.; the data storage area may store data created according to the use of the motor vehicle data security control device 1 (such as image data, etc.). In addition, the memory 12 may include high-speed random access memory, and may also include non-volatile memory, such as hard disk, memory, plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0047] If the functions described in the embodiments of the present invention are implemented in the form of software functional modules or units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the embodiments of the present invention can implement all or part of the processes in the methods described above, or they can be accomplished by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by the processor 10, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or device capable of carrying the computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium can be appropriately added or removed according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electrical carrier signals and telecommunication signals.

[0048] In another aspect, embodiments of the present invention also provide a computer-readable storage medium, the computer-readable storage medium including a stored computer program, wherein, when the computer program is executed, it controls the device where the computer-readable storage medium is located to perform the motor vehicle data security control method as described in any of the above.

[0049] In another aspect, embodiments of the present invention also provide a computer program product, including a computer program that, when executed by a processor, implements the motor vehicle data security control method as described in any of the above embodiments.

[0050] The various embodiments in this specification are described in a progressive manner. Each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.

[0051] The embodiments of the present invention have been described above with reference to the accompanying drawings. However, the present invention is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of the present invention without departing from the spirit and scope of the claims. All of these forms are within the scope of protection of the present invention.

Claims

1. A motor vehicle data security control method, characterized in that, The method includes the following steps: The step of embedding identity authentication information involves embedding identity authentication information into the first data to be transmitted generated at the data generation end based on zero-round-trip secure transmission technology. The reliable transmission identifier step involves adding an anti-replay sequence number to the data to be transmitted and determining whether the data to be transmitted needs forward error correction. If so, forward error correction coding is added to the data to be transmitted. The encryption step involves determining the data security level of the data to be transmitted based on a preset data security level classification standard, and encrypting each piece of data to be transmitted using an encryption algorithm that matches the data security level; and The encapsulation step involves encapsulating the data to be transmitted and sending the encapsulated data packet to the data receiving end.

2. The motor vehicle data security control method of claim 1, wherein, The authentication information includes a session key seed and a first authentication random number.

3. The motor vehicle data security control method of claim 2, wherein, The anti-replay sequence number includes the serial number corresponding to the data to be transmitted and the timestamp information of the data to be transmitted.

4. The motor vehicle data security control method of claim 1, wherein, The determination of the data security level of the data to be transmitted based on the preset data security level classification standard specifically refers to: determining the corresponding data security level based on the data type of the data to be transmitted. The data type includes at least: data carrying the identity authentication information, key instruction data, sensor data, log data, and response messages. The data security level includes a first security level corresponding to the data carrying the identity authentication information and the key instruction data, a second security level corresponding to the sensor data, and a third security level corresponding to the log data and response messages. The first security level corresponds to the requirement of encryption and authentication, the second security level corresponds to the requirement of authentication only, and the third security level is the requirement of no encryption and authentication.

5. The motor vehicle data security control method of claim 4, wherein, The first piece of data to be transmitted generated by the data generation end is encrypted using the following method: A key random number is generated based on the first authentication random number and the serial number of the first data to be transmitted, and the first authentication random number, the anti-replay sequence number and the forward error correction code are used as the first metadata; as well as The first piece of data to be transmitted, the session key seed, and the first metadata are encrypted together using a preset encryption and authentication algorithm based on a pre-stored shared key and the key random number to generate an authentication encrypted ciphertext and a real authentication tag associated with the authentication encrypted ciphertext. The shared key is derived from the data generating end and the data receiving end based on a master-slave competition mechanism before the vehicle leaves the factory and is bound to the identity information of the data generating end. The first data packet sent to the data receiving end includes: the first metadata, the real authentication tag, and the authentication encryption ciphertext.

6. The motor vehicle data security control method of claim 5, wherein, The following method is used to encrypt each subsequent data to be transmitted generated at the data generation end: The data receiver receives a second authentication random number, which is generated and returned by the data receiver after receiving and verifying a data packet containing the authentication tag. A session key is generated based on the first authentication random number, the second authentication random number, and the session key seed. The serial number of the data to be transmitted is used as the session random number, and the anti-replay sequence number and the forward error correction code are used as the second metadata. as well as Based on the data security level of the data to be transmitted, it is determined whether encryption and authentication are required. If both encryption and authentication are required, the encryption and authentication algorithm is used to encrypt the subsequent data to be transmitted and the second metadata together with the session key and the session random number to generate session encrypted ciphertext and a first real session tag associated with the session encrypted ciphertext. If only authentication is required, a preset authentication algorithm is used to calculate the second real session tag of the data to be transmitted and the second metadata. Subsequent data packets sent to the data receiving end include: the second metadata, the first real session tag, and the session encryption ciphertext; or, subsequent data packets sent to the data receiving end include: the second metadata, the data to be transmitted, and the second real session tag; or, subsequent data packets sent to the data receiving end include: the second metadata and the data to be transmitted.

7. The motor vehicle data security control method of any one of claims 1-6, wherein, The serial numbers of each piece of data to be transmitted generated by the data generation end change sequentially and continuously. When adding the corresponding serial number to the data to be transmitted, it is also determined whether the data receiving end needs to respond based on the data to be transmitted and return response data. If so, a serial number corresponding to the response data is spaced between two adjacent pieces of data to be transmitted.

8. A motor vehicle data security control device, connected to a data generation end and a data receiving end of a motor vehicle respectively, characterized in that, The device includes a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, wherein the processor executes the computer program to implement the motor vehicle data security control method as described in any one of claims 1 to 7.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored computer program, wherein, when the computer program is executed, it controls the device on which the computer-readable storage medium is located to perform the motor vehicle data security control method as described in any one of claims 1 to 7.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the motor vehicle data security control method as described in any one of claims 1-7.

Images