Highly flexible configurable multi-measuring-point equipment linkage control system and method

Abstract

The invention relates to a multi-measuring-point equipment linkage control system and method for an industrial monitoring scene, and the system is characterized in that a rule configuration module supports a user to define a linkage rule in a JSON format, and the linkage rule comprises condition subitems, execution results and multi-dimensional time parameters (condition duration, output duration and convergence time interval); signal anti-shake, action timing control and prevention of frequent start and stop of an execution mechanism are realized; the linkage engine module is responsible for loading and analyzing rules, circularly collecting measuring point data and triggering execution actions when conditions are met; the interface adaptation module manages various protocol interfaces such as RS485, DI / DO and Ethernet in a unified mode, and seamless access and measuring point data mapping of heterogeneous equipment are achieved. Through a multi-dimensional time cooperative control mechanism, the linkage control is upgraded from discrete triggering to refined process control, the reliability and stability of the system are remarkably improved, the service life of the system is remarkably prolonged, and the system is suitable for various industrial monitoring scenes such as machine rooms, transformer substations and intelligent buildings.

Description

Technical Field

[0001] This invention relates to the field of industrial monitoring technology, and in particular to a highly flexible and configurable multi-point device linkage control system and method. Background Technology

[0002] With the rapid development of the Industrial Internet of Things (IIoT), a large number of heterogeneous devices are commonly found in industrial monitoring scenarios such as computer rooms, substations, and smart buildings. These include temperature and humidity sensors, smoke detectors, and digital input (DI) and digital output (DO) actuators connected via serial interfaces such as RS485 and RS232. These devices typically use different communication protocols and data formats, leading to high system integration complexity.

[0003] In existing technologies, equipment linkage control mainly adopts the following two schemes:

[0004] The first method is hard-coding: developers pre-write fixed program code to bind the acquisition signals of specific devices to the execution actions. This method has obvious drawbacks: (1) poor flexibility, the source code needs to be modified and redeployed when the device is changed or the logic is adjusted; (2) weak scalability, the linkage logic needs to be redesigned when adding new devices, and the development cycle is long; (3) poor user experience, the end users cannot define the rules themselves and rely on the developers; (4) high maintenance cost, high system coupling and difficult debugging.

[0005] The second type is a configurable method based on rule engines: For example, Chinese invention patent application CN113423294A discloses an IoT device linkage control method based on rule engines, which uses a device abstract model and JSON format to configure rules and supports "IF-THEN" logic combinations. This technology solves the flexibility problem of hard coding to a certain extent, but still has the following shortcomings: (1) The device abstraction granularity is relatively coarse, only realizing device-level mapping, and not performing fine-grained abstraction of multiple measurement points inside the device; (2) The timing control mechanism is simple, only supporting simple time delay, lacking multi-dimensional time collaborative control capabilities, and cannot effectively cope with the instantaneous jump of sensors and the frequent start and stop of actuators in industrial scenarios; (3) The rule configuration syntax is more universal but less adaptable to the domain, making it difficult to meet the standardized deployment requirements of industrial monitoring.

[0006] In summary, existing technologies have failed to fully address the challenges of optimizing the flexibility, stability, and ease of use in the coordinated control of heterogeneous devices in industrial monitoring scenarios. There is an urgent need for a coordinated control system that better meets actual industrial needs, possesses refined configuration capabilities, and has a multi-dimensional timing control mechanism. Summary of the Invention

[0007] The purpose of this invention is to provide a highly flexible and configurable multi-measurement point device linkage control system and method, thereby solving the aforementioned problems existing in the prior art.

[0008] To achieve the above objectives, the technical solution adopted by the present invention is as follows:

[0009] A multi-point device linkage control system for industrial monitoring scenarios includes:

[0010] The configuration management module is used to abstract physical devices into logical peripherals and assign unique peripheral codes. It configures at least one measurement point for each peripheral and assigns a measurement point code, forming a two-level abstract configuration of devices and measurement points.

[0011] The rule configuration module is used to receive the linkage rules defined by the user in JSON format. The linkage rule includes a trigger condition consisting of at least one condition sub-item, the execution result corresponding to the trigger condition, and a convergence time interval to prevent the rule from being triggered frequently. Each condition sub-item includes a formulaic expression based on peripheral encoding and measurement point encoding: #peripheral encoding@measurement point encoding@attribute#, and a condition duration parameter for filtering transient interference.

[0012] The linkage engine module is used to load and parse linkage rules, collect real-time data from each measuring point in a loop, and trigger the execution of the result when the trigger condition is continuously met within the condition duration parameter and the convergence time interval is met. The duration of the execution action is controlled according to the preset output duration parameter.

[0013] The interface adapter module is used to uniformly manage multiple interface protocols such as RS485, digital input (DI) / digital output (DO), and Ethernet, enabling unified access of heterogeneous devices and mapping of measurement point data.

[0014] Furthermore, the linkage engine module includes a configuration parsing unit, a data acquisition unit, a rule judgment unit, and an action scheduling unit. The configuration parsing unit constructs a rule linked list structure in memory, the rule judgment unit replaces the encoded references in the formulaic expression with real-time values ​​to form a computable logical expression, and the action scheduling unit generates control instructions and starts a timer to manage the output duration.

[0015] Furthermore, the condition duration parameter is used to eliminate sensor transient fluctuation interference in industrial monitoring scenarios, the output duration parameter is used to control the action holding time of the actuator, and the convergence time interval is used to prevent the actuator from frequently starting and stopping due to repeated fulfillment of conditions. The three work together to form a multi-dimensional time control mechanism to improve system stability.

[0016] Furthermore, the interface adapter module includes an RS485 interface management unit, a DI / DO interface management unit, and an Ethernet interface management unit. The RS485 interface management unit supports dynamic access of Modbus RTU protocol devices, and the DI / DO interface management unit is used to map digital input and output signals to measurement point status.

[0017] Furthermore, the system is applied to scenarios such as fire alarm linkage, temperature and humidity over-limit alarm, and equipment start-up and shutdown control in computer room environment monitoring, substation automation, and intelligent building management, enabling users to configure it independently without modifying the source code.

[0018] Based on the same concept, a multi-point device linkage control method for industrial monitoring scenarios includes the following steps:

[0019] Step S1: Abstract the physical device into a logical peripheral through the configuration management module and assign a unique peripheral code. Assign a measurement point code to the measurement point of each peripheral and establish a two-level abstract configuration between the device and the measurement point.

[0020] Step S2: Receive the linkage rules defined by the user in JSON format through the rule configuration module. The linkage rules include a trigger condition consisting of at least one condition sub-item, the execution result corresponding to the trigger condition, and a convergence time interval to prevent the rule from being triggered frequently. Each condition sub-item includes a formulaic expression based on peripheral encoding and measurement point encoding: #peripheral encoding@measurement point encoding@attribute#, and a condition duration parameter for filtering transient interference.

[0021] Step S3: The linkage engine module loads and parses the linkage rules, and collects real-time data from each measuring point in a loop;

[0022] Step S4: When the triggering condition is continuously satisfied within the condition duration parameter and the convergence time interval is met, the execution result is triggered, and the duration of the execution action is controlled according to the preset output duration parameter.

[0023] Step S5: Through the interface adapter module, manage multiple protocol interfaces such as RS485, DI / DO, and Ethernet in a unified manner to realize unified access of heterogeneous devices and mapping of measurement point data.

[0024] Furthermore, step S4 specifically includes: traversing each linkage rule and replacing the formulaic expression with a real-time value; determining whether the triggering condition is effectively met based on the linkage method type and condition duration parameter; executing the action definition in the result list and generating the corresponding interface control instruction after the convergence interval expires; starting a timer to manage the output duration and automatically canceling the output after the duration expires.

[0025] Furthermore, the conditional duration parameter is used for anti-jitter filtering, the output duration parameter is used for timing control, and the convergence time parameter is used to prevent frequent rule triggering. The three constitute a multi-dimensional time-coordinated control mechanism, which effectively reduces the false trigger rate and equipment wear in industrial monitoring scenarios.

[0026] Furthermore, the method is applicable to scenarios such as computer room environment monitoring, substation automation, and intelligent building management, enabling fire alarm linkage, temperature and humidity over-limit linkage, and equipment status linkage control, and supports end-user self-configuration without the need for developer intervention.

[0027] Furthermore, when adding new equipment or measurement points, only the configuration needs to be updated without modifying the program code. The system configuration efficiency is significantly improved compared to the traditional hard-coding method, supporting the need for rapid on-site deployment.

[0028] The beneficial effects of this invention are:

[0029] Significantly improved configuration flexibility: Through two-level abstract configuration and JSON rule definition, users can complete device access and logic adjustment on-site without the need for developer intervention, greatly accelerating the response speed and meeting the rapid deployment needs of industrial scenarios.

[0030] Enhanced system stability: The multi-dimensional time-coordinated control mechanism effectively eliminates transient interference, prevents frequent start-stop of actuators, significantly reduces the risk of false triggering, and extends equipment lifespan.

[0031] Scalability and maintainability optimization: Adding new devices or measurement points only requires parameter configuration through configuration tools, reducing system integration complexity and maintenance costs. Visual configuration of linkage logic facilitates troubleshooting and rule adjustment.

[0032] Highly adaptable to industrial scenarios: Designed for specific scenarios such as computer rooms, substations, and smart buildings, it supports multiple industrial protocols such as RS485, DI / DO, and Ethernet, and has wide applicability. Attached Figure Description

[0033] Figure 1 This is a schematic diagram of the overall architecture of the multi-measuring-point device linkage control system of the present invention;

[0034] Figure 2 This is a flowchart of the multi-measuring-point device linkage control method of the present invention;

[0035] Figure 3 This is a flowchart of another embodiment of the present invention. Detailed Implementation

[0036] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention.

