An integrated intelligent auxiliary method for safety management and control
By mapping dictionary matching and scaling transformation of hardware node communication messages, combined with the isolated forest algorithm and linkage control matrix, the problems of static threshold identification of explicit anomalies and control timing disorder caused by manual intervention in the existing technology are solved. Unified data processing and automated closed-loop management of heterogeneous devices are realized, improving the stability and response efficiency of the system.
Patent Information
- Application Number
- CN202611337235.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-31
- Publication Date
- 2026-11-17
AI Technical Summary
Existing safety management solutions use static thresholds to identify obvious anomalies, which cannot identify hidden deviations. Manual intervention can easily lead to control timing errors. The lack of closed-loop tracking and verification of instructions results in management disconnect and response delays under high-concurrency collaborative conditions.
By acquiring communication messages from hardware nodes, performing dictionary matching and scaling transformation of field identifiers and numerical payloads, standard state data is constructed. The topology path length is calculated using the isolated forest algorithm, safety warning events are generated, and instructions are issued through the linkage control matrix. In conjunction with the local clock, instruction tracking records are generated, and device latency is adaptively evaluated to form a complete automated closed loop.
It enables unified data processing for various heterogeneous devices, captures deep anomalies, ensures traceability and verification of control actions, improves system stability and response efficiency, and reduces manual intervention.
Smart Images

