A weak current building automatic control system device linkage control method and system

Abstract

The application provides a weak current building automatic control system equipment linkage control method and system, relates to the building automatic control technical field, and the technical scheme points are as follows: the state record of the fire compartment door in the preset time period before and after the event is acquired, the actual opening and closing condition is determined, and is compared with the default crossing attribute, when the actual opening and closing condition is inconsistent, the actual opening and closing condition is taken as the target crossing attribute, so that the propagation range of the linkage control instruction is consistent with the actual physical isolation state, the linkage range misalignment problem caused by the static topology lag is avoided, the accuracy and reliability of the fire emergency linkage are improved, and have important application value.

Description

Technical Field

[0001] This application relates to the field of building automation control technology, and more specifically, to a method and system for the linkage control of equipment in a low-voltage building automation system. Background Technology

[0002] In building automation systems, the coordinated control of equipment after a fire alarm event is triggered is a crucial aspect of ensuring building safety. When a detector in a certain zone issues an alarm, the system typically needs to determine the event source zone and its adjacent zones based on the location of the event and the preset spatial topology. It then decides whether to propagate coordinated control commands such as alarms, evacuation broadcasts, and access control releases from the event source zone to adjacent zones, so as to coordinate the low-voltage equipment in the relevant areas to perform emergency actions.

[0003] Currently, common implementations primarily rely on pre-configured building space topology maps. In this topology map, fire compartment doors separating different fire compartments are considered boundary nodes and assigned fixed default crossing attributes, such as being marked as blocking or passable. When a fire alarm event occurs, the system, based on the default crossing attributes recorded in this static topology and the priority of the event itself, decides whether to generate and issue linkage control commands to adjacent compartments, and sorts the devices to be included in the linkage. This method can complete basic linkage control tasks when the topology data remains consistent with the on-site physical environment over a long period.

[0004] However, in actual building operation, the physical state of fire compartment doors often changes temporarily or continuously due to personnel passage, temporary construction, equipment aging, or maintenance. For example, for convenient daily passage, fire compartment doors may be wedged open and kept open, or they may fail to close properly due to door closer malfunction or component damage. Although some building automation systems have the ability to collect real-time status data of fire compartment doors through door magnetic sensors and door closer status bits, this real-time status data is mostly used only for equipment monitoring, alarm recording, or display on the operation and maintenance interface, and is not systematically incorporated into the cross-zone linkage judgment process when a fire alarm event occurs. The default traversal attributes in the spatial topology database often cannot be updated in a timely manner, causing them to lag behind the actual physical state of the door.

[0005] This disconnect between static topology and real-time physical status can easily lead to inaccurate cross-zone linkage ranges during fire alarm events. When a fire compartment door is actually open but the static topology attribute is marked as blocked, the system may incorrectly intercept alarm broadcasts and evacuation instructions that should be propagated to adjacent zones, preventing critical low-voltage equipment from responding in a timely manner and delaying personnel evacuation and emergency response. Conversely, when a door has actually closed due to a malfunction and the topology attribute is marked as passable, the system may incorrectly propagate linkage instructions to physically isolated adjacent areas, causing unrelated equipment to be activated unnecessarily. This not only wastes emergency resources but may also disrupt normal security operations. This inaccuracy in linkage range affects the reliability and efficiency of emergency response and poses certain safety hazards.

[0006] To address the aforementioned issues, existing technologies urgently need improvement. Summary of the Invention

[0007] The purpose of this application is to provide a method and system for linkage control of low-voltage building automation system equipment, which has the advantages of being able to dynamically adjust the cross-zone linkage judgment criteria according to the actual opening and closing status of fire compartment doors, and improving the accuracy and reliability of fire emergency linkage.

[0008] This application provides a method for the linkage control of equipment in a low-voltage building automation system, the technical solution of which is as follows:

[0009] A method for linkage control of equipment in a low-voltage building automation system includes:

[0010] Obtain event trigger information for fire alarm events, and determine the event source zone and adjacent zones based on the event trigger information;

[0011] Obtain the status records of the fire compartment doors located between the event source partition and the adjacent partition within a preset time period before and after the time corresponding to the event trigger information, and determine the actual opening and closing status of the fire compartment doors at the time corresponding to the event trigger information based on the status records;

[0012] The actual opening and closing status is compared with the default crossing attribute pre-configured for fire compartment doors in the building space topology. When the actual opening and closing status is inconsistent with the default crossing attribute, the actual opening and closing status is used as the target crossing attribute. The target crossing attribute is used as the basis for determining whether to send linkage control commands to adjacent compartments.

[0013] Furthermore, this application also proposes a step for determining the actual opening and closing status of a fire compartment door at the moment corresponding to the event triggering information, based on the status record, including:

[0014] Based on the acquisition time of the state records, organize the state values ​​in the state records to obtain a state time description that describes the state changes over time.

[0015] Based on the continuous maintenance of state values ​​in the state-time description, determine the stable state at the moment corresponding to the event trigger information, and use the stable state as the actual opening and closing state.

[0016] Furthermore, this application also proposes a step for determining the steady state at the moment corresponding to the event triggering information based on the continuous maintenance of state values ​​in the state-time description, including:

[0017] When it is determined from the state-time description that the fire compartment door is in an unstable state transition process at the corresponding time, the state in the state transition process is not regarded as a stable state.

[0018] Retrieve supplementary status records for the supplementary time period following the corresponding time.

[0019] Based on the continuous maintenance of state values ​​in the supplementary state record, the stable state within the supplementary time period is determined, and this stable state is taken as the actual opening and closing state.

[0020] Furthermore, this application also proposes that when the state time description indicates that the fire compartment door undergoes multiple state changes within a preset time period and the continuous holding time of each state value does not reach the preset stable time, a state unreliable mark is generated to indicate that the reliable state cannot be determined, and the state unreliable mark is used as the actual opening and closing status.

[0021] The method also includes:

[0022] When the actual opening and closing status is marked as unreliable, the target traversal attribute is determined according to the pre-configured conservative propagation rules.

[0023] Furthermore, this application also proposes that when a state time description cannot be obtained from the state record, a state missing marker is generated to characterize the missing state record, and the state missing marker is used as the actual opening and closing status.

[0024] The method also includes:

[0025] When the actual opening / closing status is a missing state marker, the target crossing attribute is determined according to the conservative propagation rule.

[0026] Furthermore, this application also proposes that the target traversal attributes be determined according to pre-configured conservative propagation rules, including:

