Data management system of vehicle and data management method thereof

Abstract

A data management system for a vehicle according to one embodiment of the present invention may include: a volatile memory; a non-volatile memory; and a processor that stores data collected from a sensor unit of the vehicle in the volatile memory, and when a diagnostic trouble code is detected during the operation of the vehicle, identifies at least one sensor associated with the detected diagnostic trouble code and moves the data collected from the at least one sensor among the data stored in the volatile memory to the non-volatile memory.

Description

Technology Field

[0001] The present invention relates to a data management system and a data management method for a vehicle. Background Technology

[0002] A vehicle operates through the combination of various systems, such as a steering control system, a braking system, an in-vehicle communication system, and an autonomous driving system. Each system is controlled by a control device, such as an Electronic Control Unit (ECU), and each ECU can control the vehicle or analyze its status based on data collected from the connected vehicle's sensors.

[0003] Meanwhile, conventionally, when a vehicle failure is diagnosed, it is difficult to analyze the cause of the failure because data is stored only after the failure has occurred. For example, regarding data collected from a current sensor, if a failure occurs in a gate driver or motor, the hardware sets the current to zero, so the current value after the failure is always zero.

[0004] Therefore, currently, it is difficult to analyze the cause of a vehicle malfunction even if it occurs. The problem to be solved

[0005] The objective of the present invention is to provide a vehicle data management system and a data management method capable of analyzing the cause even if a vehicle malfunction occurs. means of solving the problem

[0006] A data management system for a vehicle according to one embodiment of the present invention may include: a volatile memory; a non-volatile memory; and a processor that stores data collected from a sensor unit of the vehicle in the volatile memory, and when a diagnostic trouble code is detected during the operation of the vehicle, identifies at least one sensor associated with the detected diagnostic trouble code and moves the data collected from the at least one sensor among the data stored in the volatile memory to the non-volatile memory.

[0007] The above processor can manage data stored in the volatile memory based on priority information of a plurality of diagnostic problem codes.

[0008] The processor can identify the priority information by considering at least one of the severity index, detection frequency, and detection time for each of the plurality of diagnostic problem codes.

[0009] The above processor can set at least one sensor corresponding to each of the above diagnostic problem codes.

[0010] The processor can delete data collected from at least one sensor corresponding to the lowest priority diagnostic problem code from the volatile memory based on the priority information.

[0011] The processor can move data collected from at least one sensor corresponding to the highest priority diagnostic problem code based on the priority information to the non-volatile memory.

[0012] A data management method performed by a data management system of a vehicle according to an embodiment of the present invention may include: a step of storing data collected from a sensor unit of the vehicle in a volatile memory; a step of identifying at least one sensor associated with a detected diagnostic trouble code when a diagnostic trouble code is detected during the operation of the vehicle; and a step of moving data collected from the at least one sensor among the data stored in the volatile memory to a non-volatile memory.

[0013] The step of moving to the non-volatile memory may include the step of managing data stored in the volatile memory based on priority information of a plurality of diagnostic problem codes.

[0014] The step of moving to the non-volatile memory may include the step of identifying the priority information by considering at least one of the severity index, detection frequency, and detection time for each of the plurality of diagnostic problem codes.

[0015] The step of managing data stored in the volatile memory may include the step of deleting data collected from at least one sensor corresponding to the lowest priority diagnostic problem code based on the priority information from the volatile memory. Effects of the invention

[0016] According to one embodiment of the present invention, by securing data necessary for analyzing the cause of a failure when a failure occurs, it is possible to perform a more accurate analysis of the cause of the failure. Brief explanation of the drawing

[0017] FIG. 1 is a block diagram illustrating the configuration of a data management system of a vehicle according to one embodiment of the present invention. FIG. 2 is a diagram illustrating the operation flowchart of a data management system of a vehicle according to a first embodiment of the present invention. FIG. 3 is a diagram illustrating the operation of a data management system of a vehicle according to a second embodiment of the present invention. Specific details for implementing the invention

[0018] Hereinafter, preferred embodiments according to the present invention will be described in detail with reference to the accompanying drawings. The detailed description disclosed below in conjunction with the accompanying drawings is intended to describe exemplary embodiments of the present invention and is not intended to represent the only embodiment in which the present invention may be practiced. In order to clearly explain the present invention in the drawings, parts unrelated to the description may be omitted, and the same reference numerals may be used for identical or similar components throughout the specification. Furthermore, in the embodiments of the present invention, terms including ordinal numbers such as first, second, etc., are used solely for the purpose of distinguishing one component from another, and singular expressions include plural expressions unless the context clearly indicates otherwise.

