Data management device, vehicle including same, and method thereof

Abstract

According to an embodiment disclosed in the present document, a data management device may comprise: a first control unit electrically connected to a first digital tachograph (DTG); and a second control unit electrically connected to a second DTG. For example, the first control unit may store first driving data related to a first zone of a host vehicle in the first DTG, and the second control unit may store second driving data related to a second zone, distinguished from the first zone of the host vehicle, in the second DTG.

Description

Data management device, vehicle including the same, and method

[0001] Cross-citation with related applications

[0002] This application claims the benefit of priority from Republic of Korea Patent Application No. 10-2024-0068003, filed May 24, 2024, the entire contents of which are incorporated herein by reference.

[0003] Technology field

[0004] Embodiments disclosed in this document relate to a data management device and method, and a vehicle including the data management device.

[0005] As electric vehicles (EVs) proliferate, research and development on new vehicle architectures are actively underway. For example, electric vehicles can be powered by secondary batteries, which are rechargeable and include both conventional Ni / Cd and Ni / MH batteries, as well as more recent lithium-ion batteries. Among secondary batteries, lithium-ion batteries have the advantage of having a much higher energy density than conventional Ni / Cd and Ni / MH batteries. Furthermore, lithium-ion batteries can be manufactured in a compact and lightweight form, making them a power source for mobile devices. Recently, their use has expanded to include power sources for electric vehicles, attracting attention as a next-generation energy storage medium.

[0006] Battery cells, battery modules, battery packs, or battery racks like these can be utilized in a variety of devices. For example, batteries can be used in mobile devices such as cell phones, laptops, smartphones, and tablets, as well as in electric vehicles (EVs, HEVs, PHEVs) and large-capacity energy storage systems (ESS).

[0007] These batteries can have their status and operation managed and controlled by a battery management system (BMS). The BMS can be included with the batteries in a single device.

[0008] Meanwhile, as the automotive industry evolves, concepts of future mobility, such as Software Defined Vehicles (SDVs) and Purpose-Built Vehicles (PBVs), are becoming increasingly concrete. For example, SDVs refer to cars where hardware is controlled and managed by software. Software within SDVs can define not only driving performance but also convenience and safety features, emotional quality, and brand identity. SDV-based architectures can reduce vehicle development costs by sharing ECUs and internalizing software. Furthermore, high-performance computers and networks based on electronic architectures can advance autonomous driving technology.

[0009] As autonomous vehicle control is implemented, managing and storing data related to autonomous driving is becoming increasingly important. In particular, improving the accuracy of data recording and management technology to determine who is at fault and the percentage of fault in the event of an accident is becoming a critical issue.

[0010] One purpose of the embodiments disclosed in this document is to provide an excellent data management device and method in terms of data storage efficiency and storage management safety, and a vehicle including the data management device, by implementing an algorithm capable of efficiently storing and managing data using a plurality of data storage devices (e.g., DTG, Digital Tacho Graph) in a vehicle including an SDV structure.

[0011] The technical problems of the embodiments disclosed in this document 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 descriptions below.

[0012] According to an embodiment disclosed in this document, a first control unit electrically connected to a first DTG (digital tacho graph) and a second control unit electrically connected to a second DTG may be included.

[0013] According to an embodiment, the first control unit may be configured to store first driving data regarding a first zone of the vehicle in the first DTG.

[0014]

[0015] *11 According to an embodiment, the second control unit may be configured to store second driving data regarding a second zone distinct from the first zone of the vehicle in the second DTG.

[0016] According to an embodiment, the first control unit may be configured to transfer the first driving data stored in the first DTG to the second DTG when the amount of data processed in the first zone exceeds a specified amount, or to receive the second driving data from the second DTG and then store it in the first DTG.

[0017] According to an embodiment, the first control unit may be configured to, when receiving the second driving data, synchronize the first driving data and the second driving data based on at least one of the type, time stamp, time of occurrence, or any combination thereof of the first driving data and the second driving data to generate synchronization data, and transmit the synchronization data to a vehicle controller for controlling the vehicle.

[0018] According to an embodiment, the first driving data and the second driving data may be stored in the first DTG corresponding to the first zone and the second DTG corresponding to the second zone, respectively, via automotive Ethernet.

[0019] According to an embodiment, the first control unit may be configured to increase the priority of an operation of storing and backing up the first driving data, transmitting the first driving data to the second DTG whose mounting position is distinct from the first DTG, or storing the second driving data received from the second DTG in the first DTG when a designated event for the vehicle occurs.

