BMS Management Device and Method

Abstract

The BMS management device according to an embodiment of the present disclosure is a device including a main BMS and a plurality of slave BMSs, and includes: a main BMS configured to send an NV value confirmation request to the plurality of slave BMSs, and when receiving a response to the NV value confirmation request from the plurality of slave BMSs, send a request unification request to the plurality of slave BMSs based on whether the source ID is set; and a plurality of slave BMSs configured to send each NV value to the main BMS when receiving the NV value confirmation request from the main BMS, set a representative BMS and a target BMS based on the plurality of NV values, set the representative BMS or the slave BMS corresponding to the source ID as the source BMS according to the unification request received from the main BMS, and update the NV value of the target BMS according to the NV value of the source BMS.

Description

Technical Field

[0001] This application claims the priority of Korean Patent Application No. 10-2020-0153902, filed in Korea on November 17, 2020, the disclosure of which is incorporated herein by reference.

[0002] The present disclosure relates to a BMS (Battery Management System) management apparatus and method, and more particularly, to a BMS management apparatus and method capable of effectively updating a plurality of slave BMSs. Background Art

[0003] Recently, the demand for portable electronic products such as notebook computers, cameras, and mobile phones has increased rapidly, and electric vehicles, energy storage batteries, robots, satellites, etc. have been vigorously developed. Therefore, high-performance batteries that allow repeated charging and discharging are being actively studied.

[0004] Currently, commercially available batteries include nickel-cadmium batteries, nickel-metal hydride batteries, nickel-zinc batteries, lithium batteries, etc. Among them, lithium batteries have attracted much attention because they have almost no memory effect compared to nickel-based batteries and also have a very low self-charging rate and high energy density.

[0005] Generally, an energy storage system (ESS) includes a plurality of battery racks as system units, and each of these battery racks may include a BMS. However, in this BMS, system values (e.g., NV values, etc.) are set by the manual operation of an operator. For example, when the BMS of a battery rack is replaced, the operator sets the system value of the replaced BMS to be the same as that of other BMSs.

[0006] However, when the operator directly sets the system value of the BMS, there are costs and error risks, so a method that can handle this work at the system level through communication between BMSs is needed. Summary of the Invention

[0007] Technical problem

[0008] The present disclosure is designed to solve the problems of the prior art, and thus the present disclosure is committed to providing a BMS management apparatus and method capable of effectively updating and synchronizing NV values through a plurality of slave BMSs.

[0009] These and other objects and advantages of the present disclosure can be understood from the following detailed description and will become more fully apparent from the exemplary embodiments of the present disclosure. In addition, it will be readily understood that the objects and advantages of the present disclosure can be achieved by the means shown in the appended claims and their combinations.

[0010] Technical solution

[0011] A BMS management device according to an aspect of the present disclosure is a device including a main BMS and a plurality of slave BMSs, and may include: a main BMS configured to send an NV value confirmation request to the plurality of slave BMSs, and when receiving a response to the NV value confirmation request from the plurality of slave BMSs, send a unification request to the plurality of slave BMSs based on whether a source ID is set; and a plurality of slave BMSs configured to, when receiving an NV value confirmation request from the main BMS, send each NV value to the main BMS, set a representative BMS and a target BMS based on the plurality of NV values, set the representative BMS or the slave BMS corresponding to the source ID as the source BMS according to the unification request received from the main BMS, and update the NV value of the target BMS according to the NV value of the source BMS.

[0012] When receiving the ID of any one of the plurality of slave BMSs from the outside, the main BMS may be configured to set the received ID as the source ID.

[0013] The main BMS may be configured to: when the source ID is set, send a first unification request including the source ID to the plurality of slave BMSs.

[0014] The main BMS may be configured to: when the source ID is not set, send a second unification request not including the source ID to the plurality of slave BMSs.

[0015] The plurality of slave BMSs may be configured to: when receiving the first unification request, set the slave BMS corresponding to the source ID as the source BMS.

[0016] The plurality of slave BMSs may be configured to: when receiving the second unification request, set the representative BMS as the source BMS.

[0017] After setting the representative BMS and the target BMS, when no unification request is received within a predetermined time, the plurality of slave BMSs may be configured to set the representative BMS as the source BMS.

[0018] The plurality of slave BMSs may be configured to generate a main group and at least one secondary group according to the number of slave BMSs included in a group including slave BMSs having the same NV value, set any one of the plurality of slave BMSs included in the main group as the representative BMS, and set the slave BMSs included in at least one secondary group as the target BMSs.

[0019] The plurality of slave BMSs may be configured to set, as the representative BMS, the slave BMS having an ID corresponding to a preset condition among the plurality of slave BMSs included in the main group.

