A fire safety remote monitoring system and method based on multi-terminal synchronization

Abstract

The application relates to the field of remote supervision management, and discloses a fire safety remote monitoring system and method based on multi-terminal synchronization, wherein the fire safety remote monitoring method based on multi-terminal synchronization comprises the following steps: modeling running objects of fire duty posts, facility maintenance positions and patrol execution areas; generating checking instructions with effective start and end times according to monitoring and scheduling strategies, and delivering the checking instructions to terminals bound to target running objects through corresponding communication channels; performing consistency comparison based on data type completeness, and generating corresponding abnormal mark records when detecting data content conflicts; taking abnormal monitoring nodes as trigger conditions, and establishing an association relationship between disposal process objects and abnormal monitoring nodes in the instantiation process; and writing rectification feedback data, processing time consumption and review results into historical state records of corresponding running objects. The application has the advantages of improving the effectiveness of social unit fire safety management.

Description

Technical Field

[0001] This invention relates to the field of remote supervision and management, specifically to a fire safety remote supervision system and method based on multi-terminal synchronization. Background Technology

[0002] Currently, in the fire safety management of social units, especially in places requiring long-term duty such as commercial complexes and warehousing and logistics parks, daily fire safety still mainly relies on manual inspections, paper registration, and regular reporting. Units typically organize regular or irregular fire safety spot checks and hazard investigations according to management requirements. These checks and summaries cover aspects such as the condition and aging of electrical wiring, the unobstructed access of safety exits and evacuation routes, the condition of fire protection facilities and equipment, the operational status of automatic fire alarm and linkage systems, the formulation and implementation of emergency plans and drills, the on-duty status of personnel in the fire control room, and annual fire inspection and facility maintenance records.

[0003] Regarding the specific aspects of duty management and hazard investigation, there are widespread problems such as the inability to perceive duty status and verify the investigation process. Taking night duty, holiday duty, or low-load operation periods as examples, it is difficult for managers to remotely confirm whether duty personnel are on duty as required, whether they have completed the inspection of electrical circuits, key areas, safety exits, and fire-fighting facilities according to the established routes and time nodes, and it is also difficult to promptly verify whether there are any cases of absenteeism, dereliction of duty, or inadequate handling of abnormalities in the fire control room. Even if some units have deployed management platforms or electronic ledger systems, their core data still mainly rely on manual entry, lacking the ability to objectively record and continuously verify inspection behavior, hazard discovery process, and rectification trigger conditions. As a result, some fire safety hazards persist for a long time during the inspection interval, and rectification is passively discovered and delayed, thus prolonging the hazard exposure cycle and increasing fire safety management risks.

[0004] Therefore, it is necessary to design a remote fire safety monitoring system and method based on multi-terminal synchronization to improve the effectiveness of fire safety management in social units. Summary of the Invention

[0005] To address the shortcomings of existing technologies, this invention provides a remote fire safety monitoring system and method based on multi-terminal synchronization, which has the advantage of improving the effectiveness of fire safety management in social units and solves the problems mentioned in the background technology.

[0006] To achieve the aforementioned goal of improving the effectiveness of fire safety management in social units, this invention provides the following technical solution: a remote fire safety monitoring method based on multi-terminal synchronization, comprising the following steps: Model the operational objects of fire duty posts, facility maintenance locations and patrol execution areas, assign a unique digital identifier to each operational object, and construct a non-reusable terminal access constraint relationship based on the digital identifier to associate the equipment terminal type and communication channel. Under the terminal access constraint relationship, a verification instruction with an effective start and end time is generated according to the regulatory scheduling strategy, and sent to the terminal bound to the target operating object through the corresponding communication channel, automatically collecting duty confirmation signals, on-site image data and facility operation parameters; The system performs structured parsing of the status data of the same target running object uploaded on different terminals, performs consistency comparison based on data type integrity, generates corresponding anomaly marker records when data content conflicts are detected, and marks the running object as an anomaly monitoring node. Using anomaly monitoring nodes as trigger conditions, the handling process object is automatically instantiated, and the association between the handling process object and the anomaly monitoring node is established during the instantiation process. The corresponding instructions are pushed to the unit's operation terminal and the mobile terminal of the management personnel through a multi-terminal synchronization mechanism. After the object in the handling process is completed, the rectification feedback data, processing time and review results are written into the historical status record of the corresponding object and the risk status identifier in the supervision platform is updated in real time.

