Method for managing battery data and battery management system providing the same

Abstract

The present invention relates to a battery data management method and a battery system that provides the method. The battery management system of the present invention includes a plurality of slave BMSs that each collect and store battery data including status information of a battery module at a predetermined storage period, and a master BMS that receives the battery data and identification data including identification information of the slave BMS from each of the plurality of slave BMSs at the storage period, and maps and stores the battery data and the identification data.

Description

[Technical Field]

[0001] [CROSS-REFERENCE TO RELATED APPLICATIONS] This application claims the benefit of priority based on Korean Patent Application No. 10-2023-0060584, filed May 10, 2023, and all contents disclosed in the documents of said Korean patent application are incorporated herein by reference.

[0002] The present invention relates to a method for managing battery data and a battery management system that provides the method. [Background technology]

[0003] Since batteries used in automobiles are also products, battery manufacturers or distributors provide after-service (A / S) for batteries they sell during the warranty period. After-service (A / S) is a service that provides consumers with services such as repairs, installation, and inspections for sold products at special prices.

[0004] The distributor provides after-sales service (A / S) based on warranty data such as the cumulative number of charge / discharge cycles of the battery, cumulative discharge energy, etc. For example, the distributor may decide that the warranty period will be until the cumulative number of charge / discharge cycles reaches 1,000.

[0005] The quality assurance data is battery data that serves as a basis for determining whether or not to apply after-sales service (A / S), and can be collected and / or calculated by a slave battery management system (Slave BMS) electrically connected to the battery. For example, if a battery system includes multiple battery modules, multiple slave BMSs electrically connected to each of the multiple battery modules can collect and / or calculate multiple pieces of quality assurance data corresponding to each of the multiple battery modules. The collected quality assurance data can be stored in a storage unit of the slave BMS.

[0006] Meanwhile, if a battery module becomes defective or reaches the end of its life, the battery pack consisting of the battery module and slave BMS can be replaced with a new battery pack. Alternatively, only the master BMS (Master Battery Management System, Master BMS) that controls multiple slave BMSs can be replaced. In this case, quality assurance data that reflects the current status must be updated.

[0007] Previously, updating quality assurance data by transferring it to the master BMS involved cumbersome work such as connecting a PC communication cable and running a program to transfer the data. Summary of the Invention [Problem to be solved by the invention]

[0008] The present invention provides a battery data management method that can efficiently store and manage battery data, and a battery management system that provides the method. [Means for solving the problem]

[0009] A battery management system according to one embodiment of the present invention includes a plurality of slave BMSs that each collect and store battery data including status information of a battery module at a predetermined storage period, and a master BMS that receives the battery data and identification data including identification information of the slave BMS from each of the plurality of slave BMSs at the storage period, and maps and stores the battery data and the identification data.

[0010] The battery data may include at least one of information on a total number of charge / discharge cycles of the battery module and a total energy discharged by the battery module.

[0011] When the master BMS receives a signal requesting the battery data from an external system, the master BMS may transmit the stored battery data to the external system.

[0012] When the master BMS receives the battery data transmission request signal, it requests and receives the identification data from each of the plurality of slave BMSs, and when the received identification data matches the stored identification data, it can transmit the stored battery data to the external system.

[0013] If the received identification data does not match the stored identification data, the master BMS may request and receive the battery data from the slave BMS corresponding to the mismatched identification data, and may update the stored battery data to the received battery data.

[0014] The master BMS may transmit battery data stored in the master BMS after an update to the external system.

[0015] When the master BMS receives power from a power source and wakes up, it requests and receives the identification data from each of the plurality of slave BMSs, requests and receives the battery data from at least one slave BMS whose received identification data does not match pre-stored identification data, and updates the stored battery data to the received battery data.

[0016] A battery data management method according to another embodiment of the present invention is a method in which a master BMS manages battery data collected by each of a plurality of slave BMSs electrically connected to a plurality of battery modules and stored in each of the plurality of slave BMSs for each predetermined storage period, the method including the steps of receiving a battery data request signal including status information of the battery module from an external system, and transmitting the battery data received from each of the plurality of slave BMSs for each storage period, mapped with identification data including identification information of the slave BMS, and stored to the external system.

[0017] The battery data may include at least one of information on a total number of charge / discharge cycles of the battery module and a total energy discharged by the battery module.

