KR20240039462A - method of analyzing and gathering vehicle data for CAN DataBase - Google Patents

Abstract

The present invention relates to vehicle data analysis and collection technology that can effectively perform CAN communication protocol analysis to build a CAN database necessary for the design of vehicle devices linked to CAN communication. According to the present invention, there is an advantage of effectively performing CAN communication protocol analysis for designing automotive electronic devices. In particular, according to the present invention, aftermarket companies can effectively build a CAN database for new vehicles even if they are not provided with detailed specifications of the CAN communication protocol from the OEM, allowing them to quickly design aftermarket products for vehicles and improve product quality. This has the advantage of improving the competitiveness of aftermarket products and protecting consumer rights.

Description

Method of analyzing and gathering vehicle data for CAN database {method of analyzing and gathering vehicle data for CAN DataBase}

The present invention relates to vehicle data analysis and collection technology that can effectively perform CAN communication protocol analysis to build a CAN database necessary for the design of vehicle devices linked to CAN communication.

CAN communication is generally used for internal vehicle communication. [Figure 1] is a conceptual diagram showing a general CAN communication system for vehicles.

CAN (Controller Area Network) is a standard communication standard designed to allow electronic modules to communicate with each other in a vehicle without a host computer. The vehicle's electronic control unit (ECU), such as the engine controller 10, transmission controller 20, brake controller 30, and steering controller 40, communicates using the CAN protocol. In addition, various peripheral devices (50 to 70) of the vehicle, such as navigation devices, black box devices, head-up display (HUD) devices, and surround view monitoring (SVM) devices, also exchange data through CAN communication.

As shown in [Figure 1], in CAN communication, a CAN bus is formed by two twisted pair wires, and a plurality of nodes (10 to 70) are connected in parallel to this CAN bus. In the CAN communication protocol, each node (10 to 70) broadcasts and transmits messages to the CAN bus and selectively receives messages it needs from the CAN bus.

[Figure 2] is a diagram showing the internal structure of a CAN message according to the CAN communication protocol.

Each node (10 to 70) transmits a message containing its CAN ID and CAN Data, but the specific details of the CAN message are slightly different for each company (OEM company). However, the detailed specifications of the CAN message are not disclosed to external aftermarket companies due to the company's security concerns.

Accordingly, whenever a new vehicle is released, aftermarket companies acquire the vehicle and directly analyze and collect the CAN communication protocol that occurs in the vehicle. Based on the analysis results of this CAN communication protocol, specialized vehicle interlocking functions for the vehicle are implemented in the company's aftermarket products such as HUD, navigation, black box, etc.

[Figure 3] is an example diagram showing a configuration for collecting vehicle data by analyzing the CAN communication protocol in the prior art.

Referring to Figure 3, the analysis target vehicle 100 and the analysis engineer's computer 200 are connected, for example, through an OBD (On-board diagnostics) connector 101. CAN protocol analysis software is running on the analysis engineer's computer 200. The analysis engineer's computer 200 acquires messages passing through the CAN bus, and CAN protocol analysis software analyzes the CAN messages obtained in this way.

In analyzing vehicle data, the skills of the CAN protocol analysis engineer as well as the vehicle to be analyzed (100) and the analysis engineer's computer (200) are very important. CAN protocol analysis engineers analyze numerous data from CAN communications and extract useful information. In general, the OEM company's existing CAN database (CAN communication protocol database) is referred to or the vehicle 100 to be analyzed is operated here and there (e.g., transmission operation, brake operation) to find data values that change in the process.

Through analysis of these CAN messages, the computer 200 builds a CAN database (DB). The CAN database is a database that collects information contained in CAN messages for each node (10 to 70). The CAN database includes specific field specifications of CAN messages transmitted and received by each node (10 to 70). For example, information on how each bit of the CAN Data field of a CAN message is filled in response to vehicle speed, vehicle transmission gear status, wiper operation status, etc. is built into a CAN database.