[0027] When the default crossing attribute of a fire compartment door is blocked, the target crossing attribute is determined to be passable, and a restricted marker is generated. The restricted marker is used to prevent the linkage control command for access control release in adjacent compartments from being issued until it is confirmed.

[0028] When the default cross-cross attribute is set to crossable, the target cross-cross attribute is set to block.

[0029] Furthermore, this application also proposes that the target crossing attributes include traversable attributes, blocking attributes, and restricted traversable attributes;

[0030] The method also includes:

[0031] Add the low-voltage interconnected devices within the event source partition to the immediate execution queue;

[0032] For adjacent partitions, when the target crossing attribute is a traversable attribute, the low-voltage linkage devices in the adjacent partition are added to the immediate execution queue.

[0033] When the target crosses an attribute that is blocking, the low-voltage interconnected devices in the adjacent partition will not be included in the linkage range.

[0034] When the target traversal attribute is restricted traversable attribute, alarm broadcast type low-voltage linkage devices in the adjacent partition are assigned to the immediate execution queue, and access control type low-voltage linkage devices in the adjacent partition are assigned to the pending confirmation execution queue. The linkage control commands in the pending confirmation execution queue are not executed before external confirmation is obtained.

[0035] Furthermore, this application also proposes, and includes:

[0036] Obtain status anomaly information generated in different fire alarm event processing for the same fire compartment door, which is used to characterize the status anomaly of the fire compartment door when determining cross-zone propagation;

[0037] Based on the abnormal status information obtained multiple times, the cumulative abnormal information of the fire compartment door is determined;

[0038] When the accumulated abnormal information meets the preset conditions, obtain the boundary confirmation information used to characterize the current actual state of the fire compartment door;

[0039] Based on the boundary confirmation information, the default crossing attribute pre-configured for the door of this fire compartment in the building space topology is updated to the crossing attribute corresponding to the boundary confirmation information.

[0040] Furthermore, this application also proposes that, when it is determined that a fire compartment door is in an unstable state switching process at a corresponding moment, the method further includes:

[0041] The first crossing attribute is determined based on the state during the state transition process, and the initial linkage control command is generated based on the first crossing attribute.

[0042] After taking the stable state during the supplementary time period as the actual opening and closing situation, the second crossing attribute is determined based on the stable state.

[0043] When the first span attribute is inconsistent with the second span attribute, update the instructions that have not yet been executed in the initial linkage control instructions according to the second span attribute, and keep the high-priority instructions that have been executed in the initial linkage control instructions unchanged.

[0044] In addition, this application also provides a linkage control system for low-voltage building automation system equipment, the technical solution of which is as follows:

[0045] A low-voltage building automation system equipment linkage control system, used to execute the above method, includes:

[0046] The event trigger information acquisition module is used to acquire event trigger information of fire alarm events and determine the event source partition and the adjacent partitions adjacent to the event source partition based on the event trigger information.

[0047] The actual opening and closing status determination module is used to obtain the status records of the fire compartment doors located between the event source zone and the adjacent zone within a preset time period before and after the time corresponding to the event trigger information, and to determine the actual opening and closing status of the fire compartment doors at the time corresponding to the event trigger information based on the status records.

[0048] The target crossing attribute determination module is used to compare the actual opening and closing status with the default crossing attribute pre-configured for fire compartment doors in the building space topology. When the actual opening and closing status is inconsistent with the default crossing attribute, the actual opening and closing status is used as the target crossing attribute. The target crossing attribute is used as the basis for determining whether to issue linkage control commands to adjacent compartments.

[0049] As can be seen from the above, the low-voltage building automation system equipment linkage control method and system provided in this application obtains the status records of fire compartment doors within a preset time period before and after an event, determines their actual opening and closing status, and compares them with the default crossing attribute. When they are inconsistent, the actual opening and closing status is used as the target crossing attribute, thereby ensuring that the propagation range of the linkage control command is consistent with the actual physical partition status, avoiding the problem of inaccurate linkage range caused by static topology lag, improving the accuracy and reliability of fire emergency linkage, and having important application value. Attached Figure Description

[0050] Figure 1 A schematic diagram of the method flow provided in this application.

[0051] Figure 2 A schematic diagram of the overall process provided for this application. Detailed Implementation

[0052] The following description, in conjunction with the technical solution of this application, provides a clearer and more complete explanation of the relevant content. It should be noted that the embodiments described herein are only a part of the implementation methods of this application, and not all of them. Other implementation methods obtained by those skilled in the art based on the embodiments of this application without creative effort should also fall within the protection scope of this application. Furthermore, in the description of this application, the terms "first," "second," etc., are mainly for distinction and should not be construed as indicating relative importance.

[0053] Reference Figure 1 This application proposes a method for the linkage control of equipment in a low-voltage building automation system, including:

[0054] S1. Obtain the event trigger information of the fire alarm event, and determine the event source zone and the adjacent zones adjacent to the event source zone based on the event trigger information;

[0055] S2. Obtain the status records of the fire compartment door located between the event source partition and the adjacent partition within a preset time period before and after the time corresponding to the event trigger information, and determine the actual opening and closing status of the fire compartment door at the time corresponding to the event trigger information based on the status records.

[0056] S3. Compare the actual opening and closing status with the default crossing attribute pre-configured for the fire compartment door in the building space topology. When the actual opening and closing status is inconsistent with the default crossing attribute, the actual opening and closing status is used as the target crossing attribute. The target crossing attribute is used as the basis for determining whether to send linkage control commands to adjacent compartments.

[0057] In some real-world scenarios, a fire compartment door in an office building is deliberately wedged shut for ease of daily access, remaining permanently open. However, the default cross-border attribute pre-configured for this door in the building space information database is still "block," a static value set based on the door's design function as a fire compartment boundary node. When a smoke detector near this door triggers a fire alarm, the standard linkage control process directly uses the pre-configured blocking attribute in the topology library to determine that the event is confined to this compartment and will not propagate the linkage command to the adjacent compartment on the other side of the door. However, because the door is actually open, there is no physical barrier to smoke and potential fire, and personnel in adjacent compartments face equal risk. The audible and visual alarms and emergency broadcasts in this compartment remain silent, and the access control controller does not execute any release actions, resulting in a fatal coverage blind spot in evacuation guidance. The root cause of this blind spot is that the boundary door cross-border attribute used for determining cross-community propagation is misaligned with the actual open / closed state of the door at the time of the event.

