Battery data management method and battery management system providing same

Abstract

The present disclosure relates to a battery data management method and a battery management system (BMS) providing the same, and the BMS includes: a plurality of slave BMSs each configured to collect and store battery data including state information of a battery module for each predetermined storage period; and a master BMS configured to receive, for each storage period, battery data and identification data including identification information of each of the plurality of slave BMSs from each of the plurality of slave BMSs, and map and store the battery data and the identification data.

Description

Technical Field

[0001] Cross - Reference to Related Applications

[0002] This application claims priority and the benefit of Korean Patent Application No. 10-2023-0060584, filed with the Korean Intellectual Property Office on May 10, 2023, the entire content of which is incorporated herein by reference.

[0003] The present disclosure relates to a battery data management method and a battery management system providing the same. Background Art

[0004] Since batteries used in vehicles and the like are also products, battery manufacturers or sellers provide after-service (A / S) for the sold batteries during the warranty period. A / S is a service that provides services such as repair, installation, inspection, etc. of the sold product to consumers at a special price or the like.

[0005] The seller provides A / S based on warranty data such as the cumulative count of charge / discharge cycles of the battery, cumulative discharge energy, etc. For example, the seller can set the warranty period until the cumulative count of charge / discharge cycles reaches 1000 times.

[0006] Warranty data is battery data that serves as the basis for determining the application of A / S, and can be collected and / or calculated by a slave battery management system (BMS) electrically connected to the battery. For example, when a battery system includes a plurality of battery modules, a plurality of warranty data respectively corresponding to the plurality of battery modules can be collected and / or calculated by a plurality of slave BMSs respectively electrically connected to the plurality of battery modules. The collected warranty data can be stored in the storage unit of the slave BMS.

[0007] Meanwhile, when a defect occurs in a battery module or when the life of the battery module ends, the battery pack including the battery module and the slave BMS can be replaced with a new battery pack. Alternatively, only the master BMS that controls the plurality of slave BMSs can be newly replaced. In this case, it is necessary to update the warranty data reflecting the current state.

[0008] In the related art, updating the warranty data by transmitting the warranty data to the master BMS involves cumbersome tasks such as connecting a PC communication cable and executing a program for data transmission. Summary of the Invention

[0009] [Technical Problem]

[0010] The present disclosure attempts to provide a battery data management method capable of efficiently storing and managing battery data and a battery management system providing the same.

[0011] [Technical Solution]

[0012] According to one aspect of the present disclosure, a battery management system (BMS) includes: a plurality of slave BMSs, each slave BMS being configured to collect and store battery data including status information of a battery module for each predetermined storage period; and a master BMS configured to receive the battery data and identification data including identification information of each of the plurality of slave BMSs from each of the plurality of slave BMSs for each storage period, and map and store the battery data and the identification data.

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

[0014] The master BMS may send the stored battery data to an external system when a request signal for the battery data is received from the external system.

[0015] The master BMS may request and receive the identification data from each of the plurality of slave BMSs when a transmission request signal for the battery data is received, and send the stored battery data to the external system when the received identification data matches the stored identification data.

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

[0017] The master BMS may send the battery data stored in the master BMS to the external system after the update.

[0018] The master BMS may request and receive the identification data from each of the plurality of slave BMSs when powered on and awakened from a power source, request and receive the battery data from at least one of the slave BMSs whose received identification data does not match the previously stored identification data, and update the stored battery data with the received battery data.

[0019] According to another aspect of the present disclosure, a battery data management method executed by a master BMS manages battery data collected and stored in each of a plurality of slave BMSs for each predetermined storage period by each of the plurality of slave BMSs electrically connected to a plurality of battery modules. The battery data management method includes: receiving a request signal for battery data from an external system, the battery data including status information of each of the plurality of battery modules; and sending battery data to the external system, the battery data being received from each of the plurality of slave BMSs for each storage period, mapped to identification data including identification information of each of the plurality of slave BMSs, and stored.

[0020] The battery data may include information on at least one of the total number of charge / discharge cycles of each of the plurality of battery modules and the total energy discharged from each of the plurality of battery modules.