[0007] Preferably, the process of assigning a unique digital identifier to each running object is as follows: The fire duty posts, facility maintenance locations, and patrol areas within the regulatory scope are broken down into elements, and spatial location attributes, functional attributes, and regulatory role attributes are extracted respectively. Based on attribute information, a set of descriptions of running objects is constructed, and a unique digital identifier is generated for each running object to represent its unique identity in the monitoring system. The digital identifier is then written into the basic information table of the running object.

[0008] Preferably, the process of constructing non-reusable terminal access constraint relationships is as follows: Based on the digital identifier of the object being operated, determine the corresponding device terminal type, including management terminal, mobile monitoring terminal, or unit-side operation terminal; Assign a unique communication channel identifier to each terminal type, and bind and store the communication channel identifier with the digital identifier of the running object; By introducing an identifier verification mechanism at the communication interface layer, the cross-use of communication channels between different running objects is restricted, forming a non-reusable terminal access constraint relationship.

[0009] Preferably, the process of generating verification instructions with effective start and end times based on the regulatory scheduling strategy is as follows: Under the terminal access constraint relationship, the verification task parameters are generated according to the regulatory scheduling strategy, and the task parameters are matched with the numerical identifier of the corresponding running object; Based on the matching results, set the start and end times for the verification task to form a verification instruction with clear time boundaries; The terminal access constraints that bind the verification command to the running object are encapsulated.

[0010] The preferred process for automatically acquiring duty confirmation signals, on-site image data, and facility operating parameters is as follows: The verification command is sent to the corresponding terminal through the communication channel bound to the running object; During the effective period of the verification order, the control terminal automatically collects duty confirmation signals, on-site image data and operating parameters of fire protection facilities; The collected data are appended with a digital identifier of the operating object and a collection timestamp, and then uploaded to the regulatory platform for centralized storage.

[0011] Preferably, the process of performing consistency comparison based on data type integrity is as follows: The uploaded status data is classified and parsed according to the data source terminal, and then split into an identifier field, a time field, and a content field; The status data from different terminals are merged based on the numerical identifier of the running object. Perform field-level integrity checks on the merged content fields to determine if there are any data content conflicts.

[0012] Preferably, the process of marking the running object as an anomaly monitoring node is as follows: After completing the field-level integrity verification, the fields of the same content uploaded from different terminals are compared item by item. When the status values ​​of the same field on different terminals are logically inconsistent, it is determined to be a data content conflict; Anomaly markers are generated for detected data content conflicts, and the corresponding running objects are marked as anomaly monitoring nodes.

[0013] Preferably, the process of establishing the association between the handling process object and the anomaly monitoring node during instantiation is as follows: The generation event of the anomaly monitoring node is used as a trigger signal to instantiate the corresponding handling process object from the preset handling process template; During instantiation, the numerical identifier of the anomaly monitoring node is written into the associated field of the handling process object; Through a multi-terminal synchronization mechanism, the disposal instructions in the disposal process are pushed to the unit's operating terminal and the mobile terminal of the management personnel respectively.

[0014] Preferably, the process of real-time synchronization and updating of risk status indicators in the regulatory platform is as follows: After the object of the handling process is completed, receive rectification feedback data from the unit's operation terminal and the review results from the management terminal; The execution time from instantiation to completion of the statistical processing object is used to form processing time data; The rectification feedback data, processing time, and review results are uniformly written into the historical status record of the corresponding operating object, and the risk status identifier in the supervision platform is updated simultaneously.

[0015] This invention also discloses another technical solution: a fire safety remote monitoring system based on multi-terminal synchronization, comprising: Object modeling module: Models operational objects for fire duty posts, facility maintenance locations, and patrol execution areas, and assigns a unique digital identifier to each operational object; Command scheduling module: Generates verification commands with effective time boundaries according to the regulatory scheduling strategy, and sends them to the terminal bound to the target running object through the corresponding communication channel; Status verification module: performs structured parsing and field integrity verification on status data uploaded by the same running object on different terminals, and generates anomaly marker records and marks anomaly monitoring nodes when data content conflicts are detected; Disposal generation module: Instantiates disposal process objects when triggered by an anomaly monitoring node, establishes the association between disposal process objects and anomaly monitoring nodes, and pushes disposal instructions to the unit's operation terminal and the mobile terminal of management personnel through a multi-terminal synchronization mechanism; Status update module: After the handling process is completed, the rectification feedback data, processing time and review results are written into the historical status record of the running object, and the risk status identifier in the supervision platform is updated simultaneously.

