Battery management device and energy storage system

Abstract

This application discloses a battery management device and energy storage system, relating to the field of battery management technology. The battery management device includes: a main control module integrating an LWIP protocol stack and a BMS (Battery Management System) function; and a communication module coupled to the main control module. The main control module determines a communication protocol using the LWIP protocol stack and outputs the communication protocol to the communication module, which then performs data transmission based on the communication protocol. By integrating the LWIP protocol stack and BMS function within the main control module, and utilizing the LWIP protocol stack to achieve multi-protocol network communication, this application is suitable for network communication needs in various scenarios and reduces the device's footprint and operating costs through high integration.

Description

Technical Field

[0001] This application relates to the field of battery management technology, and in particular to a battery management device and energy storage system. Background Technology

[0002] With the rapid development of new energy technologies, battery management systems (BMS) have become a core component in electric vehicles, energy storage systems, and other fields. BMS is responsible for monitoring battery status, ensuring safe operation, and extending battery life. Traditional BMS often use CAN bus or serial communication for data exchange, but these methods suffer from problems such as short transmission distance, limited bandwidth, and poor interconnectivity.

[0003] Traditional battery management systems (BMS) rely on independent communication devices (such as Wi-Fi or Ethernet chips) to achieve data transmission, resulting in high hardware costs, system complexity, and poor protocol compatibility. Summary of the Invention

[0004] The main purpose of this application is to propose a solution that addresses the problems of high hardware costs, system complexity, and poor protocol compatibility caused by the reliance on independent communication devices for data communication in traditional battery management systems.

[0005] To achieve the above objectives, the battery management device proposed in this application includes: a main control module, which integrates an LWIP protocol stack and BMS functions; and a communication module coupled to the main control module. The main control module is used to determine the communication protocol through the LWIP protocol stack and output the communication protocol to the communication module, and the communication module performs data transmission based on the communication protocol.

[0006] In one embodiment, the battery management device further includes: a data acquisition module, one end of which is coupled to the battery module and the other end of which is coupled to the main control module; wherein the data acquisition module is used to acquire voltage data, current data and temperature data of the battery module in real time and transmit them to the main control module.

[0007] In one embodiment, the battery management device further includes a protection module, one end of which is coupled to the main control module and the other end of which is coupled to the battery module; wherein the protection module is used to disconnect and isolate the battery module when it detects overcharging, over-discharging, or over-temperature of the battery module.

[0008] In one embodiment, the battery management device further includes a power module coupled to the main control module and the communication module, the power module being used to supply power to the main control module and the communication module.

[0009] In one implementation, the LWIP protocol stack is configured to support multi-protocol parallel processing.

[0010] In one implementation, the multi-protocol parallel processing includes: TCP / IP protocol for reliable data transmission, HTTP / HTTPS protocol for web service interfaces, MQTT protocol for cloud data push, UDP protocol for real-time data broadcasting, SNMP protocol for network device management, and MODBUS-TCP protocol for industrial equipment interconnection.

[0011] In one embodiment, the main control module includes: a microcontroller; a memory coupled to the microcontroller, the memory storing an LWIP protocol stack and an algorithm for performing BMS functions; wherein, the microcontroller performs communication functions and battery management based on the LWIP protocol stack and the algorithm for performing BMS functions.

[0012] In one implementation, the microcontroller integrates a MAC core and a PHY chip.

[0013] In one implementation, the microcontroller is an ARM Cortex-M4 series STM32F407VGT6 microcontroller with a main frequency of 168MHz, supporting hardware floating-point arithmetic (FPU) and DSP instructions.

[0014] This application also proposes an energy storage system comprising: a battery module; and a battery management device coupled to the battery module, wherein the battery management device is the battery management device described in any of the embodiments above.

[0015] The technical solution of this application integrates the LWIP protocol stack and BMS function into the main control module, and uses the LWIP protocol stack to realize multi-protocol network communication function, which is suitable for network communication needs in various scenarios, and reduces the equipment's footprint and usage cost in a highly integrated manner. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on the structures shown in these drawings without creative effort.

