Log reporting method and device

Abstract

The invention discloses a log reporting method. The method comprises the following steps: acquiring log reporting strategy information; and reporting the first log of the first vehicle-mounted component or the hash value of the first log to at least one first server according to the log reporting strategy information, and reporting the first log or the hash value of the first log to at least one second server. The at least one first server is one or more of an OEM server, a supplier server or a supervision mechanism server, the at least one second server is one or more of the OEM server, the supplier server or the supervision mechanism server, and the first server is different from the second server. By adopting the embodiment of the invention, the logs of different servers or the hash values of the logs can be mutually verified, so that the logs or the hash values of the logs can be prevented from being tampered. The scheme can be further applied to the Internet of Vehicles, such as vehicle external connection V2X, inter-vehicle communication long term evolution technology LTE-V, vehicle-vehicle V2V and the like.

Description

Log reporting method and device Technical Field

[0001] The present application relates to the fields of Internet of Vehicles and communication technology, and in particular to a log reporting method and device. Background Art

[0002] Currently, when a car accident occurs and the cause needs to be determined or liability needs to be determined, logs can be analyzed. Typically, this analysis is done on logs provided by the original equipment manufacturer (OEM). However, these logs may be tampered with, making preventing log tampering a pressing technical challenge.

[0003] Summary of the Invention

[0004] The present application provides a log reporting method and device, which can prevent logs or log hash values ​​from being tampered with.

[0005] In a first aspect, a log reporting method is provided, including: obtaining log reporting policy information; reporting first log-related information of a first vehicle-mounted component to at least one first server according to the log reporting policy information, and reporting second log-related information of the first vehicle-mounted component to at least one second server.

[0006] In an embodiment of the present application, at least one first server is one or more of an OEM server, a supplier server, or a regulatory agency server, and at least one second server is one or more of an OEM server, a supplier server, or a regulatory agency server, and the first server is different from the second server.

[0007] Among them, the server mentioned in each embodiment of the present application can be a server or a server cluster composed of multiple servers. Specifically, the OEM server, supplier server or regulatory agency server can be a server containing a centralized storage of logs or hash values ​​of logs, or a distributed server cluster containing distributed storage of logs or hash values ​​of logs. For example, a distributed server can be a server cluster composed of multiple servers, and a server cluster can include servers of the same type or different types of servers. Exemplarily, server cluster #1 includes OEM server #A1 and OEM server #A2; server cluster #2 includes supplier server #B1 and supplier server #B2; server cluster #3 includes regulatory agency server #C1 and regulatory agency server #C2. Another example is that server cluster #1 includes OEM server #A1 and supplier server #B1, and server cluster #2 includes OEM server #A2, supplier server #B2 and regulatory agency server #C1. For the convenience of description, a single server, a distributed server, and a server cluster are collectively referred to as servers in the embodiments of the present application.

[0008] The vehicle-mounted component mentioned in the embodiment of the present application may be at least one component in the vehicle. The vehicle-mounted component may generate log-related information. The vehicle-mounted component may communicate with a server. Optionally, the vehicle-mounted component may be a separate component in the vehicle, or may be deployed as a module in the component. Furthermore, the vehicle-mounted component may be a hardware module or a computer program. For example, a module may be included in the vehicle's T-box, and the module may generate log-related information, so the Tbox may be regarded as a vehicle-mounted component. For another example, a component may be pre-assembled in the vehicle, and the component may have a processor or an integrated circuit integrated therein, and the component may generate log-related information, so the component may be regarded as a vehicle-mounted component.

[0009] For example, an on-board component may be one or more of a mobile data center (MDC) in the vehicle, a module or component for human-machine interaction (HMI), a gateway (GW), a telematics box (Tbox or TCU), an electronic control unit (ECU), a vehicle integrated / integration unit (VIU), a domain controller (DC), etc. Alternatively, it may be a media device in the vehicle, such as a camera or radar. An ECU is composed of one or more of a processor, memory, input / output (I / O) interface, analog-to-digital converter (A / D), and large-scale integrated circuits such as shaping and driving, and can perform a variety of functions.

[0010] Among them, the log involved in the embodiment of the present application may include at least one of the following: the time when the vehicle-mounted component performs the operation, the log type, the operation performed by the vehicle-mounted component, and the result of the operation performed by the vehicle-mounted component.

[0011] In an embodiment of the present application, the operations performed by the vehicle-mounted component can be used to implement one or more of a thermal management function, a seat management function, a door and window management function, an audio and video entertainment function, an automatic driving function, a body control function, an in-vehicle and out-of-vehicle communication function, an upgrade function, etc. The time when the vehicle-mounted component performs the operation may include one or more of the local time, the time offset of the universal time coordinated (UTC), etc. Optionally, the time when the vehicle-mounted component performs the operation may also include daylight saving time. Exemplarily, the time when the vehicle-mounted component performs the operation is: 2022-06-21 15:02:01.012+05:30. The result of the vehicle-mounted component performing the operation may include success or failure.

[0012] In addition, the log involved in the embodiment of the present application may also include at least one of the following: the danger level of the operation performed by the vehicle-mounted component, the name (or identification) of the operator who controls the vehicle-mounted component to perform the operation, the domain to which the vehicle-mounted component belongs, the terminal or access interface used when the vehicle-mounted component performs the operation, and additional information.

[0013] In an embodiment of the present application, the danger level of the operation performed by the on-board component can be determined based on the impact of the operation on the business of the on-board component. For example, if the operation has a great impact on the business, the danger level is high risk (risk); if the operation has an impact on the business but is controllable, the danger level is normal (normal); if the operation has no impact on the business, the danger level is none (none). Generally speaking, the danger level of the security log is normal or high risk. In one possible implementation, the business of the on-board component can be divided into: business with high latency requirements, i.e., low latency business, business with medium latency requirements, and business with low latency requirements. In another possible implementation, the business of the on-board component can be divided into: business with high reliability requirements, business with medium reliability requirements, and business with low reliability requirements. The domain to which the on-board component belongs can be, for example, one or more of the autonomous driving function domain, smart cockpit, etc. The additional information can be a supplement to the result of the operation performed by the on-board component, such as an error code. When there is no supplement, the log involved in the embodiment of the present application may not include the additional information.

[0014] When the on-board component is a separate component in the vehicle, the log involved in the embodiment of the present application may also include the service name or module name that creates the log in the on-board component. If the on-board component is a module or component for implementing HMI, the service name that creates the log in the on-board component may be an audio service. When the on-board component is a hardware module or a computer program, the log may also include the name of the subsystem or system where the on-board component is located. For example, the name of the subsystem or system where the on-board component is located may be an automatic driving system (ADS), a cockpit domain controller (CDC), a Tbox, a vehicle control unit (VCU), or a GW, etc.

[0015] The hash value of the log involved in the embodiment of the present application is obtained by performing a hash calculation on the log. Exemplarily, a hash function is used to perform a hash calculation on the log to obtain the hash value of the log. Optionally, the hash function involved in the embodiment of the present application may include, for example, a secure hash algorithm (SHA) 256. 2 , SHA256, SHA512, etc.

[0016] As can be seen, in the above technical solution, the first vehicle-mounted component can obtain log reporting policy information, and thus can report the first log-related information and the second log-related information of the first vehicle-mounted component to different servers respectively according to the log reporting policy information. Through this implementation, the log-related information of different servers can be mutually verified, thereby preventing the log-related information from being tampered with.

[0017] Optionally, in combination with the first aspect, the first log association information includes at least one of the first log and a hash value of the first log; and the second log association information includes at least one of the first log and a hash value of the first log.

[0018] As can be seen, in the above technical solution, log association information can include at least one of the log and the log's hash value, allowing different servers to obtain the same or different log content. This also allows log association information from different servers to be mutually verified, thereby preventing tampering with the log association information.

[0019] Optionally, in combination with the first aspect, the method further includes: reporting third log association information of the first vehicle-mounted component to at least one third server according to the log reporting policy information.

[0020] In an embodiment of the present application, at least one third server is one or more of an OEM server, a supplier server, or a regulatory agency server, and the first, second, and third servers are different. For example, first server #1 is OEM server #A1, second server #1 is supplier server #B1, and third server #1 is regulatory agency server #C1. For another example, first server #1 is OEM server #A1, first server #2 is supplier server #B1; second server #1 is supplier server #B2, second server #2 is regulatory agency server #C1; and third server #1 is OEM server #A2.

[0021] The third log association information may include at least one of the first log and a hash value of the first log.

[0022] It can be seen that in the above technical solution, the first vehicle-mounted component can also report the third log-related information of the first vehicle-mounted component to at least one third server according to the log reporting policy information, meeting the scenario of reporting log-related information to more servers.

[0023] Optionally, in combination with the first aspect, first log association information of the first vehicle-mounted component is reported to at least one first server according to the log reporting policy information, and second log association information of the first vehicle-mounted component is reported to at least one second server, including: according to the log reporting policy information, the first log association information is reported to at least one first server through the first security channel or the second vehicle-mounted component, and the second log association information is reported to at least one second server through the second security channel or the third vehicle-mounted component, the first security channel being the channel between the first vehicle-mounted component and each server in the at least one first server, the second security channel being the channel between the first vehicle-mounted component and each server in the at least one second server, a security channel being established between the second vehicle-mounted component and each server in the at least one first server, and a security channel being established between the third vehicle-mounted component and each server in the at least one second server.

[0024] In an embodiment of the present application, the secure channel may be one or more of an Internet Protocol Security (IPsec) secure channel, a Datagram Transport Layer Security (TLS) secure channel, a Datagram Transport Layer Security (DTLS) secure channel, or a Hypertext Transfer Protocol Secure (HTTPS) secure channel.

[0025] It should be understood that the first and second security channels may be of the same type, such as an IPsec security channel between the first vehicle-mounted component and each of the at least one first server, and an IPsec security channel between the first vehicle-mounted component and each of the at least one second server. Alternatively, the first and second security channels may be of different types, such as an IPsec security channel between the first vehicle-mounted component and each of the at least one first server, and a TLS security channel between the first vehicle-mounted component and each of the at least one second server.

[0026] Optionally, the first vehicle-mounted component is different from the second vehicle-mounted component and the third vehicle-mounted component. The second vehicle-mounted component and the third vehicle-mounted component may be the same or different, which is not limited here.

[0027] It can be seen that the above technical solution enriches the channels for reporting log association information. At the same time, because log association information can be reported through a secure channel, the security of log association information can be improved.

[0028] Optionally, in combination with the first aspect, the log reporting policy information includes at least one of the following: the identification of the vehicle-mounted component that needs to report the log, the destination address of the vehicle-mounted component for reporting the log, the type of log that the vehicle-mounted component needs to report, the triggering condition for the vehicle-mounted component to report the log, the log content that the vehicle-mounted component needs to report, or the first information; wherein, the first information is used to indicate the hash value of the log reported by the vehicle-mounted component or to indicate that the vehicle-mounted component reports the log.

[0029] In an embodiment of the present application, the destination address for the vehicle-mounted component to report a log may include at least one of the Internet Protocol (IP) addresses, Media Access Control (MAC) addresses, and the like of multiple servers. For example, the destination address for the first vehicle-mounted component to report a log may include the IP addresses of at least one first server and at least one second server, and may further include the IP address of at least one third server.

[0030] It should be understood that one server may correspond to one IP address and one MAC address, and the MAC address may be obtained through the IP address, and vice versa.

[0031] In this embodiment of the present application, the types of logs that the vehicle-mounted component needs to report may include operation logs or security logs. Operation logs are used to record user operation information, such as one or more of the user's account query history, vehicle navigation history, and vehicle music playback history. Security logs are used to record security access information, such as one or more of the user's login authentication information, network attack information, and access control information.

[0032] It can be seen that the above technical solution provides the specific content of the log reporting policy information, so that the vehicle-mounted components can better meet the needs when reporting logs or log hash values.

[0033] Optionally, in combination with the first aspect, the trigger condition includes at least one of the following: the danger level of the operation performed by the vehicle-mounted component is equal to or higher than the preset danger level; the cycle for the vehicle-mounted component to report the log arrives; a log reporting trigger event occurs.

[0034] In the embodiment of the present application, the preset risk level may be a value predefined, preconfigured, or pre-specified in the protocol, for example, high risk, general, or none, which is not limited here.

[0035] It can be seen that the above technical solution provides trigger conditions for the vehicle-mounted components to report logs, so that the vehicle-mounted components can better report logs or log hash values ​​according to the trigger conditions, avoiding the problem of low system performance caused by real-time reporting of logs or log hash values.

[0036] Optionally, in combination with the first aspect, the log reporting triggering event includes at least one of the following: the vehicle's event data recorder (EDR) is triggered, the vehicle's automatic driving is started, the vehicle's automatic driving is turned off, and the user is reminded to take over the driving control of the vehicle when the vehicle is in automatic driving mode, and the vehicle includes on-board components.

