Vehicle cloud service-based operation log recall method, device and equipment and storage medium

Abstract

The invention provides a running log recall method, device and equipment based on vehicle cloud service and a storage medium, log recall configuration information is generated through a cloud server, and the configuration information comprises a vehicle identifier ID and a controller identifier ID. And the cloud server issues the log recall configuration information to the vehicle-mounted TBOX of the target vehicle according to the vehicle identifier ID, and the TBOX forwards the information to the vehicle central domain controller. And after analyzing the controller identifier ID, the central domain controller issues a log recall request to the corresponding target controller. And after confirming that the request is legal, the target controller requests to obtain the URL address of the target server and uploads the target log file to the corresponding server, so that remote recall of the running log is realized. According to the method, the log recall configuration information is uniformly generated and issued through the cloud server, centralized management and automatic scheduling of the log recall tasks are realized, the recall tasks can be accurately issued for specific vehicles and controllers, and low efficiency and errors caused by manual operation are avoided.

Description

Technical Field

[0001] This invention relates to the field of vehicle networking technology, and in particular to a method, apparatus, device, and storage medium for recalling vehicle cloud service operation logs. Background Technology

[0002] With the development of intelligent connected vehicles, multiple electronic control units (ECUs) and a central domain controller are integrated within the vehicle to realize various functions such as power control, body control, driver assistance, and infotainment. To facilitate fault diagnosis and remote maintenance, vehicles typically generate operating logs in the controllers to record system operating status, communication data, and anomaly information. When a vehicle experiences a problem or requires software upgrade verification, maintenance personnel often need to retrieve the relevant operating logs from the vehicle to assist in analyzing the cause of the problem.

[0003] However, existing log retrieval methods generally suffer from the following problems: First, traditional solutions mostly rely on manual or diagnostic equipment to extract logs via wired connections, which cannot meet the remote recall needs of large-scale distributed fleets. Second, even if some vehicles support log uploads via vehicle-to-cloud communication, the lack of a unified scheduling mechanism and security verification strategy leads to inconsistent log upload paths, unstable data transmission, and a high risk of missing logs or upload failures. Furthermore, existing systems typically lack fine-grained management of log types and time ranges from different controllers, and also lack a closed-loop feedback mechanism for upload status, affecting the traceability and reliability of log recall tasks.

[0004] In summary, the problems existing in the current technology urgently need to be solved. Summary of the Invention

[0005] This invention provides a method, apparatus, device, and storage medium for recalling vehicle cloud service operation logs, which addresses the deficiencies in the prior art and enables centralized management and automatic scheduling of log recall tasks.

[0006] This invention provides a method for recalling data based on vehicle cloud service operation logs, including: Log recall configuration information is generated by a cloud server based on preset configuration parameters. The log recall configuration information includes vehicle identifier ID and controller identifier ID. The log recall configuration information is sent to the vehicle's onboard TBOX based on the vehicle identification ID, so that the log recall configuration information can be forwarded to the target vehicle's central domain controller through the onboard TBOX. The central domain controller parses the controller identifier ID in the log recall configuration information and sends a log recall request to the target controller in the target vehicle. The target controller verifies whether the log recall request is valid. If the log retrieval request is valid, the central domain controller is requested to obtain the URL address of the target server, and the target log file is uploaded to the target server corresponding to the URL address.

[0007] According to the present invention, a method for recalling logs based on vehicle cloud service operation logs includes the following step: Firstly, the log recall configuration information is sent to the vehicle's onboard TBOX based on the vehicle identifier ID, and then the onboard TBOX forwards the log recall configuration information to the target vehicle's central domain controller. The cloud server determines the communication channel of the target vehicle based on the vehicle identification ID; The log recall configuration information is sent to the vehicle TBOX corresponding to the target vehicle via the vehicle cloud service; After receiving the log recall configuration information, the vehicle-mounted TBOX verifies the integrity of the configuration information and forwards the log recall configuration information to the central domain controller of the target vehicle according to the communication protocol.