[0018] The battery data management method may further include, after the step of receiving the battery data request signal, a step of requesting and receiving the identification data from each of the plurality of slave BMSs, and a step of determining whether the received identification data matches the identification data stored in the master BMS. In the step of transmitting to the external system, if the determination results in a match, the battery data stored in the master BMS may be transmitted to the external system.

[0019] The battery data management method may further include, after the step of determining whether the received identification data matches pre-stored identification data, if the determination result shows no match, requesting and receiving the battery data from at least one slave BMS corresponding to the mismatched identification data, and updating the stored battery data to the received battery data, and the transmitting to the external system may transmit the battery data stored in the master BMS to the external system after the updating step.

[0020] According to another embodiment of the present invention, a battery data management method is a method in which a master BMS manages battery data collected by each of a plurality of slave BMSs electrically connected to a plurality of battery modules at predetermined storage intervals and stored in each of the plurality of slave BMSs, the method including the steps of receiving power from a power source and waking up; requesting and receiving identification data including identification information of the slave BMS from each of the plurality of slave BMSs; determining whether the received identification data matches identification data stored in the master BMS; if the determination results in a mismatch, requesting and receiving the battery data from at least one slave BMS corresponding to the mismatched identification data; and updating the battery data stored in the master BMS to the received battery data.

[0021] The battery data may be mapped with the identification data and stored in the master BMS.

[0022] The battery data may include at least one of a total number of charge / discharge cycles of the battery module and a total energy discharged by the battery module. [Effects of the Invention]

[0023] The present invention allows warranty data to be updated to the latest state when a slave BMS or master BMS is replaced, without the need to connect a PC communication cable or run a program for transferring battery data. [Brief explanation of the drawings]

[0024] [Figure 1] FIG. 1 is a diagram illustrating a battery system according to an embodiment. [Figure 2] FIG. 2 is a block diagram illustrating the configuration of the slave BMS of FIG. [Figure 3] FIG. 3 is a block diagram illustrating the configuration of the master BMS of FIG. [Figure 4] FIG. 4 is a conceptual diagram illustrating a state in which battery data is stored in a plurality of slave BMSs and a master BMS according to an embodiment. [Figure 5] FIG. 5 is a conceptual diagram illustrating how battery data is updated when a master BMS is replaced according to one embodiment. [Figure 6] FIG. 6 is a conceptual diagram illustrating a method for updating battery data when a first slave BMS is replaced according to one embodiment. [Figure 7] FIG. 7 is a flowchart illustrating a method in which battery data collected by a slave BMS is stored in a master BMS according to another embodiment. [Figure 8] FIG. 8 is a flowchart illustrating a method for updating battery data stored in a master BMS according to another embodiment. [Figure 9] FIG. 9 is a flowchart illustrating a method for a master BMS to transmit battery data to an external system according to another embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0025] Hereinafter, the embodiments disclosed herein will be described in detail with reference to the accompanying drawings. Identical or similar components will be assigned identical or similar drawing numbers, and redundant descriptions thereof will be omitted. The suffixes "module" and / or "section" for components used in the following description are assigned or used interchangeably solely for the convenience of writing the specification, and do not have any distinct meanings or roles. Furthermore, in describing the embodiments disclosed herein, if it is determined that a detailed description of related publicly known technology may obscure the gist of the embodiments disclosed herein, such a detailed description will be omitted. Furthermore, the accompanying drawings are intended only to facilitate understanding of the embodiments disclosed herein, and should not be construed as limiting the technical ideas disclosed herein, and should be understood to include any modifications, equivalents, or alternatives within the spirit and technical scope of the present invention.

[0026] Terms including ordinal numbers such as "first," "second," etc. may be used to describe various components, but the components are not limited by the terms. The terms are used only to distinguish one component from another.

[0027] When a component is referred to as being "coupled" or "connected" to another component, it should be understood that the component may be directly coupled or connected to the other component, but that there may be other components in between. Conversely, when a component is referred to as being "directly coupled" or "directly connected" to another component, it should be understood that there are no other components in between.

[0028] In this application, the use of terms such as "comprises" or "having" is intended to specify the presence of any feature, number, step, operation, component, part, or combination thereof described in the specification, but should be understood not to preclude the presence or additional possibility of one or more other embodiments, numbers, steps, operations, components, parts, or combinations thereof.

