Vehicle-mounted TBOX log remote secure transmission method, device and medium

Through two-way authentication communication and encryption processing between the TBOX device and the backend server, the network security problem in TBOX log transmission is solved, and the comprehensive collection of the vehicle status and the secure transmission of log files are realized, ensuring the security of the transmission process Sex and integrity.

CN119030788AInactive Publication Date: 2024-11-26YODO SMART
View PDF 9 Cites 0 Cited by

Patent Information

Application Number
CN202411471059.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-10-21
Publication Date
2024-11-26
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

The existing TBOX log transmission has network security problems, which cannot effectively protect the vehicle's sensitive information, and cannot fully understand the vehicle's status, resulting in high maintenance costs and insufficient inspection support.

Method used

Through the two-way authentication communication between the TBOX device and the backend server, the certificate signature request information is obtained, the log data is obtained after security verification is performed, and the encrypted log files are sent using the public key infrastructure two-way authentication protocol to ensure the security of transmission.

Benefits of technology

It realizes encryption processing and secure storage of TBOX devices, associated controllers and vehicle communication data, ensures the confidentiality and integrity of log files during transmission, and provides comprehensive collection and secure transmission of the vehicle status.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119030788A_ABST
    Figure CN119030788A_ABST
Patent Text Reader

Abstract

The invention provides a vehicle-mounted TBOX log remote secure transmission method and device and a medium, and the method comprises the steps: carrying out the security verification of the device communication state of a TBOX device and a background server according to the certificate signature request information of the TBOX device; when the device communication state of the TBOX device and the background server is a secure communication state, the TBOX device is controlled to encrypt the TBOX device log data, the associated controller log data and the vehicle-mounted communication data, and a TBOX device log file, an associated controller log file and a vehicle-mounted communication log file are generated; according to a public key infrastructure bidirectional authentication communication protocol, the TBOX equipment is controlled to send a TBOX equipment log file, an association controller log file and a vehicle-mounted communication log file to a background server, so that the transmission safety of the log files is guaranteed while the complete vehicle state is comprehensively collected and recorded.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of vehicle-mounted data security transmission, and in particular to a vehicle-mounted TBOX log remote security transmission method, device and medium. Background Art

[0002] With the rapid development of intelligent vehicle networking, the market has put forward higher requirements for the secure interaction of applications and data between TBOX devices (Telematics BOX, an on-board remote communication terminal, a module integrating body network and wireless communication, used to connect the vehicle to the external network) and the background server of intelligent networking.

[0003] TBOX logs (log information of TBOX equipment operation) are important information for TBOX equipment / vehicle operation and maintenance. Uploading TBOX logs to the backend server of intelligent network connection through cellular network can facilitate operation and maintenance personnel to check problems of vehicles and TBOX equipment to reduce maintenance costs. And because TBOX logs record sensitive information of TBOX equipment / vehicles, and TBOX equipment has certain network security issues in the process of interaction with the backend server of intelligent network connection, it is necessary to ensure the security of log data while ensuring the convenience of operation and maintenance and providing detailed log information for checking vehicles / TBOX equipment.

[0004] The existing TBOX log generally only records the log information of the TBOX device itself, which is unable to understand the status of the entire vehicle and provides insufficient support for the troubleshooting of vehicle problems. In addition, the existing TBOX devices usually store the TBOX log in plain text or simply encrypt it and transmit it to the background server. The lack of security authentication can easily lead to the leakage of sensitive vehicle information. Summary of the invention

[0005] In view of the above technical problems, the technical solution adopted by the present invention is: According to one aspect of the present application, a method for remote secure transmission of vehicle-mounted TBOX logs is provided, which is applied to a log transmission system, wherein the log transmission system includes a TBOX device and a background server that is in communication connection with the TBOX device; Among them, the vehicle-mounted TBOX log remote secure transmission method described in this application includes: According to the certificate signature request information corresponding to the TBOX device, perform security verification on the device communication status between the TBOX device and the backend server; When the device communication status between the TBOX device and the background server is a secure communication status, the TBOX device log data, the associated controller log data and the vehicle communication data are obtained and sent to the TBOX device; the TBOX device log data is the log information data generated by the TBOX device during operation; the associated controller log data is the log information data generated by the vehicle controller that has a communication relationship with the TBOX device during operation; the vehicle communication data is the real-time information data transmitted on the vehicle communication bus connected to the TBOX device; Control the TBOX device to encrypt the TBOX device log data, the associated controller log data and the vehicle communication data respectively, and generate a TBOX device log file corresponding to the TBOX device log data, an associated controller log file corresponding to the associated controller log data and a vehicle communication log file corresponding to the vehicle communication data according to a preset log file generation storage rule; According to the public key infrastructure two-way authentication communication protocol, the TBOX device is controlled to send the TBOX device log file, the associated controller log file and the vehicle communication log file to the background server.

