Data processing method and device and log pulling platform

Abstract

The embodiment of the invention provides a data processing method and device and a log pulling platform. The method comprises the steps that a log pulling task is established according to an obtained after-sales problem report, the after-sales problem report comprises a frame number and after-sales problem information, and the log pulling task comprises the frame number and the after-sales problem information; receiving a first query request sent by the intelligent driving domain control device according to a set time interval, wherein the first query request comprises a frame number of the intelligent driving vehicle; inquiring whether a specified log pulling task exists or not, wherein the specified log pulling task is a log pulling task comprising a frame number of the specified log pulling task; if it is inquired that the specified log pulling task exists, the specified log pulling task is returned to the intelligent driving domain control device, so that the intelligent driving domain control device screens out a specified log from logs according to after-sales problem information of the specified log pulling task, and the specified log is packaged to generate a log file. According to the embodiment of the invention, timely positioning of the after-sales problem is realized, and the customer experience is greatly improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of intelligent driving technology, and in particular to a data processing method, device, and log pulling platform. Background Art

[0002] Various intelligent driving data are generated during the operation of the intelligent driving system. For example, intelligent driving data may include vehicle surrounding environment data collected by sensors such as cameras, millimeter-wave radars, lidars, and ultrasonic radars, algorithm intermediate results generated during the operation of each intelligent driving module, and various logs generated during the operation of the intelligent driving system.

[0003] When an intelligent driving after-sales problem occurs, the OEM needs to analyze the sensor data, algorithm intermediate results and detailed log data when the problem occurs in order to locate the problem. In the existing technology, customers can be coordinated to drive the vehicle to the 4S store, and the after-sales staff of the 4S store will read the intelligent driving data and upload the read intelligent driving data to the OEM, and then the OEM will analyze the intelligent driving data.

[0004] On the one hand, the technical solutions of the existing technology have a relatively long data link and the data processing takes a long time, which affects the timely location of after-sales problems. On the other hand, when after-sales problems occur, customers are less willing to cooperate, and it is difficult for the OEM to obtain relevant data for after-sales problem analysis. Summary of the invention

[0005] In view of this, the embodiments of the present application provide a data processing method, device and log pulling platform for timely locating after-sales problems and improving customer experience.

[0006] A first aspect provides a data processing method, comprising:

[0007] A log pulling task is established according to the obtained after-sales problem report, wherein the after-sales problem report includes a vehicle frame number and after-sales problem information, and the log pulling task includes the vehicle frame number and the after-sales problem information;

[0008] Receiving a first query request sent by the intelligent driving domain control device at a set time interval, wherein the first query request includes the frame number of the intelligent driving vehicle itself;

[0009] Query whether there is a specified log pulling task, where the specified log pulling task is a log pulling task including the vehicle frame number of the vehicle;

[0010] If the query finds that there is a specified log pulling task, the specified log pulling task is returned to the intelligent driving domain control device, so that the intelligent driving domain control device can filter out the specified log from the log according to the after-sales problem information of the specified log pulling task, and package the specified log to generate a log file.

[0011] In a possible implementation, before establishing the log pulling task according to the acquired after-sales problem report, the process further includes:

[0012] Receive the after-sales problem report sent by the OEM through the cloud.

[0013] In a possible implementation, the method further includes:

[0014] Receive upload information uploaded by the intelligent driving domain control device through a created upload task, where the upload information includes a segment file and first file information, where the segment file is generated by the intelligent driving domain control device performing segment processing on the log file;

[0015] Receiving second file information sent by the intelligent driving domain control device, where the second file information includes a first file MD5 value, where the first file MD5 value is generated by the intelligent driving domain control device calculating the log file;

[0016] The fragment files are merged to generate a log file, and MD5 calculation is performed on the log file to generate an MD5 value of a second file;

[0017] If it is determined that the MD5 value of the first file matches the MD5 value of the second file, it is determined that the verification is correct.

[0018] In a possible implementation, the method further includes:

[0019] If it is determined that the MD5 value of the first file and the MD5 value of the second file do not match, a verification error is determined and the verification error is returned to the intelligent driving domain control device.

[0020] In a possible implementation, the first file information includes a file name, a file size, a fragment number, a fragment size, a fragment quantity, a task identifier, and a fragment MD5 value.

[0021] In a possible implementation, the second file information further includes a log identifier, a task identifier, a file name, a file size, and a number of shards.

