Power management device, vehicle comprising same and power management method

Abstract

According to embodiments disclosed in the present document, an electric power management apparatus can include a first control unit electrically connected to a battery pack, at least one second control unit electrically connected to the first control unit, and a terminal apparatus electrically connected to the first control unit and the at least one second control unit and configured to control the battery pack. For example, the terminal apparatus can receive electric power from the first control unit and receive a wake-up packet from the at least one second control unit.

Description

Technical Field

[0001] Cross-references to related applications

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

[0003] The embodiments disclosed in this document relate to power management devices and power management methods. Background Technology

[0004] With the increasing prevalence of electrically powered vehicles, research and development of new vehicle architectures are actively underway. For example, electric vehicles can be powered by rechargeable batteries. Here, rechargeable batteries are batteries that can be charged and discharged, and can be interpreted as including both conventional Ni / Cd batteries, Ni / MH batteries, and more recently, lithium-ion batteries. Among rechargeable batteries, lithium-ion batteries have the advantage of a much higher energy density than conventional Ni / Cd and Ni / MH batteries. Furthermore, lithium-ion batteries can be manufactured to be smaller and lighter, thus they are used as power sources for mobile devices. Recently, the application of lithium-ion batteries has expanded to include power sources for electric vehicles, and lithium-ion batteries are attracting attention as a next-generation energy storage medium.

[0005] These battery cells, modules, packs, or racks can be used in a wide variety of devices. For example, batteries can be used not only in mobile devices such as mobile phones, laptops, smartphones, and tablets, but also in electrically powered vehicles (EVs, HEVs, and PHEVs), energy storage devices (ESS), and more.

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

[0007] Meanwhile, 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, SDV refers to a vehicle where hardware is controlled and managed by software. Software based on SDVs can define not only the vehicle's driving performance but also its convenience features, safety features, emotional qualities, and brand identity. The SDV architecture allows for reduced vehicle development costs through the commonality of ECUs and the internalization of software. Furthermore, autonomous driving technology can be improved through high-performance computers and networks based on electronic architecture. Summary of the Invention

[0008] Technical issues

[0009] Effective power management within an SDV (Sustainable Storage and Distribution) architecture can be critical. Developing efficient and adaptive processes is essential for supplying power from the battery pack to other components, such as area controllers, terminal devices, etc.

[0010] From the perspective of power control and power efficiency, the embodiments disclosed in this document provide a power management device and a power management method, which are implemented by realizing signal transmission and reception between components under an SDV structure. This also includes a vehicle incorporating the power management device.

[0011] The technical problems of the embodiments disclosed in this document are not limited to the above-described technical problems, and other technical problems not mentioned can be clearly understood by those skilled in the art from the following description.

[0012] Technical solution

[0013] According to the embodiments disclosed in this document, a power management device includes: a first control unit electrically connected to a battery pack; at least one second control unit electrically connected to the first control unit; and a terminal device electrically connected to the first control unit and the at least one second control unit and configured to control the battery pack.

[0014] According to an embodiment, the terminal device may be configured to receive power from the first control unit and receive a wake-up packet from the at least one second control unit.

[0015] According to an embodiment, the first control unit may be configured to provide power received from the battery pack to the at least one second control unit and the terminal device via Power over Data Line (PoDL) when it receives an ignition start input for its own vehicle.

[0016] According to an embodiment, the first control unit may be configured to determine the magnitude of the power to be supplied to the target device based on at least one of the type, operating state, operating type, or any combination thereof of the target device to be powered.

[0017] According to an embodiment, the power supplied to the at least one second control unit may be greater than the power supplied to the terminal device.

[0018] According to an implementation, the first control unit can be configured to monitor the status information of the battery pack, and if it is determined based on the status information that the battery pack corresponds to a specified state, identify the real-time status of its own vehicle, use the real-time status to set a priority for each terminal device in the terminal devices, and provide power to the terminal devices sequentially according to the set priority.

[0019] According to an implementation, the first control unit can be configured to determine that the battery pack corresponds to the specified state when the state of charge (SoC) of the battery pack is less than or equal to a specified value.

[0020] According to an implementation, the first control unit can be configured to: if it is identified based on the real-time status that the driving speed of its own vehicle is less than or equal to a specified value and the user is in its own vehicle, then set a high priority for the infotainment device; and prioritize providing power to the infotainment device in the terminal device.

[0021] According to an implementation, the at least one second control unit is configured to: identify a designated terminal device corresponding to the designated event in the terminal devices if a designated event occurs; generate a wake-up packet in which wake-up conditions are set using at least one of its own vehicle status, whether the data is erroneous, or any combination thereof; and send the wake-up packet to the designated terminal device based on LAN Wake-up (WoL).

[0022] According to an implementation, the designated terminal device can be configured to be woken up based on the fulfillment of the wake-up condition.

[0023] According to the embodiments disclosed in this document, a vehicle including any of the above-described power management devices is provided.

