Battery data management device and operation method thereof

Abstract

A battery data management device according to one embodiment disclosed in this document may include a plurality of functional modules that perform functions defined based on a pre-set algorithm, a first broker that relays cooperative operations between the plurality of functional modules based on battery data of at least one of the plurality of functional modules, and a first controller that controls the operation of the plurality of functional modules and the first broker.

Description

[Technical Field]

[0001] The embodiments disclosed in this document claim the benefit of priority based on Korean Patent Application No. 10-2021-0148332, filed November 1, 2021, and all contents disclosed in the documents of this Korean patent application are incorporated herein by reference. SUMMARY OF THE INVENTION The embodiments disclosed herein relate to a battery data management device and method of operation. [Background technology]

[0002] An energy storage system (ESS) stores large amounts of electrical energy in multiple battery racks, each containing multiple battery modules connected in series and / or parallel. The battery racks of an energy storage system may generate heat due to chemical reactions during the charging and discharging process, which can damage the performance and lifespan of the battery racks. Therefore, the battery racks can transmit and manage battery data, including the temperature, voltage, and current of the battery racks, to a battery system controller (BSC).

[0003] However, such a large-capacity battery system controller requires a high-performance system to perform various functions such as data communication and data logging in a single system, which results in problems such as high installation costs and the need for a lot of resources for maintenance. Summary of the Invention [Problem to be solved by the invention]

[0004] One objective of the embodiments disclosed in this document is to provide a battery data management device and an operating method thereof that can distribute the operations of functional modules to quickly process battery data simultaneously in multiple modules and efficiently manage battery data.

[0005] The technical problems of the embodiments disclosed in this document are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art from the following description. [Means for solving the problem]

[0006] A battery data management device according to one embodiment disclosed in this document may include a plurality of functional modules that perform defined functions based on a pre-set algorithm, a first broker that relays cooperative operations between the plurality of functional modules based on battery data of at least one of the plurality of functional modules, and a first controller that controls the operations of the plurality of functional modules and the first broker.

[0007] In one embodiment, the plurality of functional modules can perform defined functions based on control instructions of the first controller. In one embodiment, the plurality of functional modules may perform battery data communication with the first broker to transmit the battery data.

[0008] In one embodiment, the first broker may cache battery data of at least one of the plurality of functional modules. In one embodiment, the first broker may relay the battery data cached from the plurality of functional modules between the plurality of functional modules.

[0009] In one embodiment, when a failure occurs in at least one of the plurality of functional modules, the controller can control other functional modules to perform the defined functions of the functional module.

[0010] In one embodiment, the battery data management device may further include a second broker that relays cooperative operations between the plurality of functional modules based on battery data of at least one of the plurality of functional modules, and a second controller that controls the operation of the plurality of functional modules and the second broker.

[0011] In one embodiment, the first broker and the second broker may share the cached battery data from the plurality of functional modules. In one embodiment, the first broker or the second broker may transmit the battery data cached from at least one of the plurality of functional modules to the second broker or the first broker.

[0012] In one embodiment, the first controller or the second controller can control at least one of the plurality of functional modules that communicates battery data with the first broker or the second broker to communicate battery data with the second broker or the first broker when a failure occurs in the first broker or the second broker.

[0013] An operating method of a battery data management device according to one embodiment disclosed in this document may include the steps of: a plurality of functional modules performing defined functions based on a pre-set algorithm; a first broker relaying cooperative operations between the plurality of functional modules based on battery data of at least one of the plurality of functional modules; and a first controller controlling the operations of the plurality of functional modules and the first broker.

[0014] In one embodiment, the step in which the first controller controls the operation of the plurality of functional modules and the first broker can include the first controller controlling other functional modules to perform the defined functions of at least one of the plurality of functional modules when a failure occurs in the functional module.

[0015] In one embodiment, a method of operating a battery data management device may further include a step in which a second broker relays cooperative operations between the plurality of functional modules based on battery data of at least one of the plurality of functional modules, and a step in which a second controller controls the operations of the plurality of functional modules and the second broker.

