A method, device and storage medium for analyzing custom storage data of an automobile

Abstract

The present application relates to a method, device and storage medium for analyzing automotive custom storage data. By utilizing the characteristics that in-vehicle electronic modules communicate using the CAN protocol and have CAN interfaces, based on the CAN-based DBC protocol, data matching the data in the constructed data feature matching library is simulated and sent to the in-vehicle electronic module to be analyzed. By extracting the conversion data simulated and written by the electronic module and matching it with the data in the feature matching library, the specific meaning of the custom data field can be determined in reverse, which can solve the problem of difficult determination of in-vehicle electronic custom data fields.

Description

Technical Field

[0001] The present application relates to the technical field of electronic data forensics, and in particular, to a method, device, and storage medium for analyzing automotive custom storage data. Background Art

[0002] With the development of automotive electronic technology, as a complex electronic system with Internet functions, the in-vehicle system of an automobile is equipped with more and more electronic modules internally. A large amount of high-value electronic data is generated and stored by various modules. Especially for intelligent connected vehicles and new energy vehicles, this provides favorable conditions for automotive electronic data forensics. However, currently, the storage of many automotive electronic data is not standard CAN messages, but based on manufacturer customization. Without the constraint of standard specifications, usually CAN data is converted and specially processed, etc., making it difficult to conduct forensic analysis on automotive electronic data. Summary of the Invention

[0003] Aiming at the problem that currently, the storage of many automotive electronic data is not standard CAN messages, but based on manufacturer customization. Without the constraint of standard specifications, usually CAN data is converted and specially processed, etc., making it difficult to conduct forensic analysis on automotive electronic data, the present application proposes a method, device, and storage medium for analyzing automotive custom storage data.

[0004] In the first aspect, the present application proposes a method for analyzing automotive custom storage data, including the following steps:

[0005] S1: Extract the original custom data set BK from the electronic data module of the automobile used to store custom data;

[0006] S2: Construct a feature data matching library TB for body event data with specific features according to the manufacturer's DBC format;

[0007] S3: Use the feature data matching library TB to simulate CAN data and send it to the in-vehicle electronic module to form a new custom data set ND in the electronic data module;

[0008] S4: Analyze and convert the new custom data set ND to obtain a set CVD of body events after reverse conversion and corresponding event mapping tag values;

[0009] S5: Use the feature data matching library TB to match the data in the set CVD, and combine the DBC protocol to identify the specific meaning of the custom data corresponding to the fields matched in the CVD, denoted as the set PD;

[0010] S6: Use the set PD to perform reference data parsing on the original custom data set BK to parse out the specific content of the original custom data fields.

[0011] Preferably, the S1 specifically includes:

[0012] S11: Extract the stored data from the vehicle-mounted electronic data module and record it as the set MD;

[0013] S12: Obtain the DBC protocol file corresponding to the CAN communication message of the vehicle-mounted electronic data module;

[0014] S13: Analyze the stored data MD, and filter out the custom data of non-standard messages according to the manufacturer's DBC protocol and CAN message characteristics, and record it as BK.

[0015] Preferably, the S3 includes:

[0016] S31: Extract the specific characteristic body event data from TB, and simulate and construct a CAN message according to the DBC protocol, and record it as CD;

[0017] S32: Power on the vehicle-mounted electronic module, select a CAN message from CD for data transmission and write it into the vehicle-mounted electronic module storage, so as to form a new custom data set ND in the electronic data module.

[0018] Preferably, the S6 specifically includes:

[0019] S61: Perform reverse conversion on the custom data BK to extract the body event and the body event mapping tag value, and record it as CBK;

[0020] S62: Perform reference data parsing on the data CBK according to the event mapping tag value in PD to parse out the specific meaning of the custom data field.

[0021] In a second aspect, the present application also proposes an automobile custom storage data analysis device, which is characterized in that: the device includes:

[0022] A custom data extraction module, configured to extract the original custom data set BK from the electronic data module of the vehicle used to store custom data;

