An on-vehicle component safety log function implementation method, device and computer system

Abstract

The application discloses a kind of vehicle-mounted component security log function implementation methods, steps are as follows: security log deployment: setting log recording component on each processor, the interface of log recording component is provided, security log is sent to IVI-SOC processor;Log recording: sensitive data access and / or network communication abnormal condition are logged;Security log forwarding: log forwarding component is responsible for the security log received from CAN network is forwarded to IVI-SOC processor by SPI;Collect and upload: IVI-SOC processor is provided with log collection component, and is responsible for collecting the security log of whole vehicle, and is uploaded to cloud by IDPS component.The application also discloses a kind of vehicle-mounted component security log function implementation device and computer system.The application can record or collect abnormal event of internal security mechanism of vehicle-mounted processor, and can be widely applied in new energy automobile field.

Description

Technical Field

[0001] This invention relates to new energy vehicles, and in particular to a method, device, and computer system for implementing a safety log function for vehicle components. Background Technology

[0002] Components that interact with the outside world via the network need to have a security protection function that records logs. When the security mechanism fails, the logs should be recorded and ensured that they cannot be illegally modified or replaced when access control mechanisms are in place. This should not affect the management of permissions for reading, writing, and deleting logs. The logs should also be uploaded to the cloud for data analysis through security measures such as authentication and encryption, so that security incidents can be displayed and traced.

[0003] Controllers on existing operating systems such as Android only record system logs based on system services, and do not record security event logs. Controllers without an operating system do not have the function of recording security logs.

[0004] In light of this, many have begun to undertake research and development work in this area.

[0005] For example, some technical solutions describe that after the IVI obtains the information security log generated by the gateway from the CAN bus, it promptly sends the obtained information security log to the cloud log collection server. However, the security log obtained from the CAN bus does not employ encryption, verification, or freshness counting technologies. Therefore, the lack of encryption, verification, and freshness counting technologies in the security log obtained from the CAN bus does not fundamentally solve this problem.

[0006] For example, some solutions utilize the VSOC cloud platform's data acquisition system to obtain real-time target vehicle data sent by the IDPS component of the target vehicle's ECU, aiming for better results. However, since the IDPS component is only integrated into the IVI controller, it cannot independently collect log messages from other controllers and related safety events, leaving the safety logging work incomplete.

[0007] Therefore, how to design a safety log on vehicle components has become an urgent problem to be solved. Summary of the Invention

[0008] The purpose of this invention is to overcome the shortcomings of the above-mentioned background technology and provide a method, device and computer system for implementing the safety log function of vehicle components, so that it can record or collect abnormal events of the internal security mechanism of SOC and MCU processors, and forward the recorded data of abnormal events of the security mechanism generated by other processors.

[0009] This invention provides a method for implementing a vehicle-mounted component safety log function, comprising the following steps: Safety log deployment: Corresponding log recording components are set on the VIUL processor, HAD / VIUR processor, IVI-MCU processor, and IVI-SOC processor, respectively, and interfaces are provided for the log recording components. The VIUL processor, HAD / VIUR processor, and IVI-MCU processor use these interfaces to send their respective safety logs to the IVI-SOC processor; Log recording: When one or more log recording components record abnormal situations of sensitive data access and / or network communication, the log recording components log the abnormal situations of sensitive data access and / or network communication; Safety log forwarding: A log forwarding component is set on the IVI-MCU processor. The log forwarding component is responsible for forwarding the safety logs received from the CAN network and the safety logs generated by the IVI-MCU processor itself to the IVI-SOC processor via SPI; Collection and uploading: The IVI-SOC processor is equipped with a log collection component responsible for collecting the vehicle's safety logs and uploading them to the cloud via an IDPS component set within the IVI-SOC processor. The log collection component and the IDPS component communicate via Binder.

[0010] In the above technical solution, the specific process of the IVI-SOC processor collecting log records within the processor during the collection and uploading steps is as follows: Calling and Sending: SOC-related components are set up on the IVI-SOC processor. These components call the log recording API interface of the SOC log system component set up on the IVI-SOC processor to send log data to the SOC log system component; Adding Time: The SOC log system component uses the Get System Time API interface to obtain the system time and adds it to the log data; Calling the Callback Function: The SOC log system component calls the callback function of the IDPS component to send the log data to IDPS; Storage: IDPS stores the logs; Sending to the Cloud: IDPS sends the logs to the cloud.

