Driving log uploading method, device and equipment and computer readable storage medium

Abstract

This application discloses a method, apparatus, device, and computer-readable storage medium for uploading driving logs, relating to the field of intelligent driving technology. The method includes: acquiring vehicle characteristic information; generating an updated configuration file and a current configuration file based on the vehicle characteristic information; determining log data based on the current configuration file and the updated configuration file; uploading the log data and determining the upload status to send a task list; and performing after-sales problem analysis based on the task list. This application determines log data by generating an updated configuration file and a current configuration file and uploading it to the cloud, generating a header file to identify the upload status, and obtaining a task list to view and download the uploaded log data. This allows for rapid after-sales problem analysis without affecting the operation of intelligent driving functions, saving bandwidth and space. The upload can be resumed using a breakpoint resume method when the upload conditions are met again.

Description

Technical Field

[0001] This application relates to the field of intelligent driving technology, and in particular to driving log uploading methods, devices, equipment, and computer-readable storage media. Background Technology

[0002] With the rapid development of intelligent driving technology, the automotive industry has undergone a technological revolution. While providing convenience, intelligent driving systems also bring new challenges, especially in handling after-sales issues. When problems arise with an intelligent driving system, log data, as a crucial source of information recording system operating status, user behavior, and abnormal events, is essential for quickly locating and resolving after-sales problems. Therefore, timely and accurate acquisition of vehicle-side log data is an indispensable task.

[0003] Currently, existing methods for acquiring vehicle log data primarily rely on remote configuration. This involves receiving configuration commands from the monitoring platform, parsing the configuration information, and sending this information to the electronic control unit (ECU) to configure and store the logs according to the specified settings. Another existing approach involves automatically monitoring the vehicle's current mode upon startup, recording data corresponding to that mode, and then storing and uploading this data to the cloud in a tiered manner.

[0004] However, current practices require configuration operations through the monitoring platform every time log data is needed, a cumbersome and inefficient process. Furthermore, if the previously issued log configuration information is insufficient to support after-sales problem analysis, it is usually necessary to reproduce the problem in a real vehicle to obtain data, which is not only time-consuming but also difficult to implement. Another existing approach records large amounts of data in autonomous driving mode and uploads it in real time, consuming significant bandwidth and cloud storage space. Moreover, real-time data uploads also consume on-vehicle computing resources, impacting vehicle performance. Therefore, how to conveniently upload driving logs has become an urgent problem to be solved.

[0005] The above content is only used to help understand the technical solution of this application and does not represent an admission that the above content is prior art. Summary of the Invention

[0006] The main objective of this application is to provide a method, apparatus, device, and computer-readable storage medium for uploading driving logs, aiming to solve the technical problem of how to conveniently upload driving logs.

[0007] To achieve the above objectives, this application proposes a method for uploading driving logs, the method comprising:

[0008] Obtain vehicle characteristic information, and generate an updated configuration file and a current configuration file based on the vehicle characteristic information;

[0009] Log data is determined based on the current configuration file and the updated configuration file;

[0010] The log data is uploaded to determine the upload status and a task list is generated. After-sales issues are analyzed based on the task list.

[0011] In one embodiment, the step of obtaining vehicle feature information includes:

[0012] Obtain vehicle signature information, vehicle model information, log data type information, and time information;

[0013] Vehicle characteristic information is determined based on the vehicle feature code information, the vehicle model information, and the log data type information.

[0014] In one embodiment, the step of generating an updated configuration file and a current configuration file based on the vehicle feature information includes:

[0015] A feature identifier value is generated based on the vehicle feature code information and time information in the vehicle feature information;

[0016] The updated configuration file and the current configuration file are determined based on the vehicle feature code information, the vehicle model information, the log data type information, the time information, and the feature identifier value.

[0017] In one embodiment, the step of determining the updated configuration file and the current configuration file based on the vehicle feature code information, the vehicle model information, the log data type information, the time information, and the feature identifier value includes:

[0018] The feature identifier value in the updated configuration file is matched with the feature identifier value in the current configuration file to determine the configuration file update status and obtain the matching result;

[0019] Based on the matching results, an empty configuration file or an updated configuration file is sent to the vehicle.

[0020] In one embodiment, after the step of determining the updated configuration file and the current configuration file based on the vehicle feature code information, the vehicle model information, the log data type information, the time information, and the feature identifier value, the method further includes:

[0021] Get the polling list;

[0022] Upload the log data from the update configuration file, create an update task, and add it to the polling list to run.

[0023] In one embodiment, the step of uploading the log data and determining the upload status to send the task list includes:

[0024] Obtain information on the driver's status and network conditions;

[0025] When the manual driving status information indicates that the manual driving status is good and the network condition status information indicates that the network condition is good, the log data is uploaded and the upload status is determined to obtain the upload result.

[0026] A header file is generated to distribute the task list based on the upload results.

[0027] In one embodiment, the step of performing after-sales problem analysis based on the task list further includes:

[0028] Obtain log retrieval instructions and cloud configuration instructions, and determine the distribution status based on the log retrieval instructions;

[0029] Based on the issued status, log data files can be viewed and downloaded, and a task list can be determined based on the URL link corresponding to the cloud configuration command.