[0037] Reference Figure 1 , Figure 2 and Figure 3 The multi-measurement point device linkage control system for industrial monitoring scenarios includes a configuration management module, which abstracts physical devices into logical peripherals and assigns unique peripheral codes, configures at least one measurement point for each peripheral and assigns a measurement point code, forming a two-level abstract configuration of devices and measurement points; a rule configuration module, which receives linkage rules defined by users in JSON format, where each linkage rule includes a trigger condition consisting of at least one conditional item, the execution result corresponding to the trigger condition, and a convergence time interval to prevent frequent triggering of the rule, wherein each conditional item includes a formulaic expression based on the peripheral code and measurement point code: #peripheral code@measurement point code@attribute#, and a condition duration parameter for filtering transient interference; a linkage engine module, which loads and parses the linkage rules, cyclically collects real-time data from each measurement point, and triggers the execution result when the trigger condition is continuously satisfied within the condition duration parameter and the convergence time interval is met, and controls the duration of the execution action according to a preset output duration parameter; and an interface adaptation module, which uniformly manages multiple interface protocols such as RS485, digital input (DI) / digital output (DO), and Ethernet to achieve unified access and measurement point data mapping for heterogeneous devices.

[0038] In this embodiment, the overall system architecture and module collaborative working mechanism are as follows: This invention provides a multi-measurement point device linkage control system for industrial monitoring scenarios. The system adopts a modular, layered architecture design, achieving flexible linkage control of heterogeneous industrial equipment through the organic collaboration of four core functional modules. The system is deployed entirely within a monitoring host, completing initial configuration through interaction with the management host via a configuration tool, and then independently executing real-time linkage tasks. The configuration management module serves as the abstraction foundation of the system, and its functionality is implemented in two layers: a peripheral abstraction layer and a measurement point mapping layer. In the peripheral abstraction layer, the module receives user-input interface parameters and device address information through the configuration tool, uniformly registering various sensors and actuators connected in the physical world via RS485 serial bus, DI / DO hardwiring, or Ethernet links as logical peripherals. Each logical peripheral is assigned a unique peripheral code, which serves as the device's global identifier within the system, permeating the entire process of rule definition, data storage, and instruction scheduling. In the measurement point mapping layer, the module configures one or more measurement point objects for each logical peripheral's data acquisition or control attributes. Each measurement point object contains metadata attributes such as measurement point code, data type, measurement range, and acquisition frequency. The measurement point code and peripheral code together constitute a two-level abstract system of "peripheral code + measurement point code". The key to this system is that when field equipment is changed or expanded, users only need to adjust the registration information of peripherals and measurement points through configuration tools. No code-level modifications are required at the linkage control logic level, thus achieving a high degree of decoupling between equipment hardware and linkage rules. The rule configuration module is responsible for the semantic definition and structured storage of linkage logic. The module provides a rule description language based on JSON format, allowing users to build "condition-result" causal chains in a visual manner through configuration tools. At the rule structure level, each linkage rule contains six core elements: rule identifier, rule name, linkage method type, condition array, result array, and convergence time interval. The linkage method type defines the logical relationship between each item in the condition array, supporting two combination modes: logical "AND" and logical "OR". The condition array consists of at least one condition sub-item, each using a formulaic expression as the basis for judgment. This expression is based on a two-level abstract system of "peripheral code + measurement point code," with the syntax #peripheral code@measurement point code@attribute#. The attribute field includes a value type representing the real-time value of the measurement point and an alarm type representing the alarm status. The expression body supports nested combinations of arithmetic, relational, and logical operators, forming a domain-specific language with industrial expression capabilities. Each condition sub-item is also configured with a condition duration parameter. This parameter introduces a time-dimensional anti-jitter mechanism in the rule judgment, ensuring that the measurement point value continuously satisfies the logical relationship defined in the expression and remains for the duration set by the parameter before the condition sub-item is deemed valid. This effectively filters out false triggers caused by electromagnetic interference or instantaneous sensor fluctuations in the industrial environment.The result array contains at least one action definition. Each action definition uses a target measurement point assignment expression with the syntax #peripheral code@measurement point code#:target value, and is associated with an output duration parameter to control the duration of action execution. The convergence interval, as a global parameter at the rule level, starts a countdown after a rule is triggered. During this period, even if the triggering condition is met again, the system will block the rule from being triggered again, thereby preventing the actuator from frequently starting and stopping due to fluctuations in operating conditions, reducing mechanical wear and energy waste. The linkage engine module, as the core execution unit of the system, uses a multi-threaded collaborative mechanism to realize the real-time parsing, judgment, and scheduling of linkage rules. When the module starts, the configuration parsing unit reads the JSON format configuration file generated by the rule configuration module and builds a rule linked list data structure in memory. This linked list stores all active rules and their associated conditional items, action definitions, and time parameters in priority order. The data acquisition unit uses an independent thread to loop through the measurement point data interface provided by the interface adapter module, refreshes the real-time values ​​of each measurement point to the shared memory data area, and uses a version number mechanism to achieve read-write isolation for concurrent data access. The rule judgment unit, acting as the engine's main computing thread, polls the rule linked list at fixed time slices and executes the following judgment process for each rule: First, it extracts the formulaic expressions of each sub-item in the condition array, replaces the encoded references in the expressions with real-time measurement point values ​​in the shared memory data area, forming a logical expression that can be parsed and executed by the script engine; then, it combines and judges the validity of all condition sub-items according to the linkage method type. If the linkage method is logical "AND", all condition sub-items are required to remain valid within their respective condition duration parameters; if the linkage method is logical "OR", only a single condition sub-item needs to meet the duration requirement; after confirming the validity of the condition combination, the system queries the timestamp of the last trigger of the rule. Only when the difference between the current time and the last trigger time exceeds the convergence time interval can the trigger execution stage be entered. After the rule is triggered, the action scheduling unit traverses the action definitions in the result array, parses the target measurement point assignment expression into specific control instructions, and sends them to the corresponding execution device through the interface adaptation module; simultaneously, the scheduling unit starts the output duration timer, automatically sending a reset instruction to the target measurement point after the preset duration is reached, realizing continuous control and automatic cancellation of the action. The linkage engine module, through the closed-loop process of configuration parsing, data acquisition, rule judgment, and action scheduling, transforms user-defined logical rules into real-time control behaviors in the industrial field. The interface adaptation module, acting as a communication bridge between the system and physical devices, adopts a pluggable protocol stack architecture to achieve unified management of three mainstream industrial interface protocols: RS485, DI / DO, and Ethernet.For the RS485 interface, the module has a built-in Modbus RTU protocol stack, supporting automatic master / slave mode identification, dynamic device address scanning, data frame CRC check, and retransmission mechanism. It can directly map devices such as temperature and humidity sensors and gas detectors compliant with the Modbus protocol as logical peripherals and measurement points. For the DI / DO interface, the module reads the level state of the digital input signal through the GPIO driver and converts it into a Boolean value for the measurement point. For digital output control, the module drives relays or transistors to output high and low level signals according to the switching commands issued by the action scheduling unit, realizing the start and stop control of external actuators. For the Ethernet interface, the module supports TCP / IP protocol suite Socket communication, allowing connection to smart meters, IP cameras, or network relay devices with network communication capabilities. Data parsing and command encapsulation are achieved through pre-set communication message templates. During the initialization phase, the interface adaptation module registers the managed interface instance information with the configuration management module. During the runtime phase, it provides a unified measurement point data read / write interface to the upper layer, shielding the underlying protocol differences. This allows the linkage engine module to focus on rule logic calculation and scheduling without needing to concern itself with the physical connection details of the devices.

[0039] Furthermore, the linkage engine module includes a configuration parsing unit, a data acquisition unit, a rule judgment unit, and an action scheduling unit. The configuration parsing unit constructs a rule linked list structure in memory, the rule judgment unit replaces the encoded references in the formulaic expression with real-time values ​​to form a computable logical expression, and the action scheduling unit generates control instructions and starts a timer to manage the output duration.

[0040] In this embodiment, the configuration parsing unit undertakes the in-memory reconstruction task of the linkage rules during the system startup phase. After receiving the JSON-formatted configuration file from the rule configuration module, this unit executes a multi-level structured parsing process. First, it performs syntax validity checks, verifying the integrity of the JSON file format and the existence of required fields. Then, it extracts the total number of rules from the top-level configuration object, allocates contiguous storage space in the memory heap based on this number, and constructs the head node of a linear linked list. For each independent linkage rule, the unit dynamically creates a rule node instance and inserts the node at the tail of the linked list, forming a rule linked list structure arranged in configuration order. Each rule node contains metadata fields such as rule identifier, rule name, linkage method type, convergence time interval, and last trigger timestamp, and attaches two auxiliary data structures: a condition sub-linked list and an action definition sub-linked list. The condition sub-linked list consists of multiple condition nodes connected in series. Each condition node stores a formulaic expression string, a condition duration parameter value, a condition activation flag, and a duration timer handle. The action definition sub-linked list consists of multiple action nodes. Each action node stores a target measurement point assignment expression, an output duration parameter value, an action execution status flag, and an output duration timer handle. After all parsing is completed, the configuration parsing unit registers the first address of the rule chain list to the global variable area of ​​the linkage engine module for subsequent units to share and access, and triggers the data acquisition unit and rule judgment unit to enter the ready state.