[0037] For example, EDR can be integrated into a software module within a vehicle's airbag control unit, enabling the vehicle's black box to generate logs. Generally, EDR is triggered when the vehicle is involved in a collision or experiences a dramatic change in speed. EDR triggering can be understood as the EDR starting to record logs.

[0038] It can be seen that the above technical solution provides a log reporting trigger event, so that the vehicle-mounted components can report the log or the hash value of the log when the log reporting trigger event occurs, avoiding the problem of low system performance caused by real-time reporting of the log or the hash value of the log.

[0039] Optionally, in combination with the first aspect, the log content includes at least one of the following: the operation performed by the vehicle-mounted component, the result of the operation performed by the vehicle-mounted component, and the time when the vehicle-mounted component performed the operation.

[0040] It can be seen that the above technical solution provides the log content that the vehicle-mounted components need to report, so that the logs or hash values ​​of the logs reported by the vehicle-mounted components can meet the requirements.

[0041] Optionally, in combination with the first aspect, the vehicle-mounted component includes a first vehicle-mounted component. That is, the vehicle-mounted component that needs to report the log includes the first vehicle-mounted component. Therefore, the first vehicle-mounted component can report the first log of the first vehicle-mounted component or the hash value of the first log according to the log reporting policy information.

[0042] Optionally, in combination with the first aspect, the method further includes: generating a first log or a hash value of the first log; or, sending second information to one or more of the second vehicle-mounted component and the third vehicle-mounted component, the second information being used to generate a hash value of the first log.

[0043] In the embodiment of the present application, the second information includes the first log.

[0044] It can be seen that in the above technical solution, the log is generated by the first vehicle-mounted component, and the hash value of the log can be generated by the first vehicle-mounted component, or by one or more of the second vehicle-mounted component and the third vehicle-mounted component, which enriches the generation method of the hash value of the log.

[0045] Optionally, in combination with the first aspect, at least one first server and at least one second server correspond to nodes of the blockchain network.

[0046] In the embodiment of the present application, at least one third server may also correspond to a node of the blockchain network. It should be understood that one server may correspond to one node of the blockchain network.

[0047] A blockchain is a chained data structure in which blocks are linked in chronological order. Furthermore, cryptography can be used to ensure that blockchains are tamper-proof and unforgeable. In this application, a block is the smallest unit in a blockchain used to store logs or log hashes. A block can consist of a header and a body.

[0048] The block header is mainly used to record one or more characteristic information of the current block. For example, the block header may include at least one characteristic information such as the version number, necessary information to form a chain structure with the previous block of the current block (such as the hash value (Prev_Hash) of the previous block of the current block), timestamp, and random number (nonce).

[0049] To determine the hash value of the current block, the various characteristic information in the block header of the current block can be concatenated in a predetermined order to form a string. This string is then hashed using a hash function to obtain a hash value, which serves as the hash value of the current block. Because the characteristic information included in the block headers of different blocks typically has different values, each block can be uniquely associated with a hash value. Because each block can be uniquely associated with a hash value, and each block header can include the hash value of the previous block (or previous block), multiple blocks can form a blockchain. The timestamp can be used to indicate the time the current block was generated.

[0050] The block body can be used to store logs or log hash values.

[0051] A blockchain network typically consists of multiple nodes, which communicate with each other via wired or wireless means. In a blockchain network, any node or accounting node can generate a new block based on the logs or log hashes reported by on-board components and broadcast it to other nodes. Other nodes then verify the block. Once all nodes in the blockchain network reach consensus, the new block is added to the blockchain. Accounting nodes are nodes in the blockchain network that have competitively obtained the right to record data. This means that once a accounting node obtains this right, it can store the logs or log hashes reported by on-board components in the blockchain.

[0052] It can be seen that in the above technical solution, different servers can correspond to nodes of the blockchain network, and then the tamper-proof and non-forgeable characteristics of the blockchain can be utilized to prevent the logs or the hash values ​​of the logs from being tampered with.

[0053] In a second aspect, a log reporting method is provided, including: generating log reporting policy information; and sending the log reporting policy information.

[0054] It can be seen that in the above technical solution, by sending log reporting policy information, the vehicle-mounted components can better meet the needs when reporting logs or log hash values.

[0055] Optionally, in combination with the second aspect, the log reporting policy information includes at least one of the following: the identification of the vehicle-mounted component that needs to report the log, the destination address of the vehicle-mounted component reporting the log, the type of log that the vehicle-mounted component needs to report, the triggering condition for the vehicle-mounted component to report the log, the log content that the vehicle-mounted component needs to report, or the first information; wherein the first information is used to indicate the hash value of the vehicle-mounted component reporting the log or to indicate the vehicle-mounted component reporting the log.

[0056] Optionally, in combination with the second aspect, the trigger condition includes at least one of the following: the danger level of the operation performed by the vehicle-mounted component is equal to or higher than the preset danger level; the cycle for the vehicle-mounted component to report the log arrives; a log reporting trigger event occurs.

[0057] Optionally, in combination with the second aspect, the log reporting triggering event includes at least one of the following: the vehicle's EDR is triggered, the vehicle's automatic driving is started, the vehicle's automatic driving is turned off, and the user is reminded to take over the driving control of the vehicle when the vehicle is in automatic driving mode, and the vehicle includes on-board components.

[0058] Optionally, in combination with the second aspect, the log content includes at least one of the following: the operation performed by the vehicle-mounted component, the result of the operation performed by the vehicle-mounted component, and the time when the vehicle-mounted component performed the operation.

[0059] Optionally, in combination with the second aspect, the vehicle-mounted component includes a first vehicle-mounted component.

[0060] In a third aspect, a log reporting device is provided, which includes a receiving unit and a sending unit.

[0061] A receiving unit, used to obtain log reporting policy information;

[0062] A sending unit is used to report first log-related information of a first vehicle-mounted component to at least one first server according to log reporting policy information, and to report second log-related information of the first vehicle-mounted component to at least one second server. The at least one first server is one or more of an original equipment manufacturer OEM server, a supplier server, or a regulatory agency server. The at least one second server is one or more of an original equipment manufacturer OEM server, a supplier server, or a regulatory agency server. The first server is different from the second server.

[0063] Optionally, in combination with the third aspect, the first log association information includes at least one of the first log and a hash value of the first log; and the second log association information includes at least one of the first log and a hash value of the first log.

[0064] Optionally, in combination with the third aspect, the sending unit is specifically used to report first log-related information to at least one first server through a first security channel or a second vehicle-mounted component according to the log reporting policy information, and report second log-related information to at least one second server through a second security channel or a third vehicle-mounted component. The first security channel is a channel between the first vehicle-mounted component and each server in the at least one first server, the second security channel is a channel between the first vehicle-mounted component and each server in the at least one second server, a security channel is established between the second vehicle-mounted component and each server in the at least one first server, and a security channel is established between the third vehicle-mounted component and each server in the at least one second server.

[0065] Optionally, in combination with the third aspect, the log reporting policy information includes at least one of the following: the identifier of the vehicle-mounted component that needs to report the log, the destination address of the vehicle-mounted component for reporting the log, the type of log that the vehicle-mounted component needs to report, the triggering condition for the vehicle-mounted component to report the log, the log content that the vehicle-mounted component needs to report, or the first information; wherein the first information is used to indicate the hash value of the log reported by the vehicle-mounted component or to indicate that the vehicle-mounted component reports the log.

[0066] Optionally, in combination with the third aspect, the trigger condition includes at least one of the following: the danger level of the operation performed by the vehicle-mounted component is equal to or higher than the preset danger level; the period for the vehicle-mounted component to report the log arrives; a log reporting trigger event occurs.

[0067] Optionally, in combination with the third aspect, the log reporting triggering event includes at least one of the following: the vehicle EDR is triggered, the vehicle's automatic driving is started, the vehicle's automatic driving is turned off, and the user is reminded to take over the driving control of the vehicle when the vehicle is in automatic driving mode, and the vehicle includes on-board components.

[0068] Optionally, in combination with the third aspect, the log content includes at least one of the following: the operation performed by the vehicle-mounted component, the result of the operation performed by the vehicle-mounted component, and the time when the vehicle-mounted component performed the operation.

[0069] Optionally, in combination with the third aspect, the vehicle-mounted component includes a first vehicle-mounted component.

[0070] Optionally, in combination with the third aspect, the device also includes a processing unit, which is used to generate a first log or a hash value of the first log; or, a sending unit, which is used to send second information to one or more of the second vehicle-mounted component and the third vehicle-mounted component, and the second information is used to generate a hash value of the first log.

[0071] Optionally, in combination with the third aspect, at least one first server and at least one second server correspond to nodes of the blockchain network.

[0072] In a fourth aspect, a log reporting device is provided, which is deployed in a vehicle and includes a receiving unit and a sending unit.

[0073] A receiving unit, used to obtain log reporting policy information;

[0074] A sending unit is used to report first log-related information of a first vehicle-mounted component to at least one first server according to log reporting policy information, and to report second log-related information of the first vehicle-mounted component to at least one second server. The at least one first server is one or more of an original equipment manufacturer OEM server, a supplier server, or a regulatory agency server. The at least one second server is one or more of an original equipment manufacturer OEM server, a supplier server, or a regulatory agency server. The first server is different from the second server.

[0075] Optionally, in combination with the fourth aspect, the first log association information includes at least one of the first log and a hash value of the first log; and the second log association information includes at least one of the first log and a hash value of the first log.

[0076] Optionally, in combination with the fourth aspect, the sending unit is specifically used to report first log-related information to at least one first server through a first security channel or a second vehicle-mounted component according to the log reporting policy information, and report second log-related information to at least one second server through a second security channel or a third vehicle-mounted component. The first security channel is a channel between the first vehicle-mounted component and each server in the at least one first server, the second security channel is a channel between the first vehicle-mounted component and each server in the at least one second server, a security channel is established between the second vehicle-mounted component and each server in the at least one first server, and a security channel is established between the third vehicle-mounted component and each server in the at least one second server.

[0077] Optionally, in combination with the fourth aspect, the log reporting policy information includes at least one of the following: the identification of the vehicle-mounted component that needs to report the log, the destination address of the vehicle-mounted component for reporting the log, the type of log that the vehicle-mounted component needs to report, the triggering condition for the vehicle-mounted component to report the log, the log content that the vehicle-mounted component needs to report, or the first information; wherein the first information is used to indicate the hash value of the log reported by the vehicle-mounted component or to indicate that the vehicle-mounted component reports the log.

[0078] Optionally, in combination with the fourth aspect, the trigger condition includes at least one of the following: the danger level of the operation performed by the vehicle-mounted component is equal to or higher than the preset danger level; the cycle for the vehicle-mounted component to report the log arrives; a log reporting trigger event occurs.

[0079] Optionally, in combination with the fourth aspect, the log reporting triggering event includes at least one of the following: the vehicle EDR is triggered, the vehicle's automatic driving is started, the vehicle's automatic driving is turned off, and the user is reminded to take over the driving control of the vehicle when the vehicle is in automatic driving mode, and the vehicle includes on-board components.

[0080] Optionally, in combination with the fourth aspect, the log content includes at least one of the following: the operation performed by the vehicle-mounted component, the result of the operation performed by the vehicle-mounted component, and the time when the vehicle-mounted component performed the operation.

[0081] Optionally, in combination with the fourth aspect, the vehicle-mounted component includes a first vehicle-mounted component.

[0082] Optionally, in combination with the fourth aspect, the device also includes a processing unit, which is used to generate a first log or a hash value of the first log; or, a sending unit, which is used to send second information to one or more of the second vehicle-mounted component and the third vehicle-mounted component, and the second information is used to generate a hash value of the first log.

[0083] Optionally, in combination with the fourth aspect, at least one first server and at least one second server correspond to nodes of the blockchain network.

[0084] In a fifth aspect, a log reporting device is provided, the device comprising a processing unit and a sending unit.

[0085] A processing unit, configured to generate log reporting policy information;

[0086] The sending unit is used to send log reporting policy information.

[0087] Optionally, in combination with the fifth aspect, the log reporting policy information includes at least one of the following: the identification of the vehicle-mounted component that needs to report the log, the destination address of the vehicle-mounted component reporting the log, the type of log that the vehicle-mounted component needs to report, the triggering condition for the vehicle-mounted component to report the log, the log content that the vehicle-mounted component needs to report, or the first information; wherein, the first information is used to indicate the hash value of the vehicle-mounted component reporting the log or to indicate the vehicle-mounted component reporting the log.

[0088] Optionally, in combination with the fifth aspect, the trigger condition includes at least one of the following: the danger level of the operation performed by the vehicle-mounted component is equal to or higher than the preset danger level; the cycle for the vehicle-mounted component to report the log arrives; a log reporting trigger event occurs.