[0006] In an exemplary embodiment of the present application, according to the certificate signing request information corresponding to the TBOX device, a security check is performed on the device communication status between the TBOX device and the background server, including: Get the certificate signing request information corresponding to the TBOX device; Send the certificate signing request information to the backend server via the Hypertext Transfer Protocol (HTTP). If the device certificate sent by the background server is received, it is determined that the device communication state between the TBOX device and the background server is a secure communication state; the device certificate is a security certificate corresponding to the TBOX device generated after the background server verifies the certificate signature request information.

[0007] In an exemplary embodiment of the present application, a vehicle-mounted controller having a communication relationship with a TBOX device is used to perform the following method: In response to receiving a data provision request sent by a TBOX device, performing security verification on the TBOX device according to a security certificate corresponding to the TBOX device included in the data provision request; When the TBOX device passes the safety check, the associated controller log data is sent to the TBOX device.

[0008] In an exemplary embodiment of the present application, the log file generation storage rule includes the following method: Obtain the data volume n of the encrypted data; the encrypted data is any one of the encrypted data obtained by encrypting the TBOX device log data, the encrypted data obtained by encrypting the associated controller log data, and the encrypted data obtained by encrypting the vehicle communication data; Create roundup(n / m) initial files; roundup() is the preset upper integer function; m is the maximum amount of data that can be stored in the initial file; The n encrypted data are stored in the corresponding initial files in sequence according to the acquisition time.

[0009] In an exemplary embodiment of the present application, after generating the TBOX device log file, the associated controller log file and the vehicle communication log file, the TBOX device is further used to perform the following method: Obtain the file size of each TBOX device log file, associated controller log file and vehicle communication log file in real time; If the file size of any TBOX device log file, associated controller log file and vehicle communication log file reaches the corresponding storage data volume upper limit, the log file will be compressed; According to the storage address corresponding to the data type of the preset log file, each TBOX device log file, associated controller log file and vehicle communication log file are stored in the storage location at the corresponding storage address.

[0010] In an exemplary embodiment of the present application, after storing each TBOX device log file, the associated controller log file and the vehicle communication log file to the storage location at the respective corresponding storage address, the TBOX device is further used to perform the following method: When there is a log file that has been generated but not stored, the log file is determined as a log file to be stored; The log files stored in the TBOX device and having the same data type as the log file to be stored are determined as log files of the same type; Get the number of log files of the same type; If the number of files of the same type of log files is greater than the preset file storage threshold, the log file of the same type with the earliest generation time will be deleted, and the log file to be stored will be stored in the storage location at the storage address corresponding to the data type of the log file to be stored; if the number of files of the same type of log files is less than or equal to the preset file storage threshold, the log file to be stored will be stored in the storage location at the storage address corresponding to the data type of the log file to be stored.

[0011] In an exemplary embodiment of the present application, the TBOX device is also used to perform the following method: In the process of sending the TBOX device log file, the associated controller log file and the vehicle communication log file to the background server, if the file transmission is interrupted due to a network anomaly, the log file that has not been sent to the background server is determined as the log file to be transmitted; The network connection status is obtained in real time. When the network connection is normal, the log files to be transmitted are sent to the background server in sequence.

[0012] In an exemplary embodiment of the present application, the on-board controller having a communication relationship with the TBOX device and the TBOX device perform interactive communication via Ethernet of the SOMEIP protocol.

[0013] According to one aspect of the present application, a non-transitory computer-readable storage medium is provided, in which at least one instruction or at least one program is stored, and the at least one instruction or the at least one program is loaded and executed by a processor to implement the aforementioned vehicle-mounted TBOX log remote secure transmission method.