[0058] The execution process of this solution is specifically designed to correct this misalignment. In S1, the event triggering information of the fire alarm event is obtained. After detecting a fire alarm signal, the fire alarm control panel generates an alarm event message containing a unique detector identifier, alarm type, and precise trigger timestamp. When this message enters the linkage processing stage, the detector ID and trigger timestamp T_event are first parsed out. Subsequently, based on the detector ID, the partition to which its installation location belongs is retrieved in the building space information database, and it is marked as the event source partition Z_src. At the same time, the partition records that are adjacent to Z_src in the building space topology map are traversed to locate all adjacent partitions separated by fire compartment doors as boundary nodes, forming an adjacent partition set Z_adj. This step determines the origin of the event and the potential cross-zone propagation direction, providing spatial constraints for subsequently locking the boundary nodes that need to be verified.

[0059] Upon entering S2, the real-time status records of the associated fire compartment doors are first obtained. For the unique fire compartment door between Z_src and each Z_adj, a list of boundary doors to be verified is generated. A preset time window is constructed based on T_event, for example, 5 seconds before and 3 seconds after T_event. This time window setting captures the actual physical state of the doors before and after the event trigger, and tolerates millisecond to second-level reporting delays that may exist from door magnetic sensors. Subsequently, the system requests all status records of all boundary doors in this list within this time window from the door status database of the building automation system or fire monitoring system. These records typically come from periodic collection of fire door magnetic switches or event-driven reporting. Each record includes at least the door ID, status value (e.g., closed, open, faulty, offline), timestamp of status collection, and data source identifier.

[0060] For each boundary door, one or more status records acquired within the time window are sorted by timestamp. If only a single record or multiple consecutive records have the same status value, this consistent status value can be extracted as the actual opening / closing status of the fire compartment door at time T_event. If the records show that the door status changed within the time window, the status of the record closest to T_event and later than T_event by no more than a preset small tolerance is preferred. This is because the cross-zone propagation of fire events is essentially concerned with the pathway conditions for the spread of smoke and fire after the event. Thus, from the sensor time-series data, an estimated value representing the physical open / closed state of the door at the time of the event is synthesized, which is referred to here as the actual opening / closing status.

[0061] It is understandable that the actual opening and closing status here is not a simple snapshot of instantaneous sensor readings, but rather an inference based on the synthesis of states from continuous records within a time window before and after the event. It reflects the physical path state upon which the linkage propagation determination should rely. This is fundamentally different from the default span attribute pre-configured in the static database, in terms of information timeliness and the ability to reflect physical reality.

[0062] After obtaining the actual opening and closing status, S3 performs verification and on-demand correction. For each boundary door to be verified, the actual opening and closing status determined in S2 is compared with the pre-configured default crossing attribute read from the building space topology library. The default crossing attribute typically includes two types: blocking and passable, representing whether the door should be in a closed blocking state or a passable state under ideal fire compartment design, respectively. If the comparison result shows that the two are consistent, for example, the door is actually closed and the topology is blocked by default, then it can be determined that the static topology is still valid at this moment, and the original attribute is directly used as the target crossing attribute for subsequent cross-zone propagation determination.

[0063] When the two are inconsistent, it means that the original cross-zone determination logic has been broken, i.e., there is a deviation between the determination basis and the actual physical state. In this case, the actual opening and closing status inferred from the real-time status is taken as the target crossing attribute. Specifically, in the aforementioned office building scenario, if the door is wedged open and remains open, its actual opening and closing status is open, while the default crossing attribute is blocked. Through this comparison and correction, the target crossing attribute of the boundary door in this event is forcibly corrected to be crossable. Therefore, when determining whether to issue a linkage control command to the adjacent zone based on the target crossing attribute, it will be determined that the boundary is crossable, thereby including the affected audible and visual alarms, emergency broadcast terminals, and access control controllers in the adjacent zone into the linkage scope.

[0064] This approach differs from conventional methods based on simple rule triggers. The proposed solution does not rely on a single threshold judgment of existing state bits, nor does it directly use sensor data as a generator of control commands. Instead, it inserts a closed-loop verification and correction action driven by real-time door status at the critical decision point of cross-zone propagation judgment within the existing open-loop decision chain that relies on static topology and event priorities. This action transforms the implicit relationship where the default cross-zone attribute in the static topology library is directly used as the sole basis for decision-making into a relationship that can be explicitly verified and corrected as needed each time an event is triggered. In this way, the target cross-zone attribute ultimately used to filter the set of linked devices and arrange the execution sequence can follow the actual open / closed state of the fire compartment doors in real time, allowing the linkage range to more closely reflect the actual fire compartment and personnel escape route conditions at the time of the event.

[0065] When directly determining the opening and closing status of fire compartment doors based on discrete state records, the door may rebound rapidly after being pushed open, the door closer may oscillate, or the door magnetic signal may jump instantaneously near the closing point, resulting in the acquisition of the door's momentary passing state. This transient state cannot represent the true continuous on / off state of the door before and after the event, easily leading to subsequent topology comparisons and corrections based on incorrect actual opening and closing conditions. To address this, this application proposes a steady-state determination process based on time continuity:

[0066] The steps for determining the actual opening and closing status of fire compartment doors at the time corresponding to the event trigger information based on the status records include: organizing the status values ​​in the status records according to the time of collection of the status records to obtain a status time description describing the changes of the status over time; determining the stable state at the time corresponding to the event trigger information based on the continuous maintenance of the status values ​​in the status time description, and taking the stable state as the actual opening and closing status.

[0067] In the specific implementation process, after acquiring the state records within a preset time window before and after the event trigger time, a stability judgment process based on temporal continuity is triggered. First, the state values ​​are organized according to the acquisition time of each state record to form a state time description that reflects the change of state over time. As an optional implementation method, the state records within the time window can be sorted according to the acquisition time, and the state values ​​of adjacent records can be checked for consistency. If the state values ​​are consistent, they are merged into a continuous state segment. This continuous state segment can include a start time, an end time, a state value, and a duration. In this way, the originally discrete multiple records are organized into a descriptive form that can reflect temporal continuity.

[0068] After obtaining the state time description, the system determines whether a stable state exists near the event trigger time based on the continuity of the state values ​​in the description. Specifically, it checks whether there is a continuous state segment before and after the event trigger time that includes that moment, and whether the duration of this segment reaches a preset stability threshold. If the stability threshold is reached, it can be determined as a stable state. The preset stability threshold can be configured based on the mechanical action time of the fire compartment door, the door closer rebound characteristics, and the sampling period of the door magnetic sensor to tolerate normal opening and closing actions and identify short-term jitter.