[0030] Furthermore, to achieve the above objectives, this application also proposes a driving log uploading device, which includes:

[0031] The acquisition module is used to acquire vehicle feature information and generate an updated configuration file and a current configuration file based on the vehicle feature information;

[0032] The processing module is used to determine log data based on the current configuration file and the updated configuration file;

[0033] The execution module is used to upload the log data, determine the upload status, send a task list, and perform after-sales problem analysis based on the task list.

[0034] In addition, to achieve the above objectives, this application also proposes a driving log uploading device, the device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the driving log uploading method as described above.

[0035] In addition, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the driving log uploading method described above.

[0036] One or more technical solutions proposed in this application have at least the following technical effects:

[0037] This application proposes a method for uploading driving logs, which involves acquiring vehicle characteristic information, generating an updated configuration file and a current configuration file based on the vehicle characteristic information, determining log data based on the current configuration file and the updated configuration file, uploading the log data, determining the upload status, sending a task list, and performing after-sales problem analysis based on the task list. This application obtains vehicle characteristic information, generates updated and current configuration files, determines log data, uploads it to the cloud, generates a header file to identify the upload status, and obtains a task list to view and download the uploaded log data, thereby enabling rapid after-sales problem analysis. The method is simple to operate and improves the efficiency of after-sales problem analysis. Furthermore, file uploads occur when the user exits the intelligent driving function, without affecting the operation of the intelligent driving function. In addition, uploading data during after-sales problem analysis significantly saves upload traffic costs and cloud storage space. The method uses a task list for management on the vehicle side, and comprehensively considers multiple cloud downloads and upload failures, thus resuming uploads when the upload conditions are met again. Attached Figure Description

[0038] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0039] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0040] Figure 1 This is a flowchart illustrating the driving log uploading method of this application in Embodiment 1;

[0041] Figure 2 This is a simplified flowchart illustrating the driving log uploading method of this application;

[0042] Figure 3 This is a flowchart illustrating Embodiment 2 of the driving log uploading method of this application;

[0043] Figure 4 This is a flowchart illustrating Embodiment 3 of the driving log uploading method of this application;

[0044] Figure 5 This is a schematic diagram of the module structure of the driving log uploading device according to an embodiment of this application;

[0045] Figure 6 This is a schematic diagram of the device structure of the hardware operating environment involved in the driving log uploading method in this application embodiment.

[0046] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0047] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.

[0048] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0049] The main solution of this application embodiment is: to obtain vehicle feature information, generate an updated configuration file and a current configuration file based on the vehicle feature information; to determine log data based on the current configuration file and the updated configuration file; to upload the log data to a task list under the upload status, and to perform after-sales problem analysis based on the task list.

[0050] In this embodiment, for ease of description, the vehicle control module will be used as the execution subject in the following description.

[0051] Current technology requires configuration through the monitoring platform every time log data is needed, a cumbersome and inefficient process. Furthermore, if the previously issued log configuration information is insufficient to support after-sales problem analysis, it is usually necessary to reproduce the problem in a real vehicle to obtain data, which is not only time-consuming but also difficult to implement. Another existing approach records a large amount of data in autonomous driving mode and uploads it in real time, which not only consumes a lot of bandwidth but also occupies cloud storage space. In addition, real-time data uploads also consume computing resources on the vehicle, affecting vehicle performance.

[0052] This application provides a solution to obtain vehicle characteristic information, generate an updated configuration file and a current configuration file based on the vehicle characteristic information; determine log data based on the current configuration file and the updated configuration file; upload the log data to a task list based on the upload status, and perform after-sales problem analysis based on the task list.

[0053] As can be seen from the above embodiments, this application obtains vehicle characteristic information, generates updated configuration files and current configuration files, thereby determining log data and uploading it to the cloud, generating header files to identify the upload status, and obtaining a task list to view and download the uploaded log data, thus enabling rapid after-sales problem analysis. The operation is simple and improves the efficiency of after-sales problem analysis. Furthermore, file uploads are performed when the user exits the intelligent driving function, without affecting the operation of the intelligent driving function. In addition, data uploads are performed when there is after-sales problem analysis, which greatly saves upload traffic costs and cloud storage space. The task list is used for management on the vehicle side, taking into account multiple cloud downloads and upload failures, so that the upload can continue using the breakpoint resume method when the upload conditions are met again.

[0054] Based on this, this application provides a method for uploading driving logs, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the driving log uploading method of this application.

[0055] In this embodiment, the driving log uploading method includes steps S10 to S30:

[0056] Step S10: Obtain vehicle feature information, and generate an updated configuration file and a current configuration file based on the vehicle feature information;

[0057] It should be noted that the vehicle feature information reflects the vehicle's configuration attributes and identification details, including vehicle feature code information, vehicle model information, log data type information, and time information.

[0058] It is understandable that, such as Figure 2 As shown, Figure 2 This is a simplified flowchart of the driving log upload method of this application. After the vehicle is powered on, the cloud sends a configuration file and checks whether the vehicle has retrieved the log configuration. If the vehicle has not retrieved the log configuration, the log retrieval ends. Otherwise, the retrieval directory and files in the directory are read, and it is determined whether the vehicle has entered autonomous driving mode. If the vehicle has not entered autonomous driving mode, it waits for one minute and checks again. Otherwise, the log file is uploaded, and it is determined whether all logs have been uploaded. If any log has not been uploaded, the upload continues. Otherwise, the header file is uploaded to the cloud, and the log retrieval ends.

