Data encryption method and device and intelligent driving domain control device

Abstract

The embodiment of the invention provides a data encryption method and device and an intelligent driving domain control device. The method comprises the following steps: encrypting corresponding intelligent driving data through a generated character string to generate an encrypted file; and encrypting the character string through a main engine plant public key to generate a first digital envelope, and encrypting the character string through an intelligent driving provider public key to generate a second digital envelope. According to the technical scheme provided by the embodiment of the invention, the intelligent driving algorithm development and after-sales problem processing efficiency is improved, and the waste of resources is avoided.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of intelligent driving technology, and in particular to a data encryption method, device and intelligent driving domain control device. Background Art

[0002] Various intelligent driving data are generated during the operation of the intelligent driving system. For example, intelligent driving data may include vehicle surrounding environment data collected by sensors such as cameras, millimeter-wave radars, lidars, and ultrasonic radars, algorithm intermediate results generated during the operation of each intelligent driving module, and various logs generated during the operation of the intelligent driving system.

[0003] Before the above-mentioned smart driving data is saved and transmitted back to the cloud, it is necessary to encrypt the smart driving data to prevent data leakage. At present, the common development method of smart driving is joint development by the OEM and the smart driving provider. The OEM public key is used to encrypt the collected smart driving data in a digital envelope. After the encrypted data is transmitted back to the OEM cloud, the OEM private key is used to decrypt the encrypted data to obtain the smart driving data. Then, the public key of the smart driving provider can be used to encrypt the smart driving data to obtain the encrypted data for download by the smart driving provider.

[0004] However, the prior art has the following technical problems:

[0005] In some scenarios of smart driving function development and after-sales problem handling, smart driving providers can obtain collected smart driving data from the vehicle side, but because the smart driving data on the vehicle side is encrypted using the OEM's public key, the smart driving provider cannot decrypt the encrypted smart driving data and still needs to wait for the smart driving data to be transmitted back to the OEM's cloud, and use the OEM's private key to complete data decryption and the smart driving provider's public key to encrypt the smart driving data according to the above process before it can be used by the smart driving provider. This results in a long data link, affecting the efficiency of smart driving algorithm development and after-sales problem handling.

[0006] After the OEM cloud obtains the encrypted data A encrypted with the OEM public key, it needs to decrypt the encrypted data A and encrypt the encrypted data A with the public key of the smart driving provider to obtain the encrypted data B. Both the encrypted data A and the encrypted data B need to be stored in the OEM cloud. Since the smart driving provider cannot decrypt the encrypted data A, the encrypted data A can only be used by the OEM; since the OEM cannot decrypt the encrypted data B, the encrypted data B can only be used by the smart driving provider. Therefore, in the prior art, two copies of data need to be stored in the OEM cloud, resulting in a waste of cloud resources. Summary of the invention

[0007] In view of this, the embodiments of the present application provide a data encryption method, device and intelligent driving domain control device, which are used to improve the efficiency of intelligent driving algorithm development and after-sales problem handling, and avoid waste of cloud resources.

[0008] The first aspect provides a data encryption method, including:

[0009] The corresponding intelligent driving data is encrypted by using the generated character string to generate an encrypted file;

[0010] The character string is encrypted by the host manufacturer's public key to generate a first digital envelope, and the character string is encrypted by the smart driving provider's public key to generate a second digital envelope.

[0011] In a possible implementation, after encrypting the string by using the host manufacturer's public key to generate the first digital envelope and encrypting the string by using the smart driving provider's public key to generate the second digital envelope, the method further includes:

[0012] Establishing a first correspondence relationship for each of the encrypted files, wherein the first correspondence relationship includes a file path and a file name of the encrypted file and a correspondence relationship between a first digital envelope and a second digital envelope;

[0013] Acquire at least one target encrypted file from the generated encrypted files, query the first digital envelope and the second digital envelope corresponding to the file path and the file name of each target encrypted file according to the first corresponding relationship, and generate at least one key file according to the file path and the file name of at least one target encrypted file and the corresponding first digital envelope and the second digital envelope;

[0014] Upload at least one of the target encrypted files and the corresponding key file to the OEM cloud and the smart driving provider cloud.

[0015] In a possible implementation, encrypting the corresponding intelligent driving data by using the generated character string to generate an encrypted file includes:

