Vehicle cloud interaction data transmission method, device and equipment, medium and vehicle

Abstract

The embodiment of the invention provides a vehicle cloud interaction data transmission method, device and equipment, a medium and a vehicle, and relates to the technical field of data transmission. The method comprises the following steps: acquiring a dynamic key, and a VIN code and a TCODE code of a vehicle; wherein the VIN code can uniquely identify a vehicle, and the TCODE code can uniquely identify a vehicle-mounted terminal in the vehicle; on the basis of a specified random number seed, performing supplementation adjustment on the VIN code and the TCODE code to obtain a first plaintext and a second plaintext; symmetrically encrypting the first plaintext and the second plaintext according to the dynamic key to obtain a first ciphertext corresponding to the first plaintext and a second ciphertext corresponding to the second plaintext; splicing the first ciphertext and the second ciphertext to obtain a spliced ciphertext, and performing asymmetric encryption on the spliced ciphertext to obtain a third ciphertext; and determining a target key according to the specified length and the third ciphertext, and performing encryption or decryption verification on the vehicle cloud interaction data based on the target key, so that the possibility that the key is cracked and exposed can be reduced.

Description

Technical Field

[0001] The embodiments described in this specification relate to the field of data transmission technology, specifically to a vehicle-to-cloud interactive data transmission method, apparatus, device, medium, and vehicle. Background Technology

[0002] The rapid proliferation of intelligent connected vehicles has driven the rapid iteration of automotive digital key technologies, such as Public Key Infrastructure (PKI). PKI is a fundamental framework for authentication and encryption in modern digital environments, primarily used to protect the security of network interactions and communications. However, it relies on a large cluster of Certificate Authority Servers (CAs) for certificate issuance, revocation, and key management, requiring continuous investment of significant hardware resources and bandwidth. Its operational costs are excessively high, especially as the number of vehicles surges. The real-time requirements of certificate chain verification cause an exponential increase in server cluster load, and cross-regional deployment of PKI nodes poses a risk of synchronization delays. Furthermore, the centralized storage of root certificate private keys can become a single point of attack target; a leak could lead to the collapse of the entire vehicle networking platform's security system.

[0003] Secondly, the vehicle's software development kit (SDK) relies on third parties, and its encryption modules are often provided by closed-source external vendors, employing black-box key derivation algorithms. This makes it difficult for automakers to independently audit the code's security, posing risks of hidden backdoors or weak random number generation. More seriously, the update cycle of third-party SDKs is mismatched with the pace of automakers' over-the-air (OTA) technology, easily leading to known vulnerabilities not being patched in a timely manner.

[0004] Therefore, it is necessary to provide a vehicle-to-cloud (V2X) data transmission method to reduce the possibility of key cracking during V2X interaction, thereby improving the security of two-way V2X data interaction. Summary of the Invention

[0005] In view of this, this specification provides several embodiments aimed at providing a vehicle-to-cloud interactive data transmission method to reduce the possibility of key cracking and exposure.

[0006] This specification provides a vehicle-to-cloud (V2X) interactive data transmission method, comprising: acquiring a dynamic key, and a vehicle's VIN and TCODE codes; wherein the VIN uniquely identifies the vehicle, and the TCODE uniquely identifies the in-vehicle terminal within the vehicle; padding and adjusting the VIN and TCODE codes based on a specified random number seed to obtain a first plaintext and a second plaintext; symmetrically encrypting the first plaintext and the second plaintext according to the dynamic key to obtain a first ciphertext corresponding to the first plaintext and a second ciphertext corresponding to the second plaintext; concatenating the first ciphertext and the second ciphertext to obtain a concatenated ciphertext, and asymmetrically encrypting the concatenated ciphertext to obtain a third ciphertext; determining a target key based on a specified length and the third ciphertext, and encrypting or decrypting the V2X interactive data based on the target key for verification.

[0007] In some implementations, the step of symmetrically encrypting the first plaintext and the second plaintext according to the dynamic key includes: using the first plaintext as plaintext and the dynamic key as the key, performing symmetric encryption in AES-ECB mode to generate the first ciphertext; and using the second plaintext as plaintext and the dynamic key as the key, performing symmetric encryption in AES-ECB mode to generate the second ciphertext.