[0017] Figure 1 This is a schematic diagram of the structure of the first embodiment of the battery management device provided in this application.

[0018] Figure 2 This is a schematic diagram of the structure of the second embodiment of the battery management device provided in this application.

[0019] Figure 3 This is a schematic diagram of the third embodiment of the battery management device provided in this application.

[0020] Figure 4 This is a schematic diagram of the structure of the second embodiment of the battery management device provided in this application.

[0021] Figure 5 This is a schematic diagram of the structure of an embodiment of the main control module provided in this application.

[0022] Figure 6 This is a schematic diagram of an embodiment of the energy storage system provided in this application.

[0023] Explanation of icon numbers:

[0024] 100. Battery management device; 1. Main control module; 2. Communication module; 3. Data acquisition module; 4. Battery module; 5. Protection module; 6. Power supply module; 11. Microcontroller; 12. Memory.

[0025] 200. Energy storage system.

[0026] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0027] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0028] It should be noted that if the embodiments of this application involve directional indicators (such as up, down, left, right, front, back, etc.), the directional indicators are only used to explain the relative positional relationship and movement of the components in a specific posture. If the specific posture changes, the directional indicators will also change accordingly.

[0029] Furthermore, if the embodiments of this application involve descriptions such as "first" or "second," these descriptions are for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first" or "second" may explicitly or implicitly include at least one of those features. Additionally, the use of "and / or" or "and / or" throughout the text includes three parallel solutions. For example, "A and / or B" includes solution A, solution B, or a solution that simultaneously satisfies A and B. Furthermore, the technical solutions of the various embodiments can be combined with each other, but this must be based on the ability of those skilled in the art to implement them. When the combination of technical solutions is contradictory or impossible to implement, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection claimed in this application.

[0030] Existing solutions struggle to simultaneously support multiple network protocols (such as TCP / UDP / IPv6) in resource-constrained embedded devices, and multi-chip integration increases power consumption and size. The LWIP protocol stack (Lightweight IP protocol stack) provides complete TCP / IP functionality for embedded systems, offering advantages such as low resource consumption, high portability, and multi-protocol support, making it highly suitable for BMS applications. However, current technologies lack a BMS solution that fully utilizes LWIP to address the shortcomings of existing BMS systems in remote monitoring, real-time performance, and interoperability.

[0031] Therefore, this application proposes a battery management device and an energy storage system to solve the above problems.

[0032] It should be noted that LWIP (LightWeightIP) is a lightweight TCP / IP protocol stack designed specifically for embedded systems. It solves the problems of bloated code and high memory consumption of general TCP / IP protocol stacks (such as protocol stacks on PCs), which cannot run on resource-constrained devices such as microcontrollers / embedded MCUs. It is the standard protocol stack for embedded Ethernet development.

[0033] Please see Figure 1 As shown, Figure 1 This is a schematic diagram of the structure of the first embodiment of the battery management device provided in this application; in one embodiment of this application, the battery management device 100 includes: a main control module 1, which integrates an LWIP protocol stack and BMS functions; and a communication module 2, which is coupled to the main control module 1; wherein, the main control module 1 is used to determine the communication protocol through the LWIP protocol stack and output the communication protocol to the communication module 2, and the communication module 2 performs data transmission based on the communication protocol.

[0034] It should be noted that LWIP (LightWeightIP) is a lightweight TCP / IP protocol stack designed specifically for embedded systems. The BMS function refers to the Battery Management System, a deeply integrated hardware and software intelligent control system designed for rechargeable batteries (such as lithium batteries). As the core hub between the battery pack and the power-consuming equipment / charger, its core mission is to ensure battery safety throughout its entire lifecycle, extend its service life, optimize charge and discharge performance, and achieve accurate monitoring and intelligent management of battery status. It is a core and essential component for the large-scale application of lithium batteries in new energy vehicles, energy storage, industrial equipment, and consumer electronics.

[0035] The technical solution of this application integrates the LWIP protocol stack and BMS function in the main control module 1, and uses the LWIP protocol stack to realize multi-protocol network communication function, which is suitable for network communication needs in various scenarios, and reduces the equipment's footprint and usage cost in a highly integrated manner.