[0059] Additionally, it should be noted that the configuration file is generated based on the vehicle feature information, log data is determined, logs are uploaded, and after-sales problem analysis is performed to ensure the accuracy of the log data and facilitate the maintenance of the intelligent driving system.

[0060] In one embodiment, to facilitate the acquisition of vehicle feature information, an updated configuration file and a current configuration file are generated based on the vehicle feature information. A corresponding information acquisition device, such as an information acquisition module, can be pre-set to acquire vehicle feature information, generate an updated configuration file and a current configuration file based on the vehicle feature information, and store the vehicle feature information in a corresponding storage device. The specific storage method is not limited, as long as it can store the vehicle feature information, such as a storage module or a memory.

[0061] In practical implementation, the information collection device is in a real-time working state or a timed working state, acquiring vehicle feature information in real time or at regular intervals. If the information collection device acquires vehicle feature information at a certain moment, it stores the vehicle feature information in the memory, generates an updated configuration file and a current configuration file based on the vehicle feature information, and performs subsequent processing based on the updated configuration file and the current configuration file.

[0062] For ease of understanding, we will take the acquisition of vehicle feature information as an example, where the information acquisition device is the information acquisition module and the storage device is the memory.

[0063] The information acquisition module obtains vehicle feature code information, which supports multiple vehicles, such as vehicle VIN code; obtains vehicle model information, such as model information, style information and configuration information; obtains log data type information, such as configuration log file; and obtains time information, such as 1 minute. Based on the vehicle feature code information, vehicle model information, log data type information and time information, the module determines vehicle feature information and stores the vehicle feature information in the memory. Subsequent processing is then performed based on the vehicle feature information.

[0064] In one feasible implementation, step S10 may include steps A11 to A12:

[0065] Step A11: Obtain vehicle feature code information, vehicle model information, log data type information, and time information;

[0066] It should be noted that the vehicle feature code information reflects the unique identifier of the vehicle and is used to identify a specific vehicle. The vehicle model information reflects the model configuration of the vehicle, including but not limited to model information, style information, and configuration information, and is used to distinguish different models. The log data type information reflects the characteristics of the types of vehicle log data, including but not limited to vehicle performance data, fault codes, and driving behavior data. The time information reflects the time point of the log data upload status, which is the time from the initial upload status time point to the current time point, and is used to record the generation time of the log data.

[0067] It is understood that the vehicle feature code information can ensure that the log data of each vehicle can be accurately identified and classified. The vehicle model and configuration can be determined based on the vehicle model information, thereby generating a configuration file for a specific vehicle model. The log data type information can ensure the relevance of the log data, making after-sales problem analysis more efficient. The time information marks the generation time of the log data, thereby tracking the time point of the problem when conducting after-sales problem analysis, and locating the cause of the problem more quickly.

[0068] Step A12: Determine vehicle feature information based on the vehicle feature code information, the vehicle model information, and the log data type information.

[0069] It should be noted that by obtaining vehicle feature code information, vehicle model information, log data type information, and time information, vehicle feature information can be obtained, thereby generating updated configuration files and current configuration files. This ensures the consistency and accuracy of log data, making after-sales problem analysis faster and more accurate, reducing the time and cost of problem diagnosis, and helping to take maintenance measures in advance to avoid failures.

[0070] Understandably, the vehicle identification number (VIN) not only serves as a unique identifier for a vehicle but also contains crucial information such as the manufacturer, production year, and model. Decoding the VIN allows for further refinement of the vehicle's specific model and configuration. Model information includes the brand, model, style, and configuration level. Different types of vehicles require different log data types. Log data types also record key data during vehicle operation, such as engine status, mileage, speed, and fault codes. Vehicle characteristic information also includes static vehicle information, covering dynamic log data requirements. This results in a more accurate log recording configuration, ensuring that the recorded data matches the vehicle's actual operating status, aligns with the vehicle's actual needs, avoids recording invalid data, improves data processing efficiency, and reduces fault diagnosis time and costs.

[0071] Step S20: Determine log data based on the current configuration file and the updated configuration file;

[0072] It should be noted that the current configuration file reflects the characteristics of the configuration file stored in the cloud, the updated configuration file reflects the characteristics of the newly generated configuration file, and the log data reflects the characteristics of recording vehicle configuration information.

[0073] Understandably, to facilitate after-sales troubleshooting, log data includes data modules, anomaly information, sensor status, radar status, and abnormal system configuration parameters. The data from the last three parking video recordings, along with related vehicle control CAN data and vehicle body data, can also be classified as a log data type. However, since the last three parking video recordings contain sensitive information such as faces and license plates, they need to be anonymized on the vehicle side and meet regulatory requirements before they can be uploaded to the cloud along with signal data.