[0020] The master BMS can be configured to store the NV value of the source BMS at a previous update time as a standard NV value, and when the multiple NV values received from multiple slave BMSs are classified into the same number, the master BMS can be configured to set the ID of any one of the multiple slave BMSs having the same NV value as the standard NV value among the multiple NV values as the source ID.

[0021] The source BMS can be configured to receive whether the NV value is updated and the updated NV value from each target BMS, and send a unification completion notification or a unification failure notification to the master BMS according to whether the updated NV value received from the target BMS is the same as the NV value of the source BMS.

[0022] An energy storage system according to another aspect of the present disclosure may include a BMS management device according to one aspect of the present disclosure.

[0023] A BMS management method according to still another aspect of the present disclosure is a method executed by a BMS management device including a master BMS and multiple slave BMSs, and may include: an NV value confirmation request step of sending an NV value confirmation request to the multiple slave BMSs; an NV value sending step of sending each NV value to the master BMS when an NV value confirmation request is received from the master BMS; a representative BMS and target BMS setting step of setting a representative BMS and a target BMS based on the multiple NV values; a unification request sending step of sending a unification request to the multiple slave BMSs based on whether the source ID is set when a response to the NV value confirmation request is received from the multiple slave BMSs; a source BMS setting step of setting the representative BMS or the slave BMS corresponding to the source ID as the source BMS according to the unification request received from the master BMS; and an NV value update step of updating the NV value of the target BMS according to the NV value of the source BMS.

[0024] Beneficial effect

[0025] According to one aspect of the present disclosure, there is an advantage that multiple slave BMSs can autonomously update the NV value not only when the source ID is specified by the master BMS but also when the source ID is not specified.

[0026] The effects of the present disclosure are not limited to the effects mentioned above, and according to the description of the claims, those skilled in the art will clearly understand other effects not mentioned. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] The drawings illustrate preferred embodiments of the present disclosure and, together with the foregoing disclosure, are used to provide a further understanding of the technical features of the present disclosure. Therefore, the present disclosure is not to be construed as limited to the drawings.

[0028] Figure 1FIG. is a diagram schematically showing a BMS management device according to an embodiment of the present disclosure.

[0029] Figure 2 FIG. is a diagram schematically showing an embodiment of a BMS management device according to an embodiment of the present disclosure.

[0030] Figure 3 FIG. is a diagram schematically showing another embodiment of a BMS management device according to an embodiment of the present disclosure.

[0031] Figure 4 FIG. is a diagram schematically showing still another embodiment of a BMS management device according to an embodiment of the present disclosure.

[0032] Figures 5 to 8 FIG. is a diagram schematically showing an embodiment in which the NV value of the BMS is updated by the BMS management device according to an embodiment of the present disclosure.

[0033] Figure 9 FIG. is a diagram schematically showing a BMS management method according to another embodiment of the present disclosure.

[0034] Figure 10 FIG. is a diagram schematically showing a representative BMS and target BMS setting step in a BMS management method according to another embodiment of the present disclosure.

[0035] Figure 11 FIG. is a diagram schematically showing a source BMS setting step in a BMS management method according to another embodiment of the present disclosure. DETAILED DESCRIPTION

[0036] It should be understood that the terms used in the specification and the appended claims should not be construed as limited to the general and dictionary meanings, but should be interpreted based on the meanings and concepts corresponding to the technical aspects of the present disclosure on the basis of the principle that allows the inventor to appropriately define the terms for the best explanation.

[0037] Therefore, the descriptions presented herein are merely preferred examples for illustrative purposes only and are not intended to limit the scope of the present disclosure. Thus, it should be understood that equivalents and modifications can be made thereto without departing from the scope of the present disclosure.

[0038] Additionally, when describing the present disclosure, detailed descriptions of related known elements or functions are omitted herein when it is considered that such detailed descriptions would obscure the key subject matter of the present disclosure.

[0039] Terms including ordinal numbers such as "first", "second", etc. may be used to distinguish one element from another among various elements, but are not intended to limit the elements by these terms.

[0040] Throughout the specification, when a part is referred to as "including" or "containing" any element, unless specifically stated otherwise, it means that the part may further include other elements without excluding other elements.

[0041] In addition, throughout the specification, when a part is referred to as "connected" to another part, this is not limited to the case where they are "directly connected", but also includes the case of "indirect connection" where another element is interposed between them.

[0042] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

[0043] Figure 1 is a diagram schematically showing a BMS management device 100 according to an embodiment of the present disclosure.

[0044] Referring to Figure 1 , the BMS management device 100 may include a main BMS 110 and a plurality of slave BMSs 120.

[0045] For example, the main BMS 110 may be a superior BMS of the slave BMSs.

[0046] The main BMS 110 may be configured to send a non-volatile (NV) value confirmation request to the plurality of slave BMSs 120.