[0020] According to an embodiment, the first control unit may be configured to determine that the specified event has occurred when it is determined that an abnormality has occurred in the operation of the vehicle.

[0021] According to an embodiment, when the power supply to the first zone is interrupted, the first DTG may be supplied with power from an emergency power source, and the first driving data stored in the first DTG may be transmitted to the second DTG through PoE (Power over Ethernet) by the emergency power source, or the second driving data stored in the second DTG may be transmitted to the first DTG.

[0022] According to embodiments disclosed in this document, a vehicle including any one of the data management devices described above may be provided.

[0023] According to an embodiment disclosed in this document, a data management method may include a step in which a first control unit stores first driving data regarding a first zone of a vehicle in a first DTG corresponding to the first zone, and a step in which a second control unit stores second driving data regarding a second zone of the vehicle, which is distinct from the first zone, in a second DTG corresponding to the second zone.

[0024] According to an embodiment, the data management method may further include a step of, when the amount of data processed in the first zone exceeds a specified amount, the first control unit transfers the first driving data stored in the first DTG to the second DTG, or receives the second driving data from the second DTG and then stores it in the first DTG.

[0025] According to an embodiment, the data management method may further include a step of generating synchronization data by synchronizing the first driving data and the second driving data based on at least one of the type, time stamp, time of occurrence, or any combination thereof of each of the first driving data and the second driving data when the first control unit receives the second driving data, and a step of transmitting the synchronization data to a vehicle controller for controlling the vehicle.

[0026] According to an embodiment, the first driving data and the second driving data may be stored in the first DTG corresponding to the first zone and the second DTG corresponding to the second zone, respectively, via automotive Ethernet.

[0027] According to an embodiment, the data management method may further include a step of increasing the priority of an operation of storing and backing up the first driving data, transmitting the first driving data to the second DTG whose mounting position is distinct from the first DTG, or storing the second driving data received from the second DTG in the first DTG when a designated event for the vehicle occurs, by the first control unit.

[0028] According to an embodiment, the data management method may further include a step of determining that the specified event has occurred when the first control unit identifies that an abnormality has occurred in the operation of the vehicle.

[0029] According to an embodiment, the data management method may further include a step of supplying power from an emergency power source when the power supply to the first zone is interrupted, and a step of transmitting the first driving data stored in the first DTG to the second DTG or transmitting the second driving data stored in the second DTG to the first DTG via PoE (Power over Ethernet) by the emergency power source.

[0030] The data management device and method according to the embodiments disclosed in this document can provide a more efficient and intuitive vehicle data management method by implementing a data transmission path, a power transmission path, and a transmission subject separately under an SDV structure.

[0031] In addition, various effects may be provided, either directly or indirectly, through this document.

[0032] FIG. 1 is a conceptual diagram illustrating the structure of a vehicle including a data management device according to one embodiment disclosed in this document.

[0033] FIG. 2 is a conceptual diagram illustrating the structure of a vehicle including a data management device according to an embodiment disclosed in this document.

[0034] FIG. 3 is a block diagram showing the configuration of a data management device according to one embodiment disclosed in this document.

[0035] FIG. 4 is a conceptual diagram showing the configuration of a vehicle including a data management device according to an embodiment disclosed in this document.

[0036] FIG. 5 is a block diagram showing the configuration of a vehicle including a data management device according to an embodiment disclosed in this document.

[0037] Figure 6 is a flowchart of a data management method according to one embodiment disclosed in this document.

[0038] Figure 7 is a flowchart of a data management method according to an embodiment disclosed in this document.

[0039] FIG. 8 is a block diagram showing the hardware configuration of a computing system for performing an operation method of a data management device according to an embodiment disclosed in this document.

[0040] Hereinafter, various embodiments of the present invention will be described with reference to the attached drawings. However, this is not intended to limit the present invention to specific embodiments, and it should be understood that the present invention encompasses various modifications, equivalents, and / or alternatives of the embodiments.

[0041] In this document, the singular form of a noun corresponding to an item may include one or more of said items, unless the context clearly indicates otherwise. In this document, phrases such as "A or B," "at least one of A and B," "at least one of A or B," "A, B, or C," "at least one of A, B, and C," and "at least one of A, B, or C" may each include any one of the items listed together in that phrase, or all possible combinations thereof. Terms such as "first," "second," or "first" or "second" may be used merely to distinguish the corresponding element from other corresponding elements, and do not limit the corresponding elements in any other respect (e.g., importance or order). When a component (e.g., a first component) is referred to as being “coupled” or “connected” to another component (e.g., a second component), with or without the terms “functionally” or “communicatively,” it means that the component can be connected to the other component directly (e.g., wired), wirelessly, or through a third component.