[0074] Additionally, it should be noted that the vehicle-side has a fixed storage area and size for storing log data, and it supports storing log data from 38-42 hours of continuous vehicle operation. If the subsequently collected log data exceeds the set storage size, the original collected data will be overwritten using a rollover method. However, storing log data from 38-42 hours of continuous vehicle operation is sufficient for after-sales problem analysis.

[0075] In one embodiment, in order to determine log data based on the current configuration file and the updated configuration file, a processing device, such as a vehicle processing module, can be pre-set in the vehicle. The vehicle processing module will search and read the current configuration file and the updated configuration file, determine the log data based on the current configuration file and the updated configuration file, and perform subsequent processing based on the log data. The specific method of searching and reading is not limited, as long as it can achieve the acquisition of the current configuration file and the updated configuration file, such as a memory, processor, etc.

[0076] In practice, the processing device is in a normally closed state. If at a certain moment the processing device obtains the current configuration file and the updated configuration file, it determines the log data based on the current configuration file and the updated configuration file, and performs subsequent processing based on the log data.

[0077] For ease of understanding, we will use the current configuration file and the updated configuration file as examples. The information collection device is the information collection module, the storage device is the memory, and the processing device is the processing module.

[0078] The information collection module acquires vehicle feature code information, which supports multiple vehicles, such as vehicle VIN codes. It also acquires vehicle model information, such as model, style, and configuration information, log data type information, such as configuration log files, and time information, such as 1 minute. Based on the vehicle feature code information, vehicle model information, log data type information, and time information, it determines vehicle characteristic information and stores it in the memory. After clicking "Deploy" on the operation interface, an updated configuration file is generated and saved to the cloud. The current configuration file is then acquired. Every 3 minutes after the vehicle is powered on, a configuration file update request is sent to the cloud. The cloud compares the current configuration file on the vehicle with the updated configuration file. If they do not match, the updated configuration file is pushed to the vehicle, which saves the updated configuration file and uploads the corresponding log data to the cloud according to the configuration file. If they match, the cloud sends an empty configuration file to the vehicle, and the vehicle does not upload any log data. Subsequent processing is based on this log data.

[0079] Step S30: Upload the log data to the task list under the upload status, and perform after-sales problem analysis based on the task list.

[0080] It should be noted that the task list reflects the characteristics of the log data upload status results.

[0081] Understandably, based on the determined log data, the data is uploaded to the cloud server via the vehicle's communication module. The log data upload includes data compression, encryption, and transmission optimization to ensure data security and transmission efficiency. During the data upload process, the upload status is monitored in real time, including upload progress, speed, and error status, so as to perform timely response operations, such as retrying, pausing, or canceling the upload, thereby generating a task list. The task list includes data priority, analysis requirements, and expected results, thereby guiding after-sales problem analysts to perform subsequent data processing and problem analysis.

[0082] Furthermore, it should be noted that automated uploading and task list generation significantly improve the efficiency of after-sales problem analysis, reduce manual operations and waiting time, and enhance data security by encrypting and monitoring data during the upload process, protecting the privacy of vehicles and users. The generation of task lists allows after-sales problem analysts to allocate resources more rationally, prioritize important and urgent log data, improve the response speed of problem resolution, and accurately obtain upload status and header information, thereby improving the accuracy and reliability of after-sales problem analysis. This, in turn, improves the maintenance and service quality of the entire intelligent driving system, as well as the reliability and user satisfaction of the entire intelligent driving system.

[0083] In one embodiment, in order to upload the log data, determine the upload status, and send a task list, and perform after-sales problem analysis based on the task list, a corresponding execution device, such as a vehicle execution module, can be pre-set in the vehicle to upload the log data, determine the upload status, and send a task list, and perform after-sales problem analysis based on the task list. The specific method of analysis is not limited, as long as it can realize after-sales problem analysis based on the task list, such as a control module, processing module, etc.

[0084] In practice, the execution device is normally closed. If the execution device obtains the task list at a certain moment, it will perform after-sales problem analysis based on the task list.

[0085] For ease of understanding, we will take the acquisition of a task list as an example. The information acquisition device is the information acquisition module, the storage device is the memory, and the execution device is the execution module.

[0086] The information acquisition module obtains vehicle feature code information, vehicle model information, log data type information, and time information. Based on these information, it determines vehicle feature information and stores it in the memory. After clicking "Distribute" on the operation interface, an updated configuration file is generated and saved to the cloud. The current configuration file is then retrieved. Every 3 minutes after the vehicle is powered on, a configuration file update request is sent to the cloud. The cloud compares the current configuration file on the vehicle with the updated configuration file. If they do not match, the updated configuration file is pushed to the vehicle. The vehicle saves the updated configuration file and uploads the corresponding log data according to the configuration file. If the data is consistent with the cloud, the cloud sends an empty configuration file to the vehicle. The vehicle will not upload any log data. It obtains the human driving status information and network condition status information. When the human driving status information indicates that the human driving status is good and the network condition information indicates that the network condition is good, the log data is uploaded and the upload status is judged. The upload result is obtained, and a header file is generated based on the upload result to send a task list. At this time, the cloud can check whether the file upload is successful by detecting whether the header file is in the file uploaded by the vehicle. The cloud can then view and download the log data content uploaded by the vehicle in the sent task list and perform after-sales problem analysis.