[0047] For example, in the Figure 1 embodiment, the main BMS 110 may be respectively connected to the plurality of slave BMSs 120. The main BMS 110 may send an NV value confirmation request to each of the first slave BMS 120a, the second slave BMS 120b, the third slave BMS 120c, the fourth slave BMS 120d, and the fifth slave BMS 120e.

[0048] When receiving responses to the NV value confirmation request from the plurality of slave BMSs 120, the main BMS 110 may be configured to send a unification request to the plurality of slave BMSs 120 based on whether the source ID is set.

[0049] For example, when the main BMS 110 receives all NV value confirmation requests from each of the plurality of slave BMSs 120, the main BMS 110 may send a unification request to the plurality of slave BMSs 120. In this case, the main BMS 110 may send the first unification request or the second unification request to the plurality of slave BMSs 120 in the same manner according to whether the source ID is set.

[0050] That is, when the source ID is set, the master BMS 110 can be configured to send a first unification request including the source ID to multiple slave BMSs 120. Conversely, when the source ID is not set, the master BMS 110 can be configured to send a second unification request not including the source ID to multiple slave BMSs 120.

[0051] In Figure 1 an embodiment, when all NV value confirmation requests are received from multiple slave BMSs 120, the master BMS 110 can send a unification request to multiple slave BMSs 120.

[0052] Multiple slave BMSs 120 can be configured to send each NV value to the master BMS 110 when an NV value confirmation request is received from the master BMS 110.

[0053] Each of multiple slave BMSs 120 can send its NV value to the master BMS 110 as a response to the NV value confirmation request. Preferably, multiple slave BMSs 120 can use the same hash function to generate a hash value for the NV value. Additionally, multiple slave BMSs 120 can send the generated hash value to the master BMS 110.

[0054] For example, in Figure 1 an embodiment, each of the first slave BMS 120a, the second slave BMS 120b, the third slave BMS 120c, the fourth slave BMS 120d, and the fifth slave BMS 120e can send its NV value as a response to the NV value confirmation request.

[0055] Multiple slave BMSs 120 can be configured to set a representative BMS and a target BMS based on multiple NV values. When multiple slave BMSs 120 receive an NV value confirmation request from the master BMS 110, multiple slave BMSs 120 can set a representative BMS and a target BMS based on multiple NV values. Preferably, multiple slave BMSs 120 can set a representative BMS and a target BMS after sending the NV value to the master BMS 110.

[0056] For example, in Figure 1 an embodiment, each of multiple slave BMSs 120 can have an NV value. That is, the number of multiple NV values can be five. Multiple slave BMSs 120 can set any one of multiple slave BMSs 120 as a representative BMS based on the five NV values. Additionally, multiple slave BMSs 120 can set a target BMS based on the five NV values. Specific details of setting a representative BMS and a target BMS by multiple slave BMSs 120 based on multiple NV values will be described later.

[0057] Multiple slave BMSs 120 may be configured to set a representative BMS or a slave BMS corresponding to a source ID as a source BMS according to a unification request received from a master BMS 110.

[0058] Specifically, multiple slave BMSs 120 may set a representative BMS or a slave BMS corresponding to a source ID as a source BMS according to whether a source ID is included in a unification request received from a master BMS 110.

[0059] That is, multiple slave BMSs 120 may be configured to set a slave BMS corresponding to a source ID as a source BMS when a first unification request is received. Conversely, multiple slave BMSs 120 may be configured to set a representative BMS as a source BMS when a second unification request is received.

[0060] Multiple slave BMSs 120 may be configured to update an NV value of a target BMS according to an NV value of a source BMS.

[0061] For example, in Figure 1 an embodiment, when an NV value of a first slave BMS 120a and NV values of second to fourth slave BMSs 120b to 120d are the same and an NV value of a fifth slave BMS 120e is different, assuming that the first slave BMS 120a is set as a source BMS and the fifth slave BMS 120e is set as a target BMS. That is, the second to fourth slave BMSs 120b to 120d may not be set as target BMSs. The first slave BMS 120a may send its NV value to the fifth slave BMS 120e to update the NV value of the fifth slave BMS 120e to be the same as the NV values of the first to fourth slave BMSs 120a to 120d.

[0062] The BMS management apparatus 100 according to an embodiment of the present disclosure has the following advantages: Multiple slave BMSs 120 may autonomously update NV values not only when a source ID is specified by a master BMS 110 but also when a source ID is not specified.

[0063] For example, even if a source ID is missing in a unification request received by multiple slave BMSs 120 from a master BMS 110 or is lost due to a communication failure, multiple slave BMSs 120 may normally update NV values by setting a source BMS by themselves.

[0064] Meanwhile, the master BMS 110 and multiple slave BMSs 120 may include a control unit and a storage unit.