[0016] In one embodiment, the step in which the first broker relays the interconnection between the plurality of functional modules based on battery data of at least one of the plurality of functional modules is characterized in that the first broker transmits the battery data cached from at least one of the plurality of functional modules to the second broker, and the step in which the second broker relays the interconnection between the plurality of functional modules based on battery data of at least one of the plurality of functional modules can be characterized in that the second broker transmits the battery data cached from at least one of the plurality of functional modules to the first broker.

[0017] In one embodiment, the step in which the first controller controls the operation of the plurality of functional modules and the first broker is characterized in that the first controller controls at least one of the plurality of functional modules that communicates battery data with the first broker to communicate battery data with the second broker when a failure occurs in the first broker, and the step in which the second controller controls the operation of the plurality of functional modules and the second broker can be characterized in that the second controller controls at least one of the plurality of functional modules that communicates battery data with the second broker to communicate battery data with the first broker when a failure occurs in the second broker. [Effects of the Invention]

[0018] According to one embodiment of the battery data management device and its operating method disclosed in this document, the operation of functional modules can be distributed to quickly process battery data simultaneously in multiple modules, thereby efficiently managing battery data. [Brief explanation of the drawings]

[0019] [Figure 1] 1 is a diagram illustrating a schematic configuration of an energy storage system to which a battery data management device according to an embodiment disclosed herein is applied. [Figure 2] FIG. 1 is a diagram specifically illustrating the configuration of a battery data management device according to an embodiment disclosed in a document. [Figure 3] FIG. 10 is a diagram for specifically explaining the configuration of a battery data management device according to another embodiment disclosed in this document. [Figure 4] 1 is a flowchart illustrating a method of operating a battery data management device according to an embodiment disclosed herein. [Figure 5] 1 is a block diagram showing the hardware configuration of a computing system that implements an operation method of a battery data management device according to an embodiment disclosed in this document. DETAILED DESCRIPTION OF THE INVENTION

[0020] Some embodiments disclosed herein will be described in detail below with reference to exemplary drawings. When assigning reference numerals to components in each drawing, it should be noted that the same reference numerals are assigned to the same components when they appear in other drawings as much as possible. Furthermore, when describing the embodiments disclosed herein, if a detailed description of related known structures or functions is deemed to hinder understanding of the embodiments disclosed herein, such detailed description will be omitted.

[0021] When describing components of the embodiments disclosed herein, terms such as first, second, A, B, (a), (b), etc. may be used. Such terms are merely used to distinguish the component from other components and do not limit the nature, order, or procedure of the components. Furthermore, unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by a person of ordinary skill in the art to which the embodiments disclosed herein belong. Terms defined in commonly used dictionaries should be interpreted to have a meaning consistent with the context of the relevant art and should not be interpreted in an idealized or overly formal sense unless expressly defined herein.

[0022] FIG. 1 is a schematic diagram of a battery management device applied in an energy storage system according to one embodiment disclosed herein. Referring to FIG. 1 , an energy storage system (ESS) 1 may include a battery bank 10 , a power conversion system (PCS) 20 , and a battery data management device 100 .

[0023] The battery data management device 100 can control the plurality of batteries in the battery bank 10 to acquire battery data. The battery data management device 100 can perform data communication with the plurality of batteries and receive battery data related to the plurality of batteries. For example, the battery data management device 100 can receive measured values ​​of the temperatures and voltages of the plurality of batteries and SOC and SOH parameters derived therefrom from the plurality of batteries.

[0024] According to one embodiment, the battery data management device 100 is implemented in the form of a battery system controller (BSC) and can control the operation of multiple batteries. That is, the battery data management device 100 can communicate with a controller provided in the battery system. The battery data management device 100 can transmit control signals to the battery system to control the operation of multiple batteries. The battery data management device 100 can also receive battery data from the battery system and manage the status of the battery system.

[0025] The battery data management device 100 can analyze and manage battery data acquired from a plurality of batteries using internal components with abundant computing resources. In addition, the battery data management device 100 can precisely analyze abnormal phenomena in battery data through the internal components and diagnose whether or not a plurality of batteries are in an abnormal state.

[0026] Here, according to one embodiment, the plurality of batteries may be realized in the form of a plurality of battery racks provided in the energy storage system and storing electrical energy. A battery rack is a unit for storing electrical energy in the energy storage system. The energy storage system may include one or more battery banks including a plurality of battery racks. The battery bank may include a plurality of battery racks and a bank battery management system (BBMS).

