Log collection method and device, vehicle and storage medium

Abstract

The invention relates to the technical field of vehicle management, in particular to a log collection method and device, a vehicle and a storage medium. The method comprises the steps of judging whether a log collection request is received or not; if a log acquisition request is received, determining a to-be-packaged log based on the log acquisition request, sending the log acquisition request to a fault diagnosis instrument through a gateway of the vehicle, and acquiring a target log file according to the to-be-packaged log through the fault diagnosis instrument; and obtaining the target uploading address, and uploading the target log file according to the target uploading address. Therefore, by providing a new method for remotely checking the log, the problems that in the prior art, the time period is long, time and labor are consumed, the real-time performance is poor, and the overall failure rate of the log is high due to the fact that an acquisition path is complex are solved, vehicle end log local acquisition and cloud end whole vehicle log acquisition are supported, vehicle and cloud integrated log retrieval and analysis are achieved, and the efficiency is improved. And the user experience is improved.

Description

Technical Field

[0001] The present application relates to the field of vehicle management technology, and in particular to a log collection method, device, vehicle and storage medium. Background Art

[0002] At present, the role that software assumes or plays in vehicles is becoming more and more important. From the initial "mechanical definition" to "electrical definition", then to "electronic definition" and finally to the current "software definition", software will be deeply involved in the entire life cycle of the vehicle. The log data generated by the software running on the vehicle will play an important role in the vehicle's overall safety, after-sales service, and continuous optimization of the software.

[0003] In the related art, traditional vehicle logs require technicians to go to the vehicle site or 4S shop maintenance personnel to read the vehicle logs through the diagnostic instrument OBD (On-Board Diagnostics) port of the faulty vehicle; there are also methods to collect the entire vehicle log through the vehicle computer or T-BOX (Telematics BOX, remote vehicle terminal), and then read the logs through the vehicle computer serial port or USB (Universal Serial Bus) port and download and store them, and then transfer them to the file server through email or FTP (File Transfer Protocol, file transfer protocol), and the technical department of the OEM downloads the vehicle logs and then conducts troubleshooting.

[0004] However, this method has a long cycle, is time-consuming and labor-intensive, has poor real-time performance, and the complex collection path leads to a high overall log failure rate, which needs to be solved urgently. Summary of the invention

[0005] The present application provides a log collection method, device, vehicle and storage medium to solve the problems of the prior art, such as long time period, time-consuming and labor-intensive, poor real-time performance, and high overall log failure rate due to complex collection paths. The method supports local acquisition of vehicle-side logs and cloud-based acquisition of vehicle logs, realizes vehicle-cloud integrated log retrieval and analysis, and improves user experience.

[0006] To achieve the above objectives, the first embodiment of the present application proposes a log collection method, comprising the following steps:

[0007] Determine whether a log collection request is received;

[0008] If the log collection request is received, the logs to be packaged are determined based on the log collection request, and the log collection request is sent to the fault diagnosis instrument through the gateway of the vehicle, and the target log file is collected by the fault diagnosis instrument according to the logs to be packaged;

[0009] Obtain a target upload address, and upload the target log file according to the target upload address.

[0010] Through the above-mentioned technical means, based on standardized communication protocols and interfaces, seamless connection and data exchange between different systems are achieved, and vehicle log data is effectively managed and utilized, providing strong support for vehicle manufacturers, maintenance service providers, car owners and other parties.

[0011] According to an embodiment of the present application, before obtaining the target upload address, the method further includes:

[0012] Sending the log collection request to the target server;

[0013] If the verification pass instruction generated by the target server based on the log collection request is not received, the log uploading action is stopped.

[0014] Through the above technical means, sending log collection requests and waiting for the verification instruction of the target server can ensure that only authorized devices and users can perform log collection and upload operations, which significantly improves the security of the system and prevents unauthorized data access and leakage.

[0015] According to an embodiment of the present application, obtaining a target upload address and uploading the target log file according to the target upload address includes:

[0016] Send data upload request to the target server;

[0017] Receiving OBD login information and upload address sent by the target server based on the data upload request;

[0018] The target log file is uploaded to the OBD based on the OBD login information and the upload address.