[0065] Meanwhile, the control unit may optionally include a processor, an application specific integrated circuit (ASIC), another chipset, logic circuitry, registers, a communication modem, and a data processing device, etc., which are known in the art for running various control logics executed in the present disclosure. Additionally, when the control logic is implemented in software, the control unit can be implemented as a set of program modules. In this case, the program modules can be stored in the memory and run by the control unit. The memory can be provided inside or outside the control unit and can be connected to the control unit by various well-known means.

[0066] In addition, the storage unit can store data or programs necessary for the operation and function of each component of the main BMS 110 and the multiple slave BMSs 120, data generated during the execution of the operation or function, etc. The storage unit is not particularly limited in terms of its type as long as it is a known information storage means capable of recording, erasing, updating, and reading data. As an example, the information storage means can include RAM, flash memory, ROM, EEPROM, registers, etc. Additionally, the storage unit can store program code that defines procedures executable by the control unit.

[0067] When receiving the ID of any one of the multiple slave BMSs 120 from the outside, the main BMS 110 can be configured to set the received ID as the source ID.

[0068] For example, the main BMS 110 can communicate with the outside. The main BMS 110 can receive the ID of any one of the multiple slave BMSs 120 from a server or the like. Alternatively, the main BMS 110 can be connected to an input device to receive the ID of any one of the multiple slave BMSs 120 input through the input device. Here, the input device can be a device capable of outputting an input value through user manipulation, such as a keyboard, a mouse, and / or a touch screen.

[0069] Figure 2 FIG. is a diagram schematically showing an embodiment of a BMS management apparatus 100 according to an embodiment of the present disclosure.

[0070] Specifically, Figure 2 The embodiment is one in which the main BMS 110 sets the source ID after receiving a response to the NV value from the multiple slave BMSs 120.

[0071] In Figure 2 the embodiment, when the source ID is set, the main BMS 110 can send a first unification request including the source ID to the multiple slave BMSs 120.

[0072] When receiving the first unification request, the multiple slave BMSs 120 can set the slave BMS corresponding to the source ID as the source BMS.

[0073] That is, multiple slave BMSs 120 can set a representative BMS and a target BMS in advance before receiving the first unification request from the master BMS 110. Additionally, when receiving the first unification request, multiple slave BMSs 120 can set the source BMS according to the source ID, regardless of the set representative BMS.

[0074] The source BMS can update the NV value of the target BMS by sending its NV value to the target BMS.

[0075] Thereafter, the source BMS can be configured to receive from each target BMS whether the NV value is updated and the updated NV value. Additionally, the source BMS can be configured to send a unification completion notification or a unification failure notification to the master BMS 110 according to whether the updated NV value received from the target BMS is the same as its own NV value.

[0076] That is, after the source BMS receives the updated NV value from the target BMS and determines whether the update is successfully completed, the source BMS can send a unification completion notification or a unification failure notification to the master BMS 110 according to the determination result.

[0077] Figure 3 FIG. is a diagram schematically showing another embodiment of the BMS management apparatus 100 according to an embodiment of the present disclosure.

[0078] Specifically, different from the Figure 2 embodiment, Figure 3 the embodiment is an embodiment in which the master BMS 110 does not set the source ID.

[0079] In Figure 3 the embodiment, when the source ID is not set, the master BMS 110 can send a second unification request not including the source ID to multiple slave BMSs 120.

[0080] When receiving the second unification request, multiple slave BMSs 120 can set the representative BMS as the source BMS.

[0081] That is, multiple slave BMSs 120 can set a representative BMS and a target BMS in advance before receiving the second unification request from the master BMS 110. Additionally, when receiving the second unification request not including the source ID from the master BMS 110, multiple slave BMSs 120 can set the preset representative BMS as the source BMS.

[0082] In this case, the slave BMS set as the source BMS can send declaration information to notify the remaining slave BMSs that it is selected as the source BMS.

[0083] Thereafter, the source BMS can update the NV value of the target BMS by sending its NV value to the target BMS. That is, even when the source ID is not received from the master BMS 110, multiple slave BMSs 120 can update the NV value of the target BMS by setting the source BMS by themselves.

[0084] The source BMS can receive the updated NV value from the target BMS and determine whether the update is completed normally, and then send a notification of completion of unification or a notification of failure of unification to the master BMS 110 according to the determination result.

[0085] Figure 4 FIG. is a diagram schematically showing still another embodiment of the BMS management apparatus 100 according to an embodiment of the present disclosure.

[0086] Specifically, different from the embodiment of Figure 2 and Figure 3 the embodiment of Figure 4 is an embodiment in which, after multiple slave BMSs 120 send a response to the NV value to the master BMS 110 and set a representative BMS and a target BMS, a unification request is not received within a predetermined time.

[0087] When a unification request is not received within a predetermined time after setting the representative BMS and the target BMS, multiple slave BMSs 120 can be configured to set the representative BMS as the source BMS.