Figure CN123113535A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of control system technology, and in particular to an integrated intelligent auxiliary method for safety management and control. Background Technology
[0002] Control systems are widely used in industrial production, energy dispatching, and smart park public safety management. They primarily handle on-site equipment parameter acquisition, operational status determination, control command issuance, and execution feedback correction. They rely on various heterogeneous sensors and execution hardware to perform on-site safety management. Existing safety management solutions use fixed thresholds for direct comparison to generate anomaly alarms. After an alarm is triggered, maintenance personnel must manually analyze the alarm information, manually edit, and issue control and response commands.
[0003] The existing technology has the following drawbacks: 1. Static threshold comparison can only identify obvious anomalies of single-dimensional parameters exceeding the range, but cannot identify hidden deviations in the data. Manual intervention is also prone to causing control timing disorder. 2. After the control command is issued, there is no complete closed-loop tracking and verification process. It cannot automatically complete the acknowledgment matching and link latency assessment. Under the condition of high concurrency collaboration of multiple devices, problems such as unknown command execution status, disconnection of control and management, and delayed response are likely to occur. Summary of the Invention
[0004] The purpose of this invention is to overcome the shortcomings of the prior art and provide an integrated intelligent auxiliary method for safety management and control. This method solves the technical problems of existing safety management and control schemes, which use static thresholds to identify only explicit out-of-limit anomalies, are prone to control timing errors due to manual intervention, lack a closed-loop instruction tracking and verification mechanism, and are prone to management and control disconnection and response delays under high-concurrency collaborative working conditions.
[0005] To solve the above problems, the technical solution of the present invention is as follows: An integrated intelligent auxiliary method for safety management and control includes the following steps: S1: Obtain hardware node communication messages, extract field identifiers and numerical payloads, use a mapping dictionary to perform state matching on field identifiers and extract corresponding conversion coefficients, perform scaling transformation on numerical payloads, and construct standard state data by combining standard field names. S2: Based on standard state data, the isolated forest algorithm is used to calculate the topology path length to obtain anomaly scores. Deviation features are filtered according to preset benchmark thresholds, target device identifiers are extracted, and security warning events are constructed. S3: Based on the safety warning event retrieval linkage control matrix, obtain the action command code, generate a global sequence number with the help of the local clock, encapsulate the global sequence number, target device identifier, and action command code protocol to generate a linkage control message; S4: Parse the linkage control message to obtain the target device identifier and global sequence number, route and deliver it to the corresponding communication channel, collect the initial delivery timestamp, and generate an instruction tracking record by combining the global sequence number; S5: Based on the instruction tracking record, the feedback number and completion timestamp of the matching device acknowledgment message are recorded to assess the execution time delay, identify timeout devices through preset judgment thresholds, and build an auxiliary control scheme.
[0006] Furthermore, the standard status data includes standard field names, converted values, and device ownership identifiers; the security warning events include anomaly scores, target device identifiers, and warning levels; the linkage control messages include global sequence numbers, target device identifiers, and action command codes; the command tracking records include global sequence numbers and initial issuance timestamps; and the auxiliary control scheme includes timeout device identifiers.
[0007] Furthermore, step S1 includes the following sub-steps: S1.1: Parse the hardware node communication message to obtain the field identifier and numerical payload, compare it with the node registration directory to segment the target byte sequence, and decode and splice it to obtain the payload parsing value; S1.2: Determine the node's running state by looking up the table and mapping dictionary, retrieve the numerical conversion coefficients, and multiply the load analytical value by the conversion coefficients to obtain the scale transformation amount; S1.3: Read the standard field names from the regional library, write the scale transformation values, and package them to generate standard state data.
[0008] Furthermore, step S2 includes the following sub-steps: S2.1: Construct a splitting tree based on standard state data to perform hierarchical segmentation, obtain the topological path length, calculate the ratio of the topological path length to the splitting level, and generate the node path degree; S2.2: Combine the preset constant to obtain the mean of the binary tree, calculate the state deviation degree, and output the abnormal score through the negative exponent of the natural base. S2.3: Compare the abnormal scores with the preset benchmark threshold, filter out devices that exceed the limit, bind the target device identifier, and generate a security warning event.
[0009] Furthermore, the preset benchmark threshold is obtained by: sorting the abnormal scores of the sample set in ascending order, and taking the abnormal score corresponding to the 95th percentile as the preset benchmark threshold.
[0010] Furthermore, step S3 includes the following sub-steps: S3.1: Extract the core alarm feature identifiers of safety early warning events, match them with the linkage control matrix to obtain action command codes, and build a command scheduling set; S3.2: Read the local clock machine reading on the motherboard, multiply it by the preset bit width scaling factor, combine it with the byte capacity of the instruction scheduling set to perform bit operations and concatenate them to generate a global sequence number; S3.3: Integrate target device identifier, global sequence number, and instruction scheduling set, add message header and checksum tail, and generate linkage control message.
[0011] Furthermore, step S4 includes the following sub-steps: S4.1: Parse the linkage control message, query the preset route mapping table, obtain the corresponding channel code, and generate the channel configuration identifier; S4.2: Send messages according to the channel configuration identifier, collect the interface card clock reading, add the network delay compensation amount, and obtain the initial sending timestamp; S4.3: Serially splice the initial issued timestamp and global sequence number, calculate the CRC checksum, and establish an instruction tracing record.
[0012] Furthermore, step S5 includes the following sub-steps: S5.1: Match the feedback number of the receipt message with the global sequence number, extract the completion timestamp, and reassemble them in chronological order to generate the receipt verification sequence; S5.2: Calculate the time delay difference between the receipt verification sequence and the initial issuance timestamp to form a difference distribution vector, and obtain the root mean square to get the time delay coefficient; S5.3: Compare the time delay coefficient with the preset judgment threshold, filter out timeout device identifiers, and generate auxiliary control schemes.
[0013] Furthermore, the preset judgment threshold is obtained by: organizing the historical time delay coefficient records of the same target device, removing invalid matching records, arranging the valid records in ascending order, and taking the maximum time delay coefficient as the preset judgment threshold.
[0014] Furthermore, after generating the auxiliary control plan, it is pushed to the operation and maintenance monitoring terminal to execute the command resend or generate the equipment repair work order.
[0015] The beneficial effects of this invention are as follows: First, it performs field parsing and scale transformation on heterogeneous communication messages from different hardware nodes to construct unified standard status data, shielding data processing obstacles caused by the private protocols and inconsistent dimensions of various devices; second, it constructs a segmentation tree based on isolated forests and calculates anomaly scores based on topological path lengths, which can capture deep-seated hidden anomalies that traditional threshold comparisons cannot identify; third, it matches handling instructions through a linkage control matrix, generates global sequence numbers using a local clock to complete message encapsulation and distribution, and synchronously generates instruction tracking records with verification; fourth, it completes acknowledgment message matching and latency statistics calculation, adaptively obtains the device's preset judgment threshold, and automatically generates auxiliary control schemes. The entire method forms a complete automated closed loop, reducing manual intervention and ensuring traceability and verifiability of control actions in scenarios with a large number of heterogeneous devices operating concurrently, thereby improving overall control stability. Attached Figure Description
[0016] The invention will be further described below with reference to the accompanying drawings: Figure 1 This is a schematic diagram of the architecture of the present invention; Figure 2 This is a flowchart of the present invention. Detailed Implementation
[0017] 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.
[0018] like Figure 1 and 2 As shown, this method is deployed on a management server, including a message receiving and processing unit, a memory processing unit, a storage unit, and a network communication unit. The storage unit stores node registration lists, mapping dictionaries, area databases, linkage control matrices, preset routing mapping tables, and various historical sample data. The message receiving and processing unit interfaces with a distributed device access gateway cluster to capture binary communication messages uploaded by various heterogeneous hardware nodes on-site. The memory processing unit executes all logical operations of this method. The network communication unit completes the distribution of control messages and the reception of acknowledgment messages. All units are interconnected via a server bus. The output of the message receiving and processing unit is connected to the input of the memory processing unit. The memory processing unit and storage unit have bidirectional read / write interaction. The output of the memory processing unit interfaces with the distribution end of the network communication unit, and the acknowledgment end of the network communication unit sends data back to the message receiving and processing unit. On-site access hardware includes heterogeneous IoT devices such as temperature and humidity detection nodes, high-voltage monitoring nodes, security radar nodes, exhaust fan nodes, surveillance camera pan-tilt units, smart switches, and security gates.
[0019] A smart auxiliary method for integrated security management based on the above system includes the following steps: S1: Acquire hardware node communication messages and extract field identifiers and numerical payloads. Use a mapping dictionary to perform state matching on the field identifiers and extract the corresponding conversion coefficients. Perform scale transformation on the numerical payloads based on the conversion coefficients, merge the transformation results with standard field names, and construct standard state data. By parsing and scale-converting heterogeneous original messages, eliminate the problems of different hardware proprietary protocols and inconsistent original read dimensions, and provide a standardized input data source for subsequent unified situation assessment.
[0020] S2: Based on the standard state data, the isolated forest algorithm is used to evaluate the topological path length of the standard state data, and anomaly scores are extracted based on the topological path length. Based on a preset benchmark threshold, the anomaly scores are filtered for deviation features and the target device identifier is extracted to construct a safety warning event. By leveraging the tree segmentation logic of the isolated forest, deviation features within the data are mined to address the limitation that fixed thresholds can only identify explicit out-of-limit anomalies, locate devices with anomaly risks, and generate standardized event outputs.
[0021] S3: Based on the aforementioned safety warning event, retrieve the action command code bound to the safety warning event from the linkage control matrix, allocate a global sequence number according to the local clock, encapsulate the global sequence number, target device identifier, and action command code using a protocol, and construct a linkage control message; rely on the pre-configured linkage control matrix to complete the automatic mapping from alarm to handling command. The global sequence number can assign a unique identity to each control command, ensuring that subsequent commands are traceable throughout their entire lifecycle.
[0022] S4: Extract the target device identifier and global sequence number carried in the linkage control message, route the linkage control message to the sending communication channel bound to the target device identifier, collect the initial sending timestamp when the sending action is triggered and construct an instruction tracking record in conjunction with the global sequence number; send messages according to the device-bound channel, synchronously record the instruction sending time information, and form credential data that can be used for acknowledgment matching and traceability.
[0023] S5: Based on the instruction tracking record, obtain the feedback number and completion timestamp of the device acknowledgment message and verify and match them, evaluate the time delay between the completion timestamp and the initial issuance timestamp, perform timeout identification based on the preset judgment threshold and extract the target device identifier, and construct an auxiliary control scheme; match the device acknowledgment with the issued instruction one by one, quantify and evaluate the link and device execution delay, identify timeout abnormal devices, and output a control scheme that can be directly used for operation and maintenance business.
[0024] Furthermore, during the method flow, each business data has clearly defined constituent fields. Standard status data includes standard field names, converted values, and device ownership identifiers. Each set of data can simultaneously carry unified business fields, normalized physical values, and device ownership information, ensuring that each piece of data can be located to specific hardware. Security warning events include anomaly scores, target device identifiers, and warning levels. Anomaly scores characterize the degree to which the device deviates from the normal operating mode, target device identifiers identify risky objects, and warning levels facilitate downstream differentiation of alarm priorities. Linkage control messages include global sequence numbers, target device identifiers, and action command codes. The messages also carry tracking numbers, execution objects, and execution actions, ensuring that the device can accurately execute the message after receiving it. Command tracking records include global sequence numbers and initial issuance timestamps. These two fields combined form the source anchor for a single command. Auxiliary control schemes include timeout device identifiers and corresponding handling measures. The output results directly point to the abnormal device and executable handling actions, facilitating direct invocation by business systems.
[0025] Furthermore, step S1 includes the following sub-steps: S1.1: Obtain the field identifier and numerical payload from the hardware node communication message, compare the field identifier with the node registration directory to extract matching identifier segments, segment the target byte sequence along the overlapping identifier segments from the numerical payload, decode and concatenate the target byte sequence according to the data format specified by the communication protocol, and generate the payload parsing value. The management platform listens to the gateway buffer to capture the binary communication message uploaded by the hardware, completes field matching by comparing with the pre-stored node registration directory, accurately segments the byte segments carrying the actual measurement data, completes byte order conversion and data concatenation according to the device protocol, strips off the protocol encapsulation shell, obtains the raw physical reading, and completes the preliminary parsing of the raw message. The message parsing configuration for this step is executed according to Table 1 below.
[0026] Table 1 Hardware Node Communication Message Parsing Dictionary
[0027] S1.2: The load resolution value and the field identifier are used to determine the corresponding node's operating state by looking up the field identifier in the mapping dictionary. The numerical conversion coefficients for the corresponding node's operating state are extracted and matched. The load resolution value is multiplied by the numerical conversion coefficients to generate the scale transformation quantity. The same hardware device may have different operating states under different load conditions. The mapping dictionary pre-stores the conversion coefficients corresponding to different operating states. The original load resolution value obtained is multiplied by the corresponding conversion coefficient to complete the dimension normalization conversion, smoothing out data deviations caused by inconsistent factory reading benchmarks for different hardware. For example, the load resolution value output by the temperature and humidity sensor in the intelligent warehouse area is 2350. Looking up the table, it is determined that the device is in a normal monitoring operating state, with a corresponding numerical conversion coefficient of 0.1. After multiplication, the scale transformation quantity is obtained as 235.
[0028] S1.3: For the aforementioned scale transformation quantity, read the standard field name from the regional library, write the scale transformation quantity into the associated data bit of the standard field name, and package the standard field name and associated data bit according to the communication protocol to generate standard status data. Read the preset unified business field from the regional library, bind the converted scale transformation quantity to the standard field, complete the packaging and encapsulation according to the platform's internal communication protocol, and output standard status data with a unified format to achieve format alignment of output data from multi-source heterogeneous devices. For example, in a smart park gate entrance / exit environmental detector, the standard field name is read as the real-time temperature of the gate area, the scale transformation quantity 235 is written into the corresponding associated data bit, and the protocol packet header and footer are appended to complete the packaging, generating a complete standard status data.
[0029] Furthermore, step S2 includes the following sub-steps: S2.1: Based on the standard state data, a splitting tree is constructed to hierarchically segment the standard state data. The splitting decision value from the standard state data to the leaf node is recorded, and the splitting decision value is extracted as the topological path length. The ratio of the topological path length to the splitting level is calculated to generate the node path degree. Using the standard state dataset as input, an isolated forest splitting tree is constructed to recursively perform binary splits on the data. The higher the data anomaly, the fewer splits a data point will undergo before falling into a leaf node. This yields the topological path length. The node path degree is obtained by dividing the topological path length by the splitting level, which quantitatively represents the degree of isolation of a single data point in the tree structure. For example, the standard state data of a voltage detector undergoes 3 splitting decisions through the splitting tree, and the topological path length is equal to 3. The preset theoretical average splitting level is 10, and the calculated node path degree is 3 / 10 = 0.3.
[0030] S2.2: The node path degree is called, and the binary tree mean of the node path degree is calculated using a preset constant. The state deviation is obtained by dividing the node path degree by the binary tree mean. The negative exponent of the natural base with respect to the state deviation is calculated to generate an anomaly score. A preset constant, including Euler's constant, is introduced to eliminate calculation bias caused by the sample size. The binary tree mean is obtained, and the state deviation is obtained through division. Then, the deviation degree is mapped to the 0-1 interval through negative exponentiation to obtain the anomaly score. The higher the anomaly score, the more significant the deviation of the device's operating state from the normal mode. Continuing the previous example, the binary tree mean is calculated to be 6, and the state deviation = 0.3 ÷ 6 = 0.5. Calculation... The abnormality score was approximately 0.606.
[0031] S2.3: For the abnormal scores, obtain a preset benchmark threshold for the sample set, compare the abnormal scores with the preset benchmark threshold to filter out out-of-limit device nodes, read the target device identifier corresponding to the out-of-limit device node, and concatenate the target device identifier with the abnormal score to generate a security warning event. Compare the real-time calculated abnormal scores with the preset benchmark threshold to filter out risky devices, bind the device identifier and abnormal score information, assemble them into a security warning event, and pass it downstream to complete the identification of abnormal devices and event encapsulation.
[0032] Furthermore, the preset benchmark threshold is obtained as follows: The abnormal scores in the sample set are arranged in ascending order, and the abnormal score at the 95th percentile of the abnormal score count is taken as the preset benchmark threshold. This threshold is based on historical sample statistics and is not manually fixed. The 95th percentile value serves as the judgment boundary, which can adapt to the data distribution of actual on-site equipment operation, suppressing false alarms while ensuring that most abnormal operating conditions can be effectively detected. For example, if the sample set includes abnormal scores of 1000 devices, the abnormal score at index 950, which is 0.75, is taken as the preset benchmark threshold after ascending sorting. When the real-time abnormal score of a video surveillance camera is 0.82, which is greater than 0.75, the device is determined to be an over-limit device node. The target device identifier "Monitoring Probe A" is extracted, and the abnormal score is concatenated to generate a security warning event.
[0033] Furthermore, step S3 includes the following sub-steps: S3.1: Based on the aforementioned safety warning event, extract the core alarm feature identifier. Compare the core alarm feature identifier with the node row index of the linkage control matrix item by item, extract the action command code bound to the node row index that matches the core alarm feature identifier, and establish a command scheduling set. Parse the safety warning event to obtain the core alarm feature identifier representing the alarm type, traverse the pre-stored pre-configured plans in the linkage control matrix, match one or more action command codes that need to be executed in the corresponding alarm scenario, and integrate them into a command scheduling set with execution order to realize the automatic mapping from alarm event to handling command. See Table 2 below for an example of linkage control matrix configuration.
[0034] Table 2. Coordination Control Command Scheduling Parameters
[0035] Taking an unauthorized intrusion alarm as an example, after extracting the core alarm feature identifier, the line index code 7001 is matched to obtain the corresponding action instruction code, and the corresponding instruction scheduling set is assembled.
[0036] S3.2: Invoke the instruction scheduling set to obtain the local clock machine reading of the motherboard. Multiply the local clock machine reading by a preset bit-width scaling factor, and combine it with the byte capacity of the instruction scheduling set to generate a global sequence number. Read the machine reading of the high-precision hardware clock of the server motherboard, widen the clock value range by the preset bit-width scaling factor, and then perform bitwise operations with the byte capacity of the instruction scheduling set to generate a global sequence number. Relying on nanosecond-level clock and bit-width scaling, the problem of duplicate number conflicts among multiple instructions in high-concurrency scenarios is avoided. For example, in a high-concurrency security scenario, the motherboard local clock machine reading is 1652430000, the preset bit-width scaling factor is 1000, multiplying gives 1652430000000, the instruction scheduling set byte capacity is 512 bytes, and the combined operation yields the global sequence number 1652430000512.
[0037] S3.3: For the global sequence number, parse the security warning event to extract the target device identifier. Concatenate the target device identifier, global sequence number, and instruction scheduling set. Add a message header and a checksum tail to the concatenated data segment according to the protocol specifications to construct a linkage control message. Extract the target device identifier that needs to be handled from the security warning event. Concatenate the device identifier, global sequence number, and instruction scheduling set in sequence. Add a message header for routing and a checksum tail to ensure message transmission integrity, generating a linkage control message that can be directly sent to the field hardware. For example, for a warehouse high-temperature warning, the target device identifier is exhaust fan node B. Concatenate exhaust fan node B, global sequence number 1652430000512, and relay closing / opening instruction scheduling set in sequence, add a message header and a CRC checksum tail, and generate a linkage control message.
[0038] Furthermore, step S4 includes the following sub-steps: S4.1: Extract the target device identifier and global sequence number carried in the linkage control message, obtain the preset routing mapping table, compare the target device identifier with the node address entries in the preset routing mapping table, extract the channel code corresponding to the node address entries that overlap with the target device identifier, and generate a channel configuration identifier. Parse the target device identifier in the linkage control message, query the pre-stored routing mapping table, match the dedicated communication channel code corresponding to the hardware, generate a channel configuration identifier, and determine the network exit for message distribution. Continuing the previous example, the target device identifier, exhaust fan node B, matches the channel code 3004, dedicated communication gateway port 2, and generates a channel configuration identifier.
[0039] S4.2: For the channel configuration identifier, the linkage control message is delivered to the network port. The interface card clock reading is collected at the moment the linkage control message reaches the network port. Based on the network delay compensation amount corresponding to the channel configuration identifier, the interface card clock reading is adjusted by addition to obtain the initial delivery timestamp. The message is pushed to the corresponding network port according to the channel configuration identifier. The clock reading at the moment the message arrives at the network card port is captured. The pre-calibrated network delay compensation amount for this gateway channel is added to compensate for the inherent forwarding time of the gateway hardware, resulting in the initial delivery timestamp that represents the moment the message truly leaves the management system. In this example, the interface card clock reading at the port reached by the message is 1652430050000, and the network delay compensation amount for this channel is 200. These are added together to obtain the initial delivery timestamp 1652430050200.
[0040] S4.3: The global sequence number and the initial distribution timestamp are used to sequentially arrange the initial distribution timestamp and the global sequence number to generate a concatenated data column. A cyclic redundancy check (CRC) algorithm is used to calculate the checksum of the concatenated data column and append it to the end of the concatenated data column to establish an instruction tracking record. The timestamp and global sequence number are concatenated sequentially, and the CRC checksum is calculated and appended to the end of the data column to generate an instruction tracking record with tamper-proof capabilities and persistently stored, providing an immutable comparison basis for subsequent receipt message matching. In the example, the concatenated data column is 16524300502001652430000512, and the checksum obtained after CRC calculation is 8848. The checksum is appended to the end of the data column to complete the construction of the instruction tracking record.
[0041] Furthermore, step S5 includes the following sub-steps: S5.1: Based on the instruction tracking record, obtain the feedback number and completion timestamp of the device receipt message. Compare the feedback number with the global sequence number in the instruction tracking record, extract the completion timestamps that coincide with the feedback number, and reassemble the completion timestamps according to the time order of the overlapping points to generate a receipt verification sequence. Monitor the receipt messages transmitted back by the field hardware, extract the feedback number inside the receipt and the completion timestamp recorded after the device completes the execution, and match and compare them with the instruction tracking record stored in the database. Network transmission jitter may cause receipts to arrive out of order, so the successfully matched completion timestamps are reordered according to the original time order of the instruction, generating a receipt verification sequence with the correct time order. For example, when receiving a receipt message from an access control gate, the feedback number is equal to the global sequence number 1652430000512, corresponding to the completion timestamp 1652430055200, which is added to the receipt verification sequence after time reassembly.
[0042] S5.2: The receipt verification sequence is invoked to obtain the initial issuance timestamp. The difference between each node value in the receipt verification sequence and the initial issuance timestamp is calculated to obtain a difference distribution vector. The root mean square value of each value in the difference distribution vector is calculated to generate a time delay coefficient. The completion timestamp of each instruction in the receipt verification sequence is subtracted from the corresponding initial issuance timestamp to obtain the time delay difference for each instruction execution. All time delay differences form a difference distribution vector. The root mean square value of the vector is calculated to obtain the time delay coefficient. Root mean square calculation can mitigate the interference caused by occasional sudden time jumps, objectively reflecting the overall response performance of the equipment over a period of time. Taking the security gate of channel 2 as an example, the time delay differences obtained from two instruction receipts are 5000 and 7000, forming a difference distribution vector. After root mean square calculation... The time delay coefficient is 6082. Equipment delay assessment can be referenced in Table 3 below.
[0043] Table 3. Results of Equipment Delay Assessment and Analysis
[0044] S5.3: For the time delay coefficient, compare the time delay coefficient with a preset judgment threshold, filter out abnormal coefficient items that exceed the preset judgment threshold, extract the target device identifier mapped to the abnormal coefficient item, and merge and concatenate the target device identifier and the abnormal coefficient item to generate an auxiliary control scheme. Compare the calculated time delay coefficient with the preset judgment threshold, filter out abnormal items with excessive delay, locate the corresponding target device identifier, and concatenate and combine the device identifier and the abnormal delay value to generate a complete auxiliary control scheme.
[0045] Furthermore, the preset judgment threshold is obtained as follows: Time delay coefficient records corresponding to the same target device identifier are arranged in chronological order. Records with unmatched feedback numbers and global sequence numbers are removed. The remaining time delay coefficient records are then sorted in ascending order of value, and the maximum time delay coefficient among the sorted records is used as the preset judgment threshold. Historical delay records are maintained separately for each device. Historical records are first reviewed in chronological order, and invalid dirty data resulting from lost receipts or failed matches is removed. Valid delay records are then sorted in ascending order, and the maximum value is selected as the preset judgment threshold specific to that device. This threshold is adaptively updated based on the device's historical operating data to accommodate performance differences in different hardware. Continuing with the example of the security gate in channel 2, after cleaning, this device yields 10 valid historical delay records. The maximum time delay coefficient after ascending sorting is 5500, which is the preset judgment threshold for this device. The current time delay coefficient of 6082 is greater than 5500, indicating a timeout anomaly.
[0046] Furthermore, after completing the auxiliary control scheme, it is pushed to the operation and maintenance monitoring terminal to execute command resend or generate equipment repair work orders. The management platform's business interface reads the generated auxiliary control scheme and pushes it to the operation and maintenance monitoring terminal for display. The system automatically selects the handling logic based on the handling measures carried in the scheme. For timeouts caused by temporary link jitter, the control command is resent; for continuous timeouts caused by hardware performance degradation or equipment failure, an equipment repair work order is automatically generated to complete the closed-loop handling of anomalies. Continuing with the gate instance, an auxiliary control scheme of "device 8002 delay 6082 trigger repair mechanism" is generated, pushed to the operation and maintenance monitoring terminal, and a repair work order is automatically created.
[0047] This invention can be deployed on a smart park safety production management and control server. The server connects to a distributed device access gateway cluster. Under the gateway, heterogeneous hardware devices such as temperature and humidity detection nodes, high-voltage monitoring nodes, security radar, exhaust fan nodes, camera pan-tilt units, smart gates, and security turnstiles are mounted. Different devices use their own private communication protocols to send binary messages upwards. After the system starts, all steps of this method are continuously executed in a loop. First, step S1 is executed, where the management platform continuously listens to the gateway's receive buffer, continuously capturing communication messages uploaded by hardware nodes. Sub-step S1.1 is executed, parsing the messages to obtain field identifiers and numerical payloads, segmenting the target byte sequence according to the node registration directory, and completing decoding and splicing to output the payload parsing value. Then, step S1.2 is executed, querying the mapping dictionary to identify the current node's operating state, retrieving the corresponding numerical conversion coefficients to complete the multiplication conversion to obtain the scale transformation quantity. Step S1.3 is executed, reading the standard field names of the regional library, completing data packaging to generate standard status data. The original device messages with different protocols and units are all converted into a unified format dataset, which is continuously sent to the situation assessment stage.
[0048] Then, proceed to step S2 to perform anomaly identification on the batch of standard status data. Step S2.1 involves constructing a splitting tree in memory to perform hierarchical segmentation, calculating the topological path length corresponding to each data point, and obtaining the node path degree. Step S2.2 involves introducing a preset constant to calculate the binary tree mean, and sequentially solving for the status deviation degree and anomaly score, mapping the degree of deviation of device operation to between 0 and 1. Step S2.3 involves retrieving the historical sample set, calculating the preset benchmark threshold of the 95th percentile, comparing the anomaly score of each data point in real time, filtering out the target device identifier that exceeds the limit, encapsulating it to generate a security warning event, and outputting it externally.
[0049] Step S3 of the security warning event input process involves processing the linkage command. Step S3.1 extracts the core alarm feature identifier, retrieves the linkage control matrix to match the action command code, and constructs the command scheduling set. Step S3.2 reads the local clock reading of the server motherboard, multiplies it by the preset bit width scaling factor, and performs bit operations to generate a global sequence number based on the byte capacity of the command scheduling set, ensuring that each command number is unique in high-concurrency scenarios. Step S3.3 concatenates the target device identifier, global sequence number, and command scheduling set, adds a message header and a checksum tail, and generates a linkage control message.
[0050] The linkage control message flow proceeds to step S4 to carry out channel distribution and trace record construction. Step S4.1 parses the message and queries the preset routing mapping table to obtain the channel configuration identifier. Step S4.2 pushes the message to the corresponding network port according to the channel configuration identifier, collects the interface card clock reading, adds the network delay compensation amount, and obtains the initial distribution timestamp after correction. Step S4.3 serially concatenates the initial distribution timestamp and global sequence number, adds a cyclic redundancy checksum, generates an instruction trace record, and stores it in the storage unit for persistent storage, leaving tamper-proof traceability credentials for receipt matching.
[0051] After receiving the linkage control message, the on-site hardware completes corresponding actions such as relay switching, fan starting, and pan-tilt rotation. After the actions are completed, it sends a receipt message back to the gateway. The receipt message carries the feedback number and the completion timestamp recorded on the device side. The receipt message is sent to step S5 for closed-loop verification. Execute S5.1 to retrieve the instruction tracking record stored in the storage unit, compare the receipt feedback number with the global sequence number one by one, extract the successfully matched completion timestamps, and reassemble them according to the original distribution time sequence to obtain the receipt verification sequence to address network out-of-order issues. Execute S5.2 to obtain the difference distribution vector by subtracting each completion timestamp of the receipt verification sequence from the initial distribution timestamp, and calculate the root mean square value to obtain the time delay coefficient. Retrieve the historical time delay coefficient record of the target device, clean and remove invalid records, and take the maximum delay after ascending order as the preset judgment threshold for the device. Then execute S5.3 to compare the current time delay coefficient with the preset judgment threshold, filter the target device identifiers with excessive delay, and splice them to generate an auxiliary control scheme. The auxiliary control plan is pushed to the operation and maintenance monitoring terminal. The system automatically selects the handling path according to the plan. If there is temporary link fluctuation, the control command is automatically resent. If there is equipment hardware failure, a repair work order is automatically generated.
[0052] The entire implementation process is automatically executed by the server. From heterogeneous message access, anomaly detection and identification, linkage command generation and issuance, to receipt matching, latency assessment and automatic handling, no manual intervention is required for message parsing, alarm analysis and command issuance. The entire process can run continuously in a loop, adapting to high-concurrency business scenarios with multiple devices in industrial and park settings, and has good engineering practicality.
[0053] The embodiments described in this specification are merely examples of implementations of the inventive concept. The scope of protection of this invention should not be considered as limited to the specific forms stated in the embodiments. The scope of protection of this invention also extends to equivalent technical means that can be conceived by those skilled in the art based on the inventive concept.
Claims
1. An integrated intelligent auxiliary method for safety management and control, characterized in that, Includes the following steps: S1: Obtain hardware node communication messages, extract field identifiers and numerical payloads, use a mapping dictionary to perform state matching on field identifiers and extract corresponding conversion coefficients, perform scaling transformation on numerical payloads, and construct standard state data by combining standard field names. S2: Based on standard state data, the isolated forest algorithm is used to calculate the topology path length to obtain anomaly scores. Deviation features are filtered according to preset benchmark thresholds, target device identifiers are extracted, and security warning events are constructed. S3: Based on the safety warning event retrieval linkage control matrix, obtain the action command code, generate a global sequence number with the help of the local clock, encapsulate the global sequence number, target device identifier, and action command code protocol to generate a linkage control message; S4: Parse the linkage control message to obtain the target device identifier and global sequence number, route and deliver it to the corresponding communication channel, collect the initial delivery timestamp, and generate an instruction tracking record by combining the global sequence number; S5: Based on the instruction tracking record, the feedback number and completion timestamp of the matching device acknowledgment message are recorded to assess the execution time delay, identify timeout devices through preset judgment thresholds, and build an auxiliary control scheme.
2. The integrated intelligent auxiliary method for safety management and control according to claim 1, characterized in that, The standard status data includes standard field names, converted values, and device ownership identifiers; the security warning events include anomaly scores, target device identifiers, and warning levels; the linkage control messages include global sequence numbers, target device identifiers, and action command codes; the command tracking records include global sequence numbers and initial issuance timestamps; and the auxiliary control scheme includes timeout device identifiers.
3. The integrated intelligent auxiliary method for safety management and control according to claim 1, characterized in that, Step S1 includes the following sub-steps: S1.1: Parse the hardware node communication message to obtain the field identifier and numerical payload, compare it with the node registration directory to segment the target byte sequence, and decode and splice it to obtain the payload parsing value; S1.2: Determine the node's running state by looking up the table and mapping dictionary, retrieve the numerical conversion coefficients, and multiply the load analytical value by the conversion coefficients to obtain the scale transformation amount; S1.3: Read the standard field names from the regional library, write the scale transformation values, and package them to generate standard state data.
4. The integrated intelligent auxiliary method for safety management and control according to claim 1, characterized in that, Step S2 includes the following sub-steps: S2.1: Construct a splitting tree based on standard state data to perform hierarchical segmentation, obtain the topological path length, calculate the ratio of the topological path length to the splitting level, and generate the node path degree; S2.2: Combine the preset constant to obtain the mean of the binary tree, calculate the state deviation degree, and output the abnormal score through the negative exponent of the natural base. S2.3: Compare the abnormal scores with the preset benchmark threshold, filter out devices that exceed the limit, bind the target device identifier, and generate a security warning event.
5. The integrated intelligent auxiliary method for safety management and control according to claim 4, characterized in that, The preset benchmark threshold is obtained by sorting the abnormal scores of the sample set in ascending order and taking the abnormal score corresponding to the 95th percentile as the preset benchmark threshold.
6. The integrated intelligent auxiliary method for safety management and control according to claim 1, characterized in that, Step S3 includes the following sub-steps: S3.1: Extract the core alarm feature identifiers of safety early warning events, match them with the linkage control matrix to obtain action command codes, and build a command scheduling set; S3.2: Read the local clock machine reading on the motherboard, multiply it by the preset bit width scaling factor, combine it with the byte capacity of the instruction scheduling set to perform bit operations and concatenate them to generate a global sequence number; S3.3: Integrate target device identifier, global sequence number, and instruction scheduling set, add message header and checksum tail, and generate linkage control message.
7. The integrated intelligent auxiliary method for safety management and control according to claim 1, characterized in that, Step S4 includes the following sub-steps: S4.1: Parse the linkage control message, query the preset route mapping table, obtain the corresponding channel code, and generate the channel configuration identifier; S4.2: Send messages according to the channel configuration identifier, collect the interface card clock reading, add the network delay compensation amount, and obtain the initial sending timestamp; S4.3: Serially splice the initial issued timestamp and global sequence number, calculate the CRC checksum, and establish an instruction tracing record.
8. The integrated intelligent auxiliary method for safety management and control according to claim 1, characterized in that, Step S5 includes the following sub-steps: S5.1: Match the feedback number of the receipt message with the global sequence number, extract the completion timestamp, and reassemble them in chronological order to generate the receipt verification sequence; S5.2: Calculate the time delay difference between the receipt verification sequence and the initial issuance timestamp to form a difference distribution vector, and obtain the root mean square to get the time delay coefficient; S5.3: Compare the time delay coefficient with the preset judgment threshold, filter out timeout device identifiers, and generate auxiliary control schemes.
9. The integrated intelligent auxiliary method for safety management and control according to claim 8, characterized in that, The preset judgment threshold is obtained by: organizing the historical time delay coefficient records of the same target device, removing invalid matching records, arranging the valid records in ascending order, and taking the maximum time delay coefficient as the preset judgment threshold.
10. The integrated intelligent auxiliary method for safety management and control according to any one of claims 1 to 9, characterized in that, After generating the auxiliary control plan, it is pushed to the operation and maintenance monitoring terminal to execute the command resend or generate the equipment repair work order.
