Data interaction system, method, device and readable storage medium

Abstract

The application provides a data interaction system, method, device and readable storage medium, and comprises the following steps: using a first DES key corresponding to a diagnostic instrument software end to encrypt target plaintext including a vehicle chassis number and an engine model to obtain first ciphertext; using an RSA public key to encrypt the first DES key to obtain second ciphertext; sending the first ciphertext and the second ciphertext to a preset server end; using the RSA public key to encrypt a second DES key corresponding to a CRM end to obtain third ciphertext, and sending the third ciphertext to the preset server end; using an RSA private key corresponding to the RSA public key to decrypt the second ciphertext and the third ciphertext to obtain the first DES key and the second DES key; using the first DES key to decrypt the first ciphertext to obtain the target plaintext; using the second DES key to encrypt the target plaintext to obtain fourth ciphertext; and sending the fourth ciphertext to the CRM end, so that the data security of a diagnostic instrument device data request can be ensured.

Description

Technical Field

[0001] This invention relates to the field of automotive information security technology, and in particular to a data interaction system, method, device, and readable storage medium. Background Technology

[0002] Currently, information security technologies are not widely applied in the automotive industry. Many diagnostic tools in the automotive sector lack encryption measures, allowing external attackers to easily crack their data acquisition interfaces and mimic the diagnostic tools to obtain data from the corresponding vehicle model's controller. In this situation, some critical vehicle data is at risk of leakage, and the data security of diagnostic tools during data interaction with the data system cannot be guaranteed. Summary of the Invention

[0003] The main objective of this invention is to provide a data interaction system, method, device, and readable storage medium, aiming to solve the technical problem that existing diagnostic instruments lack encryption measures, and the data security of diagnostic instruments cannot be guaranteed when interacting with data systems.

[0004] In a first aspect, the present invention provides a data interaction system, the data interaction system comprising:

[0005] The diagnostic software is used to encrypt the target plaintext using the first DES key corresponding to the diagnostic software to obtain the first ciphertext. The target plaintext includes the vehicle chassis number and engine model.

[0006] The first DES key is encrypted using the RSA public key to obtain the second ciphertext;

[0007] Send the first ciphertext and the second ciphertext to the preset server;

[0008] The CRM terminal uses an RSA public key to encrypt the corresponding second DES key to obtain a third ciphertext, and then sends the third ciphertext to a preset server.

[0009] The default server is used to decrypt the second and third ciphertexts using the RSA private key corresponding to the RSA public key, and obtain the first DES key and the second DES key.

[0010] Decrypt the first ciphertext using the first DES key to obtain the target plaintext;

[0011] The target plaintext is encrypted using the second DES key to obtain the fourth ciphertext;

[0012] Send the fourth encrypted message to the CRM terminal.

[0013] Optionally, the CRM terminal is also used to: decrypt the fourth ciphertext using the second DES key to obtain the target plaintext;

[0014] Send the target plaintext to the TSP system and obtain the data address corresponding to the EOL and basic software data obtained by the TSP system from the PDM system based on the target plaintext request.

[0015] The data address is encrypted using the second DES key to obtain the fifth ciphertext;

[0016] Send the fifth ciphertext to the preset server;

[0017] The preset server is also used for:

[0018] Decrypt the fifth ciphertext using the second DES key to obtain the data address;

[0019] The data address is encrypted using the first DES key to obtain the sixth ciphertext;

[0020] Send the sixth encrypted message to the diagnostic instrument software.

[0021] The diagnostic instrument software is also used for:

[0022] The sixth ciphertext is decrypted using the first DES key to obtain the data address, from which the EOL and basic software data are extracted.

[0023] Optionally, the data interaction system further includes:

[0024] The first monitoring module is used to determine whether the number of data requests made by the diagnostic instrument software within a preset time period exceeds a preset number.

[0025] If the preset number of attempts is not exceeded, the diagnostic software will execute the following steps: encrypt the target plaintext using the first DES key corresponding to the diagnostic software to obtain the first ciphertext, which includes the vehicle chassis number and engine model; encrypt the first DES key using the RSA public key to obtain the second ciphertext; and send the first ciphertext and the second ciphertext to the preset server.

[0026] Optionally, the data interaction system further includes:

[0027] The second monitoring module is used to compare whether the first positioning information from the diagnostic instrument software that sent the data request is consistent with the second positioning information of the vehicle.

