Systems, methods, apparatus, media, and program products implementing a multi-monitoring center for a fire alarm system

Abstract

This application discloses a system, method, apparatus, medium, and program product for implementing multiple monitoring centers in a fire alarm system. The system includes: a fire alarm system equipment layer; a main monitoring center; at least one backup monitoring center; and a proxy module for establishing an indirect communication connection between the fire alarm system equipment layer and the at least one backup monitoring center, synchronizing data from the fire alarm system equipment layer with the main monitoring center, and scheduling and distributing the data to each backup monitoring center. The technical solution in this application can implement multiple monitoring centers without loss of resources, configuration, or additional physical wiring at the fire alarm system equipment layer.

Description

Technical Field

[0001] This application relates to the field of alarm technology, and in particular to systems, methods, apparatus, computer-readable storage media, and program products for implementing a fire alarm system (FAS) with multiple monitoring centers. Background Technology

[0002] Fire alarm monitoring centers, or fire alarm management systems, are a crucial component of fire alarm systems. In most applications, users typically need to deploy multiple fire alarm monitoring centers, i.e., set up backup monitoring centers in different locations, to avoid fire alarm monitoring interruptions caused by the failure of the main monitoring center.

[0003] In traditional multi-backup center solutions, the following steps are required: the user discovers an idle physical communication port in the fire alarm device layer; the user updates the configuration of the fire alarm device layer using engineering tools, enabling it to establish communication with the new fire alarm monitoring center through this port; the user downloads the new configuration to the fire alarm device layer using engineering tools, making the configuration effective; the fire alarm device layer needs to recognize the new configuration, complete the access to the new fire alarm monitoring center, and work collaboratively with it.

[0004] In addition, those skilled in the art are also working to find other technical solutions for FAS multi-backup centers. Summary of the Invention

[0005] In view of this, the embodiments of this application propose, on the one hand, a system for implementing multiple monitoring centers of FAS, and on the other hand, a method, apparatus, computer-readable storage medium and program product for implementing multiple monitoring centers of FAS, so as to realize multiple monitoring centers without loss, configuration and no new physical wiring at the equipment layer of the fire alarm system.

[0006] This application proposes a system for implementing multiple monitoring centers for a Fire Alarm System (FAS), comprising: a fire alarm system equipment layer; a main monitoring center; at least one backup monitoring center; and a proxy module for establishing an indirect communication connection between the fire alarm system equipment layer and the at least one backup monitoring center, synchronizing data from the fire alarm system equipment layer with the main monitoring center, and scheduling and distributing the data to each backup monitoring center.

[0007] In some implementations, the main monitoring center is connected to the fire alarm system equipment layer via at least one communication link to receive data from the fire alarm system equipment layer and synchronize the data to the agent module; or, the agent module is connected to the fire alarm system equipment layer via at least one communication link to receive data from the fire alarm system equipment layer and synchronize the data to the main monitoring center.

[0008] In some implementations, the proxy module is further configured to receive and maintain data subscription topics for each backup monitoring center, or the proxy module pre-configures and maintains data subscription topics for each backup monitoring center, and then schedules and distributes the data to each backup monitoring center according to the data subscription topics of each backup monitoring center.

[0009] In some implementations, the agent module includes: a main agent unit, configured to establish an indirect communication connection between the fire alarm system equipment layer and the at least one backup monitoring center, synchronize data from the fire alarm system equipment layer with the main monitoring center, and schedule and distribute the data to each backup monitoring center; at least one backup agent unit, configured to form a primary-backup agent redundancy architecture with the main agent unit; and an agent management unit, configured to monitor the operational health status of the main agent unit and the at least one backup agent unit in real time, and intelligently decide which agent unit is currently executing the data scheduling and distribution task based on the operational health status, and issue scheduling instructions to the corresponding agent unit.

[0010] This application proposes a method for implementing multiple monitoring centers in a fire alarm system, comprising: deploying an agent module in the fire alarm system, wherein the agent module establishes an indirect communication connection between the fire alarm system equipment layer and at least one backup monitoring center; the agent module synchronizes data from the fire alarm system equipment layer with the main monitoring center and schedules and distributes the data to each backup monitoring center.

[0011] In some implementations, the main monitoring center is connected to the fire alarm system equipment layer via at least one communication link; the agent module synchronizes data from the fire alarm system equipment layer with the main monitoring center by: the main monitoring center receiving data from the fire alarm system equipment layer and synchronizing the data to the agent module.

[0012] In some implementations, the proxy module is connected to the fire alarm system equipment layer via at least one communication link; the synchronization of data from the fire alarm system equipment layer between the proxy module and the main monitoring center includes: the proxy module receiving data from the fire alarm system equipment layer and synchronizing the data to the main monitoring center.

[0013] In some implementations, the method further includes: the agent module receiving and maintaining data subscription topics for each backup monitoring center, or the agent module pre-configuring and maintaining data subscription topics for each backup monitoring center; the method of scheduling and distributing the data to each backup monitoring center is: according to the data subscription topics of each backup monitoring center, the data is scheduled and distributed to each backup monitoring center.

