Method, system, device and medium for multi-protocol conversion between fire alarm devices

Abstract

The application discloses a multi-protocol conversion method, system, device and medium between fire alarm devices, and belongs to the technical field of communication; wherein the method comprises the following steps: S1, loading a protocol template; S2, establishing communication with a source device; S3, original data analysis and conversion; S4, data standardization writing into a database; S5, standardized data mapping and frame construction; S6, establishing communication with a target; the system comprises the following modules: a protocol configuration module, used for storing and managing template information of all converted protocols; a data acquisition and analysis engine, used for establishing communication with the source device; a data standardization and database module, used as a data transfer hub of the system; a data mapping and encapsulation engine, used for preparing communication data for the target device; and a data sending engine, used for communicating with the target device; the application solves the problems of protocol incompatibility between new and old fire alarm devices, lack of flexible conversion mechanism and difficulty in unified access to an Internet of Things platform in the prior art.

Description

Technical Field

[0001] This invention belongs to the field of communication technology, specifically relating to a method, system, equipment, and medium for multi-protocol conversion between fire alarm devices. Background Technology

[0002] Automatic fire alarm systems, as an important component of building fire protection facilities, are widely used in various types of buildings. With the development of fire protection technology, fire alarm equipment from different brands and eras employs a variety of communication protocols. Newer equipment uses standard protocols, while older equipment largely uses manufacturer-proprietary protocols, which differ significantly in frame structure, data definition, and physical layer parameters. Because these protocols are not publicly available and have poor compatibility, direct interconnection between new and old equipment is difficult.

[0003] Protocol conversion involves not only application-layer data parsing but also frequently encounters hard barriers such as physical-layer incompatibility. A typical example is that many older devices use the RS-485 protocol, which employs a non-standard 9-bit data bit format. Modern general-purpose hardware and standard communication libraries support this poorly, creating an integration technical barrier. To integrate this heterogeneous device status information into a modern IoT platform or central monitoring system, independent interfaces need to be developed for each protocol, resulting in complex system architecture and high development and maintenance costs.

[0004] In current engineering practice, common solutions include:

[0005] Bridging between old and new protocols can be achieved through manufacturer-specific adapters or conversion modules, but this method relies on hardware and has limited scalability and versatility.

[0006] Adapting the new host by replacing the old equipment is costly, time-consuming, and may affect the stability of the system.

[0007] Some software solutions only support specific brand protocols and lack cross-brand compatibility.

[0008] Therefore, how to achieve interoperability between old and new fire alarm equipment without large-scale equipment replacement remains a common need in the industry. Summary of the Invention

[0009] This invention provides a method and system for multi-protocol conversion between fire alarm devices. It offers a configurable protocol conversion method that can adapt to the proprietary or standard protocols of various brands and types of fire alarm devices, reducing the complexity and cost of system integration. It provides a software solution that does not rely on special hardware, particularly addressing the incompatibility between non-standard physical layer protocols such as the 9-bit data bits used in older devices and modern general-purpose hardware. By constructing a data hub centered on a database, it achieves the standardization and centralized storage of heterogeneous data, providing a unified and efficient data service interface for upper-layer applications. It solves the problems of protocol incompatibility between new and old fire alarm devices, lack of flexible conversion mechanisms, incompatibility with multiple brands of hosts and older devices, and difficulty in unified access to IoT platforms in existing technologies.

[0010] To achieve the above-mentioned technical objectives, the present invention is implemented through the following technical solution:

[0011] A method for multi-protocol conversion between fire alarm devices includes the following steps:

[0012] S1: Load protocol templates, load the corresponding protocol templates from the template information of all protocols to be converted;

[0013] S2: Establish communication with the source device and collect data uploaded by the source device in real time, including at least alarm information, device status, and control command data, based on the RS-485 or Ethernet communication physical interface and the corresponding protocol template.

[0014] S3: Raw data parsing and conversion. Based on the data collected through communication established in S2, the raw data stream is parsed according to the protocol template rules, valid state points are extracted, and converted into a unified intermediate format.

[0015] S4: Data standardization is written to the database. The data parsed and converted into an intermediate format in S3 is stored in the structured database and converted into a predefined standardized data model.