[0021] The battery data management method may further include: after receiving the request signal for battery data, requesting and receiving identification data from each of the plurality of slave BMSs, and determining whether the received identification data matches the identification data stored in the master BMS, and sending to the external system may include: when it is determined that the received identification data matches the identification data, sending the battery data stored in the master BMS to the external system.

[0022] The battery data management method may further include: after determining whether the received identification data matches the previously stored identification data, when it is determined that the received identification data does not match the identification data, requesting and receiving 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 sending to the external system may include sending the battery data stored in the master BMS to the external system after the update.

[0023] According to another aspect of the present disclosure, a battery data management method executed by a master BMS manages battery data collected and stored in each of a plurality of slave BMSs for each predetermined storage period by each of the plurality of slave BMSs electrically connected to a plurality of battery modules. The battery data management method includes: receiving power from a power source and waking up; requesting and receiving identification data including identification information of each of the plurality of slave BMSs from each of the plurality of slave BMSs; determining whether the received identification data matches the identification data stored in the master BMS; when it is determined that the received identification data does not match the identification data, requesting and receiving battery data from at least one slave BMS corresponding to the non-matching identification data; and updating the battery data stored in the master BMS to the received battery data.

[0024] The battery data can be mapped to the identification data and stored in the master BMS.

[0025] The battery data may include information on at least one of the total number of charge / discharge cycles of each of the plurality of battery modules and the total energy discharged from each of the plurality of battery modules.

[0026] [Advantageous Effects]

[0027] In the present disclosure, when the slave BMS or the master BMS is replaced, the warranty data can be updated to the latest state without connecting a PC communication cable and executing a program for battery data transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 is a diagram illustrating a battery system according to an embodiment.

[0029] Figure 2 is a diagram illustrating Figure 1 the configuration of a slave battery management system (BMS).

[0030] Figure 3 is a diagram illustrating Figure 1 the configuration of the master BMS.

[0031] Figure 4 is a conceptual view illustrating a state in which battery data is stored in a plurality of slave BMSs and a master BMS according to an embodiment.

[0032] Figure 5 is a conceptual view illustrating a method of updating battery data when the master BMS is replaced according to an embodiment.

[0033] Figure 6It is a conceptual view for explaining a method of updating battery data when a first slave BMS is replaced according to an embodiment.

[0034] Figure 7 It is a flowchart illustrating a method of storing battery data collected by a slave BMS in a master BMS according to another embodiment.

[0035] Figure 8 It is a flowchart illustrating a method of updating battery data stored in a master BMS according to another embodiment.

[0036] Figure 9 It is a flowchart illustrating a method of a master BMS sending battery data to an external system according to another embodiment. Detailed Description of the Embodiment

[0037] Hereinafter, embodiments disclosed in the present specification will be described in detail with reference to the accompanying drawings. However, the same or similar components are given the same or similar reference numerals, and redundant descriptions thereof will be omitted. The suffixes “module” and / or “part” of the components used in the following description are given or mixed only for convenience of writing the specification, and do not have meanings or roles that are different from each other by themselves. In addition, when determining that a detailed description of related known technologies may obscure the gist of the embodiments disclosed in the present specification, the detailed description thereof will be omitted. In addition, the drawings are only for easy understanding of the embodiments disclosed in the present specification, and do not limit the technical concept disclosed in the present specification, and should be understood to include all changes, equivalents, or substitutions included in the spirit and scope of the present disclosure.

[0038] Terms including ordinal numbers such as first and second may be used to describe various components, but the components are not limited by the terms. The terms are only for the purpose of distinguishing one component from another.

[0039] It will be understood that when a component is referred to as being “connected to” or “coupled to” another component, the component may be connected or coupled to the other component, or there may be an intermediate component. In contrast, when a component is referred to as being “directly connected to” or “directly coupled to” another component, there is no intermediate component.

[0040] It will also be understood that when used in this specification, the terms “include” and / or “comprise” specify the presence of the described features, integers, steps, operations, components, and / or parts, but do not preclude the presence or addition of one or more other features, integers, steps, operations, components, parts, and / or combinations thereof.

