KR102621707B1 - Apparatus and method for collecting of data and diagnosing, vehicle system - Google Patents

Abstract

The present invention relates to a vehicle data collection diagnostic device and method, and a vehicle system. The device according to the present invention includes a rule data management unit that updates the received rule data when rule data with changed conditions is received from a cloud server, and collects data of the corresponding item according to the data collection conditions included in the updated rule data. A data collection unit, a diagnostic unit that diagnoses the operation of the target controller according to the diagnostic conditions included in the updated rule data, and a control unit that provides at least one of the data collection result and the diagnostic result of the target controller to the cloud server. Includes.

Description

Vehicle data collection diagnostic device and method, and vehicle system {APPARATUS AND METHOD FOR COLLECTING OF DATA AND DIAGNOSING, VEHICLE SYSTEM}

The present invention relates to a vehicle data collection diagnostic device and method, and a vehicle system.

Conventional vehicles register rule data for data collection and diagnosis at the mass production stage. In this case, since the conditions such as policy, performance period, target data, etc. for collection and/or diagnosis registered in the vehicle are all fixed, it is difficult to change the conditions of rule data registered in the vehicle after the vehicle is mass-produced. It's difficult.

Therefore, even when conditions for collection and/or diagnosis of rule data change due to version upgrade, etc., it is difficult to apply the changed information to the vehicle. In addition, even when a breakdown occurs in a vehicle, there is a problem in that it is difficult to accurately analyze the cause because only information on fixed conditions can be confirmed, not the information needed to analyze the cause of the failure.

The purpose of the present invention is to generate rule data containing condition information for data collection and/or diagnosis of a vehicle from a remote location and provide it to the vehicle terminal, thereby performing data collection and/or diagnosis operations adaptively in various situations. The goal is to provide vehicle data collection diagnostic devices and methods, and vehicle systems that enable this.

Another purpose of the present invention is to collect vehicle data by providing rule data on failure situations occurring in the vehicle to the vehicle terminal, so that the cause of the failure can be quickly and accurately identified by collecting data and/or obtaining the diagnosis results of the controller from a remote location. To provide diagnostic devices and methods, and vehicle systems.

The technical problems of the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art from the description below.

A vehicle data collection and diagnosis device according to an embodiment of the present invention for achieving the above object includes a rule data management unit that updates the received rule data when rule data on a failure situation occurring in the vehicle is received from a cloud server; A data collection unit that collects data for the corresponding item according to the data collection conditions included in the updated rule data, a diagnosis unit that diagnoses the operation of the target controller according to the diagnosis conditions included in the updated rule data, and the data collection unit. It is characterized by comprising a control unit that provides at least one of a result and a diagnosis result of the target controller to the cloud server.

The rule data management unit is characterized in that, when rule data for a new failure situation is received from the cloud server, it additionally registers the received rule data.

The rule data management unit, when rule data for a pre-registered failure situation is received from the cloud server, changes the pre-registered rule data based on the received rule data.

The rule data includes at least one of rule ID, version, creation time, execution condition, trigger condition, collection cycle, data generation type, data transmission time, and diagnostic controller information.

The trigger condition is characterized in that it includes at least one of a message ID including a data collection target item, a bit start position, a bit length, a mathematical comparison operator, and a comparison variable.

The rule data is characterized in that it is defined in script form.

When rule data is received from the cloud server, the rule data management unit verifies whether the received rule data is defined according to predefined rules.

The rule data management unit is characterized in that when a breakdown situation of the vehicle occurs, it provides rule data for a pre-registered breakdown situation to the cloud server upon request from the cloud server.

In addition, the vehicle data collection and diagnosis method according to an embodiment of the present invention to achieve the above object includes the steps of updating the received rule data when rule data for a failure situation occurring in the vehicle is received from a cloud server; collecting data of the corresponding item according to the data collection conditions included in the updated rule data, diagnosing the operation of the target controller according to the diagnostic conditions included in the updated rule data, and the data collection results and the and providing at least one of the diagnosis results of the target controller to the cloud server.

