Data processing method and device of domain controller, electronic equipment and storage medium

Abstract

The invention discloses a data processing method and device of a domain controller, electronic equipment and a storage medium, and the method comprises the steps: obtaining a first data file corresponding to each target domain controller through a central domain controller (CCU); integrating the plurality of first data files into a second data file through the CCU; and uploading the second data file to a server, wherein the second data file is used for the server to carry out fault analysis on the vehicle. According to the method, when the vehicle collects the fault data, the fault data of each domain controller is unified into the target file format and then combined into one data file, so that the server can only perform fault analysis on the integrated second data file without analyzing the data files with different file formats, and the fault analysis efficiency is improved. And the analysis efficiency of fault analysis is improved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and more specifically, to a data processing method, device, electronic device and storage medium of a domain controller. Background Art

[0002] When an abnormal crash occurs in the application software nodes of each domain in the vehicle, it is necessary to collect fault information from each module separately. However, due to the inconsistency of the file formats of each domain, the fault information of each domain controller is very different. Therefore, it is necessary to troubleshoot the faults of each domain controller in turn to find the root cause of the application abnormality, which makes the abnormality troubleshooting inefficient. Summary of the invention

[0003] In view of the above problems, the present application proposes a data processing method, device, electronic device and storage medium of a domain controller.

[0004] In a first aspect, an embodiment of the present application provides a data processing method for a domain controller, the method comprising: obtaining, through a central domain controller CCU, a first data file corresponding to each target domain controller, the target domain controller refers to a domain controller other than the CCU in the vehicle, the first data file comprising fault data collected by the target domain controller after the application fault occurs in the vehicle, and the file format of the first data file corresponding to each target domain controller is a target file format; integrating multiple first data files into a second data file through the CCU; uploading the second data file to a server, the second data file being used by the server to perform fault analysis on the vehicle.

[0005] In an optional embodiment, obtaining the first data file corresponding to each target domain controller through a central domain controller CCU includes: collecting fault data in each target domain controller through each target domain controller as an initial first data file; converting the file format of the initial first data file into the target file format according to a preset conversion method through each target domain controller to obtain a first data file corresponding to the initial first data file; obtaining the first data file corresponding to each target domain controller through the CCU.

[0006] In an optional embodiment, the file format of the initial first data file is converted into the target file format according to a preset conversion method by each of the target domain controllers to obtain a first data file corresponding to the initial first data file, including: encoding the data in the initial first data file by a preprocessing component on each of the target domain controllers to obtain an encoded file as a first encoded file; converting the file format of the first encoded file into the target file format by a preprocessing component on each of the target domain controllers to obtain a first data file corresponding to the initial first data file.

[0007] In an optional embodiment, after collecting the fault data in each target domain controller as the initial first data file through each target domain controller, the method further includes: if the preprocessing component is not provided on the target domain controller, sending the initial first data file to the CCU through the target domain controller; encoding the data in the initial first data file through the preprocessing component on the CCU to obtain the encoded file as the second encoded file; converting the file format of the second encoded file into the target file format through the preprocessing component on the CCU to obtain the first data file corresponding to the initial first data file.

[0008] In an optional embodiment, the target domain controller includes multiple application software, and obtaining the first data file corresponding to each target domain controller through the central domain controller CCU includes: obtaining the software data of all application software on the target domain controller through the target domain controller; if any item of the software data matches a preset fault condition, it is determined that an application fault exists in the vehicle, and obtaining the first data file corresponding to each target domain controller through the CCU.

[0009] In an optional embodiment, obtaining the first data file corresponding to each target domain controller through the central domain controller CCU includes: receiving, through the CCU, a data acquisition instruction sent by the server, wherein the data acquisition instruction is issued by the server when the server monitors that an application failure exists in the vehicle; and obtaining, through the CCU, the first data file corresponding to each target domain controller in response to the data acquisition instruction.

[0010] In an optional embodiment, integrating multiple first data files into a second data file through the CCU includes: obtaining time information of each first data file through the CCU; and integrating multiple first data files into the second data file according to the time information through the CCU.