[0041] Figure 1 It is a diagram illustrating a battery system according to an embodiment. Figure 2 It is illustrated Figure 1Block diagram of the configuration of the slave battery management system (BMS). Figure 3 illustrates Figure 1 Block diagram of the configuration of the main BMS. Figure 4 is a conceptual view showing the state in which battery data is stored in multiple slave BMSs and the main BMS according to an embodiment.

[0042] Referring Figure 1 , the battery system 1 includes a battery 10, a relay 20, and a BMS 30.

[0043] The battery 10 may include a plurality of battery modules B_M, and the battery module B_M includes a plurality of battery cells electrically connected in series and in parallel. In one embodiment, the battery cell may be a rechargeable secondary battery. Figure 1 The battery 10 shown includes three battery modules B_M, and the battery module B_M includes three battery cells connected in series, but the present disclosure is not limited thereto. The battery 10 may include a plurality of battery modules B_M, and the battery module B_M includes various numbers of battery cells connected in series and in parallel. Each of the plurality of battery cells may be electrically connected to a slave BMS (hereinafter referred to as 'S_BMS') through wiring.

[0044] In Figure 1 , the battery 10 includes a plurality of battery cells Cell1-Celln connected in series and connected between two output terminals OUT1 and OUT2 of the battery system 1, and the relay 20 is connected between the positive electrode of the battery system 1 and the first output terminal OUT1. Figure 1 The components shown and the connection relationships between the components are examples, and the present disclosure is not limited thereto.

[0045] The relay 20 controls the electrical connection between the battery system 1 and an external device. When the relay 20 is turned on, the battery system 1 and the external device are electrically connected to each other to perform charging or discharging, and when the relay 20 is turned off, the battery system 1 and the external device are electrically separated from each other. In this regard, the external device may be a charger in a charging cycle in which the battery 10 is charged by supplying power to the battery 10, and may be a load in a discharging cycle in which the battery 10 discharges power to the external device.

[0046] The BMS 30 may include a plurality of slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3 and a main BMS MA_BMS.

[0047] Figure 1It shows that a plurality of battery modules B_M1, B_M2, and B_M3 constitute a battery 10, and a plurality of slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3 and a master BMS MA_BMS constitute a battery management system 30, but the present disclosure is not limited thereto. For example, a battery module B_M and a slave BMS S_BMS can constitute a battery module assembly. In this regard, when the battery module B_M needs to be replaced due to aging or the like, not only the battery module B_M is replaced, but also the battery module assembly can be replaced as a whole. In addition, Figure 1 It shows three slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3, but the present disclosure is not limited thereto. The BMS 30 can include various numbers of slave BMSs.

[0048] Hereinafter, when indicating a specific slave BMS among the plurality of slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3, the reference numeral "k" is used, and the communication unit, storage unit, and control unit included in the corresponding slave BMS S_BMS_k are respectively denoted by the reference numerals "S_k_1, S_k_2, and S_k_3". In addition, when indicating a battery module electrically connected to a specific slave BMS S_BMS_k, the reference numeral "B_Mk" is used, and the battery data collected by the specific slave BMS S_BMS_k and the ID of the slave BMS S_BMS_k are respectively denoted by the reference numerals "W_data_k" and "ID_k".

[0049] The slave BMS S_BMS_k can monitor the battery module B_Mk and collect battery data including information about the state of the battery module B_Mk. According to one embodiment, the battery data may include information such as the cell voltage, cell current, cell temperature, etc. of each of the plurality of battery cells. According to another embodiment, the battery data may further include warranty data, which is a reference for the warranty period, and the warranty period is a period for ensuring the maintenance and repair of the battery module B_Mk.

[0050] For example, the battery module B_Mk can be set by the manufacturer to allow free repair or the like until 4000 charge / discharge cycles or 200 MWh of cumulative discharge energy are reached. In this regard, the charge / discharge cycles and the cumulative discharge energy can correspond to the warranty data.