The step of updating the received rule data may include additionally registering the received rule data when rule data for a new failure situation is received from the cloud server.

The step of updating the received rule data includes, when rule data for a pre-registered failure situation is received from the cloud server, changing the pre-registered rule data based on the received rule data. Do it as

The rule data includes at least one of rule ID, version, creation time, execution condition, trigger condition, collection cycle, data generation type, data transmission time, and diagnostic controller information.

The trigger condition is characterized in that it includes at least one of a message ID including a data collection target item, a bit start position, a bit length, a mathematical comparison operator, and a comparison variable.

In addition, the method according to the present invention is characterized by further comprising the step of verifying whether the received rule data is defined according to a predefined rule when rule data is received from the cloud server.

In addition, the method according to the present invention further includes the step of providing rule data for pre-registered failure situations to the cloud server upon request from the cloud server when a breakdown situation of the vehicle occurs.

In addition, the vehicle system according to an embodiment of the present invention to achieve the above object is a cloud that generates rule data for the failure situation based on rule data pre-registered for the vehicle when a failure situation occurs in the vehicle. When rule data for the failure situation is received from the server and the cloud server, the received rule data is updated, and data collection and diagnosis operations are performed according to the data collection conditions and diagnosis conditions included in the updated rule data. It is characterized by including a vehicle data collection diagnostic device that provides result data to the cloud server.

According to the present invention, by generating rule data containing condition information for data collection and/or diagnosis of a vehicle from a remote location and providing it to the vehicle terminal, data collection and/or diagnosis operations can be performed adaptively in various situations. Additionally, by obtaining the controller's diagnosis results from a remote location, the cause of the failure can be quickly and accurately identified.

1 is a diagram illustrating a vehicle to which a vehicle data collection and diagnosis device according to an embodiment of the present invention is applied.
Figure 2 is a diagram showing the configuration of a vehicle data collection and diagnosis device according to an embodiment of the present invention.
3 to 6 are diagrams illustrating an embodiment referred to in explaining the operation of a vehicle data collection and diagnosis device according to an embodiment of the present invention.
Figure 7 is a diagram illustrating the operation flow of a vehicle data collection and diagnosis method according to an embodiment of the present invention.
Figure 8 is a diagram illustrating a computing system in which a method according to an embodiment of the present invention is executed.

Hereinafter, some embodiments of the present invention will be described in detail through illustrative drawings. When adding reference numerals to components in each drawing, it should be noted that identical components are given the same reference numerals as much as possible even if they are shown in different drawings. Additionally, when describing embodiments of the present invention, if detailed descriptions of related known configurations or functions are judged to impede understanding of the embodiments of the present invention, the detailed descriptions will be omitted.

In describing the components of the embodiment of the present invention, terms such as first, second, A, B, (a), and (b) may be used. These terms are only used to distinguish the component from other components, and the nature, sequence, or order of the component is not limited by the term. Additionally, unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as generally understood by a person of ordinary skill in the technical field to which the present invention pertains. Terms defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning in the context of the related technology, and should not be interpreted in an ideal or excessively formal sense unless explicitly defined in the present application. No.

1 is a diagram illustrating a vehicle to which a vehicle data collection and diagnosis device according to an embodiment of the present invention is applied.

The vehicle data collection and diagnosis device 100 according to the present invention may be implemented inside a vehicle. At this time, the vehicle data collection and diagnosis device 100 may be formed integrally with the vehicle's internal control units, or may be implemented as a separate device and connected to the vehicle's control units through a separate connection means. Here, the vehicle data collection and diagnosis device 100 may operate in conjunction with a plurality of controllers within the vehicle.

Figure 2 is a diagram showing the configuration of a vehicle data collection and diagnosis device according to an embodiment of the present invention.

