A clustered field device aggregation control method

Abstract

This invention relates to the field of Industrial Internet of Things (IIoT) and industrial control, specifically to a clustered field device aggregation control method. The method includes the following steps: abstracting multiple independent field devices connected to a domain controller into one or more aggregation groups; treating all devices within an aggregation group as a logical whole; and performing unified data acquisition and control command issuance. This invention effectively solves problems in existing technologies such as low communication resource utilization, difficulty in real-time scheduling, complex management, and the inability to uniformly manage heterogeneous bus devices through techniques such as aggregation interface management, aggregation identifier and routing mapping, aggregation data acquisition, aggregation control issuance, automatic and manual aggregation, aggregation feature-related data mapping, aggregation port virtualization, and policy priority and feedback mechanisms.

Description

Technical Field

[0001] This invention belongs to the field of industrial Internet of Things and industrial control, specifically relating to a clustered field device aggregation control method. Background Technology

[0002] In large-scale energy storage or industrial IoT systems, field devices (such as battery management system (BMS) subsystems, sensor nodes, and actuator units) typically exist as independent units, each managing a group of nodes. The host computer (such as a domain controller, programmable logic controller (PLC), or edge gateway) needs to establish communication links with multiple independent devices to separately acquire data and issue control commands. As the number of devices continues to increase, this point-to-point independent management approach faces significant challenges in terms of communication resource utilization, real-time scheduling capabilities, and system management complexity.

[0003] Aggregation control technology, as a technique that abstracts multiple physical links or devices into a logical group for unified management, represents a potential solution to the aforementioned problems. Currently, various aggregation-related technologies exist in the industrial sector, but all have significant limitations and cannot meet the efficient management needs of large-scale field device clusters.

[0004] One existing technology is link aggregation (IEEE 802.3ad) in industrial Ethernet. This technology bundles multiple physical network ports into a single logical link, primarily used to increase network bandwidth and provide link redundancy. Link aggregation operates at Layer 2 of the OSI model, is transparent to upper-layer protocols, and is widely used in bandwidth expansion scenarios between switches or between servers and switches. Its configuration methods include static manual aggregation and dynamic aggregation based on the Link Aggregation Control Protocol (LACP). However, this technology has the following inherent drawbacks: It only applies to bandwidth aggregation at the network interface level and does not involve the aggregation control of multiple independent field devices (such as BMS systems), thus failing to achieve unified management at the device level. It lacks device-level data acquisition and command issuance multicast capabilities, and cannot send targeted control commands to multiple devices simultaneously; The lack of a device identification mapping mechanism, especially the lack of mapping from non-IP bus addresses such as CAN ID and RS485 address to IP addresses, makes it unsuitable for unified management of heterogeneous bus devices. It does not support control strategy priority division and failure feedback mechanism, and cannot meet the strict requirements for real-time performance and reliability in industrial control scenarios.

[0005] Existing technology two is the master-slave polling mode in industrial fieldbuses. In this mode, a master device connects to multiple slave devices via a single bus, and the master polls each slave in turn to obtain data or issue commands. Some systems support broadcast commands, but broadcast commands can usually only be sent to all slaves on the bus, and cannot flexibly specify a particular group of slaves. This technology is widely used in traditional industrial fieldbus systems such as Modbus RTU and CANopen. However, this technology also has the following significant drawbacks: Serial polling is inefficient. As the number of slave stations increases, the communication cycle of the system increases linearly, which seriously affects the real-time performance of the system. Broadcast commands lack selectivity, making it impossible to achieve fine-grained multicast control and easily causing unnecessary network traffic and device load; Each slave station has a fixed address, lacks dynamic mapping and automatic aggregation capabilities, requires manual configuration for new device access, and has poor system scalability; It does not support the aggregated management of multiple independent bus systems. Each bus requires an independent master station interface, which increases the hardware cost and management complexity of the system.

[0006] In summary, existing technologies cannot effectively solve the problems of low communication resource utilization, difficulty in real-time scheduling, complex management, and inability to uniformly manage heterogeneous bus devices in large-scale field device cluster management. Therefore, there is an urgent need for a new clustered field device aggregation control method. Summary of the Invention