[0027] Each of the battery racks may include a rack battery management system (RBMS) that controls a plurality of battery modules, a charging / discharging device, and a plurality of module BMSs that control the battery modules. The battery modules may supply power to a target device (not shown). To this end, the battery modules may be electrically connected to the target device. The target device may include electrical, electronic, or mechanical devices that operate by receiving power from each of the battery racks including the battery modules. For example, the target device may be, but is not limited to, an energy storage system (ESS). Each of the battery modules may include, but is not limited to, a plurality of battery cells connected in series and / or parallel. The battery cells may be, but are not limited to, lithium-ion (Li-ion) batteries, lithium-ion polymer (Li-ion) batteries, nickel-cadmium (Ni-Cd) batteries, nickel-metal hydride (Ni-MH) batteries, etc.

[0028] In the following description, it is assumed that the plurality of batteries are realized in the form of a battery bank including a plurality of battery racks. The battery bank 10 can include a first battery rack 11, a second battery rack 12, a third battery rack 13, and a fourth battery rack 14. Although the number of battery racks is shown as four in FIG. 1, the number is not limited to four, and the battery bank 10 can include n battery racks (n is a natural number equal to or greater than 1).

[0029] The battery data management device 100 can manage each component included in the energy storage system 1 and control the overall operation. That is, the battery data management device 100 can control the operation of the plurality of battery racks 11, 12, 13, and 14 and the power conversion device 20 included in the energy storage system 1.

[0030] First, the battery data management device 100 can receive battery data from the plurality of battery racks 11, 12, 13, and 14 and manage the status of the plurality of battery racks 11, 12, 13, and 14. Specifically, the battery data management device 100 can communicate with controllers (e.g., rack BMS) provided in the plurality of battery racks 11, 12, 13, and 14. The battery data management device 100 can receive battery data from the controllers provided in the plurality of battery racks 11, 12, 13, and 14 and manage the status of the plurality of battery racks 11, 12, 13, and 14.

[0031] Furthermore, the battery data management device 100 can transmit control signals to the plurality of battery racks 11, 12, 13, and 14 to control the operations of the plurality of battery racks 11, 12, 13, and 14. The battery data management device 100 can transmit a control signal to the power conversion device 20 and control the power conversion operation of the power conversion device 20. The power conversion device 20 can perform the power conversion operation in accordance with the control of the battery data management device 100.

[0032] Here, the power conversion device 20 can convert AC power to DC power (AC / DC convert) or convert DC power to DC power (DC / DC convert) and supply the converted DC power to the multiple battery racks 11, 12, 13, and 14. The power conversion device 20 can convert DC power supplied from the multiple battery racks 11, 12, 13, and 14 into AC power. The power conversion device 20 can also supply the converted AC power to a load (not shown).

[0033] The battery racks 11, 12, 13, and 14 can be charged using DC power supplied from the power conversion device 20. The battery racks 11, 12, 13, and 14 can also discharge by outputting DC power and supplying it to the power conversion device 20.

[0034] Fig. 2 is a diagram specifically explaining the configuration of a battery data management device according to one embodiment disclosed in the document, and Fig. 3 is a diagram specifically explaining the configuration of a battery data management device according to another embodiment disclosed in the document.

[0035] The configuration of the battery data management device 100 will be specifically described below with reference to FIGS. First, referring to FIG. 2, the battery data management device 100 may include a plurality of function modules 110, a first broker 120, and a first controller .

[0036] The plurality of functional modules 110 may include a first functional module 111, a second functional module 112, a third functional module 113, and a fourth functional module 114. Although the plurality of functional modules is shown as four in FIG. 2, the present invention is not limited to this, and the plurality of functional modules 110 may be configured to include n (n is a natural number equal to or greater than 2) functional modules.

[0037] Each of the functional modules 111, 112, 113, and 114 can perform a defined function based on a preset algorithm. For example, each of the functional modules 111, 112, 113, and 114 can perform one of battery data communication with the battery racks 11, 12, 13, and 14, control of the battery racks 11, 12, 13, and 14, user interface (UI) operation of the energy storage system 1 to which the battery data management device 100 is applied, and battery data logging. In other words, the battery data management device 100 can distinguish the functions of the functional modules 111, 112, 113, and 114 and support load distribution.