[0087] In one feasible implementation, step S30 may include steps B11 to B13:

[0088] Step B11: Obtain manual driving status information and network condition status information;

[0089] It should be noted that the manual driving status information reflects the characteristics of the current vehicle driving behavior status, including the status of the automatic driving assistance function, steering wheel operation status, acceleration status, and braking status. The network condition status information reflects the characteristics of the current network connection status, including signal strength, network latency, bandwidth, and data transmission rate.

[0090] Understandably, vehicle sensors and control modules can collect driving status data, such as steering wheel angle, brake pedal position, and accelerator pedal position, while also detecting the current vehicle network connectivity status, including signal strength, network type, and data transmission rate.

[0091] Additionally, it should be noted that to avoid impacting the vehicle's computing resources when users are using intelligent driving functions, data uploads are only performed when the driver is in a good driving state and the network conditions are good. If the internal signal indicates a driving state that is not AVP, not ANP, not HAVP (Half-High Assist Valet Parking), and the network condition is such that the last upload failure occurred less than 2 minutes prior to the current time, then the network failure status is considered unrecovered. AVP includes APA, HAVP, PAVP, RA, and FA; ANP includes ACC, ICA, and HANP. AVP stands for Automatic Valet Parking, meaning the vehicle can autonomously complete the parking process without the driver being present. APA stands for Automatic Parking Assist, assisting the driver in automatically completing the parking process. HAVP stands for Automated Valet Parking in Home Areas, enabling automatic valet parking in home or private parking lots. PAVP stands for Automated Valet Parking in Personal Areas, allowing for automatic valet parking within personal settings. The system enables automated valet parking in specific areas. RA stands for Remote Automated Parking, which achieves automated parking through remote control. FA stands for Fully Autonomous Driving, where the vehicle can drive completely autonomously without driver intervention. ANP stands for Automatic Navigation Parking, meaning the vehicle can autonomously complete parking based on a navigation system. ACC stands for Adaptive Cruise Control, which automatically adjusts the vehicle speed based on the speed of vehicles ahead to maintain a safe distance. ICA stands for Integrated Cruise Assist, which integrates adaptive cruise control and lane keeping assist functions to automatically control vehicle speed and maintain lane position. HANP stands for Automated Navigation Parking in Home or Private Parking Areas, enabling automated navigation parking in home or private parking lots. HAVP refers to the vehicle's learning and memorization of parking routes during automated parking. Judgment based on manual driving status information and network condition information effectively avoids data loss due to upload failures caused by unstable driving conditions or poor network connectivity.

[0092] Step B12: When the manual driving status information is "manual driving status is good" and the network condition status information is "network condition is good", the log data is uploaded and the upload status is determined to obtain the upload result.

[0093] Understandably, the cloud can select the type of logs to be pulled from the vehicle and supports pulling multiple log data types from multiple vehicles. After the cloud issues a command, it will display the issuance status, which includes issuance in progress, issuance successful, and issuance failed. If the vehicle data is successfully uploaded, the log data file can be viewed and downloaded in the issued task list. At this time, the URL link corresponding to the configuration command issued by the cloud can be sent via SMS, email, etc., thereby realizing the maintenance of log data.

[0094] Step B13: Generate a header file distribution task list based on the upload results.

[0095] Understandably, once the log data is successfully uploaded, a header file will be generated. This header file includes basic information about the log data, such as upload time, data size, and vehicle identifier. The header file can serve as an index for the log data, facilitating subsequent searching and analysis.

[0096] In another feasible implementation, step S10 may include steps C11 to C12:

[0097] Step C11: Obtain the log retrieval command and the cloud configuration command, and determine the distribution status based on the log retrieval command;

[0098] It should be noted that the log retrieval command reflects the characteristics of the operation required to retrieve log data from the cloud, and the cloud configuration command reflects the characteristics of the operation required to retrieve the current configuration file from the cloud.

[0099] Understandably, currently, log retrieval commands can be issued multiple times in the cloud, and the vehicle can respond to the configuration file and upload data as long as it is powered on and not in intelligent driving mode. There are very few cases where log file retrieval fails. However, considering that remotely waking up the vehicle has strict limitations and may pose a risk to the user's vehicle safety, such as battery depletion and other issues that may cause user complaints, further consideration is needed for remotely waking up the vehicle to make vehicle-side requests and upload data.

[0100] Step C12: Based on the issued status, view and download the log data file, and determine the task list based on the URL link corresponding to the cloud configuration command.

[0101] Understandably, based on the issued status, the system accesses the log data file stored on the vehicle side. The log data file includes vehicle performance data, fault codes, and driving behavior data. Once the integrity of the log data file is confirmed, it can be downloaded to the cloud server. The download process may include data encryption and compression to ensure the security and efficiency of data transmission. Based on cloud configuration instructions, a task list is generated. The task list may include data priority, analysis requirements, and expected results.