[0024] According to the embodiments disclosed in this document, a power management method includes the following steps: when receiving an ignition start input for its own vehicle, a first control unit uses power received from a battery pack via Power over Data Line (PoDL) to provide a first power and a second power to at least one second control unit and a terminal device, respectively; if a specified event occurs, the at least one second control unit identifies a specified terminal device corresponding to the specified event in the terminal device, generates a wake-up packet, and sends the wake-up packet to the specified terminal device; and the specified terminal device is turned on by the power provided from the first control unit and is woken up based on the receipt of the wake-up packet.

[0025] According to an implementation, the power management method may further include the following steps: when an ignition start input for its own vehicle is received, the first control unit uses power received from the battery pack via Power over Data Line (PoDL) to provide first power and second power to the at least one second control unit and the terminal device, respectively.

[0026] According to an implementation, the power management method may further include the following step: the first control unit determines the magnitude of the power to be supplied to the target device based on at least one of the type, operating state, operating type, or any combination thereof of the target device to be powered.

[0027] According to an implementation, the power management method may further include the following steps: the first control unit monitors the status information of the battery pack, and if it is determined based on the status information that the battery pack corresponds to a specified status, identifies the real-time status of its own vehicle; the first control unit uses the real-time status to set a priority for each terminal device in the terminal devices; and the first control unit provides power to the terminal devices sequentially according to the set priority.

[0028] According to an implementation, the power management method may further include the following steps: if, based on the real-time status, it is identified that the driving speed of its own vehicle is less than or equal to a specified value and the user is inside its own vehicle, then the first control unit sets a high priority for the infotainment device; and the first control unit preferentially provides power to the infotainment device in the terminal device.

[0029] According to the embodiments disclosed in this document, a vehicle including any of the above-described power management devices may be disclosed.

[0030] Beneficial effects

[0031] The power management device and method according to the embodiments disclosed in this document can realize the data transmission path, power transmission path and transmission object separately by distinguishing the data transmission path, power transmission path and transmission object under the SDV structure, thereby providing a more efficient and controllable intuitive power management method for vehicles.

[0032] In addition, various effects that can be identified directly or indirectly through this article can be provided. Attached Figure Description

[0033] Figure 1 This is a conceptual diagram illustrating the structure of a vehicle including an electric management device according to an embodiment disclosed in this document.

[0034] Figure 2This is a conceptual diagram illustrating the structure of a vehicle including an electric management device according to an embodiment disclosed in this document.

[0035] Figure 3 This is a block diagram illustrating the configuration of a power management device according to an embodiment disclosed in this document.

[0036] Figure 4 This is a block diagram illustrating the configuration of a power management device according to an embodiment disclosed in this document.

[0037] Figure 5 This is a block diagram illustrating the configuration of a power management device according to an embodiment disclosed in this document.

[0038] Figure 6 This is a flowchart of a power management method according to the implementation method disclosed in this document.

[0039] Figure 7 This is a flowchart of a power management method according to the implementation method disclosed in this document.

[0040] Figure 8 This is a block diagram illustrating the hardware configuration of a computing system for performing an operation method of a power management device according to an embodiment disclosed in this document. Detailed Implementation

[0041] In the following description, various embodiments of the present disclosure will be illustrated with reference to the accompanying drawings. However, this is not intended to limit the present disclosure to specific embodiments, but should be understood to include various modifications, equivalents, and / or alternatives to the embodiments of the present disclosure.

[0042] In this document, the singular form of the noun corresponding to an item may include one or more of the items, unless the relevant context explicitly indicates otherwise. In this document, each of the phrases “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 of the items listed with the phrase, or all possible combinations thereof. Terms such as “first,” “second,” or “first” or “second” may be used only to distinguish one component from another and do not limit the components in any other way (e.g., importance or order). When a component (e.g., the first component) is referred to as “connected” or “linked” to another component (e.g., the second component), with or without the terms “functionally” or “communically,” this means that the component may be directly (e.g., wired) or wirelessly connected to the other component via a third component.

[0043] Each component (e.g., module or program) described in this document may contain one or more entities. Depending on the implementation, one or more components or operations may be omitted, or one or more additional components or operations may be added. Alternatively or additionally, multiple components (e.g., module or program) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each of the multiple components in the same or similar manner as the functions performed by the corresponding components among the multiple components prior to integration. Depending on the implementation, 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, omitted, or performed by adding one or more additional operations.

[0044] For example, the terms "module" or "unit" as used in this document can include units implemented in hardware, software, or firmware, and can be used interchangeably with terms such as logic, logic block, section, or circuit. A module can be an integrally formed component or the smallest unit or part of a component that performs one or more functions. For example, depending on the implementation, a module can be implemented as an application-specific integrated circuit (ASIC).