[0016] Compared with the prior art, the present invention provides a fire safety remote monitoring system and method based on multi-terminal synchronization, which has the following beneficial effects: This invention achieves precise differentiation of data sources from multiple terminals in terms of identity, channel, and responsibility boundaries by uniformly modeling the operational objects of fire duty posts, facility maintenance locations, and patrol execution areas, and establishing non-reusable terminal access constraints for each operational object. This effectively avoids the regulatory distortion problems caused by mixed terminal use, shared accounts, or unclear data sources in traditional fire supervision. It introduces a mechanism for generating and issuing verification instructions with clearly defined start and end times, giving fire duty confirmation, on-site image acquisition, and facility operation parameter acquisition clear time constraints and task boundaries, significantly improving the timeliness and traceability of remote verification. Furthermore, it performs structured parsing and data type integrity-based analysis on the status data of the same operational object uploaded from different terminals. Consistency comparison can promptly identify content conflicts between multi-source data and explicitly mark them as anomaly monitoring nodes, thereby transforming hidden management risks into regulatory objects that can be proactively captured by the system. The system automatically instantiates handling process objects based on anomaly monitoring nodes as trigger conditions and pushes handling instructions to both the unit and management sides through a multi-terminal synchronization mechanism, creating a closed-loop linkage between hazard discovery, task assignment, and rectification execution, reducing the intensity of manual intervention. Through unified archiving of rectification feedback, handling time, and review results, and real-time updates of risk status indicators, the system provides reliable data support for regulatory departments to conduct dynamic assessments, accountability investigations, and refined management, comprehensively improving the accuracy, response efficiency, and engineering implementation capabilities of remote fire safety supervision. Attached Figure Description

[0017] Figure 1 This is a schematic diagram of the method of the present invention; Figure 2 This is a schematic diagram of the structure of the present invention. Detailed Implementation

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

[0019] Example 1: Please refer to Figure 1 As shown in the figure, a method for remote fire safety monitoring based on multi-terminal synchronization in an embodiment of the present invention includes the following steps: S1: Model the operational objects of fire duty posts, facility maintenance locations and patrol execution areas, assign a unique digital identifier to each operational object, and construct non-reusable terminal access constraint relationships based on the digital identifier to associate the equipment terminal type and communication channel.

[0020] The process of assigning a unique numerical identifier to each running object in S1 is as follows: The fire duty posts, facility maintenance locations, and patrol execution areas within the regulatory scope are broken down into elements, and spatial location attributes, functional attributes, and regulatory role attributes are extracted respectively. During the initialization phase of the regulatory platform, the fire duty posts, facility maintenance locations, and patrol execution areas included in the regulatory scope are broken down item by item, and each item is regarded as a candidate operation object. For each candidate operation object, its spatial location attributes, functional attributes, and regulatory role attributes are collected. The spatial location attribute is used to describe the physical location information of the operation object in the building or area, the functional attribute is used to describe the fire management or facility operation functions undertaken by the operation object, and the regulatory role attribute is used to describe the responsibility category of the operation object in the regulatory process. By performing integrity verification on the three types of attributes, it is ensured that each candidate operation object has a set of basic attributes that can be used for differentiation. Based on attribute information, a set of operational object descriptions is constructed, and a unique digital identifier is generated for each operational object, representing its unique identity in the regulatory system. The digital identifier is written into the basic information table of the operational object. After attribute extraction, the spatial location attributes, functional attributes, and regulatory role attributes corresponding to the same candidate operational object are combined to construct a standardized operational object description record. Based on the operational object description record, a unique digital identifier is generated according to preset identifier generation rules. The identifier generation rules include at least attribute code combination and conflict verification mechanisms to avoid different operational objects generating the same identifier. After the digital identifier is generated, the digital identifier and the corresponding operational object description record are written into the operational object basic information table, and the writing results are subjected to repeatability detection and consistency verification to ensure that the digital identifier is unique in the regulatory system and can be stably referenced by data collection, status comparison, and disposal processes.