[0029] FIG. 1 is a diagram illustrating a battery system according to one embodiment, FIG. 2 is a block diagram illustrating the configuration of a slave BMS of FIG. 1, FIG. 3 is a block diagram illustrating the configuration of a master BMS of FIG. 1, and FIG. 4 is a conceptual diagram illustrating a state in which battery data is stored in multiple slave BMSs and a master BMS according to one embodiment.

[0030] Referring to FIG. 1, the battery system 1 includes a battery 10, a relay 20, and a battery management system (hereinafter referred to as "BMS") 30.

[0031] The battery 10 may include a plurality of battery modules B_M, each including a plurality of battery cells electrically connected in series and parallel. In some embodiments, the battery cells may be rechargeable secondary batteries. While FIG. 1 illustrates the battery 10 including three battery modules B_M, each including three battery cells connected in series, the present invention is not limited to this. The battery 10 may include a plurality of battery modules B_M, each including various numbers of battery cells connected in series and parallel. Each of the plurality of battery cells may be electrically connected to a slave BMS (hereinafter referred to as "S_BMS") via wiring.

[0032] 1, a battery 10 includes a plurality of battery cells (Cell1-Celln) connected in series and is connected between two output terminals OUT1 and OUT2 of a battery system 1, and a relay 20 is connected between the positive electrode of the battery system 1 and the first output terminal OUT1. The configurations and connections between the configurations shown in FIG. 1 are merely examples, and the present invention is not limited thereto.

[0033] The relay 20 controls the electrical connection between the battery system 1 and the external device. When the relay 20 is turned on, the battery system 1 and the external device are electrically connected to perform charging or discharging, and when the relay 20 is turned off, the battery system 1 and the external device are electrically disconnected. In this case, the external device may be a charger in a charging cycle that supplies power to the battery 10 to charge it, or a load in a discharging cycle that the battery 10 discharges power to the external device.

[0034] The battery management system 30 may include multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) and a master BMS (MA_BMS).

[0035] In FIG. 1, multiple battery modules (B_M1, B_M2, B_M3) are shown as constituting the battery 10, and multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) and a master BMS (MA_BMS) are shown as constituting the battery management system 30, but this is not limiting. For example, the battery module B_M and the slave BMS (S_BMS) may constitute a battery module assembly. In this case, if the battery module B_M needs to be replaced due to aging or other reasons, the entire battery module assembly may be replaced rather than just the battery module B_M. Also, while FIG. 1 shows three slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3), this is not limiting. The battery management system 30 may include various numbers of slave BMSs.

[0036] Hereinafter, a specific slave BMS among multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) will be referred to by the reference symbol "k," and the communication unit, storage unit, and control unit included in the slave BMS (S_BMS_k) will be referred to by the reference symbols "S_k_1, S_k_2, S_k_3," respectively. Also, a battery module electrically connected to a specific slave BMS (S_BMS_k) will be referred to by the reference symbol "B_Mk," and the battery data collected by a specific slave BMS (S_BMS_k) and the ID of the slave BMS (S_BMS_k) will be referred to by the reference symbols "W_data_k" and "ID_k," respectively.

[0037] The slave BMS (S_BMS_k) may monitor the battery module B_Mk and collect battery data including information on the status of the battery module B_Mk. According to one embodiment, the battery data may include information such as the cell voltage, cell current, and cell temperature of each of the plurality of battery cells. According to another embodiment, the battery data may further include warranty data that serves as a basis for a warranty period, which is a period during which maintenance and repairs for the battery module B_Mk are guaranteed.

[0038] For example, the manufacturer may designate a battery module B_Mk as eligible for free repairs until it reaches 4,000 charge / discharge cycles or 200 MWh of cumulative discharge energy, etc. In this case, the charge / discharge cycles and cumulative discharge energy may correspond to quality assurance data.

[0039] Referring to FIG. 2, a slave BMS (S_BMS_k) may include a communication unit S_k_1, a storage unit S_k_2, and a control unit S_k_3.

[0040] The communication unit S_k_1 can communicate with the master BMS (MA_BMS) using the CAN communication method to transmit battery data or receive various signals. For example, the communication unit S_k_1 can transmit battery data stored in the storage unit S_k_2 and identification data including identification information ID_k of the slave BMS (S_BMS_k) to the master BMS (MA_BMS) under the control of the control unit S_k_3. As another example, the communication unit S_k_1 can receive a signal requesting battery data or a signal requesting identification information ID_k from the master BMS (MA_BMS).