[0045] The various implementations of this document can be implemented as software (e.g., a program or application) including 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 enables 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, "non-transitory" simply means that the storage medium is a tangible device and does not contain signals (e.g., electromagnetic waves), and this term does not distinguish between cases where data is stored semi-permanently and cases where data is temporarily stored in the storage medium.

[0046] Figure 1 This is a conceptual diagram illustrating the structure of a vehicle including an electric management device according to an embodiment disclosed in this document.

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

[0048] 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 and receive path 160, an additional element 170, or any combination thereof. A power management device for power management of vehicle 110 may include at least some of the components included in vehicle 110.

[0049] For example, components based on the SDV architecture may include a hierarchical structure in the order of HPC 150, area controller, and terminal device.

[0050] As an 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.

[0051] As an 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 device 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, when one of the second terminal devices 132 is a BMS, the additional element 170 may be defined as a battery pack.

[0052] As an 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.

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

[0054] The power management device according to the embodiments of this document can control and manage the communication process of power and / or data sent and received between the aforementioned components.

[0055] Figure 2 This is a conceptual diagram illustrating the structure of a vehicle including an electric management device according to an embodiment disclosed in this document.

[0056] exist Figure 2 In the middle, used with Figure 1The description of components with the same name defined in the above can be used. Figure 1 The description is replaced with [the description].

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

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

[0059] Figure 3 This is a block diagram illustrating the configuration of a power management device according to an embodiment disclosed in this document.

[0060] Reference Figure 3 The power management device 300 may include a first control unit 310, a second control unit 320, and a terminal device 330.

[0061] According to an embodiment, the power management device 300 can perform power and / or data management among components used to control its own vehicle. For example, its own vehicle can be operated by components based on an SDV architecture. For example, an SDV can include a hierarchical structure in the order of a high-performance computer (HPC), zones, terminal devices, and sensors / actuators. In this case, the SDV-based vehicle can be divided into multiple zones, and each zone can include a control unit (e.g., a zone controller) for controlling the components in the lower layers included in that zone. The control unit of the zone is 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., according to...), Figure 2 (In the implementation of the SDV architecture), HPC and terminal devices can be operatively connected to each other, and this area can be omitted.

