Management system and method for power supply and energy storage battery networking

Abstract

An embodiment of the present invention provides a management system for a network of power supplies and energy storage batteries, comprising: multiple groups of energy storage batteries, a site control unit (SCU), and a centralized monitoring unit (CSU). The multiple groups of energy storage batteries form one or more battery clusters, each of which is connected to the SCU via an RS485 interface. The CSU is used to manage the power supply and is connected to the SCU via a northbound interface to send power supply data to the SCU. The SCU is used to manage the multiple groups of energy storage batteries and is connected to the CSU via a southbound interface to obtain power supply data from the CSU. The SCU is connected to a network management system via an Ethernet interface to send battery data and power supply data of the multiple groups of energy storage batteries to the network management system and receive instructions from the network management system. In this embodiment of the present invention, the power control unit (CSU) is responsible for power management, while the site control unit (SCU) is responsible for battery management. This decouples power management from battery management, thereby resolving the issue of power supply and battery version coupling.

Description

Technical Field

[0001] The present invention relates to the field of battery energy storage, and in particular to a management system and method for networking power sources and energy storage batteries. Background Art

[0002] With the large-scale construction of 5G networks and the trend of "lead out, lithium in" in the context of dual carbon emissions, the installed base of lithium batteries for communications energy storage is expanding, and market demand for paralleling multiple lithium battery groups is rapidly increasing. For parallel lithium battery systems, a common approach is to connect the batteries in parallel via the Controller Area Network (CAN) bus and the RS485 bus. The power supply is connected to the same bus as the battery pack via RS485, with the power supply managing the batteries. However, this approach requires the power supply to not only provide power services but also be able to interface and manage the lithium batteries, resulting in a strong coupling between the power supply and battery services. Due to the large number of lithium battery manufacturers and the lack of a unified protocol definition, power supplies are forced to be compatible with a wide range of lithium battery models, resulting in a large number of customized versions and a version explosion. Furthermore, due to signal attenuation, the number of RS485 master-slave parallel systems cannot exceed 32 groups. Therefore, this parallel network structure can only support a maximum of 32 lithium battery groups, which is difficult to meet the current large-scale networking requirements. One approach to improvement is to expand the power supply's access points or add external serial port repeaters to enhance the power supply's access capabilities. However, the power supply itself is limited by its standard form factor, and its access capacity expansion is very limited. It cannot support large-scale lithium battery networking needs. Solutions like external repeaters lack parallel management on the power supply side, making it difficult to meet battery management efficiency requirements. Furthermore, these improvements fail to address the coupling issue between power supply and battery services, and the impact on the power supply remains significant. Another approach is to use site collectors, connecting both batteries and power supplies to the collector. This approach solves the problem of large-scale battery networking. However, since collectors are primarily used for site access and lack basic services like battery current sharing, software customization is required. Furthermore, site collectors are typically much more expensive than power supplies, making them less cost-competitive when only a small number of batteries are available.

[0003] From the above analysis, it can be seen that the key to networking communication energy storage and communication power lies in solving the problem of large-scale communication energy storage battery networking with more than 32 groups and solving the problem of decoupling power supply and battery services. Summary of the Invention

[0004] The embodiments of the present invention provide a management system and method for a power supply and energy storage battery network, so as to at least solve the problem of decoupling power supply and battery services in related technologies.

[0005] According to one embodiment of the present invention, a management system for a power supply and energy storage battery network is provided, comprising: multiple groups of energy storage batteries, a site control unit (SCU) and a centralized supervision unit (CSU), wherein the multiple groups of energy storage batteries form one or more battery clusters, each of which is connected to the SCU via an RS485 interface; the CSU is used to manage the power supply and is connected to the SCU via a northbound interface to send power supply data to the SCU; the SCU is used to manage the multiple groups of energy storage batteries, is connected to the CSU via a southbound interface to obtain power supply data from the CSU, and is connected to a network management system via an Ethernet interface to send battery data and power supply data of the multiple groups of energy storage batteries to the network management system and receive instructions from the network management system.

[0006] In an exemplary embodiment, each battery cluster includes a group of main energy storage batteries and one or more groups of slave energy storage batteries. The groups of energy storage batteries in each battery cluster are connected via a first CAN link for current sharing among the groups of energy storage batteries within the battery cluster. The main energy storage batteries in each battery cluster are connected via a second CAN link for current sharing among the groups of energy storage batteries between the battery clusters.

[0007] In an exemplary embodiment, when there is only one battery cluster, the SCU software runs on the hardware of the CSU and obtains the power data of the CSU through an inter-process socket. When there are multiple battery clusters, the SCU runs on independent hardware and obtains the power data of the CSU through a network socket.