[0041] The data acquisition unit, as an independent thread running the linkage engine, is responsible for maintaining the freshness of real-time data from measurement points. This unit executes in a loop with a fixed time slice. In each loop, it iterates through the measurement point enumeration interface provided by the interface adaptation module to obtain a list of identifiers for all currently registered measurement points. For each measurement point identifier, the unit calls the data reading service of the interface adaptation module to obtain the real-time raw value of the measurement point. Upon successful acquisition, the unit writes the measurement point identifier as the key and the real-time raw value as the data item to the shared memory data area. This data area is implemented using a hash table structure, supporting fast retrieval and updating of measurement point data. The unit synchronously adds a timestamp to each measurement point data item to record the data refresh time, providing a timeliness reference for the rule judgment unit. During data writing, the unit uses a read-write lock mechanism to implement concurrency control, ensuring that the rule judgment unit is not blocked by write operations or has its data integrity compromised when reading data. When a state transition is detected in the measurement point data value compared to the last sampling, the data acquisition unit sends a lightweight notification signal to the rule judgment unit, triggering the immediate evaluation process of the rule chain to reduce linkage response latency. The rule judgment unit, as the core decision-making thread of the linkage engine, operates based on a dual-mode of event-driven and timed scanning. When no external trigger event occurs, the unit traverses the rule list at a preset cycle, executing a complete condition evaluation sequence for each rule node. At the start of the evaluation, the unit extracts the linkage mode type field of the rule node. If the type is logical "AND", the initial condition satisfaction counter is zero; if the type is logical "OR", the initial condition satisfaction flag is false. Subsequently, the unit traverses the condition sub-item sub-lists of the rule node, performing the following operations for each condition node: First, the formulaic expression string stored in the condition node is loaded into the expression parser. The parser scans the string content, identifies and extracts all coded reference fragments, i.e., the parts matching the syntax pattern #peripheral code@measurement point code@attribute#. For each coded reference fragment, the parser extracts the peripheral code and measurement point code, using this code combination as the query key to access the shared memory data area and retrieve the corresponding real-time measurement point value. If the attribute field is of type value, the measurement point value is directly retrieved; if it is of type alarm, the alarm status bit of the measurement point is retrieved. The retrieved real-time values ​​replace the original encoded reference fragments, and the process is iterated until the expression no longer contains any encoded references, ultimately forming a computable logical expression composed of constants and operators. The parser submits this expression to the script engine for Boolean operations to obtain the instantaneous satisfaction status of the conditional sub-items. If the instantaneous status is true, the unit starts the duration timer for the conditional node; the conditional sub-item is considered invalid until the accumulated value of the timer reaches the threshold set by the conditional duration parameter; once the accumulated value of the timer reaches the threshold, the conditional sub-item is considered to be continuously satisfied. Depending on the linkage mode type, the unit increments the condition satisfaction counter or sets the condition satisfaction flag.After evaluating all conditional items, the unit performs rule-level validity checks: for logical "AND" operations, the condition satisfaction counter must equal the total number of conditional items; for logical "OR" operations, the condition satisfaction flag must be true. If the rule-level validity is valid, the unit further reads the last trigger timestamp of the rule node, calculates the time difference between the current time and that timestamp, and only sends a rule trigger command to the action scheduling unit when the time difference exceeds the convergence interval parameter setting, updating the last trigger timestamp to the current time and completing this judgment cycle. Upon receiving the trigger command from the rule judgment unit, the action scheduling unit immediately starts the action execution sequence. The unit first locks the action definition sub-linked list of the rule node and traverses each action node in the list. For a single action node, the unit extracts its stored target measurement point assignment expression, with the expression format #peripheral code@measurement point code#:target value. The unit parses this expression, separating the peripheral code, measurement point code, and target value into three parts, constructing a control instruction structure, where the instruction type field is set to write operation, the address field is filled with the measurement point code, and the data field is filled with the target value. The unit calls the data writing service of the interface adaptation module to send control commands to the corresponding physical devices, thus initiating the action. Subsequently, the unit checks the output duration parameter of the action node. If the parameter value is zero, the action node is marked as continuous output mode, the timer is not started, and it waits for subsequent reverse rules to actively cancel the output. If the parameter value is non-zero, the unit starts the output duration timer and binds the timer handle to the action node. The timer runs in countdown mode. When the countdown reaches zero, a callback function is automatically triggered. The callback function generates a measurement point reset command, restoring the target measurement point value to its pre-trigger state, thereby achieving automatic cancellation of the action. The action scheduling unit supports parallel scheduling of multiple action nodes, maintaining an independent timer instance for each node to ensure that the control of each actuator is independent and does not interfere with each other. During action execution, the unit feeds back the action execution status to the rule judgment unit. Based on this status, the rule judgment unit skips the condition evaluation of triggered rules in subsequent loops until the convergence time interval expires, forming a complete linkage control closed loop. Through the close collaboration of the above four functional units, the linkage engine module realizes the fully automated processing from static rule configuration to dynamic control execution. The responsibilities of each unit are clearly defined, and the data interaction mechanism is clear, ensuring that the system has high real-time performance, high reliability, and high flexibility in linkage control in industrial monitoring scenarios.

[0042] Furthermore, the condition duration parameter is used to eliminate instantaneous jump interference from sensors in industrial monitoring scenarios, the output duration parameter is used to control the action holding time of the actuator, and the convergence interval is used to prevent the actuator from frequently starting and stopping due to repeated fulfillment of conditions. The three work together to form a multi-dimensional time control mechanism to improve system stability. In this embodiment, the condition duration parameter plays a core role in sensor signal anti-jitter filtering in industrial monitoring scenarios. The industrial environment is complex, with various electromagnetic interference sources such as motor start-stop, inverter operation, and high-voltage switch switching. These interferences are easily coupled to the sensor signal transmission link, causing instantaneous jumps in the measured values ​​or false reversals of alarm states. If the linkage control system uses instantaneous triggering logic, it will cause erroneous execution of the linkage rules, resulting in unnecessary actions of the actuator and even interruption of the production process. The condition duration parameter fundamentally solves this problem by introducing a time accumulation dimension into the signal validity judgment. When the rule judgment unit detects that the formulaic expression of a certain condition sub-item is instantaneously satisfied, it does not immediately determine that the condition is valid, but instead starts the duration timer dedicated to that condition sub-item. During the timer's operation, the rule judgment unit continuously monitors the expression's satisfaction status. If the expression becomes unsatisfied due to interference before the timer's accumulated time reaches the parameter-set threshold, the timer is automatically reset. Only when the expression remains satisfied within the complete time window can the timer successfully accumulate to the threshold, at which point the rule judgment unit marks the condition as valid. This mechanism transforms signal validity judgment from discrete point sampling to continuous time domain observation, effectively identifying and filtering out instantaneous interference pulses at the millisecond to second level in industrial settings. This ensures that the linkage triggering conditions are based on stable and reliable physical quantity changes from the sensors, significantly improving the system's immunity to false signals. The output duration parameter is used for fine-grained control of the actuator's action duration. Actuators in industrial monitoring scenarios have diverse action characteristics and process requirements. Some equipment (such as audible and visual alarms and emergency lighting) needs to run continuously until manual intervention, while others (such as exhaust fans and sprinkler systems) only need to run for a fixed duration to achieve the process objective. The output duration parameter provides configurability in the time dimension for the execution of the linkage rule results. When the action scheduling unit executes the target measurement point assignment operation of an action node according to the rule-triggered instruction, it first reads the output duration parameter value configured in the action node. If the parameter value is set to zero, the action scheduling unit marks the action as a continuous output mode. The system does not start any timer for this action, and the actuator will maintain the current action state until another linkage rule triggers a reverse action to restore the measurement point value to the initial state. This mode is suitable for control scenarios that require long-term maintenance and need to be reset by external events. If the output duration parameter is set to a non-zero value, the action scheduling unit starts the output duration timer bound to the action node while sending the control instruction.The timer employs a countdown mechanism. When the countdown reaches zero, a callback mechanism is automatically triggered. The callback function generates a measurement point reset command and sends it to the same actuator, restoring the equipment to its pre-trigger state and achieving automatic cancellation of the action. This mode is suitable for timed control scenarios, avoiding resource waste or over-response issues caused by prolonged actuator occupation after rule triggering. Flexible configuration of the output duration parameter allows the system to adapt to the process characteristics of different actuators, achieving precise action duration control.

[0043] The convergence interval, as a global debouncing parameter at the rule level, plays a crucial role in preventing frequent start-stop operations of actuators due to fluctuations in operating conditions. In industrial monitoring scenarios, some controlled physical quantities (such as temperature, humidity, and pressure) often exhibit periodic or random fluctuations around control thresholds. When threshold comparison-based triggering conditions are used, the slight oscillations of physical quantities around the threshold can lead to repeated triggering of linkage rules, causing frequent actions of actuators (such as compressors, heaters, and valves). This frequent start-stop not only exacerbates equipment wear and shortens its service life but can also cause process parameter oscillations, affecting production stability. The convergence interval effectively blocks such high-frequency triggering by introducing a forced silence period after rule triggering. When a linkage rule is successfully triggered, the rule judgment unit immediately records the triggering time of the rule and activates the convergence timer. During the timer's operation, the rule judgment unit skips the evaluation branch of the rule when traversing the rule chain, and the system will not re-trigger its action execution even if its triggering conditions are continuously met or met again. Only when the cumulative time of the convergence timer reaches the parameter-set threshold will the rule be reintroduced into the normal evaluation process. This mechanism ensures that the actuator has sufficient response and stabilization time after the rule is triggered, avoiding repeated triggering due to minor fluctuations in the input signal. It fundamentally solves the long-standing problem of boundary oscillations in industrial control and plays a crucial role in protecting the actuator and maintaining stable process operation. The multi-dimensional time-coordinated control mechanism, through the organic combination of the three time parameters mentioned above, constructs a complete time-dimensional control system from input signal filtering and output action timing to trigger frequency suppression. These three parameters work together to form a closed-loop control logic. In the linkage control process, the condition duration parameter acts on the input side, pre-filtering the sensor signal to ensure the validity of the trigger condition; the output duration parameter acts on the output side, post-timing the actuator action to ensure the accuracy of the action execution; and the convergence time interval acts on the rule trigger frequency, periodically constraining the entire linkage process to ensure the stability of the system response. These three parameters are independent yet interconnected, jointly improving the stability and reliability of the linkage control system in industrial monitoring scenarios. The design of this mechanism fully considers the complex electromagnetic environment of the industrial site, the physical characteristics of the actuator, and the stability requirements of the process. It is fundamentally different from the simple delay control in general IoT scenarios, and reflects the invention’s profound understanding of the special needs of the industrial monitoring field and its targeted solutions.