[0019] The present invention proposes a method for managing data to facilitate the analysis of the cause of a vehicle failure.

[0020] A data management system (100) according to one embodiment of the present invention may be installed for each vehicle control system, such as a vehicle steering control system, a brake system, a vehicle internal communication system, and an autonomous driving system, or implemented to be applied to two or more systems, and is not limited to any one.

[0021] Hereinafter, the operation of a data management system (100) (hereinafter also referred to as the system (100)) according to one embodiment of the present invention will be described in detail with reference to the drawings.

[0022] FIG. 1 is a block diagram illustrating the configuration of a data management system of a vehicle according to one embodiment of the present invention.

[0023] A data management system (100) according to one embodiment of the present invention may include a sensor unit (110), a communication unit (120), a memory (130), a driving device (140), and a processor (150).

[0024] The sensor unit (110) may be composed of sensors connected to parts of the vehicle to detect the state of each part. For example, the sensor unit (110) may include a current sensor, a PTS (Pedal Travel Sensor), an MPS (Motor Position Sensor), a WSS (Wheel Speed ​​Sensor), a steering angle sensor, a speed sensor, an acceleration sensor, a camera, a GNSS (Global Navigation Satellite System) sensor, a LiDAR (Light Detection And Ranging) sensor, an ultrasonic sensor, a radar (Radio Detection And Ranging) sensor, etc. In addition, the sensor unit (110) may be included without limitation when mounted on the vehicle, and the number of sensors mounted or the mounting location does not limit the present invention.

[0025] At this time, the configuration of the sensor unit (110) does not necessarily have to be built into the system (100), and it is sufficient if it is configured to communicate with the system (100) via wired or wireless connection.

[0026] The communication unit (120) can communicate with external sensors, internal components of the system (100), internal components of the vehicle, a server, etc., to transmit and receive information necessary for managing data collected from the sensor unit (110), such as data collected from the sensor unit (110), a list of diagnostic trouble codes, priority information of diagnostic trouble codes, severity index for each diagnostic trouble code, and information regarding detection frequency and detection time.

[0027] To this end, the communication unit (120) can perform wireless communication such as 5G (5th generation communication), LTE-A (long term evolution-advanced), LTE (long term evolution), Wi-Fi (wireless fidelity), Bluetooth, or wired communication such as CAN (Controller Area Network) communication, LIN (Local Interconnect Network) communication, A2B (Automotive Audio Bus) communication, Ethernet, LAN (local area network), WAN (Wide Area Network), power line communication.

[0028] The memory (130) can store the operation programs of the system (100).

[0029] A memory (130) according to one embodiment of the present invention may include a volatile memory (131) and a non-volatile memory (NVM) (132).

[0030] Volatile memory (131) is a memory with volatile properties in which data is loaded to be processed by a processor (150) and data cannot be preserved if power is not provided, and may include a buffer, RAM (Random Access Memory), etc.

[0031] Non-volatile memory (132) is a storage with non-volatile properties that can preserve data (information) regardless of whether power is supplied, and may include flash memory, hard-disc drive (HDD), solid-state drive (SSD), and ROM (Read Only Memory). At this time, the non-volatile memory (132) may be implemented not only inside the system (100) but also in external server devices, and is considered to have a larger capacity than the volatile memory (131).

[0032] The memory (130) can store data collected from the sensor unit (110), a list of diagnostic problem codes, priority information of the diagnostic problem codes, severity index for each diagnostic problem code, information regarding detection frequency and detection time, etc.

[0033] The memory (130), in particular the non-volatile memory (132), can store computational programs necessary for the process of detecting diagnostic problem codes, identifying related sensors for each diagnostic problem code, identifying priority information, etc.

[0034] The drive unit (140) is a configuration necessary to drive the vehicle and may largely include a driving unit, a braking unit, and a steering unit. The driving unit is a device that controls the overall driving of the vehicle and may be configured, for example, to control the vehicle's speed of movement.

[0035] The braking system may be configured to brake the vehicle's drive, such as the driver's pedal operation, an Anti-Lock Braking System (ABS), or an Electronic Stability Control (ESC), to brake the vehicle's driving.

[0036] A steering device is a means of assisting the steering of a vehicle including a steering wheel, and can be implemented as an electric power steering (EPS) and a motor-driven power steering (MDPS).

[0037] The processor (150) can control at least one other component (e.g., hardware or software component) of the system (100) by executing software such as a program, and can perform various data processing or operations.

[0038] The processor (150) can be implemented as an Electronic Control Unit (ECU) or a Microcontroller Unit.