[0023] A characteristic data matching library construction module, configured to construct a characteristic data matching library TB corresponding to the body event data with specific characteristics according to the manufacturer's DBC format;

[0024] A simulated CAN data sending module, configured to use the characteristic data matching library TB to simulate CAN data sending to the vehicle-mounted electronic module, so as to form a new custom data set ND in the electronic data module;

[0025] An analysis and conversion module, configured to analyze and convert the new custom data set ND to obtain a set CVD containing the reverse-converted body event and the corresponding event mapping tag value;

[0026] A data matching module, configured to match data in the collection CVD by using the feature data matching library TB, and combine the DBC protocol to identify the specific meaning of the custom data corresponding to the fields matched in CVD, denoted as the collection PD;

[0027] A data parsing module, configured to perform reference data parsing on the original custom data collection BK by using the collection PD to parse out the specific content of the original custom data fields.

[0028] Preferably, extracting the original custom data collection BK from the electronic data module for storing custom data in the vehicle specifically includes:

[0029] Extracting the stored data from the in-vehicle electronic data module, denoted as the collection MD;

[0030] Obtaining the DBC protocol file corresponding to the CAN communication message of the in-vehicle electronic data module;

[0031] Analyzing the stored data MD, and filtering out the custom data of non-standard messages according to the manufacturer's DBC protocol and CAN message characteristics, denoted as BK.

[0032] Preferably, simulating the CAN data by using the feature data matching library TB and sending it to the in-vehicle electronic module to form a new custom data collection ND in the electronic data module includes:

[0033] Extracting specific feature body event data from TB, and simulating and constructing a CAN message according to the DBC protocol, denoted as CD;

[0034] Powering on the in-vehicle electronic module, selecting a CAN message from CD for data sending and writing it into the in-vehicle electronic module storage to form a new custom data collection ND in the electronic data module.

[0035] Preferably, performing reference data parsing on the original custom data collection BK by using the collection PD to parse out the specific content of the original custom data fields specifically includes:

[0036] Performing reverse conversion on the custom data BK to extract the body event and the body event mapping tag value, denoted as CBK;

[0037] Performing reference data parsing on the data CBK according to the event mapping tag value in PD to parse out the specific meaning of the custom data fields.

[0038] In a third aspect, the present application also proposes an electronic device, including:

[0039] One or more processors;

[0040] A storage device for storing one or more programs;

[0041] When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in the first aspect.

[0042] In a fourth aspect, the present application also proposes a computer-readable storage medium, on which a computer program is stored, characterized in that when the program is executed by a processor, it implements the method as described in the first aspect.

[0043] In summary, the present application at least includes the following beneficial technical effects:

[0044] 1. Based on the characteristics that the automotive in-vehicle system uses the CAN protocol for data transmission and the automotive electronic module has a CAN interface, the present application proposes a method for analyzing automotive custom storage data. This method simulates and sends specific CAN message data with certain characteristics through the CAN interface of an independent electronic module and extracts the stored data, and conducts comprehensive comparison and analysis by combining the simulated characteristic data, DBC file, conversion data format analysis, etc., and finally determines the definition of the custom storage data fields.

[0045] 2. Utilizing the characteristics that the in-vehicle electronic module uses the CAN protocol for communication and has a CAN interface, on the basis of the CAN-based DBC protocol, by simulating and sending the data in the constructed data feature matching library to the in-vehicle electronic module to be analyzed, and by extracting the conversion data simulated and written by the electronic module and matching it with the data in the feature matching library to reversely determine the specific meaning of the custom data fields, it can solve the problem that it is difficult to determine the custom data fields of in-vehicle electronics.

[0046] 3. Utilizing the characteristic that the in-vehicle electronic module uses the CAN protocol for communication, it can simulate and send specific characteristic data through the CAN interface to match and identify the data stored in the electronic module, and solve the problem that it is difficult to analyze the custom data stored in the in-vehicle electronic module. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] The drawings are included to provide a further understanding of the embodiments and are incorporated into and constitute a part of this specification. The drawings illustrate the embodiments and are used in conjunction with the description to explain the principles of the present application. Other embodiments and many of the expected advantages of the embodiments will be readily recognized as they become better understood by reference to the following detailed description. The elements of the drawings are not necessarily to scale with each other. The same reference numerals refer to corresponding like parts.