[0089] Optionally, in combination with the fifth aspect, the log reporting triggering event includes at least one of the following: the vehicle's EDR is triggered, the vehicle's automatic driving is started, the vehicle's automatic driving is turned off, and the user is reminded to take over the driving control of the vehicle when the vehicle is in automatic driving mode, and the vehicle includes on-board components.

[0090] Optionally, in combination with the fifth aspect, the log content includes at least one of the following: the operation performed by the vehicle-mounted component, the result of the operation performed by the vehicle-mounted component, and the time when the operation was performed by the vehicle-mounted component.

[0091] Optionally, in combination with the fifth aspect, the vehicle-mounted component includes a first vehicle-mounted component.

[0092] In a sixth aspect, a log reporting device is provided, the device comprising at least one processor and a communication interface, wherein the at least one processor is configured to call a computer program stored in at least one memory to perform the following operations:

[0093] Obtain log reporting policy information through the communication interface;

[0094] Through the communication interface, the first log-related information of the first vehicle-mounted component is reported to at least one first server according to the log reporting strategy information, and the second log-related information of the first vehicle-mounted component is reported to at least one second server. The at least one first server is one or more of the original equipment manufacturer OEM server, supplier server or regulatory agency server, and the at least one second server is one or more of the original equipment manufacturer OEM server, supplier server or regulatory agency server. The first server is different from the second server.

[0095] The communication interface is used to send and / or receive data.

[0096] Optionally, in combination with the sixth aspect, the first log association information includes at least one of the first log and a hash value of the first log; and the second log association information includes at least one of the first log and a hash value of the first log.

[0097] Optionally, in combination with the sixth aspect, at least one processor is specifically used to perform the following operations: according to the log reporting policy information, report the first log association information to the at least one first server through the first security channel or the second vehicle-mounted component, and report the second log association information to the at least one second server through the second security channel or the third vehicle-mounted component, the first security channel is the channel between the first vehicle-mounted component and each server of the at least one first server, the second security channel is the channel between the first vehicle-mounted component and each server of the at least one second server, a security channel is established between the second vehicle-mounted component and each server of the at least one first server, and a security channel is established between the third vehicle-mounted component and each server of the at least one second server.

[0098] Optionally, in combination with the sixth aspect, the log reporting policy information includes at least one of the following: the identifier of the vehicle-mounted component that needs to report the log, the destination address of the vehicle-mounted component for reporting the log, the type of log that the vehicle-mounted component needs to report, the triggering condition for the vehicle-mounted component to report the log, the log content that the vehicle-mounted component needs to report, or the first information; wherein the first information is used to indicate the hash value of the log reported by the vehicle-mounted component or to indicate that the vehicle-mounted component reports the log.

[0099] Optionally, in combination with the sixth aspect, the trigger condition includes at least one of the following: the danger level of the operation performed by the vehicle-mounted component is equal to or higher than the preset danger level; the period for the vehicle-mounted component to report the log arrives; a log reporting trigger event occurs.

[0100] Optionally, in combination with the sixth aspect, the log reporting triggering event includes at least one of the following: the vehicle EDR is triggered, the vehicle's automatic driving is started, the vehicle's automatic driving is turned off, and the user is reminded to take over the driving control of the vehicle when the vehicle is in automatic driving mode, and the vehicle includes on-board components.

[0101] Optionally, in combination with the sixth aspect, the log content includes at least one of the following: the operation performed by the vehicle-mounted component, the result of the operation performed by the vehicle-mounted component, and the time when the vehicle-mounted component performed the operation.

[0102] Optionally, in combination with the sixth aspect, the vehicle-mounted component includes a first vehicle-mounted component.

[0103] Optionally, in combination with the sixth aspect, at least one processor is further used to perform the following operations: generate a first log or a hash value of the first log; or, send second information to one or more of the second vehicle-mounted component and the third vehicle-mounted component through the communication interface, the second information being used to generate a hash value of the first log.

[0104] Optionally, in combination with the sixth aspect, at least one first server and at least one second server correspond to nodes of the blockchain network.

[0105] In a seventh aspect, a log reporting device is provided, the device including at least one processor and a communication interface, wherein the at least one processor is configured to call a computer program stored in at least one memory to perform the following operations:

[0106] Generate log reporting policy information;

[0107] Send log reporting policy information through the communication interface.

[0108] Optionally, in combination with the seventh aspect, the log reporting policy information includes at least one of the following: the identification of the vehicle-mounted component that needs to report the log, the destination address of the vehicle-mounted component reporting the log, the type of log that the vehicle-mounted component needs to report, the triggering condition for the vehicle-mounted component to report the log, the log content that the vehicle-mounted component needs to report, or the first information; wherein the first information is used to indicate the hash value of the vehicle-mounted component reporting the log or to indicate the vehicle-mounted component reporting the log.

[0109] Optionally, in combination with the seventh aspect, the trigger condition includes at least one of the following: the danger level of the operation performed by the vehicle-mounted component is equal to or higher than the preset danger level; the cycle for the vehicle-mounted component to report the log arrives; a log reporting trigger event occurs.

[0110] Optionally, in combination with the seventh aspect, the log reporting triggering event includes at least one of the following: the vehicle's EDR is triggered, the vehicle's automatic driving is started, the vehicle's automatic driving is turned off, and the user is reminded to take over the driving control of the vehicle when the vehicle is in automatic driving mode, and the vehicle includes on-board components.

[0111] Optionally, in combination with the seventh aspect, the log content includes at least one of the following: the operation performed by the vehicle-mounted component, the result of the operation performed by the vehicle-mounted component, and the time when the operation was performed by the vehicle-mounted component.

[0112] Optionally, in combination with the seventh aspect, the vehicle-mounted component includes a first vehicle-mounted component.

[0113] In the eighth aspect, a log reporting system is provided, comprising a first vehicle-mounted component and an over the air (OTA) server, wherein the first vehicle-mounted component is used to implement the method as described in any one of the first aspects, and the OTA server is used to implement the method as described in any one of the second aspects.

[0114] In the ninth aspect, a log reporting system is provided, including a vehicle and an OTA server, the vehicle including a first vehicle-mounted component, the first vehicle-mounted component is used to implement the method as described in any one of the first aspects, and the OTA server is used to implement the method as described in any one of the second aspects.

[0115] In a tenth aspect, a terminal is provided, which may be a smart cockpit product, a vehicle, etc., and is used to implement the method as described in any one of the first aspects.

[0116] Alternatively, the above-mentioned vehicles can also be replaced by intelligent terminals or intelligent transportation tools such as drones and robots.

[0117] In the eleventh aspect, a chip system is provided, which includes at least one processor, a memory and an interface circuit, wherein the interface circuit is used to provide information input / output for the at least one processor, and the memory stores a computer program. When the computer program runs on one or more processors, the method described in any one of the first to second aspects is implemented.

[0118] In the twelfth aspect, a computer-readable storage medium is provided, in which a computer program is stored. When the computer program runs on one or more processors, the method as described in any one of the first to second aspects is implemented.

[0119] In a thirteenth aspect, a computer program product is provided, which, when running on one or more processors, implements the method as described in any one of the first to second aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0120] The following is a brief introduction to the drawings required for describing the embodiments or prior art.

[0121] FIG1 shows a block format according to an embodiment of the present application;

[0122] FIG2 is a schematic diagram of a log reporting system provided in an embodiment of the present application;

[0123] FIG3 is a schematic diagram of a possible vehicle architecture provided by an embodiment of the present application;

[0124] FIG4 is a schematic diagram of the architecture of a vehicle based on a central computing architecture provided in an embodiment of the present application;

[0125] FIG5 is a flow chart of a log reporting method provided in an embodiment of the present application;

[0126] FIG6 is a schematic diagram of a node of a blockchain network provided in an embodiment of the present application;

[0127] FIG7 is a schematic diagram of a node of another blockchain network provided in an embodiment of the present application;

[0128] FIG8 is a schematic diagram of a node of another blockchain network provided in an embodiment of the present application;

[0129] FIG9 is a flow chart of a log reporting system and a log reporting method provided in an embodiment of the present application;

[0130] FIG10 is a schematic structural diagram of a log reporting device 100 provided in an embodiment of the present application;

[0131] FIG11 is a schematic structural diagram of a vehicle 110 provided in an embodiment of the present application;

[0132] FIG12 is a structural diagram of a log reporting device 120 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0133] The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings in the embodiments of the present application. In the embodiments of the present application, the terms "system" and "network" can be used interchangeably. Unless otherwise specified, " / " indicates that the objects associated before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in this application is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. A and B can be singular or plural. In addition, in the description of this application, unless otherwise specified, "multiple" refers to two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be one or more. In addition, to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that the words "first" and "second" do not limit the quantity or execution order, and the words "first" and "second" do not necessarily mean different.

[0134] The reference to "one embodiment" or "some embodiments" etc. described in the embodiments of the present application means that one or more embodiments of the present application include the specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the sentences "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments" etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways. The following specific embodiments further explain the purpose, technical solutions and beneficial effects of the present application in detail. It should be understood that the following are only specific embodiments of the present application and are not intended to limit the scope of protection of the present application. Any modifications, equivalent replacements, improvements, etc. made on the basis of the technical solutions of the present application should be included in the scope of protection of the present application.

[0135] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0136] The following is an explanation of some of the terms involved in this application. It is understood that when the following terms are involved elsewhere in this application, they will not be explained later.

[0137] 1. Vehicle components

[0138] The vehicle-mounted component mentioned in the embodiment of the present application may be at least one component in the vehicle. The vehicle-mounted component may generate log-related information. The vehicle-mounted component may communicate with a server, such as one or more of an OEM server, a supplier server, a regulatory agency server, an OTA server, and the like. Optionally, the vehicle-mounted component may be a separate component in the vehicle, or it may be deployed as a module within the component. Furthermore, the vehicle-mounted component may be a hardware module or a computer program. For example, a module may be included in the vehicle's T-box, and the module may generate log-related information, so the Tbox may be considered a vehicle-mounted component. For another example, a component may be pre-assembled in the vehicle, and the component may have a processor or an integrated circuit integrated therein, and the component may generate log-related information, so the component may be considered a vehicle-mounted component.

[0139] For example, the in-vehicle component can be one or more of the vehicle's MDC, HMI modules or components, GW, Tbox, ECU, VIU, and DC, or a vehicle's media device, such as a camera or radar. The ECU is composed of one or more of a processor, memory, input / output (I / O) interface, analog-to-digital converter (A / D), and large-scale integrated circuits such as shaping and driving, and can perform a variety of functions.

[0140] The log-related information involved in the embodiment of the present application may include at least one of a log and a hash value of the log. The log involved in the embodiment of the present application may include at least one of the following: the time when the vehicle-mounted component performs an operation, the log type, the operation performed by the vehicle-mounted component, and the result of the operation performed by the vehicle-mounted component.

[0141] In embodiments of the present application, the operations performed by an in-vehicle component can be used to implement one or more of thermal management, seat management, door and window management, audio and video entertainment, autonomous driving, body control, in-vehicle and out-of-vehicle communication, and upgrade functions. The time at which the in-vehicle component performs an operation may include local time and a time offset from Universal Time Coordinated (UTC). Optionally, the time at which the in-vehicle component performs an operation may also include daylight saving time. Exemplarily, the time at which the in-vehicle component performs an operation is: 2022-06-21 15:02:01.012+05:30. Log types may include operation logs or security logs. Operation logs are used to record user operation information, such as one or more of user account query records, in-vehicle navigation records, and in-vehicle music playback records. Security logs are used to record security access information, such as one or more of user login authentication information, network attack information, and access control information. The results of the in-vehicle component's operations may include success or failure.

[0142] In addition, the log involved in the embodiment of the present application may also include at least one of the following: the danger level of the operation performed by the vehicle-mounted component, the name (or identification) of the operator who controls the vehicle-mounted component to perform the operation, the domain to which the vehicle-mounted component belongs, the terminal or access interface used when the vehicle-mounted component performs the operation, and additional information.

[0143] In an embodiment of the present application, the danger level of the operation performed by the on-board component can be determined based on the impact of the operation on the business of the on-board component. For example, if the operation has a great impact on the business, the danger level is high risk (risk); if the operation has an impact on the business but is controllable, the danger level is normal (normal); if the operation has no impact on the business, the danger level is none (none). Generally speaking, the danger level of the security log is normal or high risk. Among them, in one possible implementation, the business of the on-board component can be divided into: business with high latency requirements, i.e., low latency business, business with medium latency requirements, and business with low latency requirements. In another possible implementation, the business of the on-board component can be divided into: business with high reliability requirements, business with medium reliability requirements, and business with low reliability requirements. The domain to which the on-board component belongs can be one or more of the autonomous driving function domain, smart cockpit, etc. Additional information is a supplement to the result of the operation performed by the on-board component, such as an error code. When there is no supplement, the log involved in the embodiment of the present application may not include additional information.