[0008] In some implementations, the padding and adjustment of the VIN code and the TCODE code based on a specified random number seed includes: when the VIN code does not meet a set length rule, determining a first padding sequence based on the byte length of the VIN code and the specified random number seed, and padding and adjusting the VIN code according to the first padding sequence to obtain the first plaintext; wherein the set length rule is used to constrain the byte length of the plaintext to be symmetrically encrypted to be an integer multiple of the specified length; when the TCODE code does not meet the set length rule, determining a second padding sequence based on the byte length of the TCODE code and the specified random number seed, and padding and adjusting the TCODE code according to the second padding sequence to obtain the second plaintext.

[0009] In some embodiments, the method is applied to an in-vehicle terminal in a vehicle-to-cloud (V2X) interactive system, which further includes a cloud communicationally connected to the in-vehicle terminal. The V2X interactive data includes upload instructions and download instructions. The upload instructions include a terminal activation request or OTA update request sent by the in-vehicle terminal to the cloud, and the download instructions include activation result feedback information or update response information sent by the cloud to the in-vehicle terminal. The encryption or decryption verification of the transmitted V2X interactive data based on the target key includes: decrypting the download instructions based on the target key; or encrypting the upload instructions based on the target key.

[0010] In some implementations, the method is applied to the cloud in a vehicle-to-cloud (V2X) interactive system, which further includes an in-vehicle terminal communicatively connected to the cloud. The V2X interactive data includes upload instructions and download instructions, wherein the upload instructions carry the vehicle's VIN and TCODE codes. The encryption or decryption verification of the transmitted V2X interactive data based on the target key includes: verifying the upload instructions based on the VIN and TCODE codes, and decrypting the upload instructions based on the target key; or, encrypting the download instructions based on the target key.

[0011] In some embodiments, the method further includes: issuing a new dynamic key to the vehicle terminal via the issuing instruction based on a first specified period, wherein the dynamic key is different for different first specified periods; and / or issuing a new specified random seed to the vehicle terminal via the issuing instruction based on a second specified period, wherein the specified random seed is different for different second specified periods.

[0012] This specification provides a vehicle-to-cloud interactive data transmission device, comprising: a data acquisition module for acquiring a dynamic key, and a vehicle's VIN code and TCODE code; wherein the VIN code uniquely identifies the vehicle, and the TCODE code uniquely identifies the in-vehicle terminal within the vehicle; a data padding module for padding and adjusting the VIN code and TCODE code based on a specified random number seed to obtain a first plaintext and a second plaintext; a first encryption module for symmetrically encrypting the first plaintext and the second plaintext according to the dynamic key to obtain a first ciphertext corresponding to the first plaintext and a second ciphertext corresponding to the second plaintext; a second encryption module for concatenating the first ciphertext and the second ciphertext to obtain a concatenated ciphertext, and performing asymmetric encryption on the concatenated ciphertext to obtain a third ciphertext; and a data authentication module for determining a target key based on a specified length and the third ciphertext, and encrypting or decrypting the vehicle-to-cloud interactive data based on the target key.

[0013] This specification provides a computer device including a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the vehicle-to-cloud interactive data transmission method described in any of the above embodiments.

[0014] This specification provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the vehicle-to-cloud interactive data transmission method described in any of the above embodiments.

[0015] This specification provides a vehicle that includes the device described in any of the above embodiments.

[0016] In the various implementation methods provided in this specification, firstly, a dynamic key, a VIN code that uniquely identifies the vehicle, and a TCODE code that uniquely identifies the in-vehicle terminal within the vehicle are obtained. Next, the VIN code and TCODE code are padded and adjusted based on a specified random number seed to obtain a first plaintext and a second plaintext. Then, the first and second plaintexts are symmetrically encrypted using the dynamic key to obtain a first ciphertext and a second ciphertext. The first and second ciphertexts are then concatenated to obtain a concatenated ciphertext. Finally, the concatenated ciphertext is asymmetrically encrypted to obtain a third ciphertext. A target key is determined based on a specified length and the third ciphertext. Based on the target key, vehicle-to-cloud interaction data is encrypted or decrypted for verification. This reduces the possibility of the key being cracked and exposed, improving the security and controllability of vehicle-to-cloud interaction data transmission. Attached Figure Description