[0008] According to the present invention, a method for recalling vehicle cloud service operation logs includes the step of resolving the controller identifier ID from the log recall configuration information through the central domain controller and sending a log recall request to the target controller in the target vehicle. The specific steps include: The central domain controller receives log recall configuration information forwarded by the vehicle-mounted TBOX. The log recall configuration information is structured and parsed to extract the controller identifier ID. Based on a preset controller identifier mapping table, determine the target controller communication address corresponding to the controller identifier ID; A log recall request message is generated based on the log recall configuration information and sent to the target controller.

[0009] According to the present invention, a method for recalling vehicle cloud service operation logs, the step of uploading the log file to the server corresponding to the URL address specifically includes: Package the target log file according to the log type and log time range defined in the log recall configuration information; Determine whether the size of the packaged log file exceeds a preset threshold. If the log file size exceeds the preset threshold, perform a segmented transmission operation.

[0010] According to the present invention, a method for recalling vehicle cloud service operation logs, after the step of uploading the target log file to the server corresponding to the URL address, further includes: After the log file upload is completed, the target controller generates an execution result report containing the log retrieval task ID, upload status, number of log files, upload time and error code, and sends the execution result report to the central domain controller. The execution result report is formatted and verified by the central domain controller, and then uploaded to the cloud server through the vehicle-to-cloud communication channel of the vehicle-mounted TBOX.

[0011] According to the present invention, a method for recalling vehicle cloud service operation logs, after the step of formatting and verifying the execution result report through the central domain controller and uploading it to the cloud server through the vehicle cloud communication channel of the vehicle TBOX, further includes: The task ID in the execution result report is verified through the cloud server; If an upload failure or missing data is detected, a retry task is triggered or a retransmission command is sent to the target vehicle.

[0012] According to the vehicle cloud service operation log recall method provided by the present invention, before the step of requesting the URL address of the target server from the central domain controller, the method further includes: The current network connection status is detected through the central domain controller; When the communication status between the vehicle-mounted TBOX and the cloud server is detected to be unstable, the log recall task is paused, and the request to obtain the URL address of the target server is retried after the communication is restored.

[0013] The present invention also provides a vehicle cloud service operation log recall device, comprising: The information generation module is used to generate log recall configuration information through a cloud server based on preset configuration parameters. The log recall configuration information includes vehicle identifier ID and controller identifier ID. The information delivery module is used to deliver the log recall configuration information to the vehicle TBOX of the target vehicle according to the vehicle identification ID, so as to forward the log recall configuration information to the central domain controller of the target vehicle through the vehicle TBOX. The log recall module is used to parse the controller identifier ID in the log recall configuration information through the central domain controller and send a log recall request to the target controller in the target vehicle. The request detection module is used to verify the legitimacy of the log recall request through the target controller; The log upload module is used to request the URL address of the target server from the central domain controller if the log retrieval request is valid, and then upload the target log file to the target server corresponding to the URL address.

[0014] The present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the vehicle cloud service operation log recall method described above.

[0015] The present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the vehicle-cloud service operation log recall method as described above.

[0016] The present invention also provides a computer program product, including a computer program that, when executed by a processor, implements the vehicle cloud service operation log recall method as described above.

[0017] This invention provides a method, apparatus, device, and storage medium for recalling operation logs based on vehicle-cloud services. The method generates log recall configuration information via a cloud server, including a vehicle identifier ID and a controller identifier ID. The cloud server distributes the log recall configuration information to the target vehicle's onboard unit (TBOX) based on the vehicle identifier ID, and the TBOX forwards this information to the vehicle's central domain controller. The central domain controller parses the controller identifier ID and sends a log recall request to the corresponding target controller. After confirming the request's validity, the target controller requests the URL address of the target server and uploads the target log file to the corresponding server, thus achieving remote recall of the operation logs. This invention achieves centralized management and automatic scheduling of log recall tasks by uniformly generating and distributing log recall configuration information through a cloud server. It can accurately distribute recall tasks to specific vehicles and controllers, avoiding the inefficiency and errors caused by manual operation. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in this invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0019] Figure 1 This is a flowchart illustrating the vehicle cloud service operation log recall method provided by the present invention. Figure 2 This is a schematic diagram of the structure of the vehicle cloud service operation log recall device provided by the present invention; Figure 3 This is a schematic diagram of the structure of the electronic device provided by the present invention. Detailed Implementation

