Data management device, vehicle comprising same and method

CN122514932APending Publication Date: 2026-08-04LG ENERGY SOLUTION LTD
View PDF 1 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
LG ENERGY SOLUTION LTD
Filing Date
2025-05-22
Publication Date
2026-08-04

AI Technical Summary

Benefits of technology

[0036]The data management apparatus and method according to the embodiments disclosed herein can provide a data management method for vehicles that can reduce network load and reduce latency during data transmission and reception by performing packetization based on data characteristics, thereby enabling efficient communication in a software-defined vehicle (SDV) architecture as the amount of data to be transmitted and received between components increases.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122514932A_ABST
    Figure CN122514932A_ABST
Patent Text Reader

Abstract

According to the embodiments disclosed in this document, the data management device may include a main control unit, an auxiliary control unit electrically connected to the main control unit, and a terminal device, wherein the auxiliary control unit: receives data from at least one of the main control unit, the terminal device, or any combination thereof; generates at least one frame by grouping the data based on a specified standard; and sends at least one frame to a target device identified based on the specified standard.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Cross-reference to related applications

[0002] This application claims priority to Korean Patent Application No. 10-2024-0070064, filed on May 29, 2024, the disclosure of which is incorporated herein by reference. Technical Field

[0003] The embodiments disclosed herein relate to a data management apparatus and method, and a vehicle including the data management apparatus. Background Technology

[0004] As electric vehicles become increasingly prevalent, research and development of new vehicle architectures are actively underway. For example, electric vehicles can be powered by rechargeable batteries, including conventional Ni / Cd and Ni / MH batteries, as well as the more recent lithium-ion batteries. Among rechargeable batteries, lithium-ion batteries offer significantly higher energy density than existing Ni / Cd and Ni / MH batteries. Furthermore, because lithium-ion batteries can be manufactured to be small and lightweight, they are used as power sources for mobile devices, and in recent years, their applications have expanded to include electric vehicles, making them a focus of attention as a next-generation energy storage medium.

[0005] These battery cells, modules, packs, or racks can be used in a variety of devices. For example, they can be used in mobile devices such as mobile phones, laptops, smartphones, and tablets, as well as in electric vehicles (EVs, hybrid electric vehicles (HEVs), plug-in hybrid electric vehicles (PHEVs)) and energy storage systems (ESS).

[0006] The state and operation of these batteries can be managed and controlled by a battery management system (BMS). The BMS can be included in a single device along with the batteries.

[0007] Furthermore, with the evolution of the automotive industry, concepts of future mobility, such as Software-Defined Vehicles (SDVs) and Personalized Vehicles (PBVs), are becoming increasingly concrete. For example, an SDV is a vehicle that uses software to control and manage hardware components. Based on the software of an SDV, not only can the vehicle's driving performance be defined, but also its convenience features, safety features, perceived quality, and brand identity. Through the architecture of SDVs, vehicle development costs can be reduced through ECU standardization and software internalization. Moreover, autonomous driving technology can be improved through high-performance computers and networks based on electronic architecture. Summary of the Invention

[0008] Technical issues

[0009] In the process of performing autonomous driving control of vehicles, managing and storing autonomous driving-related data is becoming increasingly important. In vehicles, including those with software-defined vehicle (SDV) architectures, specific control units (e.g., auxiliary control units or area controllers) can be used as gateways or network switches to perform signal-to-data-frame format conversion or execute response logic based on various data management methods in critical environments such as accident detection.

[0010] The embodiments disclosed herein aim to provide a data management apparatus and method, and a vehicle including the data management apparatus, which uses frames (or jumbo frames) generated by performing packetization based on the characteristics of the data when sending and receiving (or routing) data between components (e.g., high-performance computer (HPC) (or main control unit), area controller (or auxiliary control unit), and terminal device) according to the SDV architecture in a vehicle including an SDV architecture.

[0011] The technical problems of the embodiments disclosed herein are not limited to those mentioned above, and other objectives not mentioned will be clearly understood by those skilled in the art based on the following description.

[0012] Technical solution

[0013] According to the embodiments disclosed herein, a data management device is provided, the device including a main control unit, an auxiliary control unit electrically connected to the main control unit, and a terminal device.

[0014] According to an implementation, the data management device can be configured to: receive data from at least one of a main control unit, a terminal device, or any combination thereof; group the data based on a specified reference and generate at least one frame; and send at least one frame to a target device identified based on the specified reference.

[0015] According to the implementation, the auxiliary control unit can be configured to aggregate data received during a first time period and group the data based on at least one of the data type, destination, domain, or any combination thereof.

[0016] According to the implementation, the auxiliary control unit can be configured to: group data and generate a target jumbo frame to be sent to the target device; identify the control cycle of the target device; and send the target jumbo frame to the target device when the control cycle is reached for the first time.

[0017] According to the implementation method, the auxiliary control unit may include multiple area controllers.

[0018] According to the implementation method, the auxiliary control unit can be configured to send data to a second area controller corresponding to the characteristics of the data when a first area controller among a plurality of area controllers receives data.

[0019] According to an implementation, the first area controller can be configured to: receive data from at least one of a main control unit, a terminal device, or any combination thereof based on a first communication speed; and send data to the second area controller based on a second communication speed that is higher than the first communication speed.

[0020] According to the implementation method, the target device may correspond to one of the multiple high-performance computers (HPCs) included in the main control unit.

[0021] According to the embodiments disclosed herein, a vehicle including the data management device described above is provided.

[0022] According to the embodiments disclosed herein, a data management method includes the following steps: receiving data from at least one of a main control unit, a terminal device, or any combination thereof by an auxiliary control unit; grouping the data based on a specified reference and generating at least one frame by the auxiliary control unit; and sending at least one frame to a target device identified based on the specified reference by the auxiliary control unit.

[0023] According to an implementation, the data management method may further include the following steps: the auxiliary control unit aggregates the data received during a first time period, and groups the data based on at least one of the data type, destination, domain, or any combination thereof.

[0024] According to the implementation method, the data management method may further include the following steps: the auxiliary control unit groups the data and generates a target megaframe to be sent to the target device; the auxiliary control unit identifies the control cycle of the target device; and when the control cycle is reached at the first moment, the auxiliary control unit sends the target megaframe to the target device.

[0025] According to the implementation method, the data management method may further include the following steps: when a first area controller among a plurality of area controllers included in the auxiliary control unit receives data, the auxiliary control unit sends the data to a second area controller corresponding to the characteristics of the data.

[0026] According to an implementation, the data management method may further include the following steps: receiving data from at least one of a main control unit, a terminal device, or any combination thereof based on a first communication speed; and sending data from the first area controller to a second area controller based on a second communication speed higher than the first communication speed.