[0028] If the comparison matches, the diagnostic software executes the following steps: encrypting the target plaintext using the first DES key corresponding to the diagnostic software to obtain the first ciphertext, the target plaintext including the vehicle chassis number and engine model; encrypting the first DES key using the RSA public key to obtain the second ciphertext; and sending the first ciphertext and the second ciphertext to the preset server. In this case, the first location information is determined based on the IP address of the data request, and the second location information is determined based on the interaction between the CRM terminal and the TSP system terminal.

[0029] Secondly, the present invention also provides a data interaction method, the data interaction method comprising the following steps:

[0030] The diagnostic tool software uses the first DES key corresponding to the diagnostic tool software to encrypt the target plaintext to obtain the first ciphertext, which includes the vehicle chassis number and engine model; it uses the RSA public key to encrypt the first DES key to obtain the second ciphertext; and sends the first ciphertext and the second ciphertext to the preset server.

[0031] The CRM client uses an RSA public key to encrypt the corresponding second DES key, obtains a third ciphertext, and sends the third ciphertext to the preset server.

[0032] The default server uses the RSA private key corresponding to the RSA public key to decrypt the second and third ciphertexts, obtaining the first and second DES keys; it uses the first DES key to decrypt the first ciphertext, obtaining the target plaintext; it uses the second DES key to encrypt the target plaintext, obtaining the fourth ciphertext; and it sends the fourth ciphertext to the CRM terminal.

[0033] Optionally, after the step of sending the fourth encrypted message to the CRM terminal from the preset server, the method further includes:

[0034] The CRM terminal uses the second DES key to decrypt the fourth ciphertext to obtain the target plaintext; it sends the target plaintext to the TSP system terminal and obtains the data address corresponding to the EOL and basic software data obtained by the TSP system terminal from the PDM system terminal based on the target plaintext; it uses the second DES key to encrypt the data address to obtain the fifth ciphertext; and it sends the fifth ciphertext to the preset server terminal.

[0035] The preset server uses the second DES key to decrypt the fifth ciphertext to obtain the data address; it uses the first DES key to encrypt the data address to obtain the sixth ciphertext; and it sends the sixth ciphertext to the diagnostic instrument software.

[0036] The diagnostic instrument software uses the first DES key to decrypt the sixth ciphertext, obtains the data address, and extracts the EOL and basic software data from the data address.

[0037] Optionally, before the step of encrypting the target plaintext using the first DES key corresponding to the diagnostic tool software to obtain the first ciphertext, wherein the target plaintext includes the vehicle chassis number and engine model, the following steps are also included:

[0038] The first monitoring module determines whether the number of data requests made by the diagnostic instrument software within a preset time period exceeds a preset number.

[0039] If the preset number of attempts is not exceeded, the diagnostic software will execute the following steps: encrypt the target plaintext using the first DES key corresponding to the diagnostic software to obtain the first ciphertext, which includes the vehicle chassis number and engine model; encrypt the first DES key using the RSA public key to obtain the second ciphertext; and send the first ciphertext and the second ciphertext to the preset server.

[0040] Optionally, before the step of encrypting the target plaintext using the first DES key corresponding to the diagnostic tool software to obtain the first ciphertext, wherein the target plaintext includes the vehicle chassis number and engine model, the following steps are also included:

[0041] The second monitoring module compares the first positioning information sent by the diagnostic instrument software with the second positioning information of the vehicle to see if they are consistent.

[0042] If the comparison matches, the diagnostic software executes the following steps: encrypting the target plaintext using the first DES key corresponding to the diagnostic software to obtain the first ciphertext, the target plaintext including the vehicle chassis number and engine model; encrypting the first DES key using the RSA public key to obtain the second ciphertext; and sending the first ciphertext and the second ciphertext to the preset server. In this case, the first location information is determined based on the IP address of the data request, and the second location information is determined based on the interaction between the CRM terminal and the TSP system terminal.

[0043] Thirdly, the present invention also provides a data interaction device, the data interaction device including a processor, a memory, and a data interaction program stored in the memory and executable by the processor, wherein when the data interaction program is executed by the processor, it implements the steps of the data interaction method as described above.

[0044] Fourthly, the present invention also provides a readable storage medium storing a data interaction program, wherein when the data interaction program is executed by a processor, it implements the steps of the data interaction method as described above.