[0021] The process of constructing non-reusable terminal access constraint relationships in S1 is as follows: Based on the digital identifier of the running object, the corresponding device terminal type is determined, including management terminal, mobile monitoring terminal, or unit-side operation terminal. In the monitoring platform, the digital identifier of the running object is used as an index to read the monitoring role attribute and usage scenario attribute of the running object from the basic information table of the running object, and the accessible device terminal type is determined according to the preset terminal type matching rules. The matching rules are used to limit different monitoring roles to only correspond to specific terminal types to avoid the same running object being operated by multiple unrelated terminals at the same time. After the matching is completed, the digital identifier of the running object is bound to the determined terminal type and recorded. The consistency check is used to confirm that there is only one valid terminal type binding result for the running object, which serves as a prerequisite for the allocation of communication channels. Each terminal type is assigned an independent communication channel identifier, and the communication channel identifier is bound and stored with the digital identifier of the running object. After the terminal type is determined, an independent communication channel identifier is assigned to each terminal type, and a correspondence between the communication channel identifier and the terminal type is established in the communication configuration table. The communication channel identifier is bound and stored with the digital identifier of the running object, so that each running object can only interact with data through the bound communication channel in the system. After the binding is completed, the uniqueness of the communication channel identifier and the integrity of the binding relationship are checked to prevent the same communication channel from being assigned to multiple running objects at the same time or from the occurrence of missing binding. By introducing an identifier verification mechanism at the communication interface layer, the cross-use of communication channels between different running objects is restricted, forming a non-reusable terminal access constraint relationship. At the communication interface layer, an identifier verification mechanism is introduced for all inbound and outbound data requests. Before a data request enters business processing, the digital identifier of the running object and the communication channel identifier carried in the request are read. By comparing whether the communication channel identifier carried in the request is consistent with the channel identifier bound to the running object stored in the system, it is determined whether the request has legitimate access rights. When a mismatch or missing communication channel identifier is detected, the corresponding data request is rejected and an abnormal access log is recorded. Thus, at the system level, the cross-use of communication channels between different running objects is restricted, forming a non-reusable terminal access constraint relationship.

[0022] S2: Under the terminal access constraint relationship, a verification instruction with an effective start and end time is generated according to the supervision and scheduling strategy, and sent to the terminal bound to the target operating object through the corresponding communication channel, automatically collecting duty confirmation signals, on-site image data and facility operation parameters.

[0023] The process of generating verification instructions with effective start and end times based on the regulatory scheduling strategy in S2 is as follows: Under terminal access constraints, verification task parameters are generated according to the regulatory scheduling strategy, and the task parameters are matched with the digital identifiers of the corresponding running objects. In the regulatory scheduling strategy pre-stored on the system side, the regulatory cycle, verification frequency, verification triggering conditions and applicable object scope are defined in the form of structured rules. When the scheduling module is triggered, the digital identifiers of running objects in a valid state within the current regulatory cycle are filtered, and combined with the verification type and execution requirements defined in the scheduling strategy, a set of verification task parameters containing verification content items, execution method markers and result feedback requirements are generated. Through the digital identifier indexing mechanism, a one-to-one correspondence is established between the verification task parameters and specific running objects. The matching process uses the consistency of digital identifiers as the sole criterion for judgment. Task parameters that fail to complete the matching are automatically marked as invalid and exit the subsequent process. Based on the matching results, an effective start time and an end time are set for the verification task to form a verification instruction with clear time boundaries. After the effective matching of the verification task parameters and the numerical identifier of the running object is completed, the execution window of the verification task is time-mapped according to the time rules preset in the regulatory scheduling strategy. This includes using the scheduling trigger time or a specified reference time as the starting benchmark to calculate the effective start time of the verification instruction, and generating the corresponding end time in combination with the upper limit of verification frequency, duration constraints or deadline conditions. The effective start time and the end time are written into the verification task parameters as time boundary fields to form a verification instruction with a clear effective range. During the verification execution process, the current time and time boundary are verified in real time through a timestamp comparison mechanism. Only when the current time falls within the effective range is the verification instruction determined to be executable, thereby avoiding the verification behavior being triggered in unauthorized time periods. The verification command is encapsulated with the terminal access constraint relationship bound to the running object. After the verification command completes the time boundary configuration, the terminal access constraint relationship information corresponding to the running object is called. The numerical identifier, time boundary and verification content parameters in the verification command are jointly encapsulated with the communication channel identifier and terminal type mark already bound to the running object to form a command carrier with access constraint attributes. During the encapsulation process, by writing a terminal access constraint verification field in the command header, the verification command must pass the dual consistency verification of the communication channel identifier and the numerical identifier of the running object during the issuance and execution stages. When the command is received by an unbound terminal or a mismatched communication channel, it is automatically determined that the command does not meet the execution conditions and an abnormal access event is recorded, thereby ensuring that the verification command can only be triggered and executed under the established terminal access constraint relationship.