[Figure 4] is an example of the CAN Data field specifications of a vehicle CAN message, and [Figure 5] is an example of a vehicle CAN database.

[Figure 4] is an example of the CAN Data field specifications of a vehicle CAN message and specifically shows how information about the vehicle speed and vehicle gear status of the vehicle instrument panel (cluster) is reflected in the CAN Data field.

[Figure 5] is an example diagram of a vehicle CAN database and specifically shows signal specifications for each CAN message transmitted and received by one node (e.g., 20). Referring to [Figure 5], in processing the data value included in the CAN message, various factors are discussed, such as how many bits of information to use (Length) and whether the data sorting order is Intel or Motorola (Byte). Order) and how much the conversion value is to be multiplied by the signal value (Factor), etc. are included. Therefore, CAN messages can be utilized only when a CAN database as shown in [Figure 5] is secured.

In general, the OEM's primary component company can manufacture products by receiving detailed specifications of the CAN communication protocol from the OEM. On the other hand, aftermarket companies do not receive detailed specifications of the CAN communication protocol from OEM companies, so in order to make aftermarket products (navigation devices, black box devices, HUD devices, SVM devices, etc.), CAN is required through the configuration shown in [Figure 3]. A CAN database must be built by analyzing the communication protocol. This process requires CAN protocol analysis engineers to manually analyze hundreds of data protocols using their experience, and through this, each aftermarket company acquired vehicle-specific CAN communication protocol information. And, when a new model is released, this exhausting process must be repeated.

Republic of Korea Patent No. 10-1088798 (2011.11.25) “Protocol message transmission method using CAN communication” Republic of Korea Patent Publication No. 10-2002-0097370 (2002.12.31) “Display device and method using CAN communication in hybrid electric vehicle”

The purpose of the present invention is to provide vehicle data analysis and collection technology that can effectively perform CAN communication protocol analysis in order to build a CAN database necessary for the design of vehicle devices linked to CAN communication.

The problem to be solved by the present invention is not limited to this matter, and other problems to be solved can be understood from the description in this specification.

In order to achieve the above object, the present invention provides a method of analyzing and collecting vehicle data performed by the analysis collection device 300 to build a CAN database necessary for the design of vehicle devices linked to CAN (Controller Area Network) communication. .

In the method of analyzing and collecting vehicle data for a CAN database according to the present invention, the data collection unit 310 of the analysis collection device 300 responds to a series of vehicle function operations at the vehicle node level for the vehicle 100 to be analyzed. A vehicle data collection step of collecting a plurality of CAN messages broadcasted to the CAN bus; A vehicle data classification step in which the data classification unit 320 of the analysis collection device 300 classifies a plurality of CAN messages collected in response to vehicle node units and vehicle function operation instructions to generate a plurality of classification groups; A vehicle data analysis step in which the data analysis unit 330 of the analysis collection device 300 acquires candidates for a CAN database for a classification group of CAN messages; Including a vehicle data verification step in which the data verification unit 340 of the analysis collection device 300 applies the acquired CAN database candidates to the test vehicle to check whether CAN messages are normally generated in response to vehicle function manipulation; It can be configured.

In the present invention, the vehicle data collection step includes guiding a series of vehicle function operations on a vehicle node basis for the vehicle 100 to be analyzed; Obtaining a plurality of CAN messages broadcast and transmitted to a CAN bus in response to a vehicle function operation applied to the analysis target vehicle 100 according to guidance on vehicle function operation; Classifying the CAN messages obtained above based on data changes before and after guidance on operating vehicle functions; It may be configured to include a step of matching and storing the plurality of CAN messages classified above with the vehicle function operation guided above.

In the present invention, the vehicle data classification step is to classify CAN messages that are maintained without data change before and after the vehicle function operation guidance in response to function maintenance operations on a vehicle node basis among the collected CAN messages to form a group of function maintenance messages. generating step; It may be configured to include: generating a function operation message group by classifying CAN messages whose data is changed before and after vehicle function operation guidance in response to a plurality of function change operations on a vehicle node basis among the collected CAN messages; there is.