[0014] In some implementations, deploying the agent module in the fire alarm system includes: deploying a main agent unit, at least one backup agent unit, and an agent management unit in the fire alarm system; the agent management unit monitors the operational health status of the main agent unit and the at least one backup agent unit in real time, and intelligently decides which agent unit is currently executing the data scheduling and distribution task based on the operational health status, and issues scheduling instructions to the corresponding agent unit.

[0015] Another apparatus for implementing multiple monitoring centers of a fire alarm system (FAS) according to an embodiment of this application includes: at least one memory storing a computer program; and at least one processor for reading and executing the computer program to implement the method for implementing multiple monitoring centers of a fire alarm system as described in any of the above embodiments.

[0016] This application proposes a computer-readable storage medium storing computer instructions; the computer instructions can be executed by at least one processor to implement the method for implementing a multi-monitoring center of a fire alarm system as described in any of the above embodiments.

[0017] The program product proposed in this application includes: a computer program; the computer program can be executed by at least one processor to implement the method for implementing a multi-monitoring center of a fire alarm system as described in any of the above embodiments.

[0018] In this embodiment, an indirect communication connection between the FAS device layer and at least one backup monitoring center is established by deploying an agent module. The data scheduling and distribution operations of the backup monitoring center are all performed by the agent module, and the FAS device layer does not need to add any communication load or configuration operations. Even if the number of backup monitoring centers continues to increase, it will not affect the existing configuration of the FAS device layer, nor will it increase the physical wiring of the FAS device layer. That is, the hardware performance of the FAS device layer will not suffer any loss, thus realizing lossless expansion of the FAS device layer. Attached Figure Description

[0019] The preferred embodiments of this application will now be described in detail with reference to the accompanying drawings, so that those skilled in the art can more clearly understand the above and other features and advantages of this application, in which:

[0020] Figure 1A This is an exemplary structural diagram of a multi-monitoring center system for implementing FAS provided in some embodiments of this application;

[0021] Figure 1B This is a schematic diagram of the structure of a multi-monitoring center system implementing FAS in one example of this application;

[0022] Figure 2 This is an exemplary structural diagram of a multi-monitoring center system for implementing FAS provided in other embodiments of this application;

[0023] Figure 3 An exemplary flowchart illustrating a method for implementing a multi-monitoring center for a fire alarm system, as provided in an embodiment of this application;

[0024] Figure 4 This is an exemplary structural diagram of a device for implementing a multi-monitoring center of a fire alarm system, provided in an embodiment of this application.

[0025] The reference numerals and their meanings in the attached figures are as follows:

[0026] 10: FAS Equipment Layer

[0027] 11: Main control board

[0028] 12: From the control panel

[0029] 20: Main Monitoring Center

[0030] 21: Communication Module

[0031] 22: Other Ontology Modules

[0032] 30: Backup Monitoring Center

[0033] 40: Proxy Module

[0034] 41: Main Agent Unit

[0035] 42: Backup Agent Unit

[0036] 43: Agent Management Unit

[0037] 431: Proxy Monitoring Submodule

[0038] 432: Agent Control Submodule

[0039] S31~S32: Steps

[0040] 401: Memory

[0041] 402: Processor

[0042] 403: Bus Detailed Implementation

[0043] After in-depth observation and analysis of actual application scenarios of fire alarm systems, the inventors discovered the following problems in the implementation process of traditional multi-backup center solutions: 1. Users need to update the configuration of the entire fire alarm equipment layer. Such changes must be negotiated with and agreed upon by end users, which consumes a significant amount of time. 2. Users need to locate the physical ports of the fire alarm equipment layer and establish physical cable connections. 3. The above two points make the implementation of the solution challenging, and the performance of the fire alarm equipment layer will decrease as the number of backup monitoring centers increases.

[0044] Therefore, to achieve multiple monitoring centers without loss of equipment layer, configuration, or additional physical wiring in the fire alarm system, this application embodiment considers using a proxy mode to construct the communication architecture. Specifically, it provides a scheme where a proxy module establishes an indirect communication connection between the fire alarm system equipment layer and at least one backup monitoring center. By deploying the proxy module to receive equipment layer data and schedule its distribution to the backup monitoring centers, all backup monitoring centers communicate indirectly with the equipment layer through this proxy module, without requiring additional physical connections or modifications to the equipment layer configuration.

[0045] To make the objectives, technical solutions, and advantages of this application clearer, the following examples are provided to further illustrate this application in detail.

[0046] Figure 1A This is an exemplary structural diagram of a multi-monitoring center system for implementing a fire alarm system, provided in some embodiments of this application. For example... Figure 1A As shown, the system may include: FAS equipment layer 10, main monitoring center 20, at least one backup monitoring center 30, and agent module 40. The FAS equipment layer is the fire alarm system equipment layer.

[0047] Among them, FAS device layer 10 is the bottom-level hardware device of the fire alarm system, which is used to collect and send fire alarm related data (such as raw data, alarm event data, device status data, etc.).

[0048] FAS equipment layer 10 may include various sensors (not shown in the figure), such as smoke detectors, temperature detectors, and flame detectors, as well as corresponding control units, such as... Figure 1AThe diagram shows the main control board 11 and the slave control board 12. The main control board 11 is the master control node of the FAS equipment layer, the core command and data aggregation unit of the entire equipment layer, and the communication port between the equipment layer and the upper-level main monitoring center 20 or agent module 40. It belongs to the master device of the FAS equipment layer. The slave control board 12 is a slave control node of the FAS equipment layer, a distributed field unit, typically deployed according to physical areas or monitoring zones at the fire alarm site (such as different floors or workshops of a building). It belongs to the slave device of the FAS equipment layer.