[0019] By using the above technical means, the dedicated OBD login information and upload address are obtained from the target server, ensuring that the upload operation is targeted at the correct target location and service, avoiding files from being mistakenly uploaded to irrelevant servers or locations, and improving the accuracy and efficiency of file management.

[0020] According to one embodiment of the present application, after uploading the target log file to the OBD based on the OBD login information and the upload address, the method further includes:

[0021] Determine whether the target log file has been uploaded;

[0022] If the target log file is uploaded completely, upload completion information is generated and sent to a preset mobile terminal.

[0023] Through the above technical means, by determining whether the upload is completed and immediately generating an upload completion reminder, the upload result can be fed back to the preset mobile terminal in real time. This instant feedback mechanism helps users to understand the status of file upload in a timely manner and improve user experience.

[0024] According to one embodiment of the present application, when uploading the target log file to the OBD based on the OBD login information and the upload address, it also includes:

[0025] Obtaining the duration of uploading the target log file to the OBD;

[0026] If the duration is longer than a preset duration, an upload failure reminder is generated and sent to a preset mobile terminal.

[0027] Through the above-mentioned technical means, by adding monitoring of the upload duration and failure reminder mechanism, problems in the upload process can be discovered and solved in a timely manner, improving the reliability of the system and user experience.

[0028] According to the log collection method proposed in the embodiment of the present application, when a log collection request is received, the log to be packaged is determined based on the log collection request, and the log collection request is sent to the fault diagnosis instrument through the vehicle's gateway, and the fault diagnosis instrument collects the target log file according to the log to be packaged, obtains the target upload address, and uploads the target log file according to the target upload address. Therefore, by providing a new method for remotely viewing logs, the problems of the prior art, such as long time cycle, time-consuming and labor-intensive, poor real-time performance, and high overall log failure rate due to complex collection paths, are solved, and the local acquisition of vehicle-side logs and the acquisition of vehicle logs in the cloud are supported, so as to realize the log retrieval and analysis of vehicle-cloud integration and improve the user experience.

[0029] To achieve the above-mentioned purpose, a second embodiment of the present application provides a log collection device, including:

[0030] A judgment module, used to judge whether a log collection request is received;

[0031] A processing module, configured to determine the logs to be packaged based on the log collection request when receiving the log collection request, and send the log collection request to the fault diagnosis instrument through the gateway of the vehicle, and collect target log files according to the logs to be packaged through the fault diagnosis instrument;

[0032] The upload module is used to obtain a target upload address and upload the target log file according to the target upload address.

[0033] According to an embodiment of the present application, before obtaining the target upload address, the upload module is further used to:

[0034] Sending the log collection request to the target server;

[0035] If the verification pass instruction generated by the target server based on the log collection request is not received, the log uploading action is stopped.

[0036] According to an embodiment of the present application, the upload module includes:

[0037] A sending unit, used for sending a data upload request to a target server;

[0038] A receiving unit, configured to receive the OBD login information and upload address sent by the target server based on the data upload request;

[0039] The uploading unit is used to upload the target log file to the OBD based on the OBD login information and the upload address.

[0040] According to one embodiment of the present application, after uploading the target log file to the OBD based on the OBD login information and the upload address, the uploading unit is further used to:

[0041] Determine whether the target log file has been uploaded;

[0042] If the target log file is uploaded completely, upload completion information is generated and sent to a preset mobile terminal.

[0043] According to one embodiment of the present application, when uploading the target log file to the OBD based on the OBD login information and the upload address, the uploading unit is further used to:

[0044] Obtaining the duration of uploading the target log file to the OBD;

[0045] If the duration is longer than a preset duration, an upload failure reminder is generated and sent to a preset mobile terminal.

[0046] According to the log collection device proposed in the embodiment of the present application, when receiving a log collection request, the log to be packaged is determined based on the log collection request, and the log collection request is sent to the fault diagnosis instrument through the vehicle's gateway, and the fault diagnosis instrument collects the target log file according to the log to be packaged, obtains the target upload address, and uploads the target log file according to the target upload address. Therefore, by providing a new method for remotely viewing logs, the problems of the prior art, such as long time cycle, time-consuming and labor-intensive, poor real-time performance, and high overall log failure rate due to complex collection paths, are solved, and the local acquisition of vehicle-side logs and the acquisition of vehicle logs in the cloud are supported, so as to realize vehicle-cloud integrated log retrieval and analysis and improve the user experience.

