Fire-fighting wireless sensor remote monitoring system

Abstract

The invention is suitable for the field of fire fighting, and provides a fire-fighting wireless sensor remote monitoring system, the system comprises a protocol analysis module, and a multi-protocol adaptation engine in the protocol analysis module comprises private protocol analysis, Haikang fire-fighting cloud http push data analysis, NB-IoT protocol analysis, GB26875.3-2011 protocol analysis and standardized data conversion; in the private protocol analysis, an equipment communication frame structure is analyzed through reverse engineering, and a data mapping rule is defined; analysis of Haikang fire-fighting cloud http pushed data: docking a Haikang fire-fighting cloud platform API, and analyzing JSON data; nB-IoT protocol analysis: NB-IoT device data is analyzed based on a CoAP / LwM2M protocol, parameters are extracted, and the parameters comprise pressure and liquid level; and standardized data conversion: uniformly converting each protocol data into a JSON format. The protocol compatibility is improved; the real-time performance is obviously optimized; the hardware decoupling is flexible; and low-cost expansion is realized.

Description

Technical Field

[0001] The present invention relates to the field of fire protection, and in particular to a fire protection wireless sensor remote monitoring system. Background Art

[0002] Existing fire equipment signal monitoring has the following pain points: poor protocol compatibility: it is unable to simultaneously parse data from multiple source protocols such as proprietary protocols, OneNet, NB-IoT, and GB26875.3-2011; lack of data standardization: data from different protocols are not uniformly converted. For example, OneNet's LwM2M format, the JSON format pushed by Hikvision Fire Cloud, and the binary frame of GB26875.3-2011 cannot be directly connected; strong hardware dependence: the parsing process is bound to the hardware interface (such as serial port and network port), making it difficult to adapt to different device access methods. Summary of the Invention

[0003] The present invention provides a fire protection wireless sensor remote monitoring system to solve the technical problems mentioned in the background technology.

[0004] Fire protection wireless sensor remote monitoring system, the system includes:

[0005] The protocol parsing module includes a multi-protocol adaptation engine, which includes private protocol parsing, Hikvision Fire Cloud HTTP push data parsing, NB-IoT protocol parsing, GB26875.3-2011 protocol parsing and standardized data conversion;

[0006] Among them, private protocol analysis: analyze the device communication frame structure through reverse engineering and define data mapping rules;

[0007] Hikvision Fire Protection Cloud HTTP push data analysis: connect to Hikvision Fire Protection Cloud Platform API and parse JSON data;

[0008] NB-IoT protocol parsing: Parses NB-IoT device data based on the CoAP / LwM2M protocol and extracts parameters such as pressure and liquid level.

[0009] GB26875.3-2011 protocol parsing: parsing binary frames and converting them into structured data;

[0010] Standardized data conversion: Convert all protocol data into JSON format.

[0011] As a further technical solution of the present invention, the data processing flow of the system is as follows:

[0012] Signal access: Receive data of different protocols through API interface, MQTT subscription, serial port, etc.

[0013] Protocol identification: automatically determine the data source protocol;

[0014] Rule parsing: Call the corresponding protocol parsing engine and extract valid data according to preset rules;

[0015] Standardized output: converted to a unified JSON format and stored in a message queue (kafka) for subsequent processing;

[0016] Anomaly judgment: Detect data anomalies in real time based on threshold rules.

[0017] As a further technical solution of the present invention, a visual interface is provided for configuring private protocol parsing rules, supporting the setting of frame header identifiers, data field offsets, and conversion algorithms.

[0018] Beneficial effects achieved by the present invention:

[0019] Improved protocol compatibility: Supports analysis of multiple source protocols, including proprietary protocols, OneNet, NB-IoT, and GB26875.3-2011, and is compatible with pressure gauges, liquid level meters, and anemometers from manufacturers such as Hikvision.

[0020] Significantly improved real-time performance: NB-IoT device data latency has been reduced from 10 minutes to within 500ms, meeting fire emergency response requirements.

[0021] Flexible hardware decoupling: Pure software parsing architecture, independent of specific hardware interfaces, supports cloud or edge deployment;

[0022] Low-cost expansion: When adding a new protocol, only the parsing rules need to be configured, without the need for hardware modification, which greatly reduces the adaptation cost. DETAILED DESCRIPTION

[0023] To make the purpose, technical solutions, and advantages of the embodiments of the present invention more clear, the technical solutions in the embodiments of the present invention are clearly and completely described below. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0024] In the description of the present invention, the terms "first" and "second" are used for descriptive purposes only and should not be understood to indicate or imply relative importance or implicitly specify the number of the technical features indicated. Therefore, a feature specified as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of the present invention, "plurality" means two or more, unless otherwise specifically defined.

[0025] An embodiment of the present invention provides a fire protection wireless sensor remote monitoring system, the system comprising:

[0026] The protocol parsing module includes a multi-protocol adaptation engine, which includes private protocol parsing, Hikvision Fire Cloud HTTP push data parsing, NB-IoT protocol parsing, GB26875.3-2011 protocol parsing and standardized data conversion;