[0144] When the on-board component is a separate component in the vehicle, the log involved in the embodiment of the present application may also include the service name or module name that creates the log in the on-board component. If the on-board component is a module or component for implementing HMI, the service name that creates the log in the on-board component may be an audio service. When the on-board component is a hardware module or a computer program, the log may also include the name of the subsystem or system where the on-board component is located. For example, the name of the subsystem or system where the on-board component is located may be an automatic driving system (ADS), a cockpit domain controller (CDC), a Tbox, a VCU or a GW, etc.

[0145] The hash value of the log involved in the embodiment of the present application is obtained by performing a hash calculation on the log. Exemplarily, a hash function is used to perform a hash calculation on the log to obtain the hash value of the log. Optionally, the hash function involved in the embodiment of the present application may include, for example, a secure hash algorithm (SHA) 256. 2 , SHA256, SHA512, etc.

[0146] 2. Blockchain

[0147] A blockchain is a chained data structure in which blocks are linked in chronological order. Furthermore, blockchains use cryptography to ensure immutability and non-forgeability. In this application, a block is the smallest unit in a blockchain used to store logs or log hashes. A block consists of a header and a body.

[0148] The block header is mainly used to record one or more characteristic information of the current block. For example, the block header may include at least one characteristic information such as the version number, necessary information to form a chain structure with the previous block of the current block (such as the hash value (Prev_Hash) of the previous block of the current block), timestamp, and random number (nonce).

[0149] To determine the hash value of the current block, the various characteristic information in the block header of the current block can be concatenated in a predetermined order to form a string. This string is then hashed using a hash function to obtain a hash value, which serves as the hash value of the current block. Because the characteristic information included in the block headers of different blocks typically has different values, each block can be uniquely associated with a hash value. Because each block can be uniquely associated with a hash value, and each block header can include the hash value of the previous block (or previous block), multiple blocks can form a blockchain. The timestamp can be used to indicate the time the current block was generated.

[0150] The block body can be used to store logs or log hash values. It should be understood that in one possible implementation, the block bodies of different blocks in the blockchain can both store logs; or, the block bodies of different blocks in the blockchain can both store log hash values; or, the block body of one block in the blockchain can store logs, while the block body of another block in the blockchain can store log hash values.

[0151] For example, see Figure 1, which provides a block format according to an embodiment of the present application. As shown in Figure 1, any block includes a block header and a block body.

[0152] The block header includes a version number, a hash value of the previous block, a timestamp, and a random number. For example, the block header of block N+1 may include the hash value of block N.

[0153] The block body can include a log or a hash value of a log. Specifically, in Figure 1-1, the block bodies of block N and block N+1 both include a log; in Figure 1-2, the block bodies of block N and block N+1 both include a hash value of a log; and in Figure 1-3, the block header of block N includes a hash value of a log, and the block header of block N+1 includes a log.

[0154] A blockchain network typically consists of multiple nodes, which communicate with each other via wired or wireless means. In a blockchain network, any node or accounting node can generate a new block based on the logs or log hashes reported by on-board components and broadcast it to other nodes. Other nodes then verify the block. Once all nodes in the blockchain network reach consensus, the new block is added to the blockchain. Accounting nodes are nodes in the blockchain network that have competitively obtained the right to record data. This means that once a accounting node obtains this right, it can store the logs or log hashes reported by on-board components in the blockchain.

[0155] The following describes the system architecture and business scenarios of the embodiments of the present application. It should be noted that the system architecture and business scenarios described in this application are intended to more clearly illustrate the technical solutions of this application and do not constitute a limitation on the technical solutions provided by this application. It is known to those skilled in the art that with the evolution of the system architecture and the emergence of new business scenarios, the technical solutions provided by this application are equally applicable to similar technical problems.

[0156] See Figure 2, which is a schematic diagram of a log reporting system provided by an embodiment of the present application. The log reporting system may include a first vehicle-mounted component, an OEM server, a supplier server, and a regulatory agency server. In addition, the log reporting system may also include an OTA server. Specifically:

[0157] The first vehicle-mounted component is an electronic device with data processing capability or data receiving and sending capability, which can receive log reporting policy information sent by the OTA server to send log-related information to one or more of the OEM server, supplier server and regulatory agency server according to the log reporting policy information.

[0158] The OEM server, supplier server, and regulatory agency server are used to receive log-related information. The number of OEM servers can be one or more, the number of supplier servers can be one or more, and the number of regulatory agency servers can be one or more, without limitation. In some specific implementation scenarios, the OEM server, supplier server, and regulatory agency server can also be referred to as the OEM cloud (or vehicle cloud), supplier cloud, and regulatory agency cloud, respectively.

[0159] The OTA server is used to generate and send log reporting policy information. Optionally, the OTA server can be the same server as the OEM server or a different server, which is not limited here. In some specific implementation scenarios, the OTA server can be referred to as the OTA cloud.

[0160] The server mentioned in each embodiment of the present application can be a server or a server cluster composed of multiple servers. In one possible implementation, the OEM server, supplier server or regulatory agency server can be a server that contains a centralized storage of logs or hash values ​​of logs, or a distributed server cluster that contains distributed storage of logs or hash values ​​of logs. For example, a distributed server can be a server cluster composed of multiple servers, and the server cluster can include servers of the same type or different types of servers. Exemplarily, server cluster #1 includes OEM server #A1 and OEM server #A2; server cluster #2 includes supplier server #B1 and supplier server #B2; server cluster #3 includes regulatory agency server #C1 and regulatory agency server #C2. Another example is that server cluster #1 includes OEM server #A1 and supplier server #B1, and server cluster #2 includes OEM server #A2, supplier server #B2 and regulatory agency server #C1. In another possible implementation, the OTA server can be a server that centrally stores log reporting policy information, or it can include a distributed server cluster that distributes log reporting policy information. For example, a distributed server can be a server cluster composed of multiple servers. The server cluster may include OTA servers, cloud computing servers, content delivery network (CDN) servers, network time protocol (NTP), domain name system (DNS) servers, etc., among which the servers can coordinate with each other to jointly complete computing, data storage, communication and other functions.

[0161] For the convenience of description, in the embodiments of the present application, a single server, a distributed server, and a server cluster are collectively referred to as a server.

[0162] Referring to Figure 3, Figure 3 is a schematic diagram of the architecture of a possible vehicle provided in an embodiment of the present application, including a cloud 301 and a vehicle 302. The cloud 301 may include, for example, an OEM cloud, a supplier cloud, a regulatory agency cloud, and an OTA cloud. Vehicle 302 is a vehicle based on the vehicle electrical / electronic architecture (E / E) architecture. Referring to area 303, vehicle 302 may include the following components: a mobile data center (MDC), a human-machine interaction (HMI), a gateway (GW), a telematics box (Tbox or TCU), an electronic control unit (ECU), and other modules. Among them, GW is a core component in the entire vehicle's electrical and electronic architecture. As the data interaction hub of the entire vehicle network, it can route network data such as the controller area network (CAN), the local interconnect network (LIN), the multimedia data transmission (MOST), and the FlexRay in different networks. MDC is the vehicle's intelligent onboard computing platform. The T-BOX is primarily used to communicate with the vehicle's external systems, backend systems, and mobile applications (APPs). The HMI is the vehicle's infotainment system. The ECU is a dedicated microcomputer controller for the vehicle.

[0163] Referring to Figure 4, Figure 4 is a schematic diagram of the architecture of a vehicle based on a central computing architecture provided by an embodiment of the present application. Vehicle 40 is a vehicle based on a central computing architecture (CCA). The CCA includes several vehicle integrated / integration units (VIUs) and multiple automotive components. Multiple VIUs form a ring network to achieve high bandwidth (high-definition cameras, high-definition displays), low latency, and high-reliability processing capabilities to continuously improve competitiveness, simplify vehicle network configuration, and improve upgrade and maintenance efficiency. Automotive components (such as ECUs, Tboxes, etc.) can be connected to the VIU, or can be connected to a domain controller (DC), such as a cockpit domain controller (CDC), an MDC, or a vehicle domain controller (VDC), and then connected to the VIU via the DC. In this way, it avoids the need for each component of the vehicle to be connected to the DC through its own wiring harness in the traditional system for realizing electronic control functions in the vehicle, which is conducive to reducing the length of the wiring harness in the system for realizing electronic control functions in the vehicle.

[0164] As shown in FIG4 , compared with the automotive electrical / electronic architecture (E / E) used by vehicle 302 in FIG3 , among the multiple components of vehicle 40 , some components are connected to VIU1 (such as ECU2.1, ECU2.2, Tbox, etc.), some components are connected to VIU2 (such as ECU4.1, ECU4.2, etc.), some components are connected to VIU3, and some components are connected to VIU4.

[0165] It should be noted that, in the architecture shown in FIG4 , the connection lines in each node may be a bus based on Ethernet, or one or more of a CAN bus, a LIN bus, a MOST bus, a FlexRay bus, and the like.

[0166] 5 , which is a flow chart of a log reporting method provided in an embodiment of the present application, including but not limited to the following steps:

[0167] 501. The OTA server generates log reporting policy information.

[0168] Optionally, the log reporting policy information may include at least one of the following: the identifier of the vehicle-mounted component that needs to report the log, the destination address for the vehicle-mounted component to report the log, the type of log that the vehicle-mounted component needs to report, the triggering condition for the vehicle-mounted component to report the log, the log content that the vehicle-mounted component needs to report, or the first information; the first information is used to indicate the hash value of the vehicle-mounted component reporting the log or to indicate that the vehicle-mounted component reports the log. Among them, the identifier of the vehicle-mounted component that needs to report the log can also be understood as the identifier of the vehicle-mounted component that needs to report the hash value of the log. Similarly, the destination address for the vehicle-mounted component to report the log can also be understood as the destination address of the hash value of the vehicle-mounted component reporting the log, and the triggering condition for the vehicle-mounted component to report the log can also be understood as the triggering condition of the hash value of the vehicle-mounted component reporting the log.

[0169] Optionally, the vehicle-mounted component that needs to report the log may include the first vehicle-mounted component. Therefore, the first vehicle-mounted component may report the first log of the first vehicle-mounted component or the hash value of the first log according to the log reporting policy information.

[0170] Optionally, the destination address for the log report of the vehicle-mounted component may include at least one of the IP addresses, MAC addresses, etc. of multiple servers. For example, the destination address for the log report of the first vehicle-mounted component may include the IP addresses of at least one first server and at least one second server. Therefore, the first vehicle-mounted component may report the first log-related information of the first vehicle-mounted component to at least one first server based on the IP address of at least one first server, and may also report the second log-related information of the first vehicle-mounted component to at least one second server based on the IP address of at least one second server. In addition, the destination address for the log report of the first vehicle-mounted component may also include the IP address of at least one third server. Therefore, the first vehicle-mounted component may report the third log-related information of the first vehicle-mounted component to at least one third server based on the IP address of at least one third server.

[0171] It should be understood that one server may correspond to one IP address and one MAC address, and the MAC address may be obtained through the IP address, and vice versa.

[0172] In which, at least one first server can be one or more of an OEM server, a supplier server, or a regulatory agency server, at least one second server can be one or more of an OEM server, a supplier server, or a regulatory agency server, at least one third server can be one or more of an OEM server, a supplier server, or a regulatory agency server, and the first server, second server, and third server are different. Exemplarily, first server #1 is OEM server #A1, second server #1 is supplier server #B1, and third server #1 is regulatory agency server #C1. Another exemplary embodiment, first server #1 is OEM server #A1, first server #2 is supplier server #B1; second server #1 is supplier server #B2, second server #2 is regulatory agency server #C1; and third server #1 is OEM server #A2.

[0173] Optionally, the types of logs that the vehicle-mounted component needs to report may include operation logs or security logs. Operation logs are used to record user operation information, such as one or more of user account query records, vehicle navigation records, and vehicle music playback records. Security logs are used to record security access information, such as one or more of user login authentication information, network attack information, and access control information.

[0174] Optionally, the triggering conditions for the vehicle-mounted component to report a log may include at least one of the following: the danger level of the operation performed by the vehicle-mounted component is equal to or greater than a preset danger level; the vehicle-mounted component's log reporting period has expired; or a log reporting triggering event has occurred. The preset danger level may be a predefined, preconfigured, or protocol-specified value, such as high, normal, or none, and is not limited here. The vehicle-mounted component's log reporting period can be understood as the period of the log's hash value. The log reporting triggering event may include at least one of the following: the vehicle's EDR being triggered; the vehicle's autonomous driving being activated; the vehicle's autonomous driving being deactivated; or a reminder to the user to take over driving control when the vehicle is in autonomous driving mode, where the vehicle includes the vehicle-mounted component. The EDR can be integrated into the vehicle's airbag control unit's software module to enable the vehicle's black box to generate logs. Generally, the EDR is triggered when the vehicle is involved in a collision or experiences a dramatic change in speed. EDR triggering can be understood as the EDR starting to record a log.