[0016] The corresponding intelligent driving data is encrypted through the character string using a symmetric encryption algorithm to generate the encrypted file.

[0017] In a possible implementation, encrypting the string by using the host manufacturer's public key to generate the first digital envelope includes: using an asymmetric encryption algorithm to encrypt the string by using the host manufacturer's public key to generate the first digital envelope;

[0018] The encrypting the string by using the public key of the smart driving provider to generate the second digital envelope includes: using an asymmetric encryption algorithm to encrypt the string by using the public key of the smart driving provider to generate the second digital envelope.

[0019] In a possible implementation manner, obtaining at least one target encrypted file from the generated encrypted file includes:

[0020] At least one target encrypted file is obtained from the encrypted files according to the set trigger condition.

[0021] In a possible implementation, uploading at least one of the target encrypted files and the corresponding key file to the OEM cloud and the smart driving provider cloud includes:

[0022] By establishing the upload task, at least one of the target encrypted files and the corresponding key file are uploaded to the OEM cloud and the smart driving provider cloud.

[0023] A second aspect provides a data encryption method, comprising:

[0024] The OEM cloud receives at least one target encryption file and a corresponding key file uploaded by the intelligent driving domain control device;

[0025] The OEM cloud queries the corresponding first digital envelope from the corresponding key file according to the file path and file name of each target encrypted file, decrypts the first digital envelope using the OEM private key to generate a string, and decrypts the corresponding target encrypted file using the string to generate target intelligent driving data;

[0026] The smart driving provider cloud receives at least one target encryption file and a corresponding key file uploaded by the smart driving domain control device;

[0027] The smart driving provider cloud queries the corresponding second digital envelope from the corresponding key file according to the file path and file name of each target encrypted file, decrypts the second digital envelope using the smart driving provider private key to generate a string, and decrypts the corresponding target encrypted file using the string to generate target smart driving data.

[0028] A third aspect provides a data encryption device, comprising:

[0029] A first encryption module, used to encrypt the corresponding intelligent driving data through the generated character string to generate an encrypted file;

[0030] The second encryption module is used to encrypt the string by using the public key of the host manufacturer to generate a first digital envelope, and to encrypt the string by using the public key of the smart driving provider to generate a second digital envelope.

[0031] The fourth aspect provides an intelligent driving domain control device, comprising: one or more processors; a memory; and one or more computer programs, wherein the one or more computer programs are stored in the memory, and the one or more computer programs include instructions. When the instructions are executed by the intelligent driving domain control device, the intelligent driving domain control device executes the data encryption method in the above-mentioned first aspect or any possible implementation of the first aspect.

[0032] The fifth aspect provides a computer-readable storage medium, which includes a stored program, wherein when the program is running, the intelligent driving domain control device where the computer-readable storage medium is located is controlled to execute the data encryption method in the above-mentioned first aspect or any possible implementation of the first aspect.

[0033] In the technical solution provided in the embodiment of the present application, the corresponding intelligent driving data is encrypted by a generated character string to generate an encrypted file, the character string is encrypted by the public key of the host factory to generate a first digital envelope, and the character string is encrypted by the public key of the intelligent driving provider to generate a second digital envelope, thereby realizing a data encryption process based on a dual digital envelope, and being able to provide encrypted files and digital envelopes for the host factory cloud and the intelligent driving provider cloud, so that the host factory cloud can complete the decryption of the encrypted file through the first digital envelope and the intelligent driving provider cloud can complete the decryption of the encrypted file through the second digital envelope, thereby improving the efficiency of intelligent driving algorithm development and after-sales problem handling; both the host factory cloud and the intelligent driving provider cloud can decrypt the encrypted data, and the host factory cloud only needs to save one copy of the encrypted data, saving half of the storage space, thereby saving half of the public cloud storage rental fee, and avoiding the waste of cloud resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0035] Figure 1 A flowchart of a data encryption method provided in an embodiment of the present application;

[0036] Figure 2 A schematic diagram of the structure of a data encryption device provided in an embodiment of the present application;

[0037] Figure 3 A schematic diagram of the structure of an intelligent driving domain control device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0038] In order to better understand the technical solution of the present application, the embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0039] It should be clear that the described embodiments are only part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

[0040] The terms used in the embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to limit the present application. The singular forms "a", "said" and "the" used in the embodiments of the present application and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings.