[0008] According to another embodiment of the present invention, a method for managing a power supply and energy storage battery network is provided. The method is applied to the system of the above embodiment to provide a communication mechanism between a CSU and an SCU. The management method includes: when the CSU is started, checking whether the CSU has an SCU configuration mark; if the CSU has the SCU configuration mark, the CSU starts its own northbound transmission process and uses a network socket to pass power data to the SCU; if the CSU does not have the SCU configuration mark, the CSU starts the SCU process, and both the SCU and the CSU run on power supply hardware. After the SCU is started, it is uniformly managed by the CSU.

[0009] According to another embodiment of the present invention, a method for managing a power supply and energy storage battery network is provided. The method is applied to the system of the above embodiment and includes: upon power-on, each energy storage battery defaults to a preset initial address and broadcasts an address contention message on a first CAN link of the battery cluster in which it is located; determining a pending master energy storage battery based on whether a response to the address contention message is received from other energy storage batteries; and checking data frames received by the pending master energy storage battery from other battery clusters, and determining whether the pending master energy storage battery is the final master energy storage battery based on whether the data frames contain second CAN link information.

[0010] According to yet another embodiment of the present invention, a computer-readable storage medium is provided, in which a computer program is stored. The computer program is configured to execute the steps of any one of the above method embodiments when run.

[0011] According to another embodiment of the present invention, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to perform the steps in any one of the above method embodiments.

[0012] In the above embodiment of the present invention, the power control unit CSU is responsible for power management services, and the site control unit SCU is responsible for battery management services. Therefore, power management and battery management are decoupled, thereby solving the problem of power and battery version coupling. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 is a schematic diagram of a power supply and energy storage battery networking scenario according to an embodiment of the present invention;

[0014] Figure 2 is a schematic structural diagram of an SCU according to an embodiment of the present invention;

[0015] Figure 3 Schematic diagram of a communication power supply and communication energy storage networking scenario according to an embodiment of the present invention;

[0016] Figure 4 2. This is a schematic diagram of a multi-cluster battery parallel connection and communication power supply network according to an embodiment of the present invention;

[0017] Figure 5 This is a schematic diagram of a single battery cluster and a communication power supply network according to an embodiment of the present invention;

[0018] Figure 6 is a flow chart of communication between a CSU and an SCU according to an embodiment of the present invention;

[0019] Figure 74 is a flowchart of internal address competition in an energy storage battery according to an embodiment of the present invention. DETAILED DESCRIPTION

[0020] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings and in combination with embodiments.

[0021] To overcome the shortcomings of current communication energy storage networking solutions, address the technical issues of limited communication power supply battery access management capabilities in traditional solutions, which cannot meet the needs of large-scale energy storage battery networking, and alleviate the difficulties of coupling power and battery services, such as the numerous power supply versions and the difficulty in quickly supporting new battery services for customers, the following embodiments of the present invention provide a communication power supply, energy storage battery, and SCU to achieve decoupling and large-scale access of power and battery services. Through the SCU and CSU hardware and software design and socket design, flexible networking of various capacity batteries can be achieved at low cost and low resources. The overall solution offers significant advantages such as flexibility, good scalability, easy deployment, and low cost.

[0022] In this embodiment, a management system for power supply and energy storage battery networking is provided. Figure 1 : is a schematic diagram of a system structure according to an embodiment of the present invention, such as Figure 1 As shown, the management system includes: multiple groups of energy storage batteries, a site control unit SCU and a centralized monitoring unit CSU, wherein the multiple groups of energy storage batteries form one or more battery clusters, each of which is connected to the SCU via an RS485 interface; the CSU is used to manage the power supply and is connected to the SCU via a northbound interface to send power supply data to the SCU; the SCU is used to manage the multiple groups of energy storage batteries, is connected to the CSU via a southbound interface to obtain power supply data from the CSU, and is connected to the network management system via an Ethernet interface to send the battery data of the multiple groups of energy storage batteries and the power supply data to the network management system and receive instructions from the network management system.

[0023] In the above embodiment, each battery cluster is connected to the SCU via an RS485 interface, and the number of battery clusters is the same as the number of RS485 interfaces.

[0024] In an exemplary embodiment, each battery cluster includes a group of main energy storage batteries and one or more groups of slave energy storage batteries. The groups of energy storage batteries in each battery cluster are connected via a first CAN link for current sharing among the groups of energy storage batteries within the battery cluster. The main energy storage batteries in each battery cluster are connected via a second CAN link for current sharing among the groups of energy storage batteries between the battery clusters.

[0025] In an exemplary embodiment, the SCU includes: a battery system management unit (BSMU), used to manage the multiple groups of energy storage batteries and obtain battery data of the multiple groups of energy storage batteries; a field supervision unit (FSU), used to summarize the power supply data and the battery data; and a site gateway (SGW), used to send the summarized battery data and power supply data to the network management system, and receive instructions from the network management system.