[0048] Figure 1 It is a flowchart of a method for analyzing automotive custom storage data of the present application.

[0049] Figure 2 It is a schematic diagram of an automotive bus structure.

[0050] Figure 3 It is a structural block diagram of an in-vehicle T-Box.

[0051] Figure 4 It is a schematic diagram of the DBC format.

[0052] Figure 5 It is a schematic diagram of custom data analysis.

[0053] Figure 6 It is a schematic diagram of a specific embodiment of an automotive custom storage data analysis method that can be applied to this application.

[0054] Figure 7 It is a schematic diagram of the module structure of an automotive custom storage data analysis device in an embodiment of this application.

[0055] Figure 8 It is a schematic diagram of the structure of a computer system of an electronic device suitable for implementing the embodiments of this application. Detailed implementation manners

[0056] The following further elaborates on this application in conjunction with the accompanying drawings and embodiments. It can be understood that the specific embodiments described herein are merely for explaining the relevant invention and not for limiting the invention. Additionally, it should be noted that for the sake of description, only the parts related to the relevant invention are shown in the accompanying drawings.

[0057] It should be noted that, without conflict, the embodiments in this application and the features in the embodiments can be combined with each other. The following will elaborate on this application in detail with reference to the accompanying drawings and embodiments.

[0058] Figure 1 The flowchart of an automotive custom storage data analysis method of this application is shown. Refer to Figure 1 , and this method specifically includes the following steps:

[0059] S1: Extract the original custom data set BK from the electronic data module of the vehicle used to store custom data;

[0060] The specific content of S1 includes:

[0061] S11: Extract the stored data from the in-vehicle electronic data module and denote it as set MD;

[0062] S12: Obtain the DBC protocol file corresponding to the CAN communication message of the in-vehicle electronic data module;

[0063] S13: Analyze the stored data MD, and filter out the custom data of non-standard messages according to the manufacturer's DBC protocol and CAN message characteristics, denoted as BK.

[0064] S2: Construct a feature data matching library TB for the body event data with specific characteristics according to the manufacturer's DBC format;

[0065] S3: Use the feature data matching library TB to simulate CAN data and send it to the in-vehicle electronic module to form a new set of custom data ND in the electronic data module;

[0066] The S3 includes:

[0067] S31: Extract the body event data with specific characteristics from TB, and simulate and construct a CAN message according to the DBC protocol, denoted as CD;

[0068] S32: Power on the in-vehicle electronic module, select a CAN message from CD for data sending and writing into the storage of the in-vehicle electronic module to form a new set of custom data ND in the electronic data module.

[0069] S4: Analyze and transform the new set of custom data ND to obtain a set CVD of body events after reverse transformation and corresponding event mapping tag values;

[0070] S5: Use the feature data matching library TB to match with the data in the set CVD, and combine the DBC protocol to identify the specific meaning of the custom data corresponding to the fields matched in CVD, denoted as the set PD;

[0071] S6: Use the set PD to perform reference data parsing on the original set of custom data BK to parse out the specific content of the original custom data fields.

[0072] The S6 specifically includes:

[0073] S61: Perform reverse transformation on the custom data BK to extract the body event and the body event mapping tag value, denoted as CBK;

[0074] S62: Perform reference data parsing on the data CBK according to the event mapping tag value in PD to parse out the specific meaning of the custom data field.

[0075] In a specific embodiment, the following will specifically describe a method for analyzing automotive custom storage data of the present application:

[0076] The present application discloses a method for analyzing custom storage data of an automobile. This method simulates the transmission of specific CAN message data with certain characteristics through the CAN interface of an independent electronic module and extracts the stored data, and conducts comprehensive analysis and comparison by combining the simulated characteristic data, DBC file, conversion of data format analysis, etc., and finally determines the definition of the custom storage data field.