[0102] The driving log uploading method proposed in this embodiment obtains vehicle characteristic information, generates an updated configuration file and a current configuration file based on the vehicle characteristic information, determines log data based on the current configuration file and the updated configuration file, uploads the log data, determines the upload status, sends a task list, and performs after-sales problem analysis based on the task list. This solves the technical problem of how to conveniently upload driving logs. This application obtains vehicle characteristic information, generates an updated configuration file and a current configuration file, determines log data and uploads it to the cloud, generates a header file to identify the upload status, and obtains a task list to view and download the uploaded log data, thereby quickly performing after-sales problem analysis. The operation is simple and improves the efficiency of after-sales problem analysis. Furthermore, file uploads occur when the user exits the intelligent driving function, without affecting the operation of the intelligent driving function. In addition, data uploads during after-sales problem analysis greatly save upload traffic costs and cloud storage space. The task list is used for management on the vehicle side, and considering multiple cloud downloads and upload failures, the upload can be resumed using a breakpoint resume method when the upload conditions are met again.

[0103] Based on the first embodiment of this application, in the second embodiment of this application, the same or similar content as the first embodiment can be referred to the above description, and will not be repeated hereafter.

[0104] In this embodiment, refer to Figure 3 , Figure 3 This is a flowchart illustrating the second embodiment of the driving log uploading method of this application. Step S10 specifically includes steps S11 to S12:

[0105] Step S11: Generate a feature identifier value based on the vehicle feature code information and time information in the vehicle feature information;

[0106] It should be noted that the feature identifier value reflects the unique identifier of the configuration file and is an MD5 value. As a widely used feature identifier value, the feature identifier value provides an efficient way to verify the integrity of the data, thereby ensuring the consistency and security of the vehicle configuration file.

[0107] It is understood that the feature identifier value can take the collected vehicle feature code information and time information as input, and generate a 128-bit hash value, namely the MD5 value, which is also the feature identifier value, through the MD5 algorithm. The generated feature identifier value will be stored together with the vehicle's configuration file and transmitted when the vehicle communicates with the cloud. The cloud can verify the consistency and integrity of the configuration file by comparing the feature identifier value.

[0108] Additionally, it should be noted that each time the cloud generates a configuration file, it randomly generates an MD5 value based on the vehicle's identifier. When the vehicle initiates a request every 3 minutes, it includes the vehicle identifier, MD5 value, and other information. The cloud determines whether to update the vehicle's configuration file by comparing the MD5 values. If the MD5 values ​​of the vehicle and the cloud are the same, the vehicle's configuration file is not updated, and an empty configuration file is sent. If the MD5 values ​​of the vehicle and the cloud are different, the cloud sends the latest configuration file to the vehicle.

[0109] Step S12: Determine the update configuration file and the current configuration file based on the vehicle feature code information, the vehicle model information, the log data type information, the time information, and the feature identifier value.

[0110] It is understood that the aforementioned feature identification value can ensure that the vehicle configuration file is not tampered with or damaged during the generation and transmission process. Any unauthorized modifications will be quickly detected by comparing the feature identification value, preventing malicious software or hacker attacks, protecting the security and privacy of the vehicle configuration file, and making the management of the vehicle configuration file more efficient. The cloud can quickly compare the feature identification value to determine whether the vehicle configuration file needs to be updated, thereby reducing unnecessary data transmission and storage.

[0111] In one feasible implementation, step S10 may include steps D11 to D12:

[0112] Step D11: Match the feature identifier value in the updated configuration file with the feature identifier value in the current configuration file to determine the configuration file update status and obtain the matching result;

[0113] It should be noted that the matching results reflect the characteristics that distinguish the updated configuration file from the current configuration file.

[0114] It is understood that feature identifier values ​​are extracted based on the updated configuration file and the current configuration file, and the feature identifier values ​​are matched. Based on the matching result, it is determined whether the configuration file needs to be updated. If the two feature identifier values ​​are the same, it indicates that the current configuration file is already up-to-date and does not need to be updated. If they are different, the latest configuration file needs to be obtained from the cloud. The matching result can be recorded in the system log, so as to track the update history of the configuration file and the configuration status of the vehicle.

[0115] Step D12: Based on the matching result, send an empty configuration file to the vehicle or send an updated configuration file to the vehicle.

[0116] Understandably, by accurately matching feature identifier values, the system ensures that the configuration file used by the vehicle is consistent with the cloud, avoids abnormal vehicle functions caused by configuration errors, prevents unauthorized configuration files from being applied to the vehicle, and enhances system security.

[0117] The driving log uploading method proposed in this embodiment generates a feature identifier value based on the vehicle feature code information and time information in the vehicle feature information; and determines the updated configuration file and the current configuration file based on the vehicle feature code information, the vehicle model information, the log data type information, the time information, and the feature identifier value. This solves the technical problem of how to determine the configuration file status based on the feature identifier value to determine the updated and current configuration files. Through automated feature identifier value matching and status judgment, manual intervention is reduced, improving the efficiency and accuracy of configuration file updates. Furthermore, automated matching and update status judgment reduce vehicle recalls or repairs caused by configuration errors, lowering maintenance costs and improving user satisfaction.

[0118] Based on the first and second embodiments of this application, in the third embodiment of this application, the content that is the same as or similar to that in Embodiments 1 and 2 described above can be referred to the above description and will not be repeated hereafter. Based on this, please refer to... Figure 4 , Figure 4 This is a flowchart illustrating the driving log uploading method in Embodiment 3 of this application. After step S12, the driving log uploading method further includes steps S121 to S122:

[0119] Step S121: Obtain the polling list;

[0120] It should be noted that the polling list reflects the characteristics of recording and tracking pending upload tasks.

[0121] It is understood that the polling list represents the ability to manage upload tasks, can track all pending and ongoing upload tasks, and the order of tasks in the polling list reflects the priority and processing order of tasks, ensuring that important or urgent tasks can be processed first.

[0122] Additionally, it should be noted that after receiving the latest configuration file from the cloud, the vehicle will upload and create a task based on the corresponding log data in the configuration file and add it to the polling list. The task will be run after the upload conditions are met, thus avoiding the cloud repeatedly sending configuration files, which would cause frequent responses from the vehicle and affect its performance. The polling list is dynamically updated and can reflect the latest status of the uploaded tasks in real time, including newly added tasks, completed tasks, and tasks that need to be retried. The operation mechanism of the polling list reflects the system's response speed and processing efficiency to the uploaded tasks, ensuring that log data can be uploaded and processed in a timely manner.

[0123] Step S122: Upload the log data in the update configuration file, create an update task, and add it to the polling list for execution.

[0124] Understandably, once the log data is successfully uploaded, the system will create an update task based on the upload result. The update task includes the log data size, upload time, and vehicle characteristic information. The update task will be added to a polling list. Each task in the polling list will be processed according to a predetermined order or priority. The polling list will be checked periodically, and the tasks in the list will be processed. Tasks that have been uploaded will be marked, and failed tasks will be retried.

[0125] Additionally, it should be noted that, considering the large size of the log data files stored on the vehicle side, a packet compression method is usually adopted during the upload process to reduce the pressure on the cloud interface. Each compressed packet is treated as an upload task. If the upload fails due to network conditions or vehicle power failure, the upload can continue from the list of failed upload tasks when the upload conditions are met again.

[0126] The driving log uploading method proposed in this embodiment obtains a polling list; uploads the log data from the update configuration file; creates an update task; and adds it to the polling list for execution. This solves the technical problem of how to upload log data. Through polling list management, it efficiently tracks and processes all log data to be uploaded, ensuring the continuity and integrity of data uploads. It can also dynamically adjust the priority and order of upload tasks based on real-time conditions, thereby optimizing the utilization of vehicle and cloud resources. During the upload process, log data is encrypted and compressed, enhancing data transmission security and protecting the privacy of vehicles and users. It can also quickly respond to changes in upload tasks, promptly handling upload failures or retries, improving the response speed of upload tasks, reducing manual intervention, lowering operational complexity and error rates, and facilitating rapid problem location by after-sales problem analysts, thus improving the efficiency and accuracy of problem analysis.

[0127] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the driving log uploading method of this application. Any simple modifications based on this technical concept are within the protection scope of this application.

[0128] This application also provides a driving log uploading device, please refer to... Figure 5 The driving log uploading device includes:

[0129] The acquisition module 10 is used to acquire vehicle feature information and generate an updated configuration file and a current configuration file based on the vehicle feature information.

[0130] Processing module 20 is used to determine log data based on the current configuration file and the updated configuration file;

[0131] The execution module 30 is used to upload the log data to determine the upload status and send a task list, and to perform after-sales problem analysis based on the task list.

[0132] The driving log uploading device provided in this application, employing the driving log uploading method in the above embodiments, can solve the technical problem of how to conveniently upload driving logs. Compared with the prior art, the beneficial effects of the driving log uploading device provided in this application are the same as those of the driving log uploading method provided in the above embodiments, and other technical features in the driving log uploading device are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0133] This application provides a driving log uploading device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, which are executed by the at least one processor to enable the at least one processor to perform the driving log uploading method in Embodiment 1 above.

[0134] The following is for reference. Figure 6 The diagram illustrates a structural schematic of a driving log uploading device suitable for implementing embodiments of this application. The driving log uploading device in this application may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital radio receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Description), PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 6 The driving log upload device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0135] like Figure 6As shown, the driving log uploading device may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1003 into a random access memory (RAM) 1004. The RAM 1004 also stores various programs and data required for the operation of the driving log uploading device. The processing unit 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to the I / O interface 1006: input devices 1007 including, for example, a touchscreen, touchpad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; storage devices 1003 including, for example, magnetic tape, hard disk, etc.; and communication devices 1009. Communication device 1009 allows the driving log upload device to communicate wirelessly or wiredly with other devices to exchange data. Although driving log upload devices with various systems are shown in the figures, it should be understood that implementation or possession of all the systems shown is not required. More or fewer systems may be implemented alternatively.

[0136] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from ROM 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0137] The driving log uploading device provided in this application, employing the driving log uploading method in the above embodiments, can solve the technical problem of how to conveniently upload driving logs. Compared with the prior art, the beneficial effects of the driving log uploading device provided in this application are the same as those of the driving log uploading method provided in the above embodiments, and other technical features in this driving log uploading device are the same as those disclosed in the previous embodiment method, and will not be repeated here.

[0138] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0139] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0140] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, the computer-readable program instructions being used to execute the driving log uploading method in the above embodiments.

