Energy storage system equipment ID management method and related equipment
By adopting the broadcast method and timer to generate device identification addresses in the energy storage system, the problem of low efficiency of traditional device identification methods is solved, and the automation, uniqueness and efficient management of device identity are achieved.
Patent Information
- Application Number
- CN202510935250.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-07-08
- Publication Date
- 2025-09-09
AI Technical Summary
Traditional energy storage system equipment identification methods rely on manual operations or additional detection modules, resulting in low identification efficiency, prone to errors, complex management, increased costs, and poor compatibility.
The reordering command is broadcast to all devices in the network in a broadcasting manner, a timer is started to obtain the device identification address, its own identification address is broadcast through the communication bus, and the identification addresses of other devices are received to build an identification address set for ID allocation.
It realizes decentralized self-coordination among devices, and has high reliability, high efficiency and low-cost device identity initialization and management, which is suitable for large-scale and complex energy storage systems.
Smart Images

Figure CN120614248A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to the field of computers, and more specifically, to an energy storage system device ID management method and related devices. Background Art
[0002] With the booming new energy industry, energy storage systems have been widely adopted in power supply, electric vehicle charging stations, data center backup power, and other fields. Energy storage systems contain a large number of devices, such as battery packs, energy storage converters, and battery management systems. These devices require effective identification and management to ensure stable system operation and efficient maintenance. However, traditional device identification methods often rely on manual operation or additional detection modules, resulting in low identification efficiency, error-proneness, complex management, increased costs, and poor compatibility. For example, address allocation through DIP switches or firmware allocation requires manual operation, which is prone to errors and address duplication, resulting in low efficiency and uncertainty in device address uniqueness. Furthermore, firmware allocation requires manual programming and specialized programming equipment, which is inefficient and difficult. Alternatively, adding additional detection modules or complex communication logic to identify device addresses increases design cost and complexity. Complex communication identification logic complicates software design and leads to poor identification compatibility. Summary of the Invention
[0003] The Summary of the Invention introduces a series of simplified concepts that will be further described in the Detailed Description of the Invention. The Summary of the Invention is not intended to limit the key features and essential features of the claimed technical solution, nor is it intended to determine the scope of protection of the claimed technical solution.
[0004] To address the problems of low recognition efficiency, error-proneness, complex management, increased costs, and poor compatibility associated with traditional device identification methods, which often rely on manual operations or additional detection modules, the present invention provides, in a first aspect, a method for managing device IDs in an energy storage system, applicable to any device in the energy storage system. The method comprises:
[0005] Broadcasting a re-arrangement command to all devices in the network in a broadcasting manner, wherein the re-arrangement command is used to instruct all devices that receive the command to restart the ID allocation process;
[0006] When receiving the reorder command, start its own timer to obtain its own device identification address;
[0007] Broadcast its own device identification address to the communication bus, and receive the own device identification addresses broadcast by other devices through the bus, so as to perform ID allocation after obtaining the identification address set of other devices.
[0008] Optionally, before the step of broadcasting the reordering command to all devices in the network, the method further includes:
[0009] After power-on, it determines whether it has a valid ID code for external communication. If it does not have a valid ID code for external communication, it broadcasts a rearrangement command to all devices in the network. If it has a valid ID code for external communication, it enters normal operating mode.
[0010] Optionally, broadcasting the reordering command to all devices in the network in a broadcasting manner includes:
[0011] Select one device that is powered on the earliest or that completes initialization first as the initiator, and broadcast the reorder command to all devices in the network through the communication bus.
[0012] Optionally, broadcasting the own device identification address to the communication bus includes:
[0013] Broadcast its own device identification address to the communication bus as a slave.
[0014] Optionally, receiving the device identification address of another device broadcast via a bus includes:
[0015] Listen to broadcast information on the bus, and receive and store the identification addresses of other devices one by one to build a set of known identification addresses.
[0016] Optionally, also include:
[0017] When receiving the device identification address broadcast by other devices through the bus, the device identification address is compared with the stored identification addresses of other devices. If a duplication is found, it is considered an identification conflict, and the re-arrangement command is re-broadcast to enter a new round of identification process.
[0018] Optionally, performing ID allocation after obtaining the identification address set of other devices includes:
[0019] Sorting is performed based on the identification address of the device itself and the obtained identification address set of other devices, and the position of the device in the sorting is used as the scan ID code.
[0020] In a second aspect, the present invention further provides an energy storage system device ID management device, which is used for any device in the energy storage system, and the device includes:
[0021] a broadcast unit, configured to broadcast a re-arrangement command to all devices in the network in a broadcast manner, wherein the re-arrangement command is used to instruct all devices that receive the command to restart the ID allocation process;
[0022] A receiving unit, configured to start its own timer to obtain its own device identification address when receiving a reordering command;
[0023] The allocation unit is used to broadcast its own device identification address to the communication bus and receive the own device identification addresses broadcast by other devices through the bus, so as to perform ID allocation after obtaining the identification address set of other devices.
[0024] In a third aspect, an electronic device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor is configured to implement the steps of the energy storage system device ID management method according to any one of the first aspects described above when executing the computer program stored in the memory.
[0025] In a fourth aspect, the present invention further proposes a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the energy storage system device ID management method according to any one of the above items in the first aspect is implemented.
[0026] In summary, the energy storage system device ID management method proposed in this application is used for any device in the energy storage system, by broadcasting a re-arrangement command to all devices in the network in a broadcast manner, and the re-arrangement command is used to instruct all devices that receive the command to restart the ID allocation process; when the re-arrangement command is received, the self-timer is started to obtain the self-device identification address; the self-device identification address is broadcast to the communication bus, and the self-device identification address broadcast by other devices through the bus is received, so as to perform ID allocation after obtaining the identification address set of other devices. As a result, all devices use the same broadcast mechanism to synchronously propagate address information, and realize mutual knowledge of device status without distinguishing between master and slave roles, thereby having the characteristics of decentralization and self-coordination. It can enable all devices to obtain unique identification information from each other without relying on the main controller, provide sufficient information basis for the subsequent allocation of unique IDs, and improve the automation level and expansion capability of the system. Through the three-step process of broadcasting the start command, the timer generating a unique address, and the broadcasting and receiving of the identification address, the ID recognition preparation operation between multiple devices can be realized on a single device. This process has fully distributed execution capabilities, does not require external intervention and control nodes, and has the advantages of high reliability, high efficiency and low implementation cost. It is suitable for device identity initialization and management in scenarios with large numbers of devices and complex structures, such as energy storage systems.
[0027] The energy storage system device ID management method of the present invention, and other advantages, objectives and features of the present invention will be partially reflected in the following description, and will also be partially understood by those skilled in the art through research and practice of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS
[0028] Various other advantages and benefits will become apparent to those skilled in the art upon reading the detailed description of the preferred embodiment below. The accompanying drawings are for illustration purposes only and are not to be considered as limiting the present description. The same reference symbols are used throughout the drawings to represent the same components. In the drawings:
[0029] Figure 1 A schematic diagram of a method for managing IDs of energy storage system devices provided in an embodiment of the present application;
[0030] Figure 2 A schematic diagram of the structure of an energy storage system device ID management device provided in an embodiment of the present application;
[0031] Figure 3 A schematic diagram of the structure of an energy storage system device ID management electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0032] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments described herein can be implemented in a sequence other than that illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or that are inherent to these processes, methods, products or devices. The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the embodiments described are only part of the embodiments of the present application, not all of the embodiments.
[0033] To solve the problems of low recognition efficiency, error-proneness, complex management, increased costs, and poor compatibility caused by traditional device identification methods, which often rely on manual operations or additional detection modules, please refer to Figure 1 , is a flow chart of a method for managing an energy storage system device ID provided in an embodiment of the present application. The method is applicable to any device in the energy storage system and may specifically include steps S110 to S130.
[0034] S110 , broadcasting a re-arrangement command to all devices in the network in a broadcast manner, wherein the re-arrangement command is used to instruct all devices that receive the command to restart the ID allocation process.
[0035] S120: When receiving the reordering command, start the own timer to obtain the own device identification address.
[0036] S130, broadcasting the own device identification address to the communication bus, and receiving the own device identification addresses broadcasted by other devices through the bus, so as to perform ID allocation after obtaining the identification address set of other devices.
[0037] As can be understood, this method automatically initializes and assigns device IDs through bus communication without manual intervention between devices, ensuring that each device receives a unique identification code for subsequent data exchange and system recognition. This method is applicable to any device within the energy storage system's communication network.
[0038] For example, after any device is powered on, a re-arrangement command is sent to all devices in the network in a broadcast manner. The re-arrangement command is a type of predefined data communication instruction, and its function is to uniformly trigger all devices that receive the command to re-enter the ID allocation process. The command can be sent through bus systems that support broadcast mechanisms, such as CAN and RS485, and has the advantages of fast propagation speed and wide targets. Through the broadcast of this command, all devices in the system enter the ID identification state at the same time, avoiding inconsistent identification processes due to differences in the power-on sequence of the devices, thereby improving the synchronization of identification and the stability of the overall system. The technical effect of this step is to ensure that all devices enter the initialization process under unified instructions, improve process coordination, and reduce configuration deviations.
[0039] Exemplarily, after the device receives the above-mentioned broadcast re-arrangement command, it immediately starts a local timer to generate its own device identification address after the preset delay. The purpose of starting the timer is to introduce a minimum time difference, so as to avoid conflicts caused by all devices generating addresses at exactly the same time. After the timer arrives, each device generates a device identification address that is only used for the current identification process. The address can be derived from local hardware resources, such as the device's inherent code (such as MAC suffix), startup time, chip serial number, etc. The identification address is not an ID code that is ultimately used for external communication, but a temporary unique information used for comparison, sorting or identification between devices. The technical effect of this step is: automatically generate a unique device identifier without the need for external hardware, improve the automation and uniqueness of address generation, and avoid manual configuration errors.
[0040] For example, after obtaining its own identification address, the device immediately broadcasts it to all devices on the network via the communication bus, while simultaneously monitoring the bus to receive identification addresses sent by other devices. Each device, while broadcasting its own address, simultaneously collects the broadcasts from other devices, forming a complete set of device identification addresses. Based on this set, the device can further perform identification comparison, sorting, or ID assignment operations.
[0041] In summary, the energy storage system device ID management method provided in the embodiment of the present application is used for any device in the energy storage system, by broadcasting a re-arrangement command to all devices in the network in a broadcast manner, and the re-arrangement command is used to instruct all devices that receive the command to restart the ID allocation process; when the re-arrangement command is received, the self-timer is started to obtain the self-device identification address; the self-device identification address is broadcast to the communication bus, and the self-device identification address broadcast by other devices through the bus is received, so as to perform ID allocation after obtaining the identification address set of other devices. As a result, all devices use the same broadcast mechanism to synchronously propagate address information, and realize mutual knowledge of device status without distinguishing between master and slave roles, thereby having the characteristics of decentralization and self-coordination. It can enable all devices to obtain unique identification information from each other without relying on the main controller, provide sufficient information basis for the subsequent allocation of unique IDs, and improve the automation level and expansion capabilities of the system. Through the three-step process of broadcasting the start command, the timer generating the unique address, and the broadcasting and receiving of the identification address, the ID recognition preparation operation between multiple devices can be realized on a single device. This process has fully distributed execution capabilities, does not require external intervention and control nodes, and has the advantages of high reliability, high efficiency and low implementation cost. It is suitable for device identity initialization and management in scenarios with large numbers of devices and complex structures, such as energy storage systems.
[0042] In some examples, before broadcasting the reorder command to all devices in the network, the method further includes:
[0043] After power-on, it determines whether it has a valid ID code for external communication. If it does not have a valid ID code for external communication, it broadcasts a rearrangement command to all devices in the network. If it has a valid ID code for external communication, it enters normal operating mode.
[0044] For example, after a device is powered on and started, its internal control logic first determines its own status to determine whether it currently possesses a valid ID code for external communication. A valid ID code for external communication refers to an ID that uniquely identifies the device within the current energy storage system network. This ID must meet system-defined validity criteria, such as being non-null, non-duplicate, non-expired, and non-conflicting. This determination is typically made by reading the last configured ID information from the device's local non-volatile memory and performing a consistency check based on the current network environment or device operating status. The technical basis of this determination mechanism is that the device uses its own status information to autonomously determine whether to participate in ID allocation, enabling fully distributed operation without the need for a centralized control node. If a device determines that it already possesses a valid ID code for external communication, it indicates that it has successfully obtained a unique ID in a previous identification process and that this ID is still considered valid and legal within the system. In this case, the device does not need to participate in the identification and allocation process again, skipping the subsequent broadcast and allocation operations and quickly entering normal operation. This design prevents system-wide renegotiation when some devices frequently restart or partially reset, thereby improving overall operational stability and identification efficiency. This saves system resources and reduces communication traffic, making it particularly suitable for scenarios with a large number of devices or frequent system expansion. Conversely, if a device determines that it does not possess a valid ID code for external communication—for example, if no valid ID is detected during startup, the memory is empty, an ID conflict is detected, or the ID has expired—then it has not completed or cannot maintain its ID identification status. In this case, the device automatically initiates the first step of the ID identification process: broadcasting a reassignment command to all devices on the network. This command is a standardized control instruction that notifies all devices on the network to initiate the ID reassignment process. Because this broadcast method is independent of device role or master control, any device can autonomously initiate this process based on actual needs, achieving distributed autonomy. This enables dynamic decision-making within the device identification process. Devices with valid IDs can directly enter operational mode, avoiding redundant identification. Devices without valid IDs can proactively broadcast a reassignment command, triggering a unified ID negotiation process. The technical effect achieved by this example is to improve the intelligence and flexibility of device startup, avoid bus load caused by invalid broadcasts, and provide a low-cost, high-efficiency, and high-reliability ID initialization control mechanism for the entire energy storage system.
[0045] In some examples, broadcasting the reordering command to all devices in the network in a broadcasting manner includes:
[0046] Select one device that is powered on the earliest or that completes initialization first as the initiator, and broadcast the reorder command to all devices in the network through the communication bus.
[0047] It can be understood that in order to improve the collaborative efficiency and startup synchronization between devices, the step of broadcasting the rescheduling command to all devices in the network in a broadcast manner further includes: selecting any device that is powered on the earliest or completes the initialization process first as the initiator of the rescheduling command, and broadcasting the rescheduling command to all devices in the network through the connected communication bus.
[0048] For example, in energy storage system applications, multiple devices (e.g., energy storage converters, inverters, BMS nodes, etc.) are often connected to the power supply and powered on simultaneously or nearly simultaneously. Since the startup speed of a device after powering on may be limited by factors such as hardware initialization, software loading, and communication interface readiness, there are slight differences in the time it takes for different devices to complete the initialization process. To avoid bus conflicts or duplicate recognition caused by multiple devices broadcasting reorder commands simultaneously, this embodiment designs a broadcast control strategy based on prioritizing the first device to complete initialization. Under this strategy, each device will perform an initialization process after powering on, including circuit self-tests, communication link establishment, and operating environment loading. After completing initialization, each device will enter a waiting time window and listen to whether other devices on the network have broadcast reorder commands. If no reorder broadcast signal from other devices is detected within a set timeout period (e.g., 50ms), the current device automatically determines that it is the "first device to complete initialization" in the network and assumes the broadcast task, immediately sending the reorder command to all devices via the communication bus. This command carries a control field in a unified format that can be recognized by all devices in the network and is used to trigger the restart of the ID identification process.
[0049] It is understandable that since any device in the system has the ability to broadcast, only the device that completes initialization first initiates the command, and other devices wait and receive rescheduling instructions within a short listening window to avoid conflicts and ensure synchronization. Since this mechanism does not rely on the master device and is completely based on event-driven and time arbitration, it has extremely strong distributed negotiation capabilities. On the one hand, by introducing an initialization completion priority initiation strategy, the ID identification process is ensured to be unified and controllable, and the startup stability of multiple devices when connected to the grid is improved; on the other hand, it avoids bus conflicts or repeated rescheduling caused by multiple devices competing for broadcast resources, reduces communication load and the probability of configuration errors, and is suitable for energy storage system environments with inconsistent device startup times or large-scale device access.
[0050] In some examples, broadcasting the own device identification address to the communication bus includes:
[0051] Broadcast its own device identification address to the communication bus as a slave.
[0052] For example, in an energy storage system, multiple devices communicate through the same bus (such as a CAN bus or an RS485 bus). In a traditional master-slave communication architecture, the host usually actively polls and assigns tasks, while the slave only responds when requested. However, in the ID identification phase of the above example, in order to avoid communication deadlocks due to the master control not being determined or assigned, the system design adopts a full slave mode for initialization broadcasting, that is, all devices do not distinguish between master and slave roles in the identification phase, and are uniformly regarded as slaves, and autonomously broadcast the device identification address generated by themselves to the bus. At this time, the content of the device broadcast includes: its own device identification address field, broadcast identification bit (indicating that it is a broadcast in the identification phase), and check field, etc. Since all devices use the slave identity to broadcast information at this stage, the system does not need to specify a master device to coordinate communication or assign communication timing, thereby reducing the complexity of the system design and the control coupling of the initialization process. At the same time, the slave broadcast mechanism avoids potential master device preemption or communication instruction interference, so that all devices can complete the identification address broadcast and collection under the same conditions.
[0053] It can be understood that the above method, by utilizing the sharing nature of the broadcast channel and the decentralized nature of the slave role, enables each device to complete the necessary identification information transmission under the premise of independent control. Since the communication protocol layer accepts broadcast information by default and allows multiple slave devices to send specific identification frames, the above method can complete the reliable broadcast of identification information without introducing a master role. It improves the concurrency and robustness of the system equipment initialization identification phase; avoids communication congestion problems caused by undefined or conflicting master and slave roles; and realizes the identification broadcast of equivalence between devices, which is conducive to subsequent unified sorting and ID allocation operations, and is suitable for dynamic networking and distributed energy storage system deployment without preset master roles.
[0054] In some examples, receiving the device identification address of another device broadcast via a bus includes:
[0055] Listen to broadcast information on the bus, and receive and store the identification addresses of other devices one by one to build a set of known identification addresses.
[0056] It can be understood that in order to achieve effective synchronization and global perception of identification information between devices, after the device completes the broadcast of its own identification address, it continues to listen to the broadcast information on the communication bus, and receives the identification addresses broadcast by other devices one by one and stores them locally, thereby building a complete set of known identification addresses.
[0057] For example, in an energy storage system, each device implements broadcast communication through the same physical bus. During the ID identification phase, after each device broadcasts its own device identification address as a slave, it does not immediately exit the identification process, but enters a receiving window period. This window period is limited by protocol settings or time control logic, for example, set to 100ms to 500ms, to ensure that the broadcast messages of all devices can be fully transmitted and received within this period. During this receiving window, each device continuously turns on the listening mode on the bus to capture and parse data broadcasts that conform to the identification frame format. Whenever a broadcast message containing the identification address of another device is detected, the identification address is parsed and stored in a local temporary cache or address table structure. The device will deduplicate and verify each received address information to ensure that each address in the set is an independent and valid device identification. Each device will construct a set of known identification addresses based on all the broadcast identification information it receives. This set is used for subsequent sorting logic and ID code allocation. It should be pointed out that due to the symmetry and openness of bus broadcasting, all devices can theoretically obtain the same set of addresses, thereby ensuring the consistency of the basis for subsequent sorting by each device and ensuring global consistency of the distributed sorting results.
[0058] It is understandable that the above method utilizes the physical property of the bus broadcast protocol, which allows all nodes to monitor, to achieve masterless information sharing between devices. By locally storing a set of identification addresses, the device obtains a global view of the status of all devices participating in the identification process across the entire network, thereby enabling the subsequent independent sorting and autonomous ID assignment capabilities. On the one hand, it ensures that each device can perceive all devices participating in the broadcast on the network, improving identification accuracy and completeness; on the other hand, it constructs unified basic sorting data to provide information support for the distributed execution of ID assignment by devices, avoiding allocation conflicts caused by central node control or information asymmetry, and enhancing the scalability and autonomy of the system.
[0059] In some examples, this also includes:
[0060] When receiving the device identification address broadcast by other devices through the bus, the device identification address is compared with the stored identification addresses of other devices. If a duplication is found, it is considered an identification conflict, and the re-arrangement command is re-broadcast to enter a new round of identification process.
[0061] It can be understood that in order to ensure the uniqueness of the device identification in the entire system, when receiving the device identification address of its own device broadcasted by other devices through the bus, its own device identification address is compared with the identification addresses of other locally stored devices. If it is found to be duplicated with any stored address, it is determined that there is an identification conflict and the re-arrangement command is rebroadcast, thereby triggering a new round of identification and allocation process.
[0062] For example, after each device completes broadcasting and receives the identification addresses of other devices, it possesses complete information about the set of device identification addresses. At this point, the device performs a conflict detection operation, matching the device identification address generated by the device against all addresses in the set. This comparison can use simple numerical comparison or hashing logic to determine whether the current identification is identical to that of another device. If an identification conflict is detected during the comparison process—that is, the current device's identification address is duplicated in the set—it indicates that two or more devices have generated the same address for some reason (such as timer jitter or an unstable identification generation mechanism). In this case, the current device immediately determines that the identification process has failed. To ensure the uniqueness of subsequent ID codes assigned by the system, it immediately broadcasts a reordering command via the communication bus. This reordering command notifies all devices in the network to terminate the current identification process and restart the identification address generation and broadcasting process. Upon receiving this command, the remaining devices will also reset their timers and regenerate their own identification addresses, ensuring that conflicts are resolved and effective identification distinctions are achieved in the next round of identification.
[0063] It can be understood that the above method embodies a self-correcting distributed conflict detection mechanism that does not rely on the judgment of the master control, nor on global information synchronization. It can detect anomalies in real time and autonomously initiate a recovery mechanism only through local comparison of each device. In the broadcast bus structure, each device has peer-to-peer communication capabilities and independent identification status perception capabilities, so it can independently complete identification integrity verification and promote system rollback. In this way, the global uniqueness of the device identification address in the system can be guaranteed, avoiding ID duplication, device confusion or communication errors caused by conflicts; at the same time, the system is given a high degree of autonomous error correction capability, so that it has self-recovery characteristics and can still operate stably in large-scale networking or asynchronous deployment scenarios. It is especially suitable for environments where the power-on sequence of devices is uncertain and the identification mechanism is based on random parameter generation to ensure the robustness and robustness of the system identification process.
[0064] According to some embodiments, performing ID allocation after obtaining the identification address set of other devices includes:
[0065] Sorting is performed based on the identification address of the device itself and the obtained identification address set of other devices, and the position of the device in the sorting is used as the scan ID code.
[0066] Exemplarily, after each device obtains a complete set of identification addresses, it forms a sorting input set based on the identification address of the device itself and the identification addresses of other stored devices, and sorts all the identification addresses in the set according to a preset sorting rule (such as sorting by hexadecimal value from small to large) to determine the position number of the device itself in the sorting result, and uses the number as the scan ID code of the device for identity identification in subsequent external communications.
[0067] Exemplarily, after the device completes its own identification broadcast and successfully receives and records the identification addresses of other devices in the network, its local storage structure will contain a complete list of identification addresses. For example, when there are 5 devices in the network participating in the identification process, each device will have a set of 5 addresses, including its own address. At this time, each device will locally call a sorting algorithm (such as bubble sort, quick sort, or lightweight sorting logic adapted for embedded hardware) to sort the addresses in the set under unified rules. After the sorting is completed, the device calculates the sorting index (for example, the 1st, 2nd...Nth position) based on the position of its own identification address in the sorting result. The index value is the scan ID code (ScanID) of this device, which is usually expressed as a positive integer starting from 1, and is used as the logical unique identifier of the device in the subsequent communication process for master-slave interaction, status reporting, data acquisition and other functional modules.
[0068] It is understandable that, since the address sets obtained by all devices are theoretically completely consistent and the sorting logic is consistent, the calculation results of each device for its own ScanID are also globally consistent, thus achieving consistent ID allocation results for the entire network under distributed negotiation. This sorting and allocation method does not rely on the master control device, does not require central scheduling logic, and does not require complex mutual confirmation between devices. It only requires each device to complete the sorting and index judgment locally once to complete the ID code generation, which is extremely efficient and robust. As a result, full automation of ID allocation can be achieved without the need for configuration tools, dialing codes, or burning, and the uniqueness of the ID code and the consistency of the entire network are guaranteed. It also supports any power-on sequence and quantity expansion of devices, is highly scalable, and can adapt to large-scale, asynchronous power-on energy storage system cluster deployment, improving network deployment efficiency and system management convenience.
[0069] See also Figure 2 An embodiment of the energy storage system device ID management device in the embodiment of the present application is used for any device in the energy storage system. The device may include:
[0070] A broadcast unit 21 is configured to broadcast a re-arrangement command to all devices in the network in a broadcast manner, wherein the re-arrangement command is used to instruct all devices that receive the command to restart the ID allocation process;
[0071] The receiving unit 22 is configured to start its own timer to obtain its own device identification address when receiving the reorder command;
[0072] The allocation unit 23 is used to broadcast its own device identification address to the communication bus, and receive the own device identification addresses broadcasted by other devices through the bus, so as to perform ID allocation after obtaining the identification address set of other devices.
[0073] In summary, the energy storage system equipment ID management device provided in the embodiment of the present application is used for any device in the energy storage system, and broadcasts a re-arrangement command to all devices in the network in a broadcast manner, and the re-arrangement command is used to instruct all devices that receive the command to restart the ID allocation process; when the re-arrangement command is received, the device starts its own timer to obtain its own device identification address; broadcasts its own device identification address to the communication bus, and receives the device identification address of other devices broadcasted through the bus, so as to perform ID allocation after obtaining the identification address set of other devices. As a result, all devices use the same broadcast mechanism to synchronously propagate address information, and realize mutual knowledge of device status without distinguishing between master and slave roles, thereby having the characteristics of decentralization and self-coordination. It can enable all devices to obtain unique identification information from each other without relying on the main controller, provide sufficient information basis for the subsequent allocation of unique IDs, and improve the automation level and expansion capabilities of the system. Through the three-step process of broadcasting the start command, the timer generating the unique address, and the broadcasting and receiving of the identification address, the ID recognition preparation operation between multiple devices can be realized on a single device. This process has fully distributed execution capabilities, does not require external intervention and control nodes, and has the advantages of high reliability, high efficiency and low implementation cost. It is suitable for device identity initialization and management in scenarios with large numbers of devices and complex structures, such as energy storage systems.
[0074] like Figure 3 As shown, an embodiment of the present application also provides an electronic device 300, including a memory 310, a processor 320, and a computer program 311 stored in the memory 310 and executable on the processor. When the processor 320 executes the computer program 311, the steps of any of the above-mentioned methods for managing the ID of an energy storage system device are implemented.
[0075] Since the electronic device introduced in this embodiment is a device used to implement an energy storage system device ID management device in the embodiment of the present application, based on the method introduced in the embodiment of the present application, technical personnel in this field can understand the specific implementation of the electronic device of this embodiment and its various variations. Therefore, how the electronic device implements the method in the embodiment of the present application is not described in detail here. As long as the equipment used by technical personnel in this field to implement the method in the embodiment of the present application falls within the scope of protection to be protected by this application.
[0076] In the specific implementation process, the computer program 311 can be implemented when executed by the processor Figure 1 Any implementation manner in the corresponding embodiments.
[0077] It should be noted that, in the above embodiments, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant description of other embodiments.
[0078] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.
[0079] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded computer, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0080] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.
[0081] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.
[0082] The present application also provides a computer program product, which includes computer software instructions. When the computer software instructions are executed on a processing device, the processing device is caused to execute the following Figure 1 This corresponds to the process of energy storage system device ID management in the embodiment.
[0083] A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state drive (SSD)).
[0084] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0085] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.
[0086] Units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.
[0087] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.
[0088] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0089] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.
Claims
1. A method for managing IDs of energy storage system equipment, characterized in that: For any device in an energy storage system, the method includes: Broadcasting a re-arrangement command to all devices in the network in a broadcasting manner, wherein the re-arrangement command is used to instruct all devices that receive the command to restart the ID allocation process; When receiving the reorder command, start its own timer to obtain its own device identification address; Broadcast its own device identification address to the communication bus, and receive the own device identification addresses broadcast by other devices through the bus, so as to perform ID allocation after obtaining the identification address set of other devices.
2. The method according to claim 1, wherein Before the step of broadcasting the reordering command to all devices in the network, the method further includes: After power-on, it determines whether it has a valid ID code for external communication. If it does not have a valid ID code for external communication, it broadcasts a rearrangement command to all devices in the network. If it has a valid ID code for external communication, it enters normal operating mode.
3. The method according to claim 1, wherein The broadcasting of the reordering command to all devices in the network in a broadcasting manner includes: Select one device that is powered on the earliest or that completes initialization first as the initiator, and broadcast the reorder command to all devices in the network through the communication bus.
4. The method according to claim 1, wherein The broadcasting of the own device identification address to the communication bus includes: Broadcast its own device identification address to the communication bus as a slave.
5. The method according to claim 1, wherein The receiving of the self-device identification address broadcasted by other devices via the bus includes: Listen to broadcast information on the bus, and receive and store the identification addresses of other devices one by one to build a set of known identification addresses.
6. The method according to any one of claims 1 to 5, characterized in that Also includes: When receiving the device identification address broadcast by other devices through the bus, the device identification address is compared with the stored identification addresses of other devices. If a duplication is found, it is considered an identification conflict, and the re-arrangement command is re-broadcast to enter a new round of identification process.
7. The method according to any one of claims 1 to 5, characterized in that The step of allocating IDs after obtaining the identification address set of other devices includes: Sorting is performed based on the identification address of the device itself and the obtained identification address set of other devices, and the position of the device in the sorting is used as the scan ID code.
8. An energy storage system equipment ID management device, characterized in that: For any device in an energy storage system, the device comprises: a broadcast unit, configured to broadcast a re-arrangement command to all devices in the network in a broadcast manner, wherein the re-arrangement command is used to instruct all devices that receive the command to restart the ID allocation process; A receiving unit, configured to start its own timer to obtain its own device identification address when receiving a reordering command; The allocation unit is used to broadcast its own device identification address to the communication bus and receive the own device identification addresses broadcast by other devices through the bus, so as to perform ID allocation after obtaining the identification address set of other devices.
9. An electronic device comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor is configured to implement the steps of the energy storage system device ID management method according to any one of claims 1 to 7 when executing the computer program stored in the memory.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the energy storage system device ID management method according to any one of claims 1 to 7 is implemented.