[0022] A second aspect provides a data processing device, including:

[0023] An establishment module is used to establish a log pulling task according to the acquired after-sales problem report, wherein the after-sales problem report includes a frame number and after-sales problem information, and the log pulling task includes the frame number and the after-sales problem information;

[0024] A transceiver module, configured to receive a first query request sent by the intelligent driving domain control device at a set time interval, wherein the first query request includes a frame number of the intelligent driving vehicle itself;

[0025] A query module, used to query whether there is a specified log pulling task, wherein the specified log pulling task is a log pulling task including the vehicle frame number of the vehicle;

[0026] The transceiver module is also used to return the specified log pulling task to the intelligent driving domain control device if the query module finds that there is a specified log pulling task, so that the intelligent driving domain control device can filter out the specified log from the log according to the after-sales problem information of the specified log pulling task, and package the specified log to generate a log file.

[0027] In a possible implementation, the device further includes: a merging module, a calculating module, a judging module, and a determining module;

[0028] The transceiver module is further used to receive upload information uploaded by the intelligent driving domain control device through the created upload task, wherein the upload information includes a segment file and first file information, and the segment file is generated by the intelligent driving domain control device by segmenting the log file;

[0029] The transceiver module is further used to receive second file information sent by the intelligent driving domain control device, where the second file information includes a first file MD5 value, where the first file MD5 value is generated by the intelligent driving domain control device calculating the log file;

[0030] The merging module is used to merge the fragment files to generate a log file;

[0031] The calculation module is used to perform MD5 calculation on the log file to generate a second file MD5 value;

[0032] The judging module is used to judge whether the MD5 value of the first file matches the MD5 value of the second file;

[0033] The determination module is used to determine that the verification is correct if the judgment module determines that the MD5 value of the first file matches the MD5 value of the second file.

[0034] The third aspect provides a log pulling platform, comprising: one or more processors; a memory; and one or more computer programs, wherein the one or more computer programs are stored in the memory, and the one or more computer programs include instructions, and when the instructions are executed by the log pulling platform, the log pulling platform executes the data processing method in the above-mentioned first aspect or any possible implementation of the first aspect.

[0035] The fourth aspect provides a computer-readable storage medium, which includes a stored program, wherein when the program is running, the log pulling platform where the computer-readable storage medium is located is controlled to execute the data processing method in the above-mentioned first aspect or any possible implementation of the first aspect.

[0036] In the technical solution provided in the embodiment of the present application, a log pulling task is established according to the obtained after-sales problem report. If it is queried that there is a specified log pulling task, the specified log pulling task is returned to the intelligent driving domain control device, so that the intelligent driving domain control device can filter out the specified log from the log according to the after-sales problem information of the specified log pulling task and package the specified log to generate a log file. The embodiment of the present application completes the acquisition of log files by establishing a log pulling task, thereby avoiding the problems of long data links and time-consuming data processing, thereby realizing timely positioning of after-sales problems; the embodiment of the present application completes the acquisition of log files by establishing a log pulling task, thereby avoiding the customer driving the vehicle to the 4S store, and the acquisition of log files can be completed during the customer's normal use of the vehicle, thereby greatly improving the customer experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0038] Figure 1 A flowchart of a data processing method provided in an embodiment of the present application;

[0039] Figure 2 A flowchart of another data processing method provided in an embodiment of the present application;

[0040] Figure 3 A schematic diagram of the structure of a data processing device provided in an embodiment of the present application;

[0041] Figure 4 A structural diagram of a log pulling platform provided in an embodiment of the present application. DETAILED DESCRIPTION

[0042] In order to better understand the technical solution of the present application, the embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0043] It should be clear that the described embodiments are only part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

[0044] The terms used in the embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to limit the present application. The singular forms "a", "said" and "the" used in the embodiments of the present application and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings.

[0045] It should be understood that the term "and / or" used in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0046] Figure 1 A flowchart of a data processing method provided in an embodiment of the present application is shown in FIG. Figure 1 As shown, the method includes:

[0047] Step 102: The OEM cloud receives the after-sales problem report and sends the after-sales problem report to the log pulling platform. The after-sales problem report includes the vehicle frame number and after-sales problem information.

[0048] In the embodiment of the present application, a log pulling platform can be built in the cloud, and the log pulling platform can be used to handle after-sales issues.