[0077] As Figure 2 shown in the automotive bus structure diagram, automobiles generally use the CAN international standard serial communication protocol for communication. There are many automotive electronic modules mounted on the automotive bus, such as automotive electronic control units, infotainment navigation systems, driving recorders, in-vehicle T-Boxes, etc.

[0078] As Figure 3 shown in the T-Box structure block diagram, taking the in-vehicle T-box as an example, the module sends and receives CAN messages on the bus through the CAN interface for data interaction. The received CAN messages are processed and converted by the internal MCU of the electronic module and stored in an external storage medium. Since the stored data has no standard specification, most of it is stored in the manufacturer's custom format.

[0079] As Figure 4 shown in the DBC format schematic diagram, CAN DBC refers to the database of CAN messages, which is equivalent to a decoding book. Different automobile manufacturers have corresponding DBC protocols, including the CAN ID of the current signal message, the position where the signal appears in the CAN message, the byte order of the signal, the conversion details of the signal, and the unit of the signal. The data types communicated through the CAN bus can be read and understood using a DBC file. DBC is the most commonly used method for processing the identification and conversion of 8-byte hexadecimal CAN messages and raw CAN data. The data in a CAN frame can be divided into 8 single-byte values, 64 single-bit values, a 64-bit value, or any combination of these values. The data field can contain at most 8 bytes of data. A CAN frame can contain 0 to 64 individual signals (for 64 channels, they will all be binary).

[0080] As Figure 5 shown in the schematic diagram of analyzing custom storage data of an automobile in an embodiment, for the situation where the custom data of an automobile cannot be analyzed. First, according to the DBC protocol format of the automobile manufacturer, simulate the transmission of CAN data with certain characteristics to the electronic data module, and store the transmitted characteristic CAN data in the characteristic matching library; secondly, extract the custom data transmitted by the MCU conversion process from the electronic data module; finally, analyze the converted data and match it with the CAN database with specific characteristics to identify the CAN type to which the custom data belongs, and conduct analysis in combination with the DBC protocol format of the automobile manufacturer to finally realize the definition of the custom data field.

[0081] In a specific embodiment, the following conceptual assumptions are first made:

[0082] 1) Assume that MD = {MD1, MD2, MD3,..., MDn} represents the set of data stored in in-vehicle electronic modules, where each element MDi represents the data stored in an in-vehicle electronic module;

[0083] 2) Assume that BK = {BK1, BK2, BK3,..., BKn} represents the set of original custom data, where each element BKi represents a custom field;

[0084] 3) Assume that CBK = {CBK1, CBK2, CBK3,..., CBKn} represents the set of data after reverse conversion of the BK data analysis, where each element CBKi contains the vehicle body events and event mapping tag values after reverse conversion of the custom data;

[0085] 4) Assume that TB = {TB1, TB2, TB3,..., TBn} represents the set of a series of vehicle body events constructed according to the manufacturer's DBC protocol with specific characteristic data, where each element TBi corresponds to a specific field in the CAN message, and its series of data has identifiable characteristics;

[0086] 5) Assume that CD = {CD1, CD2, CD3,..., CDn} represents the set of a series of CAN messages constructed according to the manufacturer's DBC protocol, where each element CDi contains the vehicle body event data of TB;

[0087] 6) Assume that ND = {ND1, ND2, ND3,..., NDn} represents the set of custom data stored in the electronic module after CD is simulated and sent;

[0088] 7) Assume that CVD = {CVD1, CVD2, CVD3,..., CVDn} represents the set after ND is reverse-converted through format analysis, where each element CVDi contains the vehicle body events after reverse conversion and the corresponding event mapping tag values;

[0089] 8) Assume that PD = {PD1, PD2, PD3,..., PDn} represents the set of custom fields matched by TB and CVD, where each element PDi contains the characteristic data and event mapping tag values in TB;

[0090] In a specific embodiment, with reference to Figure 6 , the method for analyzing automotive custom storage data can be executed according to the following steps:

[0091] 1) Extract the stored data from the in-vehicle electronic module, denoted as MD;

[0092] 2) Obtain the DBC protocol file corresponding to the CAN communication message of the in-vehicle electronic module;

[0093] 3) Analyze the stored data MD, and filter out the custom data of non-standard messages according to the manufacturer's DBC protocol and CAN message characteristics, denoted as BK;

[0094] 4) Construct body event data with specific characteristics according to the DBC protocol and add it to the feature data matching library, denoted as TB;

[0095] 5) Extract the body event data with specific characteristics from TB, and simulate the construction of CAN messages according to the DBC protocol, denoted as CD;

[0096] 6) Power on the in-vehicle electronic module, select CAN messages from CD for data sending and write them into the storage of the in-vehicle electronic module;

[0097] 7) Extract the newly written custom data from the in-vehicle electronic module, denoted as ND;

[0098] 8) Analyze and convert the custom data ND, denoted as CVD;

[0099] 9) Match the data in the feature data matching library TB with the data in CVD, and combine the DBC protocol to identify the specific meaning of the custom data corresponding to the fields matched in CVD, denoted as PD;

[0100] 10) Perform reverse conversion on the custom data BK to extract the body event and the body event mapping tag value, denoted as CBK;

[0101] 11) Perform reference data parsing on the data CBK according to the event mapping tag value in PD to parse the specific meaning of the custom data field;

[0102] 12) End this process.

[0103] A method for analyzing automotive custom storage data in this application utilizes the characteristics that the in-vehicle electronic module communicates using the CAN protocol and has a CAN interface. Based on the CAN-based DBC protocol, by simulating the transmission of data in the constructed feature matching library to the in-vehicle electronic module to be analyzed, and by matching and analyzing the converted data simulated and written by the electronic module with the data in the feature matching library to reversely determine the specific meaning of the custom data field, it can solve the problem of difficult determination of the custom data field of the in-vehicle electronics.

[0104] For further reference Figure 7 , as an implementation of the above method, this application provides an embodiment of an automotive custom storage data analysis device. This device embodiment is related to Figure 1The method embodiments shown correspond to a device that can be specifically applied to various electronic devices.

[0105] Referring to Figure 7 , an automotive custom storage data analysis device includes:

[0106] A custom data extraction module 101 configured to extract an original custom data set BK from an electronic data module of the vehicle used to store custom data;

[0107] Among them, the extraction of the original custom data set BK from the electronic data module of the vehicle used to store custom data specifically includes:

[0108] Extract stored data from the in-vehicle electronic data module, denoted as set MD;

[0109] Obtain the DBC protocol file corresponding to the CAN communication message of the in-vehicle electronic data module;

[0110] Analyze the stored data MD, and filter out the custom data of non-standard messages according to the manufacturer's DBC protocol and CAN message characteristics, denoted as BK

[0111] A feature data matching library construction module 102 configured to construct a feature data matching library TB for body event data with specific features according to the manufacturer's DBC format;

[0112] A simulated CAN data sending module 103 configured to use the feature data matching library TB to simulate sending CAN data to the in-vehicle electronic module to form a new custom data set ND in the electronic data module;

[0113] Among them, the use of the feature data matching library TB to simulate sending CAN data to the in-vehicle electronic module to form a new custom data set ND in the electronic data module includes:

[0114] Extract specific feature body event data from TB, and simulate and construct a CAN message according to the DBC protocol, denoted as CD;

[0115] Power on the in-vehicle electronic module, select CAN messages from CD for data sending and writing into the in-vehicle electronic module storage to form a new custom data set ND in the electronic data module;

[0116] An analysis and conversion module 104 configured to analyze and convert the new custom data set ND to obtain a set CVD containing the body events after reverse conversion and the corresponding event mapping tag values;

[0117] The data matching module 105 is configured to match data in the collection CVD with the feature data matching library TB, and identify the specific meaning of the custom data corresponding to the fields matched in the CVD in combination with the DBC protocol, denoted as the collection PD;