[0041] It should be understood that the term "and / or" used in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0042] Figure 1 A flowchart of a data encryption method provided in an embodiment of the present application is shown in FIG. Figure 1 As shown, the method includes:

[0043] Step 102: The intelligent driving domain control device encrypts the corresponding intelligent driving data using the generated character string to generate an encrypted file.

[0044] In the embodiment of the present application, the intelligent driving domain control device can randomly generate a string, and use a symmetric encryption algorithm to encrypt the corresponding intelligent driving data through the string to generate an encrypted file. For example, the symmetric encryption algorithm can be an AES algorithm.

[0045] Specifically, an intelligent driving domain control device is provided in the intelligent driving vehicle, and the intelligent driving domain control device runs an encryption program. The intelligent driving vehicle can collect intelligent driving data. As an optional solution, the intelligent driving data may include vehicle surrounding environment data collected by sensors, algorithm intermediate results generated during the operation of each intelligent driving module, and various logs generated during the operation of the intelligent driving system. For example, the sensor may include at least one of a camera, a millimeter wave radar, a laser radar, and an ultrasonic radar. After the intelligent driving vehicle collects the intelligent driving data, the encryption program of the driving domain control device randomly generates a string of characters for the intelligent driving data, and uses a symmetric encryption algorithm to encrypt the intelligent driving data through the string to generate an encrypted file.

[0046] In the embodiment of the present application, the intelligent driving vehicle can collect multiple intelligent driving data, each of which corresponds to a string, so the intelligent driving domain control device can encrypt the corresponding intelligent driving data by the string to generate multiple encrypted files. Multiple encrypted files stored by the intelligent driving vehicle.

[0047] Step 104: The intelligent driving domain control device encrypts the string using the host manufacturer's public key to generate a first digital envelope, and encrypts the string using the intelligent driving provider's public key to generate a second digital envelope.

[0048] In the embodiment of the present application, the intelligent driving domain control device uses an asymmetric encryption algorithm to encrypt the string using the host manufacturer's public key to generate a first digital envelope, and uses an asymmetric encryption algorithm to encrypt the string using the intelligent driving provider's public key to generate a second digital envelope. For example, the asymmetric encryption algorithm may be an RSA algorithm.

[0049] Step 106: The intelligent driving domain control device establishes a first corresponding relationship for each encrypted file, where the first corresponding relationship includes the file path and file name of the encrypted file and the corresponding relationship between the first digital envelope and the second digital envelope.

[0050] The intelligent driving domain control device establishes a correspondence between the three fields of file path-file name-first digital envelope and second digital envelope for each encrypted file, and can save the correspondence between the file path, file name and the first digital envelope and the second digital envelope in the SQLite database.

[0051] Specifically, step 104 and step 106 may be executed by an encryption program of the intelligent driving domain control device.

[0052] Step 108: The intelligent driving domain control device obtains at least one target encrypted file from the generated encrypted file, queries the first digital envelope and the second digital envelope corresponding to the file path and file name of each target encrypted file according to the first corresponding relationship, and generates at least one key file according to the file path and file name of at least one target encrypted file and the corresponding first digital envelope and the second digital envelope.

[0053] In the embodiment of the present application, each key file may include the file path and file name of the target encrypted file and the corresponding first digital envelope and second digital envelope. The number of generated encrypted files may be one or more.

[0054] Specifically, the intelligent driving domain control device can obtain at least one target encrypted file from the encrypted file according to the trigger condition. In the embodiment of the present application, the trigger condition can be pre-set. As an optional solution, the trigger condition can be a set time period when the trigger event occurs. For example, the trigger condition may include a set time period when the automatic emergency braking system (Autonomous Emergency Braking, referred to as AEB) is triggered. The intelligent driving domain control device can obtain at least one encrypted file within the set time period from the encrypted file when the AEB is triggered, and use at least one encrypted file within the set time period as at least one target encrypted file. For another example, the trigger condition may include a set time period when the sensor camera image is blurred. The intelligent driving domain control device can obtain at least one encrypted file within the set time period from the encrypted file when the sensor camera image is blurred, and use at least one encrypted file within the set time period as at least one target encrypted file. For example, the set time period may include a first set time period before the trigger event occurs and a second set time period after the trigger event, or the set time period may include a time period after the trigger event occurs. In practical applications, the trigger condition can also adopt other conditions, which are not limited in the embodiment of the present application.