[0049] If an intelligent driving vehicle has an after-sales problem, the OEM staff can enter the after-sales problem report of the intelligent driving vehicle on the client, and the after-sales problem report may include the frame number and after-sales problem information. Among them, the frame number can be used to uniquely identify the intelligent driving vehicle. As an optional solution, the after-sales problem information may include the log type, log start time and log end time. Optionally, the after-sales problem information may also include the after-sales problem order number.

[0050] Step 104: The log pulling platform establishes a log pulling task according to the after-sales problem report. The log pulling task includes a log identifier (logId), a vehicle frame number, and after-sales problem information.

[0051] The log ID is used to identify the log pulling task.

[0052] Step 106: The log pulling platform receives a first query request sent by the intelligent driving domain control device at a set time interval, where the first query request includes the frame number of the intelligent driving vehicle itself.

[0053] The intelligent driving vehicle is provided with an intelligent driving domain control device. After the intelligent driving vehicle is started, the intelligent driving domain control device executes step 106. For example, the set time interval may be 3 minutes. The frame number in the log pulling task is specified to be the frame number of the intelligent driving vehicle itself.

[0054] Step 108 , the log pulling platform queries whether there is a specified log pulling task, where the specified log pulling task is a log pulling task including its own vehicle frame number. If so, execute step 110 ; if not, execute step 106 .

[0055] If the log pulling platform finds out that there is a log pulling task that includes its own vehicle frame number, it indicates that there is a designated log pulling task, and step 118 is continued to be executed; if the log pulling platform finds out that there is no log pulling task that includes its own vehicle frame number, it indicates that there is no designated log pulling task, and step 106 is continued to be executed to continue waiting for the first query request sent by the intelligent driving domain control device.

[0056] Step 110: The log pulling platform returns the specified log pulling task to the intelligent driving domain control device.

[0057] After the log pulling platform queries and finds out that there is a specified log pulling task, the log pulling platform returns the specified log pulling task to the intelligent driving domain control device, so that the intelligent driving domain control device can obtain the specified log pulling task from the log pulling platform.

[0058] Step 112: The intelligent driving domain control device filters out the specified log from the log according to the after-sales problem information of the specified log pulling task.

[0059] As an optional solution, when the after-sales problem information may include the log type, log start time, and log end time, the intelligent driving domain control device filters out the specified log from the log according to the log type, log start time, and log end time. Specifically, the intelligent driving domain control device filters out the logs whose time points are between the log start time and the log end time and whose types are the log types, and uses the filtered logs as the specified logs.

[0060] Step 114: The intelligent driving domain control device packages the specified logs and generates a log file.

[0061] Specifically, the intelligent driving domain control device can package the specified logs to compress the specified logs into a log file.

[0062] As an optional solution, after step 114, the method may further include: the intelligent driving domain control device returns status information corresponding to the specified log identifier to the log pulling platform, where the status information is in packaging, and the specified log identifier is the log identifier included in the specified log pulling task. Specifically, the intelligent driving domain control device may return status information corresponding to the specified log identifier to the log pulling platform through the called log pulling platform interface.

[0063] Figure 2 A flowchart of another data processing method provided in an embodiment of the present application. As an optional solution, Figure 2 As shown, after step 114, the following steps may also be included:

[0064] Step 116: The intelligent driving domain control device creates an upload task according to its own vehicle frame number, and obtains a task identifier (taskId) of the upload task, which is used to identify the upload task.

[0065] As an optional solution, step 116 may also include: the intelligent driving domain control device returns status information corresponding to the specified log identifier to the log pulling platform, and the status information is uploading.

[0066] As an optional solution, after step 116, the following may be included: the intelligent driving domain control device binds the log identifier and the task identifier to establish a corresponding relationship between the log identifier and the task identifier; and sends the corresponding relationship between the log identifier and the task identifier to the log pulling platform. The log identifier may be a specified log identifier.

[0067] Step 118: The intelligent driving domain control device segments the log file to generate segment files, and uploads the upload information to the log pulling platform through the created upload task, where the upload information includes the segment files and the first file information.

[0068] As an optional solution, the first file information may include a file name, a file size, a shard number, a shard size, a shard quantity, a task identifier, and a shard MD5 value, wherein the file name is the name of the log file, and the file size is the size of the log file.

[0069] Among them, the intelligent driving domain control device can perform MD5 calculation on the slice file to generate the slice MD5 value.

[0070] As an optional solution, step 118 may further include:

[0071] The log pulling platform queries the task identifier corresponding to the specified log identifier based on the correspondence between the log identifier and the task identifier.

[0072] The log pulling platform queries the first file information including the task identifier corresponding to the specified log identifier.

[0073] The log pulling platform obtains the file size and the fragment size according to the queried first file information, and counts the number of fragment files that have been uploaded.

[0074] The log pulling platform calculates the upload progress by the following formula: upload progress = shard size * number of uploaded shard files / file size. For example, the upload progress can be a percentage.

[0075] As an optional solution, when the file upload is stopped during the file upload process, for example, the file upload is stopped due to the vehicle being turned off during the file upload process, the following method can be executed after the vehicle is restarted to achieve breakpoint resume. The method also includes: the intelligent driving domain control device sends a query request to the log pulling platform, and the query request includes a task identifier; the log pulling platform queries the currently uploaded first file information including the task identifier according to the task identifier, and returns the currently uploaded first file information to the intelligent driving domain control device; the intelligent driving domain control device uploads the unuploaded upload information to the log pulling platform according to the currently uploaded first file information. Thus, the breakpoint resume function is achieved.

[0076] Step 120: The intelligent driving domain control device sends second file information to the log pulling platform, where the second file information includes the MD5 value of the first file.

[0077] After the segmented file is uploaded, the intelligent driving domain control device provides the second file information to the log pulling platform by calling the log pulling platform task completion interface.

[0078] As an optional solution, the second file information may include the MD5 value of the first file. The intelligent driving domain control device may perform MD5 calculation on the log file to generate the MD5 value of the first file.

[0079] As an optional solution, the second file information may also include a log identifier, a task identifier, a file name, a file size, and a number of shards.

[0080] Step 122: The log pulling platform merges the fragment files to generate a log file, and performs MD5 calculation on the log file to generate the MD5 value of the second file.

[0081] Step 124 , the log pulling platform determines whether the first MD5 value matches the second MD5 value. If so, execute step 126 ; if not, continue to execute step 128 .

[0082] Specifically, the log pulling platform determines whether the first MD5 value and the second MD5 value are the same. If it is determined that the first MD5 value and the second MD5 value are the same, it indicates that the first MD5 value and the second MD5 value match, and step S6 is continued; if it is determined that the first MD5 value and the second MD5 value are different, it indicates that the first MD5 value and the second MD5 value do not match, and step 128 is continued.

[0083] Step 126: The log pulling platform determines that the verification is correct.

[0084] The log pulling platform determines that the verification is correct, indicating that the verification is completed. As an optional solution, after step S6, the log pulling platform also includes: setting the status information corresponding to the specified log identifier to upload completed.

[0085] Step 128: The log pulling platform determines a verification error and returns the verification error to the intelligent driving domain control device.

[0086] Step 130: The intelligent driving domain control device responds to the verification error and continues to execute step 116.

[0087] When the log pulling platform determines that a verification error has occurred, it is necessary to notify the intelligent driving domain control device of the verification error to trigger the intelligent driving domain control device to execute step 118 and re-upload the segmented files in segments.

[0088] In the technical solution provided in the embodiment of the present application, a log pulling task is established according to the obtained after-sales problem report. If it is queried that there is a specified log pulling task, the specified log pulling task is returned to the intelligent driving domain control device, so that the intelligent driving domain control device can filter out the specified log from the log according to the after-sales problem information of the specified log pulling task and package the specified log to generate a log file. The embodiment of the present application completes the acquisition of log files by establishing a log pulling task, thereby avoiding the problems of long data links and time-consuming data processing, thereby realizing timely positioning of after-sales problems; the embodiment of the present application completes the acquisition of log files by establishing a log pulling task, thereby avoiding the customer driving the vehicle to the 4S store, and the log file can be obtained during the customer's normal use of the vehicle, thereby greatly improving the customer experience; the solution of the embodiment of the present application avoids the intervention of 4S after-sales personnel, reduces the cost of after-sales service, reduces the cost of information errors and omissions in manual communication, and reduces the information security risk of the loss of intelligent driving logs at the 4S store.

[0089] Figure 3 A schematic diagram of the structure of a data processing device provided in an embodiment of the present application is shown in FIG. Figure 3 As shown, the device includes: an establishing module 11, a transceiver module 12 and a query module 13.