In the present invention, the vehicle data analysis step includes obtaining a CAN database of a common type for a class of CAN messages by comparing a plurality of CAN databases obtained in advance with the CAN ID in the CAN message; It may be configured to include a step of receiving a CAN database for a classification of CAN messages from an analysis engineer.

Meanwhile, the computer program according to the present invention is stored in a non-volatile storage medium in order to execute the above method of analyzing and collecting vehicle data for the CAN database on the computer.

According to the present invention, there is an advantage of effectively performing CAN communication protocol analysis for designing automotive electronic devices.

In particular, according to the present invention, aftermarket companies can effectively build a CAN database for new vehicles even if they are not provided with detailed specifications of the CAN communication protocol from the OEM, allowing them to quickly design aftermarket products for vehicles and improve product quality. This has the advantage of improving the competitiveness of aftermarket products and protecting consumer rights.

[Figure 1] is a conceptual diagram showing a typical CAN communication configuration for vehicles.
[Figure 2] is a diagram showing the internal structure of a CAN message according to the CAN communication protocol.
[Figure 3] is an example diagram showing a general vehicle data collection system.
[Figure 4] is an example of the CAN Data field specifications of a vehicle CAN message.
[Figure 5] is an example diagram of a vehicle CAN database.
[Figure 6] is a diagram showing a system for analyzing and collecting vehicle data according to the present invention.
[Figure 7] is a flowchart showing the analysis and collection process of vehicle data for the CAN database according to the present invention.
[Figure 8] is a flowchart showing the vehicle data collection process in the present invention.
[Figure 9] is a conceptual diagram of an embodiment of a classification process for vehicle data in the present invention.
[Figure 10] is a flowchart showing the analysis process of vehicle data in the present invention.
[Figure 11] is a flowchart showing the verification process of vehicle data in the present invention.

Hereinafter, the present invention will be described in detail with reference to the drawings.

[FIG. 6] is a diagram showing an analysis and collection system for vehicle data according to the present invention, and [FIG. 7] is a flowchart showing the analysis and collection process of vehicle data for a CAN database according to the present invention.

Referring to [FIG. 6], in the present invention, the analysis collection device 300 is connected to the CAN bus of the analysis target vehicle 100 to obtain and analyze messages passing through the CAN bus. The analysis collection device 300 includes a data collection unit 310, a data classification unit 320, a data analysis unit 330, and a data verification unit 340, through which the vehicle data shown in [FIG. 7] is analyzed and Perform the collection process. Through this process, the analysis collection device 300 acquires a CAN database (CAN DB) for the analysis target vehicle 100.

Step (S100): First, the data collection unit 310 of the analysis collection device 300 collects a plurality of CAN messages broadcasted to the CAN bus in response to a series of vehicle function operations for the analysis target vehicle 100. do. To this end, the data collection unit 310 guides the analysis target vehicle 100 to perform various functional operations and collects CAN messages broadcast and transmitted on the CAN bus in response to the functional operations from the CAN bus.

Step (S200): Next, the data classification unit 320 of the analysis collection device 300 classifies the plurality of CAN messages collected by the data collection unit 310 in response to vehicle node units and vehicle function operation guidance.

The data classification unit 320 identifies which nodes (10 to 70) and which function operations the plurality of CAN messages obtained by the data collection unit 310 are related to, and determines a classification group for the CAN messages accordingly. For example, the data collection unit 310 selects CAN messages related to the steering controller 40 from among the plurality of CAN messages obtained. Then, for these selected CAN messages, the CAN messages are classified by identifying which vehicle steering operation they are related to.

The data classification unit 320 performs the task of classifying multiple CAN messages in response to vehicle node units and vehicle function operation instructions, and creates a plurality of classification groups from the multiple CAN messages. Each taxonomic group contains one or more CAN messages.