[0036] In one embodiment, such as Figure 2 As shown, Figure 2 This is a schematic diagram of the structure of the second embodiment of the battery management device provided in this application; the battery management device 100 further includes: a data acquisition module 3, one end of which is coupled to the battery module 4, and the other end of which is coupled to the main control module 1; wherein, the data acquisition module 3 is used to acquire the voltage data, current data and temperature data of the battery module 4 in real time, and transmit them to the main control module 1.

[0037] The battery module 4 is monitored in real time by the acquisition module 3 to collect various parameter data, thereby managing the battery module 4 based on the various parameter data.

[0038] In one embodiment, such as Figure 3 As shown, Figure 3 This is a schematic diagram of the structure of the third embodiment of the battery management device provided in this application; the battery management device 100 further includes: a protection module 6, one end of the protection module 6 is coupled to the main control module 1, and the other end of the protection module 6 is coupled to the battery module 4; wherein, the protection module 6 is used to cut off and isolate the battery module 4 when it detects that the battery module 4 is overcharged, over-discharged, or over-temperatured.

[0039] By setting up the protection module 6 in the above manner, when the protection module 6 detects abnormal conditions such as overcharging, over-discharging, and over-temperature of the battery module 4, it can promptly disconnect the coupling between the battery and the main control module 1, thereby preventing further damage to the main control module 1 when the battery module 4 is abnormal, and effectively protecting the safety of the equipment.

[0040] In one embodiment, such as Figure 4 As shown, Figure 4 This is a schematic diagram of the structure of the second embodiment of the battery management device provided in this application; the battery management device 100 further includes: a power module, which is coupled to the main control module 1 and the communication module 2, and is used to supply power to the main control module 1 and the communication module 2.

[0041] It is understandable that the power module in other embodiments can also supply power to other accessory modules so that the other accessory modules can operate normally.

[0042] In one embodiment, the LWIP protocol stack is configured to support multi-protocol parallel processing.

[0043] Understandably, the multi-protocol parallel processing of the LWIP protocol stack enables embedded devices (such as BMS, industrial sensors, and IoT terminals) to simultaneously meet the communication needs of multiple scenarios, including industrial interconnection, cloud push, real-time broadcasting, device management, and web access, while taking into account communication real-time performance, system stability, and development / networking flexibility, under the premise of limited microcontroller resources.

[0044] The above methods meet the integrated communication needs of embedded devices in multiple scenarios without the need for additional external communication devices; they take into account the communication requirements of different protocols, ensuring that real-time performance and reliability do not block each other; they are lightweight and parallel, without consuming too many microcontroller resources, and are adapted to the characteristics of embedded hardware; they isolate faults between protocols, ensuring that an anomaly in a single protocol does not paralyze the entire communication system; they improve the flexibility and scalability of development and engineering networking; and they realize an integrated communication closed loop of "local + remote, control + management, debugging + operation and maintenance".

[0045] In one embodiment, the multi-protocol parallel processing includes: TCP / IP protocol for reliable data transmission, HTTP / HTTPS protocol for web service interfaces, MQTT protocol for cloud data push, UDP protocol for real-time data broadcasting, SNMP protocol for network device management, and MODBUS-TCP protocol for industrial equipment interconnection.

[0046] It's important to note that the combination of TCP (Transmission Control Protocol) and IP (Internet Protocol) is the underlying foundation for all reliable application layer protocols. IP handles addressing, while TCP ensures reliable transmission. HTTP (Hypertext Transfer Protocol) / HTTPS (Secure Hypertext Transfer Protocol) is an application layer protocol based on TCP, specifically designed for request-response interactions in web services. It's a common standard for embedded devices to connect to cloud web servers and access browsers. MQTT (Message Queuing Telemetry Transport) is a lightweight application layer protocol based on TCP / IP, designed for IoT devices (microcontrollers / BMS / sensors), addressing the pain points of resource constraints, low bandwidth, low power consumption, and multi-device networking in cloud push applications. UDP (User Datagram Protocol) is a connectionless, unreliable data packet transmission protocol at the transport layer. Complementing TCP, it sacrifices reliability for extremely low latency and real-time performance, making it the preferred choice for real-time data broadcasting and high-frequency short data transmission. SNMP (Simple Network Management Protocol) is an application layer protocol based on UDP (adaptable to TCP), designed for unified management, status monitoring, and fault alarms of network / industrial equipment. It's a common standard for equipment operation and maintenance management in industrial / network scenarios. MODBUS-TCP is an application-layer industrial protocol based on TCP / IP. It evolved from the traditional serial port MODBUS (RTU / ASCII) adapted to Ethernet and is a universal standard for interconnecting industrial field devices (the "common language" of the industrial field).