[0069] When an event triggers precisely at a state transition point, a judgment can be made by combining the observation segments before and after the event. For example, if the state is closed before the event and changes to open after the event, and the open state lasts only a short time before reverting to closure, then the open state at the time of the event does not constitute a stable state. Only when the state meets the continuous maintenance condition before and after the event will it be considered an actual open or closed state. If the state time description shows that the door's state does not meet the stability condition near the event time, it will not be directly identified as a stable state, and the corresponding unstable state processing procedure can be initiated.

[0070] Through the above processing, the intermediate information attribute regarding the actual opening and closing status of the door at the moment of the event will change. This intermediate information, which might have originally been an estimated value sampled from discrete records, will be transformed into a stable state determination result representing the door's continuous physical state after filtering based on time continuity. This result filters out instantaneous opening and closing fluctuations that do not meet the stable holding conditions, and can characterize the door's continuous passage or blocking capability before and after the event. Even if the fire alarm event happens to occur within the short-term jump period of the fire compartment door's state, it can avoid misjudging the door's instantaneous passage state as a continuous passable state or a continuous blocking state. This reduces misjudgments of cross-zone propagation range caused by state sampling distortion, and allows subsequent comparisons and corrections with the default crossing attribute to be based on a basis closer to the door's true continuous physical conditions, thereby improving the reliability of linkage control decisions.

[0071] In determining a stable state based on the state-time description, a fire compartment door may be in a transitional phase between opening and closing. Directly classifying it as either open or closed could lead to misjudgment. Furthermore, in some priority methods, the step of determining the stable state at the time corresponding to the event trigger information based on the continuous maintenance of state values ​​in the state-time description includes: when the state-time description determines that the fire compartment door is in an unstable state transition process at the corresponding time, the state during the transition process is not considered a stable state; supplementary state records are obtained within a supplementary time period after the corresponding time; based on the continuous maintenance of state values ​​in the supplementary state records, the stable state within the supplementary time period is determined, and this stable state is taken as the actual opening / closing status.

[0072] When determining a stable state based on the state-time description, the duration of continuous state value retention in the state-time description can be checked. If the state-time description shows that the fire compartment door was closed before the event trigger time, and then opened shortly after the event trigger time, and the duration of the open segment has not yet reached the preset stability threshold, then the fire compartment door can be determined to be in an unstable state transition process at the corresponding moment. In this state, directly accepting the instantaneous state may misjudge a door that closes immediately upon rebound as continuously passable. Therefore, the state during the state transition process can be excluded from the stable state, and a delayed confirmation mechanism can be activated.

[0073] After activating the delayed confirmation mechanism, supplementary status records can be obtained within a supplementary time period following the corresponding moment. The supplementary time period can be one to three seconds after the event trigger moment, and this duration can be configured according to the acquisition delay, enabling stability verification to be completed in a very short time after the event. While obtaining supplementary status records, real-time reporting messages from door magnetic sensors can continue to be received, or a status query for the door of the fire compartment within the supplementary time period can be initiated to the door status database.

[0074] After obtaining the supplementary status records, the stable state within the supplementary time period can be determined based on the continuity of the status values ​​in the supplementary status records. The supplementary status records can be sorted by acquisition time to check whether the state remains consistent and reaches a preset stability threshold within the supplementary time period. If the state remains consistent and reaches the preset stability threshold, the stable state can be identified as the actual open / closed state. If the state is still unstable after the supplementary time period ends, other anomaly handling mechanisms can be invoked.

[0075] By introducing supplementary observation periods, the instantaneous opening and closing states can be excluded from the criteria for determining the propagation of the fire. Therefore, the determination of whether the fire propagates across zones is based on the actual, stabilized door state after the event. This method avoids misjudgments of the linkage range caused by short-term jumps in door magnetic signals or door closer rebound, making the set of linkage objects more closely match the actual passage conditions after a fire.

[0076] In actual office buildings and other structures, fire compartment doors may experience repeated opening and closing vibrations near the event trigger moment due to mechanical failure of the door closer or oxidation of the magnetic switch contacts. This high-frequency oscillation causes multiple alternating open and closed segments in the status record. If the instantaneous state closest to the event moment is forcibly extracted from these records as the actual opening and closing status, it is easy to misjudge the door's true passage capacity, leading to the incorrect blocking or opening of cross-zone linkage propagation range. To address this, this application proposes an abnormal handling mechanism for the vibration state.

[0077] Further, in some preferred embodiments, when the status time description indicates that the fire compartment door has changed its status multiple times within a preset time period and the continuous holding duration of each status value has not reached the preset stable duration, a status unreliable flag is used as the actual opening / closing situation; the method further includes: when the actual opening / closing situation is the status unreliable flag, determining the target crossing attribute according to the pre-configured conservative propagation rule.

[0078] When identifying the jitter state, traverse the sequence of status segments in the status time description and count the status switching situations within the preset time period. When it is found that there are segments of multiple different statuses and the duration of each segment is less than the preset stable duration threshold, it is determined that the current is in the jitter state. The preset stable duration can be set to values such as 2 seconds, 3 seconds, or 5 seconds, and can be configured and adjusted according to the type of fire compartment door or the response characteristics of the door magnetic sensor. The status unreliable flag can be a specific value in the enumeration value of the actual opening / closing situation in the specific implementation, or represented by an independent flag bit. After generating this flag, the subsequent conventional path of comparing the actual opening / closing situation with the default crossing attribute can be blocked. It should be noted that the reason for blocking the conventional path here in this application is that when the status jumps frequently, any single instantaneous status cannot truly reflect the physical isolation ability of the boundary.

[0079] When it is detected that the actual opening / closing situation is the status unreliable flag, call the pre-configured conservative propagation rule. The conservative propagation rule adopts a safety-oriented strategy of assuming the risk in case of doubt based on the high-priority attribute of the fire event, giving priority to ensuring the coverage of evacuation alarms, and at the same time tightening the actions that may introduce safety risks. Through the above processing, in the case where the door status is extremely unstable, the target crossing attribute is conservatively determined using the preset safety strategy, avoiding the randomness of the linkage decision. This prevents the incorrect blocking of the sound and light alarm evacuation broadcast to the adjacent compartment due to obtaining an instantaneous closed state, and also prevents the incorrect release of the access control to the area that has been physically partitioned due to obtaining an instantaneous open state. At the same time, this processing provides a clear abnormal flag and trigger record for the subsequent maintenance personnel to review the door status, facilitating the quick positioning of the fault boundary node.

[0080] Further, in some preferred embodiments, when the status time description cannot be obtained based on the status record, a status missing flag is used as the actual opening / closing situation, and the method further includes: when the actual opening / closing situation is the status missing flag, determining the target crossing attribute according to the conservative propagation rule.