Referring to FIG. 2, the vehicle data collection and diagnosis device 100 includes a control unit 110, a communication unit 120, a storage unit 130, a rule data management unit 140, a data collection unit 150, and a diagnosis unit 160. may include. Here, the control unit 110, rule data management unit 140, data collection unit 150, and diagnosis unit 160 of the vehicle data collection and diagnosis device 100 according to this embodiment are implemented as at least one processor. It can be.

The control unit 110 may process signals transmitted between each component of the vehicle data collection and diagnosis device 100.

The communication unit 120 may include a communication module that supports a communication interface with a plurality of controllers (ECU#1, ..., ECU#n) provided in the vehicle. Here, the communication module may include a module supporting vehicle network communication such as CAN (Controller Area Network) communication, LIN (Local Interconnect Network) communication, and Flex-Ray communication.

Additionally, the communication unit 120 may include a communication module that supports a communication interface with the cloud server 200. Here, the communication module may include a module for wireless Internet access or a module for short range communication.

Wireless Internet technologies may include Wireless LAN (WLAN), Wireless Broadband (Wibro), and Wi-Fi, and short-range communication technologies include Bluetooth, ZigBee, and infrared. Communications (Infrared Data Association, IrDA), etc. may be included.

The storage unit 130 may store data and/or algorithms necessary for the vehicle data collection and diagnosis device 100 to operate.

As an example, the storage unit 130 may store one or more rule data defined in response to a vehicle failure situation. Additionally, the storage unit 130 may collect data based on stored rule data and store commands and/or algorithms for diagnosing the operation of the controller.

Here, the storage unit 130 includes random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), programmable read-only memory (PROM), and electrically erasable programmable read-only memory (EEPROM). It may include storage media such as .

The rule data management unit 140 stores and manages rule data defined in response to vehicle failure situations in the storage unit 130.

Refer to FIG. 3 for an example of rule data.

Referring to Figure 3, rule data is a rule for a vehicle failure situation, including rule ID, version, creation time, execution condition, trigger condition, collection cycle, data generation type, and data transmission. It may include at least one of timing and diagnostic controller information.

The creation time may include information on the time the rule data was created in the cloud server 200.

Execution conditions may include on/off conditions of the vehicle's accelerator (ACC), on/off conditions of the ignition (IGN), etc.

Trigger conditions include a message ID containing the signal corresponding to the data item to be collected, bit start position, bit length, and mathematical comparison operators (e.g., >, <, =, !=, ≥, etc.) and at least one of the comparison variables.

The collection cycle may include cycle information such as day, month, etc.

The data generation type may include information about the time of data generation, such as period, event, and real-time.

The data transmission time may include information about the time to transmit the resulting data to the cloud server 200.

Diagnostic controller information is information on a controller that is subject to diagnosis and may include, for example, ECU ID, service ID (SID), parameter ID (PID), HEX, etc.

Here, rule data may be defined in script form. As an example, rule data may be defined in JSON (JAvaScript Object Notation), XML (eXtensible Markup Language), etc., and may also be defined in other formats of script.

The rule data management unit 140 may provide rule data for pre-registered breakdown situations to the cloud server 200 upon request from the cloud server 200 when a vehicle breakdown situation occurs.

Additionally, when rule data regarding a vehicle breakdown situation is received from the cloud server 200, the rule data management unit 140 verifies the rule data received from the cloud server 200. At this time, the rule data management unit 140 may verify whether the received rule data was created based on predefined rules.

At this time, the rule data management unit 140 may update the verified rule data in the storage unit 130.

If the updated rule data is rule data for a new failure situation, the rule data management unit 140 may additionally register the rule data received from the cloud server 200 in the storage unit 130.

Here, the rule data received from the cloud server 200 is configured by adding rule data 415 for a new failure situation to the rule data 411 and 412 for already registered failure situations, as shown in FIG. 4A. It could be.

Meanwhile, the rule data received from the cloud server 200 may consist only of rule data 425 for a new failure situation, as shown in FIG. 4B.