[0049] The fire alarm monitoring center (including the main monitoring center 20 and the backup monitoring center 30) is the core control and data presentation node of the entire fire alarm system. The main monitoring center is responsible for core scheduling, main communication, and basic control, while the backup monitoring center serves as a redundant node to provide backup in case of failure. Their core capabilities are identical, differing only in deployment roles and operational priorities. In specific implementation, each monitoring center may include: a communication module responsible for transmitting data and signals; a data parsing module responsible for analyzing and processing data; a data visualization and monitoring module responsible for monitoring and displaying data; and an emergency response intelligent linkage control module responsible for triggering alarm prompts.

[0050] exist Figure 1A In the illustrated embodiment, the main monitoring center 20 establishes a stable main communication link with the FAS device layer 10, receives various fire alarm-related data uploaded by the FAS device layer 10 in real time, and is the primary receiver of data from the FAS device layer. Simultaneously, the main monitoring center 20 synchronizes data from the FAS device layer 10 to the agent module 40. Specifically, the main monitoring center 20 can receive various fire alarm-related data uploaded by the FAS device layer 10 through the communication module 21, and the communication module 21 can then synchronize the data from the FAS device layer 10 to the agent module 40.

[0051] In addition, the main monitoring center 20 is also used to perform real-time analysis, storage, and display of data received from the FAS device layer 10, such as fire alarm signals, sensor monitoring data, and equipment offline / fault information, providing a visual monitoring interface for maintenance personnel. When emergency information such as fire alarms or major equipment failures is detected, the system's emergency response mechanism is triggered, such as audible and visual alarms, linkage reminders, and emergency command issuance. It also performs routine lightweight management operations of the fire alarm system, such as issuing data query and status confirmation commands to the FAS device layer 10 and receiving feedback results. These processes can be handled by other core modules 22 of the main monitoring center 20, including a data parsing module responsible for data analysis and processing, a data visualization and monitoring module responsible for data monitoring and display, and an emergency response intelligent linkage control module responsible for triggering alarm prompts.

[0052] In some implementations, to ensure the stability of the communication link between the main monitoring center 20 and the FAS device layer 10, the main monitoring center 20 can be connected to the FAS device layer 10 through more than one communication link. Specifically, these multiple communication links can simultaneously receive data from the FAS device layer 10, and then perform redundancy filtering processing at the main monitoring center 20; alternatively, the main monitoring center 20 can set up a primary communication link and a backup communication link for the multiple communication links, and switch to the backup communication link when the primary communication link fails.

[0053] Regardless of whether there is only one communication link, when the main monitoring center 20 fails, as long as the communication link between the main monitoring center 20 and the FAS device layer 10 can receive data, the data can be synchronized to the agent module 40. In other words, the agent module 40 is only connected to the communication module in the main monitoring center 20 that is responsible for data and signal transmission, and does not interfere with the original data flow of the main monitoring center 20, that is, the original data flow for data parsing, monitoring, emergency response, etc.

[0054] The proxy module 40 is used to establish an indirect communication connection between the FAS device layer 10 and the at least one backup monitoring center 30, synchronize data from the FAS device layer 10 with the main monitoring center 20, and schedule and distribute the data to each backup monitoring center 30. Furthermore, if a backup monitoring center 30 needs to send a lightweight query or status confirmation command to the FAS device layer 10, it can receive the command sent by the backup monitoring center 30 to the FAS device layer, forward it back to the FAS device layer 10 via the communication module of the main monitoring center 20, and send the feedback data received from the FAS device layer 10 via the communication module of the main monitoring center 20 back to the corresponding backup monitoring center 30.

[0055] In specific implementation, the proxy module 40 can be as follows: Figure 1A As shown, the proxy module 40 is deployed on the main monitoring center 20, becoming a functional module of the main monitoring center 20. The advantages of this deployment are: it simplifies implementation, reduces deployment costs, utilizes the existing hardware resources of the main monitoring center 20, and leverages its high-performance CPU and existing communication links to directly achieve data forwarding without adding a new independent node. Of course, the proxy module 40 can also be deployed independently of the main monitoring center 20, making its deployment location more flexible. The specific implementation method can be determined according to the implementation situation, and this application does not limit its specific implementation form.

[0056] Each backup monitoring center 30 can be deployed in different regions or nodes. Its core function is to prevent fire alarm monitoring interruptions caused by a failure of the main monitoring center 20. Its operation revolves around "redundant backup, fault takeover, and seamless switching," and its basic operational functions are consistent with those of the main monitoring center 20. Each backup monitoring center 30 establishes an indirect communication link with the FAS device layer 10 through the proxy module 40, receiving fire alarm-related data distributed by the proxy module 40 in real time, without needing a direct connection to the FAS device layer 10. It maintains real-time data synchronization with the main monitoring center 20 through the proxy module 40, parsing, storing, and visualizing the received FAS device layer data, ensuring that maintenance personnel can view the same monitoring information as the main monitoring center 20 on the backup monitoring center 30. When the main monitoring center 20 experiences hardware failures, communication interruptions, software crashes, or other anomalies, the backup monitoring center 30 can immediately become an effective monitoring node, continuously receiving data and ensuring uninterrupted monitoring without manual reconfiguration. When the main monitoring center 20 fails, it undertakes emergency response work, identifies emergency information, and triggers corresponding emergency mechanisms to ensure the fire alarm system's emergency response capabilities are not compromised. In addition, each backup monitoring center 30 can also perform some routine light management operations of the fire alarm system, such as issuing data query and status confirmation instructions to the FAS equipment layer 10 and receiving feedback results.