[0045] This invention provides a data interaction system, method, device, and readable storage medium. The data interaction system includes: a diagnostic instrument software terminal, used to encrypt target plaintext using a first DES key corresponding to the diagnostic instrument software terminal to obtain a first ciphertext, the target plaintext including a vehicle chassis number and engine model; encrypting the first DES key using an RSA public key to obtain a second ciphertext; and sending the first and second ciphertexts to a preset server terminal; a CRM terminal, used to encrypt the second DES key corresponding to the CRM terminal using an RSA public key to obtain a third ciphertext, and sending the third ciphertext to the preset server terminal; the preset server terminal, used to decrypt the second and third ciphertexts using an RSA private key corresponding to the RSA public key to obtain a first and second DES keys; decrypting the first ciphertext using the first DES key to obtain the target plaintext; encrypting the target plaintext using the second DES key to obtain a fourth ciphertext; and sending the fourth ciphertext to the CRM terminal. This invention uses a hybrid encryption algorithm of RSA and DES to encrypt key data exchanged in the data interaction system, which can greatly ensure data security when the diagnostic instrument requests data. Attached Figure Description

[0046] Figure 1 This is a schematic diagram of the hardware structure of the data interaction device involved in the embodiment of the present invention;

[0047] Figure 2 This is a schematic diagram of the data interaction of functional modules in an embodiment of the data interaction system of the present invention;

[0048] Figure 3 This is a schematic diagram of the data interaction of functional modules in another embodiment of the data interaction system of the present invention;

[0049] Figure 4 This is a flowchart illustrating an embodiment of the data interaction method of the present invention;

[0050] Figure 5 This is a flowchart illustrating another embodiment of the data interaction method of the present invention.

[0051] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0052] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0053] In a first aspect, embodiments of the present invention provide a data interaction device.

[0054] Reference Figure 1 , Figure 1This is a schematic diagram of the hardware structure of the data interaction device involved in an embodiment of the present invention. In this embodiment, the data interaction device may include a processor 1001 (e.g., a Central Processing Unit, CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to implement communication between these components; the user interface 1003 may include a display screen or an input unit such as a keyboard; the network interface 1004 may optionally include a standard wired interface or a wireless interface (e.g., Wireless Fidelity, Wi-Fi); the memory 1005 may be high-speed random access memory (RAM) or stable memory (non-volatile memory), such as a disk storage device. Alternatively, the memory 1005 may also be a storage device independent of the aforementioned processor 1001. Those skilled in the art will understand that… Figure 1 The hardware structure shown does not constitute a limitation of the invention and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0055] Continue to refer to Figure 1 , Figure 1 The memory 1005, serving as a computer storage medium, may include an operating system, a network communication module, a user interface module, and a data interaction program. The processor 1001 can call the data interaction program stored in the memory 1005 and execute the data interaction method provided in this embodiment of the invention.

[0056] Secondly, embodiments of the present invention provide a data interaction system.

[0057] Reference Figure 2 , Figure 2 This is a schematic diagram of the data interaction of functional modules in an embodiment of the data interaction system of the present invention.

[0058] In one embodiment of the data interaction system of the present invention, the data interaction system includes:

[0059] The diagnostic software terminal 10 is used to encrypt the target plaintext using the first DES key corresponding to the diagnostic software terminal to obtain the first ciphertext. The target plaintext includes the vehicle chassis number and engine model.

[0060] The first DES key is encrypted using the RSA public key to obtain the second ciphertext;

[0061] Send the first ciphertext and the second ciphertext to the preset server;

[0062] In this embodiment, when a user uses a diagnostic tool, they typically need to diagnose or rewrite a controller on the vehicle. Before rewriting, the diagnostic tool needs to send an EOL (End of Hour) and basic software data request to the CRM (Customer Relationship Management) system. This data request includes the vehicle chassis number and engine model. The vehicle chassis number and engine model are key data in the data request, input by the user into the diagnostic tool software based on their needs. Using the vehicle chassis number and engine model in the data request, the type of controller on the vehicle requiring rewriting or diagnostics can be located. The diagnostic tool then retrieves the corresponding EOL and basic software data from the data system and sends it to the diagnostic tool, allowing the tool to diagnose or rewrite the controller using this data.