[0041] The storage unit S_k_2 may store battery data collected by the control unit S_k_3 at predetermined intervals. The storage unit S_k_2 may store identification data including identification information ID_k of the slave BMS (S_BMS_k). For example, the identification data may be generated when the battery module assembly is manufactured and stored in the storage unit S_k_2.

[0042] The control unit S_k_3 may monitor the slave BMS (S_BMS_k), collect battery data, and store the collected data in the storage unit S_k_2. According to an embodiment, the control unit S_k_3 may transmit the battery data and / or the identification information ID_k stored in the storage unit S_k_2 to the master BMS (MA_BMS) via the communication unit S_k_1 at the request of the master BMS (MA_BMS).

[0043] The master BMS (MA_BMS) can generally control the plurality of slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3). According to an embodiment, the master BMS (MA_BMS) can store battery data collected by each of the plurality of slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) and transmit the stored battery data to an external system (e.g., an automobile system) upon request from the external system. That is, the battery data may be stored not only in the plurality of slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) but also in the master BMS (MA_BMS). In this case, the external system may include an automobile system in which the battery system 1 is installed, an energy storage system (ESS), etc.

[0044] Referring to FIG. 3, the master BMS (MA_BMS) may include a master communication unit MA_1, a master storage unit MA_2, and a master control unit MA_3.

[0045] The master communication unit MA_1 can communicate with a plurality of slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) and an external system. For example, the master communication unit MA_1 can receive a battery data request signal transmitted from an external system. As another example, the master communication unit MA_1 can receive battery data and / or a plurality of identification data including identification information ID_k of each of the plurality of slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) from each of the plurality of slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3).

[0046] The master storage unit MA_2 may store battery data transmitted from each of the plurality of slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) and a plurality of identification data including identification information ID_k of each of the plurality of slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3). According to an embodiment, the master storage unit MA_2 may store the battery data and identification data corresponding to each of the plurality of slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) in a mapped manner.

[0047] The master control unit MA_3 can integrate and manage battery data collected by each of the plurality of slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3). According to an embodiment, the master control unit MA_3 can manage the battery data stored in each of the plurality of slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) so that the state of the battery data stored in the master storage unit MA_2 is the same.

[0048] For example, referring to FIG. 4, the first slave BMS (S_BMS_1) may store first battery data W_data_1, the second slave BMS (S_BMS_2) may store second battery data W_data_2, and the third slave BMS (S_BMS_3) may store third battery data W_data_3. According to an embodiment, the master BMS (MA_BMS) may store the first battery data W_data_1 mapped to first identification data including first identification information ID_1. The master BMS (MA_BMS) may store the second battery data W_data_2 mapped to second identification data including second identification information ID_2. The master BMS (MA_BMS) may store the third battery data W_data_3 mapped to third identification data including third identification information ID_3. At this time, the identification information of the first slave BMS (S_BMS_1), the second slave BMS (S_BMS_2), and the third slave BMS (S_BMS_3) are first identification information ID_1, second identification information ID_2, and third identification information ID_3, respectively.

[0049] Hereinafter, a method for managing battery data by the master control unit MA_3 will be described in detail with reference to FIGS.

[0050] FIG. 5 is a conceptual diagram illustrating a method for updating battery data when a master BMS is replaced according to an embodiment, and FIG. 6 is a conceptual diagram illustrating a method for updating battery data when a first slave BMS is replaced according to an embodiment.

[0051] 1 and 5, it is assumed that the master BMS (MA_BMS) is replaced with a new master BMS (MA_BMS*) due to a failure or a deterioration in functionality of the master BMS (MA_BMS). At this time, the new master BMS (MA_BMS*) may not store the identification data of each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3). Furthermore, the new master BMS (MA_BMS*) may set the battery data stored in each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) to an initial value (0).

[0052] The new master BMS (MA_BMS*) can request battery data and identification data from each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3). The new master BMS (MA_BMS*) can map the battery data and identification data received from each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) and store the mapped data in the master storage unit MA_2*.