[0011] In a second aspect, an embodiment of the present application provides a data processing device for a domain controller, the device comprising: a first data file acquisition module, used to acquire a first data file corresponding to each target domain controller through a central domain controller CCU, the target domain controller refers to a domain controller other than the CCU in the vehicle, the first data file includes fault data collected by the target domain controller after the application fault occurs in the vehicle, and the file format of the first data file corresponding to each target domain controller is a target file format; a second data file determination module, used to integrate multiple first data files into a second data file through the CCU; a fault analysis module, used to upload the second data file to a server, the second data file is used by the server to perform fault analysis on the vehicle.

[0012] In a third aspect, an embodiment of the present application provides a vehicle, comprising: one or more processors; a memory; one or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, and the one or more programs are configured to execute the data processing method of the domain controller provided in the first aspect above.

[0013] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which a program code is stored. The program code can be called by a processor to execute the data processing method of the domain controller provided in the first aspect above.

[0014] In a fifth aspect, an embodiment of the present application provides a computer program product, wherein the computer program product includes a program code, and the program code can be called by a processor to execute the data processing method of the domain controller provided in the first aspect above.

[0015] The solution provided by the present application is that when there is an application anomaly in the vehicle, each target domain controller converts the collected fault data into the same target file format to obtain a first data file, and the central domain controller integrates multiple first data files into a second data file and uploads it to the server. Since the vehicle collects fault data, the fault data of each domain controller is unified into the target file format and then merged into one data file, the server can only perform fault analysis on the integrated second data file, without having to analyze data files of different file formats, thereby improving the analysis efficiency of fault analysis. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0017] Figure 1 A schematic flow chart of a data processing method of a domain controller provided in an embodiment of the present application is shown.

[0018] Figure 2 A schematic flow chart of a data processing method of a domain controller provided in another embodiment of the present application is shown.

[0019] Figure 3 A schematic flow chart of a data processing method of a domain controller provided in yet another embodiment of the present application is shown.

[0020] Figure 4 A schematic flow chart of a data processing method of a domain controller provided in yet another embodiment of the present application is shown.

[0021] Figure 5 A structural block diagram of a data processing device of a domain controller provided in an embodiment of the present application is shown.

[0022] Figure 6 A structural block diagram of a vehicle provided by an embodiment of the present application for executing a data processing method of a domain controller according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0023] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application.

[0024] In response to the technical problems raised by the background technology, the inventors have proposed a data processing method, device, electronic device and storage medium for a domain controller. When an application abnormality occurs in a vehicle, each target domain controller converts the collected fault data into the same target file format to obtain a first data file, and the central domain controller integrates multiple first data files into a second data file and uploads it to a server. When the vehicle collects fault data, the fault data of each domain controller is unified into the target file format and then merged into one data file. Therefore, the server can only perform fault analysis on the integrated second data file, without having to analyze data files of different file formats, thereby improving the analysis efficiency of fault analysis.

[0025] See also Figure 1 , Figure 1FIG. 1 is a flow chart showing a data processing method for a domain controller provided by an embodiment of the present application. In a specific embodiment, the data processing method for the domain controller is applied to Figure 5 The data processing device 200 of the domain controller and the vehicle equipped with the data processing device 200 of the domain controller are shown.

[0026] The following will focus on Figure 1 The process shown is described in detail, and the data processing method of the domain controller may specifically include the following steps:

[0027] Step S110: Obtain, through the central domain controller CCU, the first data file corresponding to each target domain controller, where the target domain controller refers to the domain controller in the vehicle other than the CCU, and the first data file includes fault data collected by the target domain controller after the application fault occurs in the vehicle, and the file format of the first data file corresponding to each target domain controller is a target file format.