[0020] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0021] To address the problems in existing technologies, this invention proposes a method for recalling vehicle cloud service operation logs, achieving centralized management and automatic scheduling of log recall tasks. The following describes this method for recalling vehicle cloud service operation logs. Figure 1 As shown, including but not limited to the following steps: Step 110: Generate log recall configuration information through the cloud server according to the preset configuration parameters. The log recall configuration information includes vehicle ID and controller ID.

[0022] In step 110, the cloud server first reads the vehicle identification information of the vehicles to be recalled from the vehicle management database and determines the target vehicle list according to the recall task strategy. Then, the cloud server generates corresponding log-based recall configuration information based on the task type, log collection cycle, log type (such as operation logs, communication logs, fault logs, etc.), and the target controller range. This configuration information includes a vehicle identifier ID used to uniquely identify the vehicle and a controller identifier ID used to identify the specific controller. The cloud server can further digitally sign and encrypt the generated configuration information to ensure data security and integrity during subsequent distribution.

[0023] Step 120: Send the log recall configuration information to the vehicle's onboard TBOX based on the vehicle identification ID, so that the log recall configuration information can be forwarded to the central domain controller of the target vehicle through the onboard TBOX.

[0024] In step 120, the cloud server determines the communication channel corresponding to the target vehicle based on the vehicle identifier ID, and sends the log recall configuration information to the TBOX module of the target vehicle through the vehicle-cloud communication service. After receiving the log recall configuration information, the TBOX first performs data integrity and signature verification operations to confirm that the configuration information has not been tampered with. After successful verification, the TBOX forwards the log recall configuration information to the central domain controller according to the vehicle's internal communication protocol (such as Ethernet, CAN, or Ethernet bus), thereby realizing the task command issuance from the cloud to the vehicle.

[0025] Step 130: Parse the controller identifier ID in the log recall configuration information through the central domain controller, and send a log recall request to the target controller in the target vehicle.

[0026] In step 130, after receiving the log recall configuration information forwarded from the TBOX, the central domain controller performs structured parsing on the configuration information, extracts the controller identifier ID, and determines the corresponding target controller communication address based on a preset controller mapping table. Subsequently, the central domain controller generates a log recall request message according to the parameters defined in the configuration information, such as log type, time range, and upload method, and sends the request to the specified target controller. This process can be implemented through a unified vehicle communication interface to ensure consistency of command format and communication reliability across controllers.

[0027] Step 140: The target controller confirms whether the log recall request is valid.

[0028] In step 140, after receiving the log retrieval request from the central domain controller, the target controller performs a validity check on the request message. The check includes request signature verification, task ID matching, timestamp validity, and parameter integrity detection. If an untrusted request source or missing message fields are detected, the target controller will refuse to execute the task and generate an error log to send back to the central domain controller; if all checks pass, the request is considered valid, preparing for subsequent log upload operations.

[0029] Step 150: If the log retrieval request is valid, request the central domain controller to obtain the URL address of the target server, and upload the target log file to the target server corresponding to the URL address.

[0030] In step 150, the target controller first locates the local log storage path based on the parameter information in the log retrieval request, and then filters and packages the log files according to the log type and time range. After the log files are packaged, the target controller determines whether the file size exceeds a preset threshold; if it exceeds the threshold, a segmented transmission strategy is executed. The target controller then sends a URL address request to the central domain controller, which accesses the cloud server through the vehicle cloud service to obtain the corresponding upload target address. After obtaining the upload URL, the target controller uploads the log files or segmented log data to the target server using secure protocols such as HTTPS. After the upload is complete, the target controller can generate an execution result report containing the task ID, upload status, file size, and timestamp, and feed it back to the central domain controller, thereby achieving closed-loop management of the entire log retrieval task.

[0031] As a further optional embodiment, the step of sending the log recall configuration information to the vehicle's onboard TBOX based on the vehicle identifier ID, so as to forward the log recall configuration information to the target vehicle's central domain controller via the onboard TBOX, specifically includes: The cloud server determines the communication channel of the target vehicle based on the vehicle identification ID; The log recall configuration information is sent to the vehicle TBOX corresponding to the target vehicle via the vehicle cloud service; After receiving the log recall configuration information, the vehicle-mounted TBOX verifies the integrity of the configuration information and forwards the log recall configuration information to the central domain controller of the target vehicle according to the communication protocol.