[0016] S5: Standardized data mapping and frame assembly: Read standardized data from the standardized data model, map the fields in the standardized data model to the specific addresses and formats required by the target device's private protocol according to the pre-configured data mapping table, and complete message framing based on the target protocol template;

[0017] S6: Establish communication with the target, and send framed data to the target fire-fighting equipment through the RS-485 interface based on the target protocol template; during the data transmission process, the ninth bit of data is simulated by dynamically switching the parity bit to realize the simulation of special hardware protocols, thereby achieving compatibility on general hardware platforms.

[0018] Preferably, the protocol template is stored in a protocol library configuration file in JSON format, which supports dynamic addition and modification; when a new brand alarm host is connected, only its protocol template needs to be added, without modifying the core system logic.

[0019] Preferably, the logic of the original data stream parsing process is as follows:

[0020] 1) Frame synchronization: Locate complete messages using the frame header and trailer identifiers defined in the protocol template; filter out data information that contains interference;

[0021] 2) Field extraction: Parse the required loop number, address number, and event type key information in the data field according to the loaded protocol template;

[0022] 3) Verification: The integrity of the message is verified using the verification and algorithm rules in the protocol template. If the verification fails, a retransmission is requested.

[0023] 4) Format conversion: Convert the extracted information into an intermediate format to eliminate differences in the source protocol.

[0024] Preferably, the message framing is performed by loading a target protocol template and framing messages according to the rules of the target protocol template. The message framing process is as follows:

[0025] 1) Fill in the frame header and frame footer;

[0026] 2) Write the mapped function code and data field;

[0027] 3) Write the verification value according to the target protocol verification method;

[0028] 4) Add priority identifiers to messages for special scenarios.

[0029] Preferably, the standardized data model includes at least: an alarm event table, a device status table, and a control command table; the standardized data model is used for unified management of multi-protocol data.

[0030] Preferably, the process of sending the framed data to the target fire-fighting equipment must strictly follow the communication sequence in the protocol template, including the sending interval and response waiting time;

[0031] After receiving the data, the target fire-fighting equipment returns a response message. The response message is compared with the sent data. If the comparison and verification do not match, a retransmission mechanism is triggered to ensure that the fire control command is delivered accurately. The cases of mismatch include at least: response timeout and content mismatch.

[0032] Preferably, the compatibility algorithm for the ninth bit data is as follows: when sending data, calculate the parity check value of the sent data according to whether the ninth bit is 1 as defined in the protocol template, and make it match the ninth bit value defined in the protocol by dynamically switching the check method.

[0033] In serial communication using hardware that supports the SPACE / MARK parity standard eight-bit data bits, the ninth address frame is simulated as 1 by dynamically setting the serial port's parity bit to MARK; the ninth data frame is simulated as 0 by dynamically setting the serial port's parity bit to SPACE.

[0034] Another object of the present invention is to provide a multi-protocol conversion system between fire alarm devices, comprising:

[0035] The protocol configuration module is used to store and manage template information for all converted protocols. This module includes a protocol library configuration file. Each protocol template defines communication parameters including baud rate, data bits, stop bits, and parity bits, as well as message format including frame header, data field length, function code, and checksum algorithm.

[0036] The data acquisition and parsing engine is used to establish communication with the source device. According to the corresponding protocol template loaded in the protocol configuration module, it acquires the data uploaded by the fire alarm host in real time through the physical interface; it parses the raw data stream and converts it into a unified intermediate format.

[0037] The data standardization and database module, as the system's data transfer hub, mainly uses the data stored after parsing in the data acquisition and parsing engine as the database and converts it into a standardized data model. The database serves as both a buffer for protocol conversion and a source of standardized data models, thereby shielding the differences between different host protocols.

[0038] The data mapping and encapsulation engine is used to prepare communication data for the target device. It reads standardized data from the database module, completes the mapping of fields in the standardized data model to specific addresses and formats of the target device's private protocol, and completes message framing based on the target protocol template.