[0175] Optionally, the log content that the vehicle-mounted component needs to report can be found in Table 1. Specifically, the log content may include at least one of the following: the operation performed by the vehicle-mounted component, the result of the operation performed by the vehicle-mounted component, and the time when the vehicle-mounted component performed the operation. The log content may also include at least one of the following: the danger level of the operation performed by the vehicle-mounted component, the name (or identifier) ​​of the operator who controls the vehicle-mounted component to perform the operation, the domain to which the vehicle-mounted component belongs, the terminal or access interface used when the vehicle-mounted component performs the operation, and additional information. In addition, when the vehicle-mounted component is a separate component in the vehicle, the log content may also include the service name or module name that creates the log in the vehicle-mounted component. When the vehicle-mounted component is a hardware module or a computer program, the log content may also include the name of the subsystem or system where the vehicle-mounted component is located.

[0176] Table 1

[0177]

[0178]

[0179] As can be seen, the above technical solution provides specific content for log reporting policy information, enabling on-board components to better meet requirements when reporting logs or log hash values. Furthermore, on-board components can better report logs or log hash values ​​based on trigger conditions, avoiding the issue of poor system performance caused by real-time reporting of logs or log hash values.

[0180] Optionally, after the OTA server generates the log reporting policy information, the log reporting method may further include: the OTA server assigns a download address, the download address is used to download the upgrade package corresponding to the log reporting policy information; the OTA server sends the download address to the first vehicle-mounted component. Accordingly, the first vehicle-mounted component receives the download address sent by the OTA server. The download address may be, for example, a uniform resource locator (URL). That is, the URL can be used to download the upgrade package corresponding to the log reporting policy information. Optionally, the log reporting policy information may be included in the upgrade package, and the upgrade package may further include version information of the upgrade package, and the version information of the upgrade package is used to indicate the version number of the log reporting policy information, which can also be understood as: the version number included in the log reporting policy information.

[0181] The OTA server sending the download address to the first vehicle-mounted component may include: the OTA server sending the download address to the first vehicle-mounted component through the second vehicle-mounted component. Correspondingly, the first vehicle-mounted component receives the download address sent by the OTA server through the second vehicle-mounted component. The first vehicle-mounted component and the second vehicle-mounted component are different. In one possible embodiment, when the first vehicle-mounted component is not a Tbox, the second vehicle-mounted component may be a Tbox, or one or more of an MDC, HMI, GW, ECU, VIU, and DC, or a media device in the vehicle, such as a camera, radar, etc. In another possible embodiment, when the first vehicle-mounted component is a Tbox, the second vehicle-mounted component may be one or more of an MDC, HMI, GW, ECU, VIU, and DC, or a media device in the vehicle, such as a camera, radar, etc.

[0182] It should be noted that when there are multiple on-board components that need to report logs, the log reporting policy information corresponding to different on-board components can be included in the same upgrade package or in different upgrade packages. Of course, the download addresses of different upgrade packages can be the same or different, which is not limited here.

[0183] It can be seen that in the above technical solution, by sending the download address to the vehicle-mounted component, the vehicle-mounted component can obtain the upgrade package corresponding to the daily reporting strategy information.

[0184] The log reporting method may further include step 502, which is as follows:

[0185] 502. The OTA server sends the log reporting policy information. Correspondingly, the first vehicle-mounted component obtains the log reporting policy information.

[0186] It should be noted that the first vehicle-mounted component can use the above download address to download the upgrade package corresponding to the log reporting policy information and thereby obtain the log reporting policy information, or it can directly receive the log reporting policy information from the OTA server. The specific method may depend on the implementation of the first vehicle-mounted component, pre-agreed agreement, or standard definition.

[0187] The OTA server sends log reporting policy information in at least two ways:

[0188] Method 1.1, the OTA server sends log reporting policy information to the first vehicle-mounted component. Correspondingly, the first vehicle-mounted component receives the log reporting policy information sent by the OTA server. Exemplarily, the OTA server sends the log reporting policy information to the first vehicle-mounted component through a secure channel between the OTA server and the first vehicle-mounted component. Of course, the first vehicle-mounted component can receive the log reporting policy information sent by the OTA server through the secure channel. In an embodiment of the present application, the secure channel can be an IPsec secure channel, a TLS secure channel, a DTLS secure channel, or an HTTPS secure channel. As another example, the OTA server directly sends the log reporting policy information to the first vehicle-mounted component through a communication link without establishing a secure channel to transmit the log reporting policy information. The specific implementation may depend on the implementation of the first vehicle-mounted component, a prior agreement, or the definition of the standard.

[0189] Method 1.2: The OTA server sends the log reporting policy information to the first vehicle-mounted component via the second vehicle-mounted component. Correspondingly, the first vehicle-mounted component receives the log reporting policy information sent by the OTA server via the second vehicle-mounted component.

[0190] In one possible implementation, the second vehicle-mounted component may establish a secure channel with a server. For example, the second vehicle-mounted component may establish a secure channel with the OTA server, and may also establish a secure channel with each of at least one first server, at least one second server, and at least one third server. Therefore, Method 2.2 can be understood as follows: the OTA server sends log reporting policy information to the first vehicle-mounted component via the secure channel between the second vehicle-mounted component and the OTA server. That is, the OTA server sends the log reporting policy information to the second vehicle-mounted component via the secure channel between the second vehicle-mounted component and the OTA server, and the second vehicle-mounted component sends the log reporting policy information to the first vehicle-mounted component. Correspondingly, the first vehicle-mounted component receives the log reporting policy information sent by the second vehicle-mounted component. In another possible implementation, the OTA server sends the log reporting policy information directly to the second vehicle-mounted component via a communication link, without establishing a secure channel to transmit the log reporting policy information. The specific implementation may depend on the implementation of the second vehicle-mounted component, pre-agreed agreements, or standard definitions. Furthermore, the second vehicle-mounted component sends the log reporting policy information to the first vehicle-mounted component.

[0191] The communication link between the first vehicle-mounted component and other vehicle-mounted components (such as the second vehicle-mounted component) can be various types of media, specifically a wired link, a wireless link, or a combination of a wired link and a wireless link. The wired link can be, for example, an Ethernet-based bus, or one or more of a CAN bus, a LIN bus, a MOST bus, a FlexRay bus, etc. The wireless link can be, for example, a short-range connection technology, including 802.11b / g, Bluetooth, ZigBee, and in-vehicle short-range wireless communication technology. Alternatively, the wireless link can be a long-range connection technology, including the Global System for Mobile Communications (GSM), the General Packet Radio Service (GPRS), the Universal Mobile Telecommunications System (UMTS), communication technology based on Long Term Evolution (LTE), fifth-generation mobile networks or wireless systems (5G or 5G technology), in-vehicle wireless communication technology, and the like. Of course, it is not ruled out that other technologies can be used to support the first vehicle-mounted component to communicate with other vehicle-mounted components (such as the second vehicle-mounted component, etc.).

[0192] It can be seen that the above technical solution enriches the channels for sending log reporting policy information. At the same time, because the log reporting policy information can be sent through a secure channel, the security of the log reporting policy information can be improved.

[0193] 503. The first vehicle-mounted component reports first log-related information of the first vehicle-mounted component to at least one first server according to the log reporting policy information, and reports second log-related information of the first vehicle-mounted component to at least one second server.

[0194] Among them, the first vehicle-mounted component reports the first log-related information of the first vehicle-mounted component to at least one first server according to the log reporting policy information, and reports the second log-related information of the first vehicle-mounted component to at least one second server. It can include: the first vehicle-mounted component reports the first log-related information to at least one first server through the first security channel or the second vehicle-mounted component or the first communication link according to the log reporting policy information, and reports the second log-related information to at least one second server through the second security channel or the third vehicle-mounted component or the second communication link.

[0195] The first secure channel is a channel between the first vehicle-mounted component and each of the at least one first server, and the second secure channel is a channel between the first vehicle-mounted component and each of the at least one second server. It should be understood that the first secure channel and the second secure channel can be of the same type, such as the first secure channel being an IPse secure channel between the first vehicle-mounted component and each of the at least one first server, and the second secure channel being an IPse secure channel between the first vehicle-mounted component and each of the at least one second server. Alternatively, the first secure channel and the second secure channel can be of different types, such as the first secure channel being an IPse secure channel between the first vehicle-mounted component and each of the at least one first server, and the second secure channel being a TLS secure channel between the first vehicle-mounted component and each of the at least one second server.

[0196] A secure channel is established between the second vehicle-mounted component and each of the at least one first server, and a secure channel is established between the third vehicle-mounted component and each of the at least one second server. Optionally, the first vehicle-mounted component is different from the second vehicle-mounted component and the third vehicle-mounted component. The second vehicle-mounted component and the third vehicle-mounted component may be the same or different, without limitation herein.

[0197] For example, when the first vehicle-mounted component is not a Tbox, the second vehicle-mounted component may be a Tbox, and the third vehicle-mounted component may be an MDC. Alternatively, when the first vehicle-mounted component is a Tbox, the second and third vehicle-mounted components may be DCs.

[0198] The first communication link is a link between the first vehicle-mounted component and at least one first server. The second communication link is a link between the first vehicle-mounted component and at least one second server.

[0199] Optionally, the first vehicle-mounted component may further report the third log-related information of the first vehicle-mounted component to at least one third server based on the log reporting policy information. Specifically, the first vehicle-mounted component reports the third log-related information of the first vehicle-mounted component to at least one third server through a third secure channel, a fourth vehicle-mounted component, or a third communication link based on the log reporting policy information.

[0200] The third security channel is a channel between the first vehicle-mounted component and each of the at least one third server.

[0201] In one possible implementation, the first secure channel, the second secure channel, and the third secure channel may be of partially the same type. For example, the first secure channel is an IPse secure channel between the first vehicle-mounted component and each of the at least one first server, the second secure channel is an IPse secure channel between the first vehicle-mounted component and each of the at least one second server, and the third secure channel is a TLS secure channel between the first vehicle-mounted component and each of the at least one third server.

[0202] In another possible implementation, the types of the first secure channel, the second secure channel, and the third secure channel may be completely different. For example, the first secure channel may be an IPse secure channel between the first vehicle-mounted component and each of the at least one first server, the second secure channel may be a TLS secure channel between the first vehicle-mounted component and each of the at least one second server, and the third secure channel may be a DTLS secure channel between the first vehicle-mounted component and each of the at least one third server.

[0203] In another possible implementation, the types of the first secure channel, the second secure channel, and the third secure channel may be identical. For example, the first secure channel may be a DTLS secure channel between the first vehicle-mounted component and each of the at least one first server, the second secure channel may be a DTLS secure channel between the first vehicle-mounted component and each of the at least one second server, and the third secure channel may be a DTLS secure channel between the first vehicle-mounted component and each of the at least one third server.

[0204] In addition, a secure channel may be established between the fourth vehicle-mounted component and each of the at least one third server. Optionally, the first vehicle-mounted component is different from the fourth vehicle-mounted component. The second vehicle-mounted component, the third vehicle-mounted component, and the fourth vehicle-mounted component may be partially identical, completely identical, or completely identical, without limitation herein.

[0205] For example, when the first vehicle-mounted component is not a Tbox, the second vehicle-mounted component may be a Tbox, the third vehicle-mounted component may be an MDC, and the fourth vehicle-mounted component may be a DC. Alternatively, when the first vehicle-mounted component is a Tbox, the second and third vehicle-mounted components may be DCs, and the fourth vehicle-mounted component may be an MDC. Alternatively, when the first vehicle-mounted component is a Tbox, the second, third, and fourth vehicle-mounted components may all be DCs.

[0206] It can be seen that the above technical solution enriches the channels for reporting log association information. At the same time, because log association information can be reported through a secure channel, the security of log association information can be improved.

[0207] Optionally, the log reporting method may further include: the first vehicle-mounted component generating the first log or a hash value of the first log; or the first vehicle-mounted component sending second information to one or more of the second vehicle-mounted component, the third vehicle-mounted component, the fourth vehicle-mounted component, etc., where the second information is used to generate the hash value of the first log. The second information includes the first log.