[0057] When there are more than one backup monitoring center 30, if the primary monitoring center 20 fails, the agent module 40 can select the current backup monitoring center 30 to replace the primary monitoring center 20, following either a traditional switching strategy or a newly designed switching strategy. For example, in some implementations, the optimal backup monitoring center can be selected as the new primary monitoring center based on a triple judgment principle of "preset priority + real-time health status + business adaptability," while the remaining backup monitoring centers remain in backup status.

[0058] The system allows for pre-setting hierarchical takeover priorities for each backup monitoring center 30, and the takeover priority configuration for each backup monitoring center 30 can be completed in the agent module 40 (this can be done during system initialization and supports dynamic adjustment later). The configuration dimensions can be combined with the business requirements, hardware performance, and deployment region design of the FAS system. The following configuration considerations can be used individually or in combination:

[0059] 1) Hardware performance priority: sorted by CPU computing power, communication bandwidth, and storage capacity, with the backup monitoring center having the best performance having the highest priority (to ensure that it can support the core monitoring and data processing work of the main monitoring center after takeover).

[0060] 2) Geographic proximity priority: Based on the physical geographical distance from the FAS equipment layer, the backup monitoring center deployed nearby has the highest priority (30) (reducing cross-regional data transmission latency and improving the response speed of fire emergency information).

[0061] 3) Business-specific priority: The backup monitoring center 30 is sorted according to its business positioning. For example, the backup monitoring center 30 deployed in the fire control room or core computer room has a higher priority than the backup monitoring center 30 of ordinary operation and maintenance nodes (to match the core business needs of fire monitoring).

[0062] The agent module 40 can obtain real-time health data from each backup monitoring center 30. When the main monitoring center 20 fails, only backup monitoring centers 30 that meet the health requirements will proceed to the next verification stage. The following health judgment criteria can be used individually or in combination:

[0063] 1) Hardware status: CPU / memory / disk utilization is within the threshold range, and there is no risk of hardware failure or downtime.

[0064] 2) Software status: The fire alarm monitoring module, data parsing module, emergency response module and other modules responsible for the corresponding processing functions are running normally, with no program crashes / log errors.

[0065] 3) Data status: The full historical and real-time data of the FAS device layer has been received and synchronized through the agent module 40, with no data loss or synchronization interruption.

[0066] The considerations for business adaptability may include: verification of business availability and link connectivity. Regarding business availability, the agent module 40 can verify whether the backup monitoring center 30 possesses all the business functions of the main monitoring center 20, ensuring that fire monitoring work is not lost after takeover. Regarding link connectivity, the agent module 40 can verify the communication link status between the backup monitoring center 30 and the agent module 40, ensuring that real-time data interaction can be maintained after takeover.

[0067] In addition, each backup monitoring center 30 can subscribe to personalized data reception from the agent module 40. For example, each backup monitoring center 30 can send a data subscription topic to the agent module 40 or pre-configure its own data subscription topic on the agent module 40. These data subscription topics can be for specific areas or specific types of fire data, etc., to achieve personalized data reception while avoiding redundant data on communication lines.

[0068] Accordingly, the proxy module 40 can be further used to receive and maintain the data subscription topics of each backup monitoring center 30, or the proxy module 40 can pre-configure and maintain the data subscription topics of each backup monitoring center 30, and then uniformly schedule and distribute the data to each backup monitoring center 30 in real time according to the data subscription topics of each backup monitoring center 30.

[0069] In a specific implementation, the proxy module 40 may include only one proxy unit, or it may be as follows: Figure 1AThe diagram shows: a main agent unit 41, at least one backup agent unit 42, and an agent management unit 43.

[0070] In specific deployment, each unit in the agent module 40 can be deployed on different physical nodes. For example, the main agent unit 41 can be deployed on the main monitoring center 20, each backup agent unit 42 can be deployed on different backup monitoring centers 30 or other devices, and the agent management unit 43 can be deployed on another backup monitoring center 30 or other devices. Alternatively, they can be partially deployed on different physical nodes. For example, the main agent unit 41 and the agent management unit 43 can be deployed on the main monitoring center 20, and each backup agent unit 42 can be deployed on the same or different backup monitoring centers 30 or other devices. Alternatively, they can be deployed simultaneously on the main monitoring center 20, the backup monitoring center 30, or a third-party independent device.

[0071] The main agent unit 41 is used to implement all the functions of the agent module 40 mentioned above. In addition, the main agent unit 41 is also used to report its own operational health status data (such as CPU utilization, communication link status, message forwarding rate, operation log, etc.) to the agent management unit 43 in real time; receive scheduling instructions issued by the agent management unit 43 and perform data forwarding, standby and other operations; and locally store all data subscription topics of the backup monitoring center 30.