[0007] The purpose of this invention is to provide a clustered field device aggregation control method to solve the problems mentioned in the background art.

[0008] To solve the above-mentioned technical problems, the present invention provides the following technical solution: A clustered field device aggregation control method includes the following steps: Aggregated interface management divides the physical interfaces on the domain controller that connect to multiple independent field devices into one or more aggregate groups according to preset rules, and assigns a unique aggregate group ID to each aggregate group. Aggregate identification and routing mapping: Assign a unique domain ID and node ID to each field device, and maintain a routing mapping table containing aggregation group ID, domain ID, node ID, physical interface ID, and bus address to realize the conversion from logical address to physical address; Aggregated data acquisition involves collecting data from multiple field devices within an aggregation group simultaneously using parallel polling or event-triggered methods, and then aggregating the collected data into a unified data packet for reporting or local processing. Aggregate control is issued by constructing an aggregation control frame containing the aggregation group ID, target node list, control command, parameters, and priority. Commands are issued in parallel through relevant physical interfaces, and execution results are collected and processed subsequently.

[0009] Furthermore, the physical interfaces include Ethernet interfaces, CAN interfaces, and RS485 interfaces, and the preset rules include device geographical location, device type, control priority, and functional module division.

[0010] Furthermore, for field devices using non-IP buses, their internal bus addresses are incorporated into the identification system; the upper-layer system uses a unified logical address to access any node, and the lower-layer driver automatically converts it to the corresponding physical interface and bus protocol address.

[0011] Furthermore, the data acquisition modes include: unicast mode, which collects data from only a single specified node; multicast mode, which collects data from a group of specified nodes within an aggregation group simultaneously; and broadcast mode, which collects data from all nodes within an aggregation group. For multicast control commands, they are only sent to the physical interface containing the target node. Each field device executes the control commands in parallel, and the domain controller collects the execution results from all devices.

[0012] Furthermore, it also includes the steps of automatic aggregation and manual aggregation. Automatic aggregation involves the domain controller periodically sending device discovery broadcasts. After a newly connected device responds, it is automatically added to the appropriate aggregation group and the routing table is updated according to preset rules. Manual aggregation involves the administrator manually selecting the device interface to be aggregated and configuring the aggregation group ID, aggregation policy, and priority. The aggregation policy includes load balancing mode and primary / backup mode.

[0013] Furthermore, it also includes the step of: aggregated feature association data mapping, which associates the overall operating characteristics of the aggregated group with the aggregated group ID, and the upper-level system directly obtains the aggregated statistical values ​​by reading the virtual sensor corresponding to the aggregated group ID; the overall operating characteristics include the total current, average voltage, highest temperature, lowest SOC and number of faults of all devices in the aggregated group.

[0014] Furthermore, it also includes the step of: aggregated port virtualization. When the domain controller has only a few physical ports and uses a daisy chain to connect multiple devices, virtual aggregated ports are created through software. Each virtual port corresponds to a logical device connection, and the mapping between virtual ports and physical ports is handled by the internal forwarding module.

[0015] Furthermore, it also includes the following steps: policy priority and feedback mechanism, setting a priority of 0~255 for each aggregation control policy, and allowing high-priority instructions to preempt the transmission resources of low-priority instructions; when control fails, retry, downgrade, report or local backup policies are executed according to preset policies; the retry operation is executed up to 3 times; the local backup policy includes closing the corresponding channel or switching to a backup device.

[0016] Furthermore, the field devices include a battery management system, industrial sensor nodes, and actuator units within the energy storage system.

[0017] Furthermore, the routing table also includes an IP address field for devices that support the IP protocol.

[0018] This application also discloses an electronic device, including: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform the clustered field device aggregation control method of the present invention described above.

[0019] Beneficial effects: Communication resource utilization is significantly improved. By using aggregation groups to uniformly schedule communication resources, the bandwidth fragmentation problem caused by multiple independent communication links is avoided, and the overall bandwidth utilization is improved by 30% to 50%.

[0020] The system's real-time performance has been greatly improved. By adopting multicast and parallel acquisition / control methods, the completion time of multi-device collaborative tasks has been shortened to 1 / N of the traditional serial method (where N is the number of devices in the aggregation group), which can meet the strict real-time requirements in industrial control scenarios.