On the other hand, if the updated rule data is rule data for a pre-registered failure situation, the rule data management unit 140 checks the change information by comparing the rule data received from the cloud server 200 with the pre-registered rule data. , pre-registered rule data can be changed based on the confirmed change information. At this time, the rule data management unit 140 may change, add, and/or delete some conditions based on the received rule data.

If the updated rule data includes condition information related to data collection, the data collection unit 150 collects data for the corresponding item according to the data collection conditions.

For example, when the data collection conditions included in the rule data are as shown in FIG. 5, the data collection unit 150 collects the internal variables of the hardware unit, the engine RPM signal, and the ISG at 00 seconds after startup according to the data collection conditions included in the rule data. Collect signals, power signals, etc.

The data collection unit 150 transmits data collection results according to data collection conditions to the control unit 110.

When the updated rule data includes condition information related to the diagnosis of the target controller, the diagnosis unit 160 diagnoses the operation of the target controller according to the diagnosis condition.

As an example, the diagnostic unit 160 checks the target controller based on information such as ECU ID, service ID (SID), parameter ID (PID), and HEX included in the rule data, and diagnoses the operation of the confirmed target controller. do.

The diagnosis unit 160 transmits the diagnosis result of the target controller according to the diagnosis conditions to the control unit 110.

When data collection and/or diagnosis results are received from the data collection unit 150 and/or diagnosis unit 160, the control unit 110 generates result data including the received results and sends the data to the cloud server through the communication unit 120. Provided as (200).

If the updated rule data includes only data collection conditions, the control unit 110 may generate result data including the data collection results from the data collection unit 150 and provide it to the cloud server 200.

Meanwhile, when the updated rule data includes only diagnostic conditions, the control unit 110 may generate result data including the diagnosis result of the target controller from the diagnosis unit 160 and provide it to the cloud server 200.

Meanwhile, when the updated rule data includes data collection conditions and diagnosis conditions, the control unit 110 includes both the data collection results from the data collection unit 150 and the diagnosis results of the target controller from the diagnosis unit 160. As a result, data can be generated and provided to the cloud server 200.

Accordingly, the cloud server 200 can analyze the cause of the failure situation based on the result data received from the control unit 110.

Figure 6 shows the operation of the vehicle system according to the present invention.

In the case of the present invention, it may not operate in cases where diagnosis is generally possible or data collection is possible.

On the other hand, in cases where diagnosis is difficult in a situation where a breakdown occurs in the vehicle or the data required for cause analysis is not included in the items to be collected, if a breakdown report is received to the customer center 610 as in operation 611, the customer center Like operation 621, the details of the failure report are transmitted to the mechanic 620 through real-time connection.

At this time, the mechanic 620 may input a rule script to the cloud server 200 based on the details of the failure report received, as in operation 631.

In this way, the cloud server 200 generates rule data for collection and/or diagnosis based on the rule script input for the occurred failure situation, and transmits the generated rule data to the vehicle terminal in real time as in operation 641. You can.

At this time, the vehicle data collection and diagnosis device of the vehicle terminal performs data collection and/or diagnosis based on the rule data received from the cloud server 200, and sends the result data of the data collection and/or diagnosis to the cloud server in operation 651. It can be sent to (200).

Accordingly, the cloud server 200 transmits the result data received from the vehicle data collection and diagnosis device of the vehicle terminal to the mechanic in operation 661, thereby enabling accurate cause analysis of the failure situation.

The vehicle data collection and diagnosis device 100 according to this embodiment, which operates as described above, may be implemented as an independent hardware device including a memory and a processor for processing each operation, such as a microprocessor or general-purpose computer system. It can be run as part of another hardware device.

The operation flow of the device according to the present invention configured as above will be described in more detail as follows.

Figure 7 is a diagram showing the operational flow of a method according to an embodiment of the present invention.

Figure 7 shows the operation flow of the vehicle data collection and diagnosis device.