[0208] In one possible implementation, after the first vehicle-mounted component generates the first log or the hash value of the first log, the log-related information may be reported to the server via one or more of a secure channel, a communication link, etc. In another possible implementation, after the first vehicle-mounted component generates the first log or the hash value of the first log, the first vehicle-mounted component may also send the first log or the hash value of the first log to one or more of a second vehicle-mounted component, a third vehicle-mounted component, a fourth vehicle-mounted component, etc., so that the reporting of the first log or the hash value of the first log is completed through one or more of the second vehicle-mounted component, the third vehicle-mounted component, the fourth vehicle-mounted component, etc.

[0209] In addition, after the first vehicle-mounted component sends the second information to one or more of the second vehicle-mounted component, the third vehicle-mounted component, the fourth vehicle-mounted component, etc., one or more of the second vehicle-mounted component, the third vehicle-mounted component, the fourth vehicle-mounted component, etc. can generate a hash value of the first log and complete the reporting of the first log or the hash value of the first log.

[0210] It can be seen that in the above technical solution, the log is generated by the first vehicle-mounted component, and the hash value of the log can be generated by the first vehicle-mounted component, or by one or more of the second vehicle-mounted component, the third vehicle-mounted component, the fourth vehicle-mounted component, etc., which enriches the generation method of the hash value of the log.

[0211] Optionally, at least one first server, at least one second server, and at least one third server may correspond to nodes of the blockchain network. It should be understood that one server may correspond to one node of the blockchain network. It should be noted that any node or accounting node in the blockchain network may generate a new block based on the reported first log or the hash value of the first log, and broadcast it to other nodes. Other nodes then verify the block. Once all nodes in the blockchain network reach consensus, the new block may be added to the blockchain.

[0212] In a possible implementation, one or more of the first vehicle-mounted component, the second vehicle-mounted component, the third vehicle-mounted component, the fourth vehicle-mounted component, etc. may also correspond to nodes of the blockchain network.

[0213] It should be understood that when the first vehicle-mounted component reports log-related information to the server only through one or more of a secure channel, a secure link, etc., the first vehicle-mounted component may correspond to a node of the blockchain network, while the second vehicle-mounted component, the third vehicle-mounted component, and the fourth vehicle-mounted component do not correspond to nodes of the blockchain network. For example, see Figure 6, which is a schematic diagram of a node of a blockchain network provided in an embodiment of the present application. As shown in Figure 6, the first vehicle-mounted component, the OEM server, the supplier server 1, the supplier server 2, the regulatory agency server 1, and the regulatory agency server 2 may correspond to nodes of the blockchain network, while one or more of the second vehicle-mounted component, the third vehicle-mounted component, the fourth vehicle-mounted component, etc. do not correspond to nodes of the blockchain network. Therefore, the first vehicle-mounted component does not report log-related information to different servers through other vehicle-mounted components, but reports log-related information to different servers through one or more of a secure channel, a secure link, etc.

[0214] When the first vehicle-mounted component reports log-related information to the server through one or more of a secure channel, a secure link, etc., and also reports log-related information to the server through other vehicle-mounted components, the first vehicle-mounted component may correspond to a node of the blockchain network, and some of the second vehicle-mounted component, the third vehicle-mounted component, the fourth vehicle-mounted component, etc. may also correspond to nodes of the blockchain network. For example, see Figure 7, which is a schematic diagram of another node of a blockchain network provided in an embodiment of the present application. In Figure 7, the first vehicle-mounted component, the second vehicle-mounted component, the OEM server, the supplier server 1, the supplier server 2, the regulatory agency server 1, and the regulatory agency server 2 may correspond to nodes of the blockchain network, while one or more of the third vehicle-mounted component, the fourth vehicle-mounted component, etc. do not correspond to nodes of the blockchain network. Assuming that the first vehicle-mounted component reports log-related information to the OEM server through the second vehicle-mounted component, then, with respect to the other servers in Figure 7, the first vehicle-mounted component reports log-related information through one or more of a secure channel, a secure link, etc., and therefore, the first vehicle-mounted component may correspond to a node of the blockchain network. Furthermore, the first vehicle-mounted component can send the first log or the hash value of the first log to the second vehicle-mounted component, so that the second vehicle-mounted component uploads the first log or the hash value of the first log to the blockchain network. Alternatively, the first vehicle-mounted component can send a second message to the second vehicle-mounted component, so that the second vehicle-mounted component generates a hash value of the first log and uploads the hash value of the first log to the blockchain network.

[0215] When the first vehicle-mounted component reports log-related information to the server only through other vehicle-mounted components, the first vehicle-mounted component does not correspond to a node in the blockchain network, while the second vehicle-mounted component, the third vehicle-mounted component, and the fourth vehicle-mounted component can all correspond to nodes in the blockchain network. For example, see Figure 8, which is a schematic diagram of another node in a blockchain network provided in an embodiment of the present application. In Figure 8, the second vehicle-mounted component, the third vehicle-mounted component, the fourth vehicle-mounted component, the OEM server, the supplier server 1, the supplier server 2, the regulatory agency server 1, and the regulatory agency server 2 can correspond to nodes in the blockchain network, while the first vehicle-mounted component does not correspond to a node in the blockchain network. Therefore, the first vehicle-mounted component reports log-related information to the different servers in Figure 8 through the second vehicle-mounted component, the third vehicle-mounted component, and the fourth vehicle-mounted component, and does not report log-related information to the server through one or more of a secure channel, a secure link, etc. Furthermore, the first vehicle-mounted component can send the first log or a hash value of the first log to the second vehicle-mounted component, so that the second vehicle-mounted component uploads the first log or the hash value of the first log to the blockchain network. Alternatively, the first vehicle-mounted component may send the second information to the second vehicle-mounted component, causing the second vehicle-mounted component to generate a hash value of the first log and upload the hash value of the first log to the blockchain network. It should be understood that the first vehicle-mounted component may also send the first log, the hash value of the first log, or the second information to one or more of the third and fourth vehicle-mounted components. For details, please refer to the interaction process between the first and second vehicle-mounted components, which will not be detailed here.

[0216] Optionally, the OTA server may correspond to a node of the blockchain network.

[0217] It can be seen that in the above technical solution, different servers can correspond to nodes of the blockchain network, and vehicle-mounted components can also correspond to nodes of the blockchain network, thereby utilizing the tamper-proof and non-forgeable characteristics of the blockchain to prevent logs or log hash values ​​from being tampered with.

[0218] It should be noted that in the embodiment shown in Figure 5, the OTA server can generate and transmit log reporting policy information, allowing the in-vehicle components to better meet requirements when reporting log-related information. At the same time, the in-vehicle components can report the first log-related information and the second log-related information of the first in-vehicle component to different servers based on the log reporting policy information. This allows the log-related information from different servers to be mutually verified, thereby preventing the log-related information from being tampered with.

[0219] The method embodiment shown in Figure 5 above includes many possible implementation schemes. Some of the implementation schemes are illustrated below in conjunction with Figure 8. It should be noted that the relevant concepts, operations or logical relationships not explained in Figure 9 can refer to the corresponding descriptions in the embodiment shown in Figure 5, and therefore will not be repeated here.

[0220] 9 , which is a flow chart of a log reporting system and a log reporting method provided by an embodiment of the present application. The system includes a vehicle and an OTA server. The method includes but is not limited to the following steps:

[0221] 901. The OTA server generates log reporting policy information.

[0222] For details, please refer to the detailed description in step 501.

[0223] 902. The OTA server sends log reporting policy information to the vehicle. In response, the vehicle obtains the log reporting policy information.

[0224] Specifically, the OTA server sends the log reporting policy information to the first vehicle-mounted component in the vehicle. Alternatively, the OTA server sends the log reporting policy information to the first vehicle-mounted component via the second vehicle-mounted component in the vehicle. For details, please refer to the detailed description in step 502.

[0225] It should be noted that the data link for sending and receiving information between the vehicle and the OTA server may include various types of connection media, specifically a wired link (such as optical fiber, etc.), or a wireless link, or a combination of a wired link and a wireless link, etc.

[0226] 903. The vehicle reports first log-related information of a first vehicle-mounted component in the vehicle to at least one first server according to the log reporting policy information, and reports second log-related information of the first vehicle-mounted component to at least one second server.

[0227] Specifically, the first vehicle-mounted component in the vehicle reports the first log-related information to at least one first server and reports the second log-related information to at least one second server according to the log reporting policy information.

[0228] Optionally, the vehicle may also report the third log-related information of the first vehicle-mounted component to at least one third server based on the log reporting policy information. Specifically, the first vehicle-mounted component in the vehicle may also report the third log-related information of the first vehicle-mounted component to at least one third server based on the log reporting policy information. For details, please refer to the detailed description in step 503.

[0229] It should be noted that in the embodiment shown in Figure 9, the OTA server can generate log reporting policy information and send it to the vehicle, enabling the vehicle to better meet requirements when reporting log-related information. Furthermore, the vehicle can report the first log-related information and the second log-related information to different servers based on the log-reporting policy information. This allows the log-related information from different servers to be mutually verified, thereby preventing tampering with the log-related information.

[0230] The above describes in detail the method of the embodiment of the present application, and the following provides an apparatus of the embodiment of the present application.

[0231] The embodiments of the present application also provide an apparatus for implementing any of the above methods. For example, a log reporting apparatus is provided, including a unit (or means) for implementing each step performed by the first vehicle-mounted component in any of the above methods. For another example, another log reporting apparatus is provided, including a unit (or means) for implementing each step performed by the OTA server in any of the above methods.

[0232] For example, please refer to Figure 10, which is a structural diagram of a log reporting device 100 provided in an embodiment of the present application. The log reporting device 100 includes a processing unit 1001, a sending unit 1002 and a receiving unit 1003, such as the log reporting method of any embodiment shown in Figure 5 or Figure 9.

[0233] It should be understood that the division of the various units in the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into a physical entity, or they can be physically separated. In addition, the units in the device can be implemented in the form of a processor calling software; for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or realize the functions of the various units of the device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units can be realized by designing the hardware circuits. The hardware circuit can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units by designing the logical relationship of the components in the circuit. For another example, in another implementation, the hardware circuit can be implemented by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units. All units of the above devices can be implemented in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0234] In an embodiment of the present application, a processor is a circuit with the ability to process signals. In one implementation, the processor may be a circuit with the ability to read and execute instructions, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP); in another implementation, the processor may implement certain functions through the logical relationship of a hardware circuit, and the logical relationship of the hardware circuit is fixed or reconfigurable, such as a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document to implement the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0235] It can be seen that each unit in the above device can be one or more processors (or processing circuits) configured to implement the above method, such as: CPU, GPU, NPU, TPU, DPU, microprocessor, DSP, ASIC, FPGA, or a combination of at least two of these processor forms.

[0236] In addition, the various units in the above devices can be fully or partially integrated together, or can be implemented independently. In one implementation, these units are integrated together and implemented in the form of a system-on-a-chip (SOC). The SOC may include at least one processor for implementing any of the above methods or implementing the functions of the various units of the device. The type of the at least one processor can be different, for example, including a CPU and FPGA, a CPU and an artificial intelligence processor, a CPU and a GPU, etc.

[0237] Regardless of whether these functional modules are subdivided or combined, the general process performed by the device 100 during the log reporting process is the same. For example, the receiving unit 1003 and the sending unit 1002 in the above-mentioned device 100 can also be combined into a communication unit. Usually, each unit corresponds to its own program code (or program instruction), and when the program code corresponding to each of these units is run on the processor, the unit executes the corresponding process to achieve the corresponding function. It should be noted that the implementation of each of the following units can correspond to the corresponding description of the embodiment shown in Figure 5 or Figure 9.

[0238] In one possible implementation, the log reporting device 100 may be the first vehicle-mounted component in the embodiment shown in FIG. 5 or FIG. 9 , or a module in the first vehicle-mounted component, such as a chip or integrated circuit. The device includes a sending unit 1002 and a receiving unit 1003 , wherein each unit is described as follows:

[0239] Receiving unit 1003, used to obtain log reporting policy information;

[0240] The sending unit 1002 is used to report the first log association information of the first vehicle-mounted component to at least one first server according to the log reporting policy information, and to report the second log association information of the first vehicle-mounted component to at least one second server. The at least one first server is one or more of the original equipment manufacturer OEM server, the supplier server or the regulatory agency server, and the at least one second server is one or more of the original equipment manufacturer OEM server, the supplier server or the regulatory agency server. The first server is different from the second server.

[0241] Optionally, the first log association information includes at least one of the first log and a hash value of the first log; and the second log association information includes at least one of the first log and a hash value of the first log.

[0242] Optionally, the sending unit 1002 is specifically used to report first log-related information to at least one first server through a first security channel or a second vehicle-mounted component according to the log reporting policy information, and to report second log-related information to at least one second server through a second security channel or a third vehicle-mounted component. The first security channel is a channel between the first vehicle-mounted component and each server in the at least one first server, the second security channel is a channel between the first vehicle-mounted component and each server in the at least one second server, a security channel is established between the second vehicle-mounted component and each server in the at least one first server, and a security channel is established between the third vehicle-mounted component and each server in the at least one second server.