[0021] The complexity of system management is significantly reduced. The upper-level system only needs to interact with the aggregation group and does not need to care about the number of specific devices, interface types and communication protocols, which greatly simplifies the software architecture and reduces the system development and maintenance costs.

[0022] It supports unified addressing and management of heterogeneous bus devices. Through a global routing mapping table, it realizes unified logical addressing and multicast control of various bus devices such as CAN, RS485, and Ethernet, thereby improving the system's compatibility and scalability.

[0023] The system is flexible and convenient to expand. The automatic aggregation function supports plug-and-play devices. New devices can be automatically added to the appropriate aggregation group after being connected, without the need for manual configuration during system downtime, which greatly shortens the system deployment and expansion time.

[0024] Supporting edge intelligent computing, the domain controller can perform local aggregation calculations (such as averages, extreme values, statistical analysis, etc.) within the aggregation group, reducing the amount of data uploaded to the cloud and lowering network bandwidth consumption and cloud computing burden. Attached Figure Description

[0025] Figure 1 This is a schematic diagram illustrating the aggregation and connection between the domain controller and multiple BMS in an embodiment of the present invention; Figure 2 This is a diagram of the aggregation control frame format in an embodiment of the present invention; Figure 3 This is a flowchart of the automatic aggregation process in an embodiment of the present invention; Figure 4 This is a timing comparison diagram of multicast command issuance in an embodiment of the present invention. Detailed Implementation

[0026] The technical solutions of the present invention will be clearly and completely described below with reference to the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present invention.

[0027] This invention provides a clustered field device aggregation control method, comprising the following steps: Aggregated interface management divides the physical interfaces on the domain controller that connect to multiple independent field devices into one or more aggregate groups according to preset rules, and assigns a unique aggregate group ID to each aggregate group. Aggregate identification and routing mapping: Assign a unique domain ID and node ID to each field device, and maintain a routing mapping table containing aggregation group ID, domain ID, node ID, physical interface ID, and bus address to realize the conversion from logical address to physical address; Aggregated data acquisition involves collecting data from multiple field devices within an aggregation group simultaneously using parallel polling or event-triggered methods, and then aggregating the collected data into a unified data packet for reporting or local processing. Aggregate control is issued by constructing an aggregation control frame containing the aggregation group ID, target node list, control command, parameters, and priority. Commands are issued in parallel through relevant physical interfaces, and execution results are collected and processed subsequently.

[0028] This invention provides a clustered field device aggregation control method. The method runs on a domain controller or edge gateway. Its core idea is to abstract multiple independent field devices connected to the domain controller into one or more aggregation groups. All devices in the aggregation group are regarded as a logical whole, and unified data acquisition and control command issuance are performed.

[0029] The specific technical solution includes the following steps: Aggregated interface management: The domain controller is configured with multiple physical interfaces, including but not limited to Ethernet, CAN, and RS485 interfaces, each connected to an independent field device. These physical interfaces are divided into one or more aggregation groups according to preset rules, and each aggregation group is assigned a unique aggregation group ID. The preset rules include, but are not limited to, device geographical location, device type, control priority, and functional module division.

[0030] Aggregate identification and routing mapping assign unique domain IDs and node IDs to each field device. For field devices using non-IP buses, their internal bus addresses are also included in the identification system. The domain controller maintains a global routing mapping table containing the following fields: aggregation group ID, domain ID, node ID, IP address (if the device supports the IP protocol), physical interface ID, and internal bus address. Through this routing mapping table, the upper-layer system can access any field device node using a unified logical address (domain ID + node ID), and the underlying driver automatically translates the logical address into the corresponding physical interface and bus protocol address.

[0031] Aggregated data acquisition: The domain controller uses aggregation groups to simultaneously acquire data from multiple field devices within the aggregation group, employing either parallel polling or event-triggered methods. Three data acquisition modes are supported: In unicast mode, data is collected from only a single specified node, and the target device is precisely located using the domain ID + node ID. In multicast mode, data from a specified set of nodes within an aggregation group is collected simultaneously, with the target device set specified by a list of node IDs. Broadcast mode collects data from all nodes within the aggregation group.