[0028] Among them, when there is an application failure in the vehicle or a data file acquisition request is received, the data file corresponding to each target domain controller will be obtained through the CCU. An application failure can be an application software crash failure, an application software data jump failure, or an abnormal trend. An application failure can be a series of abnormal phenomena that lead to abnormal use of the application software and application software data acquisition, analysis, and storage. Different application failures correspond to different fault data. When the application failure is an application software crash failure, the fault data can be the data generated when the application software crashes, or it can be the data generated and / or used by the application software within a preset time before and after the application software crashes. When the application failure is an application software data jump failure, the fault data can be jump data and application data that causes data jumps, etc. No specific limitation is made here for application failures, and no specific limitation is made for fault data.

[0029] In the field of vehicle control, vehicle functions are divided into multiple units, and each unit controller is controlled by the domain controller of the unit. The central domain controller (CCU) is a domain controller used to control other domain controllers of the entire vehicle. The CCU can also receive data transmitted by other domain controllers through wired or wireless means.

[0030] The target domain controller can be the domain controller where the application software that causes the application failure is located, or it can be all the domain controllers of the entire vehicle, including the central domain controller and all domain controllers other than the central domain controller. It can also be the domain controller where the application software that causes the application failure is located and other domain controllers related to the application software. The target domain controller is not specifically limited here.

[0031] Since different domain controllers process different data, the formats of data files collected by different domain controllers may also be different. In order to improve the processing capability of the central domain controller, the collected fault data files can be stored in the target file format on the target domain controller side. The target file format can be a text format, a structured data storage format (probuff), or a lightweight data exchange format (json). The target file format is not specifically limited here.

[0032] In some implementations, the domain controller can also collect fault data by setting up a collection component slave. The collection component provides a point-of-use interface to the application software. When the application software sends a fault, the collection component slave on the domain controller collects the fault data and stores it in a file queue or a memory cache queue. A collection component master can also be set up on the CCU. When the collection component slave on the domain controller collects data, data is exchanged through inter-component communication.

[0033] In the embodiment of the present application, when an application failure occurs in the vehicle, the target domain controller collects relevant failure data and determines the data file to be in the target file format to obtain a first data file. The CCU can obtain the first data file by communicating with the target domain controller.

[0034] Step S120: integrating the plurality of the first data files into a second data file through the CCU.

[0035] The integration method may be to integrate multiple first data files into one second data file, or to extract different data types of multiple first data files, integrate one file according to each data type, and obtain the second data file. The integration method is not specifically limited here.

[0036] Step S130: uploading the second data file to a server, where the second data file is used by the server to perform fault analysis on the vehicle.

[0037] In the embodiment of the present application, the file upload method can be through a communication protocol, and the communication protocol can be a service-oriented communication protocol (Scalable service-Oriented MiddlewarE over IP, SOME / IP), or a lightweight Internet of Things communication protocol (Message Queuing Telemetry Transport, MQTT), or other communication protocols that can realize vehicle-cloud communication. The communication protocol is not specifically limited for uploading. The file upload method can also be to forward the second file to the Internet of Vehicles module (Telematics Box, TBOX), and upload the second data file to the server through the Internet of Vehicles module. The file upload method is not specifically limited here.

[0038] When the server receives the second data file, the server can analyze the second data file through a complete analysis environment such as a tool chain and parsing tools inside the server to determine the cause of the application failure and a method for resolving the application failure. In the embodiment of the present application, the failure analysis of the server is not specifically limited. After the server determines the cause of the failure, a restart instruction can be issued to restart the faulty process or process group corresponding to the faulty application software to achieve rapid recovery after the fault analysis.

[0039] In the data processing method of the domain controller provided in the embodiment of the present application, when there is an application anomaly in the vehicle, each target domain controller converts the collected fault data into the same target file format to obtain a first data file, and the central domain controller integrates multiple first data files into a second data file and uploads it to the server. Since the vehicle unifies the fault data of each domain controller into the target file format and then merges them into one data file when collecting fault data, the server can perform fault analysis only on the integrated second data file, without having to analyze data files of different file formats, thereby improving the analysis efficiency of fault analysis.