[0017] Figure 1 A flowchart illustrating the vehicle-to-cloud interactive data transmission method provided in the embodiments of this specification; Figure 2 A flowchart illustrating the vehicle-to-cloud interactive data transmission method provided in the embodiments of this specification; Figure 3 A schematic diagram of the vehicle-to-cloud interactive data transmission device provided in the embodiments of this specification; Figure 4 A schematic diagram of a computer device provided for an embodiment of this specification. Detailed Implementation

[0018] To enable those skilled in the art to better understand the solutions described in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of them. Based on the embodiments in this specification, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this specification.

[0019] This specification provides an example of a vehicle-to-cloud (V2X) interaction scenario. The V2X interaction system may include a cloud platform and an in-vehicle terminal (Telematics Box, TBOX) located in the vehicle. The in-vehicle terminal and the cloud are connected by a communication link. The in-vehicle terminal and the cloud can interact with each other, that is, they can transmit V2X interaction data. For example, the V2X interaction data may include upload instructions and download instructions. Upload instructions refer to data or instructions sent from the in-vehicle terminal to the cloud, and download instructions refer to data or instructions sent from the cloud to the in-vehicle terminal.

[0020] For example, the upload command may include a terminal activation request or OTA update request sent by the in-vehicle terminal to the cloud, and the download command may include activation result feedback information or update response information sent by the cloud to the in-vehicle terminal. Depending on the actual situation, the upload and download commands in the vehicle-cloud interaction system may also be other data, requests, or response information.

[0021] This specification provides a vehicle-to-cloud interactive data transmission method. Please refer to [link / reference]. Figure 1 , Figure 1 This is a flowchart illustrating a vehicle-to-cloud interactive data transmission method provided in this embodiment. This embodiment provides the method operation steps shown in the flowchart, but based on conventional or non-creative labor, it may include more or fewer operation steps. The order of steps listed in this embodiment is merely one possible execution order among many, and does not represent the only possible execution order. In actual system or server product execution, the method can be executed sequentially as shown in the embodiment or in parallel (e.g., in a parallel processor or multi-threaded processing environment). This vehicle-to-cloud interactive data transmission method can be applied to in-vehicle terminals or the cloud in a vehicle-to-cloud interactive system, specifically as follows... Figure 1 As shown, the vehicle-to-cloud interactive data transmission method may include the following steps.

[0022] Step S110: Obtain the dynamic key, as well as the vehicle's VIN and TCODE codes; wherein, the VIN code can uniquely identify the vehicle, and the TCODE code can uniquely identify the vehicle's on-board terminal.

[0023] In some cases, to improve the security of vehicle-to-cloud interaction data transmitted in the vehicle-to-cloud interaction system, it is advisable to design relevant keys to perform two-way authentication of the vehicle-to-cloud interaction data.

[0024] The dynamic key can refer to an AES key. For example, the dynamic key can be determined by the current session, which can refer to the session to which the vehicle-to-cloud interaction data to be encrypted or decrypted belongs. That is, a single-session one-key. As another example, it can also be a one-key for a specified number of sessions or a one-key for a specified duration.

[0025] Step S120: Based on the specified random number seed, the VIN code and TCODE code are padded and adjusted respectively to obtain the first plaintext and the second plaintext.

[0026] This specifies the random number seed, also known as Seed or Random Seed. Based on the specified random number seed, a specified sequence of random numbers can be generated.

[0027] Specifically, it can be determined whether the VIN code and TCODE code need to be padded and adjusted based on the set specified length. If so, they are padded based on the generated specified random number sequence so that the adjusted length is an integer multiple of the specified length.

[0028] Step S130: Perform symmetric encryption on the first plaintext and the second plaintext respectively according to the dynamic key to obtain the first ciphertext corresponding to the first plaintext and the second ciphertext corresponding to the second plaintext.