As shown in FIG. 7, when the vehicle data collection and diagnosis device receives rule data for a vehicle failure situation from the cloud server 200 (S110), the received rule data is rule data for a new failure situation or already registered. Check whether the rule data for the failed failure situation is change data (S120).

If the vehicle data collection diagnostic device determines that the rule data is rule data for a new failure situation or change data for a previously registered failure situation in the 'S120' process, it updates the rule data received in the 'S110' process (S130) ).

If the rule data updated in the 'S130' process includes data collection conditions (S140), the vehicle data collection diagnostic device checks the data collection items and collection conditions (S150), and data of the items according to the confirmed collection conditions. Collect (S160).

Meanwhile, in the 'S130' process, if the updated rule data includes a diagnostic condition (S170), the vehicle data collection diagnostic device checks the diagnostic target controller and diagnostic conditions (S180), and determines the target controller's status according to the confirmed diagnostic conditions. Diagnose the operation (S190).

At this time, the vehicle data collection and diagnosis device may generate result data including the data collection results of the 'S160' process and/or the diagnosis results of the 'S190' process (S200) and transmit it to the cloud server 200 (S210). .

Accordingly, the cloud server 200 can accurately and quickly analyze the cause of the failure situation based on the result data received in the 'S210' process.

The above embodiment has described the case where rule data is generated in the cloud server and transmitted to the vehicle data collection and diagnosis device when a failure situation occurs, but it can also be applied when there is a change in the conditions of the rule data due to a policy change, etc. .

Figure 8 is a diagram illustrating a computing system in which a method according to an embodiment of the present invention is executed.

Referring to FIG. 8, the computing system 1000 includes at least one processor 1100, a memory 1300, a user interface input device 1400, a user interface output device 1500, and storage connected through a bus 1200. It may include (1600), and a network interface (1700).

The processor 1100 may be a central processing unit (CPU) or a semiconductor device that processes instructions stored in the memory 1300 and/or storage 1600. Memory 1300 and storage 1600 may include various types of volatile or non-volatile storage media. For example, the memory 1300 may include a read only memory (ROM) 1310 and a random access memory (RAM) 1320.

Accordingly, steps of a method or algorithm described in connection with the embodiments disclosed herein may be implemented directly in hardware, software modules, or a combination of the two executed by processor 1100. Software modules reside in a storage medium (i.e., memory 1300 and/or storage 1600), such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, or CD-ROM. You may. An exemplary storage medium is coupled to processor 1100, which can read information from and write information to the storage medium. Alternatively, the storage medium may be integrated with processor 1100. The processor and storage medium may reside within an application specific integrated circuit (ASIC). The ASIC may reside within the user terminal. Alternatively, the processor and storage medium may reside as separate components within the user terminal.

The above description is merely an illustrative explanation of the technical idea of the present invention, and various modifications and variations will be possible to those skilled in the art without departing from the essential characteristics of the present invention.

Accordingly, the embodiments disclosed in the present invention are not intended to limit the technical idea of the present invention, but are for illustrative purposes, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be interpreted in accordance with the claims below, and all technical ideas within the equivalent scope should be construed as being included in the scope of rights of the present invention.

10: Controller 100: Vehicle data collection and analysis device
110: control unit 120: communication unit
130: storage unit 140: rule data management unit
150: data collection unit 160: diagnosis unit
200: Cloud server

Claims (20)