[0042] Each component (e.g., a module or a program) described in this document may include one or more entities. According to various embodiments, one or more components or operations of the components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (e.g., a module or a program) may be integrated into a single component. In such a case, the integrated component may perform one or more functions of each of the plurality of components identically or similarly to those performed by the corresponding component among the plurality of components prior to integration. According to various embodiments, the operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

[0043] The term "module" or "part" used in this document may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit. A module may be an integral component, or a minimum unit or part of such a component that performs one or more functions. For example, according to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).

[0044] Various embodiments of the present document may be implemented as software (e.g., a program or an application) including one or more instructions stored in a machine-readable storage medium (e.g., memory). For example, a processor of the device may call at least one instruction among the one or more instructions stored from the storage medium and execute it. This enables the device to operate to perform at least one function according to the at least one instruction called. The one or more instructions may include code generated by a compiler or code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Here, "non-transitory" only means that the storage medium is a tangible device and does not contain a signal (e.g., electromagnetic waves), and this term does not distinguish between cases where data is stored semi-permanently and cases where it is stored temporarily in the storage medium.

[0045]

[0046] FIG. 1 is a conceptual diagram illustrating the structure of a vehicle including a data management device according to one embodiment disclosed in this document.

[0047] According to one embodiment, a data management device (e.g., data management device (300) of FIG. 3) may include at least some of the components included in a vehicle (110) according to the SDV architecture. The data management device may, for example, manage power and / or data transmitted and received between components of the vehicle (110).

[0048] For example, the vehicle (110) may include at least one of a first zone controller (121), a second zone controller (122), a third zone controller (123), a fourth zone controller (124), a first terminal device (131), a second terminal device (132), a third terminal device (133), a fourth terminal device (134), a first actuator (141), a second actuator (142), a high performance computer (HPC) (150), a transmission / reception path (160), an additional element (170), or any combination thereof. A data management device for managing data of the vehicle (110) may include at least some of the components included in the vehicle (110).

[0049] For example, components according to the SDV architecture may include a hierarchy of HPC (150), zoning controller, and end device order.

[0050] For example, the HPC (150) is connected to the first zoning controller (121), the second zoning controller (122), the third zoning controller (123), and the fourth zoning controller (124), and can transmit and receive various types of data with each zoning controller.

[0051] For example, the first zoning controller (121), the second zoning controller (122), the third zoning controller (123), and the fourth zoning controller (124) may control the first terminal device (131), the second terminal device (132), the third terminal device (133), and the fourth terminal device (134), respectively. The terminal devices may include, for example, at least one of a sensor for controlling the vehicle (110), a battery (or BMS) for driving the vehicle (110), or any combination thereof. For example, if one of the second terminal devices (132) is a BMS, the additional element (170) may be defined as a battery pack.

[0052] For example, the first zone controller (121) and the second zone controller (122) may control the first actuator (141) and the second actuator (142), respectively. The actuator may include, for example, at least one driving device for driving the vehicle (110).

[0053] For example, the components described above can perform communication based on a specified path (e.g., a transmission / reception path (160)) via automotive Ethernet.

[0054] A data management device according to one embodiment of the present document can control and manage a communication process of power and / or data transmitted and received between the above-described components.

[0055]

[0056] FIG. 2 is a conceptual diagram illustrating the structure of a vehicle including a data management device according to an embodiment disclosed in this document.

[0057] In Fig. 2, the description of components defined with the same names as in Fig. 1 may be replaced with the description of Fig. 1 described above.

[0058] For example, the self-vehicle (210) may include at least one of a first terminal device (231), a second terminal device (232), a third terminal device (233), a fourth terminal device (234), a first actuator (241), a second actuator (242), a high performance computer (HPC) (250), a transmission / reception path (260), an additional element (270), or any combination thereof. A data management device for managing data of the self-vehicle (210) may include at least some of the components included in the self-vehicle (210).

[0059] For example, the self-vehicle (210) according to FIG. 2 does not include a zoning controller compared to FIG. 1. That is, even if the SDV architecture is adopted, the self-vehicle (210) may be implemented with a structure in which the HPC (250) directly controls at least one terminal device, as in FIG. 2.

[0060]