[0014] According to one aspect of the present application, an electronic device is provided, including a processor and the aforementioned non-transitory computer-readable storage medium.

[0015] The present invention has at least the following beneficial effects: The method for remote secure transmission of vehicle-mounted TBOX logs of the present invention first performs a legality security check on the device communication status of the TBOX device and the background server according to the certificate signature request information corresponding to the TBOX device. When the device communication status of the TBOX device and the background server is a secure communication status, the TBOX device encrypts the TBOX device log data generated when the TBOX device is running, the associated controller log data generated when the vehicle-mounted controller having a communication relationship with the TBOX device is running, and the vehicle-mounted communication data transmitted on the vehicle-mounted communication bus connected to the TBOX device, respectively, so as to improve the storage security of the generated TBOX device log files, the associated controller log files, and the vehicle-mounted communication log files, and store the log files securely. Finally, according to the public key infrastructure two-way authentication communication protocol, the TBOX device sends the TBOX device log files, the associated controller log files, and the vehicle-mounted communication log files to the background server, so as to ensure the transmission security of the log files while realizing the comprehensive collection and recording of the whole vehicle status. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0017] Figure 1 A flowchart of a method for remote secure transmission of vehicle-mounted TBOX logs provided by an embodiment of the present invention; Figure 2 A connection block diagram of a log transmission system provided by an embodiment of the present invention; Figure 3 A schematic diagram of data transmission between a TBOX device and a backend server provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0018] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0019] Since existing TBOX logs either do not have a remote log collection function, or the remote log transmission is not secure, or the log storage is not secure, or the log type is not detailed enough to troubleshoot difficult problems, there are safety hazards. Therefore, the present application proposes a method for remote secure transmission of vehicle-mounted TBOX logs.

[0020] A vehicle-mounted TBOX log remote secure transmission method is applied to log transmission systems, such as Figure 2 As shown, the log transmission system includes a TBOX device and a background server connected to the TBOX device for communication. The TBOX device is also connected to the vehicle's CAN bus and the Ethernet interface of the vehicle controller to transmit communication information and control information. The background server is the vehicle's intelligent network data transceiver server, which is used to send control signals to the TBOX device to achieve remote control of the vehicle, and receive vehicle status information.

[0021] like Figure 1 As shown, the vehicle-mounted TBOX log remote secure transmission method described in this application includes: Step S100: Perform security verification on the device communication status between the TBOX device and the background server according to the certificate signature request information corresponding to the TBOX device; Further, in step S100, according to the certificate signature request information corresponding to the TBOX device, a security check is performed on the device communication status between the TBOX device and the background server, including steps S110 to S130: Step S110: Obtain the certificate signature request information corresponding to the TBOX device; Step S120: Send the certificate signing request information to the backend server via the Hypertext Transfer Protocol Security protocol; Step S130: if the device certificate sent by the backend server is received, it is determined that the device communication state between the TBOX device and the backend server is a secure communication state; Among them, the device certificate is the security certificate corresponding to the TBOX device generated after the background server verifies the certificate signature request information, and is used for two-way authentication when the TBOX device and the background server perform log transmission.

[0022] When performing a legality and security check on a TBOX device, the TBOX device generates a Certificate Signing Request (CSR), generates a key pair, fills in identity information (such as organization name, device serial number, IMEI (International Mobile Equipment Identity), etc.), and submits the certificate signing request information to the backend server through an HTTPS (Hypertext Transfer Protocol Secure) request (one-way authentication with the backend server through the root certificate preset in the TBOX device). The backend server verifies the certificate signing request information and verifies the legality of the TBOX device. When the TBOX device passes the verification, the device certificate is sent to the TBOX device.

[0023] Step S200: when the device communication state between the TBOX device and the background server is a secure communication state, the TBOX device log data, the associated controller log data and the vehicle communication data are obtained and sent to the TBOX device; Among them, the TBOX device log data is the log information data generated by the TBOX device during its own operation; the associated controller log data is the log information data generated by the vehicle-mounted controller that has a communication relationship with the TBOX device during operation; the vehicle-mounted communication data is the real-time information data transmitted on the vehicle-mounted communication bus (which can be a CAN bus) connected to the TBOX device. The vehicle-mounted communication data supports CAN / CANFD format messages and collects the vehicle-mounted communication data on the CAN bus through the CAN transceiver of the TBOX device.