[0026] In an exemplary embodiment, the BSMU adopts multi-threaded parallel management. The number of threads is the same as the number of RS485 interfaces through which the battery clusters are connected to the SCU. Each thread is responsible for accessing and managing a battery cluster connected to the RS485 interface.

[0027] In an exemplary embodiment, the power data is connected from the CSU to the FSU of the SCU via a socket, and the battery data is transferred from the BSMU to the FSU via a shared memory.

[0028] In an exemplary embodiment, when there is only one battery cluster, the SCU software runs on the hardware of the CSU and obtains the power data of the CSU through an inter-process socket. When there are multiple battery clusters, the SCU runs on independent hardware and obtains the power data of the CSU through a network socket.

[0029] An embodiment of the present invention also provides a management system for a parallel network of communication power supplies and communication energy storage systems. This embodiment is applicable to scenarios where a communication power supply is connected to multiple energy storage battery packs. It can support scenarios where a power supply is networked with up to 32 lithium battery packs and paralleled with many more battery packs. It can be applied to scenarios such as communication base stations, core equipment rooms, convergence equipment rooms, and substations.

[0030] like Figure 2As shown, the management system of this embodiment includes multiple groups of communication energy storage batteries (including battery packs and battery management units (BMSs), a supporting communication power control unit (CSU), a site control unit (SCU), an EDM network management system, and other subcomponents. These subcomponents are networked via communication methods such as CAN, RS485, and Ethernet, enabling information flow between layers and parallel networking and management of the communication power supply and communication energy storage batteries. The communication energy storage batteries have an optional CAN2 configuration. Address competition allows the battery equipped with CAN2 to become the master, and inter-cluster current sharing is achieved through host interaction. The power supply CSU separates the energy storage battery management functions and only handles power-related functions. The battery current sharing function is transferred to the communication energy storage battery, while the battery data management function is handled by the SCU. The SCU comprises hardware and software. In addition to the processor, the hardware is equipped with N RS485 ports for interfacing with multiple battery clusters and an Ethernet port for southbound data collection and interaction with the SCU. The SCU software is divided into three modules: the SBMU, the FSU, and the GW, respectively performing battery management, power supply battery information aggregation, and SCU data upload to the network management.

[0031] Specifically, the BSMU is responsible for managing communication energy storage batteries and operates in a multi-threaded manner. The FSU is responsible for interoperating with power and battery services, connecting with the CSU via network sockets or inter-process sockets. The SGW is responsible for connecting with the network management system, transmitting power and battery data, and issuing network management commands.

[0032] The CSU adds or reuses northbound Ethernet ports to enable CSU data to be sent to the SCU via network sockets. The CSU implements inter-process sockets and network sockets, ensuring compatible data transmission between the CSU and SCU in different scenarios. In single-cluster battery scenarios, the SCU software runs on the CSU hardware and obtains CSU data via inter-process sockets. In multi-cluster battery scenarios, the SCU runs on independent hardware and obtains CSU data via network sockets.

[0033] This embodiment involves technical solutions such as power management and battery management decoupling technology, multi-group communication energy storage networking technology, and current sharing between energy storage battery clusters. The technical solutions involved are described below.

[0034] In the technical solution provided in this embodiment, the power management service of the communication power supply is decoupled from the battery management service, wherein the networking of multiple battery groups and battery data management are completed by the SCU, the fusion of power and battery data and uploading to the network management are completed jointly by the CSU and SCU, and the battery current sharing service is completed by the energy storage battery.

[0035] In this embodiment, the SCU hardware includes M RS485 ports for energy storage battery access. Each RS485 port can be used as a cluster of communication energy storage batteries for access. In addition, it can also include several extended serial ports for expanding access capabilities. In addition, the SCU can also include a southbound Ethernet port for interacting with the CSU to obtain power data and a northbound Ethernet port for interacting with the network management EDM.

[0036] like Figure 3 As shown, in this embodiment, the SCU is functionally composed of three components: the BSMU is responsible for energy storage battery service management, the FSU is responsible for battery and power access and other extended access, and the SGW is responsible for sending data to the network application layer and receiving network application layer instructions. The design of each component is as follows:

[0037] (1) BSMU uses multi-threaded parallel management. The number of threads is consistent with the number of RS485 interfaces connected to the energy storage batteries. Each thread is responsible for managing the access and management of a battery cluster connected to the RS485 interface.

[0038] (2) The power data is connected to the FSU module of the SCU via a socket from the CSU, while the battery data is transferred from the BSMU to the FSU via shared memory. This completes the aggregation of power data and battery data at the FSU layer.

[0039] (3) The SGW uses the same link to transmit the power and battery data collected by the FSU to the EDM network management system, which is fully compatible with the original EDM structure.

[0040] In this invention, the CSU handles power management, while battery data management and battery current sharing are transferred to the SCU and energy storage battery. The CSU, which manages power, and the BSMU, which manages battery, are physically isolated, thereby decoupling the power and battery management services. The power supply adds or reuses a northbound Ethernet port for connection to the SCU entity. The CSU transmits power supply data (such as rectifiers and lead-acid batteries) to the SCU via a socket, where it is aggregated and then passed to the EDM.

[0041] In this embodiment, the interaction between the CSU and the SCU may be performed in the following manner:

[0042] like Figure 4 As shown in the figure, for multi-cluster battery access scenarios, configure the SCU hardware entity, communicate with the energy storage battery data through the RS485 serial port on the SCU, and the CSU exchanges data with the SCU through the network socket;

[0043] like Figure 5As shown in the figure, for a single battery cluster access scenario, no SCU hardware entity is configured, and the SCU software is deployed on the CSU hardware. The SCU software communicates with the energy storage battery data through the southbound serial port of the CSU, and the CSU and SCU exchange data through an inter-process socket.

[0044] In this embodiment, the CSU may include an SCU configuration tag, and determine through the tag whether the CSU uses a network socket or an inter-process socket, so as to achieve compatibility between the CSU and the SCU in single-cluster scenarios and multi-cluster scenarios.

[0045] like Figure 6 As shown in the figure, the steps for CSU to use network socket and process socket to achieve compatibility between single-cluster battery and multi-cluster battery scenarios are as follows:

[0046] Step S601: CSU software starts;

[0047] Step S602: Check whether the CSU has an SCU configuration flag;

[0048] Step S603: If the CSU contains the SCU configuration flag, it means that the system has configured the SCU hardware. The CSU starts its own northbound transmission process and transmits the power data to the SCU using the network socket.

[0049] Step S604: If the CSU does not contain the SCU configuration flag, it means that the system is not configured with SCU hardware. Then the CSU starts the SCU process. Both the SCU and the CSU run on the power hardware. After the SCU is started, it is included in the unified management of the CSU.

[0050] Step S605: register the SCU process to the CSU system management process;

[0051] Step S606: The CSU starts its own northbound transmission process and communicates with relevant components in the SCU software using an inter-process socket.

[0052] Step S607: Based on step S604, the CSU checks whether the SCU is running normally through heartbeat messages;

[0053] Step S608: If the SCU heartbeat is not detected, the CSU will try to restart the SCU process;

[0054] Step S609: If the SCU fails to recover after multiple attempts, the CSU generates an SCU function abnormality alarm and takes over the network management parameters in the SCU. The CSU northbound transmission process directly transmits basic power data to the network management.

[0055] In this embodiment, the communication energy storage batteries are all configured with two RS485 interfaces and one CAN interface (CAN1); based on this configuration, each cluster selects another battery to configure the second CAN interface (CAN2). The single cluster battery completes address allocation through address competition to determine the master and slave. The RS485 of the slave is used for parallel connection of battery clusters, the RS485 of the host is used for parallel connection, and one RS485 is connected to the serial port of the SCU for battery cluster data exchange. Within a single cluster, the master and slave machines use CAN1 to balance the current within the cluster; the current balancing between clusters is completed by the hosts of each cluster, and the current balancing method is the same as the current balancing method within the cluster. Battery current balancing technology is a common method in the industry and will not be described in detail here.

[0056] The embodiment of the present invention also provides a battery address competition technology to ensure that the battery configured with CAN2 competes for the battery cluster master. Figure 7 The specific steps are as follows:

[0057] Step S701: The battery is powered on, the default address is 1, and an address competition command is actively sent, for example, three times, on the battery cluster CAN1 link in a broadcast mode;

[0058] Step S702: Determine whether a response to the address contention is received. If no response is received, execute step S703. If a response is received, execute step S704.

[0059] Step S703: If there is no response, maintain the current address;

[0060] Step S704: If there is a response, the battery address is incremented by 1 based on the current address, and the address competition command is resent three times;

[0061] Step S705: Based on step S702, further determine whether the battery address is 1;

[0062] Step S706: If the battery address is 1, the battery is used as a pending host to process host contention information;

[0063] Step S707: Process the address contention information and check whether the received data frame contains CAN2 information. If the received data frame does not contain CAN2 information, the battery address remains unchanged; if the received data frame contains CAN2 information, it means that the battery with CAN2 is competing for the host, so the battery address is increased by 1 and the address contention command is resent three times.

[0064] Through the above steps, the batteries with CAN2 in the battery cluster compete to become the master. Each cluster master completes inter-cluster current sharing through CAN2 and completes intra-cluster current sharing through CAN1. This achieves the transfer of the communication energy storage battery's current sharing service from the CSU to the energy storage battery device.

[0065] In the aforementioned embodiments of the present invention, when multiple energy storage battery clusters are connected in parallel, an SCU device is added to change the traditional power supply configuration. This allows for reuse of existing power supplies while expanding battery capacity, adapting to a wider range of user needs. Furthermore, the SCU's multi-threaded management of multiple battery clusters significantly improves battery management efficiency, resulting in greater real-time data availability and more refined management, effectively enhancing the user experience. Furthermore, the energy storage batteries form an independent energy storage plane, offering higher current sharing efficiency. In extreme scenarios, even if the control plane is damaged, battery operation remains unaffected, providing a noticeable improvement to the user experience.

[0066] In order to facilitate further understanding of the technical solutions provided by the above embodiments of the present invention, a detailed description will be given below in conjunction with specific scenario embodiments.

[0067] Example 1

[0068] In this embodiment, communication energy storage lithium batteries ranging from a minimum of 10 groups to a maximum of 120 groups are provided, which are matched with rectifiers or photovoltaic plug-ins of different capacities to form communication power supply systems with various configurations. These systems are applied to various scenarios such as core equipment rooms and aggregation equipment rooms to meet the power and backup power needs of base stations at multiple sites.

[0069] To facilitate remote management and maintenance of the communication power system, the power system must be connected to the network management system. However, due to limited IP resources, the power system (including power supply and battery) at each site only uses one IP resource.

[0070] This implementation uses an SCU device (e.g., configured with six southbound RS485 ports, one southbound Ethernet port, and one northbound Ethernet port) to solve the problem of networking 120 battery packs and decoupling power and battery management services. To address these issues, the present invention provides design and operational implementation steps.

[0071] Design implementation steps:

[0072] S1: Analyze the power supply and battery configuration of the site to be networked and determine the network design. Based on the current design of battery cabinets, a single battery cabinet can accommodate a maximum of 10 battery groups. Therefore, the batteries in this implementation are divided into 12 battery cabinets. To facilitate on-site battery signal line connection and subsequent maintenance, it is necessary to ensure that the batteries in the same cabinet are connected to a single RS485 bus, while also making full use of the parallel processing capabilities of the SCU to improve battery data processing efficiency. Therefore, the 20 battery groups in two battery cabinets are connected to one RS485 bus. That is, 120 battery groups are ultimately connected to the SCU's 6 RS485 ports, the power supply CSU is connected to the SCU via the southbound Ethernet port, and the SCU is connected to the network management system via the northbound Ethernet port.

[0073] S2: CSU design and deployment:

[0074] The CSU includes power management and interaction with the SCU. It offloads current sharing and data management services from the communication energy storage battery in the traditional power supply to the SCU and energy storage battery device, respectively. The CSU's southbound RS485 port does not connect to the energy storage battery, physically decoupling power and battery management. The CSU software collects power supply information (such as DC power distribution, AC power distribution, and rectifiers) as well as information about the lead-acid batteries directly connected to the power supply. The CSU transmits this collected data to the SCU via a network socket, reusing the power supply's native northbound protocol, 1104.

[0075] S3:SCU design and deployment:

[0076] The SCU includes six southbound RS485 interfaces, one southbound Ethernet port, and one northbound Ethernet port. The SCU software consists of three components: the BSMU, FSU, and SGW. The BSMU includes six sub-threads, each of which retrieves data from connected energy storage batteries through the six RS485 ports. The BSMU interacts with the communication energy storage batteries using the Modbus protocol. Each BSMU sub-thread polls the batteries at addresses 1 through 32, sequentially obtaining information for 20 connected battery groups and storing it in shared memory. The FSU interacts with the CSU via a network socket, parsing the 1104 protocol to obtain power-related information and reading battery energy storage information obtained by the SBMU from shared memory. The FSU aggregates the acquired power and energy storage battery data to produce complete power system data. The SGW includes northbound network management connection parameters and network management response functions. It transmits the power and battery data collected by the FSU to the network management system via the northbound Ethernet port. In this example, the SNMP V3 protocol is used.

[0077] S4: Energy storage battery design and deployment:

[0078] In this example, there are 120 groups of energy storage batteries, and 20 groups of batteries are connected to one RS485 bus as a cluster. Each group of batteries is configured with two RS485s and one CAN (CAN1), and one group of every 20 batteries is selected to be configured with the second CAN (CAN2). The 20 batteries in the cluster are connected in parallel through CAN1 and RS485, and connected to the southbound RS485 port of the SCU through R485; the hosts of the 6 clusters of batteries are connected in parallel through CAN2. The address competition method is used to configure the battery configured with CAN2 to become the host of each cluster (see Example 3 for details). CAN1 and CAN2 are used respectively to achieve intra-cluster current sharing and inter-cluster current sharing, and the data transmission between the energy storage battery and the SCU adopts the modbus protocol.

[0079] Operational implementation steps:

[0080] S5: Complete system software and hardware deployment according to the design state.

[0081] S6: Energy storage system startup and current sharing: The energy storage system starts up, determines the address and host of the batteries in each cluster through address competition, starts the current sharing service, and starts the data response process to respond to instructions from the SCU.

[0082] S7: CSU Startup: The CSU starts to perform power-related services. The CSU checks the SCU configuration flag to see if the system is configured with an SCU. In this example, if the system is configured with an SCU hardware entity, the CSU will determine that an SCU is configured and start the CSU northbound process, enter the network socket response process, wait for SCU instructions and respond;

[0083] S8: SCU Startup: The SCU starts, and the BSMU, FSU, and SGW start accordingly, completing the shared memory mapping of the SBMU, FSU, and SGW. The BSMU starts six sub-threads, which concurrently poll addresses 1-32, sending modus commands and parsing the responses to store the energy storage battery data in shared memory. The FSU establishes a link with the CSU using a network socket, sends the 1104 command, and parses the response to obtain power-related data, storing it in shared memory. The SGW receives SNMP V3 commands from the network management system and, based on the command content, retrieves power and battery data from shared memory and encapsulates it in the appropriate protocol format to respond to the network management command.

[0084] Example 2

[0085] In the above Example 1, a scenario with 120 groups of batteries is used as an example to describe the implementation of the technology for parallel networking of multiple groups of batteries and decoupling power and battery services. In Example 1, the power supply and battery are completely isolated from each other in terms of software and hardware, thereby achieving complete decoupling of power and battery services.

[0086] This example further supplements the design of the CSU based on Example 1, and describes in detail the compatible design and implementation of the CSU to achieve power supply and battery decoupling solutions in single-cluster and multi-cluster battery scenarios. The main steps of this implementation example are as follows:

[0087] Design implementation steps:

[0088] S1: CSU Hardware Design: The CSU hardware is originally the power management unit hardware. This invention requires that the CSU must have an Ethernet port. If the original power supply hardware has a northbound Ethernet port, this port is reused for communication with the SCU. If the power supply does not have a northbound Ethernet port, a northbound Ethernet port is added to the power supply.

[0089] S2: CSU software design: CSU includes a power management business component for power-related business management, a northbound transmission component for transmitting power data to the SCU, and a process management business for managing CSU running processes to ensure the normal operation of each process running on the CSU. The northbound transmission component uniformly uses Socket to connect and interact with the SCU. In this example, the 1104 protocol is used for data transmission, thereby achieving compatibility between solutions in multi-cluster battery networking and single-cluster battery networking. Among them, in single-cluster battery networking, the SCU software is deployed on the CSU hardware, and the interaction between CSU and SCU is inter-process Socket; in multi-cluster battery networking, the SCU software is deployed on the SCU hardware, and the interaction between CSU and SCU is network Socket. The two scenarios are distinguished by the SCU configuration tag on the CSU and judged at runtime.

[0090] Operational state implementation steps:

[0091] S3: CSU starts, and CSU starts to carry out power-related business.

[0092] S4: CSU checks the SCU configuration flag to determine whether the system is configured with SCU; if it is detected that the system is not configured with SCU, it jumps to S5; if the SCU entity is configured, it jumps to S12.

[0093] S5: If the CSU does not contain the SCU configuration mark, it means that the system is not configured with SCU hardware. Then the CSU starts the SCU process. Both the SCU and the CSU run on the power hardware. After the SCU is started, it is included in the unified management of the CSU.

[0094] S6: Based on S5, CSU starts its own northbound transmission process and uses inter-process socket to communicate with relevant components in SCU software, waiting to receive the 1104 instruction sent by SCU, and obtains power data and responds according to the instruction content.

[0095] S7: The CSU process management module checks whether the SCU is running normally through heartbeat messages; if no SCU heartbeat is detected, the CSU will try to restart the SCU process; if the SCU cannot be restarted, jump to S8.

[0096] S8: If the SCU fails to recover after repeated attempts, the CSU generates an SCU function abnormality alarm and takes over the network management parameters in the SCU. The CSU northbound transmission process directly transmits basic power data to the network management.

[0097] S9: The SCU subcomponent (SBMU) starts a subthread to manage the energy storage battery through the RS485 port of the CSU hardware. It sends Modbus commands to poll addresses 1-32 in sequence, obtaining energy storage battery data and storing it in shared memory.

[0098] S10: The SCU subcomponent FSU communicates with the CSU process through the inter-process Socket, sends 1104 instructions to the CSU to obtain power data, parses it, and stores it in the shared memory, thereby realizing the collection of power and battery data.

[0099] S11: The SCU subcomponent parses the network management parameters, establishes a connection with the network management, and receives network management instructions to obtain power and battery data to respond to network management requirements.

[0100] S12: Based on the results of S4, if the detection system is configured with an SCU entity, the CSU does not start the SCU process. Instead, the CSU starts the northbound transmission process and communicates with the SCU entity using a network socket. The CSU waits to receive the 1104 command issued by the SCU and responds.

[0101] Through the above steps, the CSU uses socket design to achieve unified interaction between the CSU and SCU to meet the compatibility of single-cluster and multi-cluster scenarios, and realize the transfer of battery services from the CSU to the SCU.

[0102] Example 3

[0103] The above Example 1 mainly describes the overall solution for decoupling power and battery services and accessing multiple groups of energy storage batteries using the CSU, SCU, and energy storage batteries. Example 2 mainly supplements the implementation method of the CSU using the socket design to solve the compatibility problem of single-cluster battery access and multiple-cluster battery access.

[0104] This example supplements the implementation method of overall current sharing of energy storage batteries based on the previous two examples.

[0105] Design implementation steps:

[0106] S1: Each battery group is equipped with two RS485 ports and one CAN port (CAN1). CAN1 and RS485 are used for parallel operation of batteries within the cluster.

[0107] S2: In each cluster, a battery group is selected to configure the second CAN (CAN2) as the master for inter-cluster battery paralleling.

[0108] Operational implementation steps:

[0109] S3: The battery pack is powered on, the default address is 1, and the address competition command is actively sent three times on the battery cluster CAN1 link using broadcast mode.

[0110] S4: Determine the result of S3. If there is no response, maintain the current address. If the battery address is 1, the battery acts as a pending host and processes host contention information. If there is a response, add 1 to the current address and resend the address contention command three times.

[0111] S5: The pending host processes the host contention message and checks whether the received data frame contains CAN2 information; if the received contention message data frame does not contain CAN2 information, the battery address remains unchanged; if the received data frame contains CAN2 information, the battery address is increased by 1 and the address contention command is resent three times.

[0112] S6: When no more address contention commands occur from S3 to S5 to each battery, the energy storage battery completes address allocation and the battery with CAN2 becomes the host of each cluster.

[0113] S7: Each battery cluster broadcasts a current sharing instruction via the CAN1 link to share the current among the batteries in the cluster.

[0114] S8: The host of each battery cluster broadcasts the current sharing instruction through the CAN2 link to achieve current sharing of each battery host.

[0115] This implementation allows all energy storage batteries to share current, shifting the battery sharing function from traditional power sources to the energy storage batteries. This decouples the power supply from the battery function and improves the safety and reliability of the energy storage batteries. Because the energy storage batteries are decoupled from the power supply, the technical solution provided in this implementation is equally applicable when connected to third-party power sources or other devices.

[0116] Through the description of the above implementation methods, those skilled in the art can clearly understand that the technical solutions according to the above embodiments can be implemented by means of software plus the necessary general hardware platform, and of course, by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of software plus the necessary general hardware platform. The software can be stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), including a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to perform the functions of the various components of the above embodiments of the present invention.