[0061] FIG. 3 is a block diagram showing the configuration of a data management device according to one embodiment disclosed in this document.

[0062] Referring to FIG. 3, the data management device (300) may include a first control unit (311), a second control unit (312), a first DTG (321), and a second DTG (322).

[0063] According to one embodiment, the data management device (300) may perform power and / or data management between components for controlling the vehicle. For example, the vehicle may be operated by components according to the SDV architecture. For example, the SDV may include a hierarchical structure in the order of a high performance computer (HPC), a zone, an end device, and a sensor / actuator. At this time, the vehicle according to the SDV may be divided into multiple zones, and each zone may include a control unit (e.g., a zone controller) for controlling components of a lower layer included in the zone. The zone control unit is electrically connected to the HPC and can transmit and receive various signals. The above-described contents are exemplary, and embodiments of the present invention are not limited thereto. For example, according to another embodiment according to the SDV architecture (e.g., the SDV architecture embodiment according to FIG. 2), the HPC and the end device may be operatively connected, and the zone may be omitted. For example, the first control unit (311) and the second control unit (312) may be zoning controllers for controlling the first zone and the second zone among a plurality of zones within the vehicle, respectively.

[0064] The data management device (300) can transmit and receive at least one of power, data (e.g., wake-up packet), control signal, or any combination thereof to and from components included in the electronic device. In one embodiment, the electronic device may be a mobile device (e.g., a mobile phone, a laptop computer, a smart phone, a smart pad), an electric vehicle (e.g., an electric vehicle (EV), a hybrid EV (HEV), a plug-in HEV (PHEV), a fuel cell EV (FCEV)), an energy storage system (ESS), or a battery swapping system (BSS). In one embodiment, the electronic device may include a vehicle (e.g., an electric vehicle, a hybrid vehicle, etc.) and a moving body driven based on electrical energy. In other words, for example, the data management device (300) may be included in a vehicle and configured to manage data for operation of the vehicle (e.g., operation for autonomous driving control).

[0065] The operation of the data management device (300) below can be performed by a BMS (Battery management system) within a vehicle, a battery BMS provided within a battery pack, and can also be performed in various devices such as a server, cloud, charger, or charger / discharger.

[0066] According to one embodiment, the first control unit (311) and the second control unit (321) may include one or more processors corresponding to the first zone and the second zone of the vehicle, respectively. In FIG. 3, the data management device (300) is illustrated as including two control units (311, 312), but the embodiments of the present document are not limited thereto. For example, the data management device (300) may further include at least one control unit (or zoning controller) corresponding to each of a plurality of zones included in the vehicle.

[0067] For example, the first control unit (311) and the second control unit (312) may be electrically connected. The first control unit (311) and the second control unit (312) may be electrically connected to, for example, another component (e.g., at least one terminal device). The terminal device may include, for example, a battery management system (BMS).

[0068] For example, each processor included in the first control unit (311) and the second control unit (312) may include a central processing unit, an application processor, a graphics processing unit, a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor.

[0069] The functions and operations of the data management device (300) described below may be performed by one processor (or, the first control unit (311) and / or the second control unit (312)), or each function may be separated at least in part and performed by multiple processors.

[0070] According to one embodiment, the zone corresponding to the first control unit (311) and the second control unit (312) may be one of multiple zones of the physically separated vehicle. For example, the multiple zones may include a front zone including a front area of ​​the vehicle, a rear zone including a rear area, a left zone including a left area, and a right zone including a right area.

[0071] According to one embodiment, each zone may include a controller (e.g., a first control unit (311) and / or a second control unit (312)) for controlling and managing components for the operation of the vehicle (e.g., sensors, actuators, cameras, driving and braking devices, batteries, etc.).

[0072] According to one embodiment, the first control unit (311) and the second control unit (312) may correspond to the first zone and the second zone, respectively. In other words, the first control unit (311) may store and manage first driving data generated in the first zone, and the second control unit (312) may store and manage second driving data generated in the second zone.

[0073] For example, the first control unit (311) may be electrically connected to a first DTG (digital tacho graph) (321) for storing and managing first driving data, and the second control unit (312) may be electrically connected to a second DTG (digital tacho graph) (322) for storing and managing second driving data.

[0074] For example, the first DTG (321) may be mounted at a location corresponding to a different zone from the second DTG (322). For example, if the first DTG (321) is positioned in a portion of the front area of ​​the vehicle, the second DTG (322) may be positioned in at least a portion of the rear area, left area, and right area of ​​the vehicle.