[0038] Specifically, each of the plurality of functional modules 111, 112, 113, and 114 can perform a defined function based on a control command from the first controller 130. That is, each of the plurality of functional modules 111, 112, 113, and 114 can perform a specified function based on a control command from the first controller 130.

[0039] For example, any one of the multiple functional modules 111, 112, 113, and 114 can perform battery data communication with the multiple battery racks 11, 12, 13, and 14 to acquire battery data. For example, the first functional module 111 can perform wired and / or wireless communication with the first battery rack 11, which is one of the multiple battery racks 11, 12, 13, and 14. For example, the first functional module 111 can communicate with the first battery rack 11 using a differential input communication protocol. Here, examples of differential input communication protocols include CAN (Controller Area Network), RS-485 (Recommended Standard 485), and RS-422 (Recommended Standard 422). Furthermore, for example, the first functional module 111 can communicate with the first battery rack 11 using a wireless communication protocol such as Wi-Fi (registered trademark) or Bluetooth (registered trademark).

[0040] Each of the multiple function modules 111, 112, 113, and 114 can perform battery data communication with the first broker 120 and transmit acquired or generated battery data. That is, the first broker 120 can acquire battery data from the multiple function modules 111, 112, 113, and 114.

[0041] The first broker 120 can relay cooperation between the plurality of functional modules 111, 112, 113, and 114 based on battery data acquired from at least one of the plurality of functional modules 111, 112, 113, and 114. Specifically, the first broker 120 can cache battery data of at least one of the plurality of functional modules 111, 112, 113, and 114. The first broker 120 can relay between the plurality of functional modules 111, 112, 113, and 114 based on the battery data cached from the plurality of functional modules 111, 112, 113, and 114.

[0042] For example, if the second functional module 112 can perform a specified function based on battery data acquired by the first functional module 111 among the multiple functional modules 111, 112, 113, and 114, the first broker 120 can transmit the battery data cached from the first functional module 111 to the second functional module 112 and relay the coordinated operation between the multiple functional modules 111, 112, 113, and 114.

[0043] Furthermore, for example, when a failure occurs in the first functional module 111 among the plurality of functional modules 111, 112, 113, and 114, the first broker 120 can transmit the battery cached from the failed first functional module 111 to the second functional module 112 that can be driven, and relay the operation between the plurality of functional modules 111, 112, 113, and 114.

[0044] The first controller 130 can control the operations of the plurality of functional modules 111, 112, 113, and 114 and the first broker 120. When a failure occurs in at least one of the plurality of functional modules 111, 112, 113, and 114, the first controller can control another functional module capable of operating the functional module to perform a specified function of the functional module. Specifically, when a failure occurs in at least one of the plurality of functional modules 111, 112, 113, and 114, the first controller can transmit a control command to another functional module capable of operating the functional module to perform the function.

[0045] According to one embodiment, the battery data management device 100 can perform a vertical scaling function by operating the multiple functional modules 111, 112, 113, and 114, the first broker 120 that manages the battery data of the multiple functional modules 111, 112, 113, and 114, and the first controller 130 that controls the multiple functional modules 111, 112, 113, and 114 and the first broker, as separate hardware devices. That is, because the multiple functional modules 111, 112, 113, and 114, the first broker 120, and the first controller 130 of the battery data management device 100 are operated as separate hardware devices, application processing power and storage capacity can be scaled up.

[0046] Referring to FIG. 3, the battery data management device 100 may further include a second broker 140 and a second controller 150. The second broker 140 can relay the cooperative operations between the multiple functional modules 115, 116, 117, and 118 based on the battery data of at least one of the multiple functional modules 115, 116, 117, and 118. In other words, the second broker 140 performs the same function as the first broker 130 and can horizontally expand the functions of the first broker 130.

[0047] Therefore, the battery data management device 100 forms a dual structure including a first broker 130 and a second broker 140 that perform similar functions, and can distribute the load that may be concentrated on either the first broker 130 or the second broker 140.

[0048] According to one embodiment, the battery data management device 100 operates each of the multiple functional modules 111, 112, 113, 114, 115, 116, 117, 118, the first broker 120, the second broker 140, the first controller 130, and the second broker 150 as separate hardware devices, and is capable of performing horizontal scaling functions.