[0072] At least one backup agent unit 42 and the main agent unit 41 constitute a primary-backup agent redundancy architecture. This is a redundant component designed to avoid single-point failures of the main agent unit 41. It is isomorphic to the main agent unit 41 (i.e., its functions, development framework, and adaptation protocols are completely identical). Under normal conditions, it is in standby mode and does not perform actual data forwarding work, only completing basic architectural coordination. When the main agent unit 41 malfunctions, it seamlessly switches to working agent under the scheduling of the agent management unit 43, taking over all the functions of the main agent unit 41. Specifically, its functions are divided into standby mode and working mode.

[0073] In standby mode, each backup agent unit 42 only performs basic architecture coordination and does not perform any actual fire data forwarding operations. This includes: synchronizing with the main agent unit 41 and reporting its own health status to the agent management unit 43 in real time to ensure that the agent management unit 43 has a complete grasp of the status of all agent nodes; receiving standby, ready, and other scheduling instructions from the agent management unit 43, maintaining architecture synchronization with the main agent unit 41, without performing any actual fire data transmission or reception operations, thus avoiding redundant data in the communication link; and locally storing the data subscription topics of all backup monitoring centers 30.

[0074] In the switched-off working state, it fully assumes all the functions of the main agent unit 41. When the agent management unit 43 detects that the main agent unit 41 has problems such as communication interruption, hardware failure, software crash, forwarding abnormality, etc. and issues a switch command, the backup agent unit 42 immediately switches from standby to working state and executes all the functions of the main agent unit 41 without difference.

[0075] Regarding the data subscription topics for each backup monitoring center 30, to ensure the continuity of data distribution after the switchover, if the method of pre-configuring in the agent module 40 is adopted, the data subscription topics for each backup monitoring center 30 can be pre-configured in the main agent unit 41 and at least one backup agent unit 42 respectively. Alternatively, the data subscription topics for each backup monitoring center 30 can be pre-configured only in the main agent unit 41, and then synchronized by the main agent unit 41 to the agent management unit 43, which in turn synchronizes them to each backup monitoring center 30. Alternatively, the data subscription topics for each backup monitoring center 30 can be pre-configured in the agent management unit 43, and then synchronized by the agent management unit 43 to the main agent unit 41 and at least one backup agent unit 42.

[0076] If the method of sending requests by each backup monitoring center 30 is adopted, the main agent unit 41 can receive the data subscription requests sent by each backup monitoring center 30, and then the main agent unit 41 synchronizes them to the agent management unit 43, and the agent management unit 43 synchronizes them to each backup monitoring center 30.

[0077] The agent management unit 43 is used to monitor the operational health status of the main agent unit 41 and the at least one backup agent unit 42 in real time, and intelligently decide the agent unit currently executing the data scheduling and distribution task based on the operational health status, and issue scheduling instructions to the corresponding agent unit.

[0078] When there is more than one backup agent unit 42, when the main agent unit 41 fails and the switch is made to the backup agent unit 42, the agent management unit 43 can execute according to the preset priority rules and real-time health status detection. The core principle is to "take over the backup agent unit with the highest priority and health first". At the same time, it is equipped with logic for real-time status verification, status synchronization after switching, and standby backup for the remaining backup agent units.

[0079] In the agent management unit 43, priority numbers and hierarchical configurations can be pre-assigned to all backup agent units 42. The configuration method can be static preset plus dynamic adjustment, and the specific form can be selected according to system requirements. For example, the following priority settings can be used individually or in combination:

[0080] 1) Physical node priority: The backup agent is sorted by the performance and / or importance of the deployment nodes, such as backup agent units deployed in the core data center (priority 1) > backup agent units deployed in secondary data centers (priority 2) > backup agent units deployed on edge nodes (priority 3).

[0081] 2) Hardware performance priority: The backup agent is sorted by server CPU, memory, and communication bandwidth. The higher the performance, the higher the priority, to ensure that the data forwarding efficiency is not reduced after takeover.

[0082] 3) Customizable hierarchical priority: Manually configure according to the user's system planning needs. For example, backup agents in the same region as the backup monitoring center have higher priority to reduce cross-regional data transmission latency.

[0083] For example, the following health conditions can be considered alone or in combination:

[0084] 1) Hardware status: CPU / memory utilization is within the threshold range and there are no hardware faults.

[0085] 2) Communication status: The communication links with the main monitoring center 20 or FAS equipment layer 10, as well as with all backup monitoring centers 30, are normal.

[0086] 3) Software status: The agent program does not crash, message forwarding and parsing functions are normal, and there are no errors in the runtime log.

[0087] 4) Synchronization status: Local synchronization of all data subscription topics in the backup monitoring center 30 has been completed, and data distribution can be carried out directly.