[0029] Step S140: Concatenate the first ciphertext and the second ciphertext to obtain the concatenated ciphertext, and perform asymmetric encryption on the concatenated ciphertext to obtain the third ciphertext.

[0030] Step S150: Determine the target key based on the specified length and the third ciphertext, and encrypt or decrypt the vehicle-cloud interaction data based on the target key.

[0031] For example, the third ciphertext can be selected or truncated according to a specified length to obtain a key of a specified length.

[0032] Specifically, vehicle-to-cloud (V2X) interaction data can be received or to be transmitted. For received V2X interaction data, it can be decrypted and verified based on the target key; for V2X interaction data to be transmitted, it can be encrypted based on the target key.

[0033] In the above implementation, the VIN code of the pre-set unique vehicle identifier and the TCODE code of the vehicle's onboard terminal are adjusted and supplemented based on a specified random number seed. The adjusted VIN code and TCODE code are then symmetrically encrypted using a temporary dynamic key to obtain a first ciphertext and a second ciphertext. These two ciphertexts are then concatenated to obtain a concatenated ciphertext, which is then asymmetrically encrypted, and a target key is determined based on a specified length. This reduces the possibility and risk of long-term key exposure during dynamic key updates. Furthermore, this implementation eliminates the issuance, verification, and revocation processes of CA certificates, reducing server computational load and thus reducing reliance on PKI. Simultaneously, the short cycle of the dynamic key (single-session one-key or few-session one-key) avoids the latency risk caused by PKI certificate expiration, adapting to the low-latency requirements of vehicle-to-everything (V2X) networks and improving real-time performance.

[0034] In some implementations, the VIN code and TCODE code are padded and adjusted based on a specified random number seed, which may include the following steps S210-220.

[0035] Step S210: If the VIN code does not meet the set length rule, determine the first padding sequence based on the byte length of the VIN code and the specified random number seed, and pad and adjust the VIN code according to the first padding sequence to obtain the first plaintext; wherein, the set length rule is used to constrain the byte length of the plaintext to be symmetrically encrypted to be an integer multiple of the specified length.

[0036] The specified length can be 8 bytes, 16 bytes, 32 bytes, or 64 bytes, etc.

[0037] For example, a random number seed can be specified to generate a specified random number sequence. Then, it is determined whether the byte length of the VIN code is a specified length or an integer multiple of the specified length. If not, a first padding sequence is selected based on the specified random number sequence, and the VIN code is padded and adjusted using the first padding sequence to obtain the first plaintext, so that the byte length of the first plaintext is an integer multiple of the specified length.

[0038] Step S220: If the TCODE code does not meet the set length rule, determine the second padding sequence based on the byte length of the TCODE code and the specified random number seed, and adjust the TCODE code according to the second padding sequence to obtain the second plaintext.

[0039] For example, a random number seed can be specified to generate a specified random number sequence. Then, it is determined whether the byte length of the TCODE code is the specified length or an integer multiple of the specified length. If not, a second padding sequence is selected based on the specified random number sequence, and the TCODE code is padded and adjusted using the second padding sequence to obtain the second plaintext, so that the byte length of the second plaintext is an integer multiple of the specified length.

[0040] In some implementations, symmetric encryption of the first plaintext and the second plaintext is performed according to a dynamic key, which may include the following steps S310-S320.

[0041] Step S310: Using the first plaintext as the plaintext and the dynamic key as the key, perform symmetric encryption in AES-ECB mode to generate the first ciphertext.

[0042] For example, the first ciphertext can be obtained using Formula 1.

[0043] VIN_1 = AES128 (VIN + SeedV, AK) Formula 1 Wherein, VIN+SeedV represents the first plaintext, SeedV is the part of the VIN code filled or padded based on a specified random number sequence, AK represents the dynamic key, and the AES128 symmetric encryption algorithm uses ECB mode.

[0044] Step S320: Using the second plaintext as the plaintext and the dynamic key as the key, perform symmetric encryption in AES-ECB mode to generate the second ciphertext.

[0045] For example, the first ciphertext can be obtained using Formula 2.

[0046] TCODE_1=AES128 (TCODE+SeedT, AK) formula 2 Where TCODE+SeedV represents the second plaintext, and SeedT is the part of the TCODE code that is filled or padded based on a specified random number sequence.