[0027] According to an implementation, the data management method may further include processing the frame by the target device by dividing at least one frame into service units.

[0028] According to the embodiments disclosed herein, an auxiliary control unit for controlling a data management device includes a memory configured to store at least one instruction and a processor operatively connected to the memory.

[0029] According to the implementation, at least one instruction, when executed by the processor, can cause the auxiliary control unit to: receive data from at least one of the main control unit, the terminal device, or any combination thereof; group the data based on a specified reference and generate at least one frame; and send at least one frame to a target device identified based on the specified reference.

[0030] According to an implementation, at least one instruction, when executed by a processor, can cause the auxiliary control unit to aggregate data received during a first time period and group the data based on at least one of the data type, destination, domain, or any combination thereof.

[0031] According to an implementation, at least one instruction, when executed by a processor, can cause the auxiliary control unit to aggregate data received during a first time period and group the data based on at least one of the data type, destination, domain, or any combination thereof.

[0032] According to the implementation, at least one instruction, when executed by the processor, can cause the auxiliary control unit to: group data and generate a target jumbo frame to be sent to the target device; identify the control cycle of the target device; and send the target jumbo frame to the target device when the control cycle is reached for the first time.

[0033] According to the implementation, the auxiliary control unit may further include multiple region controllers. For example, when executed by the processor, at least one instruction may cause the auxiliary control unit to send data to a second region controller corresponding to the characteristics of the data when the first region controller among the multiple region controllers receives the data.

[0034] According to an implementation, at least one instruction, when executed by a processor, can cause an auxiliary control unit to: receive data from at least one of a main control unit, a terminal device, or any combination thereof via a first area controller based on a first communication speed; and send data from the first area controller to a second area controller based on a second communication speed higher than the first communication speed.

[0035] Beneficial effects

[0036] The data management apparatus and method according to the embodiments disclosed herein can provide a data management method for vehicles that can reduce network load and reduce latency during data transmission and reception by performing packetization based on data characteristics, thereby enabling efficient communication in a software-defined vehicle (SDV) architecture as the amount of data to be transmitted and received between components increases.

[0037] In addition, various effects can be provided, either directly or indirectly, through this disclosure. Attached Figure Description

[0038] Figure 1 This is a conceptual diagram illustrating the structure of a vehicle including a data management device according to an embodiment disclosed herein.

[0039] Figure 2 This is a conceptual diagram illustrating the structure of a vehicle including a data management device according to an embodiment disclosed herein.

[0040] Figure 3 This is a block diagram illustrating the configuration of a data management apparatus according to an embodiment disclosed herein.

[0041] Figure 4 This is a block diagram illustrating the configuration of an auxiliary control unit according to an embodiment disclosed herein.

[0042] Figure 5 This is a conceptual diagram illustrating the configuration of a data management apparatus according to an embodiment disclosed herein.

[0043] Figure 6 This is a conceptual diagram illustrating the configuration of a data management apparatus according to an embodiment disclosed herein.

[0044] Figure 7 This is a conceptual diagram illustrating a method for transmitting data by a data management device according to an embodiment disclosed herein.

[0045] Figure 8 This is a flowchart of a data management method according to the embodiments disclosed herein.

[0046] Figure 9 This is a flowchart of a data management method according to the embodiments disclosed herein.

[0047] Figure 10 This is a flowchart of a data management method according to the embodiments disclosed herein.

[0048] Figure 11 This is a block diagram illustrating the hardware configuration of a computing system for performing a method of an operational data management device according to an embodiment disclosed herein. Detailed Implementation

[0049] In the following description, various embodiments of the invention disclosed herein will be described with reference to the accompanying drawings. However, this is not intended to limit the invention to the specific embodiments, and it will be construed as including various modifications, equivalents, and / or alternatives to the embodiments of the invention.

[0050] In this document, it should be understood that the singular form of the noun corresponding to an item may include one or more of the aforementioned items, unless the relevant context explicitly indicates otherwise. As used herein, each of the 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 include any one or all possible combinations of the items listed together in the corresponding phrase within the phrase. Terms such as “first” and “second,” or “first” and “second” may be used simply to distinguish corresponding components from one other component and do not limit the components in other respects (e.g., importance or order). It should be understood that if an element (e.g., a first element) is referred to as “connected to another element (e.g., a second element),” “linked to another element,” “connected to another element,” or “attached to another element” with or without the terms “operably” or “communically,” this means that the element can be connected to the other element directly (e.g., wired), wirelessly, or via a third element.

[0051] Each of the components (e.g., modules or programs) described herein may include a single entity or multiple entities. According to various embodiments, one or more components may be omitted, or one or more other components may be added. Alternatively or additionally, multiple components (e.g., modules or programs) may be integrated into a single component. In this case, the integrated component may still perform one or more functions of each of the multiple components in the same or similar manner as the corresponding components of the multiple components performed one or more functions prior to integration. According to various embodiments, operations performed by a module, program, or other component may be performed sequentially, in parallel, repeatedly, or heuristically, or one or more operations may be performed in a different order or omitted, or one or more other operations may be added.

[0052] As used herein, the terms "module" or "unit" can include units implemented in hardware, software, or firmware, and are used interchangeably with other terms such as "logic," "logic block," "component," or "circuit." A module can be a single integrated component, or the smallest unit or part thereof suitable for performing one or more functions. For example, depending on the implementation, a module can be implemented as an application-specific integrated circuit (ASIC).

[0053] The various implementations described herein can be implemented as software (e.g., a program) or application comprising one or more instructions stored in a machine-readable storage medium (e.g., memory). For example, a machine's processor can invoke and execute at least one of one or more instructions stored in the storage medium. This allows the machine to operate to perform at least one function according to the invoked at least one instruction. 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, the term "non-transitory" means only that the storage medium is a physical device and does not include signals (e.g., electromagnetic waves), but the term does not distinguish between cases where data is stored semi-permanently in the storage medium and cases where data is temporarily stored in the storage medium.

[0054] Figure 1 This is a conceptual diagram illustrating the structure of a vehicle including a data management device according to an embodiment disclosed herein.