[0051] Reference Figure 2 , the slave BMS S_BMS_k can include a communication unit S_k_1, a storage unit S_k_2, and a control unit S_k_1.

[0052] The communication unit S_k_1 can communicate with the main BMS MA_BMS by using the CAN communication method to send battery data or receive various signals. For example, the communication unit S_k_1 can, under the control of the control unit S_k_1, send the battery data stored in the storage unit S_k_2 and the identification data including the identification information ID_k of the BMS S_BMS_k to the main BMS MA_BMS. For another example, the communication unit S_k_1 can receive a request signal for battery data or a request signal for the identification information ID_k from the main BMS MA_BMS.

[0053] The storage unit S_k_2 can store the battery data collected by the control unit S_k_1 every predetermined period. The storage unit S_k_2 can store the identification data including the identification information ID_k of the BMS S_BMS_k. For example, the identification data can be generated and stored in the storage unit S_k_2 when manufacturing the battery module assembly.

[0054] The control unit S_k_1 can monitor the BMS S_BMS_k, collect battery data, and store the battery data in the storage unit S_k_2. According to one embodiment, the control unit S_k_1 can, upon request of the main BMS MA_BMS, send the battery data and / or the identification information ID_k stored in the storage unit S_k_2 to the main BMS MA_BMS through the communication unit S_k_1.

[0055] The main BMS MA_BMS can generally control multiple slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3. According to one embodiment, the main BMS MA_BMS can store the battery data collected by each of the multiple slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3, and when an external system (e.g., a vehicle system, etc.) requests battery data, send the stored battery data to the external system. That is, the battery data can be stored not only in the multiple slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3, but also in the main BMS MA_BMS. In this regard, the external system can include a vehicle system in which the battery system 1 is installed, an energy storage system (ESS), etc.

[0056] Reference Figure 3 , the main BMS MA_BMS can include a main communication unit MA_1, a main storage unit MA_2, and a main control unit MA_3.

[0057] The main communication unit MA_1 can communicate with multiple slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3, as well as an external system. For example, the main communication unit MA_1 can receive a request signal for battery data sent from the external system. For another example, the main communication unit MA_1 can receive battery data and / or multiple identification data including identification information ID_k of each of the multiple slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3 from each of the multiple slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3.

[0058] The main storage unit MA_2 can store the battery data sent from each of the multiple slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3 and the multiple identification data including the identification information ID_k of each of the multiple slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3. According to one embodiment, the main storage unit MA_2 can map and store the battery data and the identification data corresponding to each of the multiple slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3.

[0059] The main control unit MA_3 can integrate and manage the battery data collected from each of the multiple slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3. According to one embodiment, the main control unit MA_3 can manage the status of the battery data stored in each of the multiple slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3 to be the same as the status of the multiple battery data stored in the main storage unit MA_2.

[0060] For example, referring to Figure 4, the first slave BMS S_BMS_1 can store the first battery data W_data_1, the second slave BMS S_BMS_2 can store the second battery data W_data_2, and the third slave BMS S_BMS_3 can store the third battery data W_data_3. According to one embodiment, the first battery data W_data_1 and the first identification data including the first identification information ID_1 can be mapped and stored in the master BMS MA_BMS. The second battery data W_data_2 and the second identification data including the second identification information ID_2 can be mapped and stored in the master BMS MA_BMS. The third battery data W_data_3 and the third identification data including the third identification information ID_3 can be mapped and stored in the master BMS MA_BMS. In this regard, 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 the first identification information ID_1, the second identification information ID_2, and the third identification information ID_3, respectively.

[0061] Hereinafter, with reference to Figure 5 and Figure 6 a method of managing battery data performed by the master control unit MA_3 will be described in detail.

[0062] Figure 5 is a conceptual view illustrating a method of updating battery data when the master BMS is replaced according to one embodiment. Figure 6 is a conceptual view for explaining a method of updating battery data when the first slave BMS is replaced according to one embodiment.