[0117] An embodiment of the present invention further provides a computer-readable storage medium, in which a computer program is stored. The computer program is configured to execute the steps of any one of the above method embodiments when running.

[0118] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.

[0119] An embodiment of the present invention further provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0120] In an exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0121] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail here.

[0122] Obviously, those skilled in the art will appreciate that the various modules or steps of the present invention described above can be implemented using a general-purpose computing device, can be centralized on a single computing device, or can be distributed across a network of multiple computing devices. They can be implemented using program code executable by the computing device, and thus, can be stored in a storage device and executed by the computing device. In some cases, the steps shown or described herein can be performed in a different order than that shown, or can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the present invention is not limited to any particular combination of hardware and software.

[0123] The foregoing description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Those skilled in the art will readily appreciate that various modifications and variations of the present invention are possible. Any modifications, equivalent substitutions, or improvements made within the principles of the present invention are intended to be within the scope of protection of the present invention.

Claims

1. A management system for a power supply and energy storage battery network, characterized in that: include: Multiple groups of energy storage batteries, site control units SCU and centralized monitoring units CSU, among which, The multiple groups of energy storage batteries form one or more battery clusters, and each battery cluster is connected to the SCU via an RS485 interface; The CSU is used to manage power supply and is connected to the SCU via a northbound Ethernet interface to send power supply data to the SCU; The SCU is used to manage the multiple energy storage batteries, connect to the CSU via the southbound Ethernet interface to obtain the power data of the CSU, and connect to the network management system via the northbound Ethernet interface to send the battery data and the power data of the multiple energy storage batteries to the network management system and receive instructions from the network management system; Each battery cluster includes a group of main energy storage batteries and one or more groups of slave energy storage batteries. The energy storage battery groups in each battery cluster are connected through a first controller area network (CAN) link, which is used for current sharing among the energy storage battery groups in the battery cluster. The main energy storage batteries in each battery cluster are connected through a second CAN link, which is used for current sharing among the energy storage battery groups between battery clusters.