[0081] In actual operation, due to reasons such as sensor failure, communication interruption, or abnormal door status acquisition nodes, valid status records may not be obtained within the preset time window, or the number of records obtained is insufficient, the timestamps deviate severely, or the status values are invalid, resulting in the inability to construct an effective status time description. In response to this, the above abnormal processing branch is proposed in this application.

[0082] Specific situations where a state time description cannot be obtained from the state record may include, but are not limited to, no state record being returned within a preset time window, the number of returned state records being less than the minimum requirement, the deviation between the timestamps of all available records and the corresponding time of the event trigger information exceeding the maximum allowable delay threshold, invalid state values ​​in the records, or unreliable data source identifiers. When any of the above situations occur, a state missing flag can be generated. The state missing flag can be implemented as a specific enumerated value or by adding an information sufficiency flag to the data structure to distinguish it from normal state values ​​such as open or closed.

[0083] State loss is distinct from jitter or transition states. State loss is typically due to insufficient data in the perception layer, making it impossible to determine the state, while jitter and transition states usually indicate that the gate has actually performed unstable actions. By distinguishing these abnormal situations, the specificity of subsequent processing can be improved.

[0084] When the actual opening / closing status is marked as missing, a conservative propagation rule can be triggered. This conservative propagation rule can be a pre-defined set of security policies, executed when a missing status is detected, and outputs a restricted target traversal attribute based on the event priority and the door's static default traversal attribute. The specific strategy of the conservative propagation rule can be further elaborated in subsequent steps.

[0085] By generating state missing markers, the actual opening and closing status can reflect the semantics of missing information, avoiding the overwriting of the true situation with erroneous state values. By invoking conservative propagation rules, subsequent cross-regional propagation decisions and coordinated execution can be carried out within preset safety boundaries, preventing loss of control due to data link breaks. This avoids the possibility of incorrectly truncating or improperly amplifying the linkage range due to unfounded use of static topology, and also avoids secondary misjudgments that may be introduced by forcibly correcting based on unreliable data, ensuring that the linkage propagation decision maintains a safety orientation even under conditions of missing information.

[0086] In scenarios where the status of fire compartment doors is identified as unreliable or missing, as described above, how to formulate conservative and secure cross-zone propagation rules to avoid erroneously intercepting evacuation alarms or mistakenly releasing access control is a problem that needs to be solved. To address this, this application proposes determining the target crossing attribute based on pre-configured conservative propagation rules, including: when the default crossing attribute of a fire compartment door is blocking, determining the target crossing attribute as traversable and generating a restricted marker; the restricted marker is used to prevent the issuance of linkage control commands for access control releases within adjacent compartments until confirmation is received; when the default crossing attribute is traversable, determining the target crossing attribute as blocking.

[0087] When the gate state is unreliable, relying on a single value for judgment is not feasible. Therefore, a conservative correction strategy based on static default attributes can be adopted. The default crossing attribute is a static boundary crossing attribute read from the building space topology library. Under normal circumstances without anomalies, it can serve as the basis for linkage propagation. When the state is unreliable, the default crossing attribute can serve as a relatively stable and reliable benchmark, and this can be used as the starting point for correction.

[0088] When the default crossing attribute is set to block, based on the principle of prioritizing high-priority fire incidents, the security of evacuation alarm coverage is higher than the security risk of local passageways. Therefore, the target crossing attribute is forcibly set to crossable, enabling audible and visual alarms and emergency broadcast terminals to coordinate across zones, ensuring that evacuation notifications are not interrupted. Simultaneously, a restricted marker is generated. The restricted marker is essentially a control level identifier; its function is to change the execution permission status of access control release commands, placing these commands in a pending state until independent confirmation is obtained. Confirmation can come from various sources, such as manual confirmation by maintenance personnel on the monitoring interface, automatic confirmation after the boundary door status is restored, or automatic review confirmation after the supplementary observation period ends. By preventing access control release through the restricted marker, security risks caused by releasing access control when the true status of the passageway is unclear can be prevented, achieving a balance between alarm coverage and passageway security.

[0089] In practical implementation, access control release can be considered a typical example of a high-risk action. In other possible implementations, restricted markings can also be extended to other high-risk actions requiring careful access, such as the lowering of fireproof roller shutters or the cutting off of power to a specific area.

[0090] When the default traversal attribute is traversable, the target traversal attribute is forcibly set to blocked, based on the principle of prioritizing the independence and security of adjacent partitions. If the status is unclear and the static topology is already set to traversable, continuing to assume traversability might include physically blocked adjacent partitions in the linkage. By forcibly blocking, we can avoid blindly issuing linkage commands to potentially physically isolated adjacent areas, reduce resource waste caused by erroneous linkage, and prioritize the independence of the adjacent partition.

[0091] After obtaining the target spanning attributes for each adjacent partition through the aforementioned process, it is necessary to further determine the actual set of linkage control commands to be issued based on these attributes. However, in cases where the boundary state is uncertain or restricted, issuing commands uniformly to all linkage devices within adjacent partitions without differentiation may pose safety risks. For example, actions involving the opening of physical channels may be incorrectly executed when safety conditions are not met, or no commands may be issued to adjacent partitions at all due to boundary uncertainty, thereby delaying evacuation warning actions. To address this, this application proposes a further hierarchical command management scheme.

[0092] The target crossing attributes include traversability, obstruction, and restricted traversability. The method further includes: adding low-voltage interlocking devices within the event source zone to the immediate execution queue. For adjacent zones, when the target crossing attribute is traversable, the low-voltage interlocking devices within that adjacent zone are added to the immediate execution queue. When the target crossing attribute is obstruction, the low-voltage interlocking devices within that adjacent zone are not included in the linkage range. When the target crossing attribute is restricted traversability, alarm broadcast-type low-voltage interlocking devices within that adjacent zone are added to the immediate execution queue, and access control-type low-voltage interlocking devices within that adjacent zone are added to the pending confirmation execution queue. Linkage control commands in the pending confirmation execution queue are not executed until external confirmation is obtained.

[0093] Specifically, the three categories of target crossing attributes can originate from the aforementioned different boundary state determination results. For example, a crossing attribute can originate from a situation where the actual opening / closing state is open and consistent with the default attribute, or inconsistent but corrected to crossing. A blocking attribute can originate from a situation where the actual closing state is consistent or corrected to blocking. A restricted crossing attribute can originate from conservative propagation rule processing triggered by abnormal situations such as untrusted states, state jitter, or transitional states. Through this classification, abstract boundary state determination results can be transformed into specific device control strategies.