[0027] Among them, private protocol analysis: analyze the device communication frame structure through reverse engineering and define data mapping rules;

[0028] For example, after the Shanying user configures the communication with the server, the server receives the TCP data packet and converts it to hexadecimal. Part of the log is as follows:

[0029] 2025-07-05 22:59:19.047 INFO [channelRead,41] - Packet: 5353482D322E302D6C69627373685F302E31312E310D0A

[0030] 2025-07-05 23:00:21.864 INFO [channelRead,41] - Packet: 5353482D322E302D6C69627373685F302E31312E310D0A

[0031] 2025-07-05 23:01:25.630 INFO [channelRead,41] - Packet: 5353482D322E302D6C69627373685F302E31312E310D0A

[0032] 2025-07-05 23:02:30.663 INFO [channelRead,41] - Packet: 5353482D322E302D6C69627373685F302E31312E310D0A

[0033] 2025-07-05 23:03:36.294 INFO [channelRead,41] - Packet: 5353482D322E302D6C69627373685F302E31312E310D0A

[0034] 2025-07-05 23:04:50.060 INFO [channelRead,41] - Packet: 5353482D322E302D6C69627373685F302E31312E310D0A

[0035] 2025-07-05 23:06:00.741 INFO [channelRead,41] - Packet: 5353482D322E302D6C69627373685F302E31312E310D0A

[0036] 2025-07-05 23:07:07.568 INFO [channelRead,41] - Packet: 5353482D322E302D6C69627373685F302E31312E310D0A

[0037] You can see that the same data packet is transmitted every 1 minute or so. If the data packet remains unchanged after a power outage and restart, it can be used as a heartbeat packet.

[0038] When different numbers are configured on the transmission line, some bits of the data packet will change. For example, 5353482D322E302D6C69627373685F302E31312E310D0A will become 5353482D422F302D6C69627373685F302E31312E310D0A.

[0039] 322E and 422F are the transmission number fields. You can try using big-endian / little-endian or converting to a binary array in forward / reverse order and converting to decimal. Once the data assembly rules are determined, modify the transmission number for testing. Other data packets such as fire alarms are processed in the same way. This is the specific process and steps for reverse engineering and analyzing device communication frames.

[0040] Hikvision Fire Protection Cloud HTTP push data analysis: connect to Hikvision Fire Protection Cloud Platform API and parse JSON data;

[0041] The following is an example of a JSON packet:

[0042] {"fps":{"msgList":[{"msgType":"980008","body":{"notifyType":null,"data":[{"resourceID":"1099015937377193985","resourceSerial":"860586062822827","unitName":"Bo Run Yuan Tong","companyName":"Xinjiang Wen Teng Information Technology Co., Ltd.","monitorPhase":0,"resourceName":"Dormitory Building Fire Hydrant","monitorValue":"100" ,"type":1,"monitorState":"1","companyID":"984376280408838145","monitorType":"400001","monitorUnit":"%","systemType":"500005","unitID":"987410646563225600","location":"Tuha Oil Base, Building 3, Block 9, Oil Base, Oil New Town Street, Yizhou District, Hami City","minThresholdValue":20,"happenTime":"2025-06-25T00:00:01.071+08:00","resourceType":"600007"},{"resourceID":"1099015937377193985","resourceSerial":"860586062822827","unitName":"Bo Run Yuan Tong","companyName":"xx Information Technology Co., Ltd.","monitorPhase":0, "remark":"{\"eclValue\":0,\"pciValue\":301,\"snrValue\":5,\"rsrpValue\":-99}","resourceName":"Fire hydrant in dormitory building","monitorValue":"2", "type":1,"monitorState":"1","companyID":"984376280408838145","monitorType":"400002","monitorUnit":"","systemType":"500005","unitID":"987410646563225600","location":"Tuha Oil Base, Building 3, Block 9, Oil Base, Oil New Town Street, Yizhou District, Hami City", "happenTime":"2025-06-25T00:00:01.071+08:00","resourceType":"600007"},{"resourceID":"1099015937377193985","resourceSerial":"860586062822827","unitName":"Bo Run Yuan Tong","companyName":"Xinjiang Wen Teng Information Technology Co., Ltd.","monitorPhase":0,"resourceName":"Dormitory Building Fire hydrant","monitorValue":"0.15","type":1,"monitorState":"0","companyID":"984376280408838145","monitorType":"400004","monitorUnit":"MPa","systemType":"500005","unitID":"987410646563225600","location":"Tuha Oil Base, Building 3, Block 9, Oil Base, Oil New Town Street, Yizhou District, Hami City", "happenTime":"2025-06-25T00:00:01.071+08:00","resourceType":"600007"}],"dataType":"980008101"}}]}};.

[0043] The msgtype value list is as follows Table 1:

[0044] Table 1

[0045]

[0046] The resourceType value list is as follows in Table 2:

[0047] Table 2

[0048]

[0049]

[0050] The systemType value list is as follows in Table 3:

[0051] Table 3

[0052]

[0053] Based on these three lists, we can know that this JSON data packet is the real-time monitoring data reported by the fire hydrant collection terminal in the fire water system. The data includes the equipment power (100%), communication signal (2dB) and current monitoring value (0.15MPa);