[0047] Understandably, by developing a lightweight web server, using the HTTP protocol for interaction, employing the SNMP protocol for the UDP client, and optionally using the TCP MODBUS and MQTT protocols for the TCP server, remote battery status monitoring, firmware upgrades, and fault alarms can be achieved. Data transmission supports encryption protocols to ensure security.

[0048] In one embodiment, such as Figure 5 As shown, Figure 5 This is a schematic diagram of the structure of an embodiment of the main control module provided in this application; the main control module 1 includes: a microcontroller 11; a memory 12, the memory 12 being coupled to the microcontroller 11, the memory 12 storing the LWIP protocol stack and the algorithm for performing BMS functions; wherein, the microcontroller 11 performs communication functions and battery management based on the LWIP protocol stack and the algorithm for performing BMS functions.

[0049] Understandably, in some other embodiments, in order to further reduce the occupied PCB area, the main control module 1 is directly implemented using a microcontroller 11, wherein files such as the LWIP protocol stack and the algorithm for executing the BMS function are directly stored in the firmware of the microcontroller 11.

[0050] In one embodiment, the microcontroller 11 integrates a MAC core and a PHY chip.

[0051] It should be noted that the MAC kernel (Media Access Control layer) belongs to the lower half of the data link layer and is a logical functional module (not an independent hardware chip). Essentially, it is a set of hardware logic or software protocols responsible for Ethernet data frame processing. The PHY chip (Physical Layer Chip) belongs to the physical layer of the OSI model and is an independent hardware chip responsible for processing the physical electrical signals of Ethernet communication.

[0052] Understandably, the MAC kernel and PHY chip are the two core components of an Ethernet communication system, corresponding to the data link layer and physical layer of the OSI seven-layer network model, respectively. They work together to convert and transmit "digital data" into "physical electrical signals." In simpler terms, the MAC kernel is the "traffic controller," responsible for the rules and logic of data transmission and reception; the PHY chip is the "signal converter," responsible for the physical transmission and reception of electrical signals.

[0053] By integrating the MAC core and PHY chip into the microcontroller 11, battery data acquisition, processing, and network communication functions can be achieved with a single chip, which helps save on equipment hardware costs. Based on this, combined with the LWIP protocol stack and other included protocols, the BMS can meet all communication needs across industrial field interconnection and IoT cloud push.

[0054] In one embodiment, the microcontroller 11 is an ARM Cortex-M4 series STM32F407VGT6 microcontroller 11 with a main frequency of 168MHz, supporting hardware floating-point arithmetic (FPU) and DSP instructions.

[0055] It should be noted that the hardware floating-point unit (FPU) is a dedicated hardware arithmetic unit integrated into the CPU core of the microcontroller 11. It is specifically responsible for handling addition, subtraction, multiplication, division, square root, and trigonometric function operations of floating-point numbers (float / double), replacing traditional software-simulated floating-point operations and achieving high-speed floating-point calculations at the hardware level. The DSP instructions (DSP Extension, Digital Signal Processing Instruction Set) are dedicated hardware instruction set extensions designed for digital signal processing by the microcontroller 11 CPU core. They are not independent hardware modules, but rather, based on ordinary CPU instructions, a batch of optimized instructions for typical digital signal processing operations are added, allowing these operations to be completed in a single cycle, significantly improving the efficiency of digital signal processing.