[0024] The process of automatically acquiring duty confirmation signals, on-site image data, and facility operation parameters in S2 is as follows: The verification command is sent to the corresponding terminal through the communication channel bound to the running object; the digital identifier of the running object contained in the verification command is read, and the communication channel identifier and terminal type information pre-bound to the running object are retrieved. During the sending phase, the platform only sends the verification command to the corresponding terminal through the communication channel. The command carries a communication channel verification field and a command validity time field. When the terminal receives the command, it compares the consistency between the communication channel identifier and the binding information stored locally. Only if the verification passes is the command successfully received. Otherwise, the command is rejected and an abnormal communication record is generated. Thus, the effective constraint on the sending path is achieved during the command transmission phase. During the effective period of the verification command, the control terminal automatically collects the duty confirmation signal, on-site image data, and fire protection facility operation parameters. After confirming that the verification command has been effectively received, the terminal starts the local time determination module based on the effective start time and end time carried in the command, and continuously compares the current system clock with the time boundary. When the current time is within the effective range of the verification command, the terminal automatically triggers the corresponding data acquisition unit according to the acquisition rules defined in the command. The duty confirmation signal is obtained through the duty personnel's operation confirmation, identity medium sensing, or status button feedback. On-site image data is captured or short-term collected by the camera equipment bound to the terminal at a preset angle. The fire protection facility operation parameters are read through the facility control interface or sensor acquisition module to read the real-time operating status. If the current time exceeds the effective range, the terminal automatically stops the acquisition behavior to avoid the generation of invalid or unauthorized data. The collected data is appended with a digital identifier of the operating object and a collection timestamp, and then uploaded to the monitoring platform for centralized storage. After completing one or more data collections, the terminal encapsulates the acquired duty confirmation signals, image data, and facility operation parameters. During the encapsulation process, the digital identifier of the operating object and the timestamp of the data generation time are automatically written into the data. The timestamp is generated based on the terminal's local clock or a standard time calibrated by the platform. The encapsulated data packet is uploaded to the monitoring platform through a verified communication channel. During the receiving phase, the platform verifies the consistency between the digital identifier and the communication channel, as well as the rationality of the timestamp. Only the data that passes the verification is written to the centralized storage unit. Data that fails the verification is marked as abnormal collection data and archived separately, thereby ensuring the traceability and reliability of the uploaded data in terms of source, time, and object.

[0025] S3: Perform structured parsing on the status data of the same target running object uploaded on different terminals, perform consistency comparison based on data type integrity, generate corresponding anomaly marker records when data content conflicts are detected, and mark the running object as an anomaly monitoring node.

[0026] The process of performing consistency comparison based on data type integrity in S3 is as follows: The uploaded status data is classified and parsed according to the data source terminal, and then split into an identification field, a time field, and a content field. After receiving status data from different terminals, the monitoring platform classifies the data source according to the terminal type identifier and communication channel identifier carried in the data packet, and calls the data parsing template corresponding to the terminal type. During the parsing process, each piece of status data is split into an identification field to identify the identity of the operating object, a time field to represent the time of data generation, and a content field to carry specific status information. The content field is further structured according to data types such as duty confirmation, image information, or facility operation parameters. If the data cannot be completely mapped to the predefined field structure during the parsing stage, it is marked as parsing abnormal data and enters the abnormal cache area. The status data from different terminals are merged based on the numerical identifier of the running object. After completing the source classification and field splitting, the regulatory platform uses the numerical identifier of the running object as the primary index key to aggregate and merge the status data from different terminals under the same identifier, and sorts the merged data according to the time field. During the merging process, the platform sets a time alignment window to limit the effective time range for data from different terminals to participate in the same consistency comparison. Only data whose time field falls within the same alignment window is included in the same comparison set. Data that exceeds the time alignment window is not included in the consistency judgment for the time being, but is recorded separately as time offset candidate data to avoid misjudgment due to collection delay. The merged content fields undergo field-level integrity checks to determine if any data content conflicts exist. After forming a comparison set, the monitoring platform calls the corresponding field integrity check rules for different data types, checking each content field for missing fields, empty field values, or mismatched field types. If the integrity check passes, the platform performs a consistency check on the values ​​of the same field in different terminal data. When field values ​​are semantically mutually exclusive, logically incompatible, or violate preset state constraint rules, the field is determined to have a data content conflict. Once any field conflict is detected, a corresponding conflict flag is generated, and the running object corresponding to the merged data set is recorded as an anomaly monitoring object.