[0094] It is worth noting that this application indiscriminately categorizes low-voltage linkage devices within the event source zone into the immediate execution queue because fire alarm events occur directly within the event source zone, where the need for personnel evacuation is relatively urgent. Regardless of whether adjacent zones are included in the linkage, alarm, broadcast, and passageway opening actions within the event source zone must be executed with priority to ensure the safety of personnel in that area.

[0095] For the device diversion processing between adjacent zones, alarm broadcasting-type low-voltage linkage devices can include audible and visual alarms, emergency broadcast terminals, and evacuation indicator light controllers, etc., used to issue evacuation warning signals. Access control-type low-voltage linkage devices can include access controllers, electric locks, and turnstile controllers, etc., used to control the opening and closing of physical passages. In scenarios where the target crossing attribute is restricted and traversable, placing alarm broadcasting devices in the immediate execution queue can ensure that personnel in adjacent areas receive fire alarm notifications in a timely manner and prepare for evacuation. At the same time, placing access control devices in the pending confirmation execution queue can avoid directly opening passages when the physical state of the boundary is unclear, thereby preventing the spread of fire or other personnel from accidentally entering dangerous areas.

[0096] At the instruction management level, the immediate execution queue and the pending execution queue can be maintained in different instruction caches in memory. Instructions in the immediate execution queue can have a direct delivery flag, and are directly sent to the delivery channel during polling. Instructions in the pending execution queue can have a restricted execution flag, whose execution enable bit is disabled. This flag is checked periodically, and the corresponding instruction is only moved to the delivery channel after the restricted execution flag is cleared.

[0097] In practical applications, external confirmation signals can take various forms. For example, an external confirmation signal can originate from a trigger signal generated when a fire monitoring center operator clicks the confirmation button on a security management terminal. It can also come from an automatically generated confirmation event after the status of a fire compartment door has returned from an abnormal state to normal closure or normal opening. Furthermore, external confirmation signals can also originate from trigger signals automatically generated according to a preset safety policy after a preset timer expires. This diverse confirmation mechanism minimizes the burden of manual intervention while ensuring safety, and provides a fallback strategy in case of untimely manual response.

[0098] Through the aforementioned queue classification mechanism, the execution authority status of the linkage control commands has been altered. Some commands involving channel opening have been conditionalized, preventing erroneous device triggering in scenarios with uncertain boundary states, while maintaining the priority of alarm actions. This approach allows the linkage propagation range correction to penetrate to the level of action risk classification. When the status of fire compartment doors is unclear, it prevents personnel in adjacent areas from missing alarms due to direct obstruction, and also prevents the erroneous release of access control in areas that should remain closed due to direct passage, achieving a balance between timeliness and security.

[0099] In the aforementioned handling of a single fire alarm event, the status anomaly markers generated for fire compartment doors can resolve the issue of correcting the linkage range for that event. However, in actual operating buildings, some fire compartment doors may have inconsistent physical states with the default crossing attributes recorded in the building space topology due to reasons such as damaged door closers or approval by management to remain permanently open. In this case, the anomaly judgment process is repeatedly triggered every time a fire alarm event occurs, and maintenance personnel repeatedly receive the same review prompts. This increases the maintenance burden and fails to address the root cause of static topology data distortion. To address this, this application further proposes a mechanism for cross-event anomaly accumulation and topology basic data feedback and update.

[0100] This application further proposes to obtain state anomaly information generated during the processing of different fire alarm events targeting the same fire compartment door, which is used to characterize the state anomaly of the fire compartment door when determining cross-zone propagation; to determine the cumulative anomaly information of the fire compartment door based on the multiple obtained state anomaly information; to obtain boundary confirmation information characterizing the current actual state of the fire compartment door when the cumulative anomaly information meets preset conditions; and to update the default crossing attribute pre-configured for the fire compartment door in the building space topology to the crossing attribute corresponding to the boundary confirmation information based on the boundary confirmation information.

[0101] Specifically, in the linkage control process of each fire alarm event, each time a cross-zone propagation determination is made for a fire compartment door, if the actual opening / closing status is found to be inconsistent with the pre-configured default crossing attribute, or if there are unreliable situations such as missing or fluctuating status records, corresponding status anomaly information will be generated. This status anomaly information can be recorded in the event log or a dedicated anomaly tracking data table. It is worth noting that the underlying topology data is not modified directly when inconsistencies are found in a single event because status anomalies in a single event are often sporadic. For example, a fire compartment door might be temporarily blocked by a cart and thus open during an alarm, or the door magnetic sensor might experience a brief interruption causing a jump. Modifying the basic topology based on only one anomaly would contaminate the static spatial data with temporary conditions. Therefore, by acquiring the status anomaly information generated for the same fire compartment door in different events and determining the cumulative anomaly information, sporadic temporary interference can be filtered out.

[0102] Accumulated anomaly information can be reflected in the number or frequency of occurrences of status anomaly information. For example, it can be used to count the number of times a fire compartment door was marked as having a status anomaly in the last five fire alarm events, or to count the total frequency of status anomaly information occurrences within a preset time window. When the accumulated anomaly information meets preset conditions, such as generating status anomaly information in three consecutive events, or accumulating five status anomaly information occurrences within a month, it indicates that the physical normal state of the fire compartment door has reliably and continuously deviated from the static topology record. At this point, a simple single dynamic correction is insufficient to address this long-term deviation, and intervention at the basic data level is required.

[0103] When the accumulated anomaly information meets preset conditions, boundary confirmation information representing the current actual normal state of the fire compartment door will be obtained. There are several ways to obtain this boundary confirmation information. In some implementations, when the accumulated anomaly information reaches a threshold, a maintenance work order can be automatically generated and pushed to the monitoring and management interface. After on-site verification, maintenance personnel input the actual normal state of the door via the confirmation button on the management terminal. For example, confirming that the door has been approved for long-term continuous opening due to management needs, or confirming that the door closer is damaged and cannot be repaired in the short term, the management terminal will generate boundary confirmation information confirming the normal state. In other implementations, if it is detected that the fire compartment door has maintained the same open / closed state for several consecutive days without any state transition, boundary confirmation information representing this state as the actual normal state can also be automatically generated.

[0104] After obtaining boundary confirmation information, the default crossing attribute pre-configured for the fire compartment door in the building space topology will be updated to the crossing attribute corresponding to the boundary confirmation information. Specifically, if the boundary confirmation information indicates that the door is normally open for extended periods, the update interface of the spatial information database will be called to change the default crossing attribute field of the door node from blocking to crossing, and the topology display in the digital twin platform will be updated synchronously. At the same time, the accumulated abnormal information corresponding to the fire compartment door will be cleared or reset.