[0063] Therefore, in this embodiment, to ensure information security, the vehicle chassis number and engine model in the data request sent to the CRM terminal are used as the target plaintext. Then, the target plaintext is encrypted once using the DES encryption algorithm on the diagnostic software side to obtain the first ciphertext. During the encryption process, the corresponding first DES key on the diagnostic software side is used. The DES encryption algorithm is a symmetric encryption algorithm; both encryption and decryption use the same key. That is, the first ciphertext is encrypted with the first DES key and also needs to be decrypted with the first DES key. The advantages of the DES encryption algorithm are obvious: it is very fast to use, the key is relatively short, and the encryption speed is relatively fast. However, it cannot verify the true identity information of the communicating parties, and key management and distribution are difficult.

[0064] Furthermore, considering that the above method of encryption using only the DES encryption algorithm can improve data security to some extent during data exchange, the DES key itself is shared, leading to a relatively high probability of leakage. In contrast, the RSA encryption algorithm, as a relatively important asymmetric encryption algorithm, has both the public and private keys generated by the decryptor. The public key is publicly available and can be used for encryption, while the private key is kept secret by the decryptor for decryption. As long as the private key is not leaked, the encrypted information is secure, and currently there is no effective means to crack the RSA encryption algorithm.

[0065] Therefore, based on encrypting the target plaintext with the first DES key to obtain the first ciphertext, this embodiment introduces a trusted third-party pre-defined server. This server manages the RSA private key, while both the diagnostic software and the CRM terminal know the RSA public key. The diagnostic software can use the publicly available RSA public key to encrypt the target plaintext using the first DES key, obtaining the second ciphertext. This second ciphertext can only be decrypted by the pre-defined server possessing the RSA private key corresponding to the RSA public key. In other words, the ciphertext between the diagnostic software and the CRM terminal is relayed through the trusted third-party server.

[0066] The above methods use a combination of RSA and DES encryption algorithms to encrypt critical data exchanged in the data interaction system, which can greatly ensure data security when diagnostic equipment requests data.

[0067] CRM terminal 20 is used to encrypt the second DES key corresponding to the CRM terminal using the RSA public key to obtain the third ciphertext, and then send the third ciphertext to the preset server terminal.

[0068] In this embodiment, the CRM terminal also uses the DES encryption algorithm for encryption. Therefore, in order to prevent the DES key from being shared and causing the ciphertext to be leaked, the second DES key and the encrypted ciphertext corresponding to the DES encryption algorithm used by the CRM terminal also need to be encrypted into a third ciphertext using the RSA public key before being sent to the preset server to further increase the security during the transmission process.

[0069] The default server 30 is used to decrypt the second and third ciphertexts using the RSA private key corresponding to the RSA public key to obtain the first DES key and the second DES key.

[0070] Decrypt the first ciphertext using the first DES key to obtain the target plaintext;

[0071] The target plaintext is encrypted using the second DES key to obtain the fourth ciphertext;

[0072] Send the fourth encrypted message to the CRM terminal.

[0073] In this embodiment, when the preset server receives the first ciphertext, the second ciphertext, and the third ciphertext, it first decrypts the second ciphertext using the RSA private key corresponding to the RSA public key to obtain the first DES key, and then decrypts the third ciphertext to obtain the second DES key. Next, it uses the decrypted first DES key to decrypt the first ciphertext, which is encrypted with the critical data from the diagnostic instrument software, to obtain the target plaintext corresponding to the critical data. While ensuring data security from the diagnostic instrument software to the preset server, the preset server then re-encrypts the target plaintext using the second DES key from the CRM end to obtain the fourth ciphertext before sending it to the CRM end, further ensuring data security when critical data is transmitted from the preset server to the CRM end.

[0074] Furthermore, in one embodiment, reference is made to Figure 3 The CRM terminal 20 is also used to: decrypt the fourth ciphertext using the second DES key to obtain the target plaintext;

[0075] Send the target plaintext to the TSP system and obtain the data address corresponding to the EOL and basic software data obtained by the TSP system from the PDM system based on the target plaintext request.

[0076] The data address is encrypted using the second DES key to obtain the fifth ciphertext;

[0077] Send the fifth ciphertext to the preset server;

[0078] The preset server 30 is also used for:

[0079] Decrypt the fifth ciphertext using the second DES key to obtain the data address;

[0080] The data address is encrypted using the first DES key to obtain the sixth ciphertext;

[0081] Send the sixth encrypted message to the diagnostic instrument software.

[0082] The diagnostic instrument software terminal 10 is also used for:

[0083] The sixth ciphertext is decrypted using the first DES key to obtain the data address, from which the EOL and basic software data are extracted.