[0047] In some implementations, the vehicle-to-cloud (V2X) interactive data transmission method can be applied to the in-vehicle terminal in the V2X interactive system. The V2X interactive data includes upload commands and download commands; wherein, upload commands may include, but are not limited to, terminal activation requests or OTA update requests sent by the in-vehicle terminal to the cloud, and download commands may include, but are not limited to, activation result feedback information or update response information sent by the cloud to the in-vehicle terminal.

[0048] In this embodiment, encrypting or decrypting the transmitted vehicle-to-cloud interaction data based on the target key can include: decrypting the sent command based on the target key; or encrypting the uploaded command based on the target key.

[0049] In some implementations, the vehicle-to-cloud (V2X) data transmission method can be applied to the cloud within the V2X system. The upload command in the V2X data can carry the vehicle's VIN and TCODE codes, allowing the cloud to verify whether the upload command originates from a legitimate vehicle already logged into the cloud based on these codes.

[0050] In this embodiment, encrypting or decrypting the transmitted vehicle-to-cloud interactive data based on the target key can include: verifying the upload command based on the VIN code and TCODE code, and decrypting the upload command based on the target key; or, encrypting the sending command based on the target key.

[0051] In some implementations, the vehicle-to-cloud interactive data transmission method may further include: issuing a new dynamic key to the vehicle terminal by issuing a command based on a first specified period, wherein the dynamic key is different for different first specified periods.

[0052] In some implementations, the vehicle-to-cloud interactive data transmission method may further include: sending a new specified random seed to the vehicle terminal by issuing an instruction based on a second specified period, wherein the specified random seed is different for different second specified periods.

[0053] This specification provides a vehicle-to-cloud interactive data transmission method. Please refer to [link / reference]. Figure 2 The vehicle-to-cloud interactive data transmission method may include the following steps.

[0054] Step S401: During the platform vehicle manufacturing stage, the cloud can receive VIN codes and TCODEs transmitted by other systems or manually, and store the vehicle's VIN code and TBOX's TCODE code in the database or cloud, so that the vehicle can be activated and verified based on the stored VIN code and TCODE code.

[0055] Step S402: TBOX can read the VIN code and TCODE code, generate a target key based on the read VIN code and TCODE code, encrypt the terminal activation request based on the target key, and upload the encrypted terminal activation request carrying the VIN code and TCODE code to the cloud.

[0056] Step S403: The cloud can receive the terminal activation request uploaded from TBOX and verify it based on the VIN code and TCODE code carried in the terminal activation request to determine whether it is an in-stock vehicle. If the verification is successful, it decrypts the vehicle based on the received VIN code and TCODE code.

[0057] Step S404: If the cloud determines to activate the device after decrypting the activation request based on the terminal, it can generate activation result feedback information, encrypt the activation result feedback information based on the target key, and send the encrypted activation result feedback information to the TBOX.

[0058] Step S405: TBOX receives the activation result feedback information sent from the cloud, decrypts it based on the target key, and completes the initialization.

[0059] Step S406: TBOX can read the VIN code and TCODE code, generate a target key based on the read VIN code and TCODE code, encrypt the OTA update request based on the target key, and upload the encrypted OTA update request carrying the VIN code and TCODE code to the cloud.

[0060] Step S407: The cloud can receive OTA update requests uploaded from TBOX and verify them based on the VIN and TCODE codes carried in the OTA update requests to determine whether they are vehicles in the warehouse. If the verification is successful, the cloud can decrypt the data based on the received VIN and TCODE codes.

[0061] Step S404: If the cloud determines to perform an OTA update after decrypting the OTA update request, it can generate an update response information, encrypt the update response information based on the target key, and send the encrypted update response information to the TBOX.

[0062] Step S405: TBOX receives the update response information sent from the cloud, decrypts it based on the target key, and waits for the OTA update package.

[0063] This specification provides a vehicle-to-cloud interactive data transmission device. Please refer to [link / reference]. Figure 3 The vehicle-to-cloud interactive data transmission device may include a data acquisition module 310, a data filling module 320, a first encryption module 330, a second encryption module 340, and a data authentication module 350.