[0063] With reference to Figure 1 and Figure 5 , for example, assume that due to a failure and functional degradation of the master BMS MA_BMS, a new master BMS is used to replace the master BMS MA_BMS. In this regard, the new master BMS may not store the identification data of each of the multiple slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3. In addition, the battery data stored in each of the multiple slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3 can be set to the initial value (0) in the new master BMS .

[0064] The new master BMS can request battery data and identification data from each of the multiple slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3. The new master BMS It can map the battery data and identification data received from each of multiple slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3, and store the battery data and identification data in the main storage unit therein.

[0065] Specifically, the new master BMS can request and receive first battery data W_data_1 and 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 the first battery data W_data_1 and the first identification data ID_1 in the main storage unit therein. Additionally, the new master BMS can request and receive second battery data W_data_2 and 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 the second battery data W_data_2 and the second identification data ID_2 in the main storage unit therein. The new master BMS can request and receive third battery data W_data_3 and 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 the third battery data W_data_3 and the third identification data ID_3 in the main storage unit therein. For example, referring to Figure 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.

[0066] The main storage unit can be updated with multiple battery data, where an initial value of 0 is mapped to each of the multiple identification information ID_1, ID_2, and ID_3. Then, multiple battery data reflecting the current state of each of the multiple slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3 can be stored in the new master BMS without cumbersome tasks such as connecting a PC communication cable or executing a program for data transmission.

[0067] Referring to Figure 1 and Figure 6, for example, when the first battery module B_M1 is replaced due to its failure or functional degradation, it is assumed that the first slave BMS S_BMS_1 electrically connected to the first battery module B_M1 is also replaced together with the first battery module B_M1. In addition, it is assumed that the first battery data W_data_1 before replacement is 10, and the new first battery data is 0. That is, since the new first battery module has no operation history, the battery data stored in the new first slave BMS can be set to the initial value (0).

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

[0069] Specifically, the master BMS MA_BMS requests and receives the new first battery data and the new first identification data from the new first slave BMS . The master BMS MA_BMS can map the new first battery data and the new first identification data , and store the new first battery data and the new first identification data in the main storage unit MA_2.

[0070] Figure 7 is a flowchart illustrating a method of storing battery data collected by a slave BMS in a master BMS according to another embodiment.

[0071] Referring to Figure 7 , first, the master BMS MA_BMS determines whether the storage period of the battery data set according to a predetermined criterion has been reached (S110).

[0072] The storage period may correspond to the period during which the slave BMS S_BMS_k collects battery data including the status information of the battery module B_Mk. For example, the storage period may correspond to the time when the charge and discharge cycle of battery 10 ends. However, the present disclosure is not limited thereto, and the storage period of the master BMS MA_BMS can be set according to various criteria.

[0073] As a result of the determination, when the storage period has not been reached (No in S110), the master BMS MA_BMS continues to count the time.

[0074] As a determined result, when the storage period (yes in S110) arrives, the main BMS MA_BMS requests and receives battery data W_data_k and identification data ID_k from each of the plurality of slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3 (S120).

[0075] For each storage period, each of the plurality of slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3 collects and stores battery data. In addition, according to the request of the main BMS MA_BMS, each of the plurality of slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3 may send the collected battery data W_data_k and identification data ID_k to the main BMS MA_BMS.

[0076] According to one embodiment, the battery data may include at least one of the total number of charge and discharge cycles of the battery module B_Mk and the total energy discharged from the battery module B_Mk. For example, when the charge and discharge cycles of battery 10 end, each of the plurality of slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3 may count the cycles and send the total number of cycles to the main BMS MA_BMS. For another example, when the discharge cycle of battery 10 ends, each of the plurality of slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3 may calculate the total energy discharged from the battery module B_Mk and send the total energy value to the main BMS MA_BMS.

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

[0078] Figure 8 is a flowchart illustrating a method of updating battery data stored in a main BMS according to another embodiment.

[0079] Reference Figure 8 FIG., first, when the main BMS MA_BMS receives power from a power source and wakes up, the main BMS MA_BMS requests and receives identification data ID_k from each of the plurality of slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3 (S210 and S220).

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