[0044] Furthermore, the interface adapter module includes an RS485 interface management unit, a DI / DO interface management unit, and an Ethernet interface management unit. The RS485 interface management unit supports dynamic access of Modbus RTU protocol devices, and the DI / DO interface management unit is used to map digital input and output signals to measurement point status.

[0045] In this embodiment, the interface adaptation module serves as the central hub for protocol conversion and data mapping between the system and physical device layers. It employs a plug-in architecture, encapsulating the communication differences between various physical interfaces into a unified measurement point access interface. The module integrates three independent interface management units, corresponding to the three most commonly used communication methods in industrial monitoring scenarios. By dynamically loading drivers and configuration parameters, it achieves plug-and-play functionality and unified management of heterogeneous devices. The RS485 interface management unit is responsible for the access and communication management of serial bus devices. Its core is the implementation of the Modbus RTU protocol stack and a dynamic device discovery mechanism. During unit initialization, based on the interface parameters issued by the configuration management module, it sets the serial port baud rate, data bits, stop bits, and parity, activating the RS485 transceiver control circuit. The unit has a built-in Modbus RTU master protocol engine, supporting standard function code sets, including reading holding registers, reading input registers, writing a single register, and writing multiple registers. For dynamic access, the unit uses a mechanism combining polling detection and active registration. For slave devices conforming to the Modbus protocol, the unit sends device identification messages one by one according to the device address range preset in the configuration file. If a valid response is received, the unit registers the device at that address as online, creates a logical peripheral instance for it, and assigns a peripheral code. For intelligent devices that support active reporting, the unit listens to the bus data frames, parses the device address field in the frame header, and automatically completes device registration. The unit periodically sends data query messages to registered devices, converts the returned register values ​​into standardized measurement point data according to the mapping relationship between register addresses and measurement point codes defined in the configuration file, and writes them to the shared memory data area. During the data conversion process, the unit automatically completes byte order conversion and scaling calculation according to the data type definition of the measurement points (such as 16-bit integer, 32-bit floating-point), ensuring that the measurement point values ​​obtained by the upper-layer modules have uniform dimensions and precision. For write operations, the unit receives control commands issued by the linkage engine module, converts the measurement point codes in the commands into Modbus register addresses, assembles the target values ​​into write commands conforming to the RTU frame format, sends them to the corresponding device, and waits for response confirmation to ensure reliable delivery of control commands. The DI / DO interface management unit is responsible for acquiring and driving digital input / output signals, realizing a direct mapping between physical level signals and logic measurement point states. On the digital input side, the unit periodically reads the pin level states of the DI interface through the GPIO driver. Based on the electrical characteristics of the industrial environment, the unit has a built-in level debouncing filter mechanism that performs a state consistency judgment on the read raw level signals within a time window. Only when the pin level remains in a continuously stable state is it considered valid, thereby eliminating erroneous inputs caused by mechanical switch contact bounce or electromagnetic interference.The confirmed voltage level is mapped to a Boolean value attribute of the measurement point. A high voltage level corresponds to a true measurement point status, and a low voltage level corresponds to a false status. This measurement point status is updated in the shared memory data area for use by the rule judgment unit. On the digital output side, the unit receives action commands from the linkage engine module and parses the measurement point code and target value in the command. When the target value is true, the unit drives the DO interface to output a high-level signal, triggering the external relay to close or the transistor to turn on; when the target value is false, the unit outputs a low-level signal, resetting the external actuator. The unit supports multiple output mode configurations for the DO interface, including level holding mode and pulse output mode. In level holding mode, the unit maintains the output level continuously until a reverse command is received; in pulse output mode, the unit automatically generates a pulse signal of a specified width according to the output duration parameter, suitable for scenarios requiring short-term triggering. The unit also configures an output status readback mechanism for each DO interface, detecting the actual output level through an independent input loop to form a closed-loop monitoring system, ensuring accurate execution of control actions. The Ethernet interface management unit is responsible for the access of network devices and IP-based communication management, supporting multiple communication modes of the TCP / IP protocol suite. During the initialization phase, the unit allocates IP addresses, subnet masks, and gateway parameters according to the configuration file and activates the network interface. For devices supporting standard industrial protocols (such as Modbus TCP and SNMP), the unit has a built-in corresponding protocol client that establishes a session with the device via a Socket connection. The unit maintains a device connection status table, recording information such as the IP address, port number, session ID, and last communication timestamp for each device, and supports disconnection reconnection and session persistence. In data acquisition mode, the unit periodically sends protocol data request messages to the device, parses the returned Protocol Data Units (PDUs) into measurement point data, and completes the conversion from physical quantities to measurement point values. For smart devices supporting HTTP / RESTful interfaces, the unit constructs a JSON-formatted GET request and extracts measurement point data from the response message returned by the device. In control output mode, the unit encapsulates the control commands issued by the linkage engine module into protocol write requests or POST requests, sends them to the device, and verifies the response status code to confirm successful command execution. The unit also supports a UDP multicast-based device discovery mechanism, broadcasting device query messages within the local area network to automatically discover network devices that support this mechanism and complete registration, simplifying the device access process. The Ethernet interface management unit unifies the data interaction of different network protocols into test point read and write operations through the protocol abstraction layer, enabling upper-layer modules to access serial devices, digital I / O devices and network devices in a consistent manner, and truly realize the unified management of heterogeneous devices.Through the collaborative work of the three interface management units mentioned above, the interface adaptation module unifies and abstracts the three heterogeneous communication methods—Modbus RTU communication of RS485 bus, level signal interaction of DI / DO interface, and IP communication of Ethernet link—into a standard measurement point data access interface. The linkage engine module does not need to care about the underlying communication details, thereby significantly reducing system complexity, improving expansion flexibility, and meeting the actual needs of diverse equipment types and mixed protocols in industrial monitoring scenarios.

[0046] Furthermore, the system is applied to scenarios such as fire alarm linkage, temperature and humidity over-limit alarm, and equipment start-up and shutdown control in computer room environment monitoring, substation automation, and intelligent building management, enabling users to configure it independently without modifying the source code.

[0047] Based on the same concept, a multi-measurement point device linkage control method for industrial monitoring scenarios includes the following steps: Step S1: Abstracting physical devices into logical peripherals through the configuration management module and assigning unique peripheral codes, assigning measurement point codes to the measurement points of each peripheral, and establishing a two-level abstract configuration between devices and measurement points; This step specifically involves: a detailed description of the two-level abstract configuration establishment process:

[0048] The configuration management module, during system initialization, first executes an interface resource detection process. The module reads the system hardware description information to identify the type and number of physical interfaces equipped on the current monitoring host, including RS485 serial interfaces, DI / DO digital interfaces, and Ethernet network interfaces. For each type of interface, the module loads the corresponding low-level driver, activates the interface circuit, and enters a communicable state. For RS485 interfaces, the module calls the serial port enumeration service to obtain the interface identifier; for DI / DO interfaces, the module scans available input / output pin groups through the GPIO controller; for Ethernet interfaces, the module binds the network protocol stack and monitors the local link status. After interface resource enumeration is complete, the module constructs an interface resource pool, assigns an interface code to each physical interface, and records metadata such as interface type, communication parameters, and hardware address, forming the foundation for interface-level configuration.

[0049] Physical device discovery and logical peripheral abstraction

[0050] After completing the interface resource pool construction, the configuration management module executes the physical device discovery process. On the RS485 bus side, the module sequentially selects target RS485 interfaces according to the interface code, and sends standard protocol identification messages to potential slave devices one by one according to the address scanning range preset in the configuration file. If the interface receives a valid device response frame, it parses the device type identifier and firmware version information carried in the frame to confirm that there is a communicable physical device at that address. The module registers the physical device as a candidate device and records its original attributes such as interface affiliation, bus address, and device type. On the DI / DO side, the module identifies connected switch devices by reading the initial level state of the digital input pins and combining it with the external device wiring diagram; it confirms the validity of the output channel by sending test pulses to the digital output pins and detecting the loop response. On the Ethernet side, the module probes online devices in the local area network through ARP scanning or multicast discovery protocols and identifies network nodes that support standard industrial communication protocols. After physical device discovery is completed, the module abstracts each candidate device into a logical peripheral object and assigns a globally unique peripheral code to each logical peripheral. Uniqueness is guaranteed by an encoding generation algorithm that integrates multi-dimensional information such as interface code, device address, and device type classification code. This ensures that even if the physical location of the device changes or it is restarted, its peripheral code remains unchanged throughout the system's lifecycle, thereby achieving stability and traceability of device identification.

[0051] Measurement point identification and construction of a two-level coding system

[0052] After the logical peripherals are abstracted, the configuration management module enters the measurement point identification stage. Based on the device type of the logical peripheral, the module loads a predefined measurement point template library. This library stores a list of standard measurement points for various industrial devices, including attributes such as measurement point name, function description, data type, access permissions, and measurement range. For temperature and humidity sensor peripherals, the library includes temperature and humidity measurement points; for smoke detector peripherals, it includes smoke concentration and alarm status point measurement points; and for DI / DO actuators, it includes switch status and action feedback measurement points. The module binds the measurement point templates to the logical peripherals, generating a list of measurement point instances. For each measurement point instance, the module assigns a unique measurement point code. These codes, along with the peripheral codes, constitute a two-level abstract configuration system. In this system, the peripheral code locates a specific device, and the measurement point code locates a specific data item within the device, forming a hierarchical addressing capability between peripherals and measurement points. The module stores the secondary coding configuration information in a structured manner, forming a configuration tree. The root of the tree is the interface coding, the first-level child nodes are the peripheral coding, the second-level child nodes are the measurement point coding, and each leaf node carries the complete metadata of the measurement point.