[0064] The data acquisition module 310 is used to acquire the dynamic key, as well as the vehicle's VIN code and TCODE code; wherein, the VIN code can uniquely identify the vehicle, and the TCODE code can uniquely identify the vehicle's on-board terminal. The data filling module 320 is used to fill and adjust the VIN code and TCODE code respectively based on a specified random number seed to obtain the first plaintext and the second plaintext; The first encryption module 330 is used to perform symmetric encryption on the first plaintext and the second plaintext respectively according to the dynamic key to obtain the first ciphertext corresponding to the first plaintext and the second ciphertext corresponding to the second plaintext; The second encryption module 340 is used to concatenate the first ciphertext and the second ciphertext to obtain the concatenated ciphertext, and to perform asymmetric encryption on the concatenated ciphertext to obtain the third ciphertext. The data authentication module 350 is used to determine the target key based on the specified length and the third ciphertext, and to encrypt or decrypt the vehicle-cloud interaction data based on the target key.

[0065] The specific functions and effects of the vehicle-to-cloud interactive data transmission device can be explained by referring to other embodiments in this manual, and will not be repeated here. Each module in the vehicle-to-cloud interactive data transmission device can be implemented entirely or partially through software, hardware, or a combination thereof. Each module can be embedded in or independent of the processor in the computer device in hardware form, or it can be stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0066] This specification also provides a chip, including a storage unit and a processing unit. The storage unit stores a computer program, and the processing unit executes the computer program to implement the vehicle-to-cloud interactive data transmission method in any of the above embodiments.

[0067] This specification also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a computer, implements the vehicle-to-cloud interactive data transmission method in any of the above embodiments.

[0068] This specification also provides a computer program product containing instructions that, when executed by a computer, implement the vehicle-to-cloud interactive data transmission method in any of the above embodiments.

[0069] This specification also provides a vehicle that includes the device described in any of the above embodiments.

[0070] This specification also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, which, when executed by the processor, implements the vehicle-to-cloud interactive data transmission method in any of the above embodiments.

[0071] In some implementations, please refer to Figure 4 The computer device can be a terminal, and its internal structure diagram can be as follows: Figure 4 As shown, the computer device includes a processor, memory, and communication interface connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, carrier networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a vehicle-to-cloud interactive data transmission method.

[0072] It is understood that the specific examples in this document are only intended to help those skilled in the art better understand the embodiments described herein, and are not intended to limit the scope of the invention.

[0073] It is understood that in the various embodiments described in this specification, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments described in this specification.

[0074] It is understood that the various implementation methods described in this specification can be implemented individually or in combination, and the implementation methods in this specification are not limited in this respect.

[0075] Unless otherwise stated, all technical and scientific terms used in the embodiments of this specification have the same meaning as commonly understood by one of ordinary skill in the art. The terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the scope of this specification. The term "and / or" as used in this specification includes any and all combinations of one or more of the associated listed items. The singular forms "a," "the," and "the" as used in the embodiments of this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.

[0076] It is understood that the processor in the embodiments of this specification can be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this specification. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this specification can be directly implemented by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory; the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above methods.

[0077] It is understood that the memory in the embodiments of this specification may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM). It should be noted that the memory in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0078] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this specification.

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

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

Claims

1. A vehicle-to-cloud interactive data transmission method, characterized in that, The method includes: Obtain the dynamic key, as well as the vehicle's VIN and TCODE codes; wherein the VIN code can uniquely identify the vehicle, and the TCODE code can uniquely identify the in-vehicle terminal in the vehicle. Based on a specified random number seed, the VIN code and the TCODE code are padded and adjusted to obtain the first plaintext and the second plaintext. The first plaintext and the second plaintext are symmetrically encrypted according to the dynamic key to obtain the first ciphertext corresponding to the first plaintext and the second ciphertext corresponding to the second plaintext. The first ciphertext and the second ciphertext are concatenated to obtain the concatenated ciphertext. The concatenated ciphertext is then subjected to asymmetric encryption to obtain the third ciphertext. The target key is determined based on the specified length and the third ciphertext, and the vehicle-cloud interaction data is encrypted or decrypted and verified based on the target key.