[0040] See also Figure 2 , Figure 2 A schematic diagram of a data processing method for a domain controller provided by another embodiment of the present application is shown below. Figure 2 The process shown is described in detail, and the data processing method of the domain controller may specifically include the following steps:

[0041] Step S210: Collecting the fault data in each target domain controller through each target domain controller as an initial first data file.

[0042] Step S220: by each of the target domain controllers, according to a preset conversion method, converting the file format of the initial first data file into the target file format, to obtain a first data file corresponding to the initial first data file.

[0043] The preset conversion method may first extract the relevant information in the initial first data file, and then obtain the first data file corresponding to the initial first data file according to the preset typesetting in the preset conversion format. The preset conversion method may also directly change the file format of the initial first data file to the target file format to obtain the first data file corresponding to the initial first data file.

[0044] In some implementations, by each of the target domain controllers, according to a preset conversion method, converting the file format of the initial first data file into the target file format to obtain a first data file corresponding to the initial first data file, including: encoding the data in the initial first data file by a preprocessing component on each of the target domain controllers to obtain an encoded file as a first encoded file. By converting the file format of the first encoded file into the target file format by a preprocessing component on each of the target domain controllers, a first data file corresponding to the initial first data file is obtained.

[0045] Among them, the preprocessing component is used to preprocess the data, and the preprocessing includes but is not limited to data cleaning, data encoding, data conversion and other data preprocessing methods.

[0046] Data encoding can be encoding the data type in the initial data file, encoding the timestamp corresponding to the data, encoding the domain controller where the initial first data file is located, encoding the node corresponding to the data, or encoding the data by combining multiple information to obtain a first encoded file.

[0047] In an implementation manner of the present application, data in an initial first data file is encoded according to a preprocessing component on a target domain controller to obtain a first encoded file, and then the first encoded file is converted into a file format through the preprocessing component to obtain a first data file.

[0048] In other embodiments, by each of the target domain controllers, according to a preset conversion method, the file format of the initial first data file is converted into the target file format to obtain a first data file corresponding to the initial first data file, including: if the preprocessing component is not provided on the target domain controller, the initial first data file is sent to the CCU by the target domain controller. The data in the initial first data file is encoded by the preprocessing component on the CCU to obtain an encoded file as a second encoded file. The file format of the second encoded file is converted into the target file format by the preprocessing component on the CCU to obtain a first data file corresponding to the initial first data file.

[0049] In the implementation manner of the present application, when the target domain controller is not provided with a preprocessing component, the CCU obtains the initial first data file of the target domain controller, and then the preprocessing component on the CCU encodes the data of the initial first data file to obtain a second encoded file, thereby obtaining the first data file of the target domain controller. Setting the preprocessing component on the CCU can avoid file integration errors caused by the inconsistency between the file format of the initial first data file and the target file format when the preprocessing component is not provided on the target domain controller.

[0050] Step S230: Obtain, through the CCU, a first data file corresponding to each of the target domain controllers.

[0051] In the embodiment of the present application, the method for obtaining the first data file can refer to the specific introduction in the above embodiment, which will not be repeated here.

[0052] Step S240: Obtaining time information of each of the first data files through the CCU.

[0053] Step S250: integrating the plurality of first data files into the second data file according to the time information through the CCU.

[0054] The time information may be a timestamp of the generation of the first data file, or may be time information when the first data file is converted into a target file format, and the time information is not specifically limited here.

[0055] In the embodiment of the present application, multiple first data files are integrated into a second data file according to time information, so that the cause of the application failure can be more clearly obtained, so that the server can perform more accurate analysis based on the second data file.

[0056] Step S260: uploading the second data file to a server, where the second data file is used by the server to perform fault analysis on the vehicle.

[0057] For the detailed description of step S260, please refer to step S130 in the aforementioned embodiment, which will not be repeated here.