[0049] That is, the battery data management device 100's multiple functional modules 111, 112, 113, 114, 115, 116, 117, 118, the first broker 120, the second broker 140, the first controller 130, and the second broker 150 can each be operated as separate hardware devices, enabling a scale-out function to be performed that can improve processing capacity by distributing functions that were previously processed by a single hardware device to multiple hardware devices.

[0050] The first broker 120 and the second broker 140 can share battery data cached from 111, 112, 113, 114, 115, 116, 117, and 118 with each other. Therefore, the first broker 120 can transmit battery data cached from at least one of the plurality of functional modules 111, 112, 113, and 114 to the second broker 140, and the second broker 140 can control the linked operations of the plurality of functional modules 111, 112, 113, and 114. Similarly, the second broker 140 can transmit battery data cached from at least one of the plurality of functional modules 115, 116, 117, and 118 to the first broker 120, and the first broker 120 can control the linked operations of the plurality of functional modules 115, 116, 117, and 118.

[0051] The second controller 150 can control the operations of the plurality of functional modules 110 and the second broker 140. When a failure occurs in at least one of the plurality of functional modules 111, 112, 113, and 114, the second controller can control another functional module capable of operating the functional module to perform a specified function of the functional module. Specifically, when a failure occurs in at least one of the plurality of functional modules 111, 112, 113, and 114, the second controller can transmit a control command to another functional module capable of operating the functional module to perform the function.

[0052] When a failure occurs in the second broker 140, the second controller 150 can control at least one of the plurality of functional modules 111, 112, 113, and 114 that communicates battery data with the second broker 140 to communicate battery data with the first broker 120. That is, the second controller 150 can change at least one of the plurality of functional modules 111, 112, 113, and 114 connected to the second broker 140 to be connected to the first broker 120.

[0053] Furthermore, when a failure occurs in the first broker 120, the first controller 130 can control at least one of the plurality of functional modules 111, 112, 113, and 114 that communicates battery data with the first broker 120 to communicate battery data with the second broker 140. That is, the first controller 130 can change at least one of the plurality of functional modules 111, 112, 113, and 114 connected to the first broker 120 to be connected to the second broker 140.

[0054] As described above, according to the battery data management device 100 of one embodiment disclosed in this document, the operation of functional modules can be distributed to quickly process battery data simultaneously in multiple modules, thereby efficiently managing battery data.

[0055] In addition, the battery data management device 100 performs a horizontal scaling function that drives multiple relatively low-performance functional modules without incorporating a high-performance system, thereby reducing installation costs and resources required for maintenance.

[0056] Furthermore, the battery data management device 100 performs a vertical scaling function that includes a broker and a controller that manage and control multiple functional modules, so that even if a failure occurs in one of the functional modules or the broker, it can immediately respond and eliminate system downtime.

[0057] 4 is a flowchart showing an operation method of the battery data management device according to an embodiment disclosed herein. Hereinafter, the operation method of the battery data management device 100 will be specifically described with reference to FIGS.

[0058] The battery data management device 100 is substantially the same as the battery data management device 100 described with reference to FIGS. 1 to 3, and therefore will be described briefly below to avoid duplication of description. Referring to FIG. 6, the operating method of the battery data management device 100 includes the steps of: a step (S101) in which a plurality of functional modules 110 perform functions defined based on a pre-set algorithm; a step (S102) in which a first broker 120 relays cooperative operations between the plurality of functional modules 110 based on battery data of at least one of the plurality of functional modules 110; a step (S103) in which a second broker 140 relays cooperative operations between the plurality of functional modules 110 based on battery data of at least one of the plurality of functional modules 110; a step (S104) in which a first controller 130 controls the operations of the plurality of functional modules 110 and the first broker 120; and a step (S105) in which a second controller 150 controls the operations of the plurality of functional modules 110 and the second broker 140.

[0059] Steps S101 to S105 will be specifically described below. In step S101, each of the functional modules 111, 112, 113, and 114 can perform a defined function based on a pre-set algorithm. For example, each of the functional modules 111, 112, 113, and 114 can perform one of battery data communication with the battery racks 11, 12, 13, and 14, control of the battery racks 11, 12, 13, and 14, user interface (UI) operation of the energy storage system 1 to which the battery data management device 100 is applied, and battery data logging. In other words, the battery data management device 100 can distinguish the functions of the functional modules 111, 112, 113, and 114 and support load distribution. In step S101 , each of the plurality of functional modules 111 , 112 , 113 , and 114 can perform a defined function based on a control command from the first controller 130 .