[0047] To achieve the above objectives, the third aspect of the present application proposes a vehicle, comprising: 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 log collection method as described in the above embodiments.

[0048] To achieve the above objectives, the fourth aspect of the present application provides a computer-readable storage medium on which a computer program is stored. The program is executed by a processor to implement the log collection method as described in the above embodiments.

[0049] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0051] Figure 1 A flow chart of a log collection method provided according to an embodiment of the present application;

[0052] Figure 2 A schematic diagram of a log collection process according to an embodiment of the present application;

[0053] Figure 3 A flowchart of another log collection method provided according to an embodiment of the present application;

[0054] Figure 4 A block diagram of a log collection device provided according to an embodiment of the present application;

[0055] Figure 5 It is a schematic diagram of the structure of a vehicle provided according to an embodiment of the present application.

[0056] Description of the accompanying drawings: 10 - log collection device, 100 - judgment module, 200 - processing module, 300 - uploading module, 501 - memory, 502 - processor, 503 - communication interface. DETAILED DESCRIPTION

[0057] The embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limiting the present application.

[0058] The following describes the log collection method, device, vehicle and storage medium proposed according to the embodiments of the present application with reference to the accompanying drawings. First, the log collection method proposed according to the embodiments of the present application will be described with reference to the accompanying drawings.

[0059] Figure 1 This is a flow chart of a log collection method according to an embodiment of the present application.

[0060] like Figure 1 As shown, the log collection method includes the following steps:

[0061] In step S101, it is determined whether a log collection request is received.

[0062] It is understandable that log collection requests are usually activated by triggers (such as users initiating requests through the vehicle system or remote APP), and the system needs to continuously monitor the requests in order to respond in a timely manner.

[0063] Specifically, combined Figure 2 As shown, the overall collection path of the embodiment of the present application includes a gateway (Gate Way, referred to as GW), a T-BOX (Telematics Box, Internet of Vehicles system), an ISP (Internet Service Provider, Internet Service Provider) and an OBD. Therefore, a mobile phone user can initiate a remote log pull request (i.e., a log collection request) through the application or service interface of the TSP (Telematics Service Provider, service provider).

[0064] In step S102, if a log collection request is received, the logs to be packaged are determined based on the log collection request, and the log collection request is sent to the fault diagnosis instrument through the vehicle gateway, and the fault diagnosis instrument collects the target log file according to the logs to be packaged.

[0065] Specifically, after receiving the log collection request, the TSP can interact with the log storage system inside the vehicle and determine the qualified logs to be packaged based on the information in the request (such as time range, module identification, etc.). The vehicle host can receive the log collection request sent by the TSP through the ACP (Advanced Co-Processor), perform preliminary analysis and verification on it to generate verification information, and send the verification information through the ACP. Since the gateway plays the role of a bridge in the vehicle network and is used for communication between different networks or different protocols, the vehicle host can forward the log collection request to the gateway via Ethernet, and the gateway sends the log collection request to the fault diagnosis instrument HDS (Honda Diagnostic System) via Ethernet. After receiving the log collection request, the fault diagnosis instrument can perform specific log collection operations based on the logs to be packaged, that is, read and package the target log file from the vehicle's ECU (Electronic Control Unit) or other log sources.

[0066] In step S103, a target upload address is obtained, and a target log file is uploaded according to the target upload address.

[0067] That is to say, after obtaining the target log file, the file upload address (i.e., the target upload address) can be obtained from the TSP or ISP, and the target log file can be uploaded to the target upload address through a suitable communication protocol (such as HTTPSs (Hypertext Transfer Protocol Secure), FTP, etc.).

[0068] The following describes in detail how to obtain the target upload address and upload the target log file according to the target upload address.

[0069] As a possible implementation method, in some embodiments, a target upload address is obtained, and a target log file is uploaded according to the target upload address, including: sending a data upload request to a target server; receiving OBD login information and an upload address sent by the target server based on the data upload request; and uploading the target log file to OBD based on the OBD login information and the upload address.