[0141] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0142] The aforementioned computer-readable storage medium may be included in the driving log upload device; or it may exist independently and not be installed in the driving log upload device.

[0143] The aforementioned computer-readable storage medium carries one or more programs. When the aforementioned one or more programs are executed by the driving log upload device, the driving log upload device causes the following: to acquire vehicle characteristic information; to generate an updated configuration file and a current configuration file based on the vehicle characteristic information; to determine log data based on the current configuration file and the updated configuration file; to upload the log data to a task list based on the upload status; and to perform after-sales problem analysis based on the task list.

[0144] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a Local Area Network (LAN) or a Wide Area Network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0145] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0146] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0147] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described driving log uploading method, thereby solving the technical problem of how to conveniently upload driving logs. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the driving log uploading method provided in the above embodiments, and will not be repeated here.

[0148] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.

Claims

1. A method for uploading driving logs, characterized in that, The method includes: Obtain vehicle characteristic information, and generate an updated configuration file and a current configuration file based on the vehicle characteristic information; Log data is determined based on the current configuration file and the updated configuration file; The log data is uploaded to determine the upload status and a task list is sent. After-sales issues are analyzed based on the task list. The step of uploading the log data, determining the upload status, and sending the task list includes: Acquire manual driving status information and network condition status information. When the driving status in the internal signal is non-automatic valet parking, non-automatic navigation parking, or non-home area automatic navigation parking, and the network condition status in the internal signal is less than a preset time from the last upload failure time point to the current time point, then update the network condition status information to network failure status not recovered. When the manual driving status information indicates that the manual driving status is good and the network condition status information indicates that the network condition is good, the log data is uploaded and the upload status is determined to obtain the upload result. Based on the upload results, a header file is generated to distribute the task list. The header file includes the upload timestamp, vehicle identifier, and data verification value. Before the step of performing after-sales problem analysis based on the task list, the following is also included: Obtain log retrieval instructions and cloud configuration instructions, and determine the distribution status based on the log retrieval instructions. The log retrieval instructions are the operation instructions required to retrieve cloud log data, and the cloud configuration instructions are the operation instructions required to retrieve the current cloud configuration file. Based on the issued status, log data files can be viewed and downloaded, and a task list can be determined based on the URL link corresponding to the cloud configuration command.

2. The method as described in claim 1, characterized in that, The steps for obtaining vehicle feature information include: Obtain vehicle signature information, vehicle model information, log data type information, and time information; Vehicle characteristic information is determined based on the vehicle feature code information, the vehicle model information, and the log data type information.

3. The method as described in claim 2, characterized in that, The steps of generating the updated configuration file and the current configuration file based on the vehicle feature information include: A feature identifier value is generated based on the vehicle feature code information and time information in the vehicle feature information; The updated configuration file and the current configuration file are determined based on the vehicle feature code information, the vehicle model information, the log data type information, the time information, and the feature identifier value.

4. The method as described in claim 3, characterized in that, The step of determining the updated configuration file and the current configuration file based on the vehicle feature code information, the vehicle model information, the log data type information, the time information, and the feature identifier value includes: The feature identifier value in the updated configuration file is matched with the feature identifier value in the current configuration file to determine the configuration file update status and obtain the matching result; Based on the matching results, an empty configuration file or an updated configuration file is sent to the vehicle.

5. The method as described in claim 3, characterized in that, The step of determining the updated configuration file and the current configuration file based on the vehicle feature code information, the vehicle model information, the log data type information, the time information, and the feature identifier value further includes: Get the polling list; Upload the log data from the update configuration file, create an update task, and add it to the polling list to run.

6. A driving log uploading device, characterized in that, The device includes: The acquisition module is used to acquire vehicle feature information and generate an updated configuration file and a current configuration file based on the vehicle feature information; The processing module is used to determine log data based on the current configuration file and the updated configuration file; The execution module is used to upload the log data, determine the upload status, send a task list, and perform after-sales problem analysis based on the task list. The execution module is also used to obtain manual driving status information and network condition status information. When the driving status in the internal signal is non-automatic valet parking, non-automatic navigation parking or non-home area automatic navigation parking and the network condition status in the internal signal is less than a preset time from the last upload failure time point to the current time point, the network condition status information is updated to network failure status not recovered. When the manual driving status information indicates that the manual driving status is good and the network condition status information indicates that the network condition is good, the log data is uploaded and the upload status is determined to obtain the upload result. Based on the upload results, a header file is generated to distribute the task list. The header file includes the upload timestamp, vehicle identifier, and data verification value. The execution module is also used to obtain log retrieval instructions and cloud configuration instructions, and determine the distribution status based on the log retrieval instructions. The log retrieval instructions are operation instructions required to retrieve cloud log data, and the cloud configuration instructions are operation instructions required to retrieve the current cloud configuration file. Based on the issued status, log data files can be viewed and downloaded, and a task list can be determined based on the URL link corresponding to the cloud configuration command.

7. A driving log uploading device, characterized in that, The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the driving log uploading method as described in any one of claims 1 to 5.

8. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, it implements the steps of the driving log uploading method as described in any one of claims 1 to 5.

Images