[0105] Through this cross-event feedback update mechanism, the building space topology can adaptively evolve as the actual physical environment changes. In subsequent fire alarm events, when the same fire compartment door is involved again, cross-zone propagation will be determined directly based on the updated default cross-domain attribute, thus avoiding repeated triggering of abnormal handling branches and conservative propagation rules due to the same long-term distortion problem. This not only reduces the fatigue of maintenance personnel when facing repeated alarms and reduces the burden of review, but also allows the basic data of linkage control to gradually approach the actual physical state, improving the accuracy and stability of overall long-term operation.

[0106] When a door is in an unstable state transition process, although a stable state has not yet been achieved, high-priority fire alarm events require emergency equipment in the source zone and some adjacent zones to act as soon as possible. At this time, the cross-zone propagation determination can only be based on a temporary judgment made in the unstable state. This temporary judgment may be inconsistent with the stable state judgment obtained later through supplementary observation. How to manage this inconsistency becomes a problem faced in transition scenarios. In response, this application proposes a corresponding version management and instruction update mechanism.

[0107] Furthermore, in some priority methods, when it is determined that the fire compartment door is in an unstable state switching process at a corresponding time, the method further includes: determining a first crossing attribute based on the state during the state switching process, and generating an initial linkage control command based on the first crossing attribute; after taking the stable state during the supplementary time period as the actual opening and closing situation, determining a second crossing attribute based on the stable state; when the first crossing attribute and the second crossing attribute are inconsistent, updating the commands that have not yet been executed in the initial linkage control command based on the second crossing attribute, and keeping the high-priority commands that have been executed in the initial linkage control command unchanged.

[0108] When a fire compartment door is in an unstable state, such as transitional open or transitional closed, waiting for it to stabilize before deciding on the linkage action will cause a delay in evacuation alarms. If the transient state is directly judged and all adjacent compartment commands are issued, some commands may be incorrect due to subsequent state changes. Therefore, the first crossing attribute can be determined based on the state during the transition. For example, if the door is transitioning from closed to open and has not yet stabilized, the first crossing attribute can be temporarily determined as "passable" based on the open state. If it is transitioning from open to closed, the first crossing attribute can be temporarily determined as "blocking" based on the closed state. When the direction of the state transition is unclear, a more conservative blocking attribute can be chosen as the first crossing attribute based on event priority.

[0109] When generating initial linkage control commands based on the first crossing attribute, action grading can be performed. Commands for fire-fighting linkage equipment within the event source zone can be issued and executed immediately. For adjacent zones, if the first crossing attribute is "crossable," commands for audible and visual alarms and emergency broadcast terminals can be issued immediately, and access control release commands can be marked as pending confirmation. If the first crossing attribute is "blocking," commands for adjacent zone equipment can be temporarily withheld. In subsequent processing, executed commands and unexecuted commands can be distinguished by device execution acknowledgment signals, command transmission status bits, or a preset command execution mapping table.

[0110] High-priority commands can include commands to activate audible and visual alarms and to enable emergency broadcasts. Once these commands are executed, stopping them midway could lead to on-site personnel misinterpreting the danger as having passed. Therefore, maintaining their execution status prevents reversal and avoids on-site confusion and misguidance. When the second span attribute differs from the first span attribute, commands that have not yet been executed can be added, canceled, or escalated. For example, commands can be issued to adjacent zone devices that were not originally included, commands in the pending confirmation queue can be canceled, or pending confirmation commands can be converted to immediate execution.

[0111] Taking a fire compartment door that is in the opening transition process when an event is triggered as an example, the initial determination of the first crossing attribute is "blocking," and a command is generated accordingly. However, during the supplementary observation period, the door stabilizes in the open state, and the second crossing attribute is corrected to "passable." At this time, the previously unincluded audible and visual alarm commands from adjacent compartments can be reissued, while the previously executed commands from the source compartment remain unchanged. In this way, the final set of issued linkage commands is consistent with the actual stable passage state of the door, ensuring safety in terms of timing and achieving logical consistency.

[0112] This application also proposes a low-voltage building automation system equipment linkage control system for performing the method steps described above, including:

[0113] The event trigger information acquisition module is used to acquire event trigger information of fire alarm events and determine the event source partition and the adjacent partitions adjacent to the event source partition based on the event trigger information.

[0114] The actual opening and closing status determination module is used to obtain the status records of the fire compartment doors located between the event source zone and the adjacent zone within a preset time period before and after the time corresponding to the event trigger information, and to determine the actual opening and closing status of the fire compartment doors at the time corresponding to the event trigger information based on the status records.

[0115] The target crossing attribute determination module is used to compare the actual opening and closing status with the default crossing attribute pre-configured for fire compartment doors in the building space topology. When the actual opening and closing status is inconsistent with the default crossing attribute, the actual opening and closing status is used as the target crossing attribute. The target crossing attribute is used as the basis for determining whether to issue linkage control commands to adjacent compartments.

[0116] Through the above scheme, during the linkage control of fire alarm events, each module can collaboratively obtain the actual opening and closing status of the fire compartment doors. When the status is inconsistent with the default crossing attribute pre-configured in the topology, the actual opening and closing status is used as the target crossing attribute for cross-zone propagation determination. This reduces the deviation in linkage range caused by the mismatch between static topology and physical boundary state, and improves the consistency between the linkage control of weak current equipment and the real scene.

[0117] In some specific implementations, refer to Figure 2 The workflow of the low-voltage building automation system's equipment linkage control system is as follows:

[0118] The event trigger information acquisition module receives fire alarm event trigger information and determines the zone and adjacent zones to identify the event source zone, adjacent zones, and the fire compartment door located between them;

[0119] The actual opening and closing status determination module combines the status records of the fire compartment door within the preset time period before and after the opening and closing. It determines the actual opening and closing status by performing operations such as state time description, stable state determination, handling unreliable or missing state switching situations, and supplementing state record acquisition.

[0120] The target crossing attribute determination module receives the actual opening and closing status, and based on the default crossing attribute in the building space topology, performs attribute comparison, applies conservative propagation rules, and updates abnormal accumulation information in sequence within the module, thereby determining whether the target crossing attribute is traversable, blocked, or restricted traversable.

[0121] Finally, based on the target crossing attribute, the linkage control command generation and issuance stage is entered. When the attribute is traversable, the command is generated normally; when the attribute is blocked, it is not included in the linkage range; when the attribute is restricted traversable, weak current linkage devices such as broadcasting are assigned to the immediate execution queue, and weak current linkage devices such as access control are assigned to the pending confirmation execution queue. Finally, based on the immediate execution queue and the pending confirmation execution queue, the corresponding linkage control command is issued to the adjacent partition.