[0058] The data processing method for the domain controller provided in the embodiment of the present application obtains the fault data of the application software on each domain controller through each target domain controller when an application fault occurs in the vehicle, and then converts the file format of the collected fault data according to a preset conversion format, so that the data file of each target domain controller is in the target file format, and then integrates multiple first data files in the target file format through the CCU to obtain a second data file, and uploads the second data file to the server, so that the server can perform fault analysis on all target domain controllers according to the second data file, thereby avoiding inconsistent data file formats collected by multiple target domain controllers and improving the analysis efficiency of server fault analysis.

[0059] See also Figure 3 , Figure 3 FIG. 1 is a flow chart of a data processing method of a domain controller provided by another embodiment of the present application. Figure 3 The process shown is described in detail, and the data processing method of the domain controller may specifically include the following steps:

[0060] Step S310: Acquire software data of all application software on the target domain controller through the target domain controller.

[0061] The software data includes but is not limited to software logs, core files, Controller Area Network (CAN) message information, Local Interconnect Network (LIN) message, Ethernet (ETH) message, register snapshot, stack snapshot, audio and video clips, etc. The software data can be acquired in real time or periodically, and the acquisition method of the software data is not limited here.

[0062] Step S320: If any of the software data matches the preset fault condition, it is determined that an application fault exists in the vehicle, and the first data file corresponding to each target domain controller is obtained through the CCU.

[0063] The preset fault condition may be a data peak value condition and a data valley value condition, or may be a data fault condition such as a data change value condition.

[0064] In an embodiment of the present application, when any software data matches a preset fault condition, the application software is determined to be abnormal and is determined to be the target application software. The domain controller where the target application software is located can be determined as the target domain controller, and the first data file of the target domain controller can be obtained through the CCU. It is also possible to determine all domain controllers involved in the target application software as target domain controllers, and obtain the first data file of the target domain controller through the CCU. It is also possible to determine the domain controller of the entire vehicle as the target domain controller when any software data matches a preset fault condition, and obtain the first data file of the target domain controller through the CCU. The method for obtaining the first data file can refer to the specific introduction of the aforementioned embodiment, which will not be repeated here.

[0065] Step S330: Integrate the plurality of first data files into a second data file through the CCU.

[0066] Step S340: uploading the second data file to a server, where the second data file is used by the server to perform fault analysis on the vehicle.

[0067] For detailed description of steps S330 to S340, please refer to steps S120 to S130 in the aforementioned embodiment, which will not be repeated here.

[0068] The data processing method of the domain controller provided in the embodiment of the present application determines that an application fault exists in the vehicle when any software data in the application software matches a preset fault condition. At this time, the target domain controller is triggered to automatically collect fault data, and the file format of the initial first data file recording the fault data is determined as the target file format to obtain a first data file. The central domain controller then integrates multiple first data files to obtain a second data file, and uploads it to the server, so that the server can analyze the data in multiple target domain controllers according to the second data file, thereby improving the efficiency of server fault analysis.

[0069] See also Figure 4 , Figure 4 A schematic diagram of a data processing method for a domain controller according to another embodiment of the present application is shown. Figure 4 The process shown is described in detail, and the data processing method of the domain controller may specifically include the following steps:

[0070] Step S410: receiving, through the CCU, a data collection instruction sent by the server, wherein the data collection instruction is sent when the server monitors that an application failure exists in the vehicle.

[0071] Among them, the data collection instruction can be an information instruction, for example, the data collection instruction is to collect data from the domain controller of the whole vehicle. The data collection instruction can also be a flag instruction, for example, the data collection instruction is that the data collection flag is 1. The specific form of the data collection instruction is not limited here. The data collection instruction can be used to instruct the collection of fault information of the domain controller of the whole vehicle, and the domain controller of the whole vehicle includes the central domain controller and the fault information of all domain controllers in the vehicle except the central domain controller. The data collection instruction can also be a data collection instruction for collecting data from a domain controller with an application failure.