[0011] In the above technical solution, the specific process of the IVI-SOC processor collecting log records from external sources in the collection and uploading steps is as follows: Calling the start function: The SOC logging system component initiates and calls the start function; Registering the first callback function: The SOC logging system component calls the callback registration interface to register the first callback function with the SPI notification component; Registering the second callback function: The IDPS calls the callback registration interface to register the second callback function with the SOC logging system component; Receiving SPI messages: The SPI notification component receives SPI messages; Callback execution function: The SPI notification component calls the callback execution function of the SOC logging system component to pass the SPI message to the SOC logging system component; Obtaining system time: The SOC logging system component uses the obtain system time interface to obtain the system time and adds the system time to the log data; Sending to IDPS: The SOC logging system component calls the callback execution function on the IDPS side to send the log data to the IDPS; Log storage: The IDPS stores the log data; Sending to the cloud: The IDPS sends the log data to the cloud.

[0012] In the above technical solution, the specific process of the IVI-MCU processor receiving security logs from the CAN network in the security log forwarding step is as follows: Receiving CAN notification: The IVI-MCU processor's CAN notification receiving component receives the CAN notification; Processing CAN log data: The IVI-MCU processor processes the log data received from the CAN network; Forwarding CAN log data: The log forwarding API interface is called to forward the CAN log data to the MCU log system component set by the IVI-MCU processor; Decrypting log data: The MCU log system component calls the SecOC decryption API to decrypt the log data transmitted from the VIUL processor; Calling the SPI forwarding API: The MCU log system component calls the SPI forwarding API to send the log data to the IVI-SOC processor; Forwarding MCU log records: The MCU-related components set by the IVI-MCU processor call the MCU log recording API interface to send the log data to the MCU log system component; Sending to the IVI-SOC processor: The MCU log system component calls the SPI forwarding API to send the log data to the IVI-SOC processor.

[0013] In the above technical solution, the specific process of the VIUL processor sending security logs through the CAN network in the security log forwarding step is as follows: Log recording API sends log data: The VIUL-related components set by the VIUL processor call the log recording API to send the log data to the VIUL log system component set by the VIUL processor; First CAN sends log data: The VIUL log system component calls the CAN transmission API to send the log data to the IVI-MCU processor.

[0014] In the above technical solution, the specific process of the HAD / VIUR processor sending security logs via the CAN network in the security log forwarding step is as follows: Forwarding HAD / VIUR log records: The HAD / VIUR-related components set up by the HAD / VIUR processor call the HAD / VIUR log record API to send log data to the HAD / VIUR log system component set up by the HAD / VIUR processor; Encrypting log data: The HAD / VIUR log system component calls the SecOC encryption interface to encrypt the log data from the HAD / VIUR processor; Second CAN transmission of log data: The HAD / VIUR log system component calls the CAN transmission API to send the log data to the IV-MCU processor.

[0015] In the above technical solution, the log data transmitted in the CAN network adopts a simplified mode, transmitting only a few bytes of status code, with the time appended by the log collection component.

[0016] In the above technical solution, during the collection and uploading steps, the log collection component provides an interface for registering function callbacks. IDPS registers the log output function with the log collection component. When the log collection component receives log data from one or more of the VIUL processor, HAD / VIUR processor, and IVI-MCU processor, it calls the callback to forward the log data to the IDPS module. The IDPS component is responsible for local log caching and access control. The log transmission interface between the log collection component and the IDPS component uses SELinux to control access permissions.

[0017] The present invention also provides a device for implementing the safety log function of vehicle components, which stores a computer program that can execute the method for implementing the safety log function of vehicle components.

[0018] The present invention also provides a computer system, the computer system including a device for implementing the vehicle component safety log function.

[0019] The present invention provides a method, apparatus, and computer system for implementing the vehicle component safety log function, which has the following beneficial effects: The present invention ensures the secure transmission of the safety log between processors by transmitting the log records between processors through encryption, verification, and freshness counting mechanisms. Attached Figure Description

[0020] Figure 1 This is a schematic diagram of the overall process for implementing the vehicle-mounted component safety log function of the present invention;