[0090] The establishment module 11 is used to establish a log pulling task according to the acquired after-sales problem report, wherein the after-sales problem report includes a frame number and after-sales problem information, and the log pulling task includes the frame number and the after-sales problem information; the transceiver module 12 is used to receive a first query request sent by the intelligent driving domain control device at a set time interval, wherein the first query request includes the frame number of the intelligent driving vehicle itself; the query module 13 is used to query whether there is a specified log pulling task, wherein the specified log pulling task is a log pulling task including its own frame number; the transceiver module 12 is also used to return the specified log pulling task to the intelligent driving domain control device if the query module 13 finds out that there is a specified log pulling task, so that the intelligent driving domain control device can filter out the specified log from the log according to the after-sales problem information of the specified log pulling task, and package the specified log to generate a log file.

[0091] As an optional solution, the transceiver module 12 is also used to receive the after-sales problem report sent by the host manufacturer through the cloud.

[0092] As an optional solution, the device further includes: a merging module 14 , a calculating module 15 , a judging module 16 and a determining module 17 .

[0093] The transceiver module 12 is also used to receive upload information uploaded by the intelligent driving domain control device through the created upload task, wherein the upload information includes a segmented file and a first file information, and the segmented information is generated by the intelligent driving domain control device performing segmentation processing on the log file; the transceiver module 12 is also used to receive the second file information sent by the intelligent driving domain control device, wherein the second file information includes a first file MD5 value, and the first file MD5 value is generated by the intelligent driving domain control device performing calculation on the log file; the merging module 14 is used to merge the segmented files to generate a log file; the calculation module 15 is used to perform MD5 calculation on the log file to generate a second file MD5 value; the judgment module 16 is used to judge whether the first file MD5 value and the second file MD5 value match; the determination module 17 is used to determine that the verification is correct if the judgment module 16 judges that the first file MD5 value and the second file MD5 value match.

[0094] As an optional solution, the determination module 16 is also used to determine a verification error if the judgment module 15 determines that the MD5 value of the first file and the MD5 value of the second file do not match, and trigger the transceiver module 12 to return the verification error to the intelligent driving domain control device.

[0095] In the technical solution provided in the embodiment of the present application, a log pulling task is established according to the obtained after-sales problem report. If it is queried that there is a specified log pulling task, the specified log pulling task is returned to the intelligent driving domain control device, so that the intelligent driving domain control device can filter out the specified log from the log according to the after-sales problem information of the specified log pulling task and package the specified log to generate a log file. The embodiment of the present application completes the acquisition of log files by establishing a log pulling task, thereby avoiding the problems of long data links and time-consuming data processing, thereby realizing timely positioning of after-sales problems; the embodiment of the present application completes the acquisition of log files by establishing a log pulling task, thereby avoiding the customer driving the vehicle to the 4S store, and the acquisition of log files can be completed during the customer's normal use of the vehicle, thereby greatly improving the customer experience.

[0096] An embodiment of the present application provides a computer-readable storage medium, which includes a stored program, wherein when the program is run, a log pulling platform where the storage medium is located is controlled to execute an embodiment of the above-mentioned data processing method.

[0097] An embodiment of the present application provides a log pulling platform, comprising: one or more processors; a memory; and one or more computer programs, wherein the one or more computer programs are stored in the memory, and the one or more computer programs include instructions, and when the instructions are executed by the log pulling platform, the log pulling platform executes the above-mentioned data processing method.

[0098] Figure 4 A structural diagram of a log pulling platform provided in an embodiment of the present application is shown in FIG. Figure 4 As shown, the log pulling platform 20 includes: a processor 21, a memory 22, and a computer program 23 stored in the memory 22 and executable on the processor 21. When the computer program 23 is executed by the processor 21, the data processing method applied in the embodiment is implemented. To avoid repetition, they are not described one by one here.

[0099] The log pulling platform 20 includes, but is not limited to, a processor 21 and a memory 22. Those skilled in the art will appreciate that Figure 4 This is only an example of the log pulling platform 20 and does not constitute a limitation of the log pulling platform 20. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the log pulling platform 20 may also include input and output devices, network access devices, buses, etc.

[0100] The processor 21 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0101] The memory 22 may be an internal storage unit of the log pulling platform 20, such as a hard disk or memory of the log pulling platform 20. The memory 22 may also be an external storage device of the log pulling platform 20, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped on the log pulling platform 20. Further, the memory 22 may also include both an internal storage unit of the log pulling platform 20 and an external storage device. The memory 22 is used to store computer programs and other programs and data required by the log pulling platform 20. The memory 22 may also be used to temporarily store data that has been output or is to be output.