[0075] For example, the first control unit (311) can store at least some of the first driving data regarding the first zone of the vehicle in the first DTG (321).

[0076] For example, the second control unit (312) can store at least some of the first driving data regarding the first zone of the vehicle in the second DTG (322).

[0077] For example, the first control unit (311) and the second control unit (312) can store the first driving data and the second driving data in the first DTG (321) corresponding to the first zone and the second DTG (322) corresponding to the second zone, respectively, via automotive Ethernet.

[0078] For example, if the amount of data processed in the first zone exceeds a specified amount, the first control unit (311) may transfer at least some of the first driving data stored in the first DTG (321) to the second DTG (322) and / or receive the second driving data from the second DTG (322) and then store it in the first DTG (321).

[0079] For example, the first control unit (311) can synchronize the stored driving data. For example, when the first control unit (311) receives the second driving data from the second DTG (322), the first control unit (311) can synchronize the first driving data and the second driving data stored in the first DTG (321). For example, the first control unit (311) can synchronize the first driving data and the second driving data based on at least one of the type, time stamp, time of occurrence, or any combination thereof of the first driving data and the second driving data, to generate synchronization data. The synchronization data can include, for example, integrated data for the operation of the vehicle. For example, the first control unit (311) can transmit the data to a vehicle controller (e.g., HPC (150, 250) of FIG. 1 or 2) for controlling the vehicle.

[0080] For example, when a designated event occurs for the vehicle, the first control unit (311) can increase the priority of at least one operation related to storage and management of the first driving data and the second driving data, and perform at least one operation before other operations.

[0081] For example, the first control unit (311) can raise the priority of an operation of storing and backing up the first driving data in the first DTG (321), transmitting the first driving data to the second DTG (322) whose mounting position is different from the first DTG (321), or storing the second driving data received from the second DTG (322) in the first DTG (321).

[0082] For example, if the first control unit (311) identifies an abnormality in the operation of the vehicle, it may determine that a designated event has occurred. An abnormality in the operation of the vehicle may include, for example, an accident, such as a collision between the vehicle and an external object (e.g., another vehicle) or a failure of at least some of the vehicle's components.

[0083] For example, if power supply to a specific zone is interrupted, the data management device (300) can store and manage driving data through power supplied from an emergency power source to the DTG corresponding to the specific zone.

[0084] For example, when power supply to the first zone is interrupted, power can be supplied to the first DTG (321) from the emergency power source. The first DTG (321) can transmit the first driving data stored in the first DTG (321) to the second DTG (322), for example, through Power over Ethernet (PoE) by the emergency power source. The first DTG (321) can receive and store the second driving data stored in the second DTG (322), for example, through Power over Ethernet (PoE) by the emergency power source.

[0085] According to one embodiment of the present document, a vehicle including the above-described data management device (300) may be disclosed. The vehicle may operate based on, for example, at least one driving data (or synchronization data) generated using the data management device (300).

[0086] The operation of the first control unit (311) described above may also be performed by the second control unit (312). In other words, the second control unit (312) may perform at least a part of the operation of the first control unit (311) described above. For example, when the amount of data generated in the second zone exceeds a specified amount, the second control unit (312) may transfer at least a part of the second driving data stored in the second DTG (322) to the first DTG (321), or may receive the first driving data from the first DTG (321) and then store it in the second DTG (322).

[0087]

[0088] FIG. 4 is a conceptual diagram showing the configuration of a data management device according to one embodiment disclosed in this document.

[0089] According to one embodiment, a vehicle (401) (e.g., vehicle (110, 210) of FIG. 1 or FIG. 2) may operate based on a data management device (e.g., data management device (300) of FIG. 3).

[0090] For example, the vehicle (401) may include a plurality of DTGs (421, 422, 423, and 424) each corresponding to a plurality of physically distinct zones.

[0091] For example, the vehicle (401) may include a front DTG (421) that stores and manages driving data generated in a zone including the front area of ​​the vehicle (401).

[0092] For example, the vehicle (401) may include a rear DTG (422) that stores and manages driving data generated in a zone including the rear area of ​​the vehicle (401).

[0093] For example, the vehicle (401) may include a left DTG (423) that stores and manages driving data generated in a zone including the left area of ​​the vehicle (401).

[0094] For example, the vehicle (401) may include a right DTG (424) that stores and manages driving data generated in a zone including the right area of ​​the vehicle (401).

[0095] According to one embodiment, the vehicle (401) can operate based on synchronization data (or integrated data) generated by synchronizing driving data stored in multiple DTGs (421, 422, 423, and 424).