[0021] Figure 2 This is a schematic diagram of the signal flow within the IVI-SOC processor in the vehicle-mounted component safety log function implementation method of the present invention;

[0022] Figure 3 This is a schematic diagram illustrating the process of the IVI-SOC processor collecting log records within the processor in the collection and uploading steps of the vehicle-mounted component safety log function implementation method of the present invention.

[0023] Figure 4 This is a schematic diagram illustrating the process of the IVI-SOC processor collecting external log records in the collection and uploading steps of the vehicle-mounted component safety log function implementation method of the present invention.

[0024] Figure 5 This is a schematic diagram illustrating the process of the IVI-MCU processor receiving the safety log from the CAN network in the safety log forwarding step of the vehicle-mounted component safety log function implementation method of the present invention.

[0025] Figure 6 This is a schematic diagram illustrating the process of the VIUL processor sending safety logs via the CAN network in the safety log forwarding step of the vehicle-mounted component safety log function implementation method of the present invention.

[0026] Figure 7 This is a schematic diagram illustrating the process of the HAD / VIUR processor sending the safety log through the CAN network in the safety log forwarding step of the vehicle-mounted component safety log function implementation method of the present invention.

[0027] Figure 8 This is a schematic diagram of the structure of the vehicle-mounted component safety log function implementation device of the present invention;

[0028] Figure 9 This is a schematic diagram of the computer system of the present invention. Detailed Implementation

[0029] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments, but these embodiments should not be construed as limiting the present invention.

[0030] The architecture and functional description of the vehicle safety log system are as follows:

[0031] See Figure 1 The method for implementing the vehicle-mounted component safety log function of the present invention includes the following steps:

[0032] Security Log Deployment: The first logging component is deployed on the IVI-SOC processor, the second logging component on the IVI-MCU processor, the third logging component on the VIUL processor, and the fourth logging component on the HAD / VIUR processor. Interfaces are provided for each logging component. The VIUL processor, HAD / VIUR processor, and IVI-MCU processor use these interfaces to send log data, which is ultimately transmitted to the log collection component of the IVI-SOC processor.

[0033] Log recording: When one or more logging components record abnormal situations of sensitive data access and / or network communication, the logging components will log the abnormal situations of sensitive data access and / or network communication.

[0034] Security log forwarding: A log forwarding component is deployed on the IVI-MCU processor. The log forwarding component is responsible for forwarding the security logs received from the CAN network and the security logs generated by the IVI-MCU processor itself to the log collection component of the IVI-SOC processor via SPI. The logs in the CAN network adopt a simplified mode, which only transmits a few bytes of status code. The log collection component is responsible for appending the time.

[0035] Collection and Upload: The log collection component on the IVI-SOC processor is responsible for collecting the vehicle's safety logs and uploading them to the cloud via the IDPS component located within the IVI-SOC processor. The log collection component and the IDPS component communicate via Binder. The log collection component provides an interface for registering function callbacks. The IDPS registers the log output function with the log collection component. When the log collection component receives logs from the first log recording component, the log forwarding component, and the second log recording component, it calls the callback to forward the logs to the IDPS module. Local caching and access control of the logs are handled by the IDPS component. The log transmission interface between the log collection component and the IDPS component uses SELinux to control access permissions.

[0036] II. The content and related definitions of the security log fields are as follows:

[0037] The logging and forwarding components (first logging component, second logging component, third logging component, fourth logging component, and log forwarding component) share common parameter definitions, sending parameters including the log's security level (level), log type (type), corresponding processor type (control), error code representing the log content (errcode), and log data content (log) to the log collection component. Among these,

[0038] (a) Log security levels are divided into the following 10 levels.

[0039] 0 emergency situations

[0040] 1. High-priority faults, such as database crashes

[0041] 2. Critical errors, such as hardware failures

[0042] 3 errors

[0043] 4 Warnings

[0044] 5 Special Circumstances That Require Attention

[0045] 6. General Information

[0046] 7 General Information

[0047] 8 Debugging Information

[0048] 9 Tracking Logs

[0049] 10 Undefined

[0050] (ii) Log types are divided into the following 4 categories:

[0051] 0 attack logs

[0052] 1 System Log