[0032] In this embodiment, the cloud server can determine the communication channel corresponding to the target vehicle based on the vehicle identification ID using vehicle registration information or the vehicle connection table maintained by the vehicle remote communication management module, thereby ensuring that the log recall task can be accurately sent to the designated vehicle. The communication channel can be an encrypted data link established through a cellular network to ensure the security and reliability of data transmission. Through the vehicle cloud service, the cloud server sends the generated log recall configuration information to the vehicle's corresponding in-vehicle TBOX. The vehicle cloud service plays a role in message relay and security authentication during this process, ensuring that only authorized vehicles can receive the corresponding recall task.

[0033] Upon receiving the log recall configuration information, the vehicle-mounted TBOX first performs integrity and validity checks on the data packet, including verifying the message header, checksum, and signature, to prevent the configuration instructions from being tampered with or damaged during transmission. If the configuration information passes verification, the vehicle-mounted TBOX forwards the log recall configuration information to the vehicle's central domain controller according to the vehicle's internal communication protocol (such as CAN, Ethernet, or FlexRay). Upon receiving this information, the central domain controller can further parse the control parameters and target controller identifier of the log recall task, providing data support for subsequent log recall execution.

[0034] As a further optional embodiment, the step of resolving the controller identifier ID from the log recall configuration information through the central domain controller and sending a log recall request to the target controller in the target vehicle specifically includes: The central domain controller receives log recall configuration information forwarded by the vehicle-mounted TBOX. The log recall configuration information is structured and parsed to extract the controller identifier ID. Based on a preset controller identifier mapping table, determine the target controller communication address corresponding to the controller identifier ID; A log recall request message is generated based on the log recall configuration information and sent to the target controller.

[0035] In this embodiment, the central domain controller, as the core communication and coordination unit within the vehicle, is used to uniformly receive and parse log recall configuration information forwarded from the vehicle-mounted TBOX. Upon receiving the log recall configuration information, the central domain controller first performs structured parsing of the data packet, breaking down the configuration information into fields according to a preset data format (such as JSON or binary TLV structure) to extract key parameters such as controller identifier ID, log type, and time range.

[0036] To achieve precise location of different controllers, the central domain controller pre-stores a controller identifier mapping table. This table defines the correspondence between each controller identifier ID and its corresponding communication address (such as a CAN node address or Ethernet IP address). Based on the extracted controller identifier ID, the central domain controller looks up the corresponding target controller communication address in this mapping table.

[0037] Subsequently, the central domain controller generates a log recall request message conforming to the vehicle's internal communication protocol specifications, based on the log recall configuration information. This request message may include fields such as recall task number, target log type, time range, data compression and upload strategy. After generation, the central domain controller sends the message to the target controller via the vehicle's internal bus (such as CAN bus, Ethernet, or LIN bus) to trigger the corresponding log recall task execution process.

[0038] As a further optional embodiment, the step of uploading the log file to the server corresponding to the URL address specifically includes: Package the target log file according to the log type and log time range defined in the log recall configuration information; Determine whether the size of the packaged log file exceeds a preset threshold. If the log file size exceeds the preset threshold, perform a segmented transmission operation.

[0039] In this embodiment, after receiving a log retrieval request from the central domain controller, the target controller first retrieves the corresponding runtime log file from local storage media (such as flash memory or a separate log cache) according to the log type and time range defined in the log retrieval configuration information. After the retrieval is completed, the target controller packages the selected log file. During the packaging process, compression algorithms (such as ZIP or LZ4) can be used to reduce data size and improve transmission efficiency.

[0040] Subsequently, the target controller calculates the overall size of the packaged log file and compares it with a system-preset threshold. If the log file size does not exceed the threshold, a single-segment transmission request is generated and uploaded directly; if the log file size exceeds the preset threshold, a segmented transmission mechanism is initiated, dividing the log file into several fixed-size data segments (e.g., each segment not exceeding 10MB). During segmented transmission, the target controller can request a unique upload task ID from the cloud server through the central domain controller, which is used to identify the entire log upload session.

[0041] During segmented transmission, the target controller assigns a number and verification mark to each data segment and uploads them sequentially to the target server corresponding to the URL address. At the receiving end, the server can perform integrity reassembly and verification of the log file based on the uploaded task ID and segment number, ensuring error-free transmission and accurate restoration of the log data.