[0072] Receiving the data collection instructions sent by the server requires establishing communication between the vehicle and the server. Therefore, the data collection instructions can be received through the vehicle's Internet of Vehicles module (Telematics Box, TBOX), and then the TBOX forwards the data collection instructions to the central domain controller. The data collection instructions can also be received by establishing communication between the central domain controller and the server through a communication protocol. The communication protocol can be a service-oriented communication protocol (Scalable service-Oriented MiddlewarE over IP, SOME / IP), or a lightweight Internet of Things communication protocol (Message Queuing Telemetry Transport, MQTT), or other communication protocols that can realize vehicle-cloud communication. The communication protocol is not specifically limited here.

[0073] Step S420: Acquire, by the CCU, a first data file corresponding to each of the target domain controllers in response to the data acquisition instruction.

[0074] In the embodiment of the present application, when the CCU obtains the data acquisition instruction, the data acquisition instruction can be sent to the domain controller where the application failure occurs, and the domain controller where the application failure occurs is used as the target domain controller to make the target domain controller perform data acquisition, or the data acquisition instruction can be sent to all domain controllers to make all domain controllers become target domain controllers, thereby performing data acquisition and obtaining the first data file corresponding to each target domain controller. The method for obtaining the first data file can refer to the specific introduction of the aforementioned embodiment, which will not be repeated here.

[0075] Step S430: Integrate the plurality of first data files into a second data file through the CCU.

[0076] Step S440: uploading the second data file to a server, where the second data file is used by the server to perform fault analysis on the vehicle.

[0077] For detailed description of steps S430 to S440, please refer to steps S120 to S130 in the aforementioned embodiment, which will not be repeated here.

[0078] In the data processing method of the domain controller provided in the embodiment of the present application, the server will also monitor the application software data of the vehicle. When the server determines that there is an application fault in the vehicle, it will send a data collection instruction to the central domain controller, and the central domain controller will forward it to other target domain controllers, so that the target domain controller can collect data according to the data collection instruction, and then the collected first data file in the target file format will be integrated by the central domain controller and uploaded to the server, so that the server will perform fault analysis on the second data file, which can avoid the situation where the application software on the domain controller is abnormal but data collection is not automatically performed, thereby improving the accuracy of application software fault identification, and further improving the accuracy of fault analysis.

[0079] See also Figure 5 , which shows a structural block diagram of a data processing device 200 of a domain controller provided in an embodiment of the present application. The data processing device 200 of the domain controller is applied to a vehicle, and the data processing device 200 of the domain controller includes: a first data file acquisition module 210, which is used to acquire the first data file corresponding to each target domain controller through the central domain controller CCU, the target domain controller refers to the domain controller other than the CCU in the vehicle, the first data file includes the fault data collected by the target domain controller after the application fault occurs in the vehicle, and the file format of the first data file corresponding to each target domain controller is the target file format; a second data file determination module 220, which is used to integrate multiple first data files into a second data file through the CCU; a fault analysis module 230, which is used to upload the second data file to a server, and the second data file is used by the server to perform fault analysis on the vehicle.

[0080] In some embodiments of the present application, the first data file acquisition module 210 includes: an initial first data file acquisition unit, used to collect fault data in each target domain controller as an initial first data file through each target domain controller; a conversion unit, used to convert the file format of the initial first data file into the target file format according to a preset conversion method through each target domain controller, to obtain a first data file corresponding to the initial first data file; a first data file acquisition unit, used to acquire the first data file corresponding to each target domain controller through the CCU.

[0081] In some embodiments of the present application, the conversion unit includes: a first encoded file acquisition subunit, which is used to encode the data in the initial first data file through a preprocessing component on each of the target domain controllers to obtain an encoded file as a first encoded file; and a conversion subunit, which is used to convert the file format of the first encoded file into the target file format through a preprocessing component on each of the target domain controllers to obtain a first data file corresponding to the initial first data file.