[0039] The data transmission engine is used to communicate with the target fire-fighting equipment. It uses a dynamic switching method of parity bits to simulate the ninth bit of data and sends framed data to the target fire-fighting equipment based on the target protocol template to achieve communication.

[0040] Another object of the present invention is to provide a multi-protocol conversion device between fire alarm devices, comprising: a processor and at least one set of memories, wherein the memories store a computer-executable program, and the processor executes the computer-executable program to complete the multi-protocol conversion method between the fire alarm devices.

[0041] Another objective of this invention is to provide a multi-protocol conversion medium between fire alarm devices, wherein the medium stores a computer-executable program, which is executed by a computer to perform a multi-protocol conversion method between the fire alarm devices.

[0042] The beneficial effects of this invention are:

[0043] With configurable protocol templates, this invention provides a system that can adapt to various fire alarm devices of different brands and communication protocols. When new types of devices need to be connected, only the configuration file needs to be added or modified without changing the program code or adding hardware, which greatly shortens the development cycle and avoids the expensive cost of repeated development for each protocol. It is particularly suitable for the renovation of old projects that include multiple brands of devices. It can also seamlessly connect with old proprietary protocol devices, avoiding system fragmentation caused by protocol inconsistencies. It achieves high versatility and flexibility, and significantly reduces integration costs and complexity.

[0044] To address the hardware-level communication barrier of "9 data bits" commonly found in older devices, this invention proposes an innovative method to simulate the 9th data bit by dynamically switching the parity bit (MARK / SPACE) in software. This enables normal communication with older devices using special protocols on standard, inexpensive general-purpose hardware such as ordinary USB to 485 converters, without the need to find or customize expensive and scarce dedicated hardware gateways. This has successfully revitalized a large number of old devices that would otherwise have been phased out, greatly saving on equipment replacement costs.

[0045] By using a central database as a data transfer hub, data collection, protocol conversion, and data forwarding are decoupled. This architecture results in a clear data flow, a single responsibility for each module, and stronger system fault tolerance. Even if a target device is temporarily offline, the data is still stored in the database and retransmitted after recovery. At the same time, the standardized data greatly facilitates access to upper-layer applications such as IoT platforms and big data analytics. It only needs to be read from the database, without needing to worry about the differences in underlying protocols, realizing "one-time collection, multiple reuse" of data. It also provides a reliable technical foundation for cross-protocol system networking and centralized supervision.

[0046] The entire conversion process is completed automatically by software, reducing manual intervention and the risk of failure caused by hardware modifications; all protocol configurations and data mapping relationships are configured through files or interfaces, and non-technical personnel can also perform daily maintenance and expansion after training, reducing the continuous dependence on professional developers and significantly reducing the long-term operation and maintenance costs of the system. Attached Figure Description

[0047] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0048] Figure 1 This is a data flow structure diagram of the multi-protocol conversion method between fire alarm devices according to the present invention;

[0049] Figure 2 This is a block diagram of the multi-protocol conversion system for fire alarm equipment rooms according to the present invention. Detailed Implementation

[0050] 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. Example

[0051] like Figure 1 As shown, the multi-protocol conversion method between fire alarm devices includes the following steps:

[0052] S1: Load protocol templates, load the corresponding protocol templates from the template information of all protocols to be converted;

[0053] To address the inconsistencies in frame structure, function codes, and verification methods among different fire-fighting equipment protocols, a protocol configuration template is constructed. This template stores the protocol templates of all fire alarm host source devices and all linkage control devices, providing a unified management system for subsequent data processing.

[0054] The protocol template mainly includes communication parameters such as baud rate, data bits, stop bits, and parity bits. It also includes the following rules specific to fire-fighting scenarios:

[0055] Message format: Clear frame header, such as the manufacturer-defined identifier 0xAA55; function code, such as 0x01 for fire alarm reporting and 0x02 for equipment failure; data field, including device address code, loop number, event type, etc.; checksum algorithm and frame tail identification;

[0056] Special field mapping: Define coding rules for alarm levels such as fire alarm, early warning, and fault, as well as device types such as smoke detectors, heat detectors, and audible and visual alarms. For example, 0x00 corresponds to fire alarm and 0x01 corresponds to fault.