[0042] As a further optional embodiment, after the step of uploading the target log file to the server corresponding to the URL address, the method further includes: After the log file upload is completed, the target controller generates an execution result report containing the log retrieval task ID, upload status, number of log files, upload time and error code, and sends the execution result report to the central domain controller. The execution result report is formatted and verified by the central domain controller, and then uploaded to the cloud server through the vehicle-to-cloud communication channel of the vehicle-mounted TBOX.

[0043] In this embodiment, after the target log file is successfully uploaded to the target server, the target controller automatically generates a log retrieval execution result report so that the cloud server can accurately grasp the execution status of the log retrieval task. This execution result report includes the log retrieval task ID, upload status (e.g., successful, failed, or partially successful), the number of uploaded log files, the upload time for each log file, error codes, and possible error descriptions. Using this information, the cloud server can accurately assess the completion quality of the log retrieval task and execute remedial measures when necessary.

[0044] Subsequently, the target controller sends the generated execution result report to the central domain controller. Upon receiving the report, the central domain controller performs format encapsulation and validity verification on the report content, including field integrity checks, task ID consistency verification, and logical verification of upload status, to ensure that the report data is authentic, complete, and conforms to upload specifications.

[0045] After verification, the central domain controller uploads the encapsulated execution result report to the cloud server via the vehicle-to-cloud communication channel of the vehicle-mounted TBOX. Upon receiving the report, the cloud server can record the task status, analyze the log recall success rate, or trigger subsequent retry and diagnostic processes when an anomaly is detected, thereby achieving closed-loop management and process traceability of log recall tasks in the vehicle-to-cloud system.

[0046] As a further optional embodiment, after the step of formatting and validating the execution result report through the central domain controller and uploading it to the cloud server through the vehicle-to-cloud communication channel of the in-vehicle TBOX, the method further includes: The task ID in the execution result report is verified through the cloud server; If an upload failure or missing data is detected, a retry task is triggered or a retransmission command is sent to the target vehicle.

[0047] In this embodiment, after receiving the execution result report uploaded by the central domain controller via the vehicle-mounted TBOX, the cloud server first verifies the task ID in the report to confirm that the report corresponds one-to-one with the pre-issued log recall task. This verification process includes checking the uniqueness of the task ID, the consistency of the task status, and the reasonableness of the task execution time interval, thereby ensuring that the uploaded result report matches the actual executed task.

[0048] When the cloud server detects an anomaly in the upload result (such as upload failure, incomplete log file count, missing log files, or abnormal error codes), it automatically triggers a retry mechanism. This mechanism can select different handling strategies based on the type of anomaly: if the upload failure is caused by communication interruption, a retry task will be automatically initiated after communication is restored; if the log file is incomplete or missing, the cloud server will send a re-upload instruction to the target vehicle, instructing the vehicle to re-upload the specified log file segment or log data for the corresponding time period.

[0049] Through the above methods, this embodiment can effectively ensure the integrity and reliability of log recall results, avoid interruption of the recall task due to network anomalies or data loss, thereby improving the stability and data consistency of the log recall process in the vehicle cloud system.

[0050] As a further optional embodiment, prior to the step of requesting the URL address of the target server from the central domain controller, the method further includes: The current network connection status is detected through the central domain controller; When the communication status between the vehicle-mounted TBOX and the cloud server is detected to be unstable, the log recall task is paused, and the request to obtain the URL address of the target server is retried after the communication is restored.

[0051] In this embodiment, before requesting the URL address from the target server, the central domain controller first checks the network connection status between the current vehicle and the cloud server. This check includes, but is not limited to, network parameters such as the stability of the communication link, signal strength, latency, and packet loss rate.

[0052] When the central domain controller detects unstable communication between the vehicle-mounted TBOX and the cloud server, such as high latency, abnormal packet loss rate, or temporary disconnection, the system will automatically pause the current log retrieval task to prevent log upload failure or data corruption due to network instability. Once the communication status recovers to a preset stable threshold, the central domain controller will automatically retry requesting the target server's URL address to continue executing the log retrieval task.