[0053] Specifically, the new master BMS (MA_BMS*) can request and receive the first battery data W_data_1 and the first identification data ID_1 from the first slave BMS (S_BMS_1), map the first battery data W_data_1 and the first identification data ID_1, and store them in the master storage unit MA_2*. The new master BMS (MA_BMS*) can also request and receive the second battery data W_data_2 and the second identification data ID_2 from the second slave BMS (S_BMS_1), map the second battery data W_data_2 and the second identification data ID_2, and store them in the master storage unit MA_2*. The new master BMS (MA_BMS*) can request and receive the third battery data W_data_3 and the third identification data ID_3 from the third slave BMS (S_BMS_3), map the third battery data W_data_3 and the third identification data ID_3, and store them in the master storage unit MA_2*. For example, referring to FIG. 5, the first battery data W_data_1, the second battery data W_data_2, and the third battery data W_data_3 can be assumed to be 10, 8, and 5, respectively.

[0054] The master storage unit MA_2* can be updated with multiple battery data items with an initial value (0) mapped to each of the multiple identification information items ID_1, ID_2, and ID_3. This allows multiple battery data items that reflect the current status of each of the multiple slave BMSs (S_BMS_1, S_BMS_2, and S_BMS_3) to be stored in the new master BMS (MA_BMS*) without the need for cumbersome tasks such as connecting a PC communication cable or running a program for data transfer.

[0055] 1 and 6, for example, when the first battery module B_M1 is replaced due to a malfunction, a deterioration in functionality, or the like, it is assumed that the first slave BMS (S_BMS_1) electrically connected to the first battery module B_M1 is also replaced along with the first battery module B_M1. It is also assumed that the first battery data W_data_1 before the replacement is 10, and the new first battery data W_data_1* is 0. In other words, because the new first battery module B_M1* has no operating history, the battery data stored in the new first slave BMS (S_BMS_1*) may be set to an initial value (0).

[0056] The master BMS (MA_BMS) can update the first battery data W_data_1 and identification data ID_1 of the first slave BMS (S_BMS_1) before replacement to new first battery data W_data_1* and new first identification data ID_1* of the new first slave BMS (S_BMS_1*).

[0057] Specifically, the master BMS (MA_BMS) requests and receives new first battery data W_data_1* and new first identification data ID_1* from the new first slave BMS (S_BMS_1*). The master BMS (MA_BMS) can map the new first battery data W_data_1* and the new first identification data ID_1* and store them in the master storage unit MA_2.

[0058] FIG. 7 is a flowchart illustrating a method in which battery data collected by a slave BMS is stored in a master BMS according to another embodiment.

[0059] Referring to FIG. 7, first, the master BMS (MA_BMS) determines whether the battery data storage period set according to a predetermined criterion has arrived (S110).

[0060] The storage period may correspond to a period during which the slave BMS (S_BMS_k) collects battery data including status information of the battery module B_Mk. For example, the storage period may correspond to a time point at which a charge and discharge cycle of the battery 10 ends. However, the storage period is not limited thereto, and the master BMS (MA_BMS) may set the storage period according to various criteria.

[0061] If the result of the determination is that the storage period has not arrived (S110; No), the master BMS (MA_BMS) continues to count the time.

[0062] If it is determined that the storage period has arrived (S110; Yes), the master BMS (MA_BMS) requests and receives battery data W_data_k and identification data ID_k from each of the slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) (S120).

[0063] At each storage period, each of the plurality of slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) collects and stores battery data, and, upon request from the master BMS (MA_BMS), each of the plurality of slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) can transmit the collected battery data W_data_k and identification data ID_k to the master BMS (MA_BMS).

[0064] According to an embodiment, the battery data may include at least one of the total number of charge / discharge cycles of the battery module B_Mk and the total energy discharged by the battery module B_Mk. For example, when the charge and discharge cycles of the battery 10 are completed, each of the plurality of slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) may count the cycles and transmit the total number of cycles to the master BMS (MA_BMS). As another example, when the discharge cycles of the battery 10 are completed, each of the plurality of slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) may calculate the total energy discharged by the battery module B_Mk and transmit the total energy value to the master BMS (MA_BMS).

[0065] Next, the master BMS (MA_BMS) maps the battery data W_data_k and the identification data ID_k corresponding to each of the plurality of slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) and stores them in the master storage unit MA_2 (S130).

[0066] FIG. 8 is a flowchart illustrating a method for updating battery data stored in a master BMS according to another embodiment.

[0067] Referring to FIG. 8, first, when the master BMS (MA_BMS) receives power from a power source and wakes up, it requests and receives identification data ID_k from each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) (S210, S220).