[0024] By collecting TBOX device log data, associated controller log data and vehicle communication data, a comprehensive record of vehicle status data can be achieved. At the same time, collecting rich types of logs can also help developers quickly locate existing problems.

[0025] Furthermore, the on-board controller and the TBOX device that have a communication relationship with the TBOX device interact and communicate with each other via Ethernet using the SOMEIP (Scalable service-oriented middleware over IP) protocol.

[0026] The vehicle-mounted controller in communication with the TBOX device is used to perform steps S210 to S220: Step S210: in response to receiving a data providing request sent by the TBOX device, performing security verification on the TBOX device according to the security certificate corresponding to the TBOX device included in the data providing request; Step S220: When the TBOX device passes the security check, the associated controller log data is sent to the TBOX device.

[0027] During the collection of associated controller log data, the TBOX device first broadcasts a service discovery request to all on-board controllers (ECUs) to determine the on-board controllers that can provide log services (i.e., the on-board controllers that have a communication relationship with the TBOX device). After receiving the service discovery request, the corresponding on-board controller verifies the legitimacy of the TBOX device's identity. When the TBOX device passes the legal verification, the TBOX device subscribes to the log service from the on-board controller. After the TBOX device successfully subscribes to the log service, the on-board controller will transmit the corresponding associated controller log data to the TBOX device.

[0028] Step S300, controlling the TBOX device to encrypt the TBOX device log data, the associated controller log data and the vehicle communication data respectively, and generating a TBOX device log file corresponding to the TBOX device log data, an associated controller log file corresponding to the associated controller log data and a vehicle communication log file corresponding to the vehicle communication data according to a preset log file generation and storage rule; Based on comprehensive considerations of equipment performance and security, the encryption methods for TBOX equipment log data, associated controller log data and vehicle communication data can adopt AES128 and XOR encryption methods.

[0029] As a feasible embodiment, the working mode of AES128 is ECB, the filling method of AES128 is PKCS7, the key of AES128 is obtained by performing MD5 digest algorithm on IMEI (International Mobile Equipment Identity) to obtain a 128-bit key value, and the 128-bit key value is used as the AES128 encryption key to cyclically encrypt the log file content.

[0030] As a feasible implementation example, the XOR filling mode is to fill the last bit with 0x00 if the original text length is not a multiple of 16 bytes. The XOR key is obtained by performing MD5 digest algorithm on IMEI to obtain a 128-bit key value, and the 128-bit key value is used as the XOR encryption key to cyclically encrypt the log file content.

[0031] The log file generation and storage rules include steps S311 to S313: Step S311, obtaining the data volume n of the encrypted data; The encrypted data is any one of the encrypted data obtained by encrypting the TBOX device log data, the encrypted data obtained by encrypting the associated controller log data, and the encrypted data obtained by encrypting the vehicle communication data.

[0032] Step S312, creating roundup(n / m) initial files; wherein roundup() is a preset ceiling function; and m is the maximum amount of data that can be stored in the initial file; Step S313: Store the n encrypted data in the corresponding initial file in sequence according to the acquisition time.

[0033] Furthermore, after generating the TBOX device log file, the associated controller log file and the vehicle communication log file, the TBOX device is further used to execute steps S321 to S323: Step S321, obtaining the file size of each TBOX device log file, associated controller log file and vehicle communication log file in real time; Step S322: If the file size of any TBOX device log file, associated controller log file and vehicle communication log file reaches the corresponding storage data volume upper limit, the log file is compressed to reduce storage space; Step S323: according to the preset storage address corresponding to the data type of the log file, each TBOX device log file, the associated controller log file and the vehicle communication log file are stored in the storage location at the corresponding storage address.

[0034] The data types of log files include TBOX device log data, associated controller log data and vehicle communication data. Each type of log file has a corresponding storage address to store log files of the corresponding data type, which is convenient for developers to manage and view data.