[0118] The data parsing module 106 is configured to perform reference data parsing on the original custom data set BK by using the collection PD to parse out the specific content of the original custom data fields.

[0119] Among them, the performing reference data parsing on the original custom data set BK by using the collection PD to parse out the specific content of the original custom data fields specifically includes:

[0120] Performing reverse conversion on the custom data BK to extract the body events and the body event mapping tag values, denoted as CBK;

[0121] Performing reference data parsing on the data CBK according to the event mapping tag values in the PD to parse out the specific meaning of the custom data fields.

[0122] Next, refer to Figure 8 , which shows a schematic structural diagram of a computer system 200 of an electronic device suitable for implementing the embodiments of the present application. Figure 8 The shown electronic device is merely an example and should not impose any limitation on the functions and usage scope of the embodiments of the present application.

[0123] As Figure 8 shown, the computer system 200 includes a central processing unit (CPU) 201, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 202 or the program loaded from the storage section 208 into the random access memory (RAM) 203. In the RAM 203, various programs and data required for the operation of the system 200 are also stored. The CPU 201, ROM 202, and RAM 203 are connected to each other through a bus 204. The input / output (I / O) interface 205 is also connected to the bus 204.

[0124] The following components are connected to the I / O interface 205: an input section 206 including a keyboard, a mouse, etc.; an output section 207 including such as a liquid crystal display (LCD), etc. and a speaker; a storage section 208 including a hard disk, etc.; and a communication section 209 including a network interface card such as a LAN card, a modem, etc. The communication section 209 performs communication processing via a network such as the Internet. The drive 220 is also connected to the I / O interface 205 as needed. A removable medium 211, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 220 as needed so that the computer program read from it can be installed into the storage section 208 as needed.

[0125] In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, an embodiment of the present disclosure includes a computer program product that includes a computer program carried on a computer-readable medium, and the computer program includes program code for performing the methods shown in the flowcharts. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 209 and / or installed from the removable medium 211. When the computer program is executed by the central processing unit (CPU) 201, the above-described functions defined in the method of the present application are performed.

[0126] As another aspect, the present application also provides a computer-readable storage medium, which may be included in the electronic device described in the above embodiments; or may exist separately without being assembled into the electronic device. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed by the electronic device, the electronic device is caused to perform the method as Figure 1 shown therein.

[0127] It should be noted that the computer-readable storage medium described in this application can be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this application, a computer-readable storage medium can be any tangible medium that contains or stores a program, which can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in a baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium can also be any computer-readable storage medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on a computer-readable storage medium can be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0128] The computer program code for performing the operations of this application can be written in one or more programming languages or combinations thereof. The programming languages include object-oriented programming languages such as Java, Smalltalk, C++, and also include conventional procedural programming languages such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, executed as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (for example, by using an Internet service provider to connect through the Internet).

[0129] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagram may represent a module, a segment of a program, or a part of code that contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than that marked in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, as well as combinations of blocks in the block diagram and / or flowchart, may be implemented by a dedicated hardware-based system that performs the specified functions or operations, or may be implemented by a combination of dedicated hardware and computer instructions.

[0130] The specific embodiments of the present application have been described above, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed in the present application can easily think of changes or substitutions, which should all be covered within the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

[0131] In the description of the present application, it should be understood that the orientation or positional relationships indicated by terms such as "upper", "lower", "inner", "outer", etc. are based on the orientation or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present application and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be construed as a limitation to the present application. The term 'comprising' does not exclude the presence of elements or steps not listed in the claims. The article 'a' or 'an' preceding an element does not exclude the presence of a plurality of such elements. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage. Any reference signs in the claims should not be construed as limiting the scope.

Claims