[0055] Specifically, the intelligent driving domain control device can obtain the corresponding first digital envelope and second digital envelope by accessing the SQLite database according to the file path and file name of the target encrypted file.

[0056] Step 110: The intelligent driving domain control device uploads at least one target encryption file and a corresponding key file to the OEM cloud and the intelligent driving provider cloud.

[0057] Specifically, the intelligent driving domain control device creates an upload task according to the frame number information of the intelligent driving vehicle, and obtains the task identifier (taskId) of the upload task, which is used to identify the upload task. The intelligent driving domain control device uploads at least one target encryption file and the corresponding key file to the OEM cloud and the intelligent driving provider cloud through the upload task. Among them, the key file may also include the task identifier and frame number information.

[0058] Specifically, step 108 and step 110 can be executed by an upload program of the intelligent driving domain control device.

[0059] Step 112: The host manufacturer cloud queries the corresponding first digital envelope from the corresponding key file according to the file path and file name of each target encrypted file, decrypts the first digital envelope using the host manufacturer's private key to generate a string, and decrypts the corresponding target encrypted file using the string to generate target intelligent driving data.

[0060] The number of target encrypted files received by the host factory cloud may be one or more, and each target encrypted file corresponds to a key file. The host factory cloud may execute step 112 to obtain the first digital envelope corresponding to each target encrypted file, decrypt the first digital envelope using the host factory private key to generate a string corresponding to each target encrypted file, and decrypt the corresponding target encrypted file using the string to generate target intelligent driving data, so that the host factory cloud can obtain the target intelligent driving data corresponding to each target encrypted file.

[0061] Step 114: The smart driving provider cloud queries the corresponding second digital envelope from the corresponding key file according to the file path and file name of each target encrypted file, decrypts the second digital envelope using the smart driving provider private key to generate a string, and decrypts the corresponding target encrypted file using the string to generate target smart driving data.

[0062] The number of target encrypted files received by the smart driving provider cloud may be one or more, and each target encrypted file corresponds to a key file. The smart driving provider cloud may execute step 114 to obtain the second digital envelope corresponding to each target encrypted file, decrypt the second digital envelope using the smart driving provider private key to generate a string corresponding to each target encrypted file, and decrypt the corresponding target encrypted file using the string to generate target smart driving data, so that the smart driving provider cloud can obtain the target smart driving data corresponding to each target encrypted file.

[0063] At this point, both the OEM cloud and the smart driving provider cloud can use strings to decrypt the smart driving data.

[0064] As an optional solution, if further analysis of the intelligent driving data is required, the upload task corresponding to the intelligent driving data can be located according to the task identifier in the key file, and the intelligent driving vehicle corresponding to the intelligent driving data can be located according to the frame number information.

[0065] In the technical solution provided in the embodiment of the present application, the corresponding intelligent driving data is encrypted by a generated character string to generate an encrypted file, the character string is encrypted by a host manufacturer's public key to generate a first digital envelope, and the character string is encrypted by a smart driving provider's public key to generate a second digital envelope, thereby realizing a data encryption process based on dual digital envelopes, and being able to provide encrypted files and digital envelopes for the host manufacturer's cloud and the smart driving provider's cloud, so that the host manufacturer's cloud can complete the decryption of the encrypted file through the first digital envelope and the smart driving provider's cloud can complete the decryption of the encrypted file through the second digital envelope, thereby improving the efficiency of smart driving algorithm development and after-sales problem handling.

[0066] In the technical solution provided in the embodiment of the present application, both the OEM cloud and the smart driving provider cloud can decrypt the encrypted data. The OEM cloud only needs to save one copy of the encrypted data, saving half of the storage space, thereby saving half of the public cloud storage rental fees and avoiding waste of cloud resources.

[0067] Figure 2 A schematic diagram of the structure of a data encryption device provided in an embodiment of the present application is shown in FIG. Figure 2 As shown, the device includes: a first encryption module 11 and a second encryption module 12.

[0068] The first encryption module 11 is used to encrypt the corresponding intelligent driving data through the generated character string to generate an encrypted file; the second encryption module 12 is used to encrypt the character string through the host manufacturer's public key to generate a first digital envelope, and to encrypt the character string through the intelligent driving provider's public key to generate a second digital envelope.