[0081] For example, when the main BMS, MA_BMS, or at least one of the plurality of slave BMSs, S_BMS_1, S_BMS_2, and S_BMS_3, i.e., slave BMS S_BMS_k, is replaced, the battery data W_data_k of slave BMS S_BMS_k stored in the main storage unit MA_2 and the battery data W_data_k stored in slave BMS S_BMS_k may have different states. The main BMS, MA_BMS, can determine whether the identification data ID_k matches whenever it wakes up and can check the status of the battery module B_Mk installed in the battery 10 in real time.

[0082] When the determined result is a match (Yes in S230), the main BMS, MA_BMS, ends without any separate subsequent steps.

[0083] When the determined result is not a match (No in S230), the main BMS, MA_BMS, requests and receives the battery data W_data_k from at least one slave BMS S_BMS_k for which the identification data ID_k does not match (S240).

[0084] For example, referring to Figure 6 , assume that the slave BMS S_BMS_k for which the identification data ID_k does not match among the first to third slave BMSs, S_BMS_1, S_BMS_2, and S_BMS_3, is the first slave BMS S_BMS_1. Then, the main BMS, MA_BMS, can request new first battery data and new first identification data from the new first slave BMS .

[0085] Next, the main BMS, MA_BMS, updates the main storage unit MA_2 by replacing the stored battery data with the received battery data (S250).

[0086] For example, referring to Figure 6 , the main BMS, MA_BMS, can update the main storage unit MA_2 by deleting the first battery data W_data_1 previously stored in the main storage unit MA_2 and storing the new first battery data in the main storage unit MA_2. In this regard, the main BMS, MA_BMS, can map the new first battery data and the new first identification data , and the new first battery data and the new first identification data are stored in the main storage unit MA_2.

[0087] Figure 9 is a flowchart illustrating a method of transmitting battery data from a main BMS to an external system according to another embodiment.

[0088] Refer to Figure 9 , first, the main BMS MA_BMS receives a request signal for battery data from an external system (S310).

[0089] The external system (not shown) may be a higher 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 BMS are installed, such as a vehicle system, an energy storage system (ESS), an electric bicycle, etc. The request signal for battery data may be a signal in which the external system requests battery data from the battery system 1.

[0090] 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 one embodiment, the battery data may further include warranty data, which is a reference for the warranty period, and the warranty period is a period for ensuring the maintenance and repair of the battery module B_Mk.

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

[0092] The identification data may include the identification information ID_k of the slave BMS S_BMS_k. The identification information ID_k may be generated and stored in the storage unit S_k_2 of the slave BMS S_BMS_k during the manufacture of the battery module assembly. For example, the identification data of the plurality of slave BMSS_BMS_1, S_BMS_2, and S_BMS_3 may include different identification information ID_k.

[0093] Next, the main BMS MA_BMS determines whether the previously stored identification data in the main storage unit MA_2 matches the received identification data (S330).

[0094] Next, when the previously stored identification data matches the received identification data (Yes in S330), the main BMSMA_BMS sends the previously stored battery data in the main storage unit MA_2 to the external system (S360).

[0095] Next, when the previously stored identification data does not match the received identification data (No in S330), the master BMS MA_BMS requests and receives battery data from the slave BMS corresponding to the non-matching identification data (S340).

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

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

[0098] For 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 send the battery data to the master BMS MA_BMS. For example, for each predetermined period, the battery data collected from each of the multiple slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3 can be stored in the multiple slave BMSs S_BMS_1, S_BMS_2, S_BMS_3 and the master BMS MA_BMS simultaneously.

[0099] For example, when the master BMS MA_BMS and at least one of the multiple slave BMSs S_BMS_1, S_BMS_2, and S_BMS_3, i.e., the slave BMS S_BMS_k, is replaced, the battery data W_data_k of the slave BMS S_BMS_k stored in the master storage unit MA_2 and the battery data W_data_k stored in the slave BMS S_BMS_k may have different states. According to an embodiment, the master BMS MA_BMS can determine whether the identification data matches whenever a request signal for battery data is received. Then, the master BMS MA_BMS can send the battery data including accurate information about the current state of each of the multiple battery modules B_M1, B_M2, and B_M3 included in the battery 10 to an external system.