[0243] Optionally, the log reporting policy information includes at least one of the following: the identification of the vehicle-mounted component that needs to report the log, the destination address of the vehicle-mounted component reporting the log, the type of log that the vehicle-mounted component needs to report, the triggering condition for the vehicle-mounted component reporting the log, the log content that the vehicle-mounted component needs to report, or the first information; wherein the first information is used to indicate the hash value of the vehicle-mounted component reporting the log or to indicate the vehicle-mounted component reporting the log.

[0244] Optionally, the trigger condition includes at least one of the following: the danger level of the operation performed by the vehicle-mounted component is equal to or higher than a preset danger level; the period for the vehicle-mounted component to report a log arrives; a log reporting trigger event occurs.

[0245] Optionally, the log reporting triggering event includes at least one of the following: the vehicle's accident data recorder EDR is triggered, the vehicle's automatic driving is started, the vehicle's automatic driving is turned off, and the user is reminded to take over the driving control of the vehicle when the vehicle is in automatic driving mode, and the vehicle includes on-board components.

[0246] Optionally, the log content includes at least one of the following: an operation performed by the vehicle-mounted component, a result of the operation performed by the vehicle-mounted component, and a time when the operation was performed by the vehicle-mounted component.

[0247] Optionally, the vehicle-mounted component includes a first vehicle-mounted component.

[0248] Optionally, the processing unit 1001 is used to generate a first log or a hash value of the first log; or the sending unit 1002 is further used to send second information to one or more of the second vehicle-mounted component and the third vehicle-mounted component, where the second information is used to generate a hash value of the first log.

[0249] Optionally, at least one first server and at least one second server correspond to nodes of the blockchain network.

[0250] In one possible implementation, the log reporting device 100 may be the OTA server in the embodiment shown in FIG. 5 or FIG. 9 , or a component of the OTA server, such as a chip or integrated circuit. The device includes a processing unit 1001 and a sending unit 1002 , wherein each unit is described as follows:

[0251] Processing unit 1001, used to generate log reporting policy information;

[0252] The sending unit 1002 is configured to send log reporting policy information.

[0253] Optionally, the log reporting policy information includes at least one of the following: the identification of the vehicle-mounted component that needs to report the log, the destination address of the vehicle-mounted component reporting the log, the type of log that the vehicle-mounted component needs to report, the triggering condition for the vehicle-mounted component reporting the log, the log content that the vehicle-mounted component needs to report, or the first information; wherein the first information is used to indicate the hash value of the vehicle-mounted component reporting the log or to indicate the vehicle-mounted component reporting the log.

[0254] Optionally, the trigger condition includes at least one of the following: the danger level of the operation performed by the vehicle-mounted component is equal to or higher than a preset danger level; the period for the vehicle-mounted component to report a log arrives; a log reporting trigger event occurs.

[0255] Optionally, the log reporting triggering event includes at least one of the following: the vehicle's accident data recorder EDR is triggered, the vehicle's automatic driving is started, the vehicle's automatic driving is turned off, and the user is reminded to take over the driving control of the vehicle when the vehicle is in automatic driving mode, and the vehicle includes on-board components.

[0256] Optionally, the log content includes at least one of the following: an operation performed by the vehicle-mounted component, a result of the operation performed by the vehicle-mounted component, and a time when the operation was performed by the vehicle-mounted component.

[0257] Optionally, the vehicle-mounted component includes a first vehicle-mounted component.

[0258] Referring to FIG. 11 , FIG. 11 is a schematic structural diagram of a vehicle 110 provided in an embodiment of the present application. The vehicle 110 may be the vehicle in the embodiment shown in FIG. 9 . The vehicle 110 includes a first vehicle-mounted component 1101 , wherein:

[0259] A first vehicle-mounted component in the vehicle, configured to obtain log reporting policy information;

[0260] The first vehicle-mounted component in the vehicle is also used to report the first log-related information of the first vehicle-mounted component to at least one first server according to the log reporting policy information, and report the second log-related information of the first vehicle-mounted component to at least one second server. The at least one first server is one or more of the original equipment manufacturer OEM server, supplier server or regulatory agency server, and the at least one second server is one or more of the original equipment manufacturer OEM server, supplier server or regulatory agency server. The first server is different from the second server.

[0261] Optionally, the first log association information includes at least one of the first log and a hash value of the first log; and the second log association information includes at least one of the first log and a hash value of the first log.

[0262] Optionally, the vehicle 110 may also include one or more of a second vehicle-mounted component 1102, a third vehicle-mounted component 1103, etc. The first vehicle-mounted component in the vehicle is specifically used to report first log-related information to at least one first server through a first security channel or a second vehicle-mounted component according to log reporting policy information, and report second log-related information to at least one second server through a second security channel or a third vehicle-mounted component. The first security channel is a channel between the first vehicle-mounted component and each server in the at least one first server, the second security channel is a channel between the first vehicle-mounted component and each server in the at least one second server, a security channel is established between the second vehicle-mounted component and each server in the at least one first server, and a security channel is established between the third vehicle-mounted component and each server in the at least one second server.

[0263] Optionally, the log reporting policy information includes at least one of the following: the identification of the vehicle-mounted component that needs to report the log, the destination address of the vehicle-mounted component reporting the log, the type of log that the vehicle-mounted component needs to report, the triggering condition for the vehicle-mounted component reporting the log, the log content that the vehicle-mounted component needs to report, or the first information; wherein the first information is used to indicate the hash value of the vehicle-mounted component reporting the log or to indicate the vehicle-mounted component reporting the log.

[0264] Optionally, the trigger condition includes at least one of the following: the danger level of the operation performed by the vehicle-mounted component is equal to or higher than a preset danger level; the period for the vehicle-mounted component to report a log arrives; a log reporting trigger event occurs.

[0265] Optionally, the log reporting triggering event includes at least one of the following: the vehicle's accident data recorder EDR is triggered, the vehicle's automatic driving is started, the vehicle's automatic driving is turned off, and the user is reminded to take over the driving control of the vehicle when the vehicle is in automatic driving mode, and the vehicle includes on-board components.

[0266] Optionally, the log content includes at least one of the following: an operation performed by the vehicle-mounted component, a result of the operation performed by the vehicle-mounted component, and a time when the operation was performed by the vehicle-mounted component.

[0267] Optionally, the vehicle-mounted component includes a first vehicle-mounted component.

[0268] Optionally, the first vehicle-mounted component in the vehicle is also used to generate a first log or a hash value of the first log; or, to send second information to one or more of the second vehicle-mounted component and the third vehicle-mounted component, and the second information is used to generate a hash value of the first log.

[0269] Optionally, at least one first server and at least one second server correspond to nodes of the blockchain network.

[0270] Referring to Figure 12 , Figure 12 is a schematic diagram of the structure of a log reporting device 120 provided in an embodiment of the present application. The device 120 may include at least one memory 1201 and at least one processor 1202. Optionally, it may also include a bus 1203. Further optionally, it may also include a communication interface 1204, wherein the memory 1201, processor 1202, and communication interface 1204 are connected via bus 1203.

[0271] Memory 1201 is used to provide storage space for storing data such as an operating system and computer programs. Memory 1201 can be one or a combination of random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM).

[0272] The processor 1202 is a module that performs arithmetic operations and / or logical operations, and can specifically be one or more combinations of processing modules such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor unit (MPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), and a complex programmable logic device (CPLD).

[0273] The communication interface 1204 is used to receive data sent externally and / or send data externally. It can be a wired link interface such as an Ethernet cable, or a wireless link interface (Wi-Fi, Bluetooth, general wireless transmission, etc.). Optionally, the communication interface 1204 can also include a transmitter (such as a radio frequency transmitter, antenna, etc.) or a receiver coupled to the interface.

[0274] The processor 1202 in the device 120 is used to read the computer program stored in the memory 1201 to execute the aforementioned log reporting method, such as the log reporting method described in any one of the embodiments of FIG. 5 or FIG. 9 .

[0275] In some possible implementations, the log reporting device 120 may be the first vehicle-mounted component in the embodiment shown in FIG. 5 or FIG. 9 , or a module in the first vehicle-mounted component, such as a chip or integrated circuit. The processor 1202 in the device 120 is configured to read the computer program stored in the memory 1201 to perform the following operations:

[0276] Obtain log reporting policy information through the communication interface 1204;

[0277] Through the communication interface 1204, the first log-related information of the first vehicle-mounted component is reported to at least one first server according to the log reporting strategy information, and the second log-related information of the first vehicle-mounted component is reported to at least one second server. The at least one first server is one or more of the original equipment manufacturer OEM server, the supplier server or the regulatory agency server, and the at least one second server is one or more of the original equipment manufacturer OEM server, the supplier server or the regulatory agency server. The first server is different from the second server.

[0278] Optionally, the first log association information includes at least one of the first log and a hash value of the first log; and the second log association information includes at least one of the first log and a hash value of the first log.

[0279] Optionally, the processor 1202 is specifically used to perform the following operations: according to the log reporting policy information, report the first log association information to the at least one first server through the first security channel or the second vehicle-mounted component, and report the second log association information to the at least one second server through the second security channel or the third vehicle-mounted component. The first security channel is the channel between the first vehicle-mounted component and each server of the at least one first server, the second security channel is the channel between the first vehicle-mounted component and each server of the at least one second server, a security channel is established between the second vehicle-mounted component and each server of the at least one first server, and a security channel is established between the third vehicle-mounted component and each server of the at least one second server.

[0280] Optionally, the log reporting policy information includes at least one of the following: the identification of the vehicle-mounted component that needs to report the log, the destination address of the vehicle-mounted component reporting the log, the type of log that the vehicle-mounted component needs to report, the triggering condition for the vehicle-mounted component reporting the log, the log content that the vehicle-mounted component needs to report, or the first information; wherein the first information is used to indicate the hash value of the vehicle-mounted component reporting the log or to indicate the vehicle-mounted component reporting the log.

[0281] Optionally, the trigger condition includes at least one of the following: the danger level of the operation performed by the vehicle-mounted component is equal to or higher than a preset danger level; the period for the vehicle-mounted component to report a log arrives; a log reporting trigger event occurs.

[0282] Optionally, the log reporting triggering event includes at least one of the following: the vehicle's accident data recorder EDR is triggered, the vehicle's automatic driving is started, the vehicle's automatic driving is turned off, and the user is reminded to take over the driving control of the vehicle when the vehicle is in automatic driving mode, and the vehicle includes on-board components.

[0283] Optionally, the log content includes at least one of the following: an operation performed by the vehicle-mounted component, a result of the operation performed by the vehicle-mounted component, and a time when the operation was performed by the vehicle-mounted component.

[0284] Optionally, the vehicle-mounted component includes a first vehicle-mounted component.

[0285] Optionally, the processor 1202 is further used to perform the following operations: generate a first log or a hash value of the first log; or send second information to one or more of the second vehicle-mounted component and the third vehicle-mounted component through the communication interface 1204, where the second information is used to generate a hash value of the first log.

[0286] Optionally, at least one first server and at least one second server correspond to nodes of the blockchain network.

[0287] In some possible implementations, the log reporting device 120 may be the OTA server in the embodiment shown in FIG. 5 or FIG. 9 , or a component of the OTA server, such as a chip or integrated circuit. The processor 1202 in the device 120 is configured to read the computer program stored in the memory 1201 and perform the following operations:

[0288] Generate log reporting policy information;

[0289] Send log reporting policy information.

[0290] The log reporting policy information is sent via the communication interface 1204. Optionally, the log reporting device 120 may be deployed in an OTA server.

[0291] Optionally, the log reporting policy information includes at least one of the following: the identification of the vehicle-mounted component that needs to report the log, the destination address of the vehicle-mounted component reporting the log, the type of log that the vehicle-mounted component needs to report, the triggering condition for the vehicle-mounted component reporting the log, the log content that the vehicle-mounted component needs to report, or the first information; wherein the first information is used to indicate the hash value of the vehicle-mounted component reporting the log or to indicate the vehicle-mounted component reporting the log.

[0292] Optionally, the trigger condition includes at least one of the following: the danger level of the operation performed by the vehicle-mounted component is equal to or higher than a preset danger level; the period for the vehicle-mounted component to report a log arrives; a log reporting trigger event occurs.

[0293] Optionally, the log reporting triggering event includes at least one of the following: the vehicle's accident data recorder EDR is triggered, the vehicle's automatic driving is started, the vehicle's automatic driving is turned off, and the user is reminded to take over the driving control of the vehicle when the vehicle is in automatic driving mode, and the vehicle includes on-board components.