[0096]

[0097] FIG. 5 is a conceptual diagram showing the configuration of a data management device according to one embodiment disclosed in this document.

[0098] According to one embodiment, a data management device (e.g., data management device (300) of FIG. 3) may include at least one of a vehicle controller (510) (e.g., HPC (150, 250) of FIG. 1 or FIG. 2), a first controller (521) (e.g., the first control unit (311) of FIG. 3), a second controller (522) (e.g., the second control unit (312) of FIG. 3), a third controller (523), a first DTG (551) (e.g., the first DTG (321) of FIG. 3), a second DTG (552) (e.g., the second DTG (322) of FIG. 3), a third DTG (553), an emergency power source (540), or any combination thereof. For example, components included in a data management device may transmit and receive power and / or data based on a first protocol (e.g., automotive Ethernet) or a second protocol (e.g., Power over Ethernet (PoE)).

[0099] In FIG. 5, the data management device is illustrated as including a vehicle controller (510) and an emergency power source (540), but this is exemplary, and the data management device may be implemented to be physically separated from the vehicle controller (510) and the emergency power source (540), and may be electrically connected to transmit and receive data and / or power.

[0100] For example, the vehicle controller (510) may transmit and receive data with a plurality of controllers corresponding to each of a plurality of zones included in the vehicle. The vehicle controller (510) may, for example, include at least one processor having relatively high performance compared to the plurality of controllers.

[0101] For example, the first controller (521), the second controller (522), and the third controller (523) may be provided to control components included in the first zone, the second zone, and the third zone among the plurality of zones, respectively.

[0102] For example, the first controller (521) can store and manage first driving data (531) generated (or identified) in the first zone in the first DTG (551).

[0103] For example, the second controller (522) can store and manage second driving data (532) occurring in the second zone in the second DTG (552).

[0104] For example, the third controller (523) can store and manage third driving data (533) generated (or identified) in the third zone in the third DTG (553).

[0105] Referring to FIG. 5, according to one embodiment, the data management device can transfer driving data to another DTG based on power supplied through an emergency power source (540) when power supply to some zones is interrupted.

[0106] For example, when the power supply to the first zone is interrupted, the first DTG (551) can receive power from the emergency power source (540). At this time, the first DTG (551) can transmit the first driving data stored in the first DTG (551) to the second DTG (552) and / or the third DTG (553) via PoE (Power over Ethernet) by the emergency power source (540), or can receive, store, and manage the driving data stored in the second DTG (552) and / or the third DTG (553) (e.g., the second driving data (552) and / or the third driving data (553)).

[0107]

[0108] Figure 6 is a flowchart of a data management method according to one embodiment disclosed in this document.

[0109] According to one embodiment, a data management device (e.g., data management device (300) of FIG. 3) can perform the operations disclosed in FIG. 6. For example, at least some of the components included in the data management device (e.g., first control unit (311), second control unit (312), first DTG (321), and / or second DTG (322) of FIG. 3) can be configured to perform the operations of FIG. 6.

[0110] In the following embodiments, operations S610 to S630 may be performed sequentially, but are not necessarily performed sequentially. For example, the order of the operations may be changed, and at least two operations may be performed in parallel. Furthermore, any content corresponding to or overlapping with the content described above with respect to FIG. 6 may be briefly described or omitted.

[0111] Referring to FIG. 6, the data management method may include a step of storing first driving data and second driving data (S610), a step of determining whether a data processing amount exceeds a specified amount (S620), and a step of exchanging driving data (S630).

[0112] In step S610, the data management device may store first driving data and second driving data in the DTG. For example, the data management device may store first driving data generated (or identified) in the first zone in the first DTG corresponding to the first zone. For example, the data management device may store second driving data generated (or identified) in the second zone in the second DTG corresponding to the second zone.

[0113] At step S620, the data management device can determine whether the data processing volume exceeds a specified amount. If the data processing volume exceeds the specified amount, the data management device can perform step S630, and if the data processing volume does not exceed the specified amount, the data management device can repeat step S610.

[0114] At step S630, the data management device can exchange driving data. For example, if the processing volume of first driving data generated in the first zone exceeds a specified amount, the data management device can transmit the first driving data to the second DTG or store the second driving data transmitted from the second DTG in the first DTG.

[0115]

[0116] Figure 7 is a flowchart of a data management method according to an embodiment disclosed in this document.