2. The system according to claim 1, wherein: The SCU includes: A battery system management unit BSMU, configured to manage the plurality of energy storage batteries and obtain battery data of the plurality of energy storage batteries; A dynamic environment monitoring unit FSU, configured to aggregate the power supply data and the battery data; The site gateway SGW is configured to send the aggregated battery data and power supply data to the network management system, and receive instructions from the network management system.

3. The system according to claim 2, characterized in that in, The BSMU adopts multi-threaded parallel management. The number of threads is the same as the number of RS485 interfaces through which the battery clusters are connected to the SCU. Each thread is responsible for accessing and managing a battery cluster connected to the RS485 interface.

4. The system according to claim 2, wherein: in, The power supply data is connected to the FSU of the SCU by the CSU through a socket, and the battery data is transferred to the FSU by the BSMU through a shared memory.

5. The system according to claim 1, wherein: in, When there is only one battery cluster, the SCU software runs on the hardware of the CSU and obtains the power data of the CSU through an inter-process socket. When there are multiple battery clusters, the SCU runs on independent hardware and obtains the power data of the CSU through a network socket.

6. The system according to claim 1, wherein: in, Each of the battery clusters is connected to the SCU via an RS485 interface, and the number of the battery clusters is the same as the number of the RS485 interfaces.

