Driving log uploading method, device and equipment and computer readable storage medium
By obtaining vehicle characteristic information to generate configuration files and determining log data, and uploading data based on manual driving status and network conditions, the problem of cumbersome driving log data acquisition and uploading processes in the intelligent driving system is solved, and efficient and resource-saving data uploading is achieved. and analysis.
Patent Information
- Application Number
- CN202411460202.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-18
- Publication Date
- 2025-01-24
- Estimated Expiration
- 2044-10-18
AI Technical Summary
The prior art is cumbersome and inefficient in the intelligent driving system. The real-time upload of data consumes a lot of traffic and storage space, affecting vehicle performance.
By obtaining vehicle characteristic information, generate updated configuration files and current configuration files, determine log data, and upload data when the manual driving status is good and the network conditions are good, and generate header files and task lists to identify the upload status and manage data.
The fast and simple upload of driving log data has been achieved, the efficiency of the analysis of after -sales problems is improved, the flow costs and cloud storage space are saved, and the task list management is adopted at the end of the vehicle end to support the renewal of the breakpoints, which improves the maintenance and service of the system. quality.
Smart Images

Figure CN119363581A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of intelligent driving technology, and in particular to a driving log uploading method, device, equipment and computer-readable storage medium. Background Art
[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 the handling of after-sales problems. When problems occur in intelligent driving systems, log data, as an important source of information for recording system operating status, user behavior, and abnormal events, is crucial for quickly locating and solving after-sales problems. Therefore, timely and accurate acquisition of vehicle-side log data is a must.
[0003] At present, the existing practice of obtaining vehicle log data mainly relies on remote configuration methods, which receive configuration instructions from the monitoring platform, parse the configuration information, and send the information to the electronic control unit, so that it can configure and store logs according to the configuration information. Another existing practice is to automatically monitor the current mode of the vehicle after the vehicle is started, record the data corresponding to the vehicle mode, and then store the data in a hierarchical manner and upload it to the cloud.
[0004] However, the existing practice requires configuration operations through the monitoring platform every time log data is needed, which is cumbersome and inefficient. In addition, if the previously issued log configuration information is not sufficient to support after-sales problem analysis, it is usually necessary to reproduce the problem on the actual vehicle to obtain data, which is not only time-consuming but also difficult to achieve. Another existing practice is to record a large amount of data in the autonomous driving mode and upload it in real time, which not only consumes a lot of traffic, but also occupies cloud storage space. In addition, uploading data in real time will also occupy the computing power resources on the vehicle side, affecting vehicle performance. Therefore, how to conveniently upload driving logs has become an urgent problem to be solved.
[0005] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention
[0006] The main purpose of this application is to provide a driving log uploading method, device, equipment and computer-readable storage medium, aiming to solve the technical problem of how to conveniently upload a driving log.
[0007] To achieve the above purpose, the present application proposes a driving log uploading method, the method comprising:
[0008] Acquire vehicle characteristic information, and generate an updated configuration file and a current configuration file based on the vehicle characteristic information;
[0009] determining log data based on the current configuration file and the updated configuration file;
[0010] The log data is uploaded and a task list is issued according to the upload status, and after-sales problem analysis is performed based on the task list.
[0011] In one embodiment, the step of obtaining vehicle characteristic information includes:
[0012] Obtain vehicle feature code information, vehicle model information, log data type information and time information;
[0013] The vehicle characteristic information is determined based on the vehicle characteristic 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 characteristic information includes:
[0015] Generate a feature identification value based on the vehicle feature code information and time information in the vehicle feature information;
[0016] An update configuration file and a 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 identification value.
[0017] In one embodiment, the step of determining 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 identification value includes:
[0018] Matching the feature identification value in the updated configuration file with the feature identification value in the current configuration file to determine the configuration file update status and obtain a matching result;
[0019] Based on the matching result, an empty configuration file is sent to the vehicle end or an updated configuration file is sent to the vehicle end.
[0020] In one embodiment, after the step of determining to update the 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 identification value, the step further includes:
[0021] Get the poll list;
[0022] Upload the log data in the update configuration file, create an update task and add it to the polling list for execution.
[0023] In one embodiment, the step of uploading the log data and determining the upload status and sending a task list comprises:
[0024] Obtaining manual driving status information and network condition status information;
[0025] When the manual driving state information indicates that the manual driving state is good and the network condition state information indicates that the network condition is good, uploading the log data, determining the upload state, and obtaining the upload result;
[0026] A header file sending task list is generated based on the upload result.
[0027] In one embodiment, before the step of performing after-sales problem analysis based on the task list, the step further includes:
[0028] Obtaining log pull instructions and cloud configuration instructions, and determining a delivery status based on the log pull instructions;
[0029] The log data file is viewed and downloaded based on the sending status, and a task list is determined based on the website link corresponding to the cloud configuration instruction.
[0030] In addition, to achieve the above purpose, the present application also proposes a driving log upload device, the driving log upload device comprising:
[0031] An acquisition module, used for acquiring vehicle characteristic information, and generating an updated configuration file and a current configuration file based on the vehicle characteristic information;
[0032] a processing module, configured 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 and determine the upload status to issue a task list, and perform after-sales problem analysis based on the task list.
[0034] In addition, to achieve the above-mentioned purpose, the present application also proposes a driving log uploading device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the driving log uploading method described above.
[0035] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by the processor, the steps of the driving log uploading method described above are implemented.
[0036] One or more technical solutions proposed in this application have at least the following technical effects:
[0037] The present application proposes a driving log upload method, which obtains vehicle feature information, generates an update configuration file and a current configuration file based on the vehicle feature information; determines log data based on the current configuration file and the update configuration file; uploads the log data and determines the upload status to send a task list, and performs after-sales problem analysis based on the task list. The present application obtains vehicle feature information, generates an update configuration file and a current configuration file, thereby determining log data and uploading it to the cloud, generates a header file to identify the upload status, obtains a task list to view and download the uploaded log data, and thus quickly performs after-sales problem analysis. The operation is simple and improves the efficiency of after-sales problems. When the user exits the smart driving function, the file is uploaded without affecting the operation of the smart driving function. In addition, when there is an after-sales problem analysis, data is uploaded, which greatly saves the upload traffic cost and cloud storage space, and is managed in the form of a task list on the vehicle side, taking into account multiple cloud-based issuances and upload failures, etc., so that the breakpoint resume method is used to continue uploading when the upload conditions are met next time. BRIEF DESCRIPTION OF THE DRAWINGS
[0038] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0039] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0040] Figure 1 A flowchart of the first embodiment of the driving log upload method of the present application is provided;
[0041] Figure 2 This is a brief flowchart of the driving log upload method for this application;
[0042] Figure 3 A flowchart of the second embodiment of the driving log upload method of this application is provided;
[0043] Figure 4 A flowchart of the third embodiment of the driving log upload method of this application is provided;
[0044] Figure 5 This is a schematic diagram of the module structure of the driving log uploading device according to an embodiment of the present 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 the embodiment of the present application.
[0046] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION
[0047] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.
[0048] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.
[0049] The main solution of the embodiment of the present application is: obtaining vehicle feature information, generating an update configuration file and a current configuration file based on the vehicle feature information; determining log data based on the current configuration file and the update configuration file; uploading the log data and determining the upload status to issue a task list, and performing after-sales problem analysis based on the task list.
[0050] In this embodiment, for the convenience of description, the following description is made by taking identification of a vehicle control module as the execution subject.
[0051] Since the existing technology requires configuration operations through the monitoring platform every time log data is needed, the process is cumbersome and inefficient. In addition, if the previously issued log configuration information is not sufficient to support after-sales problem analysis, it is usually necessary to reproduce the problem on the actual vehicle to obtain data, which is not only time-consuming but also difficult to achieve. Another existing approach is to record a large amount of data in the autonomous driving mode and upload it in real time, which not only consumes a lot of traffic, but also occupies cloud storage space. In addition, uploading data in real time will also occupy the computing power resources on the vehicle side, affecting vehicle performance.
[0052] The present application provides a solution, which includes obtaining vehicle feature information, generating an updated configuration file and a current configuration file based on the vehicle feature information; determining log data based on the current configuration file and the updated configuration file; uploading the log data and determining an upload status to issue a task list, and performing after-sales problem analysis based on the task list.
[0053] It can be seen from the above embodiments that the present application obtains vehicle characteristic information, generates an update configuration file and a current configuration file, thereby determining the log data and uploading 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, so as to quickly perform after-sales problem analysis. The operation is simple and improves the efficiency of after-sales problems. When the user exits the smart driving function, the file is uploaded without affecting the operation of the smart driving function. In addition, data is uploaded when there is an after-sales problem analysis, which greatly saves the upload traffic fee and cloud storage space, and is managed in the form of a task list on the vehicle side, taking into account multiple cloud-based downloads and upload failures, so that the next time the upload conditions are met, the breakpoint resume method is used to continue uploading.
[0054] Based on this, the embodiment of the present application provides a method for uploading a driving log, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the driving log uploading method of the present application.
[0055] In this embodiment, the driving log uploading method includes steps S10 to S30:
[0056] Step S10, acquiring vehicle characteristic information, and generating an updated configuration file and a current configuration file based on the vehicle characteristic information;
[0057] It should be noted that the vehicle characteristic information reflects the configuration attributes and identification details of the vehicle, including vehicle characteristic code information, vehicle model information, log data type information and time information.
[0058] It is understandable that if Figure 2 As shown, Figure 2 This is a brief flowchart of the driving log uploading method of this application. After the vehicle is powered on, the cloud sends a configuration file to determine whether the vehicle has pulled the log configuration. If the vehicle has not pulled the log configuration, the log pulling is completed. Otherwise, read the pulling directory and files in the directory to determine whether the vehicle has entered automatic driving. If the vehicle has not entered automatic driving, wait for one minute and judge again. Otherwise, upload the log file to determine whether all logs have been uploaded. If there are any logs that have not been uploaded, continue to upload. Otherwise, upload the header file to the cloud and the log pulling is completed.
[0059] In addition, it should be noted that, based on the vehicle characteristic information, a configuration file is generated, log data is determined, logs are uploaded, and after-sales problem analysis is performed, thereby ensuring the accuracy of the log data and facilitating the maintenance of the intelligent driving system.
[0060] In one embodiment, in order to facilitate the acquisition of vehicle characteristic information and generate an updated configuration file and a current configuration file based on the vehicle characteristic information, a corresponding information collection device, such as an information collection module, can be pre-set to acquire vehicle characteristic information, generate an updated configuration file and a current configuration file based on the vehicle characteristic information, and store the vehicle characteristic information in a corresponding storage device, wherein the specific storage method is not limited as long as the vehicle characteristic information can be stored, such as a storage module, a memory, etc.
[0061] During specific implementation, the information collection device is in a real-time working state or a scheduled working state, and obtains vehicle characteristic information real-timely or regularly. If at a certain moment, the information collection device obtains the vehicle characteristic information, the vehicle characteristic information is stored in a memory, and an updated configuration file and a current configuration file are generated based on the vehicle characteristic information, and subsequent processing is performed based on the updated configuration file and the current configuration file.
[0062] For ease of understanding, the acquisition of vehicle characteristic information is taken as an example for explanation, wherein the information collection device is an information collection module, and the storage device is a 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 vehicle model information, style information and configuration information, obtains log data type information, such as configuration log file, obtains time information, such as 1 minute, determines vehicle feature information based on the vehicle feature code information, vehicle model information, log data type information and time information, stores the vehicle feature information in a memory, and performs subsequent processing based on the vehicle feature information.
[0064] In a feasible implementation, step S10 may include steps A11 to A12:
[0065] Step A11, obtaining 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 characteristics of the vehicle's unique identification and is used to identify a specific vehicle. The vehicle model information reflects the characteristics of the vehicle's model configuration, including but not limited to vehicle model information, style information and configuration information, which is used to distinguish different vehicle models. The log data type information reflects the characteristics of the type 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 length of time from the time point of the initial upload status to the current time point, and is used to record the generation time of the log data.
[0067] It can be understood that based on the vehicle feature code information, it can be ensured that the log data of each vehicle can be accurately identified and classified, based on the vehicle model information, the model and configuration of the vehicle can be determined, so as to generate a configuration file for a specific vehicle model, based on the log data type information, the relevance of the log data can be ensured, making after-sales problem analysis more efficient, and based on the time information, the generation time of the log data is marked, so as to track the time point when the problem occurs during after-sales problem analysis, and locate the cause of the problem more quickly.
[0068] Step A12: determining 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, ensuring 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] It is understandable that the vehicle feature code not only serves as the unique identification of the vehicle, but also contains key information such as the manufacturer, production year, and model of the vehicle. By decoding the vehicle feature code, the specific model and configuration of the vehicle can be further refined. The model information also includes the brand, model, style, and configuration level of the vehicle. Different types of vehicles require different types of log data to be recorded. The log data type information also records key data during vehicle operation, such as engine status, mileage, speed, and fault codes. Vehicle feature information also includes static information of the vehicle, covering dynamic log data requirements, thereby generating a more accurate log recording configuration to ensure that the recorded data is consistent with the actual operating status of the vehicle, in line with the actual needs of the vehicle, avoiding the recording of invalid data, improving data processing efficiency, and reducing the time and cost of fault diagnosis.
[0071] Step S20, determining 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 saved by the cloud itself, the updated configuration file reflects the characteristics of the newly generated configuration file, and the log data reflects the characteristics of the recorded vehicle configuration information.
[0073] It is understandable that in order to facilitate after-sales problem troubleshooting, the log data includes data modules, abnormal information, sensor status, radar status, and system configuration parameter abnormal information. The video data of the last three parking attempts and related vehicle control CAN data, body data, etc. can also be used as a type of log data. Since the video data of the last three parking attempts contain sensitive information such as faces and license plates, they need to be desensitized on the vehicle side and meet regulatory requirements before they can be uploaded online to the cloud with signal data.
[0074] In addition, it should be noted that the vehicle side has a fixed storage area and size for storing log data, and supports at least 38h-42h of continuous operation log data of the vehicle side. If the subsequently collected log data exceeds the set storage size, the original collected data will be overwritten by rolling deletion. However, 38h-42h of continuous operation log data stored on the vehicle side is sufficient for after-sales problem analysis.
[0075] In one embodiment, in order to determine the log data based on the current configuration file and the updated configuration file, a processing device, such as a vehicle processing module, may be pre-set in the vehicle. The vehicle processing module searches for and reads the current configuration file and the updated configuration file, determines the log data based on the current configuration file and the updated configuration file, and performs subsequent processing based on the log data. The specific method of searching and reading is not limited, as long as it is possible to obtain the current configuration file and the updated configuration file, such as a memory, a processor, etc.
[0076] In a specific implementation, the processing device is in a normally closed state. If at a certain moment, after 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, the current configuration file and the updated configuration file are taken as examples for explanation, wherein 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 acquisition module obtains vehicle feature code information, which supports multiple vehicles, such as vehicle VIN code, obtains vehicle model information, such as vehicle model information, style information and configuration information, obtains log data type information, such as configuration log file, obtains time information, such as 1 minute, determines vehicle feature information based on the vehicle feature code information, vehicle model information, log data type information and time information, and stores the vehicle feature information in a memory. After clicking "Send" on the operation interface, an update configuration file will be generated and saved to the cloud, and then the current configuration file will be obtained. After the vehicle side is powered on, a configuration file update request will be initiated to the cloud every 3 minutes. The cloud will compare the current configuration file of the vehicle side with the update configuration file for consistency; if not, the update configuration file will be pushed to the vehicle side, the vehicle side will save the update configuration file, and upload the corresponding log data to the cloud according to the configuration file; if consistent, the cloud will send an empty configuration file to the vehicle side, the vehicle side will not upload any log data, and subsequent processing will be performed based on the log data.
[0079] Step S30, uploading the log data and judging the upload status to issue a task list, and performing 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] It can be understood that according to the determined log data, the data is uploaded to the cloud server through 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 conditions, 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, so as to guide after-sales problem analysts to perform subsequent data processing and problem analysis.
[0082] In addition, it should be noted that through automated uploading and task list generation, the efficiency of after-sales problem analysis has been significantly improved, manual operations and waiting time have been reduced, and data is encrypted and monitored during the upload process to enhance data security and protect the privacy of vehicles and users. The generation of task lists enables after-sales problem analysts to allocate resources more reasonably, prioritize important and urgent log data, improve the response speed of problem solving, and accurately obtain upload status and header file information, thereby improving the accuracy and reliability of after-sales problem analysis, thereby improving the maintenance and service quality of the entire intelligent driving system, and improving the reliability and user satisfaction of the entire intelligent driving system.
[0083] In one embodiment, in order to upload the log data and determine the uploaded status and send a task list, and perform after-sales problem analysis based on the task list, a corresponding execution device can be pre-set in the vehicle, such as a vehicle execution module, to upload the log data and determine the uploaded status and send a task list, and perform after-sales problem analysis based on the task list, wherein the specific method of analysis is not limited as long as it can be implemented to perform after-sales problem analysis based on the task list, such as a control module, a processing module, etc.
[0084] During specific implementation, the execution device is in a normally closed state. If at a certain moment, the execution device obtains the task list, after-sales problem analysis is performed based on the task list.
[0085] For ease of understanding, the task list is obtained as an example for explanation, wherein the information collection device is the information collection 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, determines the vehicle feature information based on the vehicle feature code information, vehicle model information, log data type information and time information, and stores the vehicle feature information in the memory. After clicking "Send" on the operation interface, an update configuration file will be generated and saved to the cloud, and then the current configuration file will be obtained. After the vehicle is powered on, a configuration file update request will be sent to the cloud every 3 minutes. The cloud will compare the current configuration file of the vehicle with the update configuration file to see if they are consistent; if they are inconsistent, the update configuration file will be pushed to the vehicle, and the vehicle will save the update configuration file and upload the corresponding log data according to the configuration file. The data is uploaded to the cloud; if they are consistent, the cloud will send an empty configuration file to the vehicle side, and the vehicle side will not upload any log data, and obtain manual driving status information and network condition status information. 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 judged to obtain the upload result, and a header file sending task list is generated based on the upload result. At this time, the cloud can determine whether the vehicle-side file upload is successful by detecting whether the header file is in the file uploaded by the vehicle side, so as to view and download the log data content uploaded by the vehicle side in the sent task list, and conduct after-sales problem analysis.
[0087] In a feasible implementation, step S30 may include steps B11 to B13:
[0088] Step B11, obtaining 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 automatic driving assistance function status, 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 delay, bandwidth and data transmission rate.
[0090] It is understandable that the vehicle's sensors and control modules can collect driving status data, such as steering wheel angle, brake pedal position and accelerator pedal position, while detecting the current vehicle network connection status, including signal strength, network type and data transmission rate.
[0091] In addition, it should be noted that in order not to affect the occupation of vehicle-side computing resources when users use the intelligent driving function, data upload is only performed when the manual driving state is good and the network conditions are good. When the driving state in the internal signal is non-AVP and the driving state is non-ANP and the driving state is non-HAVP learning route state and the network condition state is that the last upload failure time point is less than 2 minutes from the current time point, it is judged that the network failure state has not been restored. The AVP includes APA, HAVP, PAVP, RA and FA. The ANP includes ACC, ICA and HANP. The AVP is automatic valet parking, which means that the vehicle can complete the parking process autonomously without the driver in the car. The APA is automatic parking assistance, which helps the driver to automatically complete the parking process. The HAVP is automatic valet parking in the home area, which realizes automatic valet parking in the home or private parking lot. The PAVP is automatic valet parking in the personal area, which is set in the personal setting. The RA is remote automatic parking, which realizes automatic parking through remote control. The FA is fully automatic driving, and the vehicle can drive completely autonomously without driver intervention. The ANP is automatic navigation parking, which means that the vehicle can complete parking autonomously according to the navigation system. The ACC is adaptive cruise control, which automatically adjusts the vehicle speed according to the speed of the vehicle in front to maintain a safe distance. The ICA is integrated cruise assist, which integrates adaptive cruise control and lane keeping assist functions to realize automatic control of vehicle speed and lane keeping. The HANP is home area automatic navigation parking, which realizes automatic navigation parking in home or private parking lots. The HAVP learning route status is the state of the vehicle learning and memorizing the parking route during the automatic parking process. Judging by the manual driving status information and the network condition status information can effectively avoid the loss of log data due to upload failure when the driving conditions are unstable or the network connection is poor.
[0092] Step B12, when the manual driving state information indicates that the manual driving state is good and the network condition state information indicates that the network condition is good, uploading the log data and determining the upload state to obtain the upload result;
[0093] It can be understood that the type of log pulled from the vehicle side can be selected in the cloud, and it supports pulling multiple log data types from multiple vehicles. After the cloud sends the instruction, the sending status will be displayed. The sending status includes sending in progress, sending successful and sending failed. If the vehicle-side data is uploaded successfully, the log data file can be viewed and downloaded in the sent task list. At this time, the URL link corresponding to the configuration instruction sent by the cloud can be sent via SMS, email, etc., thereby realizing the maintenance of log data.
[0094] Step B13, generating a header file sending task list based on the upload result.
[0095] It is understandable that once the log data is successfully uploaded, a header file will be generated, which includes basic information of the log data, such as upload time, data size and vehicle identification. The header file can be used as an index of the log data to facilitate subsequent search and analysis.
[0096] In another feasible implementation, step S10 may include steps C11 to C12:
[0097] Step C11, obtaining a log pull instruction and a cloud configuration instruction, and determining a delivery status based on the log pull instruction;
[0098] It should be noted that the log pulling instruction reflects the characteristics of the operation required to pull the cloud log data, and the cloud configuration instruction reflects the characteristics of the operation required to pull the current configuration file on the cloud.
[0099] It is understandable that log pulling instructions can be issued multiple times on the cloud at present. The vehicle side can respond to the configuration file and upload data when it is powered on and not in intelligent driving state. Failure to pull log files rarely occurs. In addition, due to strict restrictions on remotely waking up vehicles, it may pose a hidden danger to the user's vehicle safety, and may cause problems such as battery power feeding and cause user complaints. Therefore, further consideration is needed for remotely waking up vehicles to make vehicle-side requests and upload data.
[0100] Step C12, checking and downloading the log data file based on the sending status, and determining the task list based on the website link corresponding to the cloud configuration instruction.
[0101] It can be understood that according to the sending status, the log data file stored on the vehicle side is accessed, and the log data file includes vehicle performance data, fault codes and driving behavior data. Once the integrity of the log data file is confirmed, the log data file 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 the cloud configuration instructions, a task list is generated, and the task list may include data priority, analysis requirements and expected results.
[0102] The driving log upload method proposed in this embodiment obtains vehicle feature information, generates an update configuration file and a current configuration file based on the vehicle feature information; determines log data based on the current configuration file and the update configuration file; uploads the log data and determines the upload status to issue a task list, and performs after-sales problem analysis based on the task list. The technical problem of how to conveniently upload the driving log is solved. The application obtains vehicle feature information, generates an update configuration file and a current configuration file, thereby determining the log data and uploading it to the cloud, generates a header file to identify the upload status, obtains a task list to view and download the uploaded log data, and thus quickly performs after-sales problem analysis. The operation is simple and improves the efficiency of after-sales problems. When the user exits the smart driving function, the file is uploaded without affecting the operation of the smart driving function. In addition, when there is an after-sales problem analysis, data is uploaded, which greatly saves the upload traffic fee and cloud storage space, and is managed in the form of a task list on the vehicle side, comprehensively considering the multiple downlinks and upload failures in the cloud, so that the breakpoint resume method is used to continue uploading when the upload conditions are met next time.
[0103] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can be referred to the above introduction and will not be repeated later.
[0104] In this embodiment, refer to Figure 3 , Figure 3 This is a flow chart of the second embodiment of the driving log upload method of this application, where step S10 specifically includes steps S11 to S12:
[0105] Step S11, generating a feature identification value based on the vehicle feature code information and time information in the vehicle feature information;
[0106] It should be noted that the feature identification value reflects the unique identification of the configuration file, which is an MD5 value. As a widely used feature identification value, the feature identification 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 can be understood that the feature identification value can take the collected vehicle feature code information and time information as input, and generate a 128-bit hash value, i.e., the MD5 value, which is also the feature identification value, through the MD5 algorithm. The generated feature identification 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 identification value.
[0108] In addition, it should be noted that each time the cloud generates a configuration file, it will randomly generate an MD5 value based on the vehicle feature code. When the vehicle initiates a request every 3 minutes, it will attach the vehicle feature code, MD5 value and other information. The cloud determines whether to update the vehicle's configuration file by comparing whether the MD5 values are consistent; if the MD5 values of the vehicle and the cloud are consistent, the vehicle's configuration file will not be updated and an empty configuration file will be sent; if the MD5 values of the vehicle and the cloud are inconsistent, the cloud will send the latest configuration file to the vehicle.
[0109] Step S12, determining an update configuration file and a 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 identification value.
[0110] It can be understood that the feature identification value can ensure that the vehicle configuration file is not tampered with or damaged during the generation and transmission process, and any unauthorized modification will be quickly discovered in the comparison of the feature identification value, preventing malware 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 decide whether the vehicle configuration file needs to be updated by quickly comparing the feature identification value, thereby reducing unnecessary data transmission and storage.
[0111] In a feasible implementation, step S10 may include steps D11 to D12:
[0112] Step D11, matching the feature identification value in the updated configuration file with the feature identification value in the current configuration file to determine the configuration file update status and obtain a matching result;
[0113] It should be noted that the matching result reflects the difference between the updated configuration file and the current configuration file.
[0114] It can be understood that the feature identification value is extracted according to the updated configuration file and the current configuration file, and the feature identification value is matched, and whether the configuration file needs to be updated is determined based on the matching result. If the two feature identification values are the same, it indicates that the current configuration file is already the latest and does not need to be updated. If they are different, it is necessary to obtain the latest configuration file from the cloud. The matching result can be recorded in the system log, so that the update history of the configuration file and the configuration status of the vehicle can be tracked.
[0115] Step D12: Send an empty configuration file to the vehicle side or send an updated configuration file to the vehicle side based on the matching result.
[0116] It can be understood that by accurately matching the feature identification values, the configuration file used by the vehicle is ensured to be consistent with the cloud, thus avoiding vehicle malfunctions due to configuration errors and preventing unauthorized configuration files from being applied to the vehicle, thereby enhancing the security of the system.
[0117] The driving log upload method proposed in this embodiment generates a feature identification 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 identification value. The technical problem of how to determine the updated configuration file and the current configuration file by judging the configuration file status based on the feature identification value is solved. Through the automated feature identification value matching and status judgment, manual intervention is reduced, the efficiency and accuracy of the configuration file update are improved, and the automated matching and update status judgment reduce the vehicle recall or repair caused by configuration errors, reduce maintenance costs and improve user satisfaction.
[0118] Based on the first and second embodiments of the present application, in the third embodiment of the present application, the same or similar contents as those in the first and second embodiments can be referred to the above description, and will not be described in detail later. Figure 4 , Figure 4 This is a flow chart of the third embodiment of the driving log uploading method of the present application. After step S12, the driving log uploading method further includes steps S121 to S122:
[0119] Step S121, obtaining a polling list;
[0120] It should be noted that the polling list reflects the characteristics of recording and tracking pending upload tasks.
[0121] It is understandable that the polling list represents the management capability of upload tasks, and can track all pending and ongoing upload tasks, while 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] In addition, it should be noted that after the vehicle receives the latest configuration file sent from the cloud, it will create a task based on the corresponding log data in the configuration file and add it to the polling list, and run the task after the upload conditions are met, thereby avoiding the cloud from repeatedly sending configuration files, causing frequent responses from the vehicle and affecting vehicle 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 operating 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, uploading the log data in the update configuration file, creating an update task and adding it to the polling list for execution.
[0124] It can be understood that once the log data is successfully uploaded, the system will create an update task based on the upload results. The update task includes the log data size, upload time and vehicle feature information. The update task will be added to the polling list. Each task in the polling list will be processed according to a predetermined order or priority. The polling list will be checked regularly, and the tasks in the list will be processed. Tasks that have completed upload will be marked and failed tasks will be retried.
[0125] In addition, it should be noted that considering that the log data files stored on the vehicle side are large, in order to reduce the pressure on the cloud interface during the upload process, the method of sub-packet compression is usually adopted, and each compressed package is regarded as an upload task. When the upload fails due to network conditions or vehicle power failure, the upload can be continued from the failed upload task list when the upload conditions are met next time.
[0126] The driving log upload method proposed in this embodiment obtains a polling list; uploads the log data in the update configuration file, creates an update task and adds it to the polling list for execution. The technical problem of how to upload log data is solved. Through the management of the polling list, all log data to be uploaded can be efficiently tracked and processed to ensure the continuity and integrity of data upload. The priority and order of upload tasks can be dynamically adjusted according to real-time conditions, thereby optimizing the resource utilization of vehicles and the cloud. During the upload process, log data is encrypted and compressed to enhance the security of data transmission, protect the privacy of vehicles and users, and can quickly respond to changes in upload tasks, handle upload failures or retries in a timely manner, improve the response speed of upload tasks, reduce manual intervention operations, reduce operational complexity and error rates, facilitate after-sales problem analysts to quickly locate problems, and improve the efficiency and accuracy of problem analysis.
[0127] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the driving log uploading method of the present application. More simple transformations based on this technical concept are all within the protection scope of the present application.
[0128] This application also provides a driving log upload device, please refer to Figure 5 , the driving log uploading device comprises:
[0129] An acquisition module 10, configured to acquire vehicle characteristic information and generate an updated configuration file and a current configuration file based on the vehicle characteristic information;
[0130] A processing module 20, configured 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 and determine the upload status to issue a task list, and perform after-sales problem analysis based on the task list.
[0132] The driving log upload device provided by the present application adopts the driving log upload method in the above embodiment, which can solve the technical problem of how to conveniently upload the driving log. Compared with the prior art, the beneficial effects of the driving log upload device provided by the present application are the same as the beneficial effects of the driving log upload method provided by the above embodiment, and the other technical features in the driving log upload device are the same as the features disclosed in the above embodiment method, which will not be repeated here.
[0133] The present 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, and the instructions are executed by the at least one processor so that the at least one processor can execute the driving log uploading method in the above-mentioned embodiment one.
[0134] Reference below Figure 6 , which shows a schematic diagram of the structure of a driving log upload device suitable for implementing the embodiment of the present application. The driving log upload device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 6 The driving log uploading device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0135] like Figure 6As shown, the driving log upload device may include a processing device 1001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the driving log upload device are also stored. The processing device 1001, ROM1002, and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the driving log upload device to communicate with other devices wirelessly or by wire to exchange data. Although the driving log upload device with various systems is shown in the figure, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or have alternatively.
[0136] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.
[0137] The driving log upload device provided by the present application adopts the driving log upload method in the above embodiment, which can solve the technical problem of how to conveniently upload the driving log. Compared with the prior art, the beneficial effects of the driving log upload device provided by the present application are the same as the beneficial effects of the driving log upload method provided by the above embodiment, and the other technical features in the driving log upload device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.
[0138] It should be understood that the various parts disclosed in this application can be implemented by 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 one or more embodiments or examples in a suitable manner.
[0139] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
[0140] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the driving log uploading method in the above-mentioned embodiment.
[0141] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. 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 combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.
[0142] The computer-readable storage medium may be included in the driving log uploading device; or may exist independently without being assembled into the driving log uploading device.
[0143] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the driving log uploading device, the driving log uploading device: obtains vehicle characteristic information, generates an update configuration file and a current configuration file based on the vehicle characteristic information; determines log data based on the current configuration file and the update configuration file; uploads the log data and determines the upload status to issue a task list, and performs after-sales problem analysis based on the task list.
[0144] Computer program code for performing the operations of the present application may be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0145] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0146] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.
[0147] The readable storage medium provided in the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned driving log upload method, and can solve the technical problem of how to conveniently upload the driving log. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in the present application are the same as the beneficial effects of the driving log upload method provided in the above-mentioned embodiment, and will not be repeated here.
[0148] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.
Claims
1. A driving log uploading method, characterized in that: The method includes: Acquire vehicle characteristic information, and generate 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; The log data is uploaded and a task list is issued according to the upload status, and after-sales problem analysis is performed based on the task list.
2. The method according to claim 1, characterized in that The step of obtaining vehicle characteristic information comprises: Obtain vehicle feature code information, vehicle model information, log data type information and time information; The vehicle characteristic information is determined based on the vehicle characteristic code information, the vehicle model information and the log data type information.
3. The method according to claim 1, characterized in that The step of generating an update configuration file and a current configuration file based on the vehicle characteristic information comprises: Generate a feature identification value based on the vehicle feature code information and time information in the vehicle feature information; An update configuration file and a 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 identification value.
4. The method according to claim 3, characterized in that The step of determining 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 identification value comprises: Matching the feature identification value in the updated configuration file with the feature identification value in the current configuration file to determine the configuration file update status and obtain a matching result; Based on the matching result, an empty configuration file is sent to the vehicle end or an updated configuration file is sent to the vehicle end.
5. The method according to claim 3, characterized in that After the step of determining to update the 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 identification value, the following step is further included: Get the poll list; Upload the log data in the update configuration file, create an update task and add it to the polling list for execution.
6. The method according to claim 1, characterized in that The step of uploading the log data and judging the upload status to send a task list comprises: Obtaining manual driving status information and network condition status information; When the manual driving state information indicates that the manual driving state is good and the network condition state information indicates that the network condition is good, uploading the log data, determining the upload state, and obtaining the upload result; A header file sending task list is generated based on the upload result.
7. The method according to claim 1, characterized in that Before the step of performing after-sales problem analysis based on the task list, the following steps are also included: Obtaining log pull instructions and cloud configuration instructions, and determining a delivery status based on the log pull instructions; The log data file is viewed and downloaded based on the sending status, and the task list is determined based on the website link corresponding to the cloud configuration instruction.
8. A driving log upload device, characterized in that: The device comprises: An acquisition module, used for acquiring vehicle characteristic information, and generating an updated configuration file and a current configuration file based on the vehicle characteristic information; a processing module, configured 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 and determine the upload status to issue a task list, and perform after-sales problem analysis based on the task list.
9. A driving log uploading device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the driving log upload method according to any one of claims 1 to 7.
10. 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, the steps of the driving log uploading method according to any one of claims 1 to 7 are implemented.
Citation Information
Patent Citations
Method for continuously monitoring equipment configuration change
CN114297038A
Log uploading method and device for autonomous vehicle, equipment and storage medium
CN116244530A
Configuration file generation method, device and equipment
CN116346888A
File comparison method and device
CN116483949A
Log management system for Android vehicle machine
CN116996498A