[0027] The process of marking a running object as an anomaly monitoring node in S3 is as follows: After completing the field-level integrity verification, the same content fields uploaded from different terminals are compared item by item. After the field-level integrity verification is passed, the regulatory platform groups the content fields according to data type and includes the same fields from different terminals that belong to the same running object into the same comparison set. For each comparison set, the field values ​​are standardized according to the predefined field semantic model and value range to eliminate format deviations caused by terminal differences. After standardization, horizontal comparison is performed item by item by field name to ensure that the fields participating in the comparison are comparable in semantic meaning and value scale. When the status values ​​of the same field on different terminals are logically inconsistent, it is determined to be a data content conflict. During the item-by-item comparison process, the regulatory platform calls the logical consistency judgment rule corresponding to each field for each field and performs cross-validation on the field values ​​of different terminals. When the field values ​​are mutually exclusive, violate the preset state combination rules, or cannot simultaneously meet the operating constraints defined in the system, the field is determined to be logically inconsistent. In order to avoid misjudgment caused by occasional noise, a continuous sampling confirmation mechanism is further introduced. Only when the same field is determined to be logically inconsistent in multiple consecutive comparison periods is it confirmed as a valid data content conflict. An anomaly marker record is generated for detected data content conflicts, and the corresponding running object is marked as an anomaly monitoring node. Once a valid data content conflict is confirmed, the monitoring platform generates an anomaly marker record for the conflict. The anomaly marker record includes, but is not limited to, the running object's numerical identifier, conflict field identifier, conflict type, and occurrence time information. The monitoring status of the running object is automatically updated based on the anomaly marker record, switching the running object from normal monitoring status to anomaly monitoring status, and marking it as an anomaly monitoring node in the monitoring platform. Running objects marked as anomaly monitoring nodes will be included in the trigger scope of the handling process, thereby realizing the automatic connection between detection and handling of anomalies.

[0028] S4: Using the anomaly monitoring node as the trigger condition, automatically instantiate the handling process object, and establish the association between the handling process object and the anomaly monitoring node during the instantiation process. Through the multi-terminal synchronization mechanism, the corresponding instructions are pushed to the unit's operation terminal and the manager's mobile terminal respectively.

[0029] In S4, the process of establishing the association between the handling process object and the anomaly monitoring node during instantiation is as follows: Using the generation event of the abnormal monitoring node as a trigger signal, the corresponding handling process object is instantiated from the preset handling process template. When the regulatory platform completes the marking of the abnormal monitoring node of the running object, an abnormal generation event is generated immediately and sent to the process scheduling module as a process trigger signal. The process scheduling module selects matching process templates from the pre-configured handling process template set according to the abnormality type, running object category and regulatory scenario. It then instantiates and generates an independent handling process object according to the node structure, step sequence and permission configuration in the selected template. During the instantiation process, a unique process identifier is assigned to the handling process object and the process start time is recorded for process execution status tracking and timeliness determination. During instantiation, the numerical identifier of the anomaly monitoring node is written into the associated field of the handling process object. At the same time as the handling process object is generated, the regulatory platform binds the anomaly monitoring node that triggers the process as the associated source object. The numerical identifier of the running object, the anomaly type identifier, and the trigger time corresponding to the anomaly monitoring node are written into the associated field of the handling process object. Through the associated field, the handling process object can continuously reference the status information of the anomaly monitoring node during execution to verify whether the rectification result matches the original anomaly conditions. The associated field verification mechanism prevents the same handling process object from being incorrectly associated with other anomaly monitoring nodes, thereby ensuring the uniqueness and traceability of the process-anomaly correspondence. Through a multi-terminal synchronization mechanism, the disposal instructions in the disposal process object are pushed to the unit's operating terminal and the mobile terminal of the management personnel respectively. After the disposal process object is instantiated and associated, the regulatory platform, based on the role permissions and terminal mapping rules defined in the disposal process object, splits the disposal instructions into instruction subsets adapted to different terminals, and pushes them to the unit's operating terminal and the management personnel's mobile terminal respectively through their respective bound communication channels. During the push process, the disposal process identifier and the abnormal monitoring node identifier are attached. The instruction receipt and status feedback mechanism detects whether the instruction has been successfully delivered and received by the terminal. If the push failure or response timeout is detected, the retry or alarm mechanism is triggered to ensure the reliable synchronous execution of the disposal instructions in the multi-terminal environment.

[0030] S5: After the object in the disposal process is completed, write the rectification feedback data, processing time and review results into the historical status record of the corresponding object and update the risk status identifier in the supervision platform in real time.