[0057] Timing requirements: Some fire-fighting equipment has strict requirements on communication response time, and timeout retransmission thresholds must be defined in the protocol template;

[0058] The protocol templates are stored in a JSON-formatted protocol library configuration file, which supports dynamic addition and modification. When a new device is connected to the alarm control panel of the fire protection system, only its protocol template needs to be added, without modifying the core system logic.

[0059] S2: Establish communication with the source device and collect data including alarm information, device status, and control command data uploaded by the fire alarm host in real time based on the RS-485 or Ethernet communication physical interface and the corresponding protocol template;

[0060] S3: Raw data parsing and conversion. Based on the data collected through communication established in S2, the raw data stream is parsed according to the protocol template rules, valid state points are extracted, and the data is converted into a unified intermediate format.

[0061] The logic of the original data stream parsing process is as follows:

[0062] 1) Frame synchronization: Locate complete messages using the frame header and trailer identifiers defined in the protocol template; filter out data information that contains interference;

[0063] 2) Field extraction: Parse the required loop number, address number, and event type key information in the data field according to the loaded protocol template;

[0064] 3) Verification: The integrity of the message is verified using the verification and algorithm rules in the protocol template. If the verification fails, a retransmission is requested.

[0065] 4) Format conversion: Convert the extracted information into an intermediate format, such as key-value pairs "{device_type: smoke detector, event: fire alarm, location: circuit 3, number 15}" to eliminate source protocol differences;

[0066] S4: Standardize the data and write it into the database. Store the data that has been parsed and converted into an intermediate format in S3 into a structured database and convert it into a standardized data model that conforms to fire protection industry standards.

[0067] A standardized data model can be defined by referring to the "Standard for Construction and Acceptance of Automatic Fire Alarm Systems" (GB 50116); the aforementioned standardized data model includes:

[0068] Alarm Event Table: The alarm event table includes: event ID, unique device identifier, event type (e.g., fire alarm / fault / monitoring), event level (e.g., emergency / general), occurrence time, and processing status;

[0069] Equipment Status Table: Records the online status of the equipment, operating parameters (such as detector sensitivity), self-test results, etc.

[0070] Control command table: Stores operation commands for the target device (such as start / stop), command status (such as sent / executed), and feedback results;

[0071] As a standardized data storage hub, the structured database must retain at least one year of traceable data. It also serves as a buffer, temporarily storing data in the database when the target device is temporarily offline, and automatically resending it after the device is restored to avoid the loss of fire commands. At the same time, the database supports high-concurrency read and write operations, adapting to situations where multiple source devices report simultaneously. The database also supports redundant backups to prevent data loss or damage when no backup is available.

[0072] S5: Standardized data mapping and frame assembly. This involves reading standardized data from a standardized data model and mapping fields in the standardized data model to specific addresses and formats required by the target device's private protocol, based on a pre-configured data mapping table. For example, "event type corresponds to fire alarm" in the standardized model is mapped to "function code corresponds to 0x05, data field corresponds to 0x01" in the target linkage control device protocol; "device address is circuit 3, number 15" in the standardized model is mapped to the physical address "0x3F" of the target linkage control device; and message framing is completed based on the target protocol template.

[0073] The above-mentioned message framing is achieved by loading the target protocol template and framing messages according to the rules of the target protocol template. The message framing process is as follows:

[0074] 1) Fill in the frame header and frame tail; for example, the "0xBB66" frame header required by the target linkage control device;

[0075] 2) Write the mapped function code and data field; for example, the instruction corresponding to "start the smoke exhaust fan";

[0076] 3) Write the verification value according to the target protocol verification method;

[0077] 4) For special scenarios, add priority identifiers to the message; this embodiment gives an example of a special scenario: the target linkage control device needs to process instructions according to priority; an example of a priority identifier is given: the highest bit indicates the urgency level;

[0078] S6: Establish communication with the target, and send framed data to the target fire-fighting equipment through the RS-485 interface based on the target protocol template; during the data transmission process, the ninth bit of data is simulated by dynamically switching the parity bit to realize the simulation of special hardware protocols, thereby achieving compatibility on general hardware platforms;