[0062] The power management device 300 can send and receive at least one of power, data (e.g., wake-up packets), control signals, or any combination thereof regarding components included in the electronic device. In embodiments, the electronic device can be a mobile device (e.g., a mobile phone, laptop, smartphone, tablet), an electric vehicle (e.g., an electric vehicle (EV), a hybrid electric vehicle (HEV), a plug-in hybrid electric vehicle (PHEV), and 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 driven mobile object. In other words, for example, the power management device 300 can be included in a vehicle and configured to manage the operation of the vehicle.

[0063] The operation of the power management device 300 described below can be performed by the battery management system (BMS) in the vehicle, the battery BMS installed in the battery pack, and can be performed in various devices such as servers, cloud, chargers, or chargers / dischargers.

[0064] According to an embodiment, the first control unit 310 and the second control unit 320 may include one or more processors corresponding to a first region and a second region of their respective vehicles. The second control unit 320 may include, for example, one or more control units. In other words, at least one second control unit 320 may include at least one control unit corresponding to the nth region. The first control unit 310 and at least one second control unit 320 may be electrically connected to each other. For example, the first control unit 310 and at least one second control unit 320 may be electrically connected to a terminal device 330, which is provided for controlling a battery pack included in its own vehicle. The terminal device 330 and the battery pack may also be implemented as a single module (e.g., a battery management system (BMS)).

[0065] For example, each processor included in the first control unit 310 and the second control unit 320 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.

[0066] The functions and operations of the power management device 300 described below can be performed by a single processor (or a first control unit 310 and / or a second control unit 320), or the functions can be at least partially separated and performed by multiple processors.

[0067] According to an implementation, the area corresponding to the first control unit 310 can be defined as a power area. The power area may include, for example, a controller (e.g., the first control unit 310) for power management of components within the vehicle. The first control unit 310 corresponding to the power area can, for example, send power and / or data to and receive power and / or data from the terminal device 330 and at least one second control unit 320 via Power over Data Line (PoDL) (or via PoDL).

[0068] According to an implementation, the area corresponding to at least one second control unit 320 can be defined as a general area. The general area may include, for example, a controller (e.g., at least one second control unit 320) for controlling and managing components of its own vehicle (e.g., sensors, actuators, cameras, drive and braking devices, etc.) included in the area. The at least one second control unit 320 corresponding to the general area can send and receive power and / or data to and from the terminal device 330 and the at least one second control unit 320 based on LAN Wake-up (WoL) (or via WoL).

[0069] According to an implementation, the terminal device 330 may receive power from the first control unit 310 based on PoDL and may receive data packets (e.g., wake-up packets) from at least one second control unit 320 based on WoL. The terminal device 330 may include at least one of, for example, an interface electrically connected to the first control unit 310 and the second control unit 320, a determination unit, an MCU, a memory, or any combination thereof.

[0070] According to the implementation, the first control unit 310 can provide power to peripheral devices based on PoDL. For example, when it receives an ignition start input from its own vehicle (or when it detects that its own vehicle is turned on), the first control unit 310 can provide power to peripheral devices based on PoDL.

[0071] For example, when the first control unit 310 receives power from the battery pack connected to the terminal device 330, the first control unit 310 can provide at least a portion of the received power to the peripheral device based on PoDL.

[0072] For example, the first control unit 310 may determine the magnitude (or level) of power to be supplied to the target device based on at least one of the type, operating state, operating type, or any combination thereof of the target device to be powered.

[0073] As an example, if the target device is identified as being connected to a sensor and performing a role in controlling the sensor (e.g., if the target device is a terminal device for the sensor), the first control unit 310 may provide the target device with a relatively low amplitude (or low level) of power.

[0074] As an example, if the target device is identified as controlling at least one terminal device at a lower level or performing a role in collecting and processing data (e.g., when the target device is at least one second control unit, another area controller, or a high-performance computer), the first control unit 310 may provide the target device with a relatively large value (or a high level) of power.

[0075] As an example, the first control unit 310 can use power received from the battery pack to provide a first power and a second power to at least one second control unit 320 and a terminal device 330, respectively. The first power provided to the at least one second control unit 320 may, for example, be greater than the second power provided to the terminal device 330.

[0076] For example, the first control unit 310 can set the priority of power supply based on the battery pack's status information and supply power sequentially.

[0077] As an example, the first control unit 310 can monitor the state information of the battery pack and determine whether the battery pack corresponds to a specified state based on the state information. For example, when the state of charge (SoC) of the battery pack is less than or equal to a specified value, the first control unit 310 can determine that the battery pack corresponds to the specified state.

[0078] For example, if it is determined that the battery pack corresponds to a specific state, the first control unit 310 can identify the real-time state of its own vehicle. For example, the first control unit 310 can use the real-time state to set a priority for power supply to each terminal device 330. For example, the first control unit 310 can provide power to the terminal devices 330 sequentially according to the set priority.

[0079] As an example, the first control unit 310 can identify, based on real-time status, that its own vehicle's driving speed is less than or equal to a specified value and that the user is inside its own vehicle. In this case, the first control unit 310 can set a high priority for the infotainment devices (e.g., displays, voice output devices, etc.) in the terminal device 330 and prioritize providing power to the infotainment devices.

[0080] For example, if a specified event occurs, the second control unit 320 can identify the specified terminal device corresponding to the specified event in the terminal device 330.

[0081] As an example, when it is recognized that the vehicle has started driving, the second control unit 320 can identify the driving control device (e.g., driving unit, braking unit, steering unit, etc.) in the terminal device 330 as the designated terminal device.

[0082] As an example, if it is detected that its own vehicle has started charging, the second control unit 320 can identify the charging control device (e.g., BMS, battery pack, etc.) in the terminal device 330 as the designated terminal device.

[0083] For example, the second control unit 320 may generate a wake-up packet in which wake-up conditions are set by using at least one of the state of its own vehicle, the presence of errors in the data, or any combination thereof, and then send the generated wake-up packet to a designated terminal device.

[0084] For example, the second control unit 320 and the terminal device 330 may include a memory, a logic module, and / or an MCU. The terminal device 330 may receive, for example, a wake-up packet from the second control unit 310, etc.

[0085] According to the implementation, the terminal device 330 can use at least one interface to receive power from the first control unit 310, or to send data to the first control unit 310 and the second control unit 320 and to receive data from the first control unit 310 and the second control unit 320.

[0086] For example, terminal device 330 can receive power from first control unit 310 using a first interface. For example, terminal device 330 can receive data from at least one second control unit 320 using a second interface different from the first interface.

[0087] For example, data received from the second control unit 320 may include wake-up packets that instruct the terminal device 330 to perform a wake-up operation.

[0088] According to the implementation, the terminal device 330 can receive a wake-up packet containing wake-up conditions from the second control unit 320. For example, at least one second control unit can set wake-up conditions in the wake-up packet related to at least one of its own vehicle status, the data accuracy of the terminal device, or any combination thereof, and then send the wake-up packet to the terminal device 330.

[0089] For example, terminal device 330 can use a determining unit to determine whether the wake-up conditions set for the wake-up group are met. The determining unit may include, for example, at least one logic module. If, for example, it is determined that the wake-up conditions are met, terminal device 330 can send a wake-up signal to the MCU through the determining unit. For example, the MCU can be woken up based on receiving the wake-up signal. When the MCU is woken up, terminal device 330 can also be woken up.

[0090] As an example, if the terminal device 330 recognizes that the vehicle's ignition is on, the terminal device 330 can determine that the wake-up conditions are met and send a wake-up signal to the MCU through the determination unit.

[0091] As an example, if the terminal device 330 detects that the vehicle's ignition is off, the terminal device 330 can send a wake-up signal to the MCU at a specified interval, causing the terminal device 330 to be woken up at the specified interval. Thus, the power management device 300 can prevent unnecessary continuous waking of the terminal device 330 when the vehicle's ignition is off, and can stably and effectively perform power control by waking the terminal device 330 at specified intervals.

[0092] As an example, if the terminal device 330 determines that the accuracy of its data is less than or equal to a specified value, the terminal device 330 can determine that the wake-up condition is met and send a wake-up signal to the MCU through the determination unit. For example, if there is a fault in the data stored in the memory before receiving the wake-up packet, the terminal device 330 can determine that the accuracy is less than or equal to the specified value. Thus, the terminal device 330 can perform a wake-up in cases of low data accuracy or faults in previously stored data, thereby quickly preventing problems caused by data errors.

[0093] As an example, if terminal device 330 determines that it should remain in a wake-up state, it can send a specified signal to the determining unit via the MCU. The specified signal may include, for example, a request for the transmission of a wake-up signal. Based on receiving the specified signal from the MCU, the determining unit can send a wake-up signal to the MCU, regardless of whether a wake-up packet has been received or whether wake-up conditions are met. In other words, if it is identified that the wake-up state should be maintained continuously, the determining unit can unconditionally send a wake-up signal to the MCU via the specified signal sent from the MCU, regardless of whether other conditions are met.

[0094] Figure 4 This is a conceptual diagram illustrating the configuration of a power management device according to an embodiment disclosed in this document.

[0095] According to the implementation method, the power management device (e.g., Figure 3The power management device 300 may include a first control unit 410, at least one second control unit (e.g., a (2-1) control unit 421, a (2-2) control unit 422, and a (2-3) control unit 423), at least one terminal device 431, 432, 433, 434, 435, and 436, at least one sensor 441 and 442, and a battery pack 450. For example, components included in the power management device may transmit and receive power and / or data based on a first path 491 or a second path 492. The first path 491 and the second path 492 may respectively represent electrical paths for transmitting and receiving power and / or data according to PoDL-based and WoL-based communication protocols. The first path 491 may include a 1-1 path 481, and the second path 492 may include a 2-1 path 482.

[0096] For example, the first control unit 410 can provide power or send data to the designated terminal device 431 via the 1-1 path 481.

[0097] For example, at least one second control unit (e.g., control unit 421 (2-1), control unit 422 (2-2), and control unit 423 (2-3)) and at least one terminal device 431, 432, 433, 434, 435, and 436) can send and receive data via the second path 492. As an example, control unit 423 (2-3) can send data (e.g., a wake-up packet) to a designated terminal device 431 via path 482 (2-1).

[0098] For example, the designated terminal device 431 may include control devices for controlling the battery pack 450 included in its own vehicle. The designated terminal device 431 may obtain various information about the battery pack 450 (e.g., temperature, SoH, SoC, operating history, etc.) by using, for example, at least one sensor 441 and 442.

[0099] For example, the first control unit 410 can monitor the status information of the battery pack 450. If the first control unit 410 determines based on the status information that the battery pack 450 corresponds to a specified state (e.g., a state where the SoC is less than or equal to a specified value), then the first control unit 410 can identify the real-time status of its own vehicle. The first control unit 410 can use the real-time status to set a priority for each of at least one terminal device 431, 432, 433, 434, 435, and 436, and provide power to the at least one terminal device 431, 432, 433, 434, 435, and 436 sequentially according to the set priority.

[0100] For example, upon receiving an ignition start input from its own vehicle, the first control unit 410 may supply power to at least one second control unit 421, 422, and 423 and / or at least one terminal device 431, 432, 433, 434, 435, and 436. The control unit 410 may determine the magnitude of the power to be supplied to the target device based on at least one of the type, operating state, operating type, or any combination thereof of the target device to be powered. As an example, the magnitude of the power supplied to at least one second control unit 421, 422, and 423 may be greater than the magnitude of the power sent to at least one terminal device 431, 432, 433, 434, 435, and 436.

[0101] For example, the first control unit 410 can provide power to a designated terminal device 431 for controlling the battery pack 450. The first control unit 410 can provide power to the designated terminal device 431 via, for example, a 1-1 path 481, based on Power over Data Line (PoDL).

[0102] For example, if a specified event occurs, the (2-3) control unit 423 can identify the terminal device corresponding to the specified event among at least one terminal device 431, 432, 433, 434, 435, and 436. When the specified event is related to the battery pack 450, the (2-3) control unit 423 can identify the specified terminal device 431 and send a wake-up packet via path 2-1 482.

[0103] For example, the (2-3) control unit 423 can generate a wake-up packet in which wake-up conditions are set by using at least one of the vehicle's state, the presence of errors in the data, or any combination thereof, and send the wake-up packet to the designated terminal device 431 via path 482 of 2-1 based on LAN wake-up (WoL). When the wake-up conditions are met, the designated terminal device 431 can be woken up.

[0104] Figure 5 This is a conceptual diagram illustrating the configuration of a power management device according to an embodiment disclosed in this document.

[0105] According to the implementation method, the power management device (e.g., Figure 3 The power management device 300 may include a first control unit 510 (e.g., Figure 3 First control unit 310), second control unit 520 (e.g., Figure 3 The second control unit 320), and the terminal device 530 (e.g., Figure 1The device includes a terminal device 530, at least one sensor 541 and 542, and a battery pack 550. For example, components included in the power management device can send and receive power and / or data based on a first path 591 or a second path 592. The first path 591 and the second path 592 can respectively represent electrical paths for sending and receiving power and / or data via communication protocols based on PoDL and WoL. The first path 591 may include a 1-1 path 581, and the second path 592 may include a 2-1 path 582.

[0106] For example, the first control unit 510 can provide power or send data to the terminal device 330 through the first-first path 581.

[0107] For example, the second control unit 520 and the terminal device 530 can send and receive data via the second path 392. As an example, the second control unit 520 can send data (e.g., a wake-up packet) to the terminal device 530 via the second-first path 382. The second control unit 520 can generate the wake-up conditions included in the wake-up packet, for example, by using the determining unit 525.

[0108] For example, terminal device 530 may include control devices for controlling battery pack 550 included in its own vehicle. Terminal device 530 may use, for example, at least one sensor 541 and 542 to obtain various information related to battery pack 550 (e.g., temperature, SoH, SoC, operating history, etc.).

[0109] For example, terminal device 530 can receive power from first control unit 510 using first interface 561 and receive data from second control unit 520 using second interface 562, which is different from first interface 561. The received data may include wake-up packets instructing terminal device 530 to perform a wake-up operation. Terminal device 530 can then send the power provided through first interface 561 to determination unit 532 and MCU 534.

[0110] For example, the second control unit 520 can set wake-up conditions related to at least one of the vehicle's state, the accuracy of the data for the wake-up packet from the terminal device 530, or any combination thereof. The second control unit 520 can send the wake-up packet to the terminal device 530 via a 2-1 path 582 based on LAN Wake-up (WoL). The terminal device 530 can, for example, perform a wake-up operation only if it determines that the wake-up conditions are met upon receiving the wake-up packet.

[0111] For example, terminal device 530 may include a determining unit 532 and an MCU 534. Terminal device 530 may use determining unit 532, for example, to determine whether the wake-up conditions set for the wake-up group are met.

[0112] As an example, if the vehicle's engine is detected to be on, the terminal device 530 can determine through the determination unit 532 that the wake-up condition is met and send a wake-up signal to the MCU 534.

[0113] As an example, if the accuracy of data from terminal device 530 is identified as less than or equal to a specified value, terminal device 530 can determine, through determining unit 532, that the wake-up condition is met and send a wake-up signal to MCU 534. For instance, if there is a fault or the accuracy is less than or equal to a specified value in data previously stored in memory (not shown) before receiving the wake-up packet, terminal device 530 can determine that the wake-up condition is met. Therefore, a wake-up signal can be sent to MCU 534 for wake-up operation.

[0114] As an example, if it is detected that the vehicle's engine is off, the terminal device 530 can send a wake-up signal to the MCU 534 at a specified period, so that the terminal device 530 is woken up at the specified period.

[0115] As an example, if it is determined that the terminal device 530 should continuously maintain a wake-up state, the MCU 534 can send a specified signal to the determination unit 532. For example, the MCU 534 can determine that the terminal device 530 should continuously maintain a wake-up state if its own vehicle's ignition is on or if the vehicle is being driven. Based on the specified signal received from the MCU 534, the determination unit 532 can send a wake-up signal to the MCU 534, regardless of whether a wake-up packet has been received or whether the wake-up conditions are met.

[0116] Figure 6 This is a flowchart of a power management method according to the implementation method disclosed in this document.

[0117] According to the implementation method, the power management device (e.g., Figure 3 The power management device 300 can perform Figure 6 The operation disclosed herein. For example, including at least some components in the power management device (e.g., Figure 3 The first control unit 310, the second control unit 320, and the terminal device 530 can be configured to execute Figure 6 The operation.

[0118] In the following implementation, the operations of S610 to S650 may be executed sequentially, but not necessarily sequentially. For example, the order of each operation can be changed, and at least two operations can be executed in parallel. Furthermore, details related to the above can be briefly described or omitted. Figure 6 The content described corresponds to or overlaps with the content.

[0119] Reference Figure 6 The power management method may include the following steps: (S610) igniting its own vehicle; (S620) connecting power to at least one device in its own vehicle; (S630) identifying the occurrence of a specified event related to the operation of its own vehicle; (S640) determining whether a control device corresponding to the specified event is in a sleep state; (S645) if the control device is in a sleep state, sending a wake-up packet to the control device; and (S650) if the control device is not in a sleep state (or, if the control device is in a wake-up state), operating the control device.

[0120] In step S610, the power management device can activate the ignition of its own vehicle. For example, if the power management device receives an ignition start input for its own vehicle (e.g., a button input), the power management device can activate the ignition of its own vehicle.

[0121] In step S620, the power management device may turn on the power to at least one device in its own vehicle. For example, when the power is turned on, at least one device may first enter a sleep state from a closed state. The sleep state can be defined, for example, as a state in which the power is on but has not yet been awakened and is being driven by minimal power.

[0122] In step S630, the power management device can identify the occurrence of a specified event related to the operation of its own vehicle. The power management device can identify, among at least one device, a control device corresponding to the specified event (e.g., a terminal device for controlling the battery pack).

[0123] In step S640, the power management device can determine whether the control device corresponding to the specified event is in a sleep state.

[0124] In step S645, the power management device can use a zone controller (e.g., Figure 3 The second control unit 320 sends a wake-up packet to the control device to control the control device to wake up from the sleep state and start operation.

[0125] In step S650, the power management device can operate the control device.

[0126] Figure 7 This is a flowchart of a power management method according to the implementation method disclosed in this document.

[0127] According to the implementation method, the power management device (e.g., Figure 3 The power management device 300 can perform Figure 7 The operation disclosed herein. For example, at least some components included in the power management device (e.g., Figure 3The first control unit 310, the second control unit 320, and the terminal device 330 can be configured to execute Figure 7 The operation.

[0128] In the following implementation, the operations of S710 to S750 can be executed sequentially, but not necessarily sequentially. For example, the order of each operation can be changed, and at least two operations can be executed in parallel. Furthermore, details related to the above can be briefly described or omitted. Figure 5 The content described corresponds to or overlaps with the content.

[0129] Reference Figure 7 The power management method may include the following steps: (S710) monitoring the status information of the battery pack; (S720) determining whether the battery pack is in a specified state; (S730) identifying the real-time status of its own vehicle; (S740) using the real-time status to set the priority of the corresponding terminal device; and (S750) providing power to the terminal device in sequence according to the priority.

[0130] In step S710, the power management device may use at least some of the information obtained by at least one sensor and / or the information received by the battery pack through the communication unit to continuously monitor the status information of the battery pack.

[0131] In step S720, the power management device can determine whether the battery pack is in a specified state based on state information. The specified state may include, for example, a low voltage state, a state where SoC and / or SoH are less than or equal to a specified value, etc.

[0132] In step S730, the power management device can identify the real-time status of its own vehicle, including its own vehicle's internal status, driving situation, passenger status, passenger physical information, movement, etc.

[0133] In step S740, the power management device can use real-time status to set priorities for each terminal device. For example, if the vehicle's driving speed is less than or equal to a specified value and the user is inside the vehicle, the power management device can set a high priority for the infotainment device for the user's convenience.

[0134] In step S750, the power management device may first provide power to terminal devices with higher priority. As an example, after step S740, the power management device may prioritize providing power to the infotainment device within the terminal device.

[0135] Figure 8 This is a block diagram illustrating the hardware configuration of a computing system for performing an operation method of a power management device according to an embodiment disclosed in this document.

[0136] Reference Figure 8 The computing system 3000 according to the embodiments disclosed in this document may include an MCU 1010, a memory 1020, an input / output I / F 1030, and a communication I / F 1040.

[0137] MCU 1010 can be a processor that executes various programs stored in memory 1020, processes various information including battery data, and performs the aforementioned tasks. Figure 3 The functions of the processor (or control unit) in the power management device shown.

[0138] The memory 1020 can store various programs used to perform the functions of the power 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.

[0139] Multiple such memories 1020 can be provided as needed. Memory 1020 can be volatile or non-volatile memory. Memory 1020 used as volatile memory can be RAM, DRAM, SRAM, etc. Memory 1020 used as non-volatile memory can be ROM, PROM, EAROM, EPROM, EEPROM, flash memory, etc. The examples of memory 1020 listed above are merely examples and are not limited to these examples.

[0140] The input / output I / F 1030 can provide an interface that allows data to be sent and received by connecting input devices (not shown) such as a keyboard, mouse, or touch panel and output devices (not shown) such as a display to the MCU 1010.

[0141] The Communication I / F 940 is configured to send and receive various data with a server and can be a variety of devices that support wired or wireless communication. For example, a power management device can send and receive various information, including battery data, from a separately provided external server via the Communication I / F 1040.

[0142] In this way, a computer program according to the embodiments disclosed in this document can be implemented to execute, for example, by being recorded in memory 1020 and processed by MCU 1010. Figure 1 The modules for each function are shown.

[0143] In the foregoing, even though all components constituting the embodiments disclosed in this document have been described as combined as a single component or operated in combination, 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 components may be selectively combined and operated in one or more combinations.

[0144] Furthermore, unless specifically stated to the contrary, the terms "comprising," "configured," or "having" above mean that the corresponding component may be included, and therefore should be interpreted as capable of further including, rather than excluding, other components. 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 in this document pertain. Commonly used terms, such as those defined in dictionaries, should be interpreted as consistent with the meaning in the context of the relevant art and should not be interpreted in an idealized or overly formal sense unless explicitly defined in this document.

[0145] The above description is merely an illustrative description of the technical concepts disclosed in this document, and those skilled in the art can make various modifications and variations to the embodiments disclosed in this document without departing from the basic characteristics of the embodiments disclosed in this document. Therefore, the embodiments disclosed in this document are intended to illustrate, not limit, the technical concepts of the embodiments disclosed in this document, and the scope of the technical concepts disclosed in this document is not limited by these embodiments. The scope of protection of the technical concepts disclosed in this document should be interpreted by the scope of the appended claims, and all technical concepts within the equivalent scope should be interpreted as included within the scope of the rights in this document.

Claims

1. A power management device, the power management device comprising: A first control unit, which is electrically connected to the battery pack; At least one second control unit, the at least one second control unit being electrically connected to the first control unit; as well as A terminal device electrically connected to the first control unit and the at least one second control unit and configured to control the battery pack. The terminal device is configured to receive power from the first control unit and to receive a wake-up packet from the at least one second control unit.

2. The power management device according to claim 1, wherein, The first control unit is configured to, upon receiving an ignition start input for its own vehicle, use power received from the battery pack via Power over Data Line (PoDL) to provide a first power and a second power to the at least one second control unit and the terminal device, respectively.

3. The power management device according to claim 2, wherein, The first control unit is configured to determine the magnitude of the power to be supplied to the target device based on at least one of the type, operating state, operating type, or any combination thereof of the target device to be powered.

4. The power management device according to claim 2, wherein, The first power supplied to the at least one second control unit is greater than the second power supplied to the terminal device.

5. The power management device according to claim 1, wherein, The first control unit is configured as follows: Monitor the status information of the battery pack; If it is determined based on the state information that the battery pack corresponds to a specified state, then the real-time state of its own vehicle is identified. Use the real-time status to set a priority for each terminal device in the terminal device; as well as Power is supplied to the terminal device sequentially according to the set priority.

6. The power management device according to claim 5, wherein, The first control unit is configured to determine that the battery pack corresponds to the specified state when the state of charge (SoC) of the battery pack is less than or equal to a specified value.

7. The power management device according to claim 5, wherein, The first control unit is configured as follows: If, based on the real-time status, it is determined that the vehicle's driving speed is less than or equal to a specified value and the user is inside the vehicle, then a high priority is assigned to the infotainment device; and Power is preferentially supplied to the infotainment device within the terminal device.

8. The power management device according to claim 1, wherein, The at least one second control unit is configured to: If a specified event occurs, the specified terminal device corresponding to the specified event is identified in the terminal devices. as well as Generate a wake-up packet that sets wake-up conditions based on at least one of its own vehicle status, data error existence, or any combination thereof, and send the wake-up packet to the designated terminal device based on Wake-up LAN (WoL). The designated terminal device is configured to be woken up based on the fulfillment of the wake-up conditions.

9. A vehicle comprising a power management device according to any one of claims 1 to 8.

10. A power management method, the power management method comprising the following steps: When the vehicle receives an ignition start input, the first control unit uses power received from the battery pack via Power over Data Line (PoDL) to provide first power and second power to at least one second control unit and the terminal device, respectively. If a specified event occurs, the at least one second control unit identifies the specified terminal device corresponding to the specified event in the terminal device, generates a wake-up packet, and sends the wake-up packet to the specified terminal device. as well as The designated terminal device is turned on by power supplied from the first control unit and is woken up based on the receipt of the wake-up packet.

11. The power management method according to claim 10, further comprising the following steps: When an ignition start input for its own vehicle is received, the first control unit uses power received from the battery pack via Power over Data Line (PoDL) to provide first power and second power to the at least one second control unit and the terminal device, respectively.

12. The power management method according to claim 11, further comprising the following steps: The first control unit determines the magnitude of the power to be supplied to the target device based on at least one of the target device type, operating state, operating type, or any combination thereof.

13. The power management method according to claim 10, further comprising the following steps: The first control unit monitors the status information of the battery pack, and if it is determined based on the status information that the battery pack corresponds to a specified state, it identifies the real-time status of its own vehicle. The first control unit uses the real-time status to set a priority for each terminal device in the terminal devices; as well as The first control unit supplies power to the terminal device sequentially according to the set priority.

14. The power management method according to claim 13, further comprising the following steps: If, based on the real-time status, it is determined that the driving speed of its own vehicle is less than or equal to a specified value and the user is inside its own vehicle, then the first control unit sets a high priority for the infotainment device. as well as The first control unit preferentially supplies power to the infotainment device in the terminal device.

Images