[0070] Specifically, an HTTP client is used to construct a POST request (i.e., a data upload request), which includes necessary HTTP headers and authentication information. The data upload request is sent to the corresponding endpoint of the target server, requesting the target server to provide an upload address and OBD login information for authentication. The target server responds to the data upload request, i.e., sends the OBD login information and the upload address. The OBD login information and the upload address are parsed and verified to ensure the validity and availability of the login information and the upload address. After the verification is passed, the OBD login information and the upload address can be used to construct a new POST request to upload the target log file, i.e., send the POST request containing the target log file to the upload address (i.e., OBD) provided by the server.

[0071] Furthermore, in some embodiments, before obtaining the target upload address, it also includes: sending a log collection request to the target server; if the verification instruction generated by the target server based on the log collection request is not received, stopping the log upload action.

[0072] It is understandable that, to avoid unauthorized data access and leakage, or invalid or malicious upload attempts, before uploading the target log file, a log collection request can be sent to the target disk server and wait for the target server's verification instruction.

[0073] Specifically, a log collection request is constructed using an HTTP client, and the log collection request is sent to a designated endpoint of a target server. The target server is waited for and receives a response to the log collection request. The response content is checked to confirm whether a verification instruction is included. The verification instruction may be a specific status code, a specific response message, or a returned verification token. If a verification instruction is included, the target upload address may be obtained and the target log file may be uploaded. Otherwise, if no verification instruction is received, the log upload action is stopped and an error message is displayed to the user.

[0074] Furthermore, in some embodiments, after uploading the target log file to the OBD based on the OBD login information and the upload address, it also includes: determining whether the target log file has been uploaded; if the target log file has been uploaded, generating upload completion information, and sending the upload completion information to a preset mobile terminal.

[0075] That is to say, in the process of uploading log files based on OBD, in addition to basic login information verification and uploading files to the specified address, there is also an added monitoring of the upload status and a notification mechanism after the upload is completed.

[0076] Specifically, after the target log file starts to be uploaded, the system can monitor the upload progress to ensure that the file is uploaded completely. For example, it can determine whether the target log file has been uploaded by detecting the number of bytes of the uploaded file, file verification and / or confirmation information returned by the server. After confirming that the target log file has been uploaded, the system can generate a notification (i.e., upload completion information) containing messages such as upload success, file size, and upload time. The generated upload completion information can be sent to a preset mobile terminal (such as a mobile phone, tablet, etc.) via SMS, push notification or other methods, so that users can quickly understand the file upload status.

[0077] Further, in some embodiments, when uploading the target log file to the OBD based on the OBD login information and the upload address, it also includes:

[0078] Get the duration of uploading the target log file to OBD;

[0079] If the duration is longer than the preset duration, an upload failure reminder is generated and sent to the preset mobile terminal.

[0080] The preset duration may be a duration pre-set by a user, a duration obtained through a limited number of experiments, or a duration obtained through a limited number of computer simulations, and is not specifically limited here.

[0081] That is to say, in the process of uploading the target log file to the OBD based on the OBD login information and the upload address, the system time can be used to record the moment when the file upload starts, and the upload progress and the elapsed time can be continuously monitored during the upload process, and the calculated upload duration can be compared with the preset duration. If the duration is longer than the preset duration, it is considered that there may be a problem or failure in the upload of the target log file. When it is determined that the upload of the target log file fails, an upload failure reminder containing the failure reason (such as timeout), file information, etc. can be generated, and the upload failure reminder can be sent to a preset mobile terminal via SMS, push notification or other means.

[0082] Therefore, by adding monitoring of the upload duration and a failure reminder mechanism, problems in the upload process can be discovered and resolved in a timely manner, improving system reliability and user experience.

[0083] To facilitate those skilled in the art to further understand the log collection method proposed in the embodiment of the present application, Figure 3 For further elaboration.

[0084] like Figure 3As shown, the present application provides a new path for remotely viewing vehicle real-time logs, which can realize real-time viewing of logs on a mobile phone or computer with a short path, support local acquisition of logs on the vehicle side and acquisition of vehicle logs on the cloud, realize vehicle-cloud integrated log retrieval and analysis, and provide support for business development. The log collection method can also include the following steps:

[0085] Step S301, the mobile phone TSP remotely requests to pull remote logs through TSP remote distribution instructions.

[0086] Step S302: The host requests the TSP instruction to be uploaded to the TSP via the ACP.

[0087] Step S303: TSP generates verification information and sends it through ACP.

[0088] Step S304: the host forwards the instruction to the gateway via Ethernet.

[0089] Step S305: the gateway transmits the instruction to the fault diagnosis instrument HDS via Ethernet.

[0090] Step S306, the fault diagnosis instrument completes log file packaging or satisfies data, and obtains a file upload address based on the verification information.

[0091] Step S307, the data upload request HTTPS is handed over to the TSP to generate upload information, vehicle automatic diagnostic system OBD login information and upload address.

[0092] Step S308: The log file is uploaded to the OBD via HTTPS.

[0093] According to the log collection method proposed in the embodiment of the present application, when a log collection request is received, the log to be packaged is determined based on the log collection request, and the log collection request is sent to the fault diagnosis instrument through the vehicle's gateway, and the fault diagnosis instrument collects the target log file according to the log to be packaged, obtains the target upload address, and uploads the target log file according to the target upload address. Therefore, by providing a new method for remotely viewing logs, the problems of the prior art, such as long time cycle, time-consuming and labor-intensive, poor real-time performance, and high overall log failure rate due to complex collection paths, are solved, and the local acquisition of vehicle-side logs and the acquisition of vehicle logs in the cloud are supported, so as to realize the log retrieval and analysis of vehicle-cloud integration and improve the user experience.

[0094] Next, the log collection device proposed according to the embodiment of the present application is described with reference to the accompanying drawings.

[0095] Figure 4 It is a block diagram of a log collection device according to an embodiment of the present application.

[0096] like Figure 4As shown, the log collection device 10 includes: a judgment module 100 , a processing module 200 and an uploading module 300 .

[0097] The determination module 100 is used to determine whether a log collection request has been received;

[0098] The processing module 200 is used to determine the logs to be packaged based on the log collection request when receiving the log collection request, and send the log collection request to the fault diagnosis instrument through the gateway of the vehicle, and collect the target log file according to the logs to be packaged through the fault diagnosis instrument;

[0099] The upload module 300 is used to obtain a target upload address and upload a target log file according to the target upload address.

[0100] Furthermore, in some embodiments, before obtaining the target upload address, the upload module 300 is further configured to:

[0101] Send log collection request to the target server;

[0102] If the verification instruction generated by the target server based on the log collection request is not received, the log upload action is stopped.

[0103] Furthermore, in some embodiments, the upload module 300 includes:

[0104] A sending unit, used for sending a data upload request to a target server;

[0105] A receiving unit, used for receiving OBD login information and an upload address sent by a target server based on a data upload request;

[0106] The upload unit is used to upload the target log file to the OBD based on the OBD login information and the upload address.

[0107] Further, in some embodiments, after uploading the target log file to the OBD based on the OBD login information and the upload address, the uploading unit is further used to:

[0108] Determine whether the target log file has been uploaded;

[0109] If the target log file is uploaded, an upload completion message is generated and sent to a preset mobile terminal.

[0110] Further, in some embodiments, when uploading the target log file to the OBD based on the OBD login information and the upload address, the uploading unit is further used to:

[0111] Get the duration of uploading the target log file to OBD;

[0112] If the duration is longer than the preset duration, an upload failure reminder is generated and sent to the preset mobile terminal.

[0113] It should be noted that the above explanation of the log collection method embodiment is also applicable to the log collection device of this embodiment, and will not be repeated here.

[0114] According to the log collection device proposed in the embodiment of the present application, when receiving a log collection request, the log to be packaged is determined based on the log collection request, and the log collection request is sent to the fault diagnosis instrument through the vehicle's gateway, and the fault diagnosis instrument collects the target log file according to the log to be packaged, obtains the target upload address, and uploads the target log file according to the target upload address. Therefore, by providing a new method for remotely viewing logs, the problems of the prior art, such as long time cycle, time-consuming and labor-intensive, poor real-time performance, and high overall log failure rate due to complex collection paths, are solved, and the local acquisition of vehicle-side logs and the acquisition of vehicle logs in the cloud are supported, so as to realize vehicle-cloud integrated log retrieval and analysis and improve the user experience.