[0032] After data collection is complete, the domain control unit aggregates the data returned by multiple field devices into a unified data packet, which is then reported to the upper-level energy management system (EMS) or processed locally.

[0033] Aggregated control is issued when the upper-layer EMS or local control policy needs to control multiple field device nodes. The domain controller then creates an aggregated control frame. For example... Figure 2As shown, the aggregation control frame contains the following fields: aggregation group ID, target node list (domain ID + node ID), control command, command parameters, and priority. The domain controller sends control commands in parallel through all relevant physical interfaces within the aggregation group. For multicast control commands, they are only sent to the physical interface containing the target node. Each field device executes the control commands in parallel, and the domain controller collects the execution results (success / failure) from all devices and performs subsequent processing according to the command priority and the preset feedback mechanism.

[0034] Both automatic and manual aggregation are supported for creating and managing aggregation groups. Automatic aggregation: The domain controller periodically sends device discovery broadcasts. After a newly connected field device responds, the domain controller parses the device's type, location, function and other attribute information, adds it to the appropriate aggregation group according to the preset automatic aggregation rules, and automatically updates the routing table. Manual aggregation allows administrators to manually select the field device interfaces to be aggregated and configure parameters such as aggregation group ID, aggregation policy (e.g., load balancing, master / standby mode), and control priority through a local command-line interface or a web management interface.

[0035] Aggregate feature-based data mapping associates the overall operational characteristics of an aggregation group with its aggregation group ID. These overall operational characteristics include, but are not limited to, the total current, average voltage, highest temperature, lowest SOC (state of charge), and number of faults for all devices within the aggregation group. The upper-layer system can directly obtain these aggregated statistics by reading the "virtual sensor" corresponding to the aggregation group ID, without needing to access each node within the aggregation group individually.

[0036] Aggregated port virtualization allows for the creation of virtual aggregated ports (VPorts) in software when the domain controller has only a few physical ports and uses a daisy-chain connection to multiple field devices. Each virtual aggregated port corresponds to a logical field device connection. The mapping between virtual ports and physical ports is handled by the forwarding module within the domain controller, while the aggregation control method described above remains unchanged. This approach achieves the reuse and logical isolation of physical ports, supporting flexible management of large-scale device clusters.

[0037] The policy prioritization and feedback mechanism assigns a priority to each aggregated control policy, ranging from 0 to 255, with higher values ​​indicating higher priority. High-priority commands (such as over-temperature protection and emergency shutdown commands) can preempt the transmission resources of low-priority commands, ensuring the real-time performance of critical control commands. When a control command fails to execute, the domain controller performs one or a combination of the following actions according to the preset failure handling strategy: retry (up to 3 retries), degrade execution (reducing the number of target devices or adjusting control parameters), reporting the failure information to the upper-level EMS, or executing a local backup control policy (such as closing the corresponding channel or switching to a backup device).

[0038] The present invention will now be described in further detail with reference to the accompanying drawings and specific embodiments. Example 1

[0039] This embodiment takes BMS cluster management in a large-scale energy storage system as an example to illustrate the specific implementation of the present invention.

[0040] As shown in Figure 1, the domain controller in this embodiment is configured with two physical Ethernet ports (eth0 and eth1), which are connected to four independent BMS systems (BMS0, BMS1, BMS2, and BMS3) via a daisy chain. Each BMS system manages 20 battery packs, for a total of 80 battery pack nodes.

[0041] Since the domain controller appliance only has two physical ports, it cannot directly connect to four BMS systems. Therefore, aggregated port virtualization technology is used. Four virtual aggregated ports (VPort0, VPort1, VPort2, and VPort3) are created on the domain controller appliance via software, with each virtual port corresponding to a logical BMS connection. The mapping between virtual ports and physical ports is handled by the forwarding module inside the domain controller: VPort0 and VPort1 are mapped to physical port eth0, and VPort2 and VPort3 are mapped to physical port eth1.

[0042] The administrator manually created two aggregation groups through the web management interface: Aggregation group A (ID=1): contains BMS0 and BMS1, corresponding to virtual ports VPort0 and VPort1; Aggregation group B (ID=2): contains BMS2 and BMS3, corresponding to virtual ports VPort2 and VPort3.