[0084] In this embodiment, after the CRM receives the fourth ciphertext from the preset server, it uses the second DES key to decrypt the fourth ciphertext, obtaining the target plaintext. The target plaintext is then sent to the TSP system. Based on the key data corresponding to the target plaintext (vehicle chassis number and engine model), the TSP system locates the controller type on the vehicle requiring flashing or diagnostics, obtains the required EOL and basic software data corresponding to the data address from the PDM system, and sends it to the CRM. After obtaining the data address corresponding to the EOL and basic software data, the CRM further encrypts the data address using the second DES key, obtaining the fifth ciphertext, which is then sent to the preset server to ensure data security during transmission from the CRM to the preset server.

[0085] After receiving the fifth ciphertext from the CRM terminal, the preset server first decrypts it using the second DES key to obtain the data address. Ensuring data security during transmission from the CRM terminal to the preset server, the preset server then re-encrypts the data address using the first DES key from the diagnostic software, obtaining the sixth ciphertext before sending it to the diagnostic software. This further ensures data security during transmission from the preset server to the diagnostic software.

[0086] After receiving the sixth ciphertext from the preset server, the diagnostic software decrypts it using the first DES key to obtain the data address. From this data address, the End-of-Life (EOL) and basic software data are extracted. The diagnostic equipment can then use this obtained EOL and basic software data to diagnose or rewrite the vehicle's controller. The security of the critical data sent by the diagnostic software through the above series of steps, as well as the data address obtained based on this critical data, is greatly guaranteed by the hybrid encryption method using RSA and DES encryption algorithms.

[0087] Furthermore, in one embodiment, the data interaction system further includes:

[0088] The first monitoring module is used to determine whether the number of data requests made by the diagnostic instrument software within a preset time period exceeds a preset number.

[0089] If the preset number of attempts is not exceeded, the diagnostic software will execute the following steps: encrypt the target plaintext using the first DES key corresponding to the diagnostic software to obtain the first ciphertext, which includes the vehicle chassis number and engine model; encrypt the first DES key using the RSA public key to obtain the second ciphertext; and send the first ciphertext and the second ciphertext to the preset server.

[0090] In this embodiment, in order to further prevent hackers from obtaining data, in addition to improving the security of critical data transmission when the diagnostic instrument software requests data, a first monitoring module is also set up in the data interaction system. The first monitoring module monitors whether the number of data requests made by the diagnostic instrument software corresponding to each authorized diagnostic instrument is normal within a preset time period, so as to determine whether there is a possibility that a hacker is impersonating this diagnostic instrument device.

[0091] Under normal circumstances, the number of data requests made by the diagnostic software within a preset time period will not exceed the preset number. The preset time period can be one day, and the preset number of data requests can be 20. If the number of data requests made by the diagnostic software within the preset time period exceeds the preset number, it indicates that an attacker may be impersonating the diagnostic device to obtain data. In this case, data request permissions for the diagnostic device should be immediately disabled.

[0092] When the number of data requests made by the diagnostic tool software within a preset time period does not exceed the preset limit, the data request permission for the diagnostic tool will remain open. At this time, the diagnostic tool software can send data requests to the CRM terminal to obtain the required EOL and basic software data. That is, when the data request permission for the corresponding diagnostic tool is open, the corresponding diagnostic tool software can perform the following steps: encrypt the target plaintext using the first DES key corresponding to the diagnostic tool software to obtain the first ciphertext, the target plaintext including the vehicle chassis number and engine model; encrypt the first DES key using the RSA public key to obtain the second ciphertext; and send the first ciphertext and the second ciphertext to the preset server.

[0093] Furthermore, in one embodiment, the data interaction system further includes:

[0094] The second monitoring module is used to compare whether the first positioning information from the diagnostic instrument software that sent the data request is consistent with the second positioning information of the vehicle.

[0095] If the comparison matches, the diagnostic software executes the following steps: encrypting the target plaintext using the first DES key corresponding to the diagnostic software to obtain the first ciphertext, the target plaintext including the vehicle chassis number and engine model; encrypting the first DES key using the RSA public key to obtain the second ciphertext; and sending the first ciphertext and the second ciphertext to the preset server. In this case, the first location information is determined based on the IP address of the data request, and the second location information is determined based on the interaction between the CRM terminal and the TSP system terminal.