[0088] For example, when a system failure and / or a communication failure occurs in the master BMS 110, the master BMS 110 may not be able to send a unification request to multiple slave BMSs 120. Even in such a case, since the NV values of multiple slave BMSs 120 must be updated for multiple slave BMSs 120 to operate normally, multiple slave BMSs 120 can set a preset representative BMS as the source BMS.

[0089] That is, the BMS management apparatus 100 according to an embodiment of the present disclosure has an advantage of updating the NV values of multiple slave BMSs 120 even when multiple slave BMSs 120 do not receive a unification request from the master BMS 110.

[0090] Figures 5 to 8 FIG. is a diagram schematically showing an embodiment in which the NV value of a slave BMS is updated by the BMS management apparatus 100 according to an embodiment of the present disclosure.

[0091] Specifically, Figure 5 the embodiment of Figure 5In the embodiments, in the initial stage, the first slave BMS 120a, the second slave BMS 120b, the third slave BMS 120c, the fourth slave BMS 120d, and the fifth slave BMS 120e can be provided.

[0092] Figure 6 An embodiment is an embodiment in which, among the multiple slave BMSs 120 in the initial stage, the fourth slave BMS 120d is replaced with the sixth slave BMS 120f and the fifth slave BMS 120e is replaced with the seventh slave BMS 120g.

[0093] The NV values of the first slave BMS 120a, the second slave BMS 120b, and the third slave BMS 120c can be A, the NV value of the replaced sixth slave BMS 120f can be B, and the NV value of the replaced seventh slave BMS 120g can be C. That is, the NV values of the replaced slave BMSs 120f, 120g can be different from the NV values of the existing slave BMSs 120a, 120b, 120c.

[0094] Figure 7 An embodiment is an embodiment in which the multiple slave BMSs 120 are grouped based on the NV values.

[0095] The multiple slave BMSs 120 can be configured to group the slave BMSs having the same NV value to generate a main group and at least one secondary group according to the number of included slave BMSs.

[0096] For example, in Figure 7 In the embodiments, the multiple slave BMSs 120 can communicate with each other to check the NV values from each other. Specifically, each of the multiple slave BMSs 120 can send data including its own ID and its own NV value to the remaining slave BMSs. The multiple slave BMSs 120 can check the NV values of other slave BMSs through the data received from other slave BMSs.

[0097] Three slave BMSs 120a, 120b, 120c can have an NV value of A, one slave BMS 120f can have an NV value of B, and one slave BMS 120g can have an NV value of C. Among the multiple slave BMSs 120, the slave BMSs having the same NV value can generate a group. The first group G1 can include the first slave BMS 120a, the second slave BMS 120b, and the third slave BMS 120c. The second group G2 can include the sixth slave BMS 120f, and the third group G3 can include the seventh slave BMS 120g.

[0098] In addition, the multiple slave BMSs 120 can set the group having the largest number of slave BMSs as the main group, and the remaining groups can be set as secondary groups.

[0099] For example, in Figure 7 the embodiment of Figure 7 , the first group G1 including three slave BMSs 120a, 120b, and 120c can be configured as the main group, and the second group G2 and the third group G3 can be configured as secondary groups.

[0100] The multiple slave BMSs 120 can be configured to set any one of the multiple slave BMSs 120 included in the main group as the representative BMS.

[0101] Specifically, the multiple slave BMSs 120 can be configured to set the slave BMS having an ID corresponding to a preset condition among the multiple slave BMSs 120 included in the main group as the representative BMS.

[0102] For example, the slave BMS having the lowest ID among the multiple slave BMSs 120 included in the main group can be set as the representative BMS. In Figure 7 the embodiment of Figure 7 , the first slave BMS 120a can be set as the representative BMS.

[0103] As another example, the slave BMS having the largest ID among the multiple slave BMSs 120 included in the main group can be set as the representative BMS. That is to say, since the multiple slave BMSs 120 included in the main group have the same NV value, any one of the slave BMSs included in the main group can be set as the representative BMS.

[0104] The multiple slave BMSs 120 can be configured to set the slave BMSs included in at least one secondary group as the target BMSs.

[0105] The NV values of all the slave BMSs included in the secondary group can be different from the NV values of the multiple slave BMSs 120 included in the main group. Therefore, all the slave BMSs included in the secondary group can be set as the target BMSs.

[0106] Figure 8 The embodiment of Figure 8 is an embodiment in which the NV values of the sixth slave BMS 120f and the seventh slave BMS 120g set as the target BMSs are updated.

[0107] The source BMS can be set according to whether a unification request is received from the master BMS 110 and the type of the received unification request. In addition, the source BMS can update all the NV values of the target BMS by sending its own NV value to the target BMS.