[0053] 2. Session Logs

[0054] 3 Other logs

[0055] (III) The corresponding processor types (control) are divided into the following 5 categories:

[0056] 0VIUL controller

[0057] 1VIUR controller

[0058] 2HAD controller

[0059] 3IVI-MCU Controller

[0060] 4IVI-SOC controller

[0061] (iv) The error code representing the log content is defined as follows:

[0062] Each processor needs to predefine that each Error corresponds to a string less than 16 bytes, with a maximum of 256 strings.

[0063] 0: [Secure Communication Component] SecOC module interface input parameter error

[0064] 1: [Secure Communication Component] SecOC module failed to generate MAC value.

[0065] 2: [Secure Communication Component] SecOC module MAC verification failed.

[0066] 3: [Secure Communication Component] Freshness value verification of SecOC module failed.

[0067] 4: [Secure Communication Component] SecOC module data encryption failed.

[0068] 5: [Secure Communication Component] SecOC module data decryption failed.

[0069] 6: [Secure Communication Component] SecOC module encryption key initialization failed.

[0070] 7: [Secure Communication Component] SecOC module failed to obtain Hash

[0071] 8: [Secure Communication Component] SecOC module Hash verification failed.

[0072] 9: [Cryptographic Services and Data Storage Components] CBC encryption failed.

[0073] 10: [Cryptographic Services and Data Storage Components] CBC decryption failed.

[0074] 11: [Cryptographic Services and Data Storage Components] CFB encryption failed.

[0075] 12: [Password Service and Data Storage Component] Failed to retrieve random number.

[0076] 13: [Password Service and Data Storage Components] Failed to retrieve hash data.

[0077] 14: [Cryptographic Services and Data Storage Components] Signature verification failed.

[0078] 15: [Password Service and Data Storage Component] Certificate verification failed.

[0079] 16: Error in the [Password Service and Data Storage Component] interface input parameters

[0080] 17: Password verification failed for [MCU controller external access authentication component].

[0081] 18: [MCU controller external access authentication component] failed to obtain password hash.

[0082] 19: [Diagnostic Security Component] Failed to obtain random number

[0083] 20: [Diagnostic Security Component] Failed to obtain Hash

[0084] 21: [Diagnostic Security Component] Failed to obtain Key

[0085] 22: [Diagnostic Security Component] Certificate verification failed.

[0086] 23: [Diagnose Security Components] Public key signature verification failed.

[0087] 24: [Log Data Component] failed to perform SC encryption.

[0088] 25: [Log Data Component] Controller type error

[0089] 26: [Log Data Component] failed to decrypt using SC.

[0090] 27: Password verification failed for [SOC controller external access component]

[0091] 28: Error in the interface input parameter of the [MCU controller external access authentication component]

[0092] 29: Error parameter in the [Diagnose Security Component] interface

[0093] 30: Error in the [Log Data Component] interface input parameter

[0094] 31: [Diagnostic Security Component] Authentication request data is not secure communication.

[0095] 32: [SOC controller external access component] UART user authentication failed.

[0096] 33: [Application Signature Authentication Component] Application verification failed.

[0097] 34: [Application Signature Authentication Component] The program is not running.

[0098] 35: [Application Signature Authentication Component] program has been killed.

[0099] 36: [Application Signature Authentication Component] script not running

[0100] 37: The [Application Signature Authentication Component] script has been killed.

[0101] 38: [Application Signature Authentication Component] operation not running.

[0102] 39: "[Application Signature Authentication Component] operation has been killed"

[0103] (v) The log data content (log) is defined as follows:

[0104] 2-bit controller identifier for sending logs

[0105] 4-bit log level

[0106] 2-bit log type

[0107] 1-byte log ID (range 0-255)

[0108] 2-byte log text data

[0109] 4-byte Secoc function data

[0110] See Figure 2 III. The architecture and signal flow of the security log-related components within the IVI-SOC processor are as follows:

[0111] The SOC-related components transmit the log data from the IVI-SOC processor to the first logging component, which then transmits it to the IDPS component via the log collection module. On the other hand, the SPI notification component transmits the SPI notification from the IVI-MCU processor to the log collection module, which then transmits it to the IDPS component.