[0096] In this embodiment, to further prevent attackers from acquiring data, in addition to improving the security of critical data transmission during data requests from the diagnostic software, a second monitoring module is also set up in the data interaction system. This second monitoring module compares the first location information of the diagnostic software sending the data request with the vehicle's second location information to determine if there is a possibility of an attacker impersonating the diagnostic device. The vehicle's second location information can be determined through interaction between the CRM and TSP systems, while the first location information of the diagnostic software sending the data request is determined based on the IP address of the diagnostic software sending the data request.

[0097] Under normal circumstances, when a user is using a diagnostic tool and its software to diagnose and reprogram a vehicle, the location of the diagnostic tool software and the vehicle should be consistent. If the addresses do not match, it indicates that an attacker may be impersonating the diagnostic tool to obtain data. In this case, you should immediately disable the diagnostic tool's data request permissions.

[0098] When the first location information from the diagnostic software sending the data request matches the vehicle's second location information, the diagnostic software's data request permission remains open. At this point, the diagnostic software can send a data request to the CRM to obtain the required EOL and basic software data. Specifically, when the diagnostic software's data request permission is open, the corresponding diagnostic software can perform the following steps: encrypt the target plaintext using the first DES key corresponding to the diagnostic software, obtaining the first ciphertext (which includes the vehicle chassis number and engine model); encrypt the first DES key using the RSA public key, obtaining the second ciphertext; and then send the first and second ciphertexts to a preset server.

[0099] This embodiment provides a data interaction system comprising: a diagnostic instrument software terminal, used to encrypt target plaintext using a first DES key corresponding to the diagnostic instrument software terminal to obtain a first ciphertext, the target plaintext including a vehicle chassis number and engine model; encrypting the first DES key using an RSA public key to obtain a second ciphertext; and sending the first ciphertext and the second ciphertext to a preset server terminal; a CRM terminal, used to encrypt the second DES key corresponding to the CRM terminal using an RSA public key to obtain a third ciphertext, and sending the third ciphertext to the preset server terminal; and the preset server terminal, used to decrypt the second ciphertext and the third ciphertext using an RSA private key corresponding to the RSA public key to obtain a first DES key and a second DES key; decrypting the first ciphertext using the first DES key to obtain the target plaintext; encrypting the target plaintext using the second DES key to obtain a fourth ciphertext; and sending the fourth ciphertext to the CRM terminal. This invention uses a hybrid encryption of RSA and DES encryption algorithms to encrypt key data exchanged in the data interaction system, which can greatly ensure data security when the diagnostic instrument requests data.

[0100] Thirdly, embodiments of the present invention also provide a data interaction method.

[0101] Reference Figure 4 A flowchart illustrating an embodiment of the data interaction method.

[0102] In this embodiment, the data interaction method includes:

[0103] Step S10: The diagnostic tool software uses the first DES key corresponding to the diagnostic tool software to encrypt the target plaintext to obtain the first ciphertext. The target plaintext includes the vehicle chassis number and engine model. The first DES key is encrypted using the RSA public key to obtain the second ciphertext. The first ciphertext and the second ciphertext are sent to the preset server.

[0104] Step S20: The CRM terminal uses the RSA public key to encrypt the corresponding second DES key to obtain the third ciphertext, and sends the third ciphertext to the preset server.

[0105] Step S30: The pre-set server uses the RSA private key corresponding to the RSA public key to decrypt the second ciphertext and the third ciphertext to obtain the first DES key and the second DES key; uses the first DES key to decrypt the first ciphertext to obtain the target plaintext; uses the second DES key to encrypt the target plaintext to obtain the fourth ciphertext; and sends the fourth ciphertext to the CRM terminal.

[0106] Furthermore, in one embodiment, reference is made to Figure 5 After the step of sending the fourth ciphertext to the CRM terminal from the preset server, the following is also included:

[0107] Step S40: The CRM terminal uses the second DES key to decrypt the fourth ciphertext to obtain the target plaintext; sends the target plaintext to the TSP system terminal and obtains the data address corresponding to the EOL and basic software data obtained by the TSP system terminal from the PDM system terminal based on the target plaintext; encrypts the data address using the second DES key to obtain the fifth ciphertext; and sends the fifth ciphertext to the preset server terminal.

[0108] Step S50: The preset server uses the second DES key to decrypt the fifth ciphertext to obtain the data address; it uses the first DES key to encrypt the data address to obtain the sixth ciphertext; and it sends the sixth ciphertext to the diagnostic instrument software.

[0109] In step S60, the diagnostic instrument software uses the first DES key to decrypt the sixth ciphertext to obtain the data address, and extracts the EOL and basic software data from the data address.