[0108] For example, in Figure 8In an embodiment, it is assumed that the first slave BMS 120a is set as the source BMS. The first slave BMS 120a can send its NV value to the sixth slave BMS 120f and the seventh slave BMS 120g. The sixth slave BMS 120f and the seventh slave BMS 120g can receive the NV value from the first slave BMS 120a and update their NV values. Therefore, the NV values of the first slave BMS 120a, the second slave BMS 120b, the third slave BMS 120c, the sixth slave BMS 120f, and the seventh slave BMS 120g can all be unified to A.

[0109] That is to say, the BMS management device 100 according to the embodiment of the present disclosure has the following advantages: Even if the NV values of the slave BMSs are not set separately by the user, the NV values of multiple slave BMSs can be synchronized by themselves.

[0110] At the same time, it is assumed that Figures 5 to 8 Different from the embodiment, six slave BMSs are provided at the initial stage, and three of them are replaced. If the NV values of the three replaced slave BMSs are all the same, it may not be easy to set the main group and the secondary group because the three slave BMSs have the same NV value.

[0111] If the group of the replaced slave BMS is set as the main group, there may be a problem that the NV value of the existing slave BMS is updated to the NV value of the replaced slave BMS.

[0112] To prevent this problem from occurring, the master BMS 110 can be configured to store the NV value of the source BMS at the previous update time as the standard NV value. In addition, when the multiple NV values received from multiple slave BMSs 120 are classified into the same number, the master BMS 110 can be configured to set the ID of any one of the multiple slave BMSs 120 having the same NV value as the standard NV value among the multiple NV values as the source ID.

[0113] That is to say, the master BMS 110 can store the standard NV value at the previous update time in advance, and then classify the NV values received from multiple slave BMSs 120 by itself. As a result of the classification, when the same number of slave BMSs are classified, the master BMS 110 can set the ID of the slave BMS having the same NV value as the standard NV value as the source ID. In this case, even if the ID is not input from the outside, the master BMS 110 can directly set the source ID. Therefore, even if multiple groups including the same number of slave BMSs are generated, the NV values of the multiple slave BMSs 120 can be normally updated based on the source ID set by the master BMS 110.

[0114] The BMS management device 100 according to an embodiment of the present disclosure may be included in an energy storage system (ESS). Generally, an energy storage system applied to a power plant that drives a large-scale power grid or a building or factory that consumes a large amount of electricity includes a plurality of battery racks each having a plurality of battery modules. In addition, a plurality of such battery racks are configured to form a battery bank, and a plurality of battery banks are configured to form a section.

[0115] For example, the main BMS 110 may be a battery bank management system (BBMS) corresponding to the battery bank, and each of the plurality of slave BMSs 120 may be a rack battery management system (RBMS) corresponding to the corresponding battery rack.

[0116] Therefore, when the slave BMS of some of the plurality of battery racks is replaced, the NV value of the replaced slave BMS can be updated according to the BMS management device 100.

[0117] Figure 9 FIG. is a diagram schematically showing a BMS management method according to another embodiment of the present disclosure.

[0118] Preferably, each step of the BMS management method may be executed by the BMS management device 100 including the main BMS 110 and the plurality of slave BMSs 120. Hereinafter, for convenience of description, the content overlapping with the previously described content will be omitted or briefly described.

[0119] Refer to Figure 9 , the BMS management method may include an NV value confirmation request step (S100), an NV value transmission step (S200), a representative BMS and target BMS setting step (S300), a unification request transmission step (S400), a source BMS setting step (S500), and an NV value update step (S600).

[0120] The NV value confirmation request step (S100) is a step of sending an NV value confirmation request to the plurality of slave BMSs 120, and may be executed by the main BMS 110.

[0121] The NV value transmission step (S200) is a step of sending each NV value to the main BMS 110 when an NV value confirmation request is received from the main BMS 110, and may be executed by the plurality of slave BMSs 120.

[0122] Each of the plurality of slave BMSs 120 may send its NV value to the main BMS 110 as a response to the NV value confirmation request.

[0123] The representative BMS and target BMS setting step (S300) is a step of setting the representative BMS and target BMS based on a plurality of NV values, and can be executed by a plurality of slave BMSs 120.

[0124] Refer to Figure 10 The representative BMS and target BMS setting step (S300) will be described in detail. Figure 10 FIG. is a diagram schematically showing the representative BMS and target BMS setting step S300 in the BMS management method according to another embodiment of the present disclosure.

[0125] The representative BMS and target BMS setting step (S300) may include step S310, step S320, step S330, and step S340.

[0126] In step S310, each of the plurality of slave BMSs 120 may check its NV value and the NV values of other slave BMSs.

[0127] For example, in Figure 7 the embodiment, each of the first slave BMS 120a, the second slave BMS 120b, the third slave BMS 120c, the sixth slave BMS 120f, and the seventh slave BMS 120g may check all its NV values and the NV values of other slave BMSs.

[0128] In step S320, among the plurality of slave BMSs 120, the slave BMSs having the same NV value may generate a group. Additionally, among the generated groups, the group including the largest number of slave BMSs may be set as the main group, and the remaining groups may be set as the secondary groups.