[0039] A processor (150) according to one embodiment of the present invention stores data collected from a sensor unit of the vehicle in the volatile memory, and when a diagnostic trouble code is detected during the operation of the vehicle, identifies at least one sensor associated with the detected diagnostic trouble code and can move the data collected from the at least one sensor among the data stored in the volatile memory to the non-volatile memory.

[0040] Meanwhile, the processor (150) may perform at least some of the data analysis, processing, and result information generation for performing the above operations using at least one of machine learning, neural network, or deep learning algorithms as a rule-based or artificial intelligence algorithm. Examples of neural networks may include models such as CNN (Convolutional Neural Network), DNN (Deep Neural Network), and RNN (Recurrent Neural Network).

[0041] In addition, the system (100) may further include an alarm device. The alarm device is a device that outputs necessary notification information when a malfunction occurs, and may include at least one of a speaker and a display.

[0042] A speaker is a device mounted inside a vehicle to output notification information to the driver inside the vehicle. A display is mounted inside a vehicle to display display data according to the operation of the system (100). The display can display images captured by a camera, a screen including notification information to guide the driver inside the vehicle, etc. The notification information may include information regarding the cause of a malfunction or parts requiring repair.

[0043] The display includes a liquid crystal display (LCD), a light emitting diode (LED) display, an organic light emitting diode (OLED) display, a micro electro mechanical systems (MEMS) display, and an electronic paper display. The display may be combined with an input unit to be implemented as a touch screen. However, the alarm device is not limited to this, and any device capable of outputting notification information, such as a lamp, may also be applied.

[0044] FIG. 2 is a diagram illustrating the operation flowchart of a data management system of a vehicle according to a first embodiment of the present invention.

[0045] According to one embodiment of the present invention, the processor (150) can store data collected from the sensor unit (110) of the vehicle in a volatile memory (131) (S10).

[0046] At this time, the data collected from the sensor unit (110) may be in the form of text or video. In particular, the generated data may be in the form of snapshot data that appears as if a photograph has been taken. However, the format or type of the data is not limited to any one.

[0047] The processor (150) can continuously collect data generated as the vehicle operates and temporarily store it in volatile memory (131). This is to obtain data generated before a failure occurs, as data collected before the failure occurs is more likely to be meaningful data for analyzing the cause of the failure than data collected after the failure occurs.

[0048] According to one embodiment of the present invention, when a diagnostic trouble code is detected during the operation of a vehicle, the processor (150) can identify at least one sensor associated with the detected diagnostic trouble code (S20).

[0049] A diagnostic problem code is a code used to indicate the type of fault, and pre-specifies what type of fault occurs for each of the vehicle's various systems or for each vehicle. Each diagnostic problem code has a defined detection criterion, so the processor (150) can determine whether to generate the diagnostic problem code based on the detection criterion.

[0050] In the present invention, when a specific diagnostic problem code occurs, at least one sensor associated with the diagnostic problem code is identified, and data collected from the corresponding sensor is transferred from the volatile memory (131) to the non-volatile memory (132) to perform cause analysis.

[0051] To this end, the processor (150) can set at least one sensor corresponding to each diagnostic problem code. For example, if a gate driver is associated with data from a current sensor, the processor (150) can identify that the sensor associated with the diagnostic problem code is a current sensor when a diagnostic problem code for the gate driver is detected.

[0052] At this time, the processor (150) can store information matching the diagnostic problem code - sensor in non-volatile memory (132). At this time, there may be at least one sensor for each code, and the number or type of sensors is not limited to any one.

[0053] According to one embodiment of the present invention, the processor (150) can move data collected from at least one sensor among the data stored in the volatile memory (131) to the non-volatile memory (132) (S30).

[0054] The processor (150) can manage data collected from at least one sensor associated with a diagnostic problem code, i.e., data temporarily stored in volatile memory (131).

[0055] Specifically, the processor (150) can manage data stored in volatile memory (131) based on priority information of multiple diagnostic problem codes.

[0056] Volatile memory (131) may have insufficient capacity due to its characteristics, and there is a need for management, such as moving important data to non-volatile memory (132) in advance before a diagnostic problem code occurs.

[0057] The processor (150) can identify priority information by considering at least one of a severity index per multiple diagnostic problem code, a detection frequency, and a detection time.