[0110] Furthermore, in one embodiment, before the step of encrypting the target plaintext using the first DES key corresponding to the diagnostic tool software to obtain the first ciphertext, wherein the target plaintext includes the vehicle chassis number and engine model, the following steps are also included:

[0111] The first monitoring module determines whether the number of data requests made by the diagnostic instrument software within a preset time period exceeds a preset number.

[0112] If the preset number of attempts is not exceeded, the diagnostic software will execute the following steps: encrypt the target plaintext using the first DES key corresponding to the diagnostic software to obtain the first ciphertext, which includes the vehicle chassis number and engine model; encrypt the first DES key using the RSA public key to obtain the second ciphertext; and send the first ciphertext and the second ciphertext to the preset server.

[0113] Furthermore, in one embodiment, before the step of encrypting the target plaintext using the first DES key corresponding to the diagnostic tool software to obtain the first ciphertext, wherein the target plaintext includes the vehicle chassis number and engine model, the following steps are also included:

[0114] The second monitoring module compares the first positioning information sent by the diagnostic instrument software with the second positioning information of the vehicle to see if they are consistent.

[0115] If the comparison matches, the diagnostic software executes the following steps: encrypting the target plaintext using the first DES key corresponding to the diagnostic software to obtain the first ciphertext, the target plaintext including the vehicle chassis number and engine model; encrypting the first DES key using the RSA public key to obtain the second ciphertext; and sending the first ciphertext and the second ciphertext to the preset server. In this case, the first location information is determined based on the IP address of the data request, and the second location information is determined based on the interaction between the CRM terminal and the TSP system terminal.

[0116] In the above-mentioned data interaction method, each step in the embodiment corresponds to each functional module in the above-mentioned data interaction system embodiment, and their functions and implementation processes will not be described in detail here.

[0117] Fourthly, embodiments of the present invention also provide a readable storage medium.

[0118] The present invention provides a data interaction program stored on a readable storage medium, wherein when the data interaction program is executed by a processor, it implements the steps of the data interaction method described above.

[0119] The method implemented when the data interaction program is executed can be referred to in various embodiments of the data interaction method of the present invention, and will not be repeated here.

[0120] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0121] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0122] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device to execute the methods described in the various embodiments of the present invention.

[0123] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

Claims

1. A data interaction system, characterized in that, The data interaction system includes: The diagnostic software is used to encrypt the target plaintext using the first DES key corresponding to the diagnostic software to obtain the first ciphertext. The target plaintext includes the vehicle chassis number and engine model. The first DES key is encrypted using the RSA public key to obtain the second ciphertext; Send the first ciphertext and the second ciphertext to the preset server; The CRM terminal uses an RSA public key to encrypt the corresponding second DES key to obtain a third ciphertext, and then sends the third ciphertext to a preset server. The default server is used to decrypt the second and third ciphertexts using the RSA private key corresponding to the RSA public key, and obtain the first DES key and the second DES key. Decrypt the first ciphertext using the first DES key to obtain the target plaintext; The target plaintext is encrypted using the second DES key to obtain the fourth ciphertext; Send the fourth encrypted message to the CRM terminal; The CRM terminal is also used to: decrypt the fourth ciphertext using the second DES key to obtain the target plaintext; Send the target plaintext to the TSP system and obtain the data address corresponding to the EOL and basic software data obtained by the TSP system from the PDM system based on the target plaintext request. The data address is encrypted using the second DES key to obtain the fifth ciphertext; Send the fifth ciphertext to the preset server; The preset server is also used for: Decrypt the fifth ciphertext using the second DES key to obtain the data address; The data address is encrypted using the first DES key to obtain the sixth ciphertext; Send the sixth encrypted message to the diagnostic instrument software. The diagnostic instrument software is also used for: The sixth ciphertext is decrypted using the first DES key to obtain the data address, from which the EOL and basic software data are extracted.

2. The data interaction system as described in claim 1, characterized in that, The data interaction system also includes: The first monitoring module is used to determine whether the number of data requests made by the diagnostic instrument software within a preset time period exceeds a preset number. If the preset number of attempts is not exceeded, the diagnostic software will execute the following steps: encrypt the target plaintext using the first DES key corresponding to the diagnostic software to obtain the first ciphertext, which includes the vehicle chassis number and engine model; encrypt the first DES key using the RSA public key to obtain the second ciphertext; and send the first ciphertext and the second ciphertext to the preset server.