[0122] The above description is merely an embodiment of this application and is not intended to limit the scope of protection of this application. Various modifications and variations can be made to this application by those skilled in the art. All modifications, equivalent substitutions, and improvements made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A method for linkage control of equipment in a low-voltage building automation system, characterized in that, include: Obtain event trigger information for fire alarm events, and determine the event source partition and adjacent partitions adjacent to the event source partition based on the event trigger information; Obtain the status record of the fire compartment door located between the event source partition and the adjacent partition within a preset time period before and after the time corresponding to the event trigger information, and determine the actual opening and closing status of the fire compartment door at the time corresponding to the event trigger information based on the status record; The actual opening and closing status is compared with the default crossing attribute pre-configured for the fire compartment door in the building space topology. When the actual opening and closing status is inconsistent with the default crossing attribute, the actual opening and closing status is taken as the target crossing attribute. The target crossing attribute is used as the basis for determining whether to issue a linkage control command to the adjacent compartment.

2. The method for linkage control of equipment in a low-voltage building automation system according to claim 1, characterized in that, The step of determining the actual opening and closing status of the fire compartment door based on the status record at the time corresponding to the event trigger information includes: Based on the acquisition time of the state record, organize the state values ​​in the state record to obtain a state time description that describes the state change over time. Based on the continuous maintenance of the state value in the state-time description, the stable state at the time corresponding to the event triggering information is determined, and the stable state is taken as the actual opening and closing state.

3. The method for linkage control of equipment in a low-voltage building automation system according to claim 2, characterized in that, The step of determining the stable state at the time corresponding to the event triggering information based on the continuous maintenance of the state values ​​in the state time description includes: When it is determined from the state time description that the fire compartment door is in an unstable state switching process at the corresponding time, the state in the state switching process is not regarded as the stable state. Obtain supplementary status records for the supplementary time period following the corresponding time. Based on the continuous maintenance of the state values ​​in the supplementary state record, a stable state is determined within the supplementary time period, and this stable state is taken as the actual opening and closing state.

4. The method for linkage control of equipment in a low-voltage building automation system according to claim 2, characterized in that, When the state time description indicates that the fire compartment door undergoes multiple state changes within the preset time period and the continuous holding time of each state value does not reach the preset stable time, an unreliable state flag is generated to indicate that the reliable state cannot be determined, and the unreliable state flag is used as the actual opening and closing status. The method further includes: When the actual opening and closing status is marked as an unreliable state, the target crossing attribute is determined according to the pre-configured conservative propagation rules.

5. The method for linkage control of low-voltage building automation system equipment according to claim 2, characterized in that, When the state time description cannot be obtained from the state record, a state missing marker is generated to characterize the missing state record, and the state missing marker is used as the actual opening and closing status. The method further includes: When the actual opening / closing condition is a missing state marker, the target crossing attribute is determined according to the conservative propagation rule.

6. The method according to claim 4 or 5, characterized in that, The determination of the target traversal attribute according to the pre-configured conservative propagation rules includes: When the default crossing attribute of the fire compartment door is blocked, the target crossing attribute is determined to be passable, and a restricted mark is generated. The restricted mark is used to prevent the linkage control command for access control release in the adjacent compartment from being issued before confirmation is obtained. When the default crossing attribute is traversable, the target crossing attribute is determined to be blocked.

7. The method for linkage control of equipment in a low-voltage building automation system according to claim 1, characterized in that, The target crossing attributes include traversable attributes, blocking attributes, and restricted traversable attributes; The method further includes: Add the low-voltage interconnected devices within the event source partition to the immediate execution queue; For the adjacent partitions, when the target crossing attribute is the traversable attribute, the weak current linkage devices in the adjacent partitions are included in the immediate execution queue; When the target crossing attribute is the blocking attribute, the weak current linkage devices in the adjacent partition are not included in the linkage range; When the target crossing attribute is the restricted traversable attribute, the alarm broadcast type low-voltage linkage devices in the adjacent partition are included in the immediate execution queue, and the access control type low-voltage linkage devices in the adjacent partition are included in the pending confirmation execution queue. The linkage control commands in the pending confirmation execution queue are not executed before external confirmation is obtained.

8. The method for linkage control of equipment in a low-voltage building automation system according to claim 1, characterized in that, Also includes: Obtain status anomaly information generated during the processing of different fire alarm events targeting the same fire compartment door, which is used to characterize the status anomaly of the fire compartment door when determining cross-zone propagation; Based on the multiple acquisitions of the aforementioned abnormal status information, the cumulative abnormal information of the fire compartment door is determined; When the accumulated abnormal information meets the preset conditions, boundary confirmation information is obtained to characterize the current actual state of the fire compartment door; Based on the boundary confirmation information, the default crossing attribute pre-configured for the fire compartment door in the building space topology is updated to the crossing attribute corresponding to the boundary confirmation information.

9. The method for linkage control of equipment in a low-voltage building automation system according to claim 3, characterized in that, When it is determined that the fire compartment door is in an unstable state switching process at the corresponding time, the method further includes: The first crossing attribute is determined based on the state during the state switching process, and an initial linkage control command is generated based on the first crossing attribute. After taking the stable state during the supplementary time period as the actual opening and closing situation, the second crossing attribute is determined based on the stable state; When the first span attribute is inconsistent with the second span attribute, the instructions that have not yet been executed in the initial linkage control instruction are updated according to the second span attribute, while the high-priority instructions that have been executed in the initial linkage control instruction remain unchanged.

10. A linkage control system for a low-voltage building automation system, used to execute the method described in any one of claims 1 to 9, characterized in that, include: The event triggering information acquisition module is used to acquire event triggering information of fire alarm events, and determine the event source partition and the adjacent partitions adjacent to the event source partition based on the event triggering information. The actual opening and closing status determination module is used to acquire the status records of the fire compartment door located between the event source partition and the adjacent partition within a preset time period before and after the time corresponding to the event trigger information, and determine the actual opening and closing status of the fire compartment door at the time corresponding to the event trigger information based on the status records. The target crossing attribute determination module is used to compare the actual opening and closing status with the default crossing attribute pre-configured for the fire compartment door in the building space topology. When the actual opening and closing status is inconsistent with the default crossing attribute, the actual opening and closing status is taken as the target crossing attribute. The target crossing attribute is used as the basis for determining whether to issue a linkage control command to the adjacent compartment.

Images