[0294] Optionally, the log content includes at least one of the following: an operation performed by the vehicle-mounted component, a result of the operation performed by the vehicle-mounted component, and a time when the operation was performed by the vehicle-mounted component.

[0295] Optionally, the vehicle-mounted component includes a first vehicle-mounted component.

[0296] An embodiment of the present application provides a log reporting system, including a first vehicle-mounted component and an OTA server, wherein the first vehicle-mounted component is used to implement the method as shown in any one of Figures 5 or 9, and the OTA server is used to implement the method as shown in any one of Figures 5 or 9.

[0297] An embodiment of the present application provides a log reporting system, including a vehicle and an OTA server, wherein the vehicle includes a first vehicle-mounted component, the first vehicle-mounted component is used to implement the method as shown in any one of Figures 5 or 9, and the OTA server is used to implement the method as shown in any one of Figures 5 or 9.

[0298] An embodiment of the present application provides a terminal, which may be a smart cockpit product, a vehicle, etc. The terminal is used to implement the method as shown in any one of Figures 5 or 9.

[0299] Alternatively, the above-mentioned vehicles can also be replaced by intelligent terminals or intelligent transportation tools such as drones and robots.

[0300] An embodiment of the present application provides a chip system, which includes at least one processor, a memory and an interface circuit, wherein the interface circuit is used to provide information input / output for the at least one processor. The memory stores a computer program, which implements the method on the OTA server side or the first vehicle-mounted component side in any embodiment of Figure 5 or Figure 9 when the computer program runs on one or more processors.

[0301] An embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored. When the computer program runs on one or more processors, the method shown in any one of FIG. 5 or FIG. 9 is implemented.

[0302] An embodiment of the present application further provides a computer program product, which, when running on one or more processors, implements the method shown in any one of FIG. 5 or FIG. 9 .

[0303] When the computer instruction is loaded and executed on a computer, the process or function described in the embodiment of the present application can be realized in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable devices. The computer instruction can be stored in a computer-readable storage medium or transmitted by a computer-readable storage medium. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or a data center that includes one or more available media integrations. Available media can be magnetic media, (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD) or a semiconductor medium (for example, a solid-state drive (SSD)).

[0304] The steps in the method embodiments of the present application can be adjusted in sequence, combined, or deleted according to actual needs.

[0305] The modules in the embodiment of the device of the present application can be merged, divided and deleted according to actual needs.

Claims

1. A log reporting method, characterized in that: include: Get log reporting policy information; According to the log reporting policy information, the first log of the first vehicle-mounted component or the hash value of the first log is reported to at least one first server, and the first log or the hash value of the first log is reported to at least one second server. The at least one first server is one or more of the original equipment manufacturer OEM server, the supplier server or the regulatory agency server, and the at least one second server is one or more of the original equipment manufacturer OEM server, the supplier server or the regulatory agency server, and the first server is different from the second server.

2. The method according to claim 1, characterized in that The log reporting policy information includes at least one of the following: an identifier of the vehicle-mounted component that needs to report the log, a destination address for the vehicle-mounted component to report the log, a type of log that the vehicle-mounted component needs to report, a triggering condition for the vehicle-mounted component to report the log, and a log content or first information that the vehicle-mounted component needs to report; The first information is used to indicate a hash value of a log reported by the vehicle-mounted component or to indicate a log reported by the vehicle-mounted component.

3. The method according to claim 2, characterized in that The triggering condition includes at least one of the following: The danger level of the operation performed by the vehicle-mounted component is equal to or higher than a preset danger level; The period for the vehicle-mounted component to report a log has arrived; A log reporting trigger event occurs.

4. The method according to claim 3, characterized in that The log reporting triggering event includes at least one of the following: the vehicle's accident data recorder EDR is triggered, the vehicle's automatic driving is started, the vehicle's automatic driving is turned off, and the user is reminded to take over the driving control of the vehicle when the vehicle is in automatic driving mode, and the vehicle includes the on-board components.

5. The method according to any one of claims 2 to 4, characterized in that: The log content includes at least one of the following: an operation performed by the vehicle-mounted component, a result of the operation performed by the vehicle-mounted component, and a time when the vehicle-mounted component performed the operation.

6. The method according to any one of claims 2 to 5, characterized in that: The vehicle-mounted components include a first vehicle-mounted component.

7. The method according to any one of claims 1 to 6, characterized in that The reporting of the first log of the first vehicle-mounted component or the hash value of the first log to at least one first server according to the log reporting policy information, and reporting the first log or the hash value of the first log to at least one second server, includes: According to the log reporting policy information, the first log or the hash value of the first log is reported to the at least one first server through the first security channel or the second vehicle-mounted component, and the first log or the hash value of the first log is reported to the at least one second server through the second security channel or the third vehicle-mounted component. The first security channel is the channel between the first vehicle-mounted component and each server in the at least one first server, the second security channel is the channel between the first vehicle-mounted component and each server in the at least one second server, a security channel is established between the second vehicle-mounted component and each server in the at least one first server, and a security channel is established between the third vehicle-mounted component and each server in the at least one second server.

8. The method according to any one of claims 1 to 7, characterized in that The method further comprises: generating the first log or a hash value of the first log; or, Second information is sent to one or more of a second vehicle-mounted component and a third vehicle-mounted component, where the second information is used to generate a hash value of the first log.

9. The method according to any one of claims 1 to 8, characterized in that The at least one first server and the at least one second server correspond to nodes of a blockchain network.

10. A log reporting method, characterized in that: include: Generate log reporting policy information; Send the log reporting policy information.

11. The method according to claim 10, characterized in that The log reporting policy information includes at least one of the following: an identifier of the vehicle-mounted component that needs to report the log, a destination address for the vehicle-mounted component to report the log, a type of log that the vehicle-mounted component needs to report, a triggering condition for the vehicle-mounted component to report the log, and a log content or first information that the vehicle-mounted component needs to report; The first information is used to indicate a hash value of a log reported by the vehicle-mounted component or to indicate a log reported by the vehicle-mounted component.

12. The method according to claim 11, characterized in that The triggering condition includes at least one of the following: The danger level of the operation performed by the vehicle-mounted component is equal to or higher than a preset danger level; The period for the vehicle-mounted component to report a log has arrived; A log reporting trigger event occurs.

13. The method according to claim 12, characterized in that The log reporting triggering event includes at least one of the following: the vehicle's accident data recorder EDR is triggered, the vehicle's automatic driving is started, the vehicle's automatic driving is turned off, and the user is reminded to take over the driving control of the vehicle when the vehicle is in automatic driving mode, and the vehicle includes the on-board components.

14. The method according to claim 11, characterized in that The log content includes at least one of the following: an operation performed by the vehicle-mounted component, a result of the operation performed by the vehicle-mounted component, and a time when the vehicle-mounted component performed the operation.

15. The method according to any one of claims 11 to 14, characterized in that: The vehicle-mounted components include a first vehicle-mounted component.

16. A log reporting device, characterized in that: The device comprises a receiving unit and a sending unit, The receiving unit is used to obtain log reporting policy information; The sending unit is used to report the first log of the first vehicle-mounted component or the hash value of the first log to at least one first server according to the log reporting policy information, and report the first log or the hash value of the first log to at least one second server. The at least one first server is one or more of the original equipment manufacturer OEM server, the supplier server or the regulatory agency server, and the at least one second server is one or more of the original equipment manufacturer OEM server, the supplier server or the regulatory agency server, and the first server is different from the second server.

17. The device according to claim 16, characterized in that The sending unit is specifically used to report the first log or the hash value of the first log to the at least one first server through the first security channel or the second vehicle-mounted component according to the log reporting policy information, and report the first log or the hash value of the first log to the at least one second server through the second security channel or the third vehicle-mounted component. The first security channel is the channel between the first vehicle-mounted component and each server in the at least one first server, the second security channel is the channel between the first vehicle-mounted component and each server in the at least one second server, a security channel is established between the second vehicle-mounted component and each server in the at least one first server, and a security channel is established between the third vehicle-mounted component and each server in the at least one second server.

18. The device according to claim 16 or 17, characterized in that The device further comprises a processing unit, The processing unit is configured to generate the first log or a hash value of the first log; or, The sending unit is used to send second information to one or more of the second vehicle-mounted component and the third vehicle-mounted component, where the second information is used to generate a hash value of the first log.

19. A log reporting device, characterized in that: The device is deployed in a vehicle and includes a receiving unit and a sending unit. The receiving unit is used to obtain log reporting policy information; The sending unit is used to report the first log of the first vehicle-mounted component or the hash value of the first log to at least one first server according to the log reporting policy information, and report the first log or the hash value of the first log to at least one second server. The at least one first server is one or more of the original equipment manufacturer OEM server, the supplier server or the regulatory agency server, and the at least one second server is one or more of the original equipment manufacturer OEM server, the supplier server or the regulatory agency server, and the first server is different from the second server.

20. The device according to claim 19, characterized in that The sending unit is specifically used to report the first log or the hash value of the first log to the at least one first server through the first security channel or the second vehicle-mounted component according to the log reporting policy information, and report the first log or the hash value of the first log to the at least one second server through the second security channel or the third vehicle-mounted component. The first security channel is the channel between the first vehicle-mounted component and each server in the at least one first server, the second security channel is the channel between the first vehicle-mounted component and each server in the at least one second server, a security channel is established between the second vehicle-mounted component and each server in the at least one first server, and a security channel is established between the third vehicle-mounted component and each server in the at least one second server.

21. The device according to claim 19 or 20, characterized in that The device further comprises a processing unit, The processing unit is configured to generate the first log or a hash value of the first log; or, The sending unit is used to send second information to one or more of the second vehicle-mounted component and the third vehicle-mounted component, where the second information is used to generate a hash value of the first log.

22. A log reporting device, characterized in that: The device comprises a processing unit and a sending unit, The processing unit is used to generate log reporting policy information; The sending unit is configured to send the log reporting policy information.

23. A log reporting device, characterized in that: The apparatus includes at least one processor and a communication interface, wherein the at least one processor is configured to call a computer program stored in at least one memory to perform the following operations: Obtaining log reporting policy information through the communication interface; Through the communication interface, the first log of the first vehicle-mounted component or the hash value of the first log is reported to at least one first server according to the log reporting policy information, and the first log or the hash value of the first log is reported to at least one second server. The at least one first server is one or more of the original equipment manufacturer OEM server, the supplier server or the regulatory agency server, and the at least one second server is one or more of the original equipment manufacturer OEM server, the supplier server or the regulatory agency server, and the first server is different from the second server.

24. The device according to claim 23, characterized in that The at least one processor is specifically configured to perform the following operations: Through the communication interface and according to the log reporting policy information, the first log or the hash value of the first log is reported to the at least one first server through the first security channel or the second vehicle-mounted component, and the first log or the hash value of the first log is reported to the at least one second server through the second security channel or the third vehicle-mounted component. The first security channel is the channel between the first vehicle-mounted component and each server in the at least one first server, the second security channel is the channel between the first vehicle-mounted component and each server in the at least one second server, a security channel is established between the second vehicle-mounted component and each server in the at least one first server, and a security channel is established between the third vehicle-mounted component and each server in the at least one second server.

25. The device according to claim 23 or 24, characterized in that The at least one processor is further configured to perform the following operations: generating the first log or a hash value of the first log; or, Second information is sent to one or more of the second vehicle-mounted component and the third vehicle-mounted component through the communication interface, where the second information is used to generate a hash value of the first log.

26. A log reporting device, characterized in that: The apparatus includes at least one processor and a communication interface, wherein the at least one processor is configured to call a computer program stored in at least one memory to perform the following operations: Generate log reporting policy information; The log reporting policy information is sent through the communication interface.

27. A log reporting system, characterized in that: The method comprises a first vehicle-mounted component and an over-the-air download technology OTA server, wherein the first vehicle-mounted component is used to implement the method according to any one of claims 1 to 9, and the OTA server is used to implement the method according to any one of claims 10 to 15.

28. A log reporting system, characterized in that: The invention comprises a vehicle and an over-the-air download technology OTA server, wherein the vehicle comprises a first vehicle-mounted component, the first vehicle-mounted component is used to implement the method according to any one of claims 1-9, and the OTA server is used to implement the method according to any one of claims 10-15.

29. A terminal, characterized in that: The terminal is used to implement the method according to any one of claims 1 to 9.

30. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is run on one or more processors, the method according to any one of claims 1 to 15 is implemented.

31. A computer program product, characterized in that When the computer program product is run on one or more processors, the computer program product implements the method according to any one of claims 1 to 15.

32. A chip system, characterized in that: The chip system includes at least one processor, a memory and an interface circuit, wherein the interface circuit is used to provide information input / output for the at least one processor, and a computer program is stored in the memory. When the computer program runs on one or more processors, the method described in any one of claims 1 to 15 is implemented.

Images