[0069] As an optional solution, the device further includes: an establishing module 13 , an acquiring module 14 , a querying module 15 , a generating module 16 and an uploading module 17 .

[0070] The establishment module 13 is used to establish a first correspondence relationship for each of the encrypted files, wherein the first correspondence relationship includes the file path, file name, and the correspondence between the first digital envelope and the second digital envelope of the encrypted file; the acquisition module 14 is used to obtain at least one target encrypted file from the generated encrypted file; the query module 15 is used to query the first digital envelope and the second digital envelope corresponding to the file path and file name of each of the target encrypted files according to the first correspondence relationship; the generation module 16 is used to generate at least one key file according to the file path and file name of at least one of the target encrypted files and the corresponding first digital envelope and the second digital envelope; the upload module 17 is used to upload at least one of the target encrypted files and the corresponding key file to the OEM cloud and the smart driving provider cloud.

[0071] As an optional solution, the first encryption module 11 is specifically used to encrypt the corresponding intelligent driving data through the character string using a symmetric encryption algorithm to generate the encrypted file.

[0072] As an optional scheme, the second encryption module 12 is specifically used to adopt an asymmetric encryption algorithm to encrypt the string through the OEM public key to generate the first digital envelope; and adopt an asymmetric encryption algorithm to encrypt the string through the smart driving provider public key to generate the second digital envelope.

[0073] As an optional solution, the acquisition module 14 is specifically configured to acquire at least one target encrypted file from the encrypted files according to a set trigger condition.

[0074] As an optional solution, the upload module 17 is specifically used to upload at least one of the target encrypted files and the corresponding key file to the OEM cloud and the smart driving provider cloud through an established upload task.

[0075] In the technical solution provided in the embodiment of the present application, the corresponding intelligent driving data is encrypted by a generated character string to generate an encrypted file, the character string is encrypted by a host manufacturer's public key to generate a first digital envelope, and the character string is encrypted by a smart driving provider's public key to generate a second digital envelope, thereby realizing a data encryption process based on dual digital envelopes, and being able to provide encrypted files and digital envelopes for the host manufacturer's cloud and the smart driving provider's cloud, so that the host manufacturer's cloud can complete the decryption of the encrypted file through the first digital envelope and the smart driving provider's cloud can complete the decryption of the encrypted file through the second digital envelope, thereby improving the efficiency of smart driving algorithm development and after-sales problem handling.

[0076] In the embodiment of the present application, both the OEM cloud and the smart driving provider cloud can decrypt the encrypted data. The OEM cloud only needs to save one copy of the encrypted data, saving half of the storage space, thereby saving half of the public cloud storage rental fee and avoiding waste of cloud resources.

[0077] An embodiment of the present application provides a computer-readable storage medium, which includes a stored program, wherein when the program is run, the intelligent driving domain control device where the storage medium is located is controlled to execute an embodiment of the above-mentioned data encryption method.

[0078] An embodiment of the present application provides an intelligent driving domain control device, comprising: one or more processors; a memory; and one or more computer programs, wherein the one or more computer programs are stored in the memory, and the one or more computer programs include instructions, which, when executed by the intelligent driving domain control device, enable the intelligent driving domain control device to perform the above-mentioned data encryption method.

[0079] Figure 3 A schematic diagram of the structure of an intelligent driving domain control device provided in an embodiment of the present application is shown in FIG. Figure 3 As shown, the intelligent driving domain control device 20 includes: a processor 21, a memory 22, and a computer program 23 stored in the memory 22 and executable on the processor 21. When the computer program 23 is executed by the processor 21, the data encryption method applied in the embodiment is implemented. To avoid repetition, they are not described one by one here.

[0080] The intelligent driving domain control device 20 includes, but is not limited to, a processor 21 and a memory 22. Those skilled in the art will understand that Figure 3It is only an example of the intelligent driving domain control device 20 and does not constitute a limitation of the intelligent driving domain control device 20. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the intelligent driving domain control device 20 may also include input and output devices, network access devices, buses, etc.