[0117] According to one embodiment, a data management device (e.g., data management device (300) of FIG. 3) can perform the operations disclosed in FIG. 7. For example, at least some of the components included in the data management device (e.g., first control unit (311), second control unit (312), first DTG (321), and / or second DTG (322) of FIG. 3) can be configured to perform the operations of FIG. 7.

[0118] In the following embodiments, operations S710 to S730 may be performed sequentially, but are not necessarily performed sequentially. For example, the order of the operations may be changed, and at least two operations may be performed in parallel. Furthermore, any content corresponding to or overlapping with the content described above with respect to FIG. 7 may be briefly described or omitted.

[0119] Referring to FIG. 7, the data management method may include a step of storing first driving data and second driving data (S710), a step of identifying the occurrence of a specified event (S720), and a step of increasing the priority of an operation related to driving data management (S730).

[0120] In step S710, the data management device may store first driving data and second driving data in the DTG. For example, the data management device may store first driving data generated (or identified) in the first zone in the first DTG corresponding to the first zone. For example, the data management device may store second driving data generated (or identified) in the second zone in the second DTG corresponding to the second zone.

[0121] At step S720, the data management device can monitor whether a specified event occurs in the vehicle. If it identifies an abnormality in the vehicle's operation, the data management device can determine that the specified event has occurred.

[0122] At step S730, the data management device can increase the priority of an operation of storing and backing up the first driving data, transmitting the first driving data to a second DTG whose mounting location is distinct from the first DTG, or storing the second driving data received from the second DTG in the first DTG. Through this, the data management device can implement a safe data storage algorithm by exchanging and backing up previously stored data between DTGs before or immediately after data damage occurs due to a malfunction of the vehicle (or an accident).

[0123]

[0124] FIG. 8 is a block diagram showing the hardware configuration of a computing system for performing an operation method of a data management device according to an embodiment disclosed in this document.

[0125] Referring to FIG. 8, a computing system (3000) according to an embodiment disclosed in the present document may include an MCU (1010), a memory (1020), an input / output I / F (1030), and a communication I / F (1040).

[0126] The MCU (1010) may be a processor that executes various programs stored in the memory (1020), processes various information including battery data through these programs, and performs the functions of the processor (or control unit) included in the data management device shown in FIG. 3 described above.

[0127] The memory (1020) can store various programs for performing the functions of the data management device. In addition, the memory (1020) can store various information, including battery data (voltage data, capacity data, etc.), differential capacity data, etc., and can include a constructed database.

[0128] Such memories (1020) may be provided in multiple numbers as needed. The memories (1020) may be volatile memories or non-volatile memories. As volatile memories (1020), RAM, DRAM, SRAM, etc. may be used. As non-volatile memories (1020), ROM, PROM, EAROM, EPROM, EEPROM, flash memories, etc. may be used. The examples of the memories (1020) listed above are merely examples and are not limited to these examples.

[0129] The input / output I / F (1030) can provide an interface that enables data transmission and reception between an input device (not shown) such as a keyboard, mouse, or touch panel, and an output device (not shown) such as a display and the MCU (1010).

[0130] The communication I / F (1040) is a component capable of transmitting and receiving various data with the server, and may be any device capable of supporting wired or wireless communication. For example, the data management device can transmit and receive various information, including battery data, from a separately provided external server, etc., via the communication I / F (1040).

[0131] In this way, a computer program according to an embodiment disclosed in this document may be implemented as a module that is recorded in a memory (1020) and processed by an MCU (1010) to perform each function illustrated in FIG. 1, for example.

[0132]

[0133] In the above, although all components constituting the embodiments disclosed in this document have been described as being combined or operating in combination as one, the embodiments disclosed in this document are not necessarily limited to such embodiments. That is, within the scope of the purpose of the embodiments disclosed in this document, all of the components may be selectively combined and operated one or more times.

[0134] In addition, terms such as "include," "comprise," or "have" described above, unless specifically stated to the contrary, should be interpreted to imply the inclusion of the corresponding component, and thus should not be interpreted to exclude other components, but rather to include other components. All terms, including technical or scientific terms, have the same meaning as commonly understood by a person of ordinary skill in the art to which the embodiments disclosed in this document belong, unless otherwise defined. Commonly used terms, such as terms defined in a dictionary, should be interpreted to be consistent with the contextual meaning of the relevant technology, and shall not be interpreted in an idealized or overly formal sense, unless explicitly defined in this document.