[0056] The microcontroller 11 described above can efficiently handle real-time data sampling and multi-protocol communication tasks of the battery management system. In another embodiment, the microcontroller 11 is equipped with 1MB Flash and 192KB RAM, enabling the complete deployment of the LWIP protocol stack and complex battery algorithms without the need for external storage chips, thus reducing hardware costs. It has a built-in 10 / 100Mbps Ethernet MAC, directly supporting TCP / UDP / HTTP / IPv6 protocols of the LWIP protocol stack. The LWIP protocol stack is directly integrated into the microcontroller 11 firmware, eliminating the need for an external protocol processing chip.

[0057] This application also proposes an energy storage system 200, such as Figure 6 As shown, Figure 6 This is a schematic diagram of an embodiment of the energy storage system provided in this application. Specifically, the energy storage system 200 includes a battery module 4 and a battery management device 100. The specific structure of the battery management device 100 is as described in the above embodiment. Since the energy storage system 200 adopts all the technical solutions of all the above embodiments, it has at least all the beneficial effects brought about by the technical solutions of the above embodiments, which will not be described in detail here.

[0058] This application provides a battery management device 100 and an energy storage system 200, which integrates an LWIP protocol stack and BMS functions within the main control module 1. The LWIP protocol stack is used to realize multi-protocol network communication functions, which is suitable for network communication needs in various scenarios. It also reduces the device's footprint and operating costs with a high degree of integration. Furthermore, the LWIP-based support for multiple network protocols can effectively improve system compatibility and flexibility. Moreover, the open-source LWIP protocol stack can simplify the development process, shorten the development cycle, and make it easier for designers to develop.

[0059] The above description is merely an exemplary embodiment of this application and does not limit the patent scope of this application. Any equivalent structural transformations made based on the technical concept of this application and the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included within the patent protection scope of this application.

Claims

1. A battery management device, characterized in that, The battery management device includes: The main control module integrates the LWIP protocol stack and BMS functionality. A communication module, which is coupled to the main control module; The main control module is used to determine the communication protocol through the LWIP protocol stack and output the communication protocol to the communication module, and the communication module performs data transmission based on the communication protocol.

2. The battery management device as claimed in claim 1, characterized in that, The battery management device further includes: A data acquisition module, one end of which is coupled to the battery module, and the other end of which is coupled to the main control module; The acquisition module is used to acquire the voltage, current and temperature data of the battery module in real time and transmit them to the main control module.

3. The battery management device as described in claim 1, characterized in that, The battery management device further includes: A protection module, one end of which is coupled to the main control module, and the other end of which is coupled to the battery module; The protection module is used to disconnect and isolate the battery module when it detects overcharging, over-discharging, or overheating.

4. The battery management device as claimed in claim 1, characterized in that, The battery management device further includes: A power module is coupled to the main control module and the communication module, and the power module is used to supply power to the main control module and the communication module.

5. The battery management device as claimed in claim 1, characterized in that, The LWIP protocol stack is configured to support parallel processing of multiple protocols.

6. The battery management device as claimed in claim 5, characterized in that, The multi-protocol parallel processing includes: TCP / IP protocol for reliable data transmission, HTTP / HTTPS protocol for web service interfaces, MQTT protocol for cloud data push, UDP protocol for real-time data broadcasting, SNMP protocol for network device management, and MODBUS-TCP protocol for industrial equipment interconnection.

7. The battery management device as claimed in claim 1, characterized in that, The main control module includes: Microcontroller; The memory is coupled to the microcontroller and stores the LWIP protocol stack and the algorithm for executing the BMS function. The microcontroller performs communication functions and battery management based on the LWIP protocol stack and the algorithm for executing the BMS function.

8. The battery management device as claimed in claim 7, characterized in that, The microcontroller integrates a MAC kernel and a PHY chip.

9. The battery management device as claimed in claim 8, characterized in that, The microcontroller is an ARM Cortex-M4 series STM32F407VGT6 microcontroller with a main frequency of 168MHz, supporting hardware floating-point arithmetic (FPU) and DSP instructions.

10. An energy storage system, characterized in that, The energy storage system includes: Battery module; A battery management device coupled to the battery module, wherein the battery management device is the battery management device as claimed in any one of claims 1-9.

Images