When rule data with changed conditions is received from a cloud server, a rule data management unit updates the received rule data;
a data collection unit that collects data for the corresponding item according to data collection conditions included in the updated rule data;
a diagnostic unit that diagnoses the operation of the target controller according to diagnostic conditions included in the updated rule data; and
a control unit providing at least one of the data collection result and the diagnosis result of the target controller to the cloud server;
Including,
The rule data management unit,
A vehicle data collection and diagnosis device characterized in that when the conditions of the rule data are changed, rule data for a pre-registered failure situation is provided to the cloud server upon request from the cloud server. In claim 1,
The rule data management unit,
A vehicle data collection and diagnosis device, characterized in that when rule data including condition information for a newly occurring failure situation in a vehicle is received from the cloud server, the received rule data is additionally registered. In claim 1,
The rule data management unit,
When rule data including change condition information for a pre-registered failure situation is received from the cloud server, the vehicle data collection and diagnosis device changes the pre-registered rule data based on the received rule data. In claim 1,
The rule data is,
A vehicle data collection diagnostic device comprising at least one of rule ID, version, creation time, execution condition, trigger condition, collection cycle, data generation type, data transmission point, and diagnostic controller information. In claim 4,
The trigger condition is,
A vehicle data collection diagnostic device comprising at least one of a message ID including a data collection target item, a bit start position, a bit length, a formula comparison operator, and a comparison variable. In claim 1,
The rule data is,
A vehicle data collection diagnostic device defined in the form of a script. In claim 1,
The rule data management unit,
When rule data is received from the cloud server, the vehicle data collection and diagnosis device is characterized in that it verifies whether the received rule data is written based on predefined rules. delete When rule data with changed conditions is received from a cloud server, updating the received rule data;
collecting data for the corresponding item according to data collection conditions included in the updated rule data;
diagnosing the operation of a target controller according to diagnostic conditions included in the updated rule data;
providing at least one of the data collection result and the diagnosis result of the target controller to the cloud server; and
Providing rule data for a pre-registered failure situation to the cloud server upon request from the cloud server when the conditions of the rule data are changed.
A vehicle data collection diagnostic method comprising: In claim 9,
The step of updating the received rule data is,
When rule data including condition information on a newly occurring failure situation in a vehicle is received from the cloud server, a vehicle data collection and diagnosis method comprising additionally registering the received rule data. In claim 9,
The step of updating the received rule data is,
Vehicle data collection, comprising the step of changing pre-registered rule data based on the received rule data when rule data including change condition information for a pre-registered failure situation is received from the cloud server. Diagnosis method. In claim 9,
The rule data is,
A vehicle data collection diagnostic method comprising at least one of rule ID, version, creation time, execution condition, trigger condition, collection cycle, data generation type, data transmission point, and diagnostic controller information. In claim 12,
The trigger condition is,
A vehicle data collection diagnostic method comprising at least one of a message ID including a data collection target item, a bit start position, a bit length, a formula comparison operator, and a comparison variable. In claim 9,
When rule data is received from the cloud server, the vehicle data collection and diagnosis method further includes verifying whether the received rule data is defined according to predefined rules. delete A cloud server that generates rule data based on the change conditions of rule data already registered for the vehicle when the conditions of rule data are changed; and
When rule data with changed conditions is received from the cloud server, the received rule data is updated, and data collection and diagnosis operations are performed according to the data collection conditions and diagnosis conditions included in the updated rule data to the cloud server. Vehicle data collection diagnostic device providing resulting data
Including,
The vehicle data collection and diagnostic device,
A vehicle system characterized in that when the conditions of the rule data are changed, rule data for a pre-registered failure situation is provided to the cloud server upon request from the cloud server. In claim 16,
The cloud server is,
A vehicle system characterized in that when a breakdown situation occurs in the vehicle, rule data for the breakdown situation is generated based on rule data previously registered for the vehicle. In claim 17,
The cloud server is,
A vehicle system characterized in that rule data containing condition information for a newly occurring failure situation in the vehicle is generated and transmitted to the vehicle data collection and diagnosis device. In claim 17,
The cloud server is,
If there is pre-registered rule data for the failure situation, rule data containing change condition information for the pre-registered failure situation is generated and transmitted to the vehicle data collection and diagnosis device. In claim 17,
The cloud server is,
A vehicle system, characterized in that the cause of the failure situation is analyzed based on result data provided from the vehicle data collection and diagnosis device.

Images