[0053] Configuration information persistence and dynamic loading mechanism

[0054] After the secondary abstract configuration is constructed, the configuration management module performs configuration persistence operations. The module serializes the configuration tree in memory into a JSON-formatted configuration file, which contains three main parts: interface configuration, peripheral configuration, and measurement point configuration. The interface configuration describes the communication parameters and interface codes of each physical interface; the peripheral configuration describes the peripheral codes, interfaces, and device types of logical peripherals; and the measurement point configuration describes the measurement point codes, peripherals, data types, and access permissions of each measurement point. The configuration file is stored in non-volatile storage to ensure that the configuration is not lost after a system restart. When the monitoring host starts, the configuration management module automatically loads the configuration file, performs deserialization, reconstructs the configuration tree in memory, and initializes the interface adaptation module and the linkage engine module in sequence to complete a rapid system recovery. When adding or modifying device configurations on-site, users adjust the configuration information through the configuration tools on the management host. After receiving the update command, the configuration management module dynamically modifies the in-memory configuration tree and immediately synchronizes the incremental changes to the persistent configuration file, achieving online configuration updates without restarting the system.

[0055] Configuration validity verification and conflict resolution

[0056] During the establishment of the secondary abstract configuration, the configuration management module implements a strict configuration validity verification mechanism. The module checks the uniqueness of peripheral codes and measurement point codes to prevent duplicate allocation; it checks the consistency between the measurement point data type and the actual capabilities of the device to prevent configuration from exceeding the range; and it checks interface resource usage to prevent device address conflicts on the same interface. If the verification finds a configuration conflict or error, the module returns detailed error codes and suggested correction information to the user and refuses to write illegal configurations to the configuration file. For multi-user concurrent configuration scenarios, the module employs a configuration locking mechanism to ensure that only one configuration session is allowed to perform write operations at any given time, preventing configuration information from being overwritten or corrupted. Through these verification and protection mechanisms, the integrity and reliability of the secondary abstract configuration are guaranteed, laying a solid foundation for upper-layer linkage control logic.

[0057] Step S2: Receive the linkage rules defined by the user in JSON format through the rule configuration module. The linkage rules include a trigger condition consisting of at least one condition sub-item, the execution result corresponding to the trigger condition, and a convergence time interval to prevent the rule from being triggered frequently. Each condition sub-item includes a formulaic expression based on peripheral encoding and measurement point encoding: #peripheral encoding@measurement point encoding@attribute#, and a condition duration parameter for filtering transient interference.

[0058] This step specifically involves: a detailed explanation of the structured configuration of linkage rules and the definition of multi-dimensional time parameters.

[0059] JSON format receiving and verification mechanism of the rule configuration module

[0060] The rule configuration module provides a standardized JSON schema definition, which forms the syntactic framework for configuring linkage rules. Users construct linkage logic through a graphical configuration tool on the management host in a visually interactive manner. The configuration tool automatically serializes the graphical causal chain into a JSON text structure conforming to this schema. Upon receiving the JSON text, the module first initiates a format compliance verification process. The validator checks the integrity of the JSON object's key names, hierarchical nesting relationships, and data type matching layer by layer to ensure that the submitted rule file is free of syntax errors or structural omissions. If the verification fails, the module returns detailed error location information, instructing the user to correct the configuration. If the verification passes, the module further performs semantic rationality verification, checking whether the peripheral encoding and test point encoding referenced by the rule exist in the secondary abstract configuration system established in step S1, and verifying whether the syntactic structure of the formulaic expression conforms to the predetermined paradigm to prevent referencing non-existent devices or constructing illegal expressions. After passing both verifications, the JSON rule file is marked as a valid configuration, loaded into the rule configuration module's memory cache, and a rule version identifier is generated, providing a basis for subsequent incremental loading and hot updates of the linkage engine module.

[0061] Construction of the array of conditional sub-items for triggering conditions

[0062] The trigger condition is the logical core of the linkage rule, composed of at least one condition sub-item combined through logical operators. In the JSON structure, the trigger condition is defined as an array of condition sub-items. Each condition sub-item is independently encapsulated as an object, containing two required fields: a formulaic expression and a condition duration parameter. The formulaic expression adopts an industry-specific syntax structure of #peripheral code@measurement point code@attribute#, which embeds the two-level abstract coding system established in step S1 within the expression, decoupling the rule definition from the specific device. The peripheral code locates the target device, the measurement point code locates the data item within the device, the attribute field distinguishes between numerical and status signals, and the operator part supports comparison relationships and arithmetic operations commonly used in industrial monitoring. The condition duration parameter, in units of time, defines the discrimination window for signal stability. The order of multiple condition sub-items in the array does not affect the logical judgment result, but it does affect the traversal priority of the rule judgment unit. The rule configuration module allows users to independently set the duration parameter for each condition sub-item, enabling fine-grained customization of anti-jitter strategies. For example, a longer duration can be set for easily interfered analog signals, while a shorter duration can be set for digital switching signals, reflecting the differentiated anti-interference requirements in industrial scenarios.

[0063] Logical combination method and linkage type configuration

[0064] The linkage rules support two combination methods at the trigger condition level: logical "AND" and logical "OR". These methods are defined in the JSON structure through a linkage method type field. When configured as logical "AND", the rule judgment unit requires all condition items to be continuously satisfied within their respective duration windows for the entire trigger condition to be activated. This mode is suitable for multi-factor collaborative judgment scenarios, such as fire linkage requiring temperature exceeding limits and smoke alarms to be met simultaneously to ensure the accuracy of fire alarm judgment. When configured as logical "OR", the rule judgment unit only needs any one condition item to meet the duration requirement to activate the trigger condition. This mode is suitable for multi-source redundant judgment scenarios, such as in environmental monitoring where exceeding the gas concentration standard in any area can trigger the ventilation system. The rule configuration module provides a visual selection component for linkage types in a graphical interface. Users can set the combination method through drop-down menus or toggle buttons. The configuration tool automatically maps this setting to a JSON type field, reducing the difficulty of user configuration. This design encapsulates complex logical combination semantics into concise configuration items, enabling industrial users without programming backgrounds to intuitively define multi-condition linkage logic, significantly improving the system's usability and configurability.

[0065] Action definition array configuration of execution results

[0066] The execution result is a set of control behaviors executed by the system after the triggering conditions are met, defined as an action definition array in a JSON structure. Each action definition object contains a target measurement point assignment expression and an output duration parameter. The target measurement point assignment expression is also based on a two-level coding system, with the syntax structure #peripheral code@measurement point code#:target value. The part before the colon identifies the controlled device and measurement point, and the part after the colon defines the expected value or state. This syntax design maintains inherent consistency with the expression syntax of the conditional items, forming a unified coding standard on the input and output sides of the rule, which is convenient for users to understand and maintain. The output duration parameter assigns a time attribute to the executed action, allowing users to define the duration of the action and realize timed control functions. The action definition array supports batch configuration of multiple actions. When a rule is triggered, the action scheduling unit will execute all actions in the array sequentially. By reasonably arranging the order and duration of actions, complex linkage timing logic can be realized. For example, the auxiliary fan can be turned on first, and the main exhaust fan can be turned on after a delay of several seconds, forming a stepped ventilation strategy and avoiding power surges.

[0067] Global anti-jitter configuration for convergence time interval

[0068] The convergence interval, a global parameter at the rule level, is configured independently outside the action definition array in the JSON structure, affecting the trigger frequency control of the entire linkage rule. This parameter is introduced because industrial actuators are sensitive to frequent start-stop cycles. When physical quantities fluctuate around the control threshold, without a convergence mechanism, the linkage rule will be repeatedly triggered, causing the mechanical components of actuators (such as motors, valves, and alarms) to endure high-frequency stress impacts, accelerating wear and aging. The convergence interval forces the rule to enter a silent state after triggering, during which the rule judgment unit skips the evaluation of the rule, ensuring that the actuator has sufficient time to complete the mechanical action and stabilize the operating condition. The rule configuration module allows users to flexibly set the convergence interval according to the physical response characteristics of the actuator and process requirements. For rapidly responding solenoid valves, a shorter interval can be set; for fans or compressors with longer start-up processes, a longer interval can be set. This parameter's configuration rights are given to the user, enabling the system to adapt to the mechanical characteristics of different equipment, reflecting the concept of refined control in industrial monitoring scenarios.

[0069] Configurable integration of industrial scenario-specific syntax and multidimensional time control

[0070] The core innovation of this step lies in deeply integrating equipment identification standards, signal anti-jitter requirements, and actuator protection mechanisms in the industrial monitoring field into a JSON structured configuration, forming a domain-specific rule description language. Compared with general rule engines, the formulaic expression syntax of this invention forcibly embeds a two-level coding system, strongly associating rule configuration with device abstraction configuration, ensuring the device independence and portability of rule definitions. More importantly, this invention is the first to simultaneously front-load three time control parameters—conditional duration parameter, output duration parameter, and convergence interval—into the rule configuration layer, allowing users to define complete time-dimensional control strategies in the configuration file without programming, achieving full-process time control from input anti-jitter and output timing to trigger frequency suppression. This design transforms complex time logic that originally required hard-coding into configurable parameters, greatly reducing the adjustment threshold of linkage control logic, enabling industrial users to quickly optimize control strategies according to changes in on-site conditions. The response speed is shortened from the traditional code modification-compilation-deployment cycle to the instant delivery of configuration files, significantly improving the system's on-site adaptability and intelligence level.

[0071] Step S3: The linkage engine module loads and parses the linkage rules, and collects real-time data from each measuring point in a loop;