[0129] For example, in Figure 7 the embodiment, the first slave BMS 120a, the second slave BMS 120b, and the third slave BMS 120c having the same NV value of A may be classified into the first group G1. The sixth slave BMS 120f having the NV value of B may be classified into the second group G2. The seventh slave BMS 120g having the NV value of C may be classified into the third group G3. Additionally, the first group G1 including the largest number of slave BMSs may be set as the main group, and the remaining groups (the second group G2 and the third group G3) may be set as the secondary groups.

[0130] In step S330, any one of the plurality of slave BMSs 120 may be set as the representative BMS. Specifically, any one of the plurality of slave BMSs 120 belonging to the main group may be set as the representative BMS.

[0131] For example, in Figure 7In the embodiment, the first slave BMS 120a included in the first group G1 as the main group can be set as the representative BMS.

[0132] In step S340, at least one slave BMS belonging to the secondary group can be set as the target BMS.

[0133] For example, in Figure 7 the embodiment, the sixth slave BMS 120f included in the second group G2 and the seventh slave BMS 120g included in the third group G3 can be set as the target BMS.

[0134] The unification request sending step (S400) is a step of sending a unification request to the plurality of slave BMSs 120 based on whether the source ID is set when responses to the NV value confirmation requests are received from the plurality of slave BMSs 120, and can be executed by the master BMS 110.

[0135] When the source ID is set, the master BMS 110 can send a first unification request including the source ID to the plurality of slave BMSs 120. Conversely, when the source ID is not set, the master BMS 110 can send a second unification request not including the source ID to the plurality of slave BMSs 120.

[0136] The source BMS setting step (S500) is a step of setting the representative BMS or the slave BMS corresponding to the source ID as the source BMS according to the unification request received from the master BMS 110, and can be executed by the plurality of slave BMSs 120.

[0137] Reference will be made to Figure 11 describe the source BMS setting step (S500) in detail. Figure 11 is a diagram schematically showing the source BMS setting step S500 in the BMS management method according to another embodiment of the present disclosure.

[0138] In step S510, the plurality of slave BMSs 120 can determine whether a first unification request is received from the master BMS 110. If the plurality of slave BMSs 120 receive the first unification request, step S520 can be executed, and if the first unification request is not received, step S530 can be executed.

[0139] In step S520, the plurality of slave BMSs 120 can set the slave BMS corresponding to the source ID included in the first unification request as the source BMS. That is, even if the representative BMS is set in advance in step S330, when the source ID is received from the master BMS 110, the slave BMS corresponding to the source ID can be set as the source BMS. Then, the NV value update step (S600) can be executed.

[0140] For example, in Figure 7 the embodiment, it is assumed that the source ID included in the first unification request received by the plurality of slave BMSs 120 from the master BMS 110 is 2. In this case, the second slave BMS 120b having an ID corresponding to the source ID can be set as the source BMS. That is, even if the representative BMS is set as the first slave BMS 120a in step S330, the second slave BMS 120b corresponding to the source ID can be set as the source BMS.

[0141] In step S530, the plurality of slave BMSs 120 can determine whether a second unification request is received from the master BMS 110. If the plurality of slave BMSs 120 receive the second unification request, step S550 can be executed; otherwise, step S540 can be executed.

[0142] In step S540, after the unification request (the first unification request and the second unification request) is not received from the master BMS 110, the plurality of slave BMSs 120 can determine whether a predetermined time has elapsed since the time point when the representative BMS and the target BMS were set. If the predetermined time has elapsed, step S550 can be executed; otherwise, step S510 can be executed again.

[0143] That is, the plurality of slave BMSs 120 can wait for the reception of the unification request within a predetermined time after the representative BMS and the target BMS setting step (S300). However, if the unification request is not received within the predetermined time, step S550 can be executed to normally update the NV values of the plurality of slave BMSs 120.

[0144] Step S550 is a step of setting the representative BMS set in step S330 as the source BMS. That is, even if the master BMS 110 does not determine the source BMS (even if the first unification request including the source ID is not received), the plurality of slave BMSs 120 can set the representative BMS set by themselves as the source BMS.

[0145] For example, in Figure 7 the embodiment, the first slave BMS 120a set as the representative BMS can be set as the source BMS.

[0146] The NV value update step (S600) is a step of updating the NV value of the target BMS according to the NV value of the source BMS, and can be executed by the plurality of slave BMSs 120.

[0147] The source BMS can send its NV value to the target BMS. The target BMS that receives the NV value can update its NV value to the received NV value.

[0148] For example, in Figure 7 the embodiment of Figure 7 , the first slave BMS 120a set as the source BMS can send the NV value of A to the sixth slave BMS 120f and the seventh slave BMS 120g set as the target BMS. The sixth slave BMS 120f and the seventh slave BMS 120g can update their NV values to the received NV value of A. Therefore, in Figure 8 the embodiment of Figure 8 , the NV values of the first slave BMS 120a, the sixth slave BMS 120f, and the seventh slave BMS 120g can all be the same.