[0053] Through the above processing, this embodiment can effectively avoid log upload failures caused by network fluctuations, ensure the reliability and integrity of log retrieval tasks, and improve the stability and operating efficiency of the entire vehicle cloud service system.

[0054] The following describes the vehicle-cloud service-based operation log recall device provided by this invention, such as... Figure 2 As shown, the vehicle cloud service operation log recall device described below and the vehicle cloud service operation log recall method described above can be referred to in correspondence.

[0055] A device for recalling vehicle cloud service operation logs includes: The information generation module 210 is used to generate log recall configuration information through a cloud server according to preset configuration parameters. The log recall configuration information includes vehicle identifier ID and controller identifier ID. The information delivery module 220 is used to deliver the log recall configuration information to the vehicle TBOX of the target vehicle according to the vehicle identification ID, so as to forward the log recall configuration information to the central domain controller of the target vehicle through the vehicle TBOX. Log recall module 230 is used to parse the controller identifier ID in the log recall configuration information through the central domain controller and send a log recall request to the target controller in the target vehicle. The request detection module 240 is used to confirm whether the log recall request is legitimate through the target controller; The log upload module 250 is used to request the URL address of the target server from the central domain controller if the log retrieval request is valid, and upload the target log file to the target server corresponding to the URL address.

[0056] Figure 3An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 3 As shown, the electronic device may include: a processor 310, a communications interface 320, a memory 330, and a communication bus 340, wherein the processor 310, the communications interface 320, and the memory 330 communicate with each other via the communication bus 340. The processor 310 can call logical instructions in the memory 330 to execute a method for recalling vehicle cloud service operation logs, which includes: Log recall configuration information is generated by a cloud server based on preset configuration parameters. The log recall configuration information includes vehicle identifier ID and controller identifier ID. The log recall configuration information is sent to the vehicle's onboard TBOX based on the vehicle identification ID, so that the log recall configuration information can be forwarded to the target vehicle's central domain controller through the onboard TBOX. The central domain controller parses the controller identifier ID in the log recall configuration information and sends a log recall request to the target controller in the target vehicle. The target controller verifies whether the log recall request is valid. If the log retrieval request is valid, the central domain controller is requested to obtain the URL address of the target server, and the target log file is uploaded to the target server corresponding to the URL address.

[0057] Furthermore, the logical instructions in the aforementioned memory 330 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, essentially, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0058] On the other hand, the present invention also provides a computer program product, the computer program product comprising a computer program, which can be stored on a non-transitory computer-readable storage medium, and when the computer program is executed by a processor, the computer is able to execute the vehicle cloud service operation log recall method provided by the above methods, the method comprising: Log recall configuration information is generated by a cloud server based on preset configuration parameters. The log recall configuration information includes vehicle identifier ID and controller identifier ID. The log recall configuration information is sent to the vehicle's onboard TBOX based on the vehicle identification ID, so that the log recall configuration information can be forwarded to the target vehicle's central domain controller through the onboard TBOX. The central domain controller parses the controller identifier ID in the log recall configuration information and sends a log recall request to the target controller in the target vehicle. The target controller verifies whether the log recall request is valid. If the log retrieval request is valid, the central domain controller is requested to obtain the URL address of the target server, and the target log file is uploaded to the target server corresponding to the URL address.

[0059] In another aspect, the present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, is implemented to perform the vehicle-cloud service operation log recall method provided by the above methods, the method comprising: Log recall configuration information is generated by a cloud server based on preset configuration parameters. The log recall configuration information includes vehicle identifier ID and controller identifier ID. The log recall configuration information is sent to the vehicle's onboard TBOX based on the vehicle identification ID, so that the log recall configuration information can be forwarded to the target vehicle's central domain controller through the onboard TBOX. The central domain controller parses the controller identifier ID in the log recall configuration information and sends a log recall request to the target controller in the target vehicle. The target controller verifies whether the log recall request is valid. If the log retrieval request is valid, the central domain controller is requested to obtain the URL address of the target server, and the target log file is uploaded to the target server corresponding to the URL address.

