A method and system for linkage timing control of low-voltage fire protection equipment
By determining and maintaining the status of multiple pre-action actions in the linkage control of low-voltage fire protection equipment, and judging the effective conditions of subsequent actions, the output gap problem in the switching of emergency broadcast and background sound sources is solved, and the stability and seamless connection of equipment linkage timing are achieved.
Patent Information
- Application Number
- CN202611611012.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-10-19
- Publication Date
- 2026-11-17
AI Technical Summary
In commercial complexes or intelligent buildings, the switching between emergency broadcasts and background audio sources in the linkage control of low-voltage fire protection equipment presents an output gap problem due to clock inconsistency and equipment execution delay, which is difficult to solve effectively with existing technologies.
By identifying multiple pre-actions, at least one of which can be completed in advance and maintain its state, and another pre-action with a waiting period, it is determined whether the subsequent action can take effect within the maintenance period and the waiting period. If the determination result is that it can take effect, the other pre-action is authorized to start, ensuring that the device state is maintained until the subsequent action takes effect.
It reduces the connection time consumed by waiting for other devices, improves the stability of device linkage timing, avoids output blanks, and ensures smooth emergency broadcasting and background sound source switching.
Smart Images

Figure CN123113635A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of linkage control technology for fire protection low-voltage electrical equipment, and more specifically, to a method and system for linkage timing control of low-voltage fire protection equipment. Background Technology
[0002] In commercial complexes or intelligent buildings, background audio, emergency broadcasting, and zoned audio routing equipment are managed by control nodes located in different areas. After a fire incident is confirmed by upstream rules, the linkage control module organizes equipment actions according to the incident area. In scenarios where background audio sources and emergency broadcasting are controlled by different output paths and there is no automatic switching device to prevent simultaneous output of both, the background audio source should be turned off first, then the emergency broadcasting should be activated, and the time without output between the two should be limited.
[0003] One coordinated approach involves issuing action plans in advance, which are then executed by each control node under a unified time reference. The coordinated control module reserves time intervals between actions, assuming that the background noise source has been turned off before the emergency broadcast begins. This method relies on all nodes maintaining a consistent understanding of the planned time and on the equipment completing the actions within the reserved time. When the task being executed directly uses a calibrable clock, and each node suddenly adjusts its clock reading sequentially, the actual execution position corresponding to the planned time may change, causing subsequent actions to complete earlier than preceding actions.
[0004] To ensure that subsequent actions are executed based on the actual status of the preceding devices, completion feedback conditions can be set. However, in addition to requiring background noise to be turned off, emergency broadcasts may also require a separate routing device to connect to the target zone. When each preceding action proceeds independently and subsequent actions wait for all conditions to be met, the earlier completed background noise shutdown action will begin to consume the allowed downtime. If the routing is only ready subsequently, even if the broadcast starts according to the actual feedback, it may exceed the allowed connection time.
[0005] For example, if the background audio source is turned off at a relative time of 100 milliseconds, allowing a 50-millisecond blank period, but the target partition route is not ready until 170 milliseconds, then the conditions for complete playback are not met before 150 milliseconds, and the allowed blank period has been exceeded after 170 milliseconds. This problem cannot be eliminated simply by improving clock consistency or adding completion message verification, because the effective time of each precondition does not form a common interval that can be used by subsequent actions.
[0006] The above problems urgently need to be addressed. Summary of the Invention
[0007] The purpose of this application is to provide a method and system for controlling the linkage timing of low-voltage fire protection equipment, which has the advantages of reducing the connection time consumption caused by waiting for other equipment and improving the stability of equipment linkage timing.
[0008] First, this application provides a method for the linkage timing control of low-voltage fire protection equipment, the technical solution of which is as follows:
[0009] A method for sequential control of linkage of low-voltage fire protection equipment, comprising:
[0010] Identify multiple preceding actions that jointly constrain the same subsequent action, wherein at least one preceding action is a preceding action that can be completed ahead of time and maintain its completed state, and at least one preceding action is another preceding action that has an allowed waiting period after completion.
[0011] Perform the pre-execution actions that can be completed in advance, and maintain the resulting device state until the subsequent actions take effect;
[0012] Based on the retention period of the device status, the allowable waiting period after the completion of the other pre-action, and the expected effective time of the subsequent action, determine whether the subsequent action can take effect within the retention period and the allowable waiting period;
[0013] If the determination result is that it can take effect, the other pre-action is authorized to start, so that the allowed waiting period is opened after the subsequent action has the connection conditions.
[0014] Furthermore, the step of determining multiple preceding actions that jointly constrain the same subsequent action includes:
[0015] Based on the execution order requirements of each pre-action and its impact on the device output, the pre-action that does not require the completion of the other pre-action as a prerequisite for execution, does not trigger the device output corresponding to the subsequent action when executed in advance, and can maintain the completed state, is determined as the pre-action that can be completed in advance.
[0016] The other pre-action and its corresponding allowed waiting period are determined based on the maximum allowable interval between the completion of the pre-action and the effective date of the subsequent action.
[0017] Furthermore, maintaining the device state formed by the pre-completion actions until the subsequent actions take effect includes:
[0018] After the preliminary actions that can be completed in advance are completed, the resulting device state, the resources required to maintain the device state, and the hold deadline are determined, and hold information associated with the device state, the resources, and the hold deadline is generated;
[0019] Before the retention deadline, the resources are reserved for the subsequent action, and other tasks are restricted from reconfiguring the resources, so that the device state is maintained until the subsequent action takes effect.
[0020] Furthermore, the step of determining whether the subsequent action can take effect within the retention period and the allowed waiting period, and authorizing the initiation of the other preceding action when the determination result is that it can take effect, includes:
[0021] Based on the proposed start schedule and execution time range of the other pre-action, determine the expected completion time range of the other pre-action, and add the earliest moment of the expected completion time range to the maximum allowable waiting time to obtain the waiting deadline.
[0022] The earlier of the waiting deadline and the holding deadline is determined as the common deadline.
[0023] Based on the planned trigger time of the subsequent action, the latest completion time of each preceding action, the maximum time for completing information transmission, and the maximum execution time of the subsequent action, the latest effective time of the subsequent action is determined, and the latest effective time is used as the expected effective time.
[0024] Only when the latest effective time is not later than the common deadline time is the judgment result determined to be effective, and the other pre-action is authorized to start according to the proposed start-up arrangement, so that the allowed waiting period after the completion of the other pre-action and the retention period of the device state together cover the effective time of the subsequent action.
[0025] Furthermore, the method also includes:
[0026] The retention information, the validity period of the authorization for the other preceding action, the planned trigger time of the subsequent action, and the common deadline time are associated as the same joint execution record and sent to the control node that executes the subsequent action;
[0027] After the control node completes the execution preparation for the subsequent actions, saves and applies the joint execution record, and promises to maintain the execution preparation state, it returns preparation confirmation information.
[0028] Receiving the preparation confirmation information will be an additional condition for issuing the launch authorization.
[0029] Furthermore, the method also includes:
[0030] Establish a task-specific conversion relationship between global time and local continuous count value for the control nodes participating in this linkage, and determine the action trigger position and deadline position of this linkage based on the task-specific conversion relationship.
[0031] During this coordinated execution, the task-specific conversion relationship remains unchanged. This task-specific conversion relationship is used to interpret the completion time of the preceding actions and determine whether each deadline has expired, so that the global time synchronization during operation does not change the correspondence between the action trigger position, deadline position, and completion time of this coordinated action.
[0032] Furthermore, the method also includes:
[0033] The control node that executes the other pre-action performs the other pre-action according to the start authorization, generates completion information containing the actual completion time after the other pre-action is actually completed, and maintains the device state formed by the other pre-action.
[0034] After the control node executing the subsequent action arrives at the planned trigger position of this linkage and obtains the completion information and the valid holding information, it determines the actual waiting deadline based on the actual completion time.
[0035] The current time is determined by the task-specific conversion relationship. The subsequent action is executed only if the maximum time required for the subsequent action to take effect from the current time is not greater than the remaining time from the current time to the actual waiting deadline and the holding deadline, respectively.
[0036] Further, the step of generating completion information containing the actual completion time after the other preceding action is actually completed, and maintaining the device state formed by the other preceding action, includes:
[0037] Obtain the device status feedback and controlled output signal corresponding to the other pre-action, and determine whether the device status feedback and the controlled output signal together satisfy the completion condition of the other pre-action;
[0038] After the completion conditions are met for a predetermined confirmation period, the start time of the continuous satisfaction of the completion conditions is determined as the actual completion time, and completion information containing the actual completion time is generated.
[0039] Maintain the device state corresponding to the completion condition, and refuse to allow ordinary control tasks to cancel the device state.
[0040] Furthermore, the method also includes:
[0041] Before issuing the start authorization, check whether the maintenance information, resource usage relationship, proposed start arrangement and plan version associated with the joint execution record have changed;
[0042] When changes occur, the original joint execution record is invalidated and the issuance of start authorization based on the original joint execution record is stopped. The common cutoff time and the latest effective time of the subsequent actions are re-determined according to the changed conditions.
[0043] Once the condition that the latest effective time is no later than the common deadline is met again, and the control node executing the subsequent action returns a preparation confirmation message to the updated joint execution record, the start authorization is issued.
[0044] This application also provides a low-voltage fire protection equipment linkage timing control system for executing the above method, including:
[0045] The linkage timing control module is used for:
[0046] Identify multiple preceding actions that jointly constrain the same subsequent action, wherein at least one preceding action is a preceding action that can be completed ahead of time and maintain its completed state, and at least one preceding action is another preceding action that has an allowed waiting period after completion.
[0047] Perform the pre-execution actions that can be completed in advance, and maintain the resulting device state until the subsequent actions take effect;
[0048] Based on the retention period of the device status, the allowable waiting period after the completion of the other pre-action, and the expected effective time of the subsequent action, determine whether the subsequent action can take effect within the retention period and the allowable waiting period;
[0049] If the determination result is that it can take effect, the other pre-action is authorized to start, so that the allowed waiting period is opened after the subsequent action has the connection conditions.
[0050] As can be seen from the above, this application identifies two types of pre-actions that jointly constrain the same subsequent action. It first executes the pre-action that can be completed ahead of time and maintains the resulting device state. Then, based on the two time limits and the expected effective time of the subsequent action, it determines whether the continuation is feasible and authorizes the initiation of another pre-action accordingly. The state maintenance spans the time-based judgment, initiation authorization, and subsequent execution process, ensuring that the limited waiting period initiated after the completion of the other pre-action can be used for the continuation of the subsequent action. This reduces the connection time consumed by waiting for other devices and improves the stability of the device linkage sequence. Attached Figure Description
[0051] Figure 1 This is a flowchart of the linkage timing control method for low-voltage fire protection equipment proposed in this application.
[0052] Figure 2 This is a schematic diagram illustrating the effective time relationship of each precondition before and after adjustment in the embodiments of this application.
[0053] Figure 3 This is a logic diagram in this application embodiment where the latest effective time is used as the expected effective time for judgment and authorization.
[0054] Figure 4 This is a logic diagram showing how subsequent actions are executed based on task timing, previous state, and actual remaining time in the embodiments of this application.
[0055] Figure 5 This is a comparison diagram of the actual action timing of the two triggering methods before and after the global time synchronization jump in the embodiments of this application.
[0056] Figure 6 This is a flowchart illustrating the execution process of recording from preparation and authorization to completion, incorporating information retention in this embodiment of the application.
[0057] Figure 7 This is a logical relationship diagram of time information, action plan, start authorization, hold information, preparation confirmation information, completion information and device feedback in the embodiments of this application. Detailed Implementation
[0058] The technical solutions of this application will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of this application, and not all embodiments. The components of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.
[0059] It should be noted that similar reference numerals and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. Furthermore, in the description of this application, the terms "first," "second," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.
[0060] This application provides a method for timing control of linkage of low-voltage fire protection equipment. (Refer to...) Figure 1 The method includes the following steps:
[0061] Identify multiple preceding actions that jointly constrain the same subsequent action, wherein at least one preceding action is a preceding action that can be completed ahead of time and maintain its completed state, and at least one preceding action is another preceding action that has an allowed waiting period after completion.
[0062] Execute preliminary actions that can be completed in advance, and maintain the resulting device state until subsequent actions take effect;
[0063] Based on the retention period of the equipment status, the allowable waiting period after the completion of another preceding action, and the expected effective time of the subsequent action, determine whether the subsequent action can take effect within the retention period and the allowable waiting period;
[0064] If the determination result is that it can take effect, another preceding action is authorized to start, so that the allowed waiting period can be opened after the subsequent action has the connection conditions.
[0065] The state maintenance after the completion of the preliminary actions is a continuous process: once the preliminary actions that can be completed in advance are completed and the device state maintenance is established, time judgment and start authorization can be carried out; the device state is maintained continuously during the judgment, authorization, and subsequent execution until the subsequent actions take effect. Time judgment is not contingent on the end of state maintenance. If the time judgment fails, start authorization is not issued based on the current schedule; the schedule of unexecuted actions can be adjusted and re-judged within the task's validity period; if the state expires or the task deadline expires, exception handling is initiated.
[0066] The requirement that subsequent actions have the necessary conditions for connection means that the equipment state, which can be formed in advance, has been established and maintained, and that, based on time judgment, the subsequent actions can take effect within the two timeframes after the other preliminary action is completed according to the planned schedule. This does not mean that the other preliminary action was completed before authorization. The allowable waiting period still begins when the other preliminary action is actually completed. The preparation confirmation described later is a further limitation on initiating authorization; when using this implementation method, corresponding preparation confirmation information must also be obtained.
[0067] For example, consider the process of switching from background audio to emergency broadcasts in a shopping mall. Under normal circumstances, the background audio plays continuously. When a fire is confirmed by upstream rules, the relevant zone needs to start playing emergency broadcasts. During the switch, the background audio should stop first, and then the emergency broadcast should be started, with no excessively long pauses in the output.
[0068] To complete this switch, the emergency broadcast tributary must first be connected to the target partition. Routing preparation here involves establishing this output path. Control node A is responsible for shutting down the background audio source tributary, control node B is responsible for starting the emergency broadcast output, and control node C is responsible for routing preparation. For the emergency broadcast to start outputting, both conditions must be met: the background audio source must be shut down, and the routing must be ready.
[0069] In this example, the two branches are subsequently connected to the mixing or power amplifier equipment, and are independently controlled by different control nodes. The emergency broadcast output is initially turned off. There is no hardware switching device between the devices to automatically prevent the two outputs from being released simultaneously. Therefore, issuing two commands to be executed sequentially does not mean that the devices will necessarily complete the actions in that order; the actual status needs to be confirmed.
[0070] Control node C prepares the route to the target partition, while control node B prepares the local audio buffer and other output conditions; they perform different preparatory tasks. This method begins by receiving confirmed fire events and area information without altering the upstream fire detection and event confirmation rules.
[0071] Of these actions, routing can be configured before the emergency broadcast is output, and as long as the configuration remains available, it can still be used later. Turning off the background audio source is different: once the background audio source stops, the emergency broadcast needs to be resumed within the allowed time. If the background audio source is turned off before the routing is ready, the waiting time for routing will become blank output.
[0072] Therefore, in this example, the routing preparation action is identified as a prerequisite action that can be completed in advance, the background sound source shutdown action is identified as another prerequisite action, and the emergency broadcast initiation action is identified as a subsequent action. First, routing preparation is completed and state is maintained. Then, it is determined whether the emergency broadcast can take effect within the two timeframes, and based on the determination result, the background sound source shutdown action is authorized to be initiated; the routing state is maintained throughout this period.
[0073] Each of the two prerequisites imposes a time limit. The time interval during which the route can remain available after it is prepared is called the hold-up period; the time interval during which the emergency broadcast must start after the background audio source has actually stopped is called the allowable waiting period. Subsequent actions take effect when the device actually reaches the target output state. In this example, the emergency broadcast must actually start outputting within the allowable waiting period, while the background audio source is still off and the route is still available.
[0074] Reference Figure 2 The two time intervals at the top represent the time relationship before the adjustment. 100 to 150 milliseconds is the allowed waiting period after the background sound source shutdown action is completed, and 170 to 370 milliseconds is the period for maintaining the device state formed by the route preparation action. Since the two time intervals do not overlap, the route preparation is not yet complete before 150 milliseconds, and the allowed waiting period has already expired after 170 milliseconds. Therefore, there is no time when the emergency broadcast can take effect while meeting both time requirements.
[0075] This method first allows control node C to complete routing preparation and maintain device status, and then schedules the background sound source to be turned off. Figure 2 The lower section shows the adjusted time relationship, where the device state for route preparation remains from 170 milliseconds to 370 milliseconds, while the background sound source stops at 200 milliseconds, resulting in a corresponding allowable waiting period of 200 to 250 milliseconds. At this point, the two periods form a common valid interval, and the emergency broadcast takes effect at 213 milliseconds, falling within both the allowable waiting period and the route state maintenance period; therefore, both requirements can be met simultaneously.
[0076] This adjustment does not extend the 50-millisecond wait period after the background audio source stops; instead, it makes the 50-millisecond wait period only begin to be calculated once the audio source can be resumed. When the authorization is issued, the background audio source shutdown action has not yet been completed, and the allowed wait period has not yet been enabled. Figure 2 Using a common relative time, the vertical dashed line at 213 milliseconds indicates the effective time of the emergency broadcast activation action, used to check whether this time falls within both time limits.
[0077] Advance preparation must also yield a result that extends to the actual output. If the route is modified by other tasks immediately after preparation, the previous preparation becomes useless. Therefore, it is necessary to maintain the device state established during route preparation and preserve this state until subsequent actions take effect. The linkage control module uses this to determine whether subsequent actions can be initiated within the two timeframes before deciding whether to issue start authorization. If a device malfunctions outside the normal execution path, exception handling should be implemented; infinite waiting should not be recorded as a successful switchover.
[0078] To express the above requirements in terms of timing, the background audio source must not stop later than the emergency broadcast, and the space between the two must not exceed the allowable limit.
[0079]
[0080] in, This refers to the actual moment when the background audio source branch stops its electrical output. This refers to the actual start time of effective emergency broadcast output. This is the maximum permissible waiting time from the completion of the background sound source shutdown action to the activation of the emergency broadcast action. The above time uses a common time base for the same task; the actual stop does not include the time for the indoor acoustic reverberation to completely disappear.
[0081] The limitations imposed by routing preparation must also be met simultaneously. The effective time of the emergency broadcast must fall within both the allowed waiting period after the background sound source is turned off and the routing retention period, that is:
[0082]
[0083] in, To determine when node C actually completes its routing configuration. The duration for which the route state can be maintained after the route preparation actions are completed. This indicates the overlapping portion of two time intervals. The existence of overlapping time is only the basis for scheduling; time must be allowed before authorization to ensure information arrives and control node B actually outputs its data.
[0084] The above relationship does not depend on a shopping mall or any specific routing device. As long as multiple pre-actions jointly constrain the same subsequent action, at least one pre-action can be completed in advance and maintain the device state it forms, and there is another pre-action that has an allowable waiting period between its completion and the activation of the subsequent action, the same arrangement can be adopted. When multiple maintainable device states exist, the subsequent action shall take effect when all these device states are valid; for devices that could originally operate independently and in parallel, there is no need to artificially add sequential requirements between actions. The two types of pre-actions represent different actions and their roles in this arrangement, and do not mean that the other pre-action cannot maintain its completed state.
[0085] For example, sound-light alarms and LED information release terminals can also participate in linkage according to actual action dependencies, but whether it is necessary to wait for broadcasting and which actions can be executed in parallel shall be determined by the actual relationship between the devices. The allowable waiting duration for audio switching here shall not be used as a unified indicator for other terminals. After clarifying this applicable condition, it is first necessary to select which pre-actions can be completed in advance.
[0086] In one embodiment, determining multiple pre-actions that jointly constrain the same subsequent action includes:
[0087] According to the execution sequence requirements between the respective pre-actions and their influence on device output, a pre-action that does not take the completion of another pre-action as its execution prerequisite, whose advance execution will not trigger the device output corresponding to the subsequent action, and whose completed state can be continuously maintained is determined as a pre-action that can be completed in advance;
[0088] According to the maximum allowable interval between the completion of the pre-action and the activation of the subsequent action, the other pre-action and its corresponding allowable waiting period are determined.
[0089] In this example, it is possible to first check whether the routing preparation action can be completed while the background audio source continues to play. If configuring the target partition routing does not require turning off the background audio source first, and the emergency broadcast output function remains off, then configuring the routing in advance will not cause the emergency broadcast to be played prematurely. The control node C can thus complete the routing preparation first, and then keep the configuration and corresponding resources to make this result available until the subsequent output stage. During the check, the linkage control module reads the sequence requirements between actions in the action plan, and verifies the actual influence of the action on the output path.
[0090] On the contrary, if a certain routing switching must disconnect the background audio source first, switching in advance will destroy the original execution sequence requirement; if the switching itself allows an unapproved emergency signal to enter the output path, it also cannot be executed in advance. It can be seen that a long time consumption is not a sufficient reason to execute an action in advance. The action needs to simultaneously meet the conditions of not relying on the completion of another pre-action, not triggering subsequent output in advance, and having a continuously maintainable completed state.
[0091] The choice of another pre-action depends on which action, once completed, initiates a state that cannot be sustained for an extended period. In this example, a blank output will occur after the background sound source stops. Therefore, the linkage control module reads the maximum permissible interval between the background sound source stopping and the emergency broadcast starting, and uses this as the maximum permissible waiting time. The permissible waiting period is calculated from the moment the background sound source actually stops; when authorization is issued or a shutdown command is received, the background sound source may still be outputting, and these moments cannot be used to replace the actual completion time.
[0092] For other equipment combinations, the same selection can be made based on execution sequence requirements, output impact, and state retention capabilities, without needing to limit the equipment model. Once selected, the control nodes for subsequent actions also need to know how long the pre-established equipment state can be maintained; otherwise, it's impossible to determine whether the follow-up can proceed in time. This condition is then transmitted to the control nodes involved in the linkage through retention information.
[0093] In some preferred embodiments, maintaining the device state formed by the preceding action until the subsequent action takes effect includes:
[0094] After the preliminary actions that can be completed in advance are completed, the resulting equipment state, the resources required to maintain the equipment state, and the hold deadline are determined, and the hold information associated with the equipment state, resources, and hold deadline is generated.
[0095] Before the deadline, resources are reserved for subsequent actions, and reconfiguration of resources by other tasks is restricted, so that the device state is maintained until the subsequent actions take effect.
[0096] Having a route ready does not mean it can be used at any time in subsequent actions. After control node C completes the target partition route configuration and confirms it through device status feedback, it also needs to specify which route was retained, which resources were used, and how long it can be retained. To this end, control node C associates the route status identifier, route resource identifier, and retention deadline with this task to form retention information, which is then sent to the linkage control module and control node B.
[0097] For example, if control node C reports that routing is ready, and a regular broadcast task subsequently assigns the same channel to another partition, this historical message will no longer be able to support the current emergency output. To ensure that the hold information always corresponds to a truly usable device state, control node C retains relevant resources during the hold period and refuses to allow conflicting configurations from regular tasks. These resources can be routing channels, connection configurations, or equivalent device resources required to maintain the target device state.
[0098] The hold deadline should be determined based on the device's guaranteed hold capability. If only the completion time is known to be within a range, the guaranteed hold duration should be added to the earliest possible completion time to avoid omitting actual elapsed time. When measuring the hold duration using a local counter, counting rate error must also be considered, as a faster count may result in a shorter actual hold time than expected. Retransmitting the same hold information will not re-acquire a hold duration.
[0099] With a specified deadline, the linkage control module can require the emergency broadcast to take effect before that deadline, and control node C will maintain the route until the actual connection is completed. After the emergency broadcast begins, if the route is still needed, the resource usage right should be transferred to the running phase; the currently playing path should not be disconnected due to preparation for the scheduled end. Next, the available time of the route needs to be combined with the allowed waiting period after the background sound source stops to determine if it is sufficient to accommodate subsequent actions.
[0100] In some specific implementations, time determination and activation authorization include:
[0101] Based on the proposed start schedule and execution time range of another preceding action, determine the expected completion time range of the other preceding action, and add the earliest moment of the expected completion time range to the maximum allowable waiting time to obtain the waiting deadline.
[0102] The earlier of the waiting deadline and the holding deadline is determined as the common deadline.
[0103] Based on the planned trigger time of subsequent actions, the latest completion time of each preceding action, the maximum time for completing information transmission, and the maximum execution time of subsequent actions, the latest effective time of subsequent actions is determined, and this latest effective time is used as the expected effective time of subsequent actions.
[0104] The judgment result is determined to be effective only if the latest effective time is not later than the common deadline. Then, another pre-action is authorized to be started according to the proposed start-up schedule, so that the allowable waiting period started after the completion of the other pre-action and the maintenance period of the equipment status together cover the effective time of the subsequent action.
[0105] Reference Figure 3Before issuing a start authorization, the linkage control module needs to determine when subsequent actions are expected to take effect and when all preconditions expire. This implementation uses the latest effective time, after factoring in the maximum time consumption, as the expected effective time, and the earlier of the two deadlines as the common deadline. Only if the latest effective time is not later than the common deadline is the current schedule considered to be able to continue; when additional conditions such as preparation confirmation are used, the corresponding conditions must be met before authorization is issued. Subsequent actions still require the actual completion of the preconditions as a prerequisite for execution; the completion conditions cannot be omitted simply by comparing deadlines.
[0106] At the time of the judgment, the background noise source was still running, and the actual completion time was unknown. The linkage control module first drafted the start-up schedule, and then determined the estimated completion time range based on the authorized arrival time, the planned trigger location, and the minimum and maximum execution time of the equipment. For completed routing preparation actions, the completion time range was determined based on the completion information and timing errors. The range calculation should include the time required for this preparation and authorization; if the authorization has been delayed, it is necessary to re-check whether the schedule is still applicable.
[0107] When calculating the allowable waiting period before authorization, the estimated completion time range and maximum allowable waiting time of another preceding action under the proposed start schedule are used; at this time, the actual allowable waiting period has not yet started. After authorization is executed, the actual completion time is used to determine the actual waiting deadline. The estimated effective time of subsequent actions is used for pre-authorization judgment, and the actual effective time is used to confirm the equipment execution result; the two are not interchangeable.
[0108] For example, the background sound source shutdown action is expected to complete between 195 and 205 milliseconds, with a maximum allowed wait time of 50 milliseconds. If it actually completes in 195 milliseconds, the allowed wait period will end at 245 milliseconds. Therefore, continuation should be scheduled for 245 milliseconds before authorization. If 205 milliseconds plus 50 milliseconds is used instead, an extra 10 milliseconds will be added, omitting the output blanks that would occur if the background sound source stopped earlier. This is why the wait deadline is calculated from the earliest moment within the expected completion time range.
[0109] Now let's look at the routing side. If the completion time of the routing preparation action is between 169 and 171 milliseconds, and it can be guaranteed to remain for 200 milliseconds, then we add 200 milliseconds to 169 milliseconds, resulting in a hold-off deadline of 369 milliseconds calculated based on the earliest completion time. Emergency broadcasts must comply with both the 245 millisecond and 369 millisecond constraints simultaneously; therefore, the earlier 245 milliseconds is taken as the common deadline. If other device states need to be maintained, then the corresponding deadlines are calculated separately, and the earliest expiring constraint is included.
[0110] The next step is to calculate the latest possible output date of the emergency broadcast. Control node B may be waiting for the planned trigger location to arrive, or it may be waiting for completion information of the preceding actions; both waiting can occur simultaneously. Therefore, the latest possible time is taken between the latest time the planned trigger condition is met, the latest time each preceding action is completed, and the maximum time for transmitting the completion information. This latest time is then added to the maximum time required for control node B's necessary checks, scheduling, and actual output. Directly adding the two parallel waiting times would result in repeated calculations of the same time period.
[0111] The above calculations can be uniformly written as the following formula. The set lists the prerequisite actions for initiating this joint constraint emergency broadcast. First, calculate the latest time when each condition is met, then include the execution time after the conditions are met:
[0112]
[0113] in, This is the latest time when the emergency broadcast activation action will take effect; This is the set of prerequisite actions for the common constraint control node B. This serves as an identifier for the node or its corresponding action, and is checked sequentially during calculation. Each item in the list; Preliminary action The latest possible completion time within the estimated or measured completion time range; This represents the maximum time required for confirmation and completion information to reach control node B after the action is actually completed. To determine the latest time when the triggering conditions for control node B will be met; This determines the maximum time required for node B to complete the remaining checks, scheduling, and output from the check position after all conditions are met to the actual effective date. This indicates taking the maximum value.
[0114]
[0115] in, For a common deadline, It refers to the earliest possible completion time within the same pre-action completion time range. This refers to the allowable waiting time or state maintenance time that can be guaranteed after the action is completed. For control node A, the aforementioned values are taken. For control node C, take the aforementioned... The two durations have different meanings, but both are used to limit the effective execution period of control node B. This indicates taking the minimum value. In this example, the range of the completed control node C is determined by the measured time and error, while the range of the unexecuted control node A is determined by the planned start-up schedule and execution time.
[0116]
[0117] This comparison is based on the latest possible effective date and the earliest possible expiration date, and therefore can serve as a condition for allowing activation, avoiding underestimating the time required or overestimating the available time. Some arrangements may happen to be able to complete during actual operation, but if this condition is not met, it cannot be guaranteed that the follow-up will be in time. If the entire linkage has other response deadline requirements, the following should also be checked:
[0118]
[0119] in, The deadline for tasks determined from the overall event response requirements shall be based on the same time reference as the aforementioned time; preparation time and the time spent on other execution phases shall also be included in the overall schedule.
[0120] Using the above values, assuming that the timing condition of control node B is met no later than 211 milliseconds, the maximum time for control nodes A and C to complete confirmation and information transmission is 10 milliseconds each, and the maximum time for control node B's subsequent processing and output is 3 milliseconds, then the latest effective time is the maximum value of 211, 205 + 10, and 171 + 10 plus 3, which is 218 milliseconds. The linkage control module can only authorize control node A according to the proposed start-up schedule at least 218 milliseconds, no later than 245 milliseconds. Figure 2 A specific operation could be completed by control node C in 170 milliseconds, control node A in 200 milliseconds, and control node B taking effect in 213 milliseconds.
[0121] If the overall deadline for this example is 250 milliseconds, then a maximum effective time of 218 milliseconds also satisfies the overall deadline. This example selects the earliest and latest times within each time range for combined calculations. The completion time of the background sound source shutdown action is set to 195 or 205 milliseconds, the completion time of control node C is set to 169 or 171 milliseconds, and the timing condition of control node B is set to 209 or 211 milliseconds. The transmission time for each of the two completion messages is set to 0 or 10 milliseconds, and the remaining time for control node B is set to 0 or 3 milliseconds. A total of 64 combinations are calculated. The maximum interval between control node A and control node B is 19 milliseconds, and the maximum interval between control node C and control node B is 49 milliseconds. In each combination, no subsequent action completes before the preceding action, and the corresponding allowable waiting period or hold period is exceeded. Zero time in the calculation only indicates that the time cannot be less than zero; it does not mean that the device actually consumes no time. This calculation is for verifying the example, not for actual machine testing, and does not replace the aforementioned time calculation based on the worst-case scenario.
[0122] The maximum latency here refers to the latency that can be guaranteed not to be exceeded under agreed operating conditions, not the average latency, nor the longest latency measured in a single test. The validity of these calculations also depends on whether this maximum latency is included in all stages of the actual process. The time from device status confirmation to arrival at the receiving end may involve sending, allowed retransmissions, queuing, and transmission; all of these times should be included. The execution time of subsequent actions is counted from when conditions are met until the device actually takes effect. Preparing output data in advance, pre-allocating message buffers, and limiting concurrent tasks help determine the maximum latency that can be guaranteed not to be exceeded. Using average latency instead of maximum latency cannot cover situations where messages arrive slowly. The above values are for illustrative purposes only and do not require different devices to use the same parameters.
[0123] In communication implementation, a dedicated high-priority message queue can be set up for linked messages to limit the number of linked tasks running simultaneously, pre-allocate message buffers, and limit the usage of ordinary business processes. However, selecting a certain protocol or increasing thread priority alone is not enough to determine the maximum latency; it is still necessary to calculate based on the allowed number of retransmissions, link load, queuing, and scheduling conditions.
[0124] To further clarify the origin of the waiting time, we can first observe the local segment from when the background noise source is turned off to when the emergency broadcast is initiated. After the background noise source stops, control node B may not have reached the planned trigger time yet, and it may not have received the completion information. We will first calculate the maximum waiting time for the former scenario; if there are other preliminary actions such as routing preparation, the aforementioned common deadline condition must still be met simultaneously.
[0125]
[0126] in, After the background sound source is turned off, there is still a maximum time to wait for the control node B to trigger the plan conditions. and These are the planned trigger times for control node A and control node B, respectively, generally based on... Represents a node The planned trigger time; and These are the maximum conversion and timing errors used by control node A and control node B in this task, respectively, generally expressed as... Represents a node The maximum applicable error during the entire period of use of the task-specific conversion relationship; This refers to the shortest time from triggering control node A to its actual completion. All errors here are calculated as the absolute magnitude of the deviation, expressed in time, and are not less than zero. The same time base is used for all planned times.
[0127]
[0128] in, This refers to the maximum time taken from the actual completion of the background sound source shutdown action to the confirmation of completion and the sending of a message. This represents the maximum time required for the information to be transmitted to control node B. To control the maximum time spent on verification and scheduling after both conditions for node B are met. This represents the maximum time elapsed from initiating an output operation by control node B to the actual output. Since two waiting paths occur in parallel, only the longer one is considered. Here... and The sum corresponds to the location that should be checked. , and The sum corresponds to control node A .
[0129] For example, if control node A and control node B have planned trigger times of 100 and 120 milliseconds respectively, and the maximum error between the two nodes is 1 millisecond each, the shortest execution time for control node A is 5 milliseconds. The maximum times for completing acknowledgment and signaling, transmission, control node B scheduling, and control node B output are 2, 8, 1, and 2 milliseconds respectively. Therefore... The maximum interval is 17 milliseconds, with a maximum action interval of 20 milliseconds and an allowable waiting time of less than 50 milliseconds. To ensure that the runtime deadline check, after factoring in errors, passes within the normal error range, further checks are performed during startup to determine whether to allow the operation to proceed.
[0130]
[0131] The added time here is to allow for estimation errors and performance checks. Using the above values, we determine whether it's permissible to start at 24 milliseconds while the actual action interval still doesn't exceed 20 milliseconds. Control node B doesn't need to wait an extra 4 milliseconds; this 4 milliseconds represents the allowance for handling errors in the arrangement.
[0132] In the combined calculation of the two actions mentioned above, the maximum execution time of control node A is also set to 8 milliseconds, denoted as... This refers to the longest time elapsed from the triggering of control node A to its actual completion. By taking plus or minus 1 millisecond of the timing deviation between control node A and control node B, the execution time of control node A (5 or 8 milliseconds), and the zero and maximum values of the above time parameters, a total of 128 combinations are obtained, resulting in an actual interval of 10 to 20 milliseconds between control node A and control node B. This calculation only checks the above value combinations and cannot be used to conclude that the actual device has achieved the same performance.
[0133] If the expected latest effective time exceeds the common deadline, adjust the arrangement of unexecuted actions while the background sound source is still running, or select another configured linkage path. Adjustments should also adhere to the overall task's response deadline; emergency output should not be continuously delayed to shorten local gaps. After the time calculation is successful, another issue is whether control node B is truly ready for the takeover, which requires confirmation of readiness information.
[0134] In a further embodiment, the authorization process is also subject to preparation confirmation conditions, and the method further includes:
[0135] The information, the validity period of the authorization for another preceding action, the planned trigger time of the subsequent action, and the common expiration time are associated with the same joint execution record and sent to the control node that executes the subsequent action;
[0136] After the control node completes the preparation for the execution of subsequent actions, saves and applies the joint execution record, and promises to maintain the execution preparation state, it returns the preparation confirmation information;
[0137] Receiving a confirmation message is an additional condition for issuing the activation authorization.
[0138] The linkage control module calculates a feasible arrangement, but control node B may still be storing the trigger conditions from the previous version. If the background sound source is turned off at this point, the previous calculations cannot be implemented in actual execution. To avoid this disconnect, the linkage control module stores the current information, the validity period of the authorization for another preceding action, the planned trigger time of subsequent actions, and the common deadline time in the same joint execution record, and associates them with the task number, execution sequence number, and plan version. Control node B thus stores and applies a complete set of corresponding conditions.
[0139] The action plan first determines the participating control nodes and actions based on the event area, specifying the sequence requirements between actions, planned times, waiting times, and overall validity period. Each execution is assigned a task number, execution segment number, and execution sequence number. When the action content changes, a new plan version and plan summary are generated so that control nodes can verify whether they are executing the same arrangement. An execution segment is a set of short actions that require continuous coordination; in this example, it includes route preparation and hold, background audio source shutdown, and emergency broadcast continuation. After one execution segment is completed, the next segment can be accepted without needing to shut down all equipment in the entire building.
[0140] Messages can be organized according to an agreed data structure or communication format. In addition to the aforementioned task number and other identifying information, messages also carry a plan summary, time base version, sending node and node start identifier, action number and preceding action number, task-specific conversion relationship identifier, planned time and local deadline count, and validity period. Completion information includes actual status, event count, and message sequence number; preparation information reports errors and maximum time consumption for each item. The receiving end checks the configured sending source and message integrity, and then verifies the task, plan, and time base identifiers to avoid using messages with correct formats but belonging to another arrangement for this execution.
[0141] After receiving the joint execution record, control node B first checks the task number and other identification information, as well as the resource status. Then, it completes the initial audio buffering, necessary decoding, and output interface preparation, while keeping the output closed at this point. Only after the planned triggering conditions, prerequisite state conditions, and deadline conditions have been saved and applied does it return a preparation confirmation message. Therefore, this message indicates that the continuation can proceed according to the current arrangement, rather than simply indicating that a network message has been received.
[0142] Message interaction can be implemented in the following order. The linkage control module first sends a PREPARE message, control node A checks the closing path, control interface, and feedback interface, and control node B completes buffering, decoding, and output preparation; each control node then uses READY to report the resource preparation results, timing errors, and maximum execution time.
[0143] After the linkage control module confirms that the time base version is the same, the quality is qualified, and the time calculation is passed, it uses ARM to deploy the joint execution record. Control node B saves and applies the timing, prerequisite states, and deadline conditions, and returns ARMED; here, ARMED corresponds to the preparation confirmation information. Only after all necessary subsequent nodes have confirmed, the linkage control module sends START_ENABLE start authorization to control node A. READY indicates that the resources are ready, and ARMED indicates that the execution conditions for this time have been saved and applied. The two are at different stages and cannot replace each other.
[0144] If a timing source switch occurs during preparation, conversion errors exceed limits, or the remaining preparation time is insufficient, the original preparation results cannot be used and resampling, scheduling, and recalculation are required. Each control node should also establish message receiving and action processing channels in advance to avoid opening files, allocating large amounts of memory, or establishing connections only when output is imminent, which could cause the actual time consumption to exceed the previously calculated maximum consumption.
[0145] The linkage control module uses the receipt of the preparation confirmation message as an additional condition for issuing the start authorization. Even if the time calculation has passed, the background sound source shutdown action will not be initiated as long as the joint execution record has not been saved and applied or the execution resources are not ready. After the control node B makes the preparation confirmation, it should maintain the preparation state for the agreed task validity period; the absence of subsequent control messages for a short period does not mean that the preparation can be cancelled on its own. If cancellation is required, it should be coordinated with the linkage control module.
[0146] Thus, the actual execution sequence of the device is still to first shut down the background sound source and then output the emergency broadcast. However, during the preparation phase, the emergency broadcast must first have the capability to resume before the background sound source shutdown action is authorized to start. The authorization itself also has an expiration date and cannot be re-executed after it expires. Next, it must be ensured that the time synchronization during operation does not change the time relationship on which this joint execution record is based.
[0147] In some specific implementations, to ensure that each step uses a consistent task timing basis, the method further includes:
[0148] Establish a task-specific conversion relationship between global time and local continuous count value for the control nodes participating in this linkage, and determine the action trigger position and deadline position for this linkage based on the task-specific conversion relationship;
[0149] During this coordinated execution, the task-specific conversion relationship remains unchanged. This task-specific conversion relationship is used to interpret the completion time of the preceding actions and determine whether each deadline has expired, so that the global time synchronization during operation does not change the correspondence between the action trigger position, deadline position, and completion time of this coordinated action.
[0150] Control nodes need to collectively understand the planned timings, but the global clock may be corrected during operation. For example, if the clock reading suddenly moves forward, a trigger time that has not yet arrived may be displayed as having passed; if it moves backward, the waiting time may be extended again. If the trigger position and deadline judgments directly follow such changes, the previously calculated succession arrangements will be altered.
[0151] To this end, each control node first establishes a task-specific conversion relationship, and then determines the trigger position and deadline position of the action for this linkage based on this relationship, maintaining the task-specific conversion relationship unchanged during the execution of this linkage. In this way, the interpretation of triggering, deadline checks, and completion times can use the same set of timing criteria. In this embodiment, before the routing preparation action begins, the global time and local continuous count value under the same time base version can be obtained, and the task-specific conversion relationship can be saved. The global time is used to align the understanding of time among each control node during preparation, while the local continuous count value continues to count forward during execution. This task consistently uses the conversion parameters saved during preparation to interpret the count value.
[0152] When establishing a task-specific conversion relationship, a global time, the corresponding local continuous count value, and the estimated duration for each count can be recorded simultaneously. Subsequently, for each additional count, the corresponding duration is added to the recorded global time to obtain the time based on the current task's time baseline.
[0153]
[0154] in, For nodes The function for converting the time of this task. The local continuous count value is the input to this function. The global time at the sampling moment. For local counts at the same time, The estimated time for each count, and it must be a positive value; the subscript... This indicates the initial sampling time during the preparation phase, not another node. This function outputs the estimated time based on the current task timeline.
[0155]
[0156] in, For nodes Local action trigger count; the rounding brackets indicate that fractional parts are counted as a single count, preventing premature triggering due to rounding. Scheduled trigger time. It should be within the scope of effective preparation and arrangement; expired plans should be rescheduled, and the trigger position should not be used as the basis for supplementary execution.
[0157] The global time and local count values can be saved simultaneously using hardware. Alternatively, the local count can be read once, followed by the global time, and then the local count can be read again. The time difference between the two count reads will affect the accuracy of the corresponding moment, and this effect should be included in the sampling error.
[0158] For example, each count represents 1 microsecond, the global relative time at sampling is 40 milliseconds, and the local continuous count value is 800,000. To trigger at 120 milliseconds, another 80 milliseconds, or 80,000 counts, are needed, so the local action trigger count is 880,000. Even if the global clock is subsequently adjusted forward by 80 milliseconds, this task will still wait until count 880,000 before triggering. The not-yet-finalized hold deadline can be calculated after the hold information is formed, but the fixed task-specific conversion relationship will still be used.
[0159] This arrangement needs to be maintained throughout the entire time determination process. If only a fixed trigger timer is used, but the new time after synchronization is used to determine whether it has expired upon receiving the completion information, the trigger and the deadline will still use two different sets of criteria. Therefore, the completion count, hold-to-deadline count, and current count of the preceding actions must also be interpreted through the same task-specific conversion relationship. The local counting starting points of different control nodes can be different, as long as the same task time base is used after conversion, and the error is controlled within the allowable range.
[0160] Using fixed conversion parameters does not mean there are no timing errors. Initial time deviation, the smallest time interval that sampling can distinguish, and the accumulated deviation of the counting rate over a period of time all need to be included in the conversion error. This time period should cover preparation, hold, waiting, and execution, and should not only calculate the short time after the action starts. The current task uses fixed parameters, and the new time synchronization result is used by subsequent tasks; when a node restarts, the counter stops, or the validity period of the task-specific conversion relationship expires, the original timing basis becomes invalid and should be handled as an exception. The counting source can be a continuous hardware timer or a timing service with a known maximum error.
[0161] A microsecond-level hardware counter driven by a fixed frequency is extended to a 64-bit continuous value. During task execution, it must not be stopped, reset, or have its frequency changed without authorization; it must continue timing even when entering a low-power state, otherwise entering that state within the task is prohibited. A new node startup identifier is generated upon restart, and the original task-specific conversion relationship is abolished. When using the operating system's continuous timing service, if the timing is corrected by gradually changing the timing speed, its impact should be included in the error; even if the count value only increases and does not decrease, it cannot be concluded that there is no timing error.
[0162]
[0163] in, The maximum value of the initial error of the conversion relationship specific to the task. The maximum error caused by the smallest time interval that can be distinguished by sampling and counting. This represents the maximum value of the relative error of the counting rate. This is the maximum duration from the start of sampling to the last time the task-specific conversion relationship is used. (The aforementioned...) Based on this, the stages of preparation, maintenance, waiting, execution, and feedback are determined and covered; time amounts are expressed in units that can be converted uniformly. This is a unitless scale value.
[0164] For example, the initial error is 0.80 milliseconds, the error in sampling and converting time to count values is 0.15 milliseconds, and the counting rate error is 100 ppm. The task-specific conversion relationship uses a maximum of 500 milliseconds. 100 ppm means that a rate deviation of at most 100 time units accumulates per million time units. Therefore, the error increase within 500 milliseconds is 0.05 milliseconds, totaling 1.00 milliseconds. The actual maximum error value used should be determined in conjunction with the counting source, sampling method, and temperature range.
[0165] When only observing the local components of control node A and control node B, if control node A triggers at 100 milliseconds and stops at 105 milliseconds, control node B will receive the completion information no later than 115 milliseconds. Even if control node B experiences a global clock jump forward by 80 milliseconds at the actual 60 milliseconds, its local trigger position at 120 milliseconds remains unchanged. After waiting to this position, control node B performs a 1-millisecond scheduling and a 2-millisecond output start, taking effect at 123 milliseconds, with a local interval of 18 milliseconds. Backtracking does not extend this waiting period again; in multi-precedence scenarios, valid hold information from control node C must also be obtained simultaneously.
[0166] Reference Figure 5 The upper timeline represents the case where subsequent actions are triggered directly based on the correctable global clock, while the lower timeline represents the case where timing is based on the task-specific conversion relationship fixed for this task, combined with the completion information of the preceding actions. Both timelines use independent observation times to represent the actual location of the action. In the case shown in the upper timeline, control node B undergoes a time synchronization at 60 milliseconds, where the global clock reading jumps from 60 milliseconds to 140 milliseconds. Since the corrected clock reading has already exceeded the planned trigger time of 120 milliseconds, control node B outputs at 62 milliseconds, 2 milliseconds later. At this time, control node A does not complete the background sound source cessation until 105 milliseconds, resulting in overlapping outputs from both channels. In the case shown in the lower timeline, this task still determines the trigger position based on the task-specific conversion relationship determined before the time synchronization and waits for the actual completion information from control node A. Therefore, control node B outputs at 123 milliseconds.
[0167] The former arrangement, where the clock is not adjusted, and control node A executes for 5 milliseconds while control node B executes for 2 milliseconds, could originally create a 17-millisecond interval. This comparison is used to illustrate whether time synchronization will cause subsequent actions to be executed prematurely before the preceding actions are completed. It does not calculate the performance improvement ratio based on different scheduling details, nor does it generalize this problem of premature execution as a common problem of all fire protection systems.
[0168] This example illustrates that each arrangement plays a different role. Fixed task-specific conversion relationships ensure that time synchronization jumps do not alter the current time schedule; completion information allows subsequent actions to wait until the preceding actions are actually completed; pre-authorization calculations based on maximum time consumption and expiration checks during execution constrain waiting to exceed the deadline. Maintaining multiple preceding actions and determining a common deadline also requires these necessary conditions to be valid simultaneously within the same timeframe. Only by coordinating these relationships can the preparatory arrangements be carried over to the actual output.
[0169] In some preferred embodiments, after issuing the launch authorization, the method further includes the following actual execution and time-limit calculation process:
[0170] The control node that performs another pre-action executes the other pre-action according to the startup authorization, generates completion information containing the actual completion time after the other pre-action is actually completed, and maintains the device state formed by the other pre-action.
[0171] After the control node that executes the subsequent actions arrives at the planned trigger position of this linkage and obtains completion information and valid maintenance information, it determines the actual waiting deadline based on the actual completion time.
[0172] The current time is determined by a task-specific conversion relationship. Subsequent actions are executed only if the maximum time required for the subsequent actions to take effect from the current time is not greater than the remaining time from the current time to the actual waiting deadline and the remaining time to the holding deadline, respectively.
[0173] Before authorization, all pre-emptive actions that could be completed in advance have been finished and the resulting device state has been maintained. However, another pre-emptive action has not yet been executed, and the decision can only be made based on the estimated completion time range of that other pre-emptive action. At this point, the exact time when the background sound source will stop can be confirmed via feedback, and control node B should recalculate the remaining time accordingly. Control node A only executes the background sound source shutdown action when the authorization is valid and the local trigger position is reached. After actual completion, it records the completion time, sends a completion message, and maintains the shutdown state. The completion message is also associated with the task number, execution sequence number, plan version, action identifier, and node start identifier to prevent information left over from the previous shutdown from being used in this emergency broadcast.
[0174] Completion information can be sent directly to control node B as a DONE message and copied to the linkage control module, or it can be forwarded by the linkage control module. When using the forwarding method, the additional queuing, processing, and transmission time must be included in the estimated time consumption. Messages may also arrive repeatedly. Therefore, control node B identifies and excludes duplicate messages by action number and execution sequence number, allowing re-acknowledgment of received messages, but not repeatedly driving the device. Control commands use explicit state instructions such as "set to off" and "set to on" to ensure that the device maintains the same state after the same command is executed multiple times; if the command indicates a switch, repeated reception may actually turn the device that was just turned off back on.
[0175] Reference Figure 4 Control node B records whether the planned trigger position has been reached, and whether completion information and valid hold information have been obtained. If the message arrives first, it waits for the timing condition; if the timing condition is met first, it waits for the preceding information. After both conditions are met, the actual waiting deadline is obtained by adding the maximum allowed waiting time to the actual completion time of the background sound source closing action.
[0176] Subsequently, control node B determines the current time using a fixed task-specific conversion relationship, and calculates how much time remains until the actual waiting deadline and the hold deadline. In this way, the planned triggering and the remaining time check use the same timing basis, while the equipment's ability to continue is confirmed by the actual completion and hold information.
[0177] For example, if the background audio source actually stops at 200 milliseconds, and the maximum allowed waiting time is 50 milliseconds, then the actual waiting deadline is 250 milliseconds. The routing's hold deadline, calculated based on the earliest completion time, is 369 milliseconds. When control node B checks at 210 milliseconds, it has 40 milliseconds and 159 milliseconds remaining until the two deadlines, respectively. If the maximum time from the end of the check to the actual output is 3 milliseconds, then both remaining times are sufficient before continuing execution. This 3 milliseconds should include necessary scheduling and device startup; after the check passes, it cannot re-enter a queuing process where the maximum waiting time cannot be guaranteed.
[0178] When there is an estimation error between the current time and the completion time, the possible timing error should be included in the calculation to avoid overestimating the remaining time. The difference between the current estimated time and the estimated completion time of the background sound source shutdown action, plus the maximum time error between the two and the maximum remaining time of control node B, can be compared with the maximum allowable waiting time; a corresponding hold period check should also be performed on control node C. To ensure that arrangements within the normal error range pass the check, before startup, the maximum errors of each preceding action and control node B can be added together, and then a time reserve of twice the result can be made.
[0179] For any preceding action, the runtime deadline check, after accounting for errors, can be expressed as:
[0180]
[0181] in, The aforementioned conversion function takes the form of values at control node B. The local consecutive count read when control node B performs the current check. Preliminary action The local continuous count corresponding to the actual completed event. Both conversions use the fixed parameters of this task; the new parameters after time synchronization cannot replace either conversion. Any errors that may occur at the time of data collection completion are included in the corresponding... This formula is applied term by term. The preceding actions in the process; a guaranteed hold duration is used for control node C, while adhering to the hold end time calculated based on the earliest completion time given in the hold information.
[0182] In conjunction with this inspection, time should be allocated for handling errors for each preliminary action before authorization:
[0183]
[0184] This formula retains the meanings of the symbols mentioned above: the estimated elapsed time is at most more than the sum of the maximum errors of both sides compared to the actual value, and the operational checks add the same error compensation, therefore, a two-fold sum is reserved. The errors of each preceding action are not calculated separately at the same time, and the error of a single node cannot be directly used to represent all nodes.
[0185] When the maximum time error of each node is 1 millisecond, the aforementioned reserve time is 4 milliseconds. In the example where the latest effective time is 218 milliseconds, determining whether startup is allowed at 222 milliseconds is still earlier than the common cutoff of 245 milliseconds. This does not require control node B to wait an additional 4 milliseconds, but rather to reserve margin for estimating deviations and performing checks. If any state is invalid or the remaining time is insufficient, expired normal actions are no longer allowed to execute; the exception should be logged and the configured fault handling should be performed.
[0186] Reference Figure 6This diagram, combined with the holding information of control node C, illustrates the execution process from the background sound source shutdown action to the emergency broadcast activation action. Control node C completes route preparation and establishes a state holding mechanism. The linkage control module obtains the holding information, preparation results, and maximum time consumption. After calculation using the common deadline and latest effective time, it saves and applies the joint execution record. Only after obtaining preparation confirmation information and confirming that the authorization basis is still valid does it issue the activation authorization. The route state is continuously maintained during subsequent judgments, authorizations, and executions. During execution, the task deadline and state validity are checked first. If the timing condition or prerequisite state condition is not met but the task is still valid, it continues to wait and re-check. When the task deadline expires or the state becomes invalid, it enters exception handling. After all conditions are met, the remaining time must be checked, and the emergency broadcast activation action is only executed if sufficient time is available. Control node A sequentially goes through the stages of prepared, authorized, shutting down, and completed and remaining shut down; control node B sequentially goes through the stages of prepared, waiting for conditions, outputting execution, and completed. The timing interrupt and feedback reception record events separately. A task that processes events sequentially checks the status and changes it to "in execution." The process of checking and modifying the status is not allowed to be interrupted by other processing procedures. Output is only driven after this process is complete. Control node B returns the effective time and result after meeting the conditions for determining the actual output. The upper layer only registers success upon receiving this result.
[0187] After this action combination is completed, only temporary resources used for preparation and message coordination are released, maintaining the necessary continuous fire alarm linkage status. Background audio source restoration, emergency broadcast cessation, and route restoration require subsequent control authorization and do not occur automatically upon the end of this segment. The new time synchronization parameters and readjusted action arrangements are used in the next execution segment; normal version updates do not rewrite segments that have already been started.
[0188] Another practical problem to avoid is that when the timing event and the completion message arrive almost simultaneously, the two processing processes might each find that the conditions are met, thus repeatedly starting the output. Both types of events can be assigned to the same sequential event processing task. After confirming the conditions, the state of control node B should be changed to "in execution" before initiating the output. The execution result should be confirmed by actual output feedback; issuing the start command should not be directly recorded as success. Whether the completion message truly represents that the background sound source has stopped is ensured by the device status detection below.
[0189] In some specific implementations, the step of generating completion information containing the actual completion time after another preceding action is actually completed, and maintaining the device state formed by that other preceding action, includes:
[0190] Obtain the device status feedback and controlled output signal corresponding to another pre-action, and determine whether the device status feedback and controlled output signal together meet the completion conditions of the other pre-action;
[0191] After the completion conditions are met for a predetermined confirmation period, the start time of the continued satisfaction of the completion conditions is determined as the actual completion time, and completion information containing the actual completion time is generated.
[0192] Maintain the device state corresponding to the completion condition and refuse to allow ordinary control tasks to cancel the device state.
[0193] Determining whether a background sound source is off cannot be done solely by listening for the presence or absence of sound. Audio may inherently contain brief periods of silence, and even if the path remains open, no noticeable output may be detected. Similarly, receiving a shutdown command does not necessarily mean the device has completed shutdown. Therefore, control node A simultaneously reads both the actual gating status feedback and the output signal from the branch after the gating. Only when the gating is in the closed state and the output signal strength is below the threshold determined by the interface noise and the effective audio signal strength is both shutdown completion conditions considered met.
[0194] Gating is a control component used to connect or disconnect a signal path. In this example, the gating controller is placed before the background audio source branch enters the mixer or power amplifier. The actual gating status feedback and the signal detection after gating are input to control node A. The output signal strength judgment limit is higher than the normal noise level of the interface and lower than the signal level considered as valid output, and is determined through interface testing. This allows for the differentiation between the interface's own minor noise and the still-existing valid output.
[0195] Whether emergency broadcasts have started outputting also requires corresponding actual status judgment conditions. Control node B can check the valid data and gating status feedback of the output interface. If the terminal can only return command reception receipts, actual status acquisition should be added; when using the alternative interface of the device's maximum response time model, the applicable conditions of this estimation method should be clearly defined, and the reception receipt should not be regarded as actual completion.
[0196] Even if both conditions are met at a certain instant, it may only be a brief signal fluctuation. Therefore, control node A first records the local count at this moment and then continues to observe for a predetermined confirmation period. If either condition fails during the observation period, this candidate moment is abandoned, and confirmation is re-established only after both conditions are met again. Only after the confirmation is continuously satisfied is completion information generated, and the start time of this continuous successive confirmation process is taken as the actual completion time.
[0197] For example, the closing condition is continuously met starting at 200 milliseconds, and confirmation is only completed at 201 milliseconds. The background audio source actually stopped at 200 milliseconds, so the completion message should record 200 milliseconds. Recording it as 201 milliseconds omits the 1 millisecond gap that has already occurred. Although continuous confirmation, sampling filtering, and message sending occur before recording the completion message, the confirmation and transmission time should still be included. The allowable waiting period cannot be extended by postponing the actual completion time.
[0198] In the example where the continuous acknowledgment duration is 1 millisecond, the total time spent on filtering, sampling, continuous acknowledgment, and sending must not exceed the aforementioned 2 milliseconds reserved for completing acknowledgment and sending. The continuous acknowledgment duration cannot replace the total time spent.
[0199] After the completion message is sent, the background audio source must remain off. Otherwise, although the emergency broadcast is activated based on the actual completion message, the background audio source might be reactivated by a regular task, causing the two outputs to overlap. Therefore, control node A refuses to allow a regular task to cancel this device status, and retains the original event time when retransmitting the completion message. Other device actions can establish completion conditions using corresponding device status feedback and controlled output signals, but both should jointly reflect the target status and be continuously confirmed and maintained in the same manner.
[0200] In a further implementation, the method further includes the following validity verification process before issuing the launch authorization:
[0201] Before issuing the start authorization, check whether the maintenance information associated with the joint execution record, resource usage relationships, proposed start schedule, and plan version have changed;
[0202] When changes occur, the original joint execution record is invalidated and the issuance of initiation authorization based on the original joint execution record is stopped. The joint cutoff time and the latest effective time of subsequent actions are re-determined according to the changed conditions.
[0203] Once the condition that the latest effective time is no later than the common deadline is met again, and the control node that performs subsequent actions returns a readiness confirmation message to the updated joint execution record, an authorization to start is issued.
[0204] Between preparation and authorization, the confirmed conditions may still change. For example, route hold information may be replaced, resource coordination may shorten the committable hold period, preparation delays may require adjustments to the intended launch location, or the linkage control module may generate a new plan version. Although the original joint execution record was calculated, it corresponds to the state, resources, and schedule before the change and cannot be automatically applied to the changed task.
[0205] Therefore, before issuing a start authorization, the linkage control module checks the joint execution record against the current maintenance information, resource occupancy relationships, proposed start schedule, and planned version. If changes are found, the original joint execution record is first marked as invalid, and authorization based on it is stopped. Then, using the updated completion time range and maintenance deadline, the common deadline and latest effective time are recalculated. After the time conditions are met again, the updated joint execution record is handed over to control node B for storage and application, and awaits the corresponding preparation confirmation information.
[0206] Both recalculation and reconfirmation are required here. Recalculating alone might leave control node B waiting with the original joint execution record; simply saving and applying without recalculation makes it impossible to confirm whether the new retention period is sufficient. Therefore, no start authorization is issued if the new retention period is insufficient or control node B has not yet confirmed it. Upon receiving a message, the joint execution record before and after the update is distinguished by task number, execution sequence number, and plan version. Confirmation of the old version cannot restore expired joint execution records.
[0207] The above processing occurs before the start authorization is issued, at which point there is still an opportunity to reschedule. If the start authorization has already been validly issued, it is necessary to first verify whether the background audio source shutdown action has been initiated and the emergency broadcast start action has been executed, and then coordinate cancellation or processing as if it has already been executed. Directly releasing hold resources may cause the handover that has already begun to lose its continuity conditions. If a higher priority event must preempt, the original task should be marked as aborted, and the subsequent device status should be processed separately.
[0208] When coordination is cancelled, the linkage control module first records the task as cancelled and stops issuing start authorization, then cancels the preparation of nodes that have not yet started. If the background sound source shutdown action completion condition is not met, no completion information is sent, and the preceding action is reported as failed; if no valid output appears after control node B starts, execution failure is recorded. Normal actions are not started based on old versions or expired messages; after a node restart or the counting source becomes invalid, the old timing basis is discarded and the device status is verified. For continuous network outages, equipment failures, and manual takeover, the alternative paths or processing rules configured in the project are used; waiting, aborting, or preemption are not recorded as successful tasks.
[0209] This application also provides a low-voltage fire protection equipment linkage timing control system for executing the above method, including:
[0210] The linkage timing control module is used for:
[0211] Identify multiple preceding actions that jointly constrain the same subsequent action, wherein at least one preceding action is a preceding action that can be completed ahead of time and maintain its completed state, and at least one preceding action is another preceding action that has an allowed waiting period after completion.
[0212] Execute preliminary actions that can be completed in advance, and maintain the resulting device state until subsequent actions take effect;
[0213] Based on the retention period of the equipment status, the allowable waiting period after the completion of another preceding action, and the expected effective time of the subsequent action, determine whether the subsequent action can take effect within the retention period and the allowable waiting period;
[0214] If the determination result is that it can take effect, another preceding action is authorized to start, so that the allowed waiting period can be opened after the subsequent action has the connection conditions.
[0215] The aforementioned method is implemented by a linkage timing control module, encompassing the determination of preceding actions, advance execution and state maintenance, time judgment, and start authorization. A single logical functional unit represents the complete coordination capability described above; the division of method steps does not require the establishment of mutually independent physical modules.
[0216] A logical functional unit does not require all devices to be housed in the same enclosure. In one implementation, the linkage timing control module is implemented by a linkage control module and programs running collaboratively on each control node: the linkage control module determines the preceding actions, organizes the execution schedule, performs timing checks, and authorizes the start; each control node executes actions through the device control interface, obtains the actual completion results through the status input interface, maintains the corresponding device state, and uses a local continuous counter to maintain task timing. Even if the physical nodes are distributed in different locations, they still collectively complete the function of the same linkage timing control module.
[0217] The control node can be implemented by a microcontroller or industrial computer, configured with a processor, memory, communication interface, continuous counter, control output, and status input, and provided with regulated and isolated power supply as required by the equipment, without limitation on the rated voltage. The time synchronization function provides common time and quality information to the linkage control logic; this physical implementation is part of the aforementioned linkage timing control module and does not add another parallel system functional module.
[0218] Reference Figure 7 The arrows indicate the direction of logical information transmission. The linkage control module receives common time and quality information, issues action plans to each control node, issues route preparation and maintenance arrangements to control node C, issues joint execution records to control node B, and issues start authorization to control node A after the authorization conditions are met. Control node C sends maintenance information to the linkage control module and control node B. Control node B saves and applies the joint execution records and maintains the execution preparation state before returning preparation confirmation information to the linkage control module. Control node A sends completion information to control node B after actual completion. Each control node obtains the same time base version according to the aforementioned preparation process and establishes a task-specific conversion relationship. The background sound source gating interface, emergency broadcast output interface, and route configuration interface respectively handle the control and feedback of the corresponding devices: control node A issues a gating close command and obtains gating status and feedback of the branch output after gating; control node B issues a command to allow output and obtains valid data and gating status feedback; control node C issues a route configuration command and obtains route status and resource feedback. In the diagram, downward arrows represent device control commands, and upward arrows represent device status feedback. Completion information can also be sent to the linkage control module for unified verification. The diagram does not specify the actual transmission path of the audio signal; the audio does not need to be forwarded through the linkage control module. All control logics work together to implement a linkage timing control module.
[0219] Alternatively, these control logics can be centralized in a single integrated control device, with the processor running the same program to control the background sound source, emergency broadcast output, and routing via device interfaces. Regardless of whether a centralized or distributed implementation is adopted, it is necessary to ensure the continued availability of the pre-established device state and to initiate authorization with a shared and valid timeframe. Maintaining information, joint execution records, and completion information ensures that the aforementioned optimal control processes can be implemented on the corresponding devices.
[0220] For completion information transmitted directly and forwarded via the linkage control module, different communication interfaces can be used, but the corresponding transmission time should be included in the same time schedule. Routing, gating, and other device interfaces can be selected according to the actual devices, as long as they can execute the corresponding actions, provide feedback on the actual status, and maintain the promised relationship. Thus, the system implementation does not depend on a specific hardware model; both the method and the system revolve around initiating this relationship based on the pre-actions constrained by subsequent connectable conditions.
[0221] When checking actual operating results, the equipment output should be observed directly. The same external acquisition device can be used to record the times when the background sound source stops outputting after gating and when the emergency broadcast starts effectively. If only the logs of each control node are compared, the clock used in the logs may have been calibrated, easily masking the true intervals. During testing, apply both forward and reverse time adjustments and record the actual action intervals, the arrival time of completion information, node status, and the cause of any abnormalities.
[0222] It can also check for message arrival first, timeout first, retransmission within the allowed number of times, duplicate messages, old version messages, cancellation preparation, and node restart, and verify arrangements where the common validity period is just enough or just insufficient. Based on the actual measured completion confirmation, transmission, scheduling, output time and timing error, the reserved time is reduced or the maximum time for each item is redefined. If the result exceeds the originally calculated maximum time, the implementation or applicable scope should be adjusted, and only the success record should be changed. The aforementioned values are used to illustrate the mechanism and the value range used in the calculation, and are not actual machine measurement results.
[0223] The above are merely embodiments of this application and are 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. Any modifications, equivalent substitutions, improvements, etc., 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 sequential control of linkage of low-voltage fire protection equipment, characterized in that, include: Identify multiple preceding actions that jointly constrain the same subsequent action, wherein at least one preceding action is a preceding action that can be completed ahead of time and maintain its completed state, and at least one preceding action is another preceding action that has an allowed waiting period after completion. Perform the pre-execution actions that can be completed in advance, and maintain the resulting device state until the subsequent actions take effect; Based on the retention period of the device status, the allowable waiting period after the completion of the other pre-action, and the expected effective time of the subsequent action, determine whether the subsequent action can take effect within the retention period and the allowable waiting period; If the determination result is that it can take effect, the other pre-action is authorized to start, so that the allowed waiting period is opened after the subsequent action has the connection conditions.
2. The method for linkage timing control of low-voltage fire protection equipment according to claim 1, characterized in that, The step of determining multiple preceding actions that jointly constrain the same subsequent action includes: Based on the execution order requirements of each pre-action and its impact on the device output, the pre-action that does not require the completion of the other pre-action as a prerequisite for execution, does not trigger the device output corresponding to the subsequent action when executed in advance, and can maintain the completed state, is determined as the pre-action that can be completed in advance. The other pre-action and its corresponding allowed waiting period are determined based on the maximum allowable interval between the completion of the pre-action and the effective date of the subsequent action.
3. The method for linkage timing control of low-voltage fire protection equipment according to claim 2, characterized in that, Maintaining the device state formed by the pre-completion actions until the subsequent actions take effect includes: After the preliminary actions that can be completed in advance are completed, the resulting device state, the resources required to maintain the device state, and the hold deadline are determined, and hold information associated with the device state, the resources, and the hold deadline is generated; Before the retention deadline, the resources are reserved for the subsequent action, and other tasks are restricted from reconfiguring the resources, so that the device state is maintained until the subsequent action takes effect.
4. The method for linkage timing control of low-voltage fire protection equipment according to claim 3, characterized in that, The step of determining whether the subsequent action can take effect within the retention period and the allowed waiting period, and authorizing the initiation of the other preceding action when the determination result is that it can take effect, includes: Based on the proposed start schedule and execution time range of the other pre-action, determine the expected completion time range of the other pre-action, and add the earliest moment of the expected completion time range to the maximum allowable waiting time to obtain the waiting deadline. The earlier of the waiting deadline and the holding deadline is determined as the common deadline. Based on the planned trigger time of the subsequent action, the latest completion time of each preceding action, the maximum time for completing information transmission, and the maximum execution time of the subsequent action, the latest effective time of the subsequent action is determined, and the latest effective time is used as the expected effective time. Only when the latest effective time is not later than the common deadline time is the judgment result determined to be effective, and the other pre-action is authorized to start according to the proposed start-up arrangement, so that the allowed waiting period after the completion of the other pre-action and the retention period of the device state together cover the effective time of the subsequent action.
5. The method for linkage timing control of low-voltage fire protection equipment according to claim 4, characterized in that, Also includes: The retention information, the validity period of the authorization for the other preceding action, the planned trigger time of the subsequent action, and the common deadline time are associated as the same joint execution record and sent to the control node that executes the subsequent action; After the control node completes the execution preparation for the subsequent actions, saves and applies the joint execution record, and promises to maintain the execution preparation state, it returns preparation confirmation information. Receiving the preparation confirmation information will be an additional condition for issuing the launch authorization.
6. The method for linkage timing control of low-voltage fire protection equipment according to claim 5, characterized in that, Also includes: Establish a task-specific conversion relationship between global time and local continuous count value for the control nodes participating in this linkage, and determine the action trigger position and deadline position of this linkage based on the task-specific conversion relationship. During this coordinated execution, the task-specific conversion relationship remains unchanged. This task-specific conversion relationship is used to interpret the completion time of the preceding actions and determine whether each deadline has expired, so that the global time synchronization during operation does not change the correspondence between the action trigger position, deadline position, and completion time of this coordinated action.
7. The method for linkage timing control of low-voltage fire protection equipment according to claim 6, characterized in that, Also includes: The control node that executes the other pre-action performs the other pre-action according to the start authorization, generates completion information containing the actual completion time after the other pre-action is actually completed, and maintains the device state formed by the other pre-action. After the control node executing the subsequent action arrives at the planned trigger position of this linkage and obtains the completion information and the valid holding information, it determines the actual waiting deadline based on the actual completion time. The current time is determined by the task-specific conversion relationship. The subsequent action is executed only if the maximum time required for the subsequent action to take effect from the current time is not greater than the remaining time from the current time to the actual waiting deadline and the holding deadline, respectively.
8. The method for linkage timing control of low-voltage fire protection equipment according to claim 7, characterized in that, The step of generating completion information containing the actual completion time after the other preceding action is actually completed, and maintaining the device state formed by the other preceding action, includes: Obtain the device status feedback and controlled output signal corresponding to the other pre-action, and determine whether the device status feedback and the controlled output signal together satisfy the completion condition of the other pre-action; After the completion conditions are met for a predetermined confirmation period, the start time of the continuous satisfaction of the completion conditions is determined as the actual completion time, and completion information containing the actual completion time is generated. Maintain the device state corresponding to the completion condition, and refuse to allow ordinary control tasks to cancel the device state.
9. A method for linkage timing control of low-voltage fire protection equipment according to claim 5, characterized in that, Also includes: Before issuing the start authorization, check whether the maintenance information, resource usage relationship, proposed start arrangement and plan version associated with the joint execution record have changed; When changes occur, the original joint execution record is invalidated and the issuance of start authorization based on the original joint execution record is stopped. The common cutoff time and the latest effective time of the subsequent actions are re-determined according to the changed conditions. Once the condition that the latest effective time is no later than the common deadline is met again, and the control node executing the subsequent action returns a preparation confirmation message to the updated joint execution record, the start authorization is issued.
10. A timing control system for linkage of low-voltage fire protection equipment, used to execute the method described in any one of claims 1 to 9, characterized in that, include: The linkage timing control module is used for: Identify multiple preceding actions that jointly constrain the same subsequent action, wherein at least one preceding action is a preceding action that can be completed ahead of time and maintain its completed state, and at least one preceding action is another preceding action that has an allowed waiting period after completion. Perform the pre-execution actions that can be completed in advance, and maintain the resulting device state until the subsequent actions take effect; Based on the retention period of the device status, the allowable waiting period after the completion of the other pre-action, and the expected effective time of the subsequent action, determine whether the subsequent action can take effect within the retention period and the allowable waiting period; If the determination result is that it can take effect, the other pre-action is authorized to start, so that the allowed waiting period is opened after the subsequent action has the connection conditions.