[0088] In practice, the agent management unit 43 can also be divided into at least two sub-modules, for example, Figure 1B The diagram shows a structural schematic of a multi-monitoring center system implementing FAS as an example of this application. Figure 1B As shown, the agent management unit 43 may include an agent monitoring submodule 431 and an agent control submodule 432. The agent monitoring submodule 431 is used to monitor the operational health status of the main agent unit 41 and the at least one backup agent unit 42 in real time. When a fault is detected in the main agent unit 41, the abnormal status is reported to the agent control submodule 432. The agent control submodule 432 intelligently decides which agent unit is currently executing the data scheduling and distribution task based on the operational health status of the at least one backup agent unit 42, and issues scheduling instructions to the corresponding agent unit.

[0089] Based on the indirect communication architecture of the agent module 40, the remote fire alarm monitoring center can be directly extended in this embodiment. It is only necessary to complete the communication docking and data subscription topic between the remote monitoring center and the agent module 40 to realize remote fire alarm monitoring in different locations.

[0090] Figure 2 This is an exemplary structural diagram of a multi-monitoring center system for implementing FAS provided in other embodiments of this application.

[0091] Figure 2 The illustrated embodiments and Figure 1A and Figure 1B The difference between the embodiments is as follows: Figure 1A and Figure 1B In the illustrated embodiment, the main monitoring center 20 is connected to the FAS device layer 10 through at least one communication link and receives data from the FAS device layer 10, and then synchronizes the data to the agent module 40. Figure 2 In the illustrated embodiment, the agent module 40 is connected to the FAS device layer 10 through at least one communication link and receives data from the FAS device layer 10, and then synchronizes the data to the main monitoring center 20.

[0092] exist Figure 2 In the illustrated embodiment, direct communication between the proxy module 40 and the FAS device layer 10 can be achieved based on the existing communication ports and basic configuration of the FAS device layer 10. Furthermore, the data transmission from the FAS device layer 10 to the proxy module 40 can maintain the same data transmission method as that between the FAS device layer 10 and the main monitoring center 20. All protocol adaptation and data parsing work can be completed on the proxy module 40 side, so as to maintain the CPU, communication and other performance of the FAS device layer 10 without any additional loss.

[0093] exist Figure 2 In the illustrated embodiment, lightweight query and status confirmation commands from the main monitoring center 20 and each backup monitoring center 30 are forwarded to the FAS device layer 10 by the proxy module 40, and feedback data from the FAS device layer 10 is also transmitted back to the corresponding monitoring center via the proxy module 40.

[0094] exist Figure 2 In the embodiment shown, the agent module 40 may also include only one agent unit, or it may also include: a main agent unit 41, at least one backup agent unit 42 and an agent management unit 43.

[0095] As can be seen, in this embodiment of the application, an indirect communication connection between the FAS device layer and at least one backup monitoring center is established by deploying an agent module. The data scheduling and distribution operations of the backup monitoring center are all performed by the agent module, and the FAS device layer does not need to add any communication load or configuration operations. Even if the number of backup monitoring centers continues to increase, it will not affect the existing configuration of the FAS device layer, nor will it increase the physical wiring of the FAS device layer. That is, the hardware performance of the FAS device layer will not suffer any loss, thus realizing lossless expansion of the FAS device layer.

[0096] The above describes in detail the system for implementing a multi-monitoring center of a fire alarm system in the embodiments of this application. The method for implementing a multi-monitoring center of a fire alarm system in the embodiments of this application will now be described in detail. The system for implementing a multi-monitoring center of a fire alarm system in the embodiments of this application can be used to implement the method for implementing a multi-monitoring center of a fire alarm system in the embodiments of this application. For details not disclosed in detail in the method embodiments of this application, please refer to the corresponding descriptions in the system embodiments of this application; they will not be repeated here.

[0097] Figure 3 An exemplary flowchart illustrating a method for implementing a multi-monitoring center fire alarm system according to an embodiment of this application is shown. The fire alarm system includes: a FAS (Fire Alarm System) equipment layer, a main monitoring center, and at least one backup monitoring center. Figure 3 As shown, the method may include the following processing:

[0098] Step S31: Deploy an agent module in the fire alarm system, and establish an indirect communication connection between the FAS device layer and at least one backup monitoring center through the agent module.

[0099] Step S32: The agent module synchronizes data from the FAS device layer with the main monitoring center and schedules and distributes the data to each backup monitoring center.

[0100] In some implementations, the main monitoring center is connected to the fire alarm system equipment layer via at least one communication link. Accordingly, the synchronization of data from the fire alarm system equipment layer between the agent module and the main monitoring center includes: the main monitoring center receiving data from the fire alarm system equipment layer and synchronizing the data to the agent module.

[0101] In some implementations, the proxy module is connected to the fire alarm system equipment layer via at least one communication link. Accordingly, the synchronization of data from the fire alarm system equipment layer between the proxy module and the main monitoring center includes: the proxy module receiving data from the fire alarm system equipment layer and synchronizing the data to the main monitoring center.

[0102] In some implementations, the method further includes: the agent module receiving and maintaining data subscription topics for each backup monitoring center, or the agent module pre-configuring and maintaining data subscription topics for each backup monitoring center. Accordingly, distributing the data to each backup monitoring center involves: distributing the data to each backup monitoring center according to the data subscription topics of each backup monitoring center.

[0103] In some implementations, deploying the agent module in the fire alarm system includes: deploying a main agent unit, at least one backup agent unit, and an agent management unit in the fire alarm system; the agent management unit monitors the operational health status of the main agent unit and the at least one backup agent unit in real time, and intelligently decides which agent unit is currently executing the data scheduling and distribution task based on the operational health status, and issues scheduling instructions to the corresponding agent unit.