7. A method for managing a power supply and energy storage battery network, applied to the system according to any one of claims 1 to 6, characterized in that: include: When the CSU is started, checking whether the CSU has an SCU configuration flag; In the case where the CSU has the SCU configuration flag, the CSU starts its own northbound transmission process and transmits the power data to the SCU using the network socket; In the case that the CSU does not have an SCU configuration flag, the CSU starts the SCU process. Both the SCU and the CSU run on power hardware. After the SCU is started, it is managed uniformly by the CSU.

8. The method according to claim 7, characterized in that In a case where the CSU does not have an SCU configuration flag, the CSU starts an SCU process, including: The CSU starts its own northbound transmission process and communicates with relevant components in the SCU software using an inter-process Socket.

9. The method according to claim 7, characterized in that Also includes: The CSU checks whether the SCU is running normally through the heartbeat message. If the SCU heartbeat message cannot be detected, the CSU restarts the SCU process. In the case that restarting the SCU process fails, the CSU generates an SCU function abnormality alarm, and the CSU northbound transmission process directly sends power data to the network management system.

10. A method for managing a power supply and energy storage battery network, applied to the system according to any one of claims 1 to 6, characterized in that: include: When each energy storage battery is powered on, it defaults to a preset initial address and uses a broadcast method to send an address competition message on the first CAN link of the battery cluster where it is located; Determine the pending master energy storage battery based on whether a response to the address competition message is received from other energy storage batteries; Checking data frames received by the candidate main energy storage battery from other battery clusters, and determining whether the candidate main energy storage battery is the final main energy storage battery based on whether the data frames contain second CAN link information; Each battery cluster includes a group of main energy storage batteries and one or more groups of slave energy storage batteries. The energy storage battery groups in each battery cluster are connected through a first controller area network (CAN) link, which is used for current sharing among the energy storage battery groups in the battery cluster. The main energy storage batteries in each battery cluster are connected through a second CAN link, which is used for current sharing among the energy storage battery groups between battery clusters.

11. The method according to claim 10, characterized in that The pending master energy storage battery is determined based on whether a response to the address competition message is received from other energy storage batteries, including: When receiving a response to the address contention message from another energy storage battery, adding a preset value to the current address of the energy storage battery and rebroadcasting the contention message; In the case where no response to the address competition message is received from other energy storage batteries, the current first address of the energy storage battery is maintained, and the energy storage battery is determined as the pending master energy storage battery.

12. The method according to claim 10, characterized in that Determining whether the to-be-determined main energy storage battery is the final main energy storage battery according to whether the data frame contains the second CAN link information includes: In a case where the data frame includes the second CAN link information, adding a preset value to the current address of the to-be-determined main energy storage battery, and rebroadcasting the contention message; When the data frame does not include the second CAN link information and the current address of the to-be-determined main energy storage battery is the initial address, the main energy storage battery is determined to be the final main energy storage battery.

13. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, wherein when the computer program is executed by a processor, the computer program implements the steps of the method described in any one of claims 7 to 9, or implements the steps of the method described in any one of claims 10-12.

14. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the processor implements the steps of the method described in any one of claims 8 to 10, or implements the steps of the method described in any one of claims 10-12.

Images