[0031] The process of real-time synchronization and updating of risk status indicators in the regulatory platform in S5 is as follows: After the execution of the disposal process object is completed, the platform receives rectification feedback data from the unit's operation terminal and review results from the management terminal. When the disposal process object enters the completion state, the regulatory platform simultaneously receives rectification feedback data submitted by the unit's operation terminal and review confirmation results submitted by the management terminal through the process status monitoring module. The rectification feedback data includes, but is not limited to, rectification completion time, rectification content description and on-site supporting information. The review results include review conclusion identifier and review timestamp. The platform performs dual verification of the data execution process identifier and the running object digital identifier. Only when both types of data match the same disposal process object will it be determined as valid input and the data reception time will be recorded. The system calculates the execution time from instantiation to completion of a process object, generating processing time data. The monitoring platform reads the process start time recorded when the process object is instantiated and obtains the corresponding completion timestamp when the process status changes to the completed status. The total execution time is calculated by performing a difference calculation on the two timestamps. The platform compares the total execution time with a preset processing timeliness threshold to determine if there is a timeout. The processing time data and the timeout determination result are written as independent fields into the process execution record. The rectification feedback data, processing time, and review results are uniformly written into the historical status record of the corresponding operating object, and the risk status identifier in the regulatory platform is updated synchronously. After completing the data validity verification and processing time calculation, the regulatory platform writes the rectification feedback data, processing time data, and review results into the historical status record table of the corresponding operating object in chronological order, and retains the association index with the disposal process object and abnormal monitoring node. The platform re-determines the current risk status of the operating object based on the review result identifier and whether the processing time exceeds the limit, and synchronously refreshes the updated risk status identifier to the real-time monitoring interface of the regulatory platform. The synchronization process is triggered by an event-driven method to ensure the consistency and timeliness of the risk status identifier in the multi-terminal display.

[0032] Example 2: As Figure 2 As shown, a fire safety remote monitoring system based on multi-terminal synchronization includes: Object modeling module: Models operational objects for fire duty posts, facility maintenance locations, and patrol execution areas, and assigns a unique digital identifier to each operational object; Command scheduling module: Generates verification commands with effective time boundaries according to the regulatory scheduling strategy, and sends them to the terminal bound to the target running object through the corresponding communication channel; Status verification module: performs structured parsing and field integrity verification on status data uploaded by the same running object on different terminals, and generates anomaly marker records and marks anomaly monitoring nodes when data content conflicts are detected; Disposal generation module: Instantiates disposal process objects when triggered by an anomaly monitoring node, establishes the association between disposal process objects and anomaly monitoring nodes, and pushes disposal instructions to the unit's operation terminal and the mobile terminal of management personnel through a multi-terminal synchronization mechanism; Status update module: After the handling process is completed, the rectification feedback data, processing time and review results are written into the historical status record of the running object, and the risk status identifier in the supervision platform is updated simultaneously.

[0033] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus.

[0034] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A method for remote monitoring of fire safety based on multi-terminal synchronization, characterized in that, Includes the following steps: Model the operational objects of fire duty posts, facility maintenance locations and patrol execution areas, assign a unique digital identifier to each operational object, and construct a non-reusable terminal access constraint relationship based on the digital identifier to associate the equipment terminal type and communication channel. Under the terminal access constraint relationship, the verification instruction with effective start and end time is generated according to the supervision and scheduling strategy, and sent to the terminal bound to the target operation object through the corresponding communication channel, automatically collecting duty confirmation signals, on-site image data and facility operation parameters; The system performs structured parsing of the status data of the same target running object uploaded on different terminals, performs consistency comparison based on data type integrity, generates corresponding anomaly marker records when data content conflicts are detected, and marks the running object as an anomaly monitoring node. Using anomaly monitoring nodes as trigger conditions, the handling process object is automatically instantiated, and the association between the handling process object and the anomaly monitoring node is established during the instantiation process. The corresponding instructions are pushed to the unit's operation terminal and the manager's mobile terminal through a multi-terminal synchronization mechanism. After the object in the handling process is completed, the rectification feedback data, processing time and review results are written into the historical status record of the corresponding object and the risk status identifier in the supervision platform is updated in real time.

2. The method for remote fire safety monitoring based on multi-terminal synchronization according to claim 1, characterized in that, The process of assigning a unique numerical identifier to each running object is as follows: The fire duty posts, facility maintenance locations, and patrol areas within the regulatory scope are broken down into elements, and spatial location attributes, functional attributes, and regulatory role attributes are extracted respectively. A set of descriptions of running objects is constructed based on attribute information, and a unique digital identifier is generated for each running object to represent its unique identity in the monitoring system. The digital identifier is then written into the basic information table of the running object.