[0072] This step specifically involves: a detailed explanation of the incremental loading and real-time data closed-loop acquisition mechanism of the linkage engine module.

[0073] Lazy loading and incremental update mechanism of linkage rules

[0074] When the linkage engine module starts, it does not immediately perform full rule parsing, but first enters the configuration listening state. The module registers a configuration change callback interface with the rule configuration module. After the JSON format linkage rule file passes the validity check and is written to the rule configuration cache, the rule configuration module actively pushes the configuration version change notification and file path to the linkage engine module. After receiving the notification, the configuration parsing unit of the linkage engine module uses an incremental comparison strategy to load the rule content, rather than a full reload. The unit reads the rule linked list structure in the current memory, generates a snapshot set of existing rule identifiers, and then parses the new version JSON file, extracts the rule list in the file, and constructs a new rule identifier set. Through set difference operations, the unit identifies rules to be added, rules to be deleted, and rules to be modified. For rules to be added, the unit dynamically allocates rule node memory in the memory heap area, executes the complete node initialization process, including rule metadata filling, condition sub-item sub-linked list construction, action definition sub-linked list construction, and inserts the new node at the tail of the rule linked list. For rules to be deleted, the unit clears the activation flag of the corresponding rule node, but the physical memory of that node is not immediately released. Instead, it is marked as "invalid" and reclaimed in a subsequent garbage collection cycle to avoid performance fluctuations caused by frequent memory allocation and release during runtime. For rules to be modified, the unit locates the corresponding rule node and updates only the changed fields, such as adjusting condition duration parameters or adding / deleting action definitions. Unchanged parts remain unchanged. This incremental update mechanism enables the linkage engine module to achieve online hot updates of linkage rules without stopping the system. When industrial site requirements change, new rules take effect in real time without restarting the monitoring host, significantly improving system availability and response efficiency.

[0075] Runtime optimization organization of rule-based linked list structures

[0076] The rule list built in memory by the linkage engine module is not a simple linear structure, but an optimized organization method combining hierarchical indexing and priority sorting. After the configuration parsing unit completes rule loading, it reorganizes the rule list. The unit extracts the convergence time interval parameter of all rules and divides the rules into three logical groups according to the parameter value: fast response rule group, standard response rule group, and delayed response rule group. The fast response rule group contains rules with short convergence time intervals, which are usually associated with emergency alarms or safety linkages and require high-frequency evaluation; the standard response rule group contains rules with medium convergence time intervals, corresponding to routine process control; and the delayed response rule group contains rules with long convergence time intervals, corresponding to non-critical reminders or statistical linkages. The configuration parsing unit inserts a group sentinel node at the head of the rule list, and each sentinel node marks the group type to which its subsequent rules belong. When performing traversal evaluation, the rule judgment unit dynamically adjusts the evaluation frequency of each group according to the current system load: when the system is idle, all three groups are evaluated according to the standard cycle; when the system is under high load, the evaluation frequency of the delayed response rule group is reduced to prioritize the real-time performance of the fast response rule group. Furthermore, the rule list internally employs a doubly linked list structure instead of a singly linked list, enabling the rule judgment unit to support bidirectional forward and reverse retrieval during traversal. This facilitates rapid lookup of rule dependencies and detection of circular references. This runtime optimization improves the execution efficiency and resource utilization of the linkage engine module in scenarios with large-scale rule sets.

[0077] Lock-free concurrent access architecture for shared data areas

[0078] The data acquisition unit and rule judgment unit access real-time measurement point data through a shared data area. To avoid performance bottlenecks and deadlock risks associated with traditional locking mechanisms, the linkage engine module adopts a lock-free concurrent access architecture for the shared data area. The data area consists of multiple circular buffers, each corresponding to a measurement point dataset acquired by a physical interface. The write pointer of the circular buffer is exclusively maintained by the data acquisition unit, and the read pointer is exclusively maintained by the rule judgment unit. Synchronization between the two is achieved through memory barriers and atomic operation instructions. After each acquisition cycle, the data acquisition unit writes new data to the current write pointer position in the circular buffer and then atomically moves the write pointer to the next position without waiting for the rule judgment unit to release the lock. When evaluating rules, the rule judgment unit reads the measurement point data at the read pointer position and then atomically moves the read pointer, achieving lock-free data consumption. This design ensures that the two high-frequency operations, data acquisition and rule judgment, can be executed in parallel without interference, significantly reducing system response latency. To further improve data consistency, each measurement point data item in the shared data area includes two metadata fields: a data version number and a data timestamp. When the data acquisition unit writes new data, it synchronously increments the version number. When the rule judgment unit reads data, it compares the version number for changes. If the version number remains unchanged, the cached value is used directly to avoid duplicate calculations; if the version number changes, the data is reread and the local cache is updated. The data timestamp field records the physical time of the measurement point sampling. The rule judgment unit uses the timestamp to determine the data freshness, filtering out expired data to prevent historical data from being misused for real-time judgment due to network latency or interface blockage. This lock-free concurrent architecture enables the linkage engine module to efficiently handle high-frequency measurement point acquisition interruptions and rule evaluation threads, ensuring the real-time performance of the system in industrial monitoring scenarios.

[0079] Runtime dynamic compilation and caching mechanism for formulaic expressions

[0080] If the rule judgment unit were to replace the encoded references in the formulaic expressions with real-time measurement point values ​​using a character-by-character parsing and replacement method, it would consume significant CPU resources, becoming a performance bottleneck, especially when the number of rules is large and the expressions are complex. The linkage engine module introduces a dynamic expression compilation and caching mechanism to optimize this process. When constructing the rule linked list, the configuration parsing unit performs a pre-compilation operation on the formulaic expression of each conditional item. During pre-compilation, the unit splits the expression string into three basic elements: operators, operands, and encoded reference fragments, constructing an expression syntax tree. The leaf nodes of the syntax tree are encoded reference fragments, the internal nodes are operators, and the root node is the result of the entire expression. The pre-compiled syntax tree is stored in the conditional item nodes as an intermediate representation of the expression. In each evaluation loop of the rule judgment unit, the unit does not need to repeatedly parse the expression string; instead, it directly traverses the pre-stored syntax tree, performing real-time value replacement only on the encoded reference fragments in the leaf nodes. The replaced leaf node values ​​are passed up to the internal nodes, where the operators defined by the nodes are executed, ultimately calculating the Boolean result of the root node. This dynamic compilation mechanism reduces the complexity of expression parsing from runtime O(n) to a single overhead during pre-compilation. To further optimize, the linkage engine module establishes a cache mapping table for frequently accessed encoded reference fragments. When the rule judgment unit accesses a measured point value for the first time, it reads it from the shared data area and writes it to the cache mapping table; subsequent accesses of the same encoding prioritize retrieval from the cache mapping table, avoiding repeated access to the shared data area and improving data reading efficiency. The cache mapping table is actively invalidated by the rule judgment unit after each data acquisition unit completes a new round of data refresh, ensuring that the latest measured point value is reloaded for the next evaluation. This dynamic compilation and caching mechanism enables the linkage engine module to maintain high real-time computing capabilities even when processing a large number of complex rules.

[0081] Sliding window cumulative judgment algorithm for condition duration

[0082] The rule-based judgment unit employs a sliding window cumulative judgment algorithm, rather than a simple timer timeout judgment, when determining whether a condition item is continuously satisfied. Each condition item node maintains a duration state machine, which includes three states: inactive, accumulating, and active. Initially, the state machine is inactive, and the cumulative duration value is reset to zero. When the expression is momentarily satisfied, the state machine transitions to the accumulating state. In each evaluation cycle, the rule-based judgment unit adds the current cycle time slice to the cumulative duration value while monitoring whether the expression remains satisfied. If the expression becomes unsatisfied during accumulation, the state machine immediately reverts to the inactive state, the cumulative value is reset to zero, and it waits for the next momentary satisfaction event. If the expression remains consistently satisfied and the cumulative value reaches the threshold set by the condition duration parameter, the state machine transitions to the active state, the condition item is deemed valid, and this state is locked until the expression becomes unsatisfied, at which point it is reset. This sliding window algorithm allows condition items to be briefly unsatisfied during accumulation without immediate reset, tolerating occasional spike pulse interference in industrial signals, further improving the robustness of condition judgment. The state transition process of the state machine is atomically updated by the rule judgment unit in each evaluation cycle, ensuring the accuracy and consistency of multi-cycle accumulation.

[0083] Cross-rule collaboration and conflict prevention mechanisms for convergence time

[0084] While convergence time intervals apply to individual rules, in industrial monitoring scenarios, multiple rules may affect the same actuator, leading to coordination and conflict issues in convergence time. The linkage engine module implements a cross-rule convergence time coordination management mechanism. After constructing the rule chain, the configuration parsing unit performs rule dependency analysis, identifying all rule sets whose target actions point to the same actuator measurement point, and binding these rules to the same convergence coordination group. During rule evaluation, when any rule in the group is triggered, the unit updates not only the rule's last trigger timestamp but also the group trigger timestamp for the entire convergence coordination group. Other rules in the group must check the group trigger timestamp before evaluation. If the difference between the current time and the group trigger timestamp does not exceed the maximum convergence time interval among all rules, the entire group of rules is masked to prevent alternating triggering due to convergence time differences. This cross-rule coordination mechanism ensures that the same actuator receives a consistent silent protection period after triggering, avoiding actuator jitter caused by multiple rule competition. For emergency rules that must be responded to first, the configuration parsing unit allows them to be registered as "high-priority rules". The triggering of high-priority rules is not restricted by the convergence coordination group, but the triggering timestamp of the group is also updated after the triggering, extending the silence period of ordinary rules, thus realizing the organic combination of priority response to emergency events and orderly queuing of regular events.

[0085] Step S4: When the triggering condition is continuously satisfied within the condition duration parameter and the convergence time interval is met, the execution result is triggered, and the duration of the execution action is controlled according to the preset output duration parameter.