[0035] Furthermore, after storing each TBOX device log file, the associated controller log file and the vehicle communication log file to the storage location at the corresponding storage address, the TBOX device is also used to perform steps S331 to S334: Step S331: when there is a log file that has been generated but not stored, the log file is determined as a log file to be stored; Step S332: determine the log files stored in the TBOX device and having the same data type as the log file to be stored as log files of the same type; Step S333, obtaining the number of log files of the same type; Step S334: If the number of log files of the same type is greater than the preset file storage threshold, the log file of the same type with the earliest generation time will be deleted, and the log file to be stored will be stored in the storage location at the storage address corresponding to the data type of the log file to be stored; if the number of log files of the same type is less than or equal to the preset file storage threshold, the log file to be stored will be stored in the storage location at the storage address corresponding to the data type of the log file to be stored.

[0036] If the number of log files of the same type reaches the storage upper limit, old log files are deleted and new log files are stored according to the first-in-first-out principle to complete the update of log files while maintaining the file storage capacity.

[0037] Step S400: According to the public key infrastructure two-way authentication communication protocol, the TBOX device is controlled to send the TBOX device log file, the associated controller log file and the vehicle communication log file to the background server.

[0038] like Figure 3 As shown in the figure, before the TBOX device and the backend server transmit data, a communication link needs to be established first, that is, Figure 3 The first to fourth stages of Figure 3 The four stages are described separately: Phase 1: Establish security capabilities. The TBOX device sends a client_hello message to the backend server, and the backend server responds with a server_hello message to the TBOX device, establishing security attributes such as protocol version, session ID, and ciphertext family. At the same time, it generates and exchanges random numbers to prevent replay attacks. The ciphertext family parameters include key exchange method, encryption algorithm, MAC algorithm, encryption type, etc. Phase 2: Server Authentication and Key Exchange. The backend server will send its server certificate, the backend server sends a request for client certificate to the TBOX device, and the backend server sends a handshake complete, indicating the end of the hello phase of the backend server.

[0039] Phase 3: Client authentication and key exchange. When the TBOX device receives the handshake completion message sent by the background server, it will check the legitimacy of the server certificate, send the client certificate to the background server, and then send the client key exchange message. The content of the client key exchange message depends on the type of key exchange defined by client_hello and server_hello. The client certificate verification message is sent to verify the certificate sent by the TBOX device. The background server needs to verify the legitimacy of the certificate and the signature.

[0040] Phase 4: Modify the ciphertext family and end the handshake protocol. After the handshake is completed, the TBOX device and the backend server can send application layer data.

[0041] When uploading log files to the TBOX device, the encryption key and MAC key negotiated by the handshake protocol will be used to encrypt and decrypt the data and calculate the MAC signature to ensure the confidentiality, authentication, and integrity of the transmitted data.

[0042] The log upload action of the TBOX device is triggered by SMS or control instructions from the TSP (Telematics Service Provider) server. The log upload uses HTTPS two-way authentication based on the public key infrastructure (PKI) certificate to interact with the background server to upload the log file to the background server. This can ensure that the other party of the communication is the real identity it claims to be, reflecting the authenticity, and ensuring that the information is not tampered with or destroyed during storage or transmission, reflecting the integrity of the data. In addition to the two communicating parties, other parties cannot obtain the information, reflecting the confidentiality of the data and ensuring the security of the log transmission process.

[0043] like Figure 2 As shown in the figure, the background server provides three interfaces, namely, registration interface, upload interface and completion interface. The TBOX device calls these three interfaces in sequence to complete the upload of log files, specifically: register the file information to be uploaded to the background server through the registration interface, including: file name, file type, file size, etc. The background server returns the file ID to the TBOX device. According to the file ID returned by the registration interface, the background server is requested to upload the interface. After the log file corresponding to the file ID is uploaded, the background server is requested to complete the interface, indicating that the upload of this log file is completed.

[0044] In addition, when the TBOX device is sending the TBOX device log file, the associated controller log file and the vehicle communication log file to the background server, if the file transfer is interrupted due to a network abnormality, the log file that has not been sent to the background server will be identified as the log file to be transmitted, and the network connection status will be obtained in real time. When the network connection is normal, the log files to be transmitted will be sent to the background server in turn. This breakpoint-resume transmission mechanism can save the traffic consumption of uploading files on the vehicle side and the computing resource consumption of repeatedly uploading file content by the TBOX device in abnormal situations such as network instability.