[0043] The global routing mapping table maintained by the domain controller is shown in Table 1 below. The specific contents are as follows: Table 1 Global routing mapping table maintained by the domain controller Example of data acquisition process: When the upper-level EMS needs to read the voltage data of all 40 battery packs in aggregation group A, the EMS sends an aggregation read command to the domain controller. The command contains aggregation group ID=1 and the target node list is empty (meaning that all nodes in the aggregation group are read).

[0044] After receiving the command, the domain controller queries the routing table to determine that aggregation group A contains node 0 and node 1, corresponding to virtual ports VPort0 and VPort1 respectively. The domain controller then sends voltage read requests to BMS0 and BMS1 in parallel through these two virtual ports.

[0045] Upon receiving the request, BMS0 and BMS1 collect voltage data from the 20 battery packs they each manage in parallel and return the data to the domain controller. The domain controller then aggregates the data returned by the two BMSs into a unified data packet containing voltage data for all 40 battery packs and sends it back to the EMS.

[0046] The total time for the entire data acquisition process is approximately equal to the response time of a single BMS (approximately 100ms), while the traditional serial method requires 4 instruction cycles (approximately 400ms), thus improving real-time performance by 75%.

[0047] Example of control command issuance process: When the upper-level EMS needs to perform equalization charging control on all battery packs within aggregation group B, the EMS sends an aggregation control command to the domain controller, which includes: Aggregation group ID=2; The target node list is empty (meaning it controls all nodes within the aggregation group); Control command = Equalize charging; Command parameter = Charging current 5A; Priority = 100; After receiving the command, the domain controller queries the routing table to determine that aggregation group B contains node 2 and node 3, corresponding to virtual ports VPort2 and VPort3 respectively. The domain controller then sends equalization charging control commands to BMS2 and BMS3 in parallel through these two virtual ports.

[0048] After receiving the command, BMS2 and BMS3 execute the equalization charging operation in parallel and return the execution results to the domain controller. The domain controller collects the execution results of the two BMSs. If both are successful, it returns a success message to the EMS. If one of the BMSs fails, it retryes according to the preset failure handling policy (up to 3 times). If the retry still fails, it reports partial failure information to the EMS and marks the BMS as offline.

[0049] Example of an automated aggregation process: As shown in Figure 3, the domain controller periodically (every 30 seconds) sends a device discovery broadcast. When a new BMS system connects to the network, the BMS will respond to the device discovery broadcast and send its own device information to the domain controller, including device type, serial number, location information, supported communication protocols, etc.

[0050] After receiving a response from a new device, the domain controller parses the device information and, based on preset automatic aggregation rules (such as "all BMS located in Battery Compartment 1 will be automatically added to aggregation group A"), adds the new device to the corresponding aggregation group and automatically updates the routing table. The entire process requires no manual intervention, achieving plug-and-play functionality for the device.

[0051] Multicast command issuance timing comparison: As shown in Figure 4, in the traditional serial mode, the EMS needs to send commands to BMS0, BMS1, BMS2, and BMS3 sequentially, and each command needs to wait for a response from the previous command, thus requiring a total of 4 command cycles. However, using the multicast method of this invention, the EMS only needs to send one aggregation command, and the domain controller sends commands to the 4 BMSs in parallel. All 4 BMSs respond simultaneously, so control of all devices can be completed in just 1 command cycle. Example 2

[0052] This embodiment takes the unified management of heterogeneous bus devices as an example to illustrate how the technical solution of the present invention solves the problem of the inability to manage heterogeneous bus devices in a unified manner.

[0053] In this embodiment, the domain controller is equipped with multiple physical interfaces: two Ethernet interfaces, two CAN interfaces, and one RS485 interface. Connected field devices include: Two Ethernet interfaces: connect two BMS systems (BMS0, BMS1); Two CAN interfaces: connect to two temperature acquisition modules (TC0, TC1), each module managing 16 temperature sensors; One RS485 interface: connects to one air conditioner controller (AC0).