1. A method for analyzing custom storage data of an automobile, characterized in that: The method includes the following steps: S1: Extract the original custom data set BK from the electronic data module of the vehicle used to store custom data; S2: Construct a feature data matching library TB for the body event data with specific features according to the manufacturer's DBC format; S3: Use the feature data matching library TB to simulate CAN data and send it to the vehicle-mounted electronic module to form a new custom data set ND in the electronic data module; S4: Analyze and transform the new custom data set ND to obtain a set CVD of body events after reverse transformation and their corresponding event mapping tag values; S5: Use the feature data matching library TB to match the data in the set CVD, and combine the DBC protocol to identify the specific meaning of the custom data corresponding to the fields matched in CVD, denoted as the set PD; S6: Use the set PD to perform reference data parsing on the original custom data set BK to parse the specific content of the original custom data fields, specifically including: S61: Perform reverse transformation on the custom data BK to extract the body events and body event mapping tag values, denoted as CBK; S62: Perform reference data parsing on the data CBK according to the event mapping tag values in PD to parse the specific meaning of the custom data fields.

2. The automotive custom storage data analysis method according to claim 1, wherein: The specific content of S1 includes: S11: Extract the stored data from the vehicle-mounted electronic data module, denoted as the set MD; S12: Obtain the DBC protocol file corresponding to the CAN communication message of the vehicle-mounted electronic data module; S13: Analyze the stored data MD, and filter out the custom data of non-standard messages according to the manufacturer's DBC protocol and CAN message features, denoted as BK.

3. A method for analyzing custom storage data of an automobile according to claim 1, characterized in that: The said S3 includes: S31: Extract the body event data with specific features from TB, and simulate and construct a CAN message according to the DBC protocol, denoted as CD; S32: Power on the vehicle-mounted electronic module, select CAN messages from CD for data sending and write them into the storage of the vehicle-mounted electronic module to form a new custom data set ND in the electronic data module.

4. An automobile custom storage data analysis device, characterized in that: The device includes: a custom data extraction module configured to extract the original custom data set BK from the electronic data module of the vehicle used to store custom data; a feature data matching library construction module configured to construct a feature data matching library TB for the body event data with specific features according to the manufacturer's DBC format; a simulated CAN data sending module configured to use the feature data matching library TB to simulate CAN data and send it to the vehicle-mounted electronic module to form a new custom data set ND in the electronic data module; an analysis and transformation module configured to analyze and transform the new custom data set ND to obtain a set CVD of body events after reverse transformation and their corresponding event mapping tag values; a data matching module configured to use the feature data matching library TB to match the data in the set CVD, and combine the DBC protocol to identify the specific meaning of the custom data corresponding to the fields matched in CVD, denoted as the set PD; A data parsing module, configured to perform reference data parsing on the original custom data set BK by using the set PD to parse out the specific content of the original custom data fields, specifically including: Performing reverse conversion on the custom data BK to extract the vehicle body events and the vehicle body event mapping tag values, denoted as CBK; Performing reference data parsing on the data CBK according to the event mapping tag values in PD to parse out the specific meaning of the custom data fields.

5. An automotive custom storage data analysis device according to claim 4, characterized in that: The extracting the original custom data set BK from the electronic data module of the vehicle for storing custom data specifically includes: extracting the stored data from the in-vehicle electronic data module, denoted as the set MD; Obtaining the DBC protocol file corresponding to the CAN communication message of the in-vehicle electronic data module; Analyzing the stored data MD, and filtering out the custom data of the non-standard message according to the manufacturer DBC protocol and the CAN message characteristics, denoted as BK.

6. The automotive custom storage data analysis device according to claim 4, characterized in that: The simulating the CAN data and sending it to the in-vehicle electronic module by using the feature data matching library TB to form a new custom data set ND in the electronic data module includes: extracting the specific feature vehicle body event data from TB, and simulating and constructing the CAN message according to the DBC protocol, denoted as CD; Powering on the in-vehicle electronic module, selecting the CAN message from CD for data sending and writing it into the storage of the in-vehicle electronic module to form a new custom data set ND in the electronic data module.

7. An electronic device, comprising: One or more processors; A storage device for storing one or more programs; When the one or more programs are executed by the one or more processors, enabling the one or more processors to implement the method according to any one of claims 1-3.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, The program, when executed by the processor, implements the method according to any one of claims 1-3.

Images