[0104] Figure 4 This is a schematic diagram of the structure of a device for implementing a multi-monitoring center of a fire alarm system, as described in an embodiment of this application. Figure 4 As shown, the device may include at least one memory 401 and at least one processor 402. Additionally, it may include other components, such as communication ports. These components communicate via a bus 403.

[0105] At least one memory 401 is used to store computer programs. In addition, at least one memory 41 may also store an operating system, etc. Operating systems include, but are not limited to: Android operating system, Symbian operating system, Windows operating system, Linux operating system, etc.

[0106] At least one processor 402 is used to read and execute the computer program to implement the method for implementing a multi-monitoring center of a fire alarm system as described in the embodiments of this application. The processor 402 can be a CPU, processing unit / module, ASIC, logic module, or programmable gate array, etc. It can receive and send data through the communication port.

[0107] Those skilled in the art will recognize that the descriptions in the embodiments of this application are merely exemplary and are not intended to limit the scope of protection of the embodiments of this application.

[0108] It should be noted that not all steps and modules in the above processes and structural diagrams are mandatory; some steps or modules can be omitted as needed. The execution order of the steps is not fixed and can be adjusted as required. The division of modules is merely for the convenience of description and functional division. In actual implementation, a module can be implemented by multiple modules, and the functions of multiple modules can also be implemented by the same module. These modules can be located in the same device or in different devices.

[0109] It is understood that the modules in the above embodiments can be purely software modules or hardware modules, and hardware modules can be implemented mechanically or electronically. For example, a hardware module may include specially designed permanent circuits or logic devices (such as dedicated processors, such as FPGAs or ASICs) to perform specific operations. A hardware module may also include programmable logic devices or circuits (such as general-purpose processors or other programmable processors) temporarily configured by software to perform specific operations. The specific method used to implement the hardware module—whether it is mechanical, a dedicated permanent circuit, or a temporarily configured circuit (such as one configured by software)—can be determined based on cost and time considerations.

[0110] Furthermore, this application embodiment also provides a computer program product, including a computer program that can be executed by a processor to implement the method for implementing a multi-monitoring center of a fire alarm system as described in this application embodiment. This application embodiment also provides a computer-readable storage medium storing a computer program that can be executed by a processor to implement the method for implementing a multi-monitoring center of a fire alarm system as described in this application embodiment. Specifically, a system or device equipped with a storage medium can be provided, on which software program code implementing the functions of any of the above embodiments is stored, and the computer (or CPU or MPU) of the system or device can read and execute the program code stored in the storage medium. Furthermore, the operating system or other system operating on the computer can perform some or all of the actual operations through instructions based on the program code. The program code read from the storage medium can also be written to a memory located in an expansion board inserted into the computer or to a memory located in an expansion unit connected to the computer. Subsequently, the CPU or other system installed on the expansion board or expansion unit can execute some or all of the actual operations based on the instructions of the program code, thereby implementing the functions of any of the above embodiments. Storage media implementations for providing program code include USB, floppy disk, hard disk, magneto-optical disk, optical disk (such as CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD+RW), magnetic tape, non-volatile memory cards, and ROM, etc. Alternatively, program code can be downloaded from a server computer via a communication network.

[0111] In this embodiment, an indirect communication connection between the FAS device layer and at least one backup monitoring center is established by deploying an agent module. The data scheduling and distribution operations of the backup monitoring center are all performed by the agent module, and the FAS device layer does not need to add any communication load or configuration operations. Even if the number of backup monitoring centers continues to increase, it will not affect the existing configuration of the FAS device layer, nor will it increase the physical wiring of the FAS device layer. That is, the hardware performance of the FAS device layer will not suffer any loss, thus realizing lossless expansion of the FAS device layer.

[0112] Furthermore, since no configuration updates are required at the FAS device layer, and no consultation with end users is needed regarding configuration changes, the deployment cycle for multiple monitoring centers is significantly shortened, saving implementation time. Because there is no need to find idle physical ports at the FAS device layer for backup monitoring centers, nor to add any physical cable connections, the hardware costs and operational complexity of the project are reduced.

[0113] Furthermore, since the CPU performance of the main monitoring center is usually much higher than that of the FAS device layer, and the communication rate between monitoring centers is not limited by the performance of the FAS device layer hardware, by deploying the agent module on the main monitoring center, utilizing the existing hardware resources of the main monitoring center, and relying on the high-performance CPU and existing communication links of the main monitoring center, fire alarm emergency information can be displayed in the backup monitoring center more quickly, which greatly reduces information latency compared to traditional solutions, and there is no need to add a new independent node.

[0114] In addition, by deploying the agent module, the remote monitoring center can be rapidly expanded simply by deploying a backup monitoring center on the remote node and connecting it with the agent module, which has strong industrial applicability.

[0115] Finally, by implementing a redundant design for the primary and backup agent modules, combined with intelligent scheduling by the agent management unit, single points of failure in agent nodes can be effectively avoided, ensuring the stable operation of the entire FAS system and improving system robustness. Furthermore, by storing data subscription topics on both agent nodes through a backup monitoring center, and with only one agent node actually providing the service, redundant data in the communication lines is avoided, improving the utilization rate of the communication links.