[0058] Priority information is information indicating the importance of multiple diagnostic problem codes and is a type of weighting information. Priority information can be determined by considering at least one of the severity index, detection frequency, and detection time for each of the multiple diagnostic problem codes. Hereinafter, in the present invention, a high priority means that there is a high probability that data related to the corresponding diagnostic problem code should be transferred to non-volatile memory (132), and conversely, a low priority means that there is a low probability that the corresponding data should be transferred to non-volatile memory (132) (in some cases, it is deleted from volatile memory (131) without being transferred to non-volatile memory (132)).

[0059] The severity index for each diagnostic problem code is information indicating the severity of the diagnostic problem code itself, and can be set in various ways, such as being categorized by level.

[0060] In addition to the severity of the diagnostic problem code itself, the detection frequency or timing of the code can be considered. Detection frequency indicates how often a diagnostic problem code occurred during a predefined period, while detection timing indicates the specific time of occurrence for each code. A higher detection frequency results in a higher priority for the diagnostic problem code, and a more recent detection time can also lead to a higher priority.

[0061] The processor (150) can delete data collected from at least one sensor corresponding to the lowest priority diagnostic problem code from the volatile memory (131) based on priority information. This is to prevent important data from being erased due to the capacity of the volatile memory (131).

[0062] Alternatively, the processor (150) may move data collected from at least one sensor corresponding to the highest priority diagnostic problem code based on priority information to non-volatile memory (132). This is to prevent data stored in volatile memory (131) from being lost when the vehicle's engine is turned off, even before the diagnostic problem code actually occurs, or to secure data in advance for data that is likely to soon occur.

[0063] According to one embodiment of the present invention, by securing data necessary for analyzing the cause of a failure when a failure occurs, it is possible to perform a more accurate analysis of the cause of the failure.

[0064] FIG. 3 is a diagram illustrating the operation of a data management system of a vehicle according to a second embodiment of the present invention.

[0065] For content in Figure 3 that overlaps with the content previously explained with reference to Figure 2, refer to the previously described content.

[0066] According to one embodiment of the present invention, the processor (150) can store data collected from the sensor unit (110) in a volatile memory (131) (S310).

[0067] The processor (150) identifies whether a diagnostic problem code is detected while the vehicle is in operation, and if a diagnostic problem code is detected (Yes in S320), it can identify a sensor corresponding to the detected diagnostic problem code (S330).

[0068] If no diagnostic problem code is detected (No. of S320), the processor (150) can return to S310 and continue collecting data.

[0069] If a sensor corresponding to a detected diagnostic problem code is identified (Yes in S330), the processor (150) can move data collected from the sensor before and after the detection time from volatile memory (131) to non-volatile memory (132) (S340).

[0070] For sensors that are not the sensor corresponding to the detected diagnostic problem code (No. of S330), this algorithm terminates without moving to memory. Explanation of the symbols

[0071] 100: Data Management System 110: Sensor section 120: Communications Department 130: Memory 131: Volatile memory 132: Non-volatile memory 140: Drive unit 150: Processor

Claims

Claim 1 A data management system for a vehicle comprises: a volatile memory; a non-volatile memory; and a processor that stores data collected from a sensor unit of the vehicle in the volatile memory, and when a diagnostic trouble code is detected during the operation of the vehicle, identifies at least one sensor associated with the detected diagnostic trouble code and moves data collected from the at least one sensor among the data stored in the volatile memory to the non-volatile memory; wherein the processor identifies a priority for each of the plurality of diagnostic trouble codes by considering at least one of a severity index, detection frequency, and detection time for each of the plurality of diagnostic trouble codes, and deletes data collected from at least one sensor corresponding to the diagnostic trouble code with the lowest identified priority from the volatile memory. Claim 2 delete Claim 3 delete Claim 4 In claim 1, the processor is a data management system that sets at least one sensor corresponding to each diagnostic problem code. Claim 5 delete Claim 6 In claim 1, the processor is a data management system that moves data collected from at least one sensor corresponding to the highest priority diagnostic problem code based on the priority to the non-volatile memory. Claim 7 A data management method performed by a data management system of a vehicle, comprising: a step of storing data collected from a sensor unit of the vehicle in a volatile memory; a step of identifying at least one sensor associated with a detected diagnostic trouble code when a diagnostic trouble code is detected during the operation of the vehicle; and a step of moving data collected from the at least one sensor among the data stored in the volatile memory to a non-volatile memory, wherein the step of moving to the non-volatile memory comprises identifying a priority for each of the plurality of diagnostic trouble codes by considering a severity index, detection frequency, and detection time for each of the plurality of diagnostic trouble codes, and deleting data collected from at least one sensor corresponding to the diagnostic trouble code with the lowest identified priority from the volatile memory. Claim 8 delete Claim 9 delete Claim 10 delete

Images