[0102] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0103] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0104] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0105] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0106] The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (Processor) to perform some steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program code.

[0107] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A data processing method, characterized in that: include: A log pulling task is established according to the obtained after-sales problem report, wherein the after-sales problem report includes a vehicle frame number and after-sales problem information, and the log pulling task includes the vehicle frame number and the after-sales problem information; Receiving a first query request sent by the intelligent driving domain control device at a set time interval, wherein the first query request includes the frame number of the intelligent driving vehicle itself; Query whether there is a specified log pulling task, where the specified log pulling task is a log pulling task including the vehicle frame number of the vehicle; If the query finds that there is a specified log pulling task, the specified log pulling task is returned to the intelligent driving domain control device, so that the intelligent driving domain control device can filter out the specified log from the log according to the after-sales problem information of the specified log pulling task, and package the specified log to generate a log file.

2. The method according to claim 1, characterized in that Before establishing the log pulling task according to the obtained after-sales problem report, the process also includes: Receive the after-sales problem report sent by the OEM through the cloud.

3. The method according to claim 1, characterized in that The method further comprises: Receive upload information uploaded by the intelligent driving domain control device through a created upload task, where the upload information includes a segment file and first file information, where the segment file is generated by the intelligent driving domain control device performing segment processing on the log file; Receiving second file information sent by the intelligent driving domain control device, where the second file information includes a first file MD5 value, where the first file MD5 value is generated by the intelligent driving domain control device calculating the log file; The fragment files are merged to generate a log file, and MD5 calculation is performed on the log file to generate an MD5 value of a second file; If it is determined that the MD5 value of the first file matches the MD5 value of the second file, it is determined that the verification is correct.

4. The method according to claim 3, characterized in that: The method further comprises: If it is determined that the MD5 value of the first file and the MD5 value of the second file do not match, a verification error is determined and the verification error is returned to the intelligent driving domain control device.

5. The method according to claim 3, characterized in that: The first file information includes the file name, file size, fragment number, fragment size, number of fragments, task identifier and fragment MD5 value.

6. The method according to claim 3, characterized in that The second file information also includes a log identifier, a task identifier, a file name, a file size, and a number of shards.

7. A data processing device, characterized in that: include: An establishment module is used to establish a log pulling task according to the acquired after-sales problem report, wherein the after-sales problem report includes a frame number and after-sales problem information, and the log pulling task includes the frame number and the after-sales problem information; A transceiver module, configured to receive a first query request sent by the intelligent driving domain control device at a set time interval, wherein the first query request includes a frame number of the intelligent driving vehicle itself; A query module, used to query whether there is a specified log pulling task, wherein the specified log pulling task is a log pulling task including the vehicle frame number of the vehicle; The transceiver module is also used to return the specified log pulling task to the intelligent driving domain control device if the query module finds that there is a specified log pulling task, so that the intelligent driving domain control device can filter out the specified log from the log according to the after-sales problem information of the specified log pulling task, and package the specified log to generate a log file.

8. The device according to claim 7, characterized in that The device also includes: a merging module, a calculating module, a judging module and a determining module; The transceiver module is further used to receive upload information uploaded by the intelligent driving domain control device through the created upload task, wherein the upload information includes a segment file and first file information, and the segment information is generated by the intelligent driving domain control device performing segment processing on the log file; The transceiver module is further used to receive second file information sent by the intelligent driving domain control device, where the second file information includes a first file MD5 value, where the first file MD5 value is generated by the intelligent driving domain control device calculating the log file; The merging module is used to merge the fragment files to generate a log file; The calculation module is used to perform MD5 calculation on the log file to generate a second file MD5 value; The judging module is used to judge whether the MD5 value of the first file matches the MD5 value of the second file; The determination module is used to determine that the verification is correct if the judgment module determines that the MD5 value of the first file matches the MD5 value of the second file.

9. A log pulling platform, characterized in that: include: one or more processors; Memory; And one or more computer programs, wherein the one or more computer programs are stored in the memory, and the one or more computer programs include instructions, which, when executed by the log pulling platform, enable the log pulling platform to execute the data processing method described in any one of claims 1 to 6.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein when the program is executed, the log pulling platform where the computer-readable storage medium is located is controlled to execute the data processing method according to any one of claims 1 to 6.

Images