Step (S300): Next, the data analysis unit 330 of the analysis collection device 300 obtains candidates from the CAN database for the classification group of the CAN message. At this time, the CAN database candidate may be obtained through comparison of a plurality of CAN databases obtained in advance and the CAN ID in the CAN message, or may be obtained through CAN message analysis performed by an analysis engineer.

Step (S400): Next, the data verification unit 340 of the analysis collection device 300 applies candidates from the CAN database to the test vehicle to check whether CAN messages are normally generated in response to vehicle function manipulation. If a CAN message is generated normally, it is processed as if a CAN database has been obtained for the corresponding taxonomic group of the CAN message. Conversely, if the CAN message is not generated properly, return to (S300) and correct the error through manual analysis by an analysis engineer.

[FIG. 8] is a flowchart showing the vehicle data collection process (S100) performed by the data collection unit 310 of the analysis collection device 300 in the present invention.

Step (S110): First, the data collection unit 310 of the analysis collection device 300 guides the user through a series of vehicle function operations for the analysis target vehicle 100. At this time, it is desirable to perform vehicle function manipulation on a node-by-vehicle basis, and each node is guided to perform various functional manipulations related to the vehicle information that the analysis engineer wishes to obtain.

For example, operations of various functions related to the steering controller 40 may be guided to the user through a screen or voice. Examples of these functions include “Do not touch the steering wheel,” “Turn the steering wheel all the way to the left,” “Turn the steering wheel all the way to the right,” and “Turn the steering wheel to the center to align the wheels.” You can.

At this time, it is desirable to provide various guidance on function manipulation in order to obtain detailed information on the relationship between the function of each node and the CAN message. For example, in relation to the transmission controller 20, it is desirable to guide the vehicle's gear operation to change for each gear.

Step (S120): According to these function operation instructions, the user will authorize vehicle function operation for the analysis target vehicle 100, and in response, the steering controller 40 of the analysis target vehicle 100 operates according to the CAN communication protocol. A CAN message will be broadcasted. The data collection unit 310 of the analysis collection device 300 acquires a plurality of CAN messages broadcast and transmitted through the CAN bus.

Step (S130): The content of the CAN message broadcast from the corresponding node changes before and after operating the vehicle function for the vehicle 100 to be analyzed. Accordingly, the data collection unit 310 of the analysis collection device 300 distinguishes the plurality of CAN messages obtained above based on data changes before and after guidance on operating vehicle functions. In other words, the corresponding data change in the CAN message is treated as being caused by vehicle function manipulation.

Step (S140): Next, the data collection unit 310 of the analysis collection device 300 matches the plurality of classified CAN messages with the guided vehicle function operation and stores them. For example, the contents of the vehicle function operation (e.g., classification code) guided in (S110) and a number of CAN messages obtained in (s120) are matched and stored.

[FIG. 9] is a conceptual diagram of an embodiment of a classification process (S200) of vehicle data performed by the data classification unit 320 of the analysis collection device 300 in the present invention.

The data classification unit 320 identifies which nodes (10 to 70) and which function operations the plurality of CAN messages obtained by the data collection unit 310 are related to, and determines a classification group for the CAN messages accordingly.

At this time, in order to increase the accuracy of CAN message classification, it is desirable to process vehicle function operations by dividing them into function maintenance operations and function change operations. The function maintenance operation is an operation that maintains vehicle functions related to the corresponding node. In the case of the steering controller 40, “operation without touching the vehicle steering wheel” may be mentioned. On the other hand, a function change operation is an operation that changes the vehicle function related to the corresponding node. In the case of the steering controller 40, an example is “an operation of turning the vehicle steering wheel to the left.”