3. The data interaction system as described in claim 1, characterized in that, The data interaction system also includes: The second monitoring module is used to compare whether the first positioning information from the diagnostic instrument software that sent the data request is consistent with the second positioning information of the vehicle. If the comparison matches, the diagnostic software executes the following steps: encrypting the target plaintext using the first DES key corresponding to the diagnostic software to obtain the first ciphertext, the target plaintext including the vehicle chassis number and engine model; encrypting the first DES key using the RSA public key to obtain the second ciphertext; and sending the first ciphertext and the second ciphertext to the preset server. In this case, the first location information is determined based on the IP address of the data request, and the second location information is determined based on the interaction between the CRM terminal and the TSP system terminal.

4. A data interaction method, characterized in that, The data interaction method includes: The diagnostic tool software uses the first DES key corresponding to the diagnostic tool software to encrypt the target plaintext to obtain the first ciphertext, which includes the vehicle chassis number and engine model; it uses the RSA public key to encrypt the first DES key to obtain the second ciphertext; and sends the first ciphertext and the second ciphertext to the preset server. The CRM client uses an RSA public key to encrypt the corresponding second DES key, obtains a third ciphertext, and sends the third ciphertext to the preset server. The default server uses the RSA private key corresponding to the RSA public key to decrypt the second and third ciphertexts, obtaining the first and second DES keys; it uses the first DES key to decrypt the first ciphertext, obtaining the target plaintext; it uses the second DES key to encrypt the target plaintext, obtaining the fourth ciphertext; and it sends the fourth ciphertext to the CRM client. Following the step of sending the fourth ciphertext to the CRM terminal from the preset server, the following is also included: The CRM terminal uses the second DES key to decrypt the fourth ciphertext to obtain the target plaintext; it sends the target plaintext to the TSP system terminal and obtains the data address corresponding to the EOL and basic software data obtained by the TSP system terminal from the PDM system terminal based on the target plaintext; it uses the second DES key to encrypt the data address to obtain the fifth ciphertext; and it sends the fifth ciphertext to the preset server terminal. The preset server uses the second DES key to decrypt the fifth ciphertext to obtain the data address; it uses the first DES key to encrypt the data address to obtain the sixth ciphertext; and it sends the sixth ciphertext to the diagnostic instrument software. The diagnostic instrument software uses the first DES key to decrypt the sixth ciphertext, obtains the data address, and extracts the EOL and basic software data from the data address.

5. The data interaction method as described in claim 4, characterized in that, Before the step of encrypting the target plaintext using the first DES key corresponding to the diagnostic tool software to obtain the first ciphertext, wherein the target plaintext includes the vehicle chassis number and engine model, the following steps are also included: The first monitoring module determines whether the number of data requests made by the diagnostic instrument software within a preset time period exceeds a preset number. If the preset number of attempts is not exceeded, the diagnostic software will execute the following steps: encrypt the target plaintext using the first DES key corresponding to the diagnostic software to obtain the first ciphertext, which includes the vehicle chassis number and engine model; encrypt the first DES key using the RSA public key to obtain the second ciphertext; and send the first ciphertext and the second ciphertext to the preset server.

6. The data interaction method as described in claim 4, characterized in that, Before the step of encrypting the target plaintext using the first DES key corresponding to the diagnostic tool software to obtain the first ciphertext, wherein the target plaintext includes the vehicle chassis number and engine model, the following steps are also included: The second monitoring module compares the first positioning information sent by the diagnostic instrument software with the second positioning information of the vehicle to see if they are consistent. If the comparison matches, the diagnostic software executes the following steps: encrypting the target plaintext using the first DES key corresponding to the diagnostic software to obtain the first ciphertext, the target plaintext including the vehicle chassis number and engine model; encrypting the first DES key using the RSA public key to obtain the second ciphertext; and sending the first ciphertext and the second ciphertext to the preset server. In this case, the first location information is determined based on the IP address of the data request, and the second location information is determined based on the interaction between the CRM terminal and the TSP system terminal.

7. A data interaction device, characterized in that, The data interaction device includes a processor, a memory, and a data interaction program stored in the memory and executable by the processor, wherein when the data interaction program is executed by the processor, it implements the steps of the data interaction method as described in any one of claims 4 to 6.

8. A readable storage medium, characterized in that, The readable storage medium stores a data interaction program, wherein when the data interaction program is executed by a processor, it implements the steps of the data interaction method as described in any one of claims 4 to 6.

Images