Inter-ESS-operation-layer communication method, communication system, and computer program saved on recording medium for executing communication method
Patent Information
- Application Number
- JP2024112682
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-08-18
- Filing Date
- 2024-07-12
- Publication Date
- 2025-03-03
AI Technical Summary
【0018】 本発明によれば、ESS運営レイヤ間において、効果的に通信する通信方法、通信システム、及び通信方法を実行させるために、記録媒体に保存されたコンピュータプログラムを提供しうる。ここで、そのような効果により、本発明の範囲が限定されるのではないということは、言うまでもない。
Smart Images

Figure 2025028759000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to an ESS (energy storage system) operation inter-layer communication method, a communication system, and a computer program stored on a recording medium for executing the communication method. [Background technology]
[0002] Recently, the demand for portable electronic products such as notebook computers, video cameras, and mobile phones has increased dramatically, and the development of energy storage batteries, robots, satellites, etc. has been fully underway. As a result, research into high-performance secondary batteries that can be repeatedly charged and discharged is being actively conducted.
[0003] Currently, commercially available secondary batteries include nickel-cadmium batteries, nickel-metal hydride batteries, nickel-zinc batteries, and lithium secondary batteries. Of these, lithium secondary batteries are attracting attention due to their advantages over nickel-based secondary batteries, such as almost no memory effect, freedom in charging and discharging, a very low natural discharge rate, and high energy density.
[0004] The battery including the secondary battery as described above can be used in an ESS (energy storage system). The communication structure of the ESS is such that an enterprise management system (EMS) for managing operations of a customer is at the top of the communication structure, a system BMS (battery management system) communicates with the EMS, and the system BMS collects information from a lower rack BMS and transmits it to the EMS. The EMS and the system BMS use transmission control protocol / Internet protocol (TCPIP) communication, and the system BMS and the rack BMS are connected using controller area network (CAN) communication. In such a structure, when the EMS changes a setting value of the system BMS or issues a command, it is sufficient to input a command through the TCPIP communication. However, since the EMS and the rack BMS are not directly connected to each other, it is difficult to change a setting value of the rack BMS or issue a control command. Summary of the Invention [Problem to be solved by the invention]
[0005] The problem to be solved by the present invention is to overcome the above-mentioned problems, and to provide an ESS operation inter-layer communication method, a communication system, and a computer program stored on a recording medium for executing the communication method.
[0006] However, such assignments are illustrative and are not intended to limit the scope of the invention. [Means for solving the problem]
[0007] As a technical means for achieving the above technical object, there is provided a method for an enterprise management system (EMS), a battery management system (system BMS) and a rack BMS to communicate with each other, the method including a step of the system BMS receiving a transmission control protocol / Internet protocol (TCPIP) communication command including a controller area network (CAN) communication command for controlling the rack BMS from the EMS, and a step of the system BMS converting a TCPIP format into a CAN format based on the TCPIP communication command and transmitting the converted CAN communication command to the rack BMS.
[0008] According to an example, receiving the TCPIP communication command also includes the system BMS and the EMS performing TCPIP communication with each other.
[0009] According to another example, the step of receiving the TCPIP communication command may include a step of receiving a TCPIP communication command including a CAN communication command in a TCPIP format, the CAN communication command including information related to a CAN ID (identification) and CAN data.
[0010] According to yet another example, the step of receiving the TCPIP communication command includes a step of receiving two TCPIP communication commands mapped to a CAN ID and four TCPIP communication commands mapped to CAN data, and the step of transmitting to the rack BMS also includes a step of transmitting the CAN communication command including the CAN ID and the CAN data.
[0011] According to yet another example, the step of transmitting to the rack BMS also includes a step in which the system BMS and the rack BMS communicate with each other via CAN.
[0012] As a technical means for achieving the above technical object, a computer program stored on a recording medium is provided for using a computing device to execute the above method.
[0013] As a technical means for achieving the above-mentioned technical object, there is provided a communication system including a system BMS in a system in which an EMS, a system BMS, and a rack BMS provided in an ESS communicate with each other, which receives TCPIP communication commands including a CAN communication command for controlling the rack BMS from the EMS, converts the TCPIP format to a CAN format based on the TCPIP communication command, and transmits the converted CAN communication command to the rack BMS.
[0014] According to one example, the system BMS can communicate with the EMS via TCPIP.
[0015] According to another example, the system BMS may receive a TCPIP communication command including a CAN communication command including information related to a CAN ID and CAN data in a TCPIP format.
[0016] According to yet another example, the system BMS may receive two TCPIP communication commands mapped to a CAN ID and four TCPIP communication commands mapped to CAN data, and transmit the CAN communication commands including the CAN ID and the CAN data.
[0017] According to yet another example, the system BMS can communicate with the rack BMS via CAN. Effect of the Invention
[0018] According to the present invention, a communication method for effectively communicating between ESS operation layers, a communication system, and a computer program stored on a recording medium for executing the communication method may be provided, although it is needless to say that the scope of the present invention is not limited by such effects. [Brief description of the drawings]
[0019] [Figure 1] FIG. 1 is a diagram illustrating a structure of an ESS communication system according to an embodiment of the present invention. [Diagram 2] FIG. 1 is a diagram illustrating a structure of an ESS communication system according to an embodiment of the present invention. [Diagram 3] FIG. 2 is a diagram for explaining components of a system BMS according to an embodiment of the present invention. [Figure 4] 4 is a flowchart illustrating an ESS operation inter-layer communication method according to an embodiment of the present invention. [Diagram 5] FIG. 2 is a diagram illustrating an ESS operation inter-layer communication method according to one embodiment of the present invention. [Figure 6] FIG. 2 is a diagram illustrating an ESS operation inter-layer communication method according to one embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0020] Hereinafter, various embodiments will be described in detail with reference to the accompanying drawings so that a person having ordinary skill in the art to which the present disclosure pertains can easily carry out the present disclosure. However, the technical idea of the present disclosure may be embodied in various forms and is not limited to the embodiments described herein. In the description of the embodiments disclosed herein, if it is determined that a detailed description of related publicly known technology may make the gist of the technical idea of the present disclosure unclear, the detailed description of the publicly known technology will be omitted. Identical or similar components will be denoted by the same reference numerals, and duplicate descriptions thereof will be omitted.
[0021] In this specification, when an element is described as being "connected" to another element, this does not only mean that it is "directly connected" to another element, but also means that it is "indirectly connected" to another element by sandwiching another element therebetween. When an element "includes" another element, this does not mean that it excludes other elements in addition to the other elements, but also means that it further includes other elements, unless otherwise specified to the contrary.
[0022] Some embodiments may be described by functional block configurations and various processing steps. Some or all of such functional blocks may be embodied by various numbers of hardware configurations and / or software configurations performing specific functions. For example, the functional blocks of the present disclosure may be embodied by one or more microprocessors or by circuit configurations for a given function. The functional blocks of the present disclosure may be embodied by various programming languages or scripting languages. The functional blocks of the present disclosure may be embodied by algorithms executed by one or more processors. The functions performed by the functional blocks of the present disclosure may be performed by multiple functional blocks, or the functions performed by multiple functional blocks in the present disclosure may be performed by one functional block. In addition, the present disclosure may employ conventional techniques for electronic configuration, signal processing, and / or data processing, etc.
[0023] 1 and 2 are diagrams illustrating a schematic structure of an energy storage system (ESS) communication system according to an embodiment of the present invention, and FIG 3 is a diagram illustrating components of a battery management system (BMS) according to an embodiment of the present invention.
[0024] 1 and 2, an ESS communication system 1 according to an embodiment of the present invention also includes an ESS operation inter-layer communication system. For example, as shown in FIG. 1, the ESS communication system 1 according to an embodiment of the present invention is an ESS operation inter-layer communication system including an enterprise management system (EMS) 10, a system BMS 20, and a rack BMS 30.
[0025] The communication structure of the ESS communication system 1 according to one embodiment of the present invention is such that the EMS 10 for managing operations of customers is at the top of the communication structure, there is a System BMS 20 that communicates with the EMS 10, and the System BMS 20 collects information from the lower rack BMS 30 and transmits it to the EMS 10.
[0026] 1 and 2, for example, the EMS 10 and the system BMS 20 use TCPIP (transmission control protocol / Internet protocol) communication 12, and the system BMS 20 and the rack BMS 30 are connected using CAN (controller area network) communication 23. Also, as shown in FIG 1, each battery rack may be provided with a rack BMS 30.
[0027] For example, as shown in FIG. 3, a system BMS 20 according to one embodiment of the present invention also includes a communications module 23, a processor 25, and a memory 27.
[0028] The processor 25 may control the system BMS 20. For example, the processor 25 may control communications between the EMS 10, the system BMS 20, and the rack BMS 30.
[0029] For example, the system BMS 20 is also a BMS that controls the overall operation of the ESS communication system 1. For example, the processor 25 may be embodied in a form that selectively includes a processor, an application-specific integrated circuit (ASIC), other chipsets, logic circuits, registers, communication modems, and / or data processing devices known in the art to perform the operations of the system BMS 20. The processor 25 may also perform basic arithmetic, logic, and input / output operations, and may execute program codes stored in a memory, for example. The processor 25 may store data in the memory 27 or load data stored in the memory 27.
[0030] The memory 27 is a recording medium readable by the processor 25, and may include a random access memory (RAM), a read-only memory (ROM), and a permanent mass storage device such as a disk drive. An operating system (OS) and at least one program or application code may be stored in the memory 27. The memory 27 may store program code or data for a communication method according to an embodiment of the present invention.
[0031] The system BMS 20 further includes a communications module 23. For example, as shown in FIG 2, the system BMS 20 can use the communications module 23 to exchange data with the EMS 10 and the rack BMS 30.
[0032] The communication method of the communication module 23 is not limited, and includes not only communication methods that utilize communication networks (for example, mobile communication networks, wired Internet, wireless Internet, and broadcasting networks) that are also included in the network, but also short-distance wireless communication between devices. For example, the communication module 23 can use the TCPIP communication method with the EMS 10. Also, the communication module 23 can use the CAN communication method with the rack BMS 30.
[0033] The system BMS 20 according to the present invention also includes an input / output interface. The input / output interface is a means for interfacing with an input / output device. For example, the input device may include a device such as a keyboard or a mouse, and the output device may include a device such as a display for displaying a communication session of an application. As another example, the input / output interface is a means for interfacing with a device that integrates functions for input and output, such as a touch screen.
[0034] FIG. 4 is a flowchart illustrating an ESS operation inter-layer communication method according to an embodiment of the present invention.
[0035] 4, in step S110, the system BMS 20 according to an embodiment of the present invention may receive a TCPIP communication command including a CAN communication command for controlling the rack BMS from the EMS. For example, the system BMS 20 and the EMS 10 may perform TCPIP communication with each other.
[0036] According to an embodiment of the present invention, the BMS 20 of the system may receive a TCPIP communication command including a CAN communication command including information related to a CAN ID and CAN data in a TCPIP format.
[0037] In addition, the system BMS 20 according to an embodiment of the present invention may receive two TCPIP communication commands mapped to CAN IDs and four TCPIP communication commands mapped to CAN data.
[0038] In step S120, the system BMS 20 according to an embodiment of the present invention may convert the TCPIP format into a CAN format based on the TCPIP communication command and send the converted CAN communication command to the rack BMS. For example, the system BMS 20 and the rack BMS 30 may perform CAN communication with each other.
[0039] In addition, the BMS 20 of the system according to an embodiment of the present invention may transmit a CAN communication command including a CAN ID and CAN data.
[0040] 5 and 6 are diagrams illustrating a method of communication between ESS operation layers according to an embodiment of the present invention.
[0041] According to the present invention, the CAN communication format itself is applied to TCPIP (MODBUS) communication so as to be versatile and not vulnerable to changes and additions of rack BMS commands, and CAN ID and CAN DATA can be directly input by TCPIP communication, and the system BMS simply converts the input TCPIP data to CAN communication immediately, and the EMS simply transmits the Rack BMS change command after recognizing which command it is. In other words, according to the present invention, the system BMS can respond to changes related to rack BMS control commands without any additional firmware changes.
[0042] Previously, a method of allocating one TCPIP command separately and transmitting it via CAN communication was vulnerable to changes in the rack BMS command word, but according to the present invention, it is possible to use six TCPIP commands and include both CAN ID and CAN DATA information, and the EMS can be used as if it were transmitting a CAN communication command by using it, and even if the rack BMS command word is changed or added, the system BMS simply changes the received command from TCPIP communication to CAN communication and transmits it, eliminating the need for separate firmware modifications.
[0043] 5, an example of a TCPIP communication command sent to the system BMS 20 in the EMS 10 according to an embodiment of the present invention is shown, and an example of a CAN communication command sent to the rack BMS 30 in the system BMS 20 according to an embodiment of the present invention is also shown.
[0044] 5, the TCPIP communication command sent from the EMS 10 to the system BMS 20 includes two TCPIP communication commands mapped to CAN IDs and four TCPIP communication commands mapped to CAN data, and the CAN communication command sent from the system BMS 20 to the rack BMS 30 includes a CAN ID and CAN data.
[0045] For example, when issuing a change command to change the number of modules installed in Rack #01 in the first embodiment to five, the TCPIP communication command includes two TCPIP communication command words mapped to the CAN ID (0x0201FF00) and also includes four TCPIP communication command words mapped to the CAN data (06 02 05 00 00 00 00 00).
[0046] In addition, when issuing a forced fan operation command for Rack #03 in the second embodiment, the TCPIP communication command includes two TCPIP communication command words mapped to the CAN ID (0x0203FF00) and also includes four TCPIP communication command words mapped to the CAN data (D4 20 01 00 00 00 00 00).
[0047] In addition, when a Cell Balancing operation command is issued for Rack #02 in the third embodiment, the TCPIP communication command includes two TCPIP communication command words mapped to the CAN ID (0x0202FF00) and also includes four TCPIP communication command words mapped to the CAN data (D4 30 01 00 00 00 00 00).
[0048] 5 and 6, a forced fan operation command for Rack#03 may be initiated in step S210. Then, in step S220, the EMS 10 may transmit a TCPIP communication command including a CAN ID and CAN data to the system BMS 20.
[0049] In step S230, the system BMS 20 may receive from the EMS 10 a TCPIP communication command including two TCPIP communication commands mapped to a CAN ID (0x0203FF00) and four TCPIP communication commands mapped to CAN data (D4 20 01 00 00 00 00 00).
[0050] In step S240, if the system BMS 20 receives two TCPIP communication commands mapped to the CAN ID (0x0203FF00) related to the fan forced operation command of Rack #03 and four TCPIP communication commands mapped to the CAN data (D4 20 01 00 00 00 00 00), the system BMS 20 can transmit the commands to the rack BMS 30 via CAN communication.
[0051] In step S250, the rack BMS 30 may receive a command via CAN communication.
[0052] In steps S260 and S270, the rack BMS 30 may perform a function according to the received command, for example, the rack BMS 30 may perform a function of forcing the fan of Rack#03 to operate.
[0053] According to the present invention, when a command for causing a rack BMS to perform a specific operation is added, the EMS can instruct the rack BMS to perform this command without modifying the firmware of the system BMS.
[0054] In addition, when a command controlled via CAN communication is added to the rack BMS, in order for the EMS to execute the command from the rack BMS, the rack BMS must be directly connected via CAN communication and the EMS must also be provided with a driver capable of CAN communication. Therefore, previously, a command that can be received via TCPIP communication was added to the system BMS, and the command was sent from the EMS to the system BMS, where the system BMS received the command and further transmitted it as a CAN communication command that the rack BMS can receive.
[0055] To improve this, the present invention is configured to instantly convert the TCPIP command structure into a CAN communication structure, so that even if any command is added or changed in the rack BMS, the EMS can instantly send control commands to the rack BMS via TCPIP communication without changing the system BMS's firmware, as long as the EMS is notified of command information. In other words, the system BMS also serves as a converter from TCPIP communication to CAN communication, reducing unnecessary system BMS changes.
[0056] The various embodiments described above are merely examples, and are not to be separated from one another and implemented independently. The embodiments described in this specification may be implemented in a form in which they are combined with one another.
[0057] The various embodiments described above may be embodied in the form of a computer program that can be executed by various components on a computer, and such a computer program may be recorded on a computer-readable medium. In this case, the medium may continuously store the computer-executable program or may temporarily store it for execution or download. The medium may be various recording or storage means in the form of a single or multiple pieces of hardware combined, and is not limited to a medium directly connected to a computer system, but may also be distributed on a network. Examples of the medium include magnetic media such as hard disks, floppy disks, and magnetic tapes; optical recording media such as compact disc read only memory (CD-ROM) and digital versatile disc (DVD); magneto-optical recording media such as floptical disks; and ROM, RAM, flash memory, etc., configured to store program instructions. Examples of other media include recording media or storage media managed by app stores that distribute applications, and sites and servers that supply or distribute various other software.
[0058] In this specification, a "module" or "unit" may be a hardware component such as a processor or a circuit, and / or a software component executed by a hardware component such as a processor. For example, a "module" or "unit" may be embodied by a software component, an object-oriented software component, a component such as a class component, and a task component, as well as a process, a function, an attribute, a procedure, a subroutine, a segment of program code, a driver, firmware, microcode, a circuit, data, a database, a data structure, a table, an array, and a variable.
[0059] The above description of the present invention is for illustrative purposes only, and those skilled in the art will understand that the present invention can be easily modified into other specific forms without changing the technical idea or essential features of the present invention. Therefore, the above-described embodiments should be understood to be illustrative and not limiting in all respects. For example, each component described as a single type may be implemented in a distributed form, and similarly, each component described as distributed may be implemented in a combined form.
[0060] The scope of the present invention is defined by the claims rather than the above detailed description, and all modifications and variations that fall within the meaning, scope, and equivalent concepts of the claims should be construed as being included within the scope of the present invention. [Explanation of symbols]
[0061] 1: ESS (energy storage system) communication system 10:EMS(energy management system) 20: System BMS (battery management system) 30: Rack BMS
Claims
1. A method for mutual communication among an enterprise management system (EMS), a battery management system (BMS) and a rack BMS provided in an energy storage system (ESS), comprising: receiving, from the EMS, a transmission control protocol / Internet protocol (TCPIP) communication command including a controller area network (CAN) communication command for controlling the rack BMS; The system BMS converts a TCPIP format into a CAN format based on the TCPIP communication command, and transmits the converted CAN communication command to the rack BMS.
2. The step of receiving a TCPIP communication command comprises: The method of claim 1 , further comprising the step of: said system BMS and said EMS in TCPIP communication with each other.
3. 3. The method of claim 2, wherein receiving the TCPIP communication command comprises receiving the TCPIP communication command in a TCPIP format, the CAN communication command including information related to a CAN ID and CAN data.
4. receiving the TCPIP communication command includes receiving two TCPIP communication commands mapped to a CAN ID and four TCPIP communication commands mapped to CAN data; The method of claim 3 , wherein the transmitting to the rack BMS comprises transmitting the CAN communication command including the CAN ID and the CAN data.
5. The communication method according to claim 1 , wherein the step of transmitting to the rack BMS includes a step in which the system BMS and the rack BMS perform CAN communication with each other.
6. A computer program stored on a recording medium for causing a computing device to carry out the method according to any one of claims 1 to 5.
7. In a system in which an EMS, a system BMS, and a rack BMS provided in an ESS communicate with each other, A communication system including a system BMS that receives a TCPIP communication command including a CAN communication command for controlling the rack BMS from the EMS, converts a TCPIP format into a CAN format based on the TCPIP communication command, and transmits the converted CAN communication command to the rack BMS.
8. The communication system according to claim 7 , wherein the system BMS and the EMS communicate with each other via TCPIP.
9. The communication system of claim 8 , wherein the system BMS receives the TCPIP communication command including a CAN communication command including information related to a CAN ID and CAN data in a TCPIP format.
10. 10. The communication system of claim 9, wherein the system BMS receives two TCPIP communication commands mapped to a CAN ID and four TCPIP communication commands mapped to CAN data, and transmits the CAN communication command including the CAN ID and the CAN data.
11. The communication system according to claim 7 , wherein the system BMS and the rack BMS perform CAN communication with each other.