2. The vehicle-to-cloud interactive data transmission method according to claim 1, characterized in that, The step of symmetrically encrypting the first plaintext and the second plaintext respectively according to the dynamic key includes: Using the first plaintext as plaintext and the dynamic key as the key, symmetric encryption is performed in AES-ECB mode to generate the first ciphertext; Using the second plaintext as the plaintext and the dynamic key as the key, symmetric encryption is performed in AES-ECB mode to generate the second ciphertext.

3. The vehicle-to-cloud interactive data transmission method according to claim 1, characterized in that, The process of padding and adjusting the VIN code and TCODE code based on a specified random number seed includes: If the VIN code does not meet the set length rule, a first padding sequence is determined based on the byte length of the VIN code and the specified random number seed, and the VIN code is padded and adjusted according to the first padding sequence to obtain the first plaintext; wherein, the set length rule is used to constrain the byte length of the plaintext to be symmetrically encrypted to be an integer multiple of the specified length; If the TCODE code does not meet the set length rule, a second padding sequence is determined based on the byte length of the TCODE code and the specified random number seed, and the TCODE code is padded and adjusted according to the second padding sequence to obtain the second plaintext.

4. The vehicle-to-cloud interactive data transmission method according to claim 1, characterized in that, The method is applied to an in-vehicle terminal in a vehicle-cloud interaction system, which also includes a cloud platform that is communicatively connected to the in-vehicle terminal; the vehicle-cloud interaction data includes upload instructions and download instructions. The upload instruction includes a terminal activation request or OTA update request sent by the vehicle terminal to the cloud, and the send instruction includes activation result feedback information or update response information sent by the cloud to the vehicle terminal. The encryption or decryption verification of the transmitted vehicle-to-cloud interaction data based on the target key includes: The sending instruction is decrypted based on the target key; or, the upload instruction is encrypted based on the target key.

5. The vehicle-to-cloud interactive data transmission method according to claim 1, characterized in that, The method is applied to the cloud in the vehicle-cloud interaction system, which also includes an in-vehicle terminal that is communicatively connected to the cloud; the vehicle-cloud interaction data includes upload instructions and download instructions, and the upload instructions carry the vehicle's VIN code and TCODE code. The encryption or decryption verification of the transmitted vehicle-to-cloud interaction data based on the target key includes: The upload command is verified based on the VIN and TCODE codes, and decrypted based on the target key. Alternatively, the issued command can be encrypted based on the target key.

6. The vehicle-to-cloud interactive data transmission method according to claim 5, characterized in that, The method further includes: Based on a first specified period, a new dynamic key is issued to the vehicle terminal via the issued instruction; the dynamic key is different for different first specified periods; and / or, Based on the second specified period, a new specified random seed is sent to the vehicle terminal through the sending instruction, and the specified random seed is different for different second specified periods.

7. A vehicle-to-cloud interactive data transmission device, characterized in that, The device includes: The data acquisition module is used to acquire the dynamic key, as well as the vehicle's VIN code and TCODE code; wherein, the VIN code can uniquely identify the vehicle, and the TCODE code can uniquely identify the vehicle's on-board terminal. The data filling module is used to fill and adjust the VIN code and the TCODE code respectively based on a specified random number seed to obtain the first plaintext and the second plaintext; The first encryption module is used to symmetrically encrypt the first plaintext and the second plaintext according to the dynamic key, respectively, to obtain a first ciphertext corresponding to the first plaintext and a second ciphertext corresponding to the second plaintext; The second encryption module is used to concatenate the first ciphertext and the second ciphertext to obtain concatenated ciphertext, and to perform asymmetric encryption on the concatenated ciphertext to obtain the third ciphertext. The data authentication module is used to determine the target key based on the specified length and the third ciphertext, and to encrypt or decrypt the vehicle-cloud interaction data based on the target key.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the vehicle-to-cloud interactive data transmission method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the vehicle-to-cloud interactive data transmission method according to any one of claims 1 to 6.

10. A vehicle, characterized in that, Includes the device as described in claim 8.

Images