[0135] The above description is merely an illustrative description of the technical ideas disclosed in this document, and those skilled in the art to which the embodiments disclosed in this document pertain may make various modifications and variations without departing from the essential characteristics of the embodiments disclosed in this document. Therefore, the embodiments disclosed in this document are not intended to limit the technical ideas of the embodiments disclosed in this document, but to explain them, and the scope of the technical ideas disclosed in this document is not limited by these embodiments. The scope of protection of the technical ideas disclosed in this document should be interpreted by the claims below, and all technical ideas within a scope equivalent thereto should be interpreted as being included in the scope of rights of this document.

Claims

1. A first control unit electrically connected to a first DTG (digital tacho graph); and a second control unit electrically connected to the second DTG; The above first control unit: Store first driving data regarding the first zone of the vehicle in the first DTG, The second control unit: configured to store second driving data regarding a second zone distinct from the first zone of the above-mentioned vehicle in the second DTG; Data management device.

2. In paragraph 1, The above first control unit, When the amount of data processed in the first zone exceeds a specified amount, the first driving data stored in the first DTG is transmitted to the second DTG, or the second driving data is received from the second DTG and then stored in the first DTG. Data management device.

3. In paragraph 2, The above first control unit, When the second driving data is received, synchronization data is generated by synchronizing the first driving data and the second driving data based on at least one of the type, time stamp, occurrence time, or any combination thereof of the first driving data and the second driving data, configured to transmit the synchronization data to a vehicle controller for controlling the above-mentioned vehicle, Data management device.

4. In paragraph 1, The above first driving data and the above second driving data, Characterized in that it is stored in the first DTG corresponding to the first zone and the second DTG corresponding to the second zone, respectively, through automotive Ethernet. Data management device.

5. In paragraph 1, The above first control unit, When a designated event occurs for the vehicle, the priority of an operation of storing and backing up the first driving data, transmitting the first driving data to the second DTG whose mounting location is distinct from the first DTG, or storing the second driving data received from the second DTG in the first DTG is configured to be increased. Data management device.

6. In paragraph 5, The above first control unit, When an abnormality in the operation of the above-mentioned vehicle is identified, it is configured to determine that the above-mentioned specified event has occurred. Data management device.

7. In paragraph 1, When the power supply to the above first zone is interrupted, the above first DTG is supplied with power from the emergency power source, Characterized in that the first driving data stored in the first DTG is transmitted to the second DTG or the second driving data stored in the second DTG is transmitted to the first DTG via PoE (Power over Ethernet) by the emergency power source. Data management device.

8. Comprising any one of the data management devices of claims 1 to 7, vehicle.

9. A step in which the first control unit stores first driving data regarding the first zone of the vehicle in the first DTG corresponding to the first zone; and A second control unit includes a step of storing second driving data regarding a second zone, which is distinct from the first zone of the vehicle, in a second DTG corresponding to the second zone; How to manage data.

10. In paragraph 9, The above data management method is, The first control unit further includes a step of transmitting the first driving data stored in the first DTG to the second DTG when the amount of data generated in the first zone exceeds a specified amount, or receiving the second driving data from the second DTG and then storing it in the first DTG; How to manage data.

11. In paragraph 10, The above data management method is, A step of generating synchronization data by synchronizing the first driving data and the second driving data based on at least one of the type, time stamp, occurrence time, or any combination thereof of the first driving data and the second driving data, when the first control unit receives the second driving data; and The first control unit further includes a step of transmitting the synchronization data to a vehicle controller for controlling the vehicle; How to manage data.

12. In paragraph 9, The above first driving data and the above second driving data, Characterized in that it is stored in the first DTG corresponding to the first zone and the second DTG corresponding to the second zone, respectively, through automotive Ethernet. How to manage data.

13. In paragraph 9, The above data management method is, The first control unit further includes a step of increasing the priority of an operation of storing and backing up the first driving data, transmitting the first driving data to the second DTG whose mounting position is different from the first DTG, or storing the second driving data received from the second DTG in the first DTG when a designated event for the vehicle occurs; How to manage data.

14. In paragraph 13, The above data management method is, The first control unit further includes a step of determining that the specified event has occurred when identifying that an abnormality has occurred in the operation of the vehicle; How to manage data.

15. In paragraph 9, The above data management method is, A step for supplying power from an emergency power source when the power supply to the first zone is interrupted; and A step in which the first driving data stored in the first DTG is transmitted to the second DTG or the second driving data stored in the second DTG is transmitted to the first DTG through PoE (Power over Ethernet) by the emergency power source; further comprising; How to manage data.

Images