3. The method for remote fire safety monitoring based on multi-terminal synchronization according to claim 2, characterized in that, The process of constructing non-reusable terminal access constraint relationships is as follows: Based on the digital identifier of the object being operated, determine the corresponding device terminal type, including management terminal, mobile monitoring terminal, or unit-side operation terminal; Assign a unique communication channel identifier to each terminal type, and bind and store the communication channel identifier with the digital identifier of the running object; By introducing an identifier verification mechanism at the communication interface layer, the cross-use of communication channels between different running objects is restricted, forming a non-reusable terminal access constraint relationship.

4. The method for remote fire safety monitoring based on multi-terminal synchronization according to claim 3, characterized in that, The process of generating verification instructions with effective start and end times based on the regulatory scheduling strategy is as follows: Under the terminal access constraint relationship, the verification task parameters are generated according to the regulatory scheduling strategy, and the task parameters are matched with the numerical identifier of the corresponding running object; Based on the matching results, set the start and end times for the verification task to form a verification instruction with clear time boundaries; The terminal access constraints that bind the verification command to the running object are encapsulated.

5. A method for remote fire safety monitoring based on multi-terminal synchronization according to claim 4, characterized in that, The process of automatically acquiring duty confirmation signals, on-site image data, and facility operating parameters is as follows: The verification command is sent to the corresponding terminal through the communication channel bound to the running object; During the effective period of the verification order, the control terminal automatically collects duty confirmation signals, on-site image data and operating parameters of fire protection facilities; The collected data are appended with a digital identifier of the operating object and a collection timestamp, and then uploaded to the regulatory platform for centralized storage.

6. A method for remote fire safety monitoring based on multi-terminal synchronization according to claim 5, characterized in that, The process of performing a consistency comparison based on data type integrity is as follows: The uploaded status data is classified and parsed according to the data source terminal, and then split into an identifier field, a time field, and a content field; The status data from different terminals are merged based on the numerical identifier of the running object. Perform field-level integrity checks on the merged content fields to determine if there are any data content conflicts.

7. A method for remote fire safety monitoring based on multi-terminal synchronization according to claim 6, characterized in that, The process of marking a running object as an anomaly monitoring node is as follows: After completing the field-level integrity verification, the fields of the same content uploaded from different terminals are compared item by item. When the status values ​​of the same field on different terminals are logically inconsistent, it is determined to be a data content conflict; Anomaly markers are generated for detected data content conflicts, and the corresponding running objects are marked as anomaly monitoring nodes.

8. A method for remote fire safety monitoring based on multi-terminal synchronization according to claim 7, characterized in that, The process of establishing the association between the handling process object and the anomaly monitoring node during instantiation is as follows: The generation event of the anomaly monitoring node is used as a trigger signal to instantiate the corresponding handling process object from the preset handling process template; During instantiation, the numerical identifier of the anomaly monitoring node is written into the associated field of the handling process object; Through a multi-terminal synchronization mechanism, the disposal instructions in the disposal process are pushed to the unit's operating terminal and the mobile terminal of the management personnel respectively.

9. A method for remote fire safety monitoring based on multi-terminal synchronization according to claim 8, characterized in that, The process of real-time synchronization and updating of risk status indicators in the regulatory platform is as follows: After the object of the handling process is completed, receive rectification feedback data from the unit's operation terminal and the review results from the management terminal; The execution time from instantiation to completion of the statistical processing object is used to form processing time data; The rectification feedback data, processing time, and review results are uniformly written into the historical status record of the corresponding operating object, and the risk status identifier in the regulatory platform is updated simultaneously.

10. A fire safety remote monitoring system based on multi-terminal synchronization, applied to the method described in any one of claims 1-9, characterized in that, include: Object modeling module: Models operational objects for fire duty posts, facility maintenance locations, and patrol execution areas, and assigns a unique digital identifier to each operational object; Command scheduling module: Generates verification commands with effective time boundaries according to the regulatory scheduling strategy, and sends them to the terminal bound to the target running object through the corresponding communication channel; Status verification module: performs structured parsing and field integrity verification on status data uploaded by the same running object on different terminals, and generates anomaly marker records and marks anomaly monitoring nodes when data content conflicts are detected; Disposal generation module: Instantiates disposal process objects when triggered by an anomaly monitoring node, establishes the association between disposal process objects and anomaly monitoring nodes, and pushes disposal instructions to the unit's operation terminal and the mobile terminal of management personnel through a multi-terminal synchronization mechanism; Status update module: After the handling process is completed, the rectification feedback data, processing time and review results are written into the historical status record of the running object, and the risk status identifier in the supervision platform is updated simultaneously.

Images