[0054] NB-IoT protocol parsing: Parses NB-IoT device data based on the CoAP / LwM2M protocol and extracts parameters, including pressure and liquid level (such as sprinkler pump pressure data);

[0055] GB26875.3-2011 protocol analysis: Strictly follow national standards, parse binary frames and convert them into structured data (such as Hikvision Smart Water Collection Terminal, etc.).

[0056] GB26875.3 data packet: similar to 4040972801010b300c0707191f01000000000100000000000800021c010b300c070719e52323;

[0057] Private protocol: Similar to GB data packet, but with different data bit definitions;

[0058] Hikvision Fire Protection Cloud push: Json;

[0059] Standardized data conversion: convert all protocol data into JSON format. Example:

[0060] json

[0061] {

[0062] "protocolType": "oneNet", / / Original protocol type

[0063] "deviceType": "liquidLevelSensor", / / Device type (liquid level sensor)

[0064] "deviceId": "HIK-LV-001", / / Device ID

[0065] "value": 2.3, / / value (m)

[0066] "unit": "m", / / unit

[0067] "threshold": {"low":0.5,"high":3.0}, / / threshold range

[0068] "timestamp": "2025-06-10 10:30:22", / / timestamp

[0069] "alarmLevel": 0 / / Alarm level

[0070] }.

[0071] In this embodiment, the data processing flow of the system is as follows:

[0072] Signal access: Receive data of different protocols through API interface, MQTT subscription, serial port, etc.

[0073] Protocol identification: Automatically determine the data source protocol (e.g., identifying GB26875.3-2011 data through different request ports, and identifying OneNet and Hikvision Fire Cloud data through URL paths);

[0074] Rule parsing: Call the corresponding protocol parsing engine and extract valid data according to preset rules;

[0075] Standardized output: converted to a unified JSON format and stored in a message queue (kafka) for subsequent processing;

[0076] Abnormal judgment: Real-time detection of data abnormalities based on threshold rules (e.g., generating an alarm when the liquid level is <0.5m or >3.0m).

[0077] In this embodiment, a visual interface is provided for configuring private protocol parsing rules, and supports setting frame header identifiers, data field offsets, and conversion algorithms.

[0078] The visual interface is shown in Table 4:

[0079] Table 4

[0080]

[0081] In this embodiment, the parsing rules are automatically optimized through historical data to reduce manual configuration errors.

[0082] By extracting historical data regularly and informing the DeepSeek platform of the data structure and the actual actions of the fire host, we can obtain the above configuration table, which is manually entered into the test platform to observe the analysis effect. After the analysis is correct, it is synchronized to the production environment.

[0083] In this embodiment, the NB-IoT device supports the server to attempt to actively send a wake-up instruction, shortening the data reporting delay from the default 10 minutes to ≤500ms.

[0084] In this embodiment, the multi-protocol dynamic adaptation algorithm automatically matches the parsing rules through the protocol feature library (frame header, port, message structure) to support the rapid access of new protocols;

[0085] Heterogeneous data standardization model: defines a unified data structure to shield differences between different protocols (for example, mapping OneNet's JSON and GB26875's binary frames to the same model);

[0086] Real-time guarantee mechanism: For non-real-time protocols such as NB-IoT, a closed-loop process of wake-up, collection, and reporting is designed to ensure a response to critical data within seconds.

[0087] It should be noted that, in this document, the term "comprises" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article, or apparatus that includes a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element.

[0088] The above are only preferred embodiments of the present invention and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the description of the present invention, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. Fire wireless sensor remote monitoring system, characterized by: The system includes a protocol parsing module; The protocol parsing module includes a multi-protocol adaptation engine, which includes private protocol parsing, Hikvision Fire Cloud HTTP push data parsing, NB-IoT protocol parsing, GB26875.3-2011 protocol parsing and standardized data conversion; Among them, private protocol analysis: analyze the device communication frame structure through reverse engineering and define data mapping rules; Hikvision Fire Protection Cloud HTTP push data analysis: connect to Hikvision Fire Protection Cloud Platform API and parse JSON data; NB-IoT protocol parsing: Parsing NB-IoT device data based on the CoAP / LwM2M protocol to extract parameters, including pressure and liquid level. GB26875.3-2011 protocol parsing: parsing binary frames and converting them into structured data; Standardized data conversion: Convert all protocol data into JSON format.

2. The fire protection wireless sensor remote monitoring system according to claim 1, characterized in that: The data processing flow of the system is as follows: Signal access: receiving data of different protocols; Protocol identification: automatically determine the data source protocol; Rule parsing: Call the corresponding protocol parsing engine and extract valid data according to preset rules; Standardized output: converted into a unified JSON format and stored in a message queue for subsequent processing; Abnormal judgment: Detect data abnormalities in real time based on threshold rules.

3. The fire protection wireless sensor remote monitoring system according to claim 1, characterized in that: Provides a visual interface to configure private protocol parsing rules, and supports setting frame header identifiers, data field offsets, and conversion algorithms.

Images