[0082] In some embodiments of the present application, the first data file acquisition module 210 includes: a data sending unit, which is used to send the initial first data file to the CCU through the target domain controller if the preprocessing component is not set on the target domain controller; a second encoded file acquisition unit, which is used to encode the data in the initial first data file through the preprocessing component on the CCU to obtain the encoded file as the second encoded file; a second encoded file conversion unit, which is used to convert the file format of the second encoded file into the target file format through the preprocessing component on the CCU to obtain the first data file corresponding to the initial first data file.

[0083] In some embodiments of the present application, the target domain controller includes multiple application software, and the first data file acquisition module 210 includes: a software data acquisition unit, used to acquire software data of all application software on the target domain controller through the target domain controller; a data file acquisition unit, used to determine that there is an application fault in the vehicle if any of the software data matches a preset fault condition, and acquire the first data file corresponding to each of the target domain controllers through the CCU.

[0084] In some embodiments of the present application, the first data file acquisition module 210 includes: a data acquisition instruction receiving unit, used to receive a data acquisition instruction sent by the server through the CCU, and the data acquisition instruction is issued when the server monitors that there is an application failure in the vehicle; a data acquisition instruction response unit, used to respond to the data acquisition instruction through the CCU to obtain the first data file corresponding to each target domain controller.

[0085] In some embodiments of the present application, the second data file determination module 220 includes: a time information acquisition unit, used to obtain the time information of each first data file through the CCU; and an integration unit, used to integrate multiple first data files into the second data file according to the time information through the CCU.

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

[0087] In several embodiments provided in the present application, the coupling between modules may be electrical, mechanical or other forms of coupling.

[0088] In addition, each functional module in each embodiment of the present application can be integrated into a processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The above integrated modules can be implemented in the form of hardware or software functional modules.

[0089] Please refer to Figure 6 , which shows a structural block diagram of a vehicle provided by an embodiment of the present application. The vehicle 100 in the present application may include one or more of the following components: a processor 110, a memory 120, and one or more applications, wherein the one or more applications may be stored in the memory 120 and configured to be executed by one or more processors 110, and the one or more programs are configured to execute the method described in the aforementioned method embodiment.

[0090] The processor 110 may include one or more processing cores. The processor 110 uses various interfaces and lines to connect various parts of the entire vehicle 100, and executes various functions and processes data of the vehicle 100 by running or executing instructions, programs, code sets or instruction sets stored in the memory 120, and calling data stored in the memory 120. Optionally, the processor 110 can be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), and programmable logic array (PLA). The processor 110 can integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), and a modem. Among them, the CPU mainly processes the operating system, user interface, and application programs; the GPU is responsible for rendering and drawing display content; and the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 110, but may be implemented separately through a communication chip.

[0091] The memory 120 may include a random access memory (RAM) or a read-only memory (ROM). The memory 120 may be used to store instructions, programs, codes, code sets or instruction sets. The memory 120 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for implementing at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the following various method embodiments, etc. The data storage area may also store data created by the vehicle 100 during use (such as a phone book, audio and video data, chat record data), etc.

[0092] A computer-readable storage medium is also provided in an embodiment of the present application. A program code is stored in the computer-readable storage medium. The program code can be called by a processor to execute the method described in the above method embodiment.

[0093] The computer-readable storage medium may be an electronic memory such as a flash memory, an EEPROM (electrically erasable programmable read-only memory), an EPROM, a hard disk, or a ROM. Optionally, the computer-readable storage medium includes a non-transitory computer-readable storage medium. The computer-readable storage medium has storage space for program codes that execute any of the method steps in the above method. These program codes can be read from or written to one or more computer program products. The program code can be compressed, for example, in an appropriate form.

[0094] A computer program product is also provided in an embodiment of the present application. The computer program product includes program code, and the program code can be called by a processor to execute the method described in the above method embodiment.

[0095] In summary, the solution provided by the present application is that when there is an application anomaly in the vehicle, each target domain controller converts the collected fault data into the same target file format to obtain a first data file, and the central domain controller integrates multiple first data files into a second data file and uploads it to the server. Since the vehicle unifies the fault data of each domain controller into a target file format and then merges them into one data file when collecting fault data, the server can only perform fault analysis on the integrated second data file, without having to analyze data files of different file formats, thereby improving the analysis efficiency of fault analysis.