The data classification unit 320 classifies CAN messages that are maintained without data change before and after vehicle function operation guidance among CAN messages regarding function maintenance operations. CAN messages whose data is being changed in the function maintenance operation are CAN messages that are unrelated to the corresponding vehicle function of the corresponding node. The CAN messages that the data classification unit 320 classifies in response to the function maintenance operation are called 'function maintenance message groups (10A, 40A)' for convenience.

The data classification unit 320 classifies CAN messages in which data is changed before and after vehicle function operation guidance among CAN messages regarding function change operations. CAN messages in which data is changed before and after the guidance of each vehicle function operation are classified by each function change operation to establish a classification group. The CAN messages that the data classification unit 320 classifies in response to the function change operation are called 'function operation message groups (10B, 40B)' for convenience.

Referring to [FIG. 9], the data classification unit 320 classifies the plurality of CAN messages obtained by the data collection unit 310 for each node (10 to 40) (10MSG, 40MSG), and classifies these CAN messages into It was subclassified into the function maintenance message group (10A, 40A) and the function manipulation message group (10B1 ~ 10B5; 40B1 ~ 40B5).

[FIG. 10] is a flowchart showing the vehicle data analysis process (S300) performed by the data analysis unit 330 of the analysis collection device 300 in the present invention.

Steps (S310, S320): First, the data analysis unit 330 of the analysis collection device 300 compares a plurality of CAN databases obtained in advance with the CAN ID in the CAN message to determine a common type of CAN database for the class of CAN messages. obtain. This common type of CAN database is treated as a candidate CAN database for the corresponding taxon of CAN messages.

Preferably, the analysis collection device 300 may have previously secured a CAN database of the corresponding classification group and common type for the same OEM. In this way, various CAN databases obtained in advance are compared with the taxonomies of CAN messages. You can find a common type of CAN database by comparing CAN IDs of CAN messages with several previously acquired CAN databases.

For example, in the case of Hyundai Motors, CAN IDs are assigned to each node based on the Master CAN DB for each generation. This reflects the fact that if Avante and Sonata vehicles have the same platform, they are likely to have the same CAN message (CAN ID) protocol for the steering controller 40.

If a common type of CAN database is obtained, proceed to the vehicle data verification process (S400).

Steps (S330, S340): If a common type of CAN database is not found, the data analysis unit 330 receives a CAN database for the classification of CAN messages from an analysis engineer. This is a process similar to the prior art, in which an analysis engineer combines the values of elements (e.g. Factor, Byte Order, Length, etc.) to process the data value included in the CAN message while referring to information such as OEM information and vehicle year. CAN message analysis is performed over time.

When the analysis of the CAN message is completed, the analysis engineer provides the CAN database to the data analysis unit 330 as a candidate for the CAN database for the corresponding class of CAN message.

[FIG. 11] is a flowchart showing the vehicle data verification process (S400) performed by the data verification unit 340 of the analysis collection device 300 in the present invention.

Steps (S410, S420): First, the data verification unit 340 of the analysis collection device 300 applies the CAN database candidates obtained by the data analysis unit 330 to a test vehicle prepared in advance. This test vehicle may be a real vehicle or a virtual vehicle created through computer simulation.

The user then authorizes operation of various vehicle functions on the test vehicle. At this time, as in (S100), it is preferable that guidance for operating vehicle functions is provided and the user is configured to authorize operation of vehicle functions according to the guidance. The data verification unit 340 collects CAN messages broadcast and transmitted by the corresponding node in response to vehicle function manipulation.

Steps (S430 to S450): The data verification unit 340 checks whether a CAN message is normally generated in response to vehicle function manipulation. For example, in the case of the transmission controller 20, when the gear is in P gear, P gear is displayed by a CAN message, and when the gear is changed to R gear, it is checked whether R gear is displayed. If it is normal, it will be displayed properly, and if it is abnormal, it will display a status different from the current gear status. The process of confirming normality or abnormality may be performed automatically by a computer program, or may be configured to allow the user to input normality or abnormality.