[0079] The above-mentioned ninth-bit data compatibility algorithm is as follows: when sending data, calculate the parity check value of the sent data according to whether the ninth bit is 1 according to the protocol template definition, and make it match the ninth bit value defined by the protocol by dynamically switching the check method.

[0080] In serial communication using hardware that supports the SPACE / MARK parity standard eight-bit data bits, the ninth address frame is simulated to be 1 by dynamically setting the serial port parity bit to MARK; the ninth data frame is simulated to be 0 by dynamically setting the serial port parity bit to SPACE.

[0081] As a preferred implementation, the process of sending framed data to the target linkage control device must strictly follow the communication sequence in the protocol template, including the sending interval and response waiting time, to avoid the target linkage control device rejecting the data due to timing mismatch.

[0082] After receiving the data, the target linkage control device returns a response message. The response message is compared with the sent data. If the comparison and verification do not match, a retransmission mechanism is triggered to ensure that the fire control command is delivered accurately. The above-mentioned comparison and verification mismatch situations include: response timeout and content mismatch.

[0083] like Figure 2 As shown, the multi-protocol conversion system between fire alarm equipment includes:

[0084] The protocol configuration module is used to store and manage template information for all converted protocols. This module includes a protocol library configuration file. Each protocol template defines communication parameters including baud rate, data bits, stop bits, and parity bits, as well as message format including frame header, data field length, function code, and checksum algorithm.

[0085] The data acquisition and parsing engine is used to establish communication with the source device. According to the corresponding protocol template loaded in the protocol configuration module, it collects the data uploaded by the fire alarm host in real time through the physical interface; it parses the raw data stream and converts it into a unified intermediate format.

[0086] The data standardization and database module, as the system's data transfer hub, mainly uses the data stored after parsing in the data acquisition and parsing engine as the database, and converts it into a standardized data model; the database is both a buffer for protocol conversion and the source of the standardized data model, thereby shielding the differences between different host protocols;

[0087] The data mapping and encapsulation engine is used to prepare communication data for the target device. It reads standardized data from the database module, completes the mapping of fields in the standardized data model to specific addresses and formats of the target device's private protocol, and completes message framing based on the target protocol template.

[0088] The data transmission engine is used to communicate with the target device. It uses a dynamic switching method of parity bits to simulate the ninth bit of data and sends framed data to the target device based on the target protocol template to achieve communication.

[0089] System module collaboration and method data flow closed loop

[0090] When the system starts up, the data acquisition and parsing engine and the data transmission engine load the protocol templates of the source and target devices from the protocol configuration module to complete initialization; during normal operation, the data flow follows the closed loop path below:

[0091] Uplink (from source device to system):

[0092] Source devices including alarm control panel → RS485 / Ethernet → Data acquisition and parsing engine → Unified intermediate format → Data standardization and database module;

[0093] Downlink (system to target device):

[0094] Database (standardized data) → Data mapping and encapsulation engine → Message framing → Data sending engine → RS485 interface → Target linkage control device.

Claims

1. A method for multi-protocol conversion between fire alarm devices, characterized in that, Includes the following steps: S1: Load protocol templates, load the corresponding protocol templates from the template information of all protocols to be converted; S2: Establish communication with the source device and collect data uploaded by the source device in real time, including at least alarm information, device status, and control command data, based on the RS-485 or Ethernet communication physical interface and the corresponding protocol template. S3: Raw data parsing and conversion. Based on the data collected through communication established in S2, the raw data stream is parsed according to the protocol template rules, valid state points are extracted, and converted into a unified intermediate format. S4: Data standardization is written to the database. The data parsed and converted into an intermediate format in S3 is stored in the structured database and converted into a predefined standardized data model. S5: Standardized data mapping and frame assembly: Read standardized data from the standardized data model, map the fields in the standardized data model to the specific addresses and formats required by the target device's private protocol according to the pre-configured data mapping table, and complete message framing based on the target protocol template; S6: Establish communication with the target, and send framed data to the target fire-fighting equipment through the RS-485 interface based on the target protocol template; during the data transmission process, the ninth bit of data is simulated by dynamically switching the parity bit to realize the simulation of special hardware protocols, thereby achieving compatibility on general hardware platforms; The compatibility algorithm for the ninth bit data is as follows: when sending data, calculate the parity check value of the sent data according to whether the ninth bit is 1 as defined in the protocol template, and make it match the ninth bit value defined in the protocol by dynamically switching the check method. In serial communication using hardware that supports the SPACE / MARK parity standard eight-bit data bits, the ninth address frame is simulated as 1 by dynamically setting the serial port's parity bit to MARK; the ninth data frame is simulated as 0 by dynamically setting the serial port's parity bit to SPACE.