[0081] The processor 21 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0082] The memory 22 may be an internal storage unit of the intelligent driving domain control device 20, such as a hard disk or memory of the intelligent driving domain control device 20. The memory 22 may also be an external storage device of the intelligent driving domain control device 20, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped on the intelligent driving domain control device 20. Furthermore, the memory 22 may also include both an internal storage unit and an external storage device of the intelligent driving domain control device 20. The memory 22 is used to store computer programs and other programs and data required by the intelligent driving domain control device 20. The memory 22 may also be used to temporarily store data that has been output or is to be output.

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

[0084] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0085] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0086] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0087] The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (Processor) to perform some steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program code.

[0088] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A data encryption method, characterized in that: include: The corresponding intelligent driving data is encrypted by using the generated character string to generate an encrypted file; The character string is encrypted by the host manufacturer's public key to generate a first digital envelope, and the character string is encrypted by the smart driving provider's public key to generate a second digital envelope.

2. The method according to claim 1, characterized in that: After encrypting the string by the host manufacturer's public key to generate the first digital envelope and encrypting the string by the smart driving provider's public key to generate the second digital envelope, the method further includes: Establishing a first correspondence relationship for each of the encrypted files, wherein the first correspondence relationship includes a file path and a file name of the encrypted file and a correspondence relationship between a first digital envelope and a second digital envelope; Acquire at least one target encrypted file from the generated encrypted files, query the first digital envelope and the second digital envelope corresponding to the file path and the file name of each target encrypted file according to the first corresponding relationship, and generate at least one key file according to the file path and the file name of at least one target encrypted file and the corresponding first digital envelope and the second digital envelope; Upload at least one of the target encrypted files and the corresponding key file to the OEM cloud and the smart driving provider cloud.

3. The method according to claim 1, characterized in that The corresponding intelligent driving data is encrypted by the generated character string to generate an encrypted file, including: The corresponding intelligent driving data is encrypted through the character string using a symmetric encryption algorithm to generate the encrypted file.

4. The method according to claim 1, characterized in that: The step of encrypting the string using the host manufacturer's public key to generate the first digital envelope includes: using an asymmetric encryption algorithm to encrypt the string using the host manufacturer's public key to generate the first digital envelope; The encrypting the string by using the public key of the smart driving provider to generate the second digital envelope includes: using an asymmetric encryption algorithm to encrypt the string by using the public key of the smart driving provider to generate the second digital envelope.

5. The method according to claim 2, characterized in that: The obtaining at least one target encrypted file from the generated encrypted file comprises: At least one target encrypted file is obtained from the encrypted files according to the set trigger condition.

6. The method according to claim 2, characterized in that The uploading of at least one of the target encrypted files and the corresponding key file to the OEM cloud and the smart driving provider cloud includes: By establishing the upload task, at least one of the target encrypted files and the corresponding key file are uploaded to the OEM cloud and the smart driving provider cloud.

7. A data encryption method, characterized in that: include: The OEM cloud receives at least one target encryption file and a corresponding key file uploaded by the intelligent driving domain control device; The OEM cloud queries the corresponding first digital envelope from the corresponding key file according to the file path and file name of each target encrypted file, decrypts the first digital envelope using the OEM private key to generate a string, and decrypts the corresponding target encrypted file using the string to generate target intelligent driving data; The smart driving provider cloud receives at least one target encryption file and a corresponding key file uploaded by the smart driving domain control device; The smart driving provider cloud queries the corresponding second digital envelope from the corresponding key file according to the file path and file name of each target encrypted file, decrypts the second digital envelope using the smart driving provider private key to generate a string, and decrypts the corresponding target encrypted file using the string to generate target smart driving data.

8. A data encryption device, characterized in that: include: A first encryption module, used to encrypt the corresponding intelligent driving data through the generated character string to generate an encrypted file; The second encryption module is used to encrypt the string by using the public key of the host manufacturer to generate a first digital envelope, and to encrypt the string by using the public key of the smart driving provider to generate a second digital envelope.

9. An intelligent driving domain control device, characterized in that: include: one or more processors; Memory; And one or more computer programs, wherein the one or more computer programs are stored in the memory, and the one or more computer programs include instructions, which, when executed by the intelligent driving domain control device, enable the intelligent driving domain control device to execute the data encryption method described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein, when the program is running, the intelligent driving domain control device where the computer-readable storage medium is located is controlled to execute the data encryption method described in any one of claims 1 to 7.

Images