[0068] Next, the master BMS (MA_BMS) determines whether the identification data received from each of the plurality of slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) matches the identification data previously stored in the master storage unit MA_2 (S230).

[0069] For example, if the master BMS (MA_BMS) or at least one slave BMS (S_BMS_k) among the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) is replaced, the state of the battery data W_data_k of the slave BMS (S_BMS_k) stored in the master storage unit MA_2 may differ from the state of the battery data W_data_k stored in the slave BMS (S_BMS_k).The master BMS (MA_BMS) can check the real-time state of the battery module B_Mk installed in the battery 10 by determining whether the identification data ID_k matches each time it wakes up.

[0070] If the determination result is a match (S230; YES), the master BMS (MA_BMS) ends the process without taking any additional follow-up measures.

[0071] If the determination result is no match (S230; NO), the master BMS (MA_BMS) requests and receives battery data W_data_k from at least one slave BMS (S_BMS_k) whose identification data ID_k does not match (S240).

[0072] 6, for example, among the first to third slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3), the slave BMS (S_BMS_k) with the mismatched identification data ID_k is assumed to be the first slave BMS (S_BMS_1). Then, the master BMS (MA_BMS) can request new first battery data W_data_1* and new first identification data ID_1* from the new first slave BMS (S_BMS_1*).

[0073] Next, the master BMS (MA_BMS) updates the master storage unit MA_2 with the stored battery data and the received battery data (S250).

[0074] 6, the master BMS (MA_BMS) may delete the first battery data W_data_1 previously stored in the master storage unit MA_2, store new first battery data W_data_1*, and update the master storage unit MA_2. In this case, the master BMS (MA_BMS) may map the new first battery data W_data_1* to new first identification data ID_1* and store the mapped data in the master storage unit MA_2.

[0075] FIG. 9 is a flowchart illustrating a method for a master BMS to transmit battery data to an external system according to another embodiment.

[0076] Referring to FIG. 9, first, the master BMS (MA_BMS) receives a battery data request signal from an external system (S310).

[0077] The external system (not shown) may be a host system in which the battery system 1 is installed. For example, the external system may include a system in which the battery 10 and the battery management system BMS are installed, such as a vehicle system, an energy storage system (ESS), or an electric motorcycle. The battery data request signal may be a signal in which the external system requests battery data from the battery system.

[0078] The battery data may include information such as the cell voltage, cell current, and cell temperature of each of the plurality of battery cells. According to an embodiment, the battery data may further include warranty data that serves as a reference for a warranty period, which is a period during which maintenance and repair of the battery module B_Mk is guaranteed.

[0079] Next, the master BMS (MA_BMS) requests and receives identification data from each of the slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) (S320).

[0080] The identification data may include identification information ID_k of the slave BMS (S_BMS_k). The identification information ID_k may be generated when the battery module assembly is manufactured and stored in the storage unit S_k_2 of the slave BMS (S_BMS_k). For example, the identification data of each of the multiple slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) may include different identification information ID_k.

[0081] Next, the master BMS (MA_BMS) determines whether the identification data stored in advance in the master storage unit MA_2 matches the received identification data (S330).

[0082] Next, if the pre-stored identification data matches the received identification data (S330; Yes), the master BMS (MA_BMS) transmits the battery data pre-stored in the master storage unit MA_2 to the external system (S360).

[0083] Next, if the pre-stored identification data does not match the received identification data (S330; No), the master BMS (MA_BMS) requests and receives battery data from the slave BMS corresponding to the mismatched identification data (S340).

[0084] Next, the master BMS (MA_BMS) updates the battery data previously stored in the master storage unit MA_2 to the received battery data (S350).

[0085] Next, the master BMS (MA_BMS) transmits the battery data stored in the master storage unit MA_2 after the update to an external system (S360).

[0086] At each predetermined storage period, the slave BMS (S_BMS_k) can store the collected battery data in the storage unit S_k_2 of the slave BMS (S_BMS_k) and transmit it to the master BMS (MA_BMS). For example, at each predetermined period, the battery data collected by each of the plurality of slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) may be simultaneously stored in the plurality of slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) and the master BMS (MA_BMS).