[0100] Although the embodiments of the present disclosure have been described in detail above, the scope of the present disclosure is not limited thereto, and various modifications and improvements made by those of ordinary skill in the art to which the present disclosure pertains also fall within the scope of the present disclosure.

Claims

1. A battery management system (BMS) includes: A plurality of slave BMSs, each slave BMS being configured to collect and store battery data including status information of battery modules for each predetermined storage period; And A master BMS, the master BMS being configured to receive the battery data and identification data including identification information of each of the plurality of slave BMSs from each of the plurality of slave BMSs for each storage period, and map and store the battery data and the identification data.

2. The BMS according to claim 1, wherein: The battery data Includes information on at least one of the total number of charge / discharge cycles of the battery module and the total energy discharged from the battery module.

3. The BMS according to claim 1, wherein: The master BMS When receiving a request signal for the battery data from an external system, sends the stored battery data to the external system.

4. The BMS according to claim 3, wherein: The master BMS When receiving a transmission request signal for the battery data, 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, sends the stored battery data to the external system.

5. The BMS according to claim 4, wherein: The master BMS When the received identification data does not match the stored identification data, requests and receives the battery data from the slave BMS corresponding to the non-matching identification data, and updates the stored battery data to the received battery data.

6. The BMS according to claim 5, wherein: The master BMS After the update, sends the battery data stored in the master BMS to the external system.

7. The BMS according to claim 1, wherein: The master BMS When receiving power from a power source and waking up, 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 the previously stored identification data, and updates the stored battery data to the received battery data.

8. A battery data management method, the battery data management method being executed by a master battery management system (BMS), the battery data management method managing battery data collected and stored in each of a plurality of slave BMSs electrically connected to a plurality of battery modules for each predetermined storage period, the battery data management method including: Receiving a request signal for the battery data from an external system, the battery data including status information of each of the plurality of battery modules; And Sending the battery data to the external system, the battery data being received from each of the plurality of slave BMSs for each storage period, mapped to identification data including identification information of each of the plurality of slave BMSs, and stored.

9. The battery data management method according to claim 8, wherein: the battery data includes information on at least one of the total number of charge / discharge cycles of each battery module among the plurality of battery modules and the total energy discharged from each battery module among the plurality of battery modules.

10. The battery data management method according to claim 8, further comprising: after receiving the request signal for the battery data, requesting and receiving the identification data from each of the plurality of slave BMSs, and determining whether the received identification data matches the identification data stored in the master BMS, wherein sending to the external system includes when it is determined that the received identification data matches the identification data, sending the battery data stored in the master BMS to the external system.

11. The battery data management method according to claim 10, further comprising: after determining whether the received identification data matches the previously stored identification data, when it is determined that the received identification data does not match the identification data, requesting and receiving the battery data from at least one slave BMS corresponding to the non-matching identification data, and updating the stored battery data to the received battery data; wherein sending to the external system includes after the update, sending the battery data stored in the master BMS to the external system.

12. A battery data management method, which is executed by a master battery management system (BMS), the battery data management method managing battery data collected and stored in each of a plurality of slave BMSs by each of the plurality of slave BMSs electrically connected to a plurality of battery modules for each predetermined storage period, the battery data management method comprising: receiving power from a power source and waking up; requesting and receiving identification data including identification information of each of the plurality of slave BMSs from each of the plurality of slave BMSs; determining whether the received identification data matches the identification data stored in the master BMS; when it is determined that the received identification data does not match the identification data, requesting and receiving the battery data from at least one slave BMS corresponding to the non-matching identification data; and updating the battery data stored in the master BMS to the received battery data.

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

14. The battery data management method according to claim 12, wherein: the battery data includes information on at least one of the total number of charge / discharge cycles of each battery module among the plurality of battery modules and the total energy discharged from each battery module among the plurality of battery modules.

Images