[0055] According to an implementation, a data management device (e.g., Figure 3 The data management device 300 may include at least some of the components included in the vehicle 110 according to a software-defined vehicle (SDV) architecture. The data management device may, for example, manage the transmission and / or reception of power and / or data between the components of the vehicle 110.

[0056] For example, vehicle 110 may include at least one of the following: a first area controller 121, a second area controller 122, a third area controller 123, a fourth area 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 transmit / receive path 160, an additional element 170, or any combination thereof. A data management device for managing data of vehicle 110 may include at least some of the components included in vehicle 110.

[0057] For example, the components of the SDV architecture can be hierarchically structured as HPC 150, area controller, and terminal device.

[0058] For example, HPC 150 can connect to a first area controller 121, a second area controller 122, a third area controller 123, and a fourth area controller 124, and can send various types of data to each area controller and receive various types of data from each area controller.

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

[0060] For example, the first area controller 121 and the second area controller 122 can control the first actuator 141 and the second actuator 142, respectively. The actuator may include, for example, at least one drive device for driving the vehicle 110.

[0061] For example, the aforementioned components can communicate via automotive Ethernet based on a specified path (e.g., transmit / receive path 160).

[0062] The data management device according to the embodiments disclosed herein can control and manage the communication process of power and / or data transmitted and received between the aforementioned components.

[0063] Figure 2 This is a conceptual diagram illustrating the structure of a vehicle including a data management device according to an embodiment disclosed herein.

[0064] exist Figure 2 In the middle, used with Figure 1 The descriptions of components with the same name defined in the above can be used. Figure 1 The explanation is used instead.

[0065] For example, the main 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 transmit / receive path 260, an additional element 270, or any combination thereof. A data management device for managing data of the main vehicle 210 may include at least some of the components included in the main vehicle 210.

[0066] For example, with Figure 1 In comparison, according to Figure 2 The master vehicle 210 does not include a region controller. That is, even when using an SDV architecture, the master vehicle 210 can be implemented using an HPC 250 to directly control at least one terminal device, such as... Figure 2 As shown.

[0067] Figure 3This is a block diagram illustrating the configuration of a data management apparatus according to an embodiment disclosed herein.

[0068] Reference Figure 3 The data management device 300 may include a main device 310, a main control unit 320, an auxiliary control unit 330, and / or a terminal device 340.

[0069] According to an embodiment, the data management device 300 can perform power and / or data management between components used to control the main vehicle. For example, the main vehicle can be operated by components based on an SDV architecture. For example, an SDV can include a hierarchical structure of HPC (High-Performance Computing), zones, terminal devices, and sensors / actuators. In this case, the vehicle according to the SDV can be divided into multiple zones, and each zone can include a controller (e.g., a zone controller) for controlling the lower-level components included in that zone. The zone controller can be electrically connected to the HPC and can send and receive various signals. The above is exemplary, and embodiments of the invention are not limited thereto. For example, according to another embodiment based on an SDV architecture (e.g., Figure 2 In the SDV architecture implementation shown, the HPC and terminal devices are operatively connected, and areas can be omitted. For example, the auxiliary control unit 330 may include a zone controller corresponding to each of a plurality of zones (e.g., front zone, rear zone, left zone, right zone) within the main vehicle.

[0070] The data management device 300 can send and receive at least one of power, data (e.g., wake-up packets), control signals, or any combination thereof to components included in the electronic device. In embodiments, the electronic device can be a mobile device (e.g., a mobile phone, laptop computer, smartphone, or tablet), an electric vehicle (e.g., an electric vehicle (EV), a hybrid electric vehicle (HEV), a plug-in hybrid electric vehicle (PHEV), or a fuel cell electric vehicle (FCEV)), an energy storage system (ESS), or a battery swapping system (BSS). In embodiments, the electronic device can include a vehicle (e.g., an electric vehicle, a hybrid vehicle, etc.) and an electrically powered mobile device. In other words, for example, the data management device 300 can be included in a vehicle and can be configured to manage data for vehicle operation (e.g., operation for autonomous driving control).

[0071] The operation of the data management device 300 can be performed by the battery management system (BMS) in the vehicle or the battery BMS located in the battery pack, and can also be performed in various devices such as servers, cloud, chargers or chargeers.

[0072] According to the implementation, the main device 310 can be electrically connected to the main control unit 320, the auxiliary control unit 330 and / or the terminal device 340 to send, receive and manage various types of data.

[0073] For example, the main device 310 may be a first control device included in the main control unit 320 or the auxiliary control unit 330, or it may correspond to a second control device that is separate from the main control unit 320 and the auxiliary control unit 330.

[0074] For example, the main unit 310 may be one of a plurality of HPCs included in the main control unit 320 and a plurality of area controllers included in the auxiliary control unit 330.

[0075] For example, the main device 310 may be a separate control device (e.g., HPC or controller) that is physically and logically separate from the main control unit 320 and the auxiliary control unit 330.

[0076] For example, although the master device 310 is shown as a single unit, the data management device 300 may also include at least one additional master device.

[0077] For example, the main device 310 can generate and update network policies and control commands regarding communication protocols (such as data generation, sending and receiving, processing, deletion, storage, etc.) within the data management device 300.

[0078] For example, the master device 310 may send control signals to the master control unit 320 and / or the auxiliary control unit 330, including at least one of network policies, control commands, or any combination thereof regarding the communication protocol. The control signals may include information relating to, for example, the type of data frame, priority according to the type, destination, source, transmission method, transmission path, or any combination thereof. The master control unit 320 and / or the auxiliary control unit 330 may, for example, generate data based on the control signals received from the master device 310 and transmit that data to another device.

[0079] For example, the main device 310 can update network policies, control commands, or any combination thereof based on at least one of the network status between the main control unit 320 and the auxiliary control unit 330, an administrator command received from an external source, or any combination thereof. The main device 310 can retransmit control signals including updated content to the auxiliary control unit 330 at specific intervals.

[0080] According to the implementation, the main device 310 can determine network policies and / or control commands based on the operating status of the main vehicle including the data management device 300, and send network policies and / or control commands to other devices.

[0081] For example, when the main vehicle is operating in a normal state (e.g., stopped, driving, etc.), the main device 310 can send predefined network policies and / or control commands to another device.

[0082] For example, the master device 310 can send a predefined network policy to a terminal device 340 associated with the battery (e.g., BMS). This network policy includes a method (or protocol) for sending battery information (e.g., cell data). When the master vehicle is in normal operation, the terminal device 340 can continuously update and refresh the battery information based on the predefined network policy. If the terminal device 340 fails to send the first battery information to another device at a first time point, it can send the second battery information at a second time point, which is the next transmission cycle, without retransmitting the first battery information. The first battery information can be the battery information updated at the first time point, and the second battery information can be the battery information updated at the second time point. In other words, when the master vehicle is in normal operation, the master device 310 can determine a network policy such that if the terminal device 340 fails to send the battery information to another device at a certain time point while updating the battery information in real time, it will not send the corresponding information again, and will send the updated real-time battery information at the transmission time point of the next transmission cycle. In this way, when the master vehicle is in normal condition, unnecessary retransmission is not performed after data transmission failure. Instead, updated information can be sent in real time only at the next transmission time, thereby achieving an effective communication protocol.

[0083] For example, when the main vehicle is operating in a diagnostic (or inspection) state, the main device 310 can send network policies and / or control commands for data transmission and reception to the terminal device 340 associated with the component being diagnosed.

[0084] For example, when the main vehicle is operating in a battery diagnostic state, the main device 310 can send network policies and / or control commands to a battery-specific terminal device (e.g., BMS) in the terminal device 340 for sending and receiving battery diagnostic-related data (e.g., cell data).

[0085] For example, based on received network policies and / or control commands, a specific terminal device may permanently or, relative to other data, store battery diagnostic data for an extended period of time. In this case, unlike the normal state of the main vehicle, the terminal device may store all diagnostic data generated during the diagnostic process and send all stored diagnostic data to another device. The specific terminal device may, for example, identify a specific HPC regarding the diagnostic state among the multiple HPCs included in the main control unit 320, and send the battery diagnostic data directly to the specific area controller corresponding to the specific HPC among the multiple area controllers included in the auxiliary control unit 330. This sending process may be a logical sending process including routing. The specific terminal device may continuously send battery diagnostic data without deleting it at specified intervals until it receives an acknowledgment (ACK) signal indicating that battery diagnostic data has been received from, for example, the specific HPC and / or the specific area controller.

[0086] For example, when a malfunction occurs in the main vehicle or an accident involving the main vehicle occurs, the main device 310 can generate network policies and / or control commands and send them to other devices. These network policies and / or control commands instruct the other devices to increase the priority of sending and receiving data generated from devices involved in the malfunction and / or accident (e.g., auxiliary control unit 330 and / or terminal device 340).

[0087] For example, when a fault and / or accident is detected in a specific area among multiple areas of the main vehicle, the main device 310 can generate network policy and / or control commands and send the network policy and / or control commands to at least one device included in the data management device 300. The network policy and / or control commands instruct the at least one device to increase the priority of sending and receiving operations of data generated in the specific area (or data generated from the area controller and / or terminal device 340 corresponding to the specific area).

[0088] For example, when an accident or warning occurs in the primary vehicle, the primary device 310 can specify data corresponding to the situation in a specified format (e.g., permanent or event format) and send that data to other devices. For instance, when a first area controller, included in the auxiliary control unit 330 and communicating with the first HPC, receives the specified data, the first area controller can send the specified data to at least one other HPC besides the first HPC. The at least one HPC can be, for example, an HPC included in one of the multiple areas of the primary vehicle, excluding the first area containing the first area controller.

[0089] For example, a region controller and / or terminal device 340 corresponding to (or included in) a specific region can perform control based on received network policies and / or control commands, so that data related to faults and / or accidents in the specific region can be quickly and reliably transmitted to other devices handling faults and / or accidents by enhancing the transmission speed, quality, stability, etc. of the corresponding data.

[0090] According to one implementation, the main control unit 320 may include a plurality of HPCs.

[0091] For example, the main control unit 320 can perform operations such as data generation, transmission / reception, processing, deletion, and storage based on control signals received from the main device 310.

[0092] For example, the main control unit 320 can receive data frames from the auxiliary control unit 330.

[0093] According to the implementation, the auxiliary control unit 330 can perform operations such as data generation, transmission / reception, processing, deletion and storage based on control signals received from the main device 310, and can adjust the operation weight of each of the multiple functions that the auxiliary control unit 330 can perform.

[0094] For example, the auxiliary control unit 330 can generate data frames based on control signals.

[0095] For example, the auxiliary control unit 330 can determine the transmission method and transmission path of the data frame based on the control signal, and then send the data frame to the main control unit 320 corresponding to the data frame.

[0096] For example, the auxiliary control unit 330 can identify the designated HPC (or target device) corresponding to the data frame among the multiple HPCs included in the main control unit 320 based on control signals.

[0097] For example, the auxiliary control unit 330 can identify the control cycle of a specified HPC and then continue to aggregate data frames during the identified control cycle.

[0098] For example, the auxiliary control unit 330 can send aggregated data frames to a designated HPC based on a control cycle. In other words, the auxiliary control unit 330 can aggregate data frames during a control cycle and send the aggregated data frames (or jumbo frames) to the designated HPC.

[0099] For example, a designated HPC (or target device) can process data frames (or at least one frame) received from the auxiliary control unit 330 by dividing the data frames into service units. The target device can, for example, process data items included in at least one frame by dividing the data items into a first service related to the battery pack, a second service related to the sensor, a third service related to multimedia, etc. In this case, the target device can correspond to one of the multiple HPCs included in the main control unit 320.

[0100] For example, the auxiliary control unit 330 can adjust the operational weight of each of a plurality of functions, including at least one of terminal device control, network communication, protection, monitoring, or any combination thereof, based on control signals. By adjusting the operational weights, the auxiliary control unit 330 can change the priority, processing time, load, processing volume, etc. of each of the plurality of functions.

[0101] According to an embodiment, the terminal device 340 may be electrically connected to the auxiliary control unit 330, the main control unit 320, and / or the main device 310.

[0102] For example, terminal device 340 may include multiple control devices for controlling components of the main vehicle (e.g., sensors, cameras, battery packs, actuators, etc.).

[0103] For example, terminal device 340 may be a BMS including a battery pack, but this is exemplary and the embodiments disclosed herein are not limited thereto.

[0104] For example, terminal device 340 can receive control signals from master device 310. Terminal device 340 can, for example, generate battery pack data frames for controlling the battery pack based on the control signals, and control the battery pack based on the battery pack data frames.

[0105] For example, the terminal device 340 can perform operations such as controlling the battery pack's operating time, operating intensity, temperature and / or pressure, and controlling the TP based on the battery pack data frame.

[0106] For example, the terminal device 340 can send the battery pack control process, control results, and information about the battery pack to the auxiliary control unit 330, the main control unit 320, and / or the main device 310 based on the battery pack data frame.

[0107] For example, terminal device 340 can identify a designated area controller corresponding to the battery pack data frame among multiple area controllers included in auxiliary control unit 330 based on control signals. The designated area controller may be, for example, an area controller installed in an area including the battery pack.

[0108] For example, the terminal device 340 can aggregate battery pack data frames during the control cycle of a designated area controller and send the aggregated battery pack data frames (or battery pack jumbo frames) to the designated area controller based on the control cycle.

[0109] Figure 4 This is a block diagram illustrating the configuration of an auxiliary control unit according to an embodiment disclosed herein.

[0110] According to an implementation, a data management device (e.g., Figure 3 The data management device 300 in the middle) may include an auxiliary control unit 400 (e.g., Figure 3 (Auxiliary control unit 330 in the middle).

[0111] According to an embodiment, the auxiliary control unit 400 may include a memory 410 and a processor 420. Figure 4 The configuration of the auxiliary control unit 400 shown is exemplary, and embodiments of the present invention are not limited thereto. For example, the auxiliary control unit 400 may also include... Figure 4 Components not shown (e.g., communication unit, display unit, notification unit, multiple area controllers or any combination thereof).

[0112] According to the implementation, memory 410 may store commands or data. For example, memory 410 may store one or more instructions that, when executed by processor 420, cause auxiliary control unit 400 to perform various operations.

[0113] For example, memory 410 may be implemented together with processor 420 in a single chipset. Processor 420 may include at least one of a communication processor or a modem.

[0114] For example, memory 410 may store various types of information related to the data management device (or battery pack). For example, memory 410 may store information related to the operation history of processor 420. For example, memory 410 may store information related to the status and / or operation of components of auxiliary control unit 400 (or battery pack).

[0115] For example, memory 410 may include multiple different types of storage devices. For example, memory 410 may include at least one of random access memory (RAM), embedded multimedia card (eMMC), or any combination thereof.

[0116] According to one embodiment, the processor 420 may be operatively connected to the memory 410. For example, the processor 420 may control the operation of the memory 410.

[0117] For example, the processor 420 can be implemented as any of a microcontroller unit (MCU), a domain controller unit (DCU), or a zone control unit (ZCU).

[0118] For example, processor 420 can be derived from the host device (e.g., Figure 3 The master device 310 receives control signals including at least one of network policies regarding communication protocols, control commands, or any combination thereof.

[0119] For example, the control signal may include information relating to at least one of the following: the type of data frame to be generated and managed by the auxiliary control unit 400, priority according to the type, destination, source, transmission method, transmission path, or any combination thereof.

[0120] For example, processor 420 can generate data frames and determine the transmission method and transmission path based on control signals, and then send them to the main control unit corresponding to the data frame (e.g., ...). Figure 3 The main control unit 320 in the middle sends data frames.

[0121] For example, the processor 420 can identify the designated HPC corresponding to the data frame among the multiple HPCs included in the main control unit based on control signals, aggregate the data frame during the control cycle of the designated HPC, and send the aggregated data frame to the designated HPC based on the control cycle.

[0122] For example, processor 420 can adjust the operational weight of each of a plurality of functions, including at least one of terminal device control, network communication, protection, monitoring, or any combination thereof, based on control signals.

[0123] For example, processor 420 can access the main control unit and / or terminal device (e.g., Figure 3 The terminal device 340 receives various types of data. The processor 420 can, for example, group the received data based on a specified reference and generate at least one frame (or jumbo frame), and send the generated at least one frame to a target device identified based on the specified reference.

[0124] For example, the target device may be at least one of multiple HPCs included in the main control unit, multiple area controllers included in the auxiliary control unit, a main device, or any combination thereof.

[0125] For example, processor 420 can aggregate data received during a first time period and group the data based on at least one of data type, destination, domain, or any combination thereof.

[0126] For example, processor 420 can group the data and generate a target jumbo frame to be sent to the target device. The target jumbo frame may, for example, include the result of aggregating data generated by the target device during a first time period.

[0127] For example, the processor 420 can identify the control cycle of the target device and send the target jumbo frame to the target device when the control cycle is reached. Since the target device receives the aggregated target jumbo frame once in each control cycle, the network load on the data management device can be reduced, and data transmission and reception can be performed efficiently in each control cycle without data loss.

[0128] For example, the auxiliary control unit 400 may include multiple area controllers. Each of the multiple area controllers may include a processor 420.

[0129] For example, the first area controller may receive data from at least one of a main control unit, a terminal device, or any combination thereof. The first area controller may, for example, send data to a second area controller corresponding to the characteristics of the received data.

[0130] For example, the first area controller may receive data from at least one of the main control unit, terminal device, or any combination thereof based on a first communication speed (e.g., 1 Gbps).

[0131] For example, a first area controller can send data to a second area controller based on a second communication speed (e.g., 10 Gbps). The second communication speed can be higher than the first communication speed.

[0132] In other words, the auxiliary control unit 400 can operate at a relatively higher communication speed when performing internal communication than when performing external communication.

[0133] Figure 5 This is a conceptual diagram illustrating the configuration of a data management apparatus according to an embodiment disclosed herein.

[0134] According to an implementation, a data management device (e.g., Figure 3 The data management device 300 in the middle) may include a main device 510 (e.g., Figure 3 The main device 310; multiple main control units 521, 522, 523 and 524; multiple auxiliary control units 531 and 532; and multiple terminal devices 541, 542 and 543.

[0135] according to Figure 5The main device 510 can control the data generation, transmission / reception, processing, deletion, and management operations of other components through network policy 550. Network policy 550 can be updated and then transmitted, for example, based on a specified period. Network policy 550 can be updated based on at least one of, for example, the network status between components, administrator commands received from external sources, or any combination thereof. Network policy 500 may include information related to, for example, the type of data frame, priority according to the type, destination, source, transmission method, transmission path, or any combination thereof.

[0136] For example, the main device 510 can generate multiple network policies. The main device 510 can generate a first policy and a second policy, and selectively send the generated policies based on the characteristics of each component of the data management device (e.g., control objectives, performance, storage capacity, etc.). The main device 510 can, for example, send only one policy to a component, or send multiple policies together.

[0137] For example, the first main control unit 521, the second main control unit 522, the first terminal device 541, the first auxiliary control unit 531, and the second auxiliary control unit 532 can receive network policy 550 from the main device 510 based on a specified period. Other components not described above can manage data without being based on network policy 550, but this is merely exemplary, and other components can also receive network policy 550 and manage data.

[0138] For example, a component that has received network policy 550 can generate a data frame based on the information included in network policy 550, and identify the priority, destination, transmission method, and transmission path (e.g., routing) of the generated data frame.

[0139] For example, the main device 510 may be one of a plurality of main control units, a plurality of auxiliary control units, and a plurality of terminal devices included in a data management device.

[0140] For example, the main device 510 may be a separate device that is physically and logically separated from multiple main control units, multiple auxiliary control units and multiple terminal devices included in the data management device.

[0141] For example, the first auxiliary control unit 531 and / or the second auxiliary control unit 532 can adjust the weight of each of a plurality of executable functions based on network policies (and / or control commands) received from the master device 510. For example, the first auxiliary control unit 531 and / or the second auxiliary control unit 532 can adjust the operational weight of each of a plurality of functions, including at least one of terminal device control, network communication, protection, monitoring, or any combination thereof, based on network policies (and / or control commands).

[0142] Figure 6 This is a conceptual diagram illustrating the configuration of a data management apparatus according to an embodiment disclosed herein.

[0143] According to an implementation, a data management device (e.g., Figure 3 The data management device 300 may include multiple main control units 621, 622, 623 and 624; multiple auxiliary control units 631, 632 and 633; ​​and multiple terminal devices 641, 642 and 643.

[0144] For example, the first auxiliary control unit 631 (or the first area controller), the second auxiliary control unit 632 (or the second area controller), and the third auxiliary control unit 633 (or the third area controller) can be implemented as a single auxiliary control unit (e.g., Figure 3 (The auxiliary control unit 330 in the text). In the following description, the following assumptions are made. Figure 6 The three auxiliary control units shown are implemented as a single chip.

[0145] For example, the auxiliary control unit (or the first auxiliary control unit 631) can receive data 1 from the first main control unit 621.

[0146] For example, the auxiliary control unit (or the first auxiliary control unit 631) can receive data 2 from the second main control unit 622.

[0147] For example, the auxiliary control unit (or the first auxiliary control unit 631) can receive data 3 from the first terminal device 641.

[0148] For example, the auxiliary control unit (or the third auxiliary control unit 633) can receive data 4 from the third terminal device 643.

[0149] For example, the auxiliary control unit (or the third auxiliary control unit 633) can receive data 5 from the fourth main control unit 644.

[0150] For example, the auxiliary control unit may receive data 1 to data 5 based on the first communication protocol 591. For example, the first communication protocol 591 may be used based on a first communication speed (e.g., 1 Gbps).

[0151] According to the implementation method, the auxiliary control unit can group the received data 1 to data 5 based on a specified reference and generate at least one frame.

[0152] For example, the auxiliary control unit can aggregate data received during the first time period and group the data based on at least one of data type, destination, domain, or any combination thereof.

[0153] For example, the auxiliary control unit can group data 1 and data 3 into a frame, and group data 2 into a frame.

[0154] For example, the auxiliary control unit can identify a target device corresponding to at least one packet frame based on a specified reference. Figure 6 The auxiliary control unit can identify that the target device corresponding to data 1, data 3, and data 4 is the third main control unit 623, and the target device corresponding to data 2 and data 5 is the second terminal device 642. The auxiliary control unit can generate a target jumbo frame including data 1, data 3, and data 4, and send it to the third main control unit 623 using the second auxiliary control unit 632.

[0155] For example, the auxiliary control unit can group data based on at least one of data type, destination, domain, or any combination thereof.

[0156] According to the implementation method, the auxiliary control unit can identify the area controller to which data is to be sent based on the characteristics of the received data, and send the data to the identified area controller.

[0157] For example, the auxiliary control unit can identify the second auxiliary control unit 632 corresponding to data 1, data 2, and data 3 based on the characteristics of each of the data 1, data 2, and data 3 received through the first auxiliary control unit 631. Then, the auxiliary control unit can transmit the data 1, data 2, and data 3 sent to the first auxiliary control unit 631 to the second auxiliary control unit 632.

[0158] For example, the auxiliary control unit can identify the second auxiliary control unit 632 corresponding to data 4 and data 5 based on the characteristics of each of the data 4 and data 5 received through the third auxiliary control unit 633. Then, the auxiliary control unit can send the data 4 and data 5 sent to the third auxiliary control unit 633 to the second auxiliary control unit 632.

[0159] For example, the first auxiliary control unit 631 and the third auxiliary control unit 633 can send data to the second auxiliary control unit 632 based on the second communication protocol 592. For example, the second communication protocol 592 can be used based on a second communication speed that is higher than the first communication speed (e.g., 10 Gbps).

[0160] For example, the auxiliary control unit (or the second auxiliary control unit 632) can generate a first target megaframe to be sent to the third main control unit 623, which is the target device, by aggregating data 4 into a frame formed by grouping data 1 and data 3.

[0161] For example, the auxiliary control unit (or the second auxiliary control unit 632) can generate a second target megaframe to be sent to the second terminal device 642, which is the target device, by aggregating data 2 and data 5.

[0162] For example, the first target megaframe may include data aggregated during a first time period corresponding to the control cycle of the third main control unit 623.

[0163] For example, the second target jumbo frame may include data aggregated during a second time period corresponding to the control cycle of the second terminal device 642.

[0164] For example, the auxiliary control unit (or the second auxiliary control unit 632) can send a first target jumbo frame generated by receiving, aggregating, and grouping data during a first time period to the third main control unit 623. In other words, the auxiliary control unit can aggregate the data corresponding to the third main control unit 623 during the first time period, and send the first target jumbo frame corresponding to the aggregation result to the third main control unit 623 after the first time period has elapsed.

[0165] For example, the auxiliary control unit (or the second auxiliary control unit 632) can send a second target jumbo frame generated by receiving, aggregating, and grouping data during a second time period to the second terminal device 642. In other words, the auxiliary control unit can aggregate data corresponding to the second terminal device 642 during the second time period, and send the second target jumbo frame corresponding to the aggregation result to the second terminal device 642 after the second time period has elapsed.

[0166] Figure 7 This is a conceptual diagram illustrating a method for transmitting data by a data management device according to an embodiment disclosed herein.

[0167] According to an implementation, a data management device (e.g., Figure 3 The data management device 300 in the middle may include a battery, a terminal device (e.g., Figure 3 Terminal device 340), auxiliary control unit (e.g., Figure 3 The auxiliary control unit 330 and the main control unit (e.g., Figure 3 The main control unit 320 in the system. The main control unit may include multiple HPCs, and the auxiliary control units may include multiple area controllers.

[0168] According to the implementation, the battery and terminal device can also be implemented as a single integrated module (e.g., BMS).

[0169] For example, the battery may periodically and / or transmit battery data upon request from the auxiliary control unit and the main control unit. Battery data may include, for example, information relating to the battery's state of charge, charge / discharge data, voltage, pressure, temperature, operating history, or any combination thereof.

[0170] For example, the battery can send first battery data 751 and second battery data 752 to the auxiliary control unit (e.g., Figure 3 (Auxiliary control unit 330 in the middle).

[0171] For example, the terminal device can send multiple first terminal data 741 and multiple second terminal data 742 to the auxiliary control unit.

[0172] For example, the auxiliary control unit can group the received terminal data and generate at least one frame based on the characteristics and / or specified criteria (e.g., data type, destination, source, domain, etc.). At least one frame can be, for example, a jumbo frame with a data volume exceeding a specified value. The auxiliary control unit can also, for example, [details omitted]. Figure 7 Other terminal devices (e.g., terminal devices for controlling sensors and / or multimedia devices) not shown in the diagram receive data.

[0173] For example, the auxiliary control unit can generate a first frame 731 and a second frame 732. The destination of the first frame 731 can be, for example, in addition to... Figure 7 The main control unit other than the main control unit shown.

[0174] For example, the auxiliary control unit may send the second frame 732 to the main control unit. The auxiliary control unit may, for example, aggregate data received from the terminal device, battery, and / or main control unit during a first time period, and send the second frame 732, generated by grouping the aggregated data based on a specified reference, to the main control unit. For example, the auxiliary control unit may send the generated second frame 732 to the main control unit when a first time period (e.g., the control cycle of the main control unit) has elapsed since the generation of the second frame 732 (or when the first time period reaches the control cycle of the main control unit).

[0175] For example, when the control cycle of another main control unit corresponding to the first frame 731 has elapsed since the time point from the start of the generation of the first frame 731, the auxiliary control unit can send the first frame 731 generated during the control cycle of the other main control unit to the other main control unit.

[0176] For example, the main control unit can process the second frame 732 by dividing it into service units. The main control unit can process data items included in the second frame 732, for example, by dividing data items into a first service related to the battery pack, a second service related to the sensor, and a third service related to multimedia.

[0177] Figure 8 This is a flowchart of a data management method according to the embodiments disclosed herein.

[0178] According to this embodiment, the data management device (e.g., Figure 3 The data management device 300 in the middle can perform Figure 8 The operations disclosed herein. For example, at least some of the components included in the data management device (e.g., Figure 3 The main device 310, main control unit 320, auxiliary control unit 330 and / or terminal device 340 can be configured to perform Figure 8 The operation.

[0179] In the following embodiments, operations S810 to S840 may be executed sequentially, but not necessarily sequentially. For example, the order of operations can be changed, and at least two operations can be executed in parallel. Furthermore, references may be briefly described or omitted. Figure 8 Any content that corresponds to or repeats the content described above.

[0180] Reference Figure 8 The data management method may include: operation S810, in which the area controller receives data packets (or messages) from an external device and separates the received data packets for each target device; operation S820, in which it is determined whether the control cycle of the first target device has elapsed; operation S830, in which a jumbo frame including the separated data packets is sent to the first target device; and operation S840, in which the first target device divides the jumbo frame into service units.

[0181] In operation of S810, the area controller can receive data packets from at least some of other area controllers, HPCs, and terminal devices, and group the data packets individually based on their destination. The area controller can identify the destination of each jumbo frame generated as a result of grouping.

[0182] In operation S820, the area controller can identify the control cycle of a first target device (e.g., HPC) among multiple destinations. If it is identified that the time from the start of packet formation has elapsed to the first time of the control cycle of the first target device, the area controller can execute operation S830.

[0183] Figure 9 This is a flowchart of a data management method according to the embodiments disclosed herein.

[0184] According to this embodiment, the data management device (e.g., Figure 3 The data management device 300 in the middle can perform Figure 9 The operations disclosed herein. For example, at least some of the components included in the data management device (e.g., Figure 3 The main device 310, main control unit 320, auxiliary control unit 330 and / or terminal device 340 can be configured to perform Figure 9 The operation.

[0185] In the following embodiments, operations S910 to S930 may be executed sequentially, but not necessarily sequentially. For example, the order of the operations can be changed, and at least two operations can be executed in parallel. Furthermore, references may be briefly described or omitted. Figure 9 Any content that corresponds to or repeats the content described above.

[0186] Reference Figure 9 The data management method may include: operation S910, in which the master device sends a control signal to the auxiliary control unit, including at least one of a network policy regarding the communication protocol, a control command, or any combination thereof; operation S920, in which the auxiliary control unit generates a data frame based on the control signal and determines the transmission method and transmission path; and operation S930, in which the auxiliary control unit sends the data frame to the master control unit corresponding to the data frame.

[0187] Figure 10 This is a flowchart of a data management method according to the embodiments disclosed herein.

[0188] According to this embodiment, the data management device (e.g., Figure 3 The data management device 300 in the middle can perform Figure 9 The operations disclosed herein. For example, at least some of the components included in the data management device (e.g., Figure 3 The main device 310, main control unit 320, auxiliary control unit 330 and / or terminal device 340 can be configured to perform Figure 9 The operation.

[0189] In the following implementation, operations S1010 to S1030 may be executed sequentially, but not necessarily sequentially. For example, the order of the operations can be changed, and at least two operations can be executed in parallel. Furthermore, details regarding... Figure 10 Any content that corresponds to or repeats the content described above.

[0190] Reference Figure 10The data management method may include: operation S1010, in which the auxiliary control unit receives data from the main control unit and / or the terminal device; operation S1020, in which the auxiliary control unit groups the data based on a specified reference and generates at least one frame; and operation S1030, in which the auxiliary control unit sends at least one frame to the target device.

[0191] Figure 11 This is a block diagram illustrating the hardware configuration of a computing system for performing a method of an operational data management device according to an embodiment disclosed herein.

[0192] Reference Figure 11 The computing system 3000 according to embodiments of the present disclosure may include a microcontroller unit (MCU) 1010, a memory 1020, an input / output interface (I / F) 1030, and a communication I / F 1040.

[0193] The MCU 1010 can be a processor that executes various programs stored in the memory 1020, processes various types of information including battery data, and executes the aforementioned... Figure 3 The data management device shown includes the functions of a processor (or controller).

[0194] The memory 1020 can store various programs used to perform the functions of the data management device. Furthermore, the memory 1020 can store various types of information, including battery data (voltage data, capacity data, etc.), differential capacity data, etc., and can include a constructed database.

[0195] Multiple memories 1020 can be provided as needed. Memory 1020 can be volatile or non-volatile memory. As volatile memory, memory 1020 can be random access memory (RAM), dynamic RAM (DRAM), static RAM (SRAM), etc. For memory 1020 as non-volatile memory, read-only memory (ROM), programmable ROM (PROM), electrically rewritable ROM (EAROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, etc., can be used. The examples of memory 1020 listed above are merely exemplary and are not limited to these examples.

[0196] The Input / Output I / F 1030 provides an interface for connecting input devices (not shown) such as a keyboard, mouse, touch panel, etc., and output devices such as a display (not shown) to the MCU 1010 to enable data transmission and reception.

[0197] The Communication I / F 1040 is a component capable of sending and receiving various types of data from a server, and can be any device that supports wired or wireless communication. For example, a data management device can use the Communication I / F 1040 to send various types of information, including battery data, to a separately provided external server, and to receive various types of information, including battery data, from a separately provided external server.

[0198] By being recorded in memory 1020 and processed by MCU 1010 in this manner, a computer program according to the embodiments disclosed herein can be implemented to, for example, execute... Figure 1 Each of the modules shown represents a function.

[0199] Although all components constituting the embodiments disclosed herein have been described as combined or operated in combination, the embodiments disclosed herein are not necessarily limited to these embodiments. That is, within the scope of the purpose of the embodiments disclosed herein, all components may be selectively combined and operated once or more.

[0200] Unless otherwise stated, terms such as “comprising,” “including,” or “having” above mean that corresponding components may be present, and should therefore be interpreted as potentially including other components rather than excluding them. Unless otherwise defined, all terms including technical or scientific terms have the same meaning as commonly understood by one of ordinary skill in the art to which the embodiments disclosed herein pertain. Commonly used terms, such as those defined in dictionaries, should be interpreted as having the meaning consistent with their meaning in the context of the relevant art, and should not be interpreted in an idealized or overly formal sense unless expressly defined herein.

[0201] The above description is merely an example of the technical concept disclosed herein, and those skilled in the art to which the embodiments disclosed herein pertain can make various modifications and variations without departing from the basic characteristics of the embodiments disclosed herein. Therefore, the embodiments disclosed herein are not intended to limit the technical ideas of the embodiments disclosed herein, but rather to interpret them, and the scope of the technical concept disclosed herein is not limited by these embodiments. The scope of protection disclosed herein should be interpreted by the appended claims, and all technical concepts within the same scope should be interpreted as included within the scope of the claims herein.

Claims

1. A data management device, the data management device comprising: Main control unit; An auxiliary control unit is electrically connected to the main control unit; as well as Terminal device, The auxiliary control unit is configured as follows: Data is received from at least one of the main control unit, the terminal device, or any combination thereof; The data is grouped based on a specified benchmark and at least one frame is generated; and The at least one frame is sent to the target device identified based on the specified reference.

2. The data management device according to claim 1, wherein, The auxiliary control unit is configured to aggregate the data received during a first time period and to group the data based on at least one of the data type, destination, domain, or any combination thereof.

3. The data management device according to claim 2, wherein, The auxiliary control unit is configured to: The data is grouped and a target megaframe to be sent to the target device is generated. Identify the control cycle of the target device; and When the first time reaches the control period, the target megaframe is sent to the target device.

4. The data management device according to claim 1, wherein, The auxiliary control unit includes multiple area controllers, and The auxiliary control unit is configured to send the data to a second area controller corresponding to the characteristics of the data when the first area controller among the plurality of area controllers receives the data.

5. The data management device according to claim 4, wherein, The first area controller is configured to: The data is received from at least one of the main control unit, the terminal device, or any combination thereof based on a first communication speed; and The data is sent to the second area controller at a second communication speed that is higher than the first communication speed.

6. The data management device according to claim 1, wherein, The target device is configured to process the frame by dividing the at least one frame into service units.

7. The data management device according to claim 1, wherein, The target device corresponds to one of the multiple high-performance computers (HPCs) included in the main control unit.

8. A vehicle comprising a data management device according to any one of claims 1 to 7.

9. A data management method, the data management method comprising the following steps: The auxiliary control unit receives data from at least one of the main control unit, the terminal device, or any combination thereof. The auxiliary control unit groups the data based on a specified reference and generates at least one frame; as well as The auxiliary control unit sends the at least one frame to the target device identified based on the specified reference.

10. The data management method according to claim 9, further comprising the following steps: The auxiliary control unit aggregates the data received during the first time period and groups the data based on at least one of the data type, destination, domain, or any combination thereof.

11. The data management method according to claim 10, further comprising the following steps: The auxiliary control unit groups the data and generates a target megaframe to be sent to the target device; The auxiliary control unit identifies the control cycle of the target device; as well as When the first time reaches the control cycle, the auxiliary control unit sends the target megaframe to the target device.

12. The data management method according to claim 9, further comprising the following steps: When the first area controller, one of the multiple area controllers included in the auxiliary control unit, receives the data, the auxiliary control unit sends the data to the second area controller corresponding to the characteristics of the data.

13. The data management method according to claim 12, further comprising the following steps: The data is received by the first area controller from at least one of the main control unit, the terminal device, or any combination thereof, based on a first communication speed; as well as The first area controller sends the data to the second area controller at a second communication speed that is higher than the first communication speed.

14. The data management method according to claim 9, further comprising the following steps: The target device processes the frame by dividing the at least one frame into service units.

15. An auxiliary control unit for controlling a data management device, the auxiliary control unit comprising: A memory configured to store at least one instruction; as well as A processor, operatively connected to the memory, Wherein, when the at least one instruction is executed by the processor, the auxiliary control unit: Receive data from at least one of the main control unit, the terminal device, or any combination thereof; The data is grouped based on a specified benchmark, and at least one frame is generated; and The at least one frame is sent to the target device identified based on the specified reference.

16. The auxiliary control unit according to claim 15, wherein, When executed by the processor, the at least one instruction causes the auxiliary control unit to aggregate the data received during the first time period and to group the data based on at least one of the data type, destination, domain, or any combination thereof.

17. The auxiliary control unit according to claim 15, wherein, When executed by the processor, the at least one instruction causes the auxiliary control unit to aggregate the data received during the first time period and to group the data based on at least one of the data type, destination, domain, or any combination thereof.

18. The auxiliary control unit according to claim 17, wherein, When the at least one instruction is executed by the processor, it causes the auxiliary control unit to: The data is grouped and a target megaframe to be sent to the target device is generated. Identify the control cycle of the target device; and When the first time reaches the control period, the target megaframe is sent to the target device.

19. The auxiliary control unit according to claim 15, further comprising: Multiple area controllers, When the processor executes the at least one instruction, the auxiliary control unit sends the data to a second area controller corresponding to the characteristics of the data when the first area controller among the plurality of area controllers receives the data.

20. The auxiliary control unit according to claim 19, wherein, When the at least one instruction is executed by the processor, it causes the auxiliary control unit to: The data is received by the first area controller from at least one of the main control unit, the terminal device, or any combination thereof, based on a first communication speed. as well as The data is sent from the first area controller to the second area controller based on a second communication speed that is higher than the first communication speed.