[0087] For example, if the master BMS (MA_BMS) or at least one slave BMS (S_BMS_k) among the plurality of slave BMSs (S_BMS_1, S_BMS_2, S_BMS_3) is replaced, the state of the battery data W_data_k of the slave BMS (S_BMS_k) stored in the master storage unit MA_2 may differ from the state of the battery data W_data_k stored in the slave BMS (S_BMS_k). According to an embodiment, the master BMS (MA_BMS) may determine whether the identification data match each time it receives a battery data request signal. Then, the master BMS (MA_BMS) may transmit battery data including accurate information on the current state of the plurality of battery modules (B_M1, B_M2, B_M3) included in the battery 10 to an external system.

[0088] Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited to these, and various modifications and improvements made by those skilled in the art to which the present invention pertains also fall within the scope of the present invention.

Claims

1. a plurality of slave BMSs that respectively collect and store battery data including status information of the battery modules at predetermined storage intervals; a master BMS that receives the battery data and identification data including identification information of the slave BMSs from each of the plurality of slave BMSs for each storage period, and maps and stores the battery data and the identification data; a battery management system, including:

2. The battery data is The battery management system of claim 1 , further comprising at least one of information of a total number of charge / discharge cycles of the battery module and a total energy discharged by the battery module.

3. The master BMS: The battery management system of claim 1 or 2, wherein when a signal requesting the battery data is received from an external system, the stored battery data is transmitted to the external system.

4. The master BMS:

4. The battery management system of claim 3, wherein, when the battery data transmission request signal is received, the battery management system requests and receives the identification data from each of the plurality of slave BMSs, and when the received identification data matches the stored identification data, the battery management system transmits the stored battery data to the external system.

5. The master BMS:

5. The battery management system of claim 4, wherein, if the received identification data does not match the stored identification data, the battery data is requested from a slave BMS corresponding to the mismatched identification data, and the slave BMS receives the battery data, and the stored battery data is updated to the received battery data.

6. The master BMS: The battery management system of claim 5 , wherein the battery data stored in the master BMS is transmitted to the external system after an update.

7. The master BMS:

2. The battery management system of claim 1, wherein, upon receiving power from a power source and waking up, the battery management system requests and receives the identification data from each of the plurality of slave BMSs, requests and receives the battery data from at least one slave BMS whose received identification data does not match pre-stored identification data, and updates the stored battery data to the received battery data.

8. A method for managing battery data collected by each of a plurality of slave BMSs electrically connected to a plurality of battery modules at predetermined storage intervals and stored in each of the plurality of slave BMSs, by a master BMS, comprising: receiving a battery data request signal including status information of the battery module from an external system; transmitting, to the external system, battery data received from each of the plurality of slave BMSs for each storage period, mapped with identification data including identification information of the slave BMS, and stored; a battery data management method,

9. The battery data is 9. The battery data management method according to claim 8, wherein the information includes at least one of a total number of charge / discharge cycles of the battery module and a total energy discharged by the battery module.

10. After receiving the battery data request signal, The method further includes the steps of requesting and receiving the identification data from each of the plurality of slave BMSs, and determining whether the received identification data matches identification data stored in the master BMS, The step of transmitting to the external system includes: The battery data management method of claim 8 , wherein if the determination result is a match, the stored battery data in the master BMS is transmitted to the external system.

11. After the step of determining whether the received identification data matches the pre-stored identification data, If the determination result shows no match, the method further includes the steps of requesting and receiving the battery data from at least one slave BMS corresponding to the mismatched identification data, and updating the stored battery data to the received battery data, The step of transmitting to the external system includes: The battery data management method according to claim 10, wherein the battery data stored in the master BMS is transmitted to the external system after the updating step.

12. A method for managing battery data collected by each of a plurality of slave BMSs electrically connected to a plurality of battery modules at predetermined storage intervals and stored in each of the plurality of slave BMSs, by a master BMS, comprising: receiving power from a power source and waking up; requesting and receiving identification data including identification information of the slave BMS from each of the plurality of slave BMSs; determining whether the received identification data matches identification data stored in the master BMS; If the determination result indicates a mismatch, requesting and receiving the battery data from at least one slave BMS corresponding to the mismatched identification data; updating battery data stored in the master BMS with the received battery data; a battery data management method,

13. The battery data is The battery data management method according to claim 12, wherein the identification data is mapped to the master BMS and stored therein.

14. The battery data is 13. The battery data management method of claim 12, wherein the data includes at least one of a total number of charge / discharge cycles of the battery module and a total energy discharged by the battery module.

Images