[0045] When the in-vehicle TBOX log remote secure transmission method of the present invention is implemented, a data transmission communication link is first established between the TBOX device and the background server (which includes establishing security capabilities, server authentication and key exchange, client authentication and key exchange, modifying the ciphertext family and ending the handshake protocol in sequence). After the handshake between the TBOX device and the background server is completed, application layer data can be sent between the TBOX device and the background server. Then, according to the certificate signature request information corresponding to the TBOX device, the TBOX device is subjected to a legality security check. After the TBOX device passes the legality security check, the TBOX device obtains the TBOX device log data, the associated controller log data and the in-vehicle Communication data, the TBOX device then generates the TBOX device log file, the associated controller log file and the vehicle communication log file according to the TBOX device log data, the associated controller log data and the vehicle communication data. The TBOX device registers the file information to be uploaded with the background server through the registration interface of the background server. The background server returns the file ID to be uploaded to the TBOX device. The TBOX device then requests the background server to upload the interface according to the file ID, and uploads the log file corresponding to the file ID to the background server. After the log file is uploaded, the TBOX device requests the background server to complete the interface, indicating that the log file transmission is completed.

[0046] The method for remote secure transmission of vehicle-mounted TBOX logs of the present invention first performs a legality security check on the device communication status of the TBOX device and the background server according to the certificate signature request information corresponding to the TBOX device. When the device communication status of the TBOX device and the background server is a secure communication status, the TBOX device encrypts the TBOX device log data generated when the TBOX device is running, the associated controller log data generated when the vehicle-mounted controller having a communication relationship with the TBOX device is running, and the vehicle-mounted communication data transmitted on the vehicle-mounted communication bus connected to the TBOX device, respectively, so as to improve the security of the generated TBOX device log file, the associated controller log file and the vehicle-mounted communication log file, and store the log files securely. Finally, according to the public key infrastructure two-way authentication communication protocol, the TBOX device sends the TBOX device log file, the associated controller log file and the vehicle-mounted communication log file to the background server, so as to ensure the transmission security of the log files while realizing the comprehensive collection and recording of the whole vehicle status.

[0047] An embodiment of the present invention further provides a computer program product, which includes program code. When the program product is run on an electronic device, the program code is used to enable the electronic device to execute the steps of the method according to various exemplary embodiments of the present invention described above in this specification.

[0048] In an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above method is also provided.

[0049] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed by the present invention should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A method for remote and secure transmission of vehicle-mounted TBOX logs. It is characterized in that Applied to a log transmission system, the log transmission system includes a TBOX device and a background server communicating with the TBOX device; The vehicle-mounted TBOX log remote secure transmission method includes: According to the certificate signing request information corresponding to the TBOX device, a security check is performed on the device communication status between the TBOX device and the background server; When the device communication state between the TBOX device and the background server is a secure communication state, the TBOX device log data, the associated controller log data and the vehicle communication data are obtained and sent to the TBOX device; the TBOX device log data is the log information data generated by the TBOX device during operation; the associated controller log data is the log information data generated by the vehicle controller having a communication relationship with the TBOX device during operation; the vehicle communication data is the real-time information data transmitted on the vehicle communication bus connected to the TBOX device; Controlling the TBOX device to encrypt the TBOX device log data, the associated controller log data and the vehicle communication data respectively, and generating a TBOX device log file corresponding to the TBOX device log data, an associated controller log file corresponding to the associated controller log data and a vehicle communication log file corresponding to the vehicle communication data according to a preset log file generation and storage rule; According to the public key infrastructure two-way authentication communication protocol, the TBOX device is controlled to send the TBOX device log file, the associated controller log file and the vehicle communication log file to the background server.

2. The vehicle-mounted TBOX log remote secure transmission method according to claim 1, It is characterized in that The performing of security verification on the device communication status between the TBOX device and the background server according to the certificate signature request information corresponding to the TBOX device includes: Obtain the certificate signing request information corresponding to the TBOX device; Sending the certificate signing request information to the backend server via the Hypertext Transfer Protocol secure protocol; If the device certificate sent by the background server is received, it is determined that the device communication state between the TBOX device and the background server is a secure communication state; the device certificate is a security certificate corresponding to the TBOX device generated after the background server verifies the certificate signature request information.