[0086] This step specifically involves a detailed description of the refined control process for linkage triggering and action execution under multi-dimensional time coordination:

[0087] Pre-trial arbitration and state consistency guarantee for triggering determination

[0088] After the rule judgment unit completes the evaluation of the conditional sub-items of a certain linkage rule, it first enters the pre-arbitration stage of trigger judgment. This stage performs three-fold status checks: First, it checks the activation flag of the rule. If the rule has been marked as "invalid" or "paused," the triggering process is terminated directly to prevent outdated rules from being executed erroneously. Second, it checks the group masking status of the convergence coordination group to which the rule belongs. If the group trigger timestamp shows that it is still in the silent period, the triggering is forcibly masked even if the current rule's own convergence time has expired, ensuring cross-rule coordination consistency. Third, it checks rule dependencies. If the rule is configured with a pre-dependent rule identifier, it queries the last trigger timestamp of the dependent rule. Only if the dependent rule has been triggered within the valid time window is the current rule allowed to enter the subsequent judgment. This pre-arbitration mechanism, through a multi-state lock mechanism, ensures the safety and orderliness of trigger judgment, avoiding trigger chaos caused by concurrent rule competition or configuration changes in industrial monitoring scenarios.

[0089] Final confirmation of condition duration and marking of valid trigger points

[0090] After preliminary arbitration, the rule judgment unit performs final consistency confirmation on the duration of all conditional sub-items of the rule. The unit traverses the sub-linked list of conditional sub-items, checking the current state of the duration state machine for each sub-item. For rules with a logical "AND" linkage, all conditional sub-items' state machines must be in an "activated" state, and the cumulative duration value of each sub-item must exceed its parameter-defined threshold; failure to meet this threshold for any sub-item results in trigger failure. For rules with a logical "OR" linkage, at least one conditional sub-item must be in an "activated" state, and its cumulative value must meet the threshold; the states of other sub-items do not affect the trigger determination. This final confirmation process is completed within an atomic operation cycle to prevent asynchronous changes in sub-item states due to measurement point data updates during the confirmation process. Once all conditional sub-items meet the requirements, the rule judgment unit records the current moment as a valid trigger point and writes this moment into the "timestamp of this trigger" field of the rule node, providing a benchmark for subsequent convergence time calculations. Simultaneously, the unit increments the "trigger counter" of the rule node. This counter is used to count the cumulative number of triggers within the rule's lifecycle, providing data support for system operation status analysis.

[0091] Secondary verification of convergence time interval and trigger token issuance

[0092] After marking a valid trigger point, the rule judgment unit performs a secondary check of the convergence time interval. The unit reads the "last trigger timestamp" field of the rule node and calculates the time difference between the current trigger timestamp and the last trigger timestamp. If the difference is less than the convergence time interval parameter setting, it is determined to be a frequent trigger, and the trigger token is refused to be issued, and the rule enters a silent waiting state; if the difference is greater than or equal to the interval setting value, the trigger is determined to be legal. For the first trigger of a rule, the last trigger timestamp is initialized to a default value much earlier than the system startup time to ensure that the first trigger is unrestricted. After the check passes, the unit copies the current trigger timestamp to the last trigger timestamp field and updates the trigger status record of the rule. Subsequently, the unit generates a trigger token data structure, which contains information such as rule identifier, trigger sequence number, trigger time, and action list pointer, and submits the token to the execution queue of the action scheduling unit. The submission of trigger tokens adopts a priority queue mechanism. Tokens for high-priority rules (such as security alarms) are inserted at the front of the queue and executed first; tokens for ordinary rules are enqueued in the order of submission to ensure fair scheduling. This secondary verification and token issuance mechanism upgrades the convergence interval from a simple timer function to an arbiter of trigger frequency, ensuring that the actuator has sufficient mechanical response and stabilization time, and avoiding mechanical fatigue caused by physical quantity boundary jitter in industrial scenarios.

[0093] De-parsing of action definition sequences and instruction pre-generation

[0094] After retrieving the trigger token from the queue to be executed, the action scheduling unit immediately locks the action definition sub-linked list of the corresponding rule node and executes the reverse parsing and instruction pre-generation process of the action definition. The unit traverses each action node in the action sub-linked list, performing syntax parsing on the target measurement point assignment expression #peripheral code@measurement point code#:target value stored in the action node. The parser extracts the peripheral code and measurement point code, using this code combination as the index key to query the secondary abstract configuration tree constructed in step S1, retrieving the access path of the target measurement point, including information such as the interface type, interface instance number, device address, and register offset. Simultaneously, the parser extracts the target value portion, performing type conversion and range validity verification based on the measurement point's data type definition to prevent out-of-bounds writing of the target value due to configuration errors. After parsing, the unit pre-generates a control instruction structure, which includes fields such as instruction identifier, target interface type, target device address, measurement point register address, target value, and execution priority. For rules with multiple actions in the linkage mode, the unit generates an independent instruction structure for each action node and constructs an instruction sequence according to the order of the actions in the linked list. After the instruction sequence is generated, the unit caches it in the extended field of the trigger token to form a preloaded instruction package. It is then sent out immediately after the output duration parameter arbitration is completed, reducing the delay in instruction generation and improving the execution response speed.

[0095] Output duration mode discrimination and timer coordinated control

[0096] After instruction pre-generation is completed, the action scheduling unit enters the arbitration phase for output duration parameters. The unit reads the output duration parameter value for each action node. If the parameter value is zero, the unit marks the action as a continuous output mode, does not start any timers, and the action status is continuously maintained by the system after the instruction is issued, waiting for the subsequent reverse linkage rule to actively trigger a reset instruction to release it. This mode is suitable for scenarios such as emergency alarms and safety interlocks that need to be maintained for a long time until manual intervention. If the parameter value is non-zero, the unit marks the action as a timed output mode and starts the output duration timer bound to the action node. The timer uses a monotonically increasing hardware timestamp as a reference to avoid software timing drift caused by system load. After the timer starts, the unit immediately sends the pre-generated control instruction package to the interface adapter module to drive the actuator to act. During the timer's operation, the unit continuously monitors the feedback status of the actuator, reads back the actual action confirmation signal of the actuator through the interface adapter module, and if it finds that no valid feedback is received after the instruction is issued, it is determined that the execution has failed, the timer is immediately stopped and a fault alarm event is generated to prevent invalid waiting due to equipment failure. When the timer's accumulated value reaches the set value of the output duration parameter, the timer expiration callback is automatically triggered. The callback function generates a reverse reset command based on the measurement point code of the action node and the original target value. The target value of the command is automatically inferred based on the measurement point type: false for Boolean measurement points and the previous value for numerical measurement points. After the reverse command is sent through the interface adapter module, the actuator returns to its initial state, completing one full timed action execution cycle. The coordinated control of the output duration parameter and the timer elevates the execution of the linkage rule from a simple switching operation to a refined process control that is timed, maintainable, and automatically reset.

[0097] State machine encapsulation and circuit breaker protection for triggering execution process

[0098] The entire trigger execution process is encapsulated as a state machine model, with each linkage rule corresponding to an independent trigger state machine. The state machine includes five states: idle, condition accumulation, trigger arbitration, action execution, and convergence silence. The state transition process is driven collaboratively by the rule judgment unit and the action scheduling unit. In the idle state, the rule judgment unit continuously evaluates the condition sub-items; when a condition sub-item enters the duration accumulation phase, the state machine transitions to the condition accumulation phase; when the condition duration reaches the target and passes the convergence check, it transitions to the trigger arbitration phase; after receiving the trigger token, the action scheduling unit transitions the state machine to the action execution phase; after the action execution is completed (or the timer expires), the state machine enters the convergence silence phase and no longer responds to trigger requests during the convergence interval. This state machine encapsulation makes the state of the entire trigger execution process visible and controllable, facilitating system monitoring and fault diagnosis. Simultaneously, the module configures an exception circuit breaker protection mechanism for each state machine. If, during the execution of an action, the interface adaptation module reports multiple consecutive execution failures, or the execution mechanism's response timeout exceeds a preset threshold, the state machine automatically triggers a circuit breaker. The rule is marked as "fault-suspended," interrupting subsequent triggering attempts for that rule. Detailed fault snapshot information, including the trigger time, execution command, and reason for failure, is reported to the management host. This circuit breaker mechanism prevents rule loops caused by mechanical jamming of the execution mechanism or communication interruptions, protecting system resources from ineffective occupation and improving overall robustness.

[0099] The technical effect of this step: a paradigm shift from discrete triggering to process control in industrial linkage.

[0100] This step elevates the traditional simple "condition met - immediate execution" discrete triggering mode of linkage control to a refined control paradigm encompassing the entire process: "condition accumulation confirmation - frequency arbitration - instruction pre-generation - timed hold - automatic reset - status monitoring." By combining the condition duration parameter with the sliding window algorithm, the technical challenge of anti-jittery industrial sensor signals is solved; through cross-rule coordination of convergence time intervals and trigger token arbitration, the mechanical protection challenge of frequent start-stop operations of actuators is addressed; and through the coordination of the output duration parameter and timer callback, the automation challenge of timing control for linkage actions is resolved. The seamless integration of these three time parameters in the trigger determination, execution scheduling, and result maintenance stages constructs a complete time-dimensional control closed loop, upgrading the linkage control system from a state-response type to a process-control type. This meets the stringent requirements of industrial monitoring scenarios for high reliability, high stability, and long-life operation, producing technical effects unexpected by those skilled in the art.

[0101] Step S5: Through the interface adapter module, manage multiple protocol interfaces such as RS485, DI / DO, and Ethernet in a unified manner to realize unified access of heterogeneous devices and mapping of measurement point data.