2. The multi-protocol conversion method between fire alarm devices according to claim 1, characterized in that, The protocol templates are stored in a JSON-formatted protocol library configuration file, which supports dynamic addition and modification.

3. The multi-protocol conversion method between fire alarm devices according to claim 1, characterized in that, The logic of the original data stream parsing process is as follows: Frame synchronization: Locates complete messages using the frame header and trailer identifiers defined in the protocol template; filters out data containing interference. Field extraction: Parse the required loop number, address number, and event type key information in the data field according to the loaded protocol template; Verification: The integrity of the message is verified using the verification and algorithm rules in the protocol template. If the verification fails, a retransmission is requested. Format conversion: Converts the extracted information into an intermediate format to eliminate differences in the source protocol.

4. The multi-protocol conversion method between fire alarm devices according to claim 1, characterized in that, The message framing process involves loading a target protocol template and framing messages according to the rules of the target protocol template. The message framing process is as follows: Fill in the frame header and frame tail; Write the mapped function code and data field; Write the verification value according to the target protocol verification method; For special scenarios, add a priority identifier to the message.

5. The multi-protocol conversion method between fire alarm devices according to claim 1, characterized in that, The standardized data model includes at least: an alarm event table, a device status table, and a control command table; the standardized data model is used for the unified management of multi-protocol data.

6. The multi-protocol conversion method between fire alarm devices according to claim 1, characterized in that, The process of sending the framed data to the target fire-fighting equipment must strictly follow the communication sequence in the protocol template, including the sending interval and response waiting time. After receiving the data, the target fire-fighting equipment returns a response message. The response message is compared with the sent data. If the comparison and verification do not match, a retransmission mechanism is triggered. The cases of mismatch include at least: response timeout and content mismatch.

7. A multi-protocol conversion system between fire alarm equipment, characterized in that, include: The protocol configuration module is used to store and manage template information for all converted protocols. This module includes a protocol library configuration file. Each protocol template defines communication parameters including baud rate, data bits, stop bits, and parity bits, as well as message format including frame header, data field length, function code, and checksum algorithm. The data acquisition and parsing engine is used to establish communication with the source device. According to the corresponding protocol template loaded in the protocol configuration module, it acquires the data uploaded by the fire alarm host in real time through the physical interface; it parses the raw data stream and converts it into a unified intermediate format. The data standardization and database module, as the system's data transfer hub, mainly uses the data stored after parsing in the data acquisition and parsing engine as the database and converts it into a standardized data model. The database serves as both a buffer for protocol conversion and a source of standardized data models, thereby shielding the differences between different host protocols. The data mapping and encapsulation engine is used to prepare communication data for the target device. It reads standardized data from the database module, completes the mapping of fields in the standardized data model to specific addresses and formats of the target device's private protocol, and completes message framing based on the target protocol template. The data transmission engine is used to communicate with the target fire-fighting equipment. It uses a dynamic switching method of parity bits to simulate the ninth bit of data and sends framed data to the target fire-fighting equipment based on the target protocol template to achieve communication.

8. A multi-protocol conversion device between fire alarm equipment, characterized in that, include: The processor and at least one set of memories, wherein the memories store a computer-executable program, and the processor executes the computer-executable program to perform the multi-protocol conversion method between fire alarm devices as described in any one of claims 1 to 6.

9. A multi-protocol conversion medium between fire alarm equipment, characterized in that, The medium stores a computer-executable program, which is executed by a computer to perform the multi-protocol conversion method between fire alarm devices as described in any one of claims 1 to 6.

Images