[0096] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A data processing method of a domain controller, characterized in that: The method comprises: Acquire, through a central domain controller CCU, a first data file corresponding to each target domain controller, wherein the target domain controller refers to a domain controller other than the CCU in the vehicle, the first data file includes fault data collected by the target domain controller after the application fault occurs in the vehicle, and the file format of the first data file corresponding to each target domain controller is a file format converted into a target file format; integrating, by the CCU, a plurality of the first data files into a second data file; The second data file is uploaded to a server, and the second data file is used by the server to perform fault analysis on the vehicle.

2. The method according to claim 1, characterized in that The step of obtaining the first data file corresponding to each target domain controller through the central domain controller CCU includes: Collecting fault data in each of the target domain controllers as an initial first data file; By each of the target domain controllers, according to a preset conversion method, converting the file format of the initial first data file into the target file format, so as to obtain a first data file corresponding to the initial first data file; The first data file corresponding to each of the target domain controllers is obtained through the CCU.

3. The method according to claim 2, characterized in that The converting the file format of the initial first data file into the target file format according to a preset conversion method by each of the target domain controllers to obtain a first data file corresponding to the initial first data file includes: Encoding the data in the initial first data file through a preprocessing component on each of the target domain controllers to obtain an encoded file as a first encoded file; The file format of the first encoded file is converted into the target file format through the preprocessing component on each of the target domain controllers to obtain a first data file corresponding to the initial first data file.

4. The method according to claim 2, characterized in that After collecting the fault data in each target domain controller as an initial first data file through each target domain controller, the method further includes: If the pre-processing component is not provided on the target domain controller, sending the initial first data file to the CCU through the target domain controller; Encoding the data in the initial first data file through a preprocessing component on the CCU to obtain an encoded file as a second encoded file; The file format of the second encoded file is converted into the target file format through the preprocessing component on the CCU to obtain the first data file corresponding to the initial first data file.

5. The method according to claim 1, characterized in that The target domain controller includes a plurality of application software, and obtaining the first data file corresponding to each target domain controller through the central domain controller CCU includes: Obtaining, through the target domain controller, software data of all application software on the target domain controller; If any of the software data matches the preset fault condition, it is determined that an application fault exists in the vehicle, and the first data file corresponding to each target domain controller is obtained through the CCU.

6. The method according to claim 1, characterized in that The step of obtaining the first data file corresponding to each target domain controller through the central domain controller CCU includes: Receiving, through the CCU, a data collection instruction sent by the server, wherein the data collection instruction is sent by the server when the server monitors that an application failure exists in the vehicle; The CCU responds to the data acquisition instruction to obtain the first data file corresponding to each target domain controller.

7. The method according to any one of claims 1 to 6, characterized in that: The integrating the plurality of the first data files into a second data file by the CCU includes: Acquiring, by the CCU, time information of each of the first data files; Through the CCU, multiple first data files are integrated into the second data file according to the time information.

8. A data processing device of a domain controller, characterized in that: include: A first data file acquisition module is used to acquire a first data file corresponding to each target domain controller through a central domain controller CCU, wherein the target domain controller refers to a domain controller other than the CCU in the vehicle, and the first data file includes fault data collected by the target domain controller after the application fault occurs in the vehicle, and the file format of the first data file corresponding to each target domain controller is a file format converted into a target file format; A second data file determination module, configured to integrate a plurality of the first data files into a second data file through the CCU; The fault analysis module is used to upload the second data file to a server, and the second data file is used by the server to perform fault analysis on the vehicle.

9. An electronic device, characterized in that: include: one or more processors; Memory; One or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs are configured to execute the method according to any one of claims 1-7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores program codes, which can be called by a processor to execute the method according to any one of claims 1 to 7.

11. A computer program product, characterized in that The computer program product includes program code, and the program code can be called by a processor to execute the method according to any one of claims 1 to 7.

Images