[0102] This step specifically involves the interface adaptation module achieving unified access for heterogeneous devices through a three-layer abstract architecture: the bottom physical driver layer operates hardware registers, the middle protocol parsing layer handles state machines for protocols such as Modbus RTU, digital levels, and TCP / IP, and the top abstract service layer provides standardized interfaces for measurement point enumeration, reading and writing, and device querying. The linkage engine can access devices across interfaces without needing to be aware of the underlying protocols. For example, when a temperature and humidity sensor is migrated from RS485 to Ethernet, only the interface ownership configuration needs to be modified; the rule logic does not need to be adjusted.

[0103] After initializing the serial communication parameters, the RS485 interface management unit sends Modbus RTU device identification messages based on the configured address range. It creates logical peripheral instances and assigns codes to the responding devices. By reading the register address range, it infers the measurement point information and automatically matches the register and measurement point semantics using the built-in template library. It then establishes an address-to-measure point mapping and registers it to the upper-layer interface. The unit periodically polls measurement point data in batches. When communication is abnormal, it marks the device as offline and retryes. Upon recovery, it automatically reconnects, enabling plug-and-play functionality for RS485 devices.

[0104] The DI / DO interface management unit initializes input and output pins through the GPIO controller. It employs a dual-layer anti-bouncing mechanism of hardware filter registers and software sliding windows to verify level validity, mapping stable levels to Boolean measurement points and assigning codes. During output, it parses the pin corresponding to the instruction measurement point code, verifies the validity of the target value, drives the level, performs readback confirmation, and reports events in case of faults. The unit creates an input or output measurement point instance for each pin, abstracting digital I / O into unified measurement point read / write operations. It supports DI as the trigger condition and DO as the execution result in linkage rules, forming a digital linkage closed loop.

[0105] The Ethernet interface management unit binds to the local IP address and starts TCP / UDP listening. For Modbus TCP devices, it creates a session context, strips the MBAP header, and processes the data using the protocol engine, mapping it to measurement points. For SNMP devices, it loads the MIB library, periodically sends GET requests, and parses OIDs to map measurement points. For private protocol devices, it supports message template configuration, extracting measurement point values ​​according to the template. The unit virtualizes each network device as an independent interface instance, distinguishing devices by IP address and port number, and assigning independent peripheral codes and measurement point namespaces to achieve logical isolation and independent management of multiple devices.

[0106] Furthermore, step S4 specifically includes: traversing each linkage rule and replacing the formulaic expression with a real-time value; determining whether the triggering condition is effectively met based on the linkage method type and condition duration parameter; executing the action definition in the result list and generating the corresponding interface control instruction after the convergence interval expires; starting a timer to manage the output duration and automatically canceling the output after the duration expires.

[0107] Furthermore, the conditional duration parameter is used for anti-jitter filtering, the output duration parameter is used for timing control, and the convergence time parameter is used to prevent frequent rule triggering. The three constitute a multi-dimensional time-coordinated control mechanism, which effectively reduces the false trigger rate and equipment wear in industrial monitoring scenarios.

[0108] Furthermore, the method is applicable to scenarios such as computer room environment monitoring, substation automation, and intelligent building management, enabling fire alarm linkage, temperature and humidity over-limit linkage, and equipment status linkage control, and supports end-user self-configuration without the need for developer intervention.

[0109] Furthermore, when adding new equipment or measurement points, only the configuration needs to be updated without modifying the program code. The system configuration efficiency is significantly improved compared to the traditional hard-coding method, supporting the need for rapid on-site deployment.

[0110] By adopting the above-disclosed technical solution of this invention, the following beneficial effects are obtained:

[0111] This invention achieves a breakthrough in unified access for heterogeneous devices in industrial monitoring scenarios through a three-layer protocol abstraction architecture and a multi-dimensional device management mechanism in the interface adaptation module. The protocol independence design completely encapsulates underlying communication differences, enabling the linkage engine to achieve transparent cross-protocol access without needing to perceive the physical interfaces of devices, significantly reducing the development complexity and maintenance costs of multi-protocol hybrid networking. The dynamic device discovery and automatic measurement point mapping mechanism of the RS485 interface transforms the access of serial bus devices from traditional manual address configuration and register mapping into a plug-and-play automated process, greatly reducing the workload of on-site deployment and debugging, and allowing device replacement or expansion to be completed without professional personnel intervention. The dual-layer anti-jitter and bidirectional measurement point mapping mechanism of the DI / DO interface not only solves the reliability problem of digital signals being susceptible to interference in industrial environments, but also unifies input status monitoring and output control into standardized measurement point operations, realizing a complete closed loop of digital quantity linkage and improving system stability and determinism. Ethernet interface protocol adaptation and device virtualization mechanism enable the system to be compatible with both standard industrial protocols and proprietary protocols. Network devices obtain independent namespaces through virtualization isolation, and logical isolation and fine management can be achieved even when multiple devices share a physical network card, which greatly expands the system's applicability and configuration flexibility.

[0112] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A multi-point device linkage control system for industrial monitoring scenarios, characterized in that, include: The configuration management module is used to abstract physical devices into logical peripherals and assign unique peripheral codes. It configures at least one measurement point for each peripheral and assigns a measurement point code, forming a two-level abstract configuration of devices and measurement points. The rule configuration module is used to receive the linkage rules defined by the user in JSON format. The linkage rules include a trigger condition consisting of at least one condition sub-item, an execution result corresponding to the trigger condition, and a convergence time interval for preventing the rule from being triggered frequently. Each condition sub-item includes a formulaic expression based on the peripheral code and the measurement point code: #peripheral code@measurement point code@attribute#, and a condition duration parameter for filtering transient interference. The linkage engine module is used to load and parse the linkage rules, collect real-time data from each measuring point in a loop, and when the triggering condition is continuously satisfied within the condition duration parameter and the convergence time interval is satisfied, the execution result is triggered and the duration of the execution action is controlled according to the preset output duration parameter. The interface adapter module is used to uniformly manage multiple interface protocols such as RS485, digital input (DI) / digital output (DO), and Ethernet, enabling unified access of heterogeneous devices and mapping of measurement point data.

2. The system according to claim 1, characterized in that, The linkage engine module includes a configuration parsing unit, a data acquisition unit, a rule judgment unit, and an action scheduling unit. The configuration parsing unit constructs a rule linked list structure in memory. The rule judgment unit replaces the encoded references in the formulaic expression with real-time values ​​to form a computable logical expression. The action scheduling unit generates control instructions and starts a timer to manage the output duration.

3. The system according to claim 1, characterized in that, The condition duration parameter is used to eliminate sensor transient fluctuation interference in industrial monitoring scenarios, the output duration parameter is used to control the action holding time of the actuator, and the convergence time interval is used to prevent the actuator from frequently starting and stopping due to repeated fulfillment of conditions. The three together constitute a multi-dimensional time control mechanism to improve system stability.

4. The system according to claim 1, characterized in that, The interface adaptation module includes an RS485 interface management unit, a DI / DO interface management unit, and an Ethernet interface management unit. The RS485 interface management unit supports dynamic access of Modbus RTU protocol devices, and the DI / DO interface management unit is used to map digital input and output signals to measurement point status.

5. The system according to any one of claims 1-4, characterized in that, The system is applied to scenarios such as fire alarm linkage, temperature and humidity over-limit alarm, and equipment start-up and shutdown control in computer room environment monitoring, substation automation, and intelligent building management, allowing users to configure it independently without modifying the source code.

6. A method for coordinated control of multi-point devices in industrial monitoring scenarios, characterized in that, Includes the following steps: Step S1: Abstract the physical device into a logical peripheral through the configuration management module and assign a unique peripheral code. Assign a measurement point code to the measurement point of each peripheral and establish a two-level abstract configuration between the device and the measurement point. Step S2: Receive the linkage rules defined by the user in JSON format through the rule configuration module. The linkage rules include a triggering condition consisting of at least one condition sub-item, the execution result corresponding to the triggering condition, and a convergence time interval for preventing the rule from being triggered frequently. Each condition sub-item includes a formulaic expression based on the peripheral code and the measurement point code: #peripheral code@measurement point code@attribute#, and a condition duration parameter for filtering transient interference. Step S3: The linkage engine module loads and parses the linkage rules, and cyclically collects real-time data from each measuring point; Step S4: When the triggering condition is continuously satisfied within the condition duration parameter and the convergence time interval is satisfied, the execution result is triggered and the duration of the execution action is controlled according to the preset output duration parameter; as well as Step S5: Through the interface adapter module, manage multiple protocol interfaces such as RS485, DI / DO, and Ethernet in a unified manner to realize unified access of heterogeneous devices and mapping of measurement point data.

7. The method according to claim 6, characterized in that, Step S4 specifically includes: traversing each linkage rule and replacing the formulaic expression with a real-time value; determining whether the triggering condition is effectively met based on the linkage method type and condition duration parameter; executing the action definition in the result list and generating the corresponding interface control instruction after the convergence time interval expires; starting a timer to manage the output duration and automatically canceling the output after the duration expires.

8. The method according to claim 6, characterized in that, The condition duration parameter is used for anti-jitter filtering, the output duration parameter is used for timing control, and the convergence time parameter is used to prevent frequent rule triggering. The three constitute a multi-dimensional time-coordinated control mechanism, which effectively reduces the false trigger rate and equipment wear in industrial monitoring scenarios.

9. The method according to claim 6, characterized in that, The method is applicable to scenarios such as computer room environment monitoring, substation automation, and intelligent building management, and can realize fire alarm linkage, temperature and humidity over-limit linkage, and equipment status linkage control. It supports end users to configure it independently without the need for developers to intervene.

10. The method according to any one of claims 6-9, characterized in that, When adding new equipment or measurement points, only the configuration needs to be updated without modifying the program code. The system configuration efficiency is significantly improved compared to the traditional hard-coding method, supporting the need for rapid on-site deployment.

Images