[0060] In step S102, the first broker 120 can relay the cooperation between the plurality of functional modules 111, 112, 113, and 114 based on the battery data of at least one of the plurality of functional modules 111, 112, 113, and 114.

[0061] In step S102, the first broker 120 can constantly transmit battery data cached from at least one of the plurality of functional modules 111, 112, 113, and 114 to the second broker 140 and perform synchronization with the second broker 140.

[0062] In step S103, the second broker 140 can relay the cooperation between the plurality of functional modules 111, 112, 113, and 114 based on the battery data of at least one of the plurality of functional modules 111, 112, 113, and 114.

[0063] In step S103, the second broker 140 can constantly transmit the battery data cached from at least one of the plurality of functional modules 111, 112, 113, and 114 to the first broker 120 and perform synchronization with the first broker 120.

[0064] In step S104 , the first controller 130 can control the operations of the multiple function modules 111 , 112 , 113 , 114 and the first broker 120 . In step S104, when a failure occurs in at least one of the plurality of functional modules 111, 112, 113, and 114, the first controller 130 can control the other functional modules to perform the defined functions of the functional module.

[0065] In step S104, when a failure occurs in the first broker 120, the first controller 130 can control at least one of the multiple functional modules 111, 112, 113, and 114 that communicate battery data with the first broker 120 to communicate battery data with the second broker 140.

[0066] In step S105 , the second controller 150 can control the operations of the plurality of function modules 111 , 112 , 113 , 114 and the second broker 140 . In step S105, when a failure occurs in at least one of the plurality of functional modules 111, 112, 113, and 114, the second controller 150 can control the other functional modules to perform the defined functions of the functional module.

[0067] In step S105, when a failure occurs in the second broker 140, the second controller 150 can control at least one of the multiple functional modules 111, 112, 113, and 114 that communicate battery data with the second broker 140 to communicate battery data with the first broker 120.

[0068] FIG. 5 is a block diagram showing the hardware configuration of a computing system that implements the method of operating a battery data management device according to an embodiment disclosed herein. Referring to FIG. 5, a computing system 200 according to one embodiment disclosed herein may include an MCU 210 , a memory 220 , an input / output I / F 230 , and a communication I / F 240 .

[0069] The MCU 210 may be a broker that executes various programs (e.g., a program for monitoring battery data) stored in the memory 220, processes various data through such programs, and performs the functions of the battery data management device 100 shown in FIG. 1 described above.

[0070] The memory 220 can store various programs related to the operation of the battery data management device 100. The memory 220 can also store operation data of the battery data management device 100.

[0071] A plurality of such memories 220 may be provided as necessary. The memories 220 may be volatile memories or nonvolatile memories. As the volatile memories 220, RAM, DRAM, SRAM, etc. may be used. As the nonvolatile memories 220, ROM, PROM, EAROM, EPROM, EEPROM, flash memory, etc. may be used. The examples of the memories 220 listed above are merely illustrative and are not limited to these examples.

[0072] The input / output I / F 230 can provide an interface that connects input devices (not shown) such as a keyboard, mouse, or touch panel, and output devices such as a display (not shown), to the MCU 210, enabling data to be sent and received.

[0073] The communication I / F 240 is configured to be able to send and receive various data to and from a server, and may be any device capable of supporting wired or wireless communication. For example, programs for resistance measurement and abnormality diagnosis, various data, and the like can be sent and received from a separately provided external server via the communication I / F 240.

[0074] The above description merely exemplifies the technical ideas of the present disclosure, and various modifications and variations are possible by a person having ordinary knowledge in the technical field to which the present disclosure pertains, without departing from the essential characteristics of the present disclosure.

[0075] Therefore, the embodiments disclosed in this disclosure are intended to illustrate, not limit, the technical idea of ​​the disclosure, and the scope of the technical idea of ​​the disclosure is not limited by such embodiments. The scope of protection of the disclosure should be interpreted by the claims set forth below, and all technical ideas within the scope equivalent thereto should be interpreted as being included in the scope of rights of the disclosure. [Explanation of symbols]