[0115] Figure 5 A schematic diagram of the structure of a vehicle provided in an embodiment of the present application. The vehicle may include:

[0116] A memory 501 , a processor 502 , and a computer program stored in the memory 501 and executable on the processor 502 .

[0117] When the processor 502 executes the program, the log collection method provided in the above embodiment is implemented.

[0118] Furthermore, the vehicle also includes:

[0119] The communication interface 503 is used for communication between the memory 501 and the processor 502 .

[0120] The memory 501 is used to store computer programs that can be executed on the processor 502 .

[0121] The memory 501 may include a high-speed RAM (Random Access Memory) memory, and may also include a non-volatile memory, such as at least one disk memory.

[0122] If the memory 501, the processor 502 and the communication interface 503 are implemented independently, the communication interface 503, the memory 501 and the processor 502 can be connected to each other through a bus and communicate with each other. The bus can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 5 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0123] Optionally, in a specific implementation, if the memory 501, the processor 502 and the communication interface 503 are integrated on a chip, the memory 501, the processor 502 and the communication interface 503 can communicate with each other through an internal interface.

[0124] The processor 502 may be a CPU (Central Processing Unit), or an ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement the embodiments of the present application.

[0125] An embodiment of the present application also provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the above log collection method is implemented.

[0126] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In the description of this application, the meaning of "plurality" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0127] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms are not necessarily directed to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0128] Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limitations on the present application. Ordinary technicians in this field can change, modify, replace and modify the above embodiments within the scope of the present application.

Claims

1. A log collection method, characterized in that: The following steps are involved: Determine whether a log collection request is received; If the log collection request is received, the logs to be packaged are determined based on the log collection request, and the log collection request is sent to the fault diagnosis instrument through the gateway of the vehicle, and the target log file is collected by the fault diagnosis instrument according to the logs to be packaged; Obtain a target upload address, and upload the target log file according to the target upload address.

2. The method according to claim 1, characterized in that Before obtaining the target upload address, it also includes: Sending the log collection request to the target server; If the verification pass instruction generated by the target server based on the log collection request is not received, the log uploading action is stopped.

3. The method according to claim 1, characterized in that The obtaining of the target upload address and uploading the target log file according to the target upload address includes: Send data upload request to the target server; Receiving OBD login information and upload address sent by the target server based on the data upload request; The target log file is uploaded to the OBD based on the OBD login information and the upload address.

4. The method according to claim 3, characterized in that After uploading the target log file to the OBD based on the OBD login information and the upload address, the method further includes: Determine whether the target log file has been uploaded; If the target log file is uploaded completely, upload completion information is generated and sent to a preset mobile terminal.

5. The method according to claim 3, characterized in that: When uploading the target log file to the OBD based on the OBD login information and the upload address, it also includes: Obtaining the duration of uploading the target log file to the OBD; If the duration is longer than a preset duration, an upload failure reminder is generated and sent to a preset mobile terminal.

6. A log collection device, characterized in that: include: A judgment module, used to judge whether a log collection request is received; A processing module, configured to determine the logs to be packaged based on the log collection request when receiving the log collection request, and send the log collection request to the fault diagnosis instrument through the gateway of the vehicle, and collect target log files according to the logs to be packaged through the fault diagnosis instrument; The upload module is used to obtain a target upload address and upload the target log file according to the target upload address.

7. The device according to claim 6, characterized in that Before obtaining the target upload address, the upload module is further used to: Sending the log collection request to the target server; If the verification pass instruction generated by the target server based on the log collection request is not received, the log uploading action is stopped.

8. The device according to claim 6, characterized in that The upload module comprises: A sending unit, used for sending a data upload request to a target server; A receiving unit, configured to receive the OBD login information and upload address sent by the target server based on the data upload request; The uploading unit is used to upload the target log file to the OBD based on the OBD login information and the upload address.

9. A vehicle, characterized in that: include: 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 log collection method according to any one of claims 1 to 5.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: The program is executed by a processor to implement the log collection method as described in any one of claims 1 to 5.

Images