[0060] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0061] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0062] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for recalling based on a vehicle cloud service operation log, characterized in that, The application comprises the following steps: A cloud server generates log recall configuration information according to preset configuration parameters, wherein the log recall configuration information comprises a vehicle identification ID and a controller identification ID; The log recall configuration information is sent to a vehicle-mounted TBOX of a target vehicle according to the vehicle identification ID, so that the log recall configuration information is forwarded to a central domain controller of the target vehicle through the vehicle-mounted TBOX; The controller identification ID in the log recall configuration information is parsed by the central domain controller, and a log recall request is sent to a target controller in the target vehicle; Whether the log recall request is legal is confirmed by the target controller; If the log recall request is legal, the URL address of a target server is requested from the central domain controller, and a target log file is uploaded to the target server corresponding to the URL address. 2.The method of claim 1, wherein, The step of sending the log recall configuration information to the vehicle-mounted TBOX of the target vehicle according to the vehicle identification ID, so that the log recall configuration information is forwarded to the central domain controller of the target vehicle through the vehicle-mounted TBOX, specifically comprises the following steps: The cloud server determines a communication channel of the target vehicle based on the vehicle identification ID; The log recall configuration information is sent to the vehicle-mounted TBOX of the target vehicle through a vehicle cloud service; The integrity of the configuration information is verified by the vehicle-mounted TBOX after receiving the log recall configuration information, and the log recall configuration information is forwarded to the central domain controller of the target vehicle according to a communication protocol. 3.The method of claim 1, wherein, The step of parsing the controller identification ID in the log recall configuration information by the central domain controller and sending a log recall request to the target controller in the target vehicle, specifically comprises the following steps: The log recall configuration information forwarded by the vehicle-mounted TBOX is received by the central domain controller; The log recall configuration information is structurally parsed to extract the controller identification ID; A target controller communication address corresponding to the controller identification ID is determined based on a preset controller identification mapping relationship table; A log recall request message is generated according to the log recall configuration information and is sent to the target controller. 4.The method of claim 1, wherein, The step of uploading the log file to the server corresponding to the URL address, specifically comprises the following steps: The target log file is packaged according to the log type and log time range defined in the log recall configuration information; Whether the size of the packaged log file exceeds a preset threshold is judged, and when the size of the log file exceeds the preset threshold, a segmented transmission operation is performed. 5.The method of claim 1, wherein, After the step of uploading the target log file to the server corresponding to the URL address, the following steps are further included: After completing the log file uploading, an execution result report containing a log recall task ID, an uploading state, a log file quantity, an uploading time and an error code is generated by the target controller, and the execution result report is sent to the central domain controller; The execution result report is format-encapsulated and verified by the central domain controller, and is uploaded to the cloud server through the vehicle cloud communication channel of the vehicle-mounted TBOX. 6.The method of claim 5, wherein, After the step of encapsulating and checking the execution result report by the central domain controller and uploading to the cloud server through the vehicle cloud communication channel of the vehicle TBOX, further comprising: Verifying the task ID in the execution result report by the cloud server; If uploading fails or data is missing, triggering a retry task or issuing a supplementary transmission instruction to the target vehicle. 7.The method of claim 1, wherein, Before the step of requesting the central domain controller to obtain the URL address of the target server, further comprising: Detecting the current network connection state by the central domain controller; When detecting that the communication state between the vehicle TBOX and the cloud server is unstable, suspending the log recall task and retrying to request the URL address of the target server after the communication is restored.

8. A device for recalling based on a vehicle cloud service operation log, characterized by, Comprising: An information generation module for generating log recall configuration information according to preset configuration parameters by the cloud server, the log recall configuration information including vehicle identification ID and controller identification ID; An information issuing module for issuing the log recall configuration information to the vehicle TBOX of the target vehicle according to the vehicle identification ID, so as to forward the log recall configuration information to the central domain controller of the target vehicle through the vehicle TBOX; A log recall module for parsing the controller identification ID in the log recall configuration information by the central domain controller and issuing a log recall request to the target controller in the target vehicle; A request detection module for confirming whether the log recall request is legal by the target controller; A log uploading module for requesting the central domain controller to obtain the URL address of the target server if the log recall request is legal, and uploading the target log file to the target server corresponding to the URL address.

9. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, The processor executes the program to realize the log recall method based on vehicle cloud service running according to any one of claims 1 to 7. 10.A non-transitory computer-readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by the processor to realize the log recall method based on vehicle cloud service running according to any one of claims 1 to 7.

Images