[0076] 1. Energy storage system 10 Battery Bank 11 Battery Rack No. 1 12 Second Battery Rack 13 Third Battery Rack 14 4th Battery Rack 100 Battery data management device 110 Multiple Functional Modules 111 First Function Module 112 Second Function Module 113 Third Function Module 114 4th Function Module 115 5th Function Module 116 6th Function Module 117 7th Function Module 118 8th Function Module 120 First Broker 130 First Controller 140 Second Broker 20 Power conversion device 200 Computing Systems 210 MCU 220 memory 230 Input / Output Interface 240 communication interface

Claims

1. A battery data management device including a plurality of functional modules, a first broker that is a device connected to the plurality of functional modules, and a first controller that is a device connected to the first broker, Each of the plurality of functional modules communicates with a plurality of battery racks, and performs the following operations based on an instruction from the first controller: an acquisition function for acquiring battery data of at least one battery included in each of the plurality of battery racks; a battery rack control function for updating the battery data by controlling the plurality of battery racks based on the battery data; a data logging function for recording the battery data; configured to perform at least one of the battery data includes at least a SOC or a SOH of the at least one battery; The first broker: caching the battery data of at least a first functional module among the plurality of functional modules based on an instruction from the first controller, and sharing the battery data among the plurality of functional modules; In response to a failure of the first functional module, causing a second functional module different from the first functional module among the plurality of functional modules to perform the function that had been performed by the first functional module; or When the second functional module can perform a designated function among the acquisition function, the battery rack control function, and the data logging function based on the battery data received from the first functional module, the second functional module is caused to perform the designated function. relaying the linked operations between the plurality of functional modules by at least one of the above; Battery data management device.

2. The system further includes a second broker that is a device connected to the plurality of functional modules, and a second controller that is a device connected to the second broker, The first broker transmits the battery data cached from at least one of the plurality of functional modules to the second broker based on an instruction from the first controller, or The second broker transmits the battery data cached from at least one of the plurality of functional modules to the first broker based on an instruction from the second controller. The battery data management device according to claim 1 .

3. 3. The battery data management device of claim 2, wherein the first controller or the second controller controls at least one of the plurality of functional modules that communicates battery data with the first broker or the second broker to communicate battery data with the second broker or the first broker when a failure occurs in the first broker or the second broker.

4. A method executed by a battery data management device including a plurality of functional modules, a first broker that is a device connected to the plurality of functional modules, and a first controller that is a device connected to the first broker, By communicating with a plurality of battery racks by each of the plurality of functional modules, based on an instruction from the first controller, an acquisition function for acquiring battery data of at least one battery included in each of the plurality of battery racks; a battery rack control function for updating the battery data by controlling the plurality of battery racks based on the battery data; a data logging function for recording the battery data; wherein the battery data includes at least a SOC or a SOH of the at least one battery; the first broker caches the battery data of at least a first functional module among the plurality of functional modules based on an instruction from the first controller, and shares the battery data among the plurality of functional modules; In response to a failure of the first functional module, causing a second functional module different from the first functional module among the plurality of functional modules to perform the function that had been performed by the first functional module; or When the second functional module can perform a designated function among the acquisition function, the battery rack control function, and the data logging function based on the battery data received from the first functional module, the second functional module is caused to perform the designated function. and relaying the cooperation between the plurality of functional modules by at least one of the above. A method for operating a battery data management device.

5. the battery data management device further includes a second broker that is a device connected to the plurality of functional modules, and a second controller that is a device connected to the second broker; transmitting the battery data cached from at least one of the plurality of functional modules to the second broker by the first broker based on an instruction from the first controller; or The method further comprises a step of transmitting the battery data cached from at least one of the plurality of functional modules to the first broker by the second broker based on an instruction from the second controller; The method of claim 4 , further comprising:

6. a step of controlling, by the first controller, when a failure occurs in the first broker, at least one of the plurality of functional modules communicating battery data with the first broker to communicate battery data with the second broker; or 6. The method for operating a battery data management device according to claim 5, further comprising a step of controlling, by the second controller, when a failure occurs in the second broker, at least one of the plurality of functional modules that communicates battery data with the second broker to communicate battery data with the first broker.

Images