[0116] Those skilled in the art will understand that the features described in the various embodiments and / or claims disclosed in this application can be combined and / or combined in various ways, even if such combinations or combinations are not explicitly described in this application. In particular, without departing from the spirit and teachings of this application, the features described in the various embodiments and / or claims of this application can be combined and / or combined in various ways, and all such combinations and / or combinations fall within the scope of this application.

Claims

1. A system for realizing multiple monitoring centers of a fire alarm system, characterized in that, include: Fire alarm system equipment layer (10); Main monitoring center (20); At least one backup monitoring center (30); and The proxy module (40) is used to establish an indirect communication connection between the fire alarm system equipment layer (10) and the at least one backup monitoring center (30), synchronize data from the fire alarm system equipment layer (10) with the main monitoring center (20), and schedule and distribute the data to each backup monitoring center.

2. The system for realizing a multi-monitoring center for a fire alarm system according to claim 1, characterized in that, The main monitoring center (20) is connected to the fire alarm system equipment layer (10) through at least one communication link, for receiving data from the fire alarm system equipment layer (10) and synchronizing the data to the agent module (40); or, The agent module (40) is connected to the fire alarm system equipment layer (10) through at least one communication link, and is used to receive data from the fire alarm system equipment layer (10) and synchronize the data to the main monitoring center (20).

3. The system for realizing a multi-monitoring center for a fire alarm system according to claim 1, characterized in that, The agent module (40) is further used to receive and maintain the data subscription topics of each backup monitoring center (30) or the agent module (40) pre-configures and maintains the data subscription topics of each backup monitoring center (30), and then dispatches and distributes the data to each backup monitoring center (30) according to the data subscription topics of each backup monitoring center (30).

4. The system for implementing a multi-monitoring center fire alarm system according to any one of claims 1 to 3, characterized in that, The proxy module (40) includes: The main agent unit (41) is used to establish an indirect communication connection between the fire alarm system equipment layer (10) and the at least one backup monitoring center (30), synchronize data from the fire alarm system equipment layer (10) with the main monitoring center (20), and schedule and distribute the data to each backup monitoring center (30). At least one backup agent unit (42) is configured to form a primary-backup agent redundancy architecture with the primary agent unit (41); and The agent management unit (43) is used to monitor the operational health status of the main agent unit (41) and the at least one backup agent unit (42) in real time, and intelligently decide the agent unit currently executing the data scheduling and distribution task based on the operational health status, and issue scheduling instructions to the corresponding agent unit.

5. A method for implementing a multi-monitoring center for a fire alarm system, characterized in that, include: A proxy module is deployed in the fire alarm system, and the proxy module establishes an indirect communication connection between the fire alarm system equipment layer and at least one backup monitoring center; The agent module synchronizes data from the fire alarm system equipment layer with the main monitoring center and schedules and distributes the data to each backup monitoring center.

6. The method for implementing a multi-monitoring center for a fire alarm system according to claim 5, characterized in that, The main monitoring center is connected to the fire alarm system equipment layer through at least one communication link; The synchronization of data from the fire alarm system equipment layer between the agent module and the main monitoring center includes: the main monitoring center receiving data from the fire alarm system equipment layer and synchronizing the data to the agent module.

7. The method for implementing a multi-monitoring center for a fire alarm system according to claim 5, characterized in that, The agent module is connected to the fire alarm system device layer through at least one communication link; The synchronization of data from the fire alarm system equipment layer between the proxy module and the main monitoring center includes: the proxy module receiving data from the fire alarm system equipment layer and synchronizing the data to the main monitoring center.

8. The method for implementing a multi-monitoring center for a fire alarm system according to claim 5, characterized in that, Further includes: The proxy module receives and maintains the data subscription topics of each backup monitoring center, or the proxy module pre-configures and maintains the data subscription topics of each backup monitoring center. The process of distributing the data to each backup monitoring center involves distributing the data to each backup monitoring center according to the data subscription topics of each backup monitoring center.

9. The method for implementing a multi-monitoring center for a fire alarm system according to any one of claims 5 to 8, characterized in that, The deployment of the agent module in the fire alarm system includes: The fire alarm system is equipped with a main agent unit, at least one backup agent unit, and an agent management unit. The agent management unit monitors the operational health status of the main agent unit and the at least one backup agent unit in real time, and intelligently decides which agent unit is currently executing the data scheduling and distribution task based on the operational health status, and issues scheduling instructions to the corresponding agent unit.

10. A device for implementing a multi-monitoring center in a fire alarm system, characterized in that, include: At least one memory (401) stores a computer program; as well as At least one processor (402) is configured to read and execute the computer program to implement the method for implementing a multi-monitoring center of a fire alarm system as claimed in any one of claims 5 to 9.

11. A computer-readable storage medium storing computer instructions; characterized in that, The computer instructions can be executed by at least one processor to implement the method for implementing a multi-monitoring center of a fire alarm system as described in any one of claims 5 to 9.

12. A computer program product, comprising a computer program; characterized in that, The computer program can be executed by at least one processor and implement the method for implementing a multi-monitoring center of a fire alarm system as described in any one of claims 5 to 9.

Images