[0149] The above embodiments of the present disclosure can be implemented not only by devices and methods, but also by a program that implements functions corresponding to the configurations of the embodiments of the present disclosure or a recording medium on which the program is recorded. The program or the recording medium can be easily implemented by those skilled in the art based on the above description of the embodiments.

[0150] The present disclosure has been described in detail. However, it should be understood that the detailed description and specific examples, although indicating preferred embodiments of the present disclosure, are given by way of illustration only, since various changes and modifications within the scope of the present disclosure will become apparent to those skilled in the art in light of this specific implementation.

[0151] Additionally, without departing from the technical aspects of the present disclosure, those skilled in the art can make many substitutions, modifications, and variations to the present disclosure described above, and the present disclosure is not limited to the above embodiments and drawings, and each embodiment can be partially or wholly selectively combined to allow various modifications.

[0152] (Reference numerals)

[0153] 100: BMS management device

[0154] 110: Master BMS

[0155] 120: Multiple slave BMSs

Claims

1. A BMS management device including a main BMS and multiple slave BMSs, comprising: The master BMS is configured to send an NV value confirmation request to the multiple slave BMSs, and when receiving a response to the NV value confirmation request from the multiple slave BMSs, send a unification request to the multiple slave BMSs based on whether the source ID is set; And Multiple slave BMSs, the multiple slave BMSs are configured to send each NV value to the master BMS when receiving the NV value confirmation request from the master BMS, set a representative BMS and a target BMS based on the multiple NV values, set the representative BMS or the slave BMS corresponding to the source ID as the source BMS according to the unification request received from the master BMS, and update the NV value of the target BMS according to the NV value of the source BMS.

2. The BMS management device according to claim 1, wherein, When receiving the ID of any one of the multiple slave BMSs from the outside, the master BMS is configured to set the received ID as the source ID.

3. The BMS management device according to claim 2, wherein, The master BMS is configured to: when the source ID is set, send a first unification request including the source ID to the multiple slave BMSs, and wherein, the master BMS is configured to: when the source ID is not set, send a second unification request not including the source ID to the multiple slave BMSs.

4. The BMS management device according to claim 3, wherein, The multiple slave BMSs are configured to: when receiving the first unification request, set the slave BMS corresponding to the source ID as the source BMS, and wherein, the multiple slave BMSs are configured to: when receiving the second unification request, set the representative BMS as the source BMS.

5. The BMS management device according to claim 1, wherein, After setting the representative BMS and the target BMS, when the unification request is not received within a predetermined time, the multiple slave BMSs are configured to set the representative BMS as the source BMS.

6. The BMS management device according to claim 1, wherein, The multiple slave BMSs are configured to generate a main group and at least one secondary group according to the number of slave BMSs included in a group including slave BMSs having the same NV value, set any one of the multiple slave BMSs included in the main group as the representative BMS, and set the slave BMSs included in the at least one secondary group as the target BMSs.

7. The BMS management device according to claim 6, wherein, The multiple slave BMSs are configured to set the slave BMS having an ID corresponding to a preset condition among the multiple slave BMSs included in the main group as the representative BMS.

8. The BMS management device according to claim 1, wherein, The master BMS is configured to store the NV value of the source BMS at the previous update time as the standard NV value, and when the multiple NV values received from the multiple slave BMSs are classified into the same number, the master BMS is configured to set the ID of any one of the multiple slave BMSs having the same NV value as the standard NV value among the multiple NV values as the source ID.

9. The BMS management device according to claim 1, wherein, The source BMS is configured to receive whether the NV value is updated and the updated NV value from each target BMS, and send a notification of completion of unification or a notification of failure of unification to the master BMS according to whether the updated NV value received from the target BMS is the same as the NV value of the source BMS.

10. An energy storage system including the BMS management device according to any one of claims 1 to 9.

11. A BMS management method, which is executed by a BMS management device including a main BMS and multiple slave BMSs, comprising: An NV value confirmation request step of sending an NV value confirmation request to the plurality of slave BMSs; An NV value sending step of sending each NV value to the master BMS when receiving the NV value confirmation request from the master BMS; A representative BMS and target BMS setting step of setting a representative BMS and a target BMS based on the plurality of NV values; A unification request sending step of sending a unification request to the plurality of slave BMSs based on whether the source ID is set when receiving a response to the NV value confirmation request from the plurality of slave BMSs; A source BMS setting step of setting the representative BMS or the slave BMS corresponding to the source ID as the source BMS according to the unification request received from the master BMS; And An NV value update step of updating the NV value of the target BMS according to the NV value of the source BMS.

Images