[0054] The administrator creates an aggregation group "Data Center Environment and Energy Storage Monitoring Group" (ID=3) containing all the above-mentioned devices. The routing mapping table maintained by the domain controller is shown in Table 2 below: Table 2. Routing Mapping Table Maintained by Domain Controller When the upper-level EMS needs to obtain the operational status of the entire data center, it only needs to send an aggregate read command, targeting aggregation group ID=3. Upon receiving the command, the domain controller sends data acquisition requests to all five devices in parallel: Send Ethernet TCP requests to BMS0 and BMS1 to obtain data such as battery voltage, current, and SOC; Send CAN messages to TC0 and TC1 to obtain temperature sensor data; Send an RS485 message to AC0 to obtain data such as the air conditioner's operating status and set temperature.

[0055] All devices return data in parallel. The domain controller converts this data, which uses different protocols and formats, into a unified standard format, aggregating it into a single data packet containing the operating status of all devices, and then reports it to the EMS. The upper-layer EMS does not need to concern itself with the communication protocols and interface types of the underlying devices; it can access all devices simply through a unified logical address, greatly simplifying system integration. Example 3

[0056] This embodiment uses a high-priority instruction preemption mechanism as an example to illustrate how the strategy priority and feedback mechanism of the present invention ensures the security and reliability of the system.

[0057] In this embodiment, the domain controller is executing a low-priority battery capacity calibration task (priority = 50). This task requires sending calibration instructions to all BMSs within the aggregation group and waiting for all BMSs to return calibration results.

[0058] During task execution, a BMS detected that the battery temperature exceeded the safety threshold (60°C) and sent an over-temperature alarm to the domain controller. Upon receiving the alarm, the domain controller immediately generated a high-priority emergency shutdown command (priority = 255).

[0059] Because the emergency shutdown command has higher priority than the ongoing capacity calibration task, the domain controller immediately suspends the capacity calibration task, seizes all available communication resources, and prioritizes sending the emergency shutdown command to all BMSs. Upon receiving the command, all BMSs immediately cut off battery output to ensure system safety.

[0060] After the emergency stop command is executed, the domain controller reports the over-temperature alarm and the emergency stop result to the EMS. Once the fault is resolved, the domain controller can resume the interrupted capacity calibration task or initiate a new control task as needed.

[0061] If a BMS communication fails when sending an emergency shutdown command, the domain controller will immediately retry sending the command (up to 3 times). If the retry still fails, the local backup strategy will be executed: the main contactor of the battery cluster corresponding to the BMS will be disconnected, a serious fault information will be reported to the EMS, and an audible and visual alarm will be activated to notify maintenance personnel to handle the situation promptly.

[0062] This application also provides an embodiment of an electronic device. The electronic device is manifested in the form of a general-purpose computing device. The components of the electronic device may include, but are not limited to: one or more processors or processing units, memory, and buses connecting different components (including memory and processing units).

[0063] A bus refers to one or more of several bus architectures, including memory buses or memory controllers, peripheral buses, graphics acceleration ports, processors, or local buses using any of the various bus architectures. Examples of these architectures include, but are not limited to, Industry Standard Architecture (ISA) buses, Micro Channel Architecture (MCA) buses, Enhanced ISA buses, Video Electronics Standards Association (VESA) local buses, and Peripheral Component Interconnect (PCI) buses.

[0064] Electronic devices typically include a variety of computer-readable media. These media can be any available media that can be accessed by the electronic device, including volatile and non-volatile media, and removable and non-removable media.

[0065] The memory may include computer-readable media in the form of volatile memory, such as random access memory (RAM) and / or cache memory. Electronic devices may further include other removable / non-removable, volatile / non-volatile computer device storage media. By way of example only, the storage system may be used to read and write non-removable, non-volatile magnetic media.

[0066] The electronic device can also communicate with one or more external devices (e.g., keyboard, pointing device, camera, etc.), may include a display, and may communicate with one or more devices that enable a user to interact with the electronic device, and / or with any device that enables the electronic device to communicate with one or more other computing devices (e.g., network card, modem, etc.). This communication can be performed via an input / output (I / O) interface. Furthermore, the electronic device can also communicate with one or more networks (e.g., Local Area Network (LAN), Wide Area Network (WAN) and / or public networks, such as the Internet) via a network adapter. The network adapter communicates with other modules of the electronic device via a bus. The processor executes various functional applications and data processing by running programs stored in memory, such as implementing the clustered field device aggregation control method provided in the above embodiments of the present invention.