If a CAN message is generated normally, it is processed as if a CAN database has been obtained for the corresponding taxonomy of the CAN message. The CAN database is stored for application to product development. Conversely, if the CAN message is not generated properly, return to (S330) and correct the error through manual analysis by an analysis engineer.

According to the present invention as described above, the analysis and collection process of vehicle data for building a CAN database can be performed very effectively. By automatically classifying large amounts of CAN messages and processing vehicle data through the collection and analysis process, the overall process efficiency is very high, and the reliability of the analysis results can be increased through the verification process.

Vehicle data has different data formats for each vehicle manufacturer and vehicle model. If engineers manually analyze vehicle data, there is a problem that it takes too much time, and if they analyze vehicle data with a computer program to increase efficiency, there is a problem that the analysis value may be incorrect if it does not correspond to a specific format set in advance. According to the present invention, such problems of the prior art can be solved.

Meanwhile, the present invention can be implemented in the form of computer-readable code on a computer-readable non-volatile recording medium. These non-volatile recording media include various types of storage devices, such as hard disks, SSDs, CD-ROMs, NAS, magnetic tapes, web disks, and cloud disks. Additionally, the present invention can be implemented in a form in which code is distributed and stored and executed in a plurality of storage devices connected through a network. Additionally, the present invention may be implemented in the form of a computer program stored on a medium in order to execute a specific procedure in combination with hardware.

Claims (5)

A method of analyzing and collecting vehicle data performed by the analysis collection device 300 to build a CAN database necessary for the design of a vehicle device linked to CAN (Controller Area Network) communication, comprising:
For vehicles in which the data collection unit 310 of the analysis collection device 300 collects a plurality of CAN messages broadcast and transmitted to the CAN bus in response to a series of vehicle function operations at the vehicle node level for the analysis target vehicle 100. data collection phase;
A vehicle data classification step in which the data classification unit 320 of the analysis and collection device 300 classifies the collected CAN messages in response to vehicle node units and vehicle function operation instructions to generate a plurality of classification groups;
A vehicle data analysis step in which the data analysis unit 330 of the analysis and collection device 300 obtains candidates for a CAN database for the classification group of the CAN message;
A vehicle data verification step in which the data verification unit 340 of the analysis collection device 300 applies the obtained CAN database candidates to a test vehicle to check whether a CAN message is normally generated in response to vehicle function manipulation;
Analysis and collection method of vehicle data for CAN database including.
In claim 1,
The vehicle data collection step is,
Guiding a series of vehicle function operations on a vehicle node basis for the vehicle 100 to be analyzed;
Obtaining a plurality of CAN messages broadcast and transmitted to a CAN bus in response to a vehicle function operation applied to the analysis target vehicle 100 according to the guidance of the vehicle function operation;
Classifying the obtained CAN message based on data changes before and after guidance on operating the vehicle function;
Matching and storing the plurality of divided CAN messages with the guided vehicle function operation;
A method of analyzing and collecting vehicle data for a CAN database, comprising:
In claim 2,
The vehicle data classification step is,
Generating a group of function maintenance messages by classifying CAN messages maintained without data change before and after vehicle function operation guidance in response to function maintenance operations on a vehicle node basis among the collected CAN messages;
Generating a function operation message group by classifying CAN messages in which data is changed before and after vehicle function operation guidance in response to a plurality of function change operations on a vehicle node basis among the collected CAN messages;
A method of analyzing and collecting vehicle data for a CAN database, comprising:
In claim 3,
The vehicle data analysis step is,
Obtaining a CAN database of a common type for the classification group of the CAN message by comparing a plurality of CAN databases obtained in advance with the CAN ID in the CAN message;
Receiving a CAN database for the classification group of the CAN message from an analysis engineer;
A method of analyzing and collecting vehicle data for a CAN database, comprising:
A computer program stored in a storage medium for executing a method of analyzing and collecting vehicle data for a CAN database according to any one of claims 1 to 4 on a computer.

Images