3. The vehicle-mounted TBOX log remote secure transmission method according to claim 2, It is characterized in that The vehicle controller in communication with the TBOX device is used to perform the following method: In response to receiving a data providing request sent by the TBOX device, performing a security check on the TBOX device according to a security certificate corresponding to the TBOX device included in the data providing request; In case the TBOX device passes the security check, the associated controller log data is sent to the TBOX device.

4. The vehicle-mounted TBOX log remote secure transmission method according to claim 1, It is characterized in that The log file generation and storage rules include the following methods: Obtaining the data volume n of the encrypted data; the encrypted data is any one of the encrypted data obtained by encrypting the TBOX device log data, the encrypted data obtained by encrypting the associated controller log data, and the encrypted data obtained by encrypting the vehicle communication data; Create roundup(n / m) initial files; where roundup() is a preset upper integer function; and m is the maximum amount of data that can be stored in the initial file; The n encrypted data are stored in the corresponding initial files in sequence according to the acquisition time.

5. According to the vehicle-mounted TBOX log remote secure transmission method of claim 4, It is characterized in that After generating the TBOX device log file, the associated controller log file and the vehicle communication log file, the TBOX device is further used to execute the following method: Obtaining in real time the file size of each of the TBOX device log files, the associated controller log files and the vehicle communication log files; If the file size of any of the TBOX device log file, the associated controller log file and the vehicle communication log file reaches the corresponding upper limit of the storage data volume, the log file is compressed; According to the storage address corresponding to the data type of the preset log file, each of the TBOX device log file, the associated controller log file and the vehicle communication log file is stored in the storage location at the corresponding storage address.

6. The vehicle-mounted TBOX log remote secure transmission method according to claim 5, It is characterized in that After storing each of the TBOX device log files, the associated controller log files and the vehicle communication log files to the storage locations at the respective corresponding storage addresses, the TBOX device is further used to execute the following method: When there is a log file that has been generated but not stored, the log file is determined as a log file to be stored; Determine the log files stored in the TBOX device and having the same data type as the log file to be stored as log files of the same type; Obtain the number of log files of the same type; If the number of log files of the same type is greater than a preset file storage threshold, the log file of the same type with the earliest generation time is deleted, and the log file to be stored is stored in a storage location at a storage address corresponding to the data type of the log file to be stored; If the number of log files of the same type is less than or equal to a preset file storage amount threshold, the log file to be stored is stored in a storage location at a storage address corresponding to the data type of the log file to be stored.

7. The vehicle-mounted TBOX log remote secure transmission method according to claim 1, It is characterized in that The TBOX device is also used to perform the following method: In the process of sending the TBOX device log file, the associated controller log file and the vehicle communication log file to the backend server, if file transmission is interrupted due to network abnormality, the log file that has not been sent to the backend server is determined as a log file to be transmitted; The network connection status is obtained in real time, and when the network connection is normal, the log files to be transmitted are sent to the background server in sequence.

8. The vehicle-mounted TBOX log remote secure transmission method according to claim 1, It is characterized in that The on-board controller in communication with the TBOX device and the TBOX device perform interactive communication via Ethernet of the SOMEIP protocol.

9. A non-transitory computer-readable storage medium, wherein at least one instruction or at least one program is stored in the storage medium. It is characterized in that The at least one instruction or the at least one program is loaded and executed by the processor to implement the vehicle-mounted TBOX log remote secure transmission method as described in any one of claims 1-8.

10. An electronic device, It is characterized in that The invention comprises a processor and the non-transitory computer-readable storage medium as claimed in claim 9.

Citation Information

Patent Citations

  • Secure communication method for vehicle-mounted TBOX and cloud server

    CN110753321A

  • Method and device for remotely exporting TBOX log

    CN112437140A

  • Vehicle-mounted Ethernet detection defense method and device

    CN114978656A

  • OTA security communication method based on TLS bidirectional authentication

    CN115189925A

  • Log acquisition method, device and system of vehicle terminal and storage medium

    CN115884129A