[0067] Finally, it should be noted that the above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing embodiments or make equivalent substitutions for some of the technical features. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A clustered field device aggregation control method, characterized in that, Includes the following steps: Aggregated interface management divides the physical interfaces on the domain controller that connect to multiple independent field devices into one or more aggregate groups according to preset rules, and assigns a unique aggregate group ID to each aggregate group. Aggregate identification and routing mapping: Assign a unique domain ID and node ID to each field device, and maintain a routing mapping table containing aggregation group ID, domain ID, node ID, physical interface ID, and bus address to realize the conversion from logical address to physical address; Aggregated data acquisition involves collecting data from multiple field devices within an aggregation group simultaneously using parallel polling or event-triggered methods, and then aggregating the collected data into a unified data packet for reporting or local processing. Aggregate control is issued by constructing an aggregation control frame containing the aggregation group ID, target node list, control command, parameters, and priority. Commands are issued in parallel through relevant physical interfaces, and execution results are collected and processed subsequently.

2. The clustered field device aggregation control method according to claim 1, characterized in that, The physical interfaces include Ethernet, CAN, and RS485 interfaces, and the preset rules include device geographical location, device type, control priority, and functional module division.

3. The clustered field device aggregation control method according to claim 1, characterized in that, For field devices using non-IP buses, their internal bus addresses are incorporated into the identification system; the upper-layer system uses a unified logical address to access any node, and the lower-layer driver automatically converts it to the corresponding physical interface and bus protocol address.

4. The clustered field device aggregation control method according to claim 1, characterized in that, The data acquisition modes include: unicast mode, which collects data from only a single specified node; multicast mode, which collects data from a group of specified nodes within an aggregation group simultaneously; and broadcast mode, which collects data from all nodes within an aggregation group. For multicast control commands, they are only sent to the physical interface containing the target node. Each field device executes the control commands in parallel, and the domain controller collects the execution results from all devices.

5. The clustered field device aggregation control method according to claim 1, characterized in that, The process also includes the steps of automatic aggregation and manual aggregation. Automatic aggregation involves the domain controller periodically sending device discovery broadcasts. After a newly connected device responds, it is automatically added to the appropriate aggregation group and the routing table is updated according to preset rules. Manual aggregation involves the administrator manually selecting the device interface to be aggregated and configuring the aggregation group ID, aggregation policy, and priority. The aggregation policy includes load balancing mode and primary / backup mode.

6. The clustered field device aggregation control method according to claim 1, characterized in that, It also includes the step of: aggregate feature association data mapping, which associates the overall operating characteristics of the aggregate group with the aggregate group ID. The upper-level system directly obtains the aggregate statistics by reading the virtual sensor corresponding to the aggregate group ID. The overall operating characteristics include the total current, average voltage, highest temperature, lowest SOC and number of faults of all devices in the aggregate group.

7. The clustered field device aggregation control method according to claim 1, characterized in that, It also includes the step of: aggregated port virtualization. When the domain controller has only a few physical ports and uses a daisy chain to connect multiple devices, virtual aggregated ports are created through software. Each virtual port corresponds to a logical device connection, and the mapping between virtual ports and physical ports is handled by the internal forwarding module.

8. The clustered field device aggregation control method according to claim 1, characterized in that, It also includes the following steps: policy priority and feedback mechanism, setting a priority of 0~255 for each aggregation control policy, and allowing high-priority instructions to preempt the transmission resources of low-priority instructions; when control fails, retry, downgrade, report or local backup policies are executed according to preset policies; the retry operation is executed up to 3 times; the local backup policy includes closing the corresponding channel or switching to a backup device.

9. The clustered field device aggregation control method according to claim 1, characterized in that, The field devices include a battery management system, industrial sensor nodes, and actuator units within the energy storage system.

10. The clustered field device aggregation control method according to claim 1, characterized in that, The routing table also includes an IP address field for devices that support the IP protocol.

Images