[0112] See Figure 3 This diagram illustrates the calling relationships between the IVI-SOC logging component (the first logging component) and other components (other security components on the IVI, such as firewall, external port access authentication, Ethernet encryption and trusted program loading, and log collection components). It is a sequence diagram of relevant interface calls transmitted from the IVI-SOC processor's logging component when the IVI-SOC processor collects log records within the processor. The specific process is as follows:

[0113] Call Send 1: Other components (i.e., SOC-related components) call the logging API interface of the first logging component (i.e., the logging component in the diagram) to send log data to the first logging component.

[0114] Call 2: The first logging component calls the log forwarding API to send log data to the log collection component.

[0115] Adding Time: The log collection component uses the system time API to obtain the system time and adds the system time to the log data.

[0116] Calling the callback function: The log collection component calls the callback function of the IDPS component to send log data to IDPS.

[0117] Storage: IDPS stores the logs.

[0118] Send to the cloud: IDPS sends logs to the cloud.

[0119] See Figure 4 This diagram illustrates the calling relationships between the IVI-SOC log collection component and the IDPS and SPI notification receiving components. It is a timing diagram of the relevant interface calls for receiving SPI notifications when the IVI-SOC processor collects log records from external sources. The specific process is as follows:

[0120] Calling the start function: The log collection component calls the start function upon startup.

[0121] Register the first callback function: The log collection component calls the callback registration interface to register the first callback function with the SPI notification component (i.e., the SPI notification module in the diagram).

[0122] Registering a second callback function: IDPS calls the callback registration interface to register a second callback function with the log collection component.

[0123] Receive SPI messages: The SPI notification component has received an SPI message.

[0124] Callback execution function: The SPI notification component calls the callback execution function of the log collection component to pass the SPI message to the log collection component.

[0125] Get System Time: The log collection component uses the Get System Time interface to obtain the system time and adds the system time to the log data.

[0126] Send to IDPS: The log collection component calls the callback function on the IDPS side to send the log data to IDPS.

[0127] Log storage: IDPS stores the logs.

[0128] Send to the cloud: IDPS sends logs to the cloud.

[0129] See Figure 5Fourth, this diagram reflects the calling relationships between the IVI-MCU logging component (log forwarding component, second log recording component) and other component modules (including other security components on the IVI-MCU such as port access authentication, communication encryption component, encryption / decryption component, diagnostic security component, IVI-MCU CAN notification receiving component, SPI forwarding component, and SecOC component). It is a timing diagram of the relevant interface calls for the IVI-MCU processor to receive log records issued by CAN notification and other components when receiving security logs from the CAN network. The specific process is as follows:

[0130] Receive CAN notification: The IVI-MCU CAN notification receiving component (i.e., the CAN notification module in the diagram) receives the CAN notification.

[0131] Processing CAN log data: The IVI-MCU processes the log data received from the CAN network.

[0132] Forward CAN log data: Call the log forwarding API interface to forward the log CAN message to the log forwarding component.

[0133] Decrypting log data: The log forwarding component calls the SecOC decryption API to decrypt the log data transmitted from the VIUL processor.

[0134] Calling the SPI forwarding API: The log forwarding component calls the SPI forwarding API to send log data to IVI-SOC.

[0135] Forwarding MCU log records: Other components (i.e., MCU-related components) call the log recording API interface to send log data to the second log recording component (i.e., the log recording component in the diagram).

[0136] Sending to the IVI-SOC processor: The second logging component calls the SPI forwarding API to send log data to the IVI-SOC.

[0137] See Figure 6 Fifth, this diagram illustrates the calling relationships between the VIUL processor's logging component (the third logging component) and other interfaces (diagnostic security component, encryption / decryption component, and CAN message processing component). The specific process is as follows:

[0138] The logging API sends log data: Other components (i.e., VIUL-related components) call the logging API to send log information to the third logging component (i.e., the logging component in the diagram).

[0139] First CAN sends log data: Third logging component (i.e., the logging component in the diagram) calls the CAN sending API to send log data to the IVI-MCU processor.

[0140] See Figure 7 VI. This diagram illustrates the calling relationships between the HAD / VIUR processor's logging component (fourth logging component) and other interfaces (including the diagnostic security component, CAN communication encryption component, encryption / decryption component, SecOC secure communication component, and CAN message processing component on the HAD / VIUR processor). The specific process is as follows:

[0141] Forwarding HAD / VIUR log records: Other components (i.e., HAD / VIUR related components) call the log record API to send log data to the fourth log record component (i.e., the log record component in the diagram).

[0142] Encrypting log data: The fourth logging component calls the SecOC encryption interface to encrypt log data from the HAD / VIUR processor.

[0143] The second CAN transmits log data: The fourth logging component calls the CAN transmission API to send data to the IV-MCU processor.

[0144] See Figure 8 The present invention provides a device for implementing the safety log function of vehicle components, comprising the following steps:

[0145] Security log deployment module: Corresponding logging components are set on the VIUL processor, HAD / VIUR processor, IVI-MCU processor and IVI-SOC processor respectively, and an interface is provided for the logging components. The VIUL processor, HAD / VIUR processor and IVI-MCU processor use the interface to send their respective security logs to the IVI-SOC processor.

[0146] Log recording module: When one or more logging components record abnormal situations of sensitive data access and / or network communication, the logging components will log the abnormal situations of sensitive data access and / or network communication.

[0147] Security Log Forwarding Module: A log forwarding component is set on the IVI-MCU processor. The log forwarding component is responsible for forwarding the security logs received from the CAN network and the security logs generated by the IVI-MCU processor itself to the IVI-SOC processor via SPI.

[0148] Collection and Upload Module: The IVI-SOC processor is equipped with a log collection component responsible for collecting the vehicle's safety logs and uploading them to the cloud via the IDPS component located within the IVI-SOC processor. The log collection component and the IDPS component communicate with each other via Binder.

[0149] See Figure 9 The present invention relates to a computer system, wherein the computer system includes a device for implementing the vehicle component safety log function.

[0150] Technical principles and key technical points of this invention:

[0151] 1) Design and implementation principles, data structures, and function interface call relationships of the safety event recording system in vehicle components.

[0152] 2) Log data is securely transmitted in the CAN bus.

[0153] Definitions of abbreviations and key terms:

[0154] IVI: Entertainment and Audio System, also known as In-Vehicle Information Interaction System

[0155] IDPS: Intrusion Detection and Prevention System

[0156] SOC: System-on-a-Chip

[0157] MCU: Microcontroller Unit

[0158] Secoc: Board-side encrypted communication

[0159] Obviously, those skilled in the art can make various modifications and variations to this invention without departing from its spirit and scope. Therefore, if these modifications and variations fall within the scope of the claims of this invention and their equivalents, this invention also intends to include these modifications and variations.

[0160] The contents not described in detail in this specification are existing technologies known to those skilled in the art.

Claims

1. A method for implementing a safety log function for an on-board component, characterized in that: Includes the following steps: Security log deployment: Corresponding logging components are set up on the VIUL processor, HAD / VIUR processor, IVI-MCU processor and IVI-SOC processor respectively, and an interface is provided for the logging components. The VIUL processor, HAD / VIUR processor and IVI-MCU processor use the interface to send their respective security logs to the IVI-SOC processor. Log recording: When one or more logging components record abnormal situations of sensitive data access and / or network communication, the logging components will log the abnormal situations of sensitive data access and / or network communication. Security log forwarding: The IVI-MCU processor is equipped with a log forwarding component, which is responsible for forwarding the security logs received from the CAN network and the security logs generated by the IVI-MCU processor itself to the IVI-SOC processor via SPI; Collection and Upload: The IVI-SOC processor is equipped with a log collection component responsible for collecting the safety logs of the entire vehicle and uploading them to the cloud through the IDPS component set in the IVI-SOC processor. The log collection component and the IDPS component communicate with each other via Binder.

2. The method for implementing the vehicle-mounted component safety log function according to claim 1, characterized in that: In the collection and uploading step, the IVI-SOC processor collects the log records within the processor in the following specific process: Call sending: The IVI-SOC processor is equipped with SOC-related components, which call the logging API interface of the SOC logging system component set on the IVI-SOC processor to send log data to the SOC logging system component; Adding Time: The SOC log system component uses the Get System Time API interface to obtain the system time and adds the system time to the log data; Calling the callback function: The SOC logging system component calls the IDPS component's callback function to send log data to IDPS; Storage: IDPS stores the logs; Send to the cloud: IDPS sends logs to the cloud.

3. The method for implementing the vehicle-mounted component safety log function according to claim 1, characterized in that: In the collection and uploading steps, the specific process by which the IVI-SOC processor collects log records from external sources is as follows: Calling the start function: The SOC logging system component calls the start function upon startup; Registering the first callback function: The SOC logging system component calls the callback registration interface to notify the SPI component to register the first callback function; Registering the second callback function: IDPS calls the callback registration interface to register the second callback function with the SOC logging system component; Receiving SPI messages: The SPI notification component has received an SPI message; Callback execution function: The SPI notification component calls the callback execution function of the SOC logging system component to pass the SPI message to the SOC logging system component; Get System Time: The SOC log system component uses the Get System Time interface to obtain the system time and adds the system time to the log data; Send to IDPS: The SOC logging system component calls the IDPS-side callback execution function to send the log data to IDPS; Log storage: IDPS stores log data; Send to the cloud: IDPS sends log data to the cloud.

4. The method for implementing the vehicle-mounted component safety log function according to claim 1, characterized in that: In the security log forwarding step, the specific process by which the IVI-MCU processor receives security logs from the CAN network is as follows: Receive CAN notification: The IVI-MCU processor receives a CAN notification from the CAN notification receiving component; Processing CAN log data: The IVI-MCU processor processes the log data received from the CAN network; Forwarding CAN log data: Calling the log forwarding API interface to forward CAN log data to the MCU log system component configured by the IVI-MCU processor; Decrypting log data: The MCU log system component calls the SecOC decryption API to decrypt the log data transmitted from the VIUL processor; Calling the SPI forwarding API: The MCU logging system component calls the SPI forwarding API to send log data to the IVI-SOC processor; Forwarding MCU log records: The MCU-related components configured in the IVI-MCU processor call the API interface for MCU logging to send log data to the MCU logging system component; Send to IVI-SOC processor: The MCU logging system component calls the SPI forwarding API to send log data to the IVI-SOC processor.

5. The method for implementing the vehicle component safety log function according to claim 1, characterized in that: In the security log forwarding step, the specific process by which the VIUL processor sends security logs via the CAN network is as follows: The logging API sends log data: The VIUL-related components set up by the VIUL processor call the logging API to send log data to the VIUL logging system components set up by the VIUL processor; First CAN transmits log data: The VIUL logging system component calls the CAN transmission API to send log data to the IVI-MCU processor.

6. The method for implementing the vehicle component safety log function according to claim 1, characterized in that: In the security log forwarding step, the specific process by which the HAD / VIUR processor sends security logs via the CAN network is as follows: Forwarding HAD / VIUR log records: The HAD / VIUR-related components set up by the HAD / VIUR processor call the HAD / VIUR log record API to send log data to the HAD / VIUR log system components set up by the HAD / VIUR processor; Encrypting log data: The HAD / VIUR log system component calls the SecOC encryption interface to encrypt the log data from the HAD / VIUR processor; The second CAN transmits log data: The HAD / VIUR log system component calls the CAN transmission API to send log data to the IV-MCU processor.

7. The method for implementing the vehicle-mounted component safety log function according to any one of claims 1 to 6, characterized in that: Log data transmitted over the CAN network uses a simplified mode, transmitting only a few bytes of status code, with the time appended by the log collection component.

8. The method for implementing the vehicle component safety log function according to any one of claims 1 to 6, characterized in that: In the collection and uploading steps, the log collection component provides an interface for registering function callbacks. IDPS registers the log output function with the log collection component. When the log collection component receives log data from one or more of the VIUL processor, HAD / VIUR processor, and IVI-MCU processor, it calls the callback to forward the log data to the IDPS module. The IDPS component is responsible for local caching of logs and access control. The log transmission interface between the log collection component and the IDPS component uses SELinux to control access permissions.

9. A device for implementing a safety log function for vehicle components, comprising a computer program, characterized in that: The computer program is capable of executing the vehicle component safety log function implementation method as described in any one of claims 1 to 8.

10. A computer system, characterized in that: The computer system includes the vehicle component safety log function implementation device as described in claim 9.

Images