A multi-protocol decoupling gateway system for rail transit and its decoupling method
By constructing a virtual device layer and using graphical development, the decoupling of the rail transit system was achieved, solving the problems of long system development cycles and difficulties in interconnection, and improving development efficiency and system interconnection capabilities.
Patent Information
- Application Number
- CN202311101872.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-08-30
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2043-08-30
AI Technical Summary
The development of existing integrated monitoring systems for rail transit is labor-intensive and time-consuming, and parallel development is not possible, which leads to extended construction periods and difficulties in interconnection between systems.
A virtual device layer is constructed using a graphical development approach and a logic/function separation method. It consists of core data service units, intelligent logic service units, device mapping service units, monitoring view data service units, and industry extension model construction service units. This shields device differences and forms a unified industry extension model system, thereby decoupling data acquisition, view monitoring, and operation.
It decouples the professional system equipment and software platform of the rail transit system, solves the problems of data silos and logical silos, and improves development efficiency and system interconnection capabilities.
Smart Images

Figure CN117155740B_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the field of rail transit industrial control technology, specifically relating to a rail transit multi-protocol decoupling gateway system and its decoupling method. Background Technology
[0002] The existing integrated monitoring system primarily integrates existing large-scale data service platforms and configuration development platforms, supplemented by programming development. Its data acquisition configuration, HMI monitoring view development, business logic development, and environment platform migration configuration are all customized development tasks. Therefore, its development workload and cycle are relatively long. Generally, initial development must begin after equipment bidding is completed, followed by subsequent development and system integration testing after equipment installation and commissioning. The work sequence is basically a sequential workflow with heavy external dependencies. The parts that can be developed in a quasi-parallel manner are mainly concentrated in data development and view development; other tasks must be performed sequentially. Considering the workload of its own system development and the discovery and rectification of bugs and defects, the overall project duration is inevitably long.
[0003] The best approach is to build a virtual device layer, shielding specific devices and filtering out their differences. This allows for comprehensive modeling of rail transit facilities and equipment according to a unified standard, forming an industry-wide extended model system covering stations, lines, and networks. Virtual device entities can then be constructed as needed using this industry-wide extended model, creating address spaces and data services. All applications above this level will use the virtual devices as the endpoint for data collection, view monitoring, and operation execution.
[0004] This invention employs graphical development (primarily configuration), separation of logic / function from the runtime engine, and decoupling of business development from system development. Therefore, its model creation, monitoring view creation, and on-site logic creation all utilize graphical configuration tools. Configuration results are described in common JSON and XML languages, offering a superior user experience, data retention, and versatility. Due to the decoupling of configuration and system, parallel engineering design and system development, parallel roadshows and debugging, and parallel integration testing and OTA firmware upgrades are possible. Summary of the Invention
[0005] The purpose of this invention is to address the shortcomings of existing technologies by providing a multi-protocol decoupling gateway system and its decoupling method for rail transit. This decoupling method constructs a virtual device layer through its core data service unit, intelligent logic service unit, device mapping service unit, external data service unit, monitoring view data service unit, and industry-extended model construction service unit. This layer shields specific devices, filters out differences between them, and models rail transit facilities and equipment comprehensively according to a unified standard, forming an industry-extended model system covering stations, lines, and networks. Virtual device entities are constructed as needed using the industry-extended models, forming address spaces and data services. All applications above use virtual devices as the endpoint for data acquisition, view monitoring, and operation execution. Furthermore, it employs graphical development (primarily configuration), separation of logic / function and runtime engine, and decoupling of business development and system development. Therefore, its model compilation, monitoring view compilation, and on-site logic compilation are all done using graphical configuration tools, with configuration results described in general JSON and XML languages, offering a good user experience, data retention, and fluidity.
[0006] The objective of this invention is achieved through the following technical solutions: A multi-protocol decoupling gateway system for rail transit is characterized in that the gateway system includes a core data service unit, an intelligent logic service unit, an equipment mapping service unit, an external data service unit, a monitoring view data service unit, and an industry extended model construction service unit; wherein, the intelligent logic service unit communicates with the core data service unit via the SOCKET communication protocol; the equipment mapping service unit communicates with the core data service unit via the MQTT communication protocol; the monitoring view data service unit communicates with the core data service unit via the WEB SOCKET communication protocol; the external data service unit is integrated with the core data service unit and is provided with an external interface; the industry extended model construction service unit is communicatively connected to the equipment mapping service unit and the core data service unit.
[0007] The equipment mapping service unit communicates with each rail transit professional system, and communicates with the core data service unit by carrying pseudo-instructions through the MQTT communication protocol.
[0008] The industry extended model construction service unit builds a model file based on the EXCEL file of the industrial control point table. The equipment mapping service unit and the core data service unit determine the underlying equipment information through the model file.
[0009] The intelligent logic service unit communicates with the core data service unit via the SOCKET communication protocol. The core data service unit forwards the control commands sent by the monitoring view data service unit to the intelligent logic service unit. The intelligent logic service unit determines whether the control command is a scene control command or a device control command. If the control command is a scene control command, it matches the edited scene rules and sends device control pseudo-commands to the device mapping service unit in a sequential manner. If the control command is a device control command, it directly forwards the control command to the device mapping service unit.
[0010] The monitoring view data service unit provides data services to the HMI front-end operation interface, pushing measurement events, alarm events, alarm feedback events, command events, and command feedback event data from each of the rail transit professional systems to the HMI front-end operation interface in real time. The control commands are issued through the HMI front-end operation interface on the monitoring view data service unit.
[0011] A decoupling method for a multi-protocol decoupling gateway system for rail transit, as described above, is characterized by the following steps: a monitoring view data service unit sends control commands to a core data service unit; the core data service unit sends the control commands to an intelligent logic service unit for parsing; the intelligent logic service unit returns the parsed sequential control pseudo-commands to the core data service unit; the core data service unit sends the sequential control pseudo-commands to an equipment mapping service unit for translation; if the sequential control pseudo-commands do not exist, they are returned to the core data service unit; if the sequential control pseudo-commands exist, they are translated into real commands and returned to the equipment mapping service unit, then sent to the rail transit professional system for equipment control; finally, the control data from the rail transit professional system is returned, completing the decoupling process.
[0012] The advantages of this invention are: (1) For the first time, the professional system equipment and software platform in the field of rail transit industrial control technology have been decoupled, solving the problems of data islands, logic islands, and technology islands caused by the customized development of traditional systems, as well as the difficulty of interconnection between professional systems and between lines; (2) Using the industry extended model building tool, based on the EXCEL file of the industrial control point table of a rail transit station's fire alarm system, BAS system, passenger information system, power monitoring system, broadcasting system, AFC automatic fare collection system, etc., the tool is used to build the element equipment model, subsystem model, system model, spatial architecture model, and equipment organization architecture model, and configure the industrial control channel model and its read / write configuration to form a configuration file, which constitutes the business basic mechanism data model; (3) It can flexibly support industry extension models, that is, it can meet the full objectification of modeling nesting, association and integration of rail transit equipment, including meta-equipment models, spatial equipment models, subsystem models, system models, equipment organizational structure models, etc.; at the same time, it integrates data access, alarm and early warning, historical data access and trend monitoring. Attached Figure Description
[0013] Figure 1 This is a structural framework diagram of the multi-protocol decoupling gateway system for rail transit in this invention; Figure 2 This is a diagram illustrating the scope and professional range of the decoupling protocol in this invention; Figure 3 This is a functional module relationship diagram of the rail transit multi-protocol decoupling gateway system in this invention; Figure 4 This is a schematic diagram of the decoupling process in this invention. Implementation
[0014] The features and other related features of the present invention will be further described in detail below with reference to the accompanying drawings and embodiments, so as to facilitate understanding by those skilled in the art: Example: Figure 1 , 2 As shown in Figures 3 and 4, this embodiment specifically relates to a multi-protocol decoupling gateway system for rail transit and its decoupling method. The gateway system includes a core data service unit, an intelligent logic service unit, an equipment mapping service unit, an external data service unit, a monitoring view data service unit, and an industry-specific extended model construction service unit. The intelligent logic service unit communicates with the core data service unit via the SOCKET communication protocol; the equipment mapping service unit communicates with the core data service unit via the MQTT communication protocol; the monitoring view data service unit communicates with the core data service unit via the WEB SOCKET communication protocol; the external data service unit is integrated with the core data service unit and has an external interface; the industry-specific extended model construction service unit is communicatively connected to the equipment mapping service unit and the core data service unit; and the equipment mapping service unit is communicatively connected to various rail transit professional systems.
[0015] like Figure 1 , 2As shown in Figures 3 and 4, the core data service unit provides real-time and historical data services based on object address space, using general industrial control protocols or self-organizing communication protocols. The core data service includes real-time and historical data services and real-time and historical event alarm services. The core data service unit communicates with the intelligent logic service unit via SOCKET, with the device mapping service unit via MQTT, and with the monitoring view service unit via WEB SOCKET. Event data of the core data service unit is stored in RADIS, providing real-time data services externally. The core data service unit is responsible for data coordination and forwarding throughout the system.
[0016] like Figure 1 , 2 As shown in Figures 3 and 4, the intelligent logic service unit adopts CEP (Complex Event Process Control), providing complex process business logic judgment and instruction filtering based on real-time and historical service address space data and event services. This forms a rule-based processing and scene control instruction service that decouples subjective and objective business logic. The intelligent logic service unit communicates with the core data service unit via SOCKET. The core data service unit forwards control instructions sent by the HMI front end of the monitoring view data service unit to the intelligent logic service unit. The intelligent logic service unit determines whether the instruction is a scene control instruction or a device control instruction. If it is a scene control instruction, it matches the edited scene rules and issues device control pseudo-instructions to the device mapping service unit in a sequential control manner. If the instruction is a device control instruction, it directly forwards the control instruction to the device mapping service unit. Through the above process, it can provide complex process business logic judgment and instruction filtering, forming a rule-based processing and scene control instruction service that decouples subjective and objective business logic. This is a key point in realizing scenario-based operation.
[0017] like Figure 1 , 2 As shown in Figures 3 and 4, the device mapping service unit includes various hardware and software data interfaces, communication, data acquisition and command issuance for parsing. Based on hard interfaces, it is divided into two categories: one is communication based on TCP protocol or serial port, using network or bus communication methods, including the most commonly used MODBUS protocol, custom messages, common industrial control protocols (PROFIBUS, 104, etc.), and dirty interfaces (such as uncommon protocols and proprietary protocols); the other is hardwired and serial port communication, typically converting DTU, RTU, etc., to TCP communication. The device mapping service unit connects to various rail transit professional systems through corresponding protocols and communicates with the core data service unit via the MQTT protocol carrying pseudo-instructions. Because pseudo-instructions are used for data interaction, it is not necessary to directly send real instructions to the professional systems, thus shielding the specific device layer and achieving decoupling.
[0018] like Figure 1, 2 As shown in Figures 3 and 4, the monitoring view data service unit provides data services to the HMI front-end operation interface. It pushes measurement events, alarm events, alarm feedback events, command events, and command feedback event data from various rail transit professional systems to the HMI front-end operation interface in real time, providing data support for the interface. This system uses WEBSOCKET for communication. The monitoring view data service unit provides data services to the HMI, which is built using an SVG B / S architecture and communicates via WEBSOCKET or other methods (including general industrial control protocols and other methods). This mainly includes data communication, view data filtering, subscription mechanism construction, and command reception and translation. The monitoring view service unit sends control commands to the core data service unit. The core data service unit parses the model file generated based on the point table and stores the parsed device mapping data in the RADIS cache. When the device mapping service unit starts, it also loads and parses the model file. The core data service unit forwards the pseudo-commands sent by the monitoring view service unit to the device mapping service unit. The device mapping service unit translates these into actual commands for specific devices based on the device mapping relationships in the model file and issues them for control.
[0019] like Figure 1 , 2 As shown in Figures 3 and 4, the external data service unit primarily targets communication with the IoT cloud portion, employing methods such as MQTT, WEBSOCKET, and WINSOCKET. Its main functions include data conversion and subscription, cloud command reception, and translation. The external data service unit is responsible for the interface connection and data interaction functions of the rail transit multi-protocol decoupling gateway system. External systems can access the decoupling gateway system by interacting with the external data service unit through standard protocols. In this embodiment, the system is classified as a station-level system according to the rail transit system level; therefore, the service target of the external data service unit is the rail transit line-level system.
[0020] like Figure 1 , 2 As shown in Figures 3 and 4, the industry extended model construction service unit is responsible for generating model files based on the location table. The model files contain meta-equipment models, subsystem and system models, spatial organization models, and organizational structure models. The core data service unit and equipment mapping service unit will determine the specific information of the underlying equipment through the model files. The industry extended model construction service unit includes meta-equipment models, subsystem and system models, spatial organization models, and organizational structure models. The models can be constructed as JSON or XML files and injected into the real-time and historical service servers for operation.
[0021] like Figure 1 , 2As shown in Figures 3 and 4, the decoupling method of the rail transit multi-protocol decoupling gateway system in this embodiment includes the following steps: the monitoring view data service unit sends control commands to the core data service unit; the core data service unit sends the control commands to the intelligent logic service unit for parsing; the intelligent logic service unit returns the parsed sequential control pseudo-commands to the core data service unit; the core data service unit sends the sequential control pseudo-commands to the device mapping service unit for translation; if the sequential control pseudo-commands do not exist, they are returned to the core data service unit; if the sequential control pseudo-commands exist, they are translated into real commands and returned to the device mapping service unit and sent to the rail transit professional system for device control; then the control data from the rail transit professional system is returned, completing the decoupling process.
[0022] like Figure 3 As shown in the figure, this embodiment discloses the functional module composition relationship of a multi-protocol decoupling gateway system for rail transit. The industry extended model building service unit generates an XML format model file for the core data service unit to parse, and generates a JSON format model file for the intelligent logic service unit to parse. The core data service unit can issue operation instructions to the device mapping service unit, provide data support to the monitoring view data service unit, provide an external data interface via MQTT, and interact with the intelligent logic service unit to achieve complex scenario-based control functions. The device mapping service unit receives device control pseudo-instructions issued by the core data service and returns the controlled data to the core data service unit. The external data service unit can receive control instructions issued by external systems and receive real-time data pushes from the core data service unit. The monitoring view service unit can receive real-time data pushed by the core data service and issue scenario control instructions to the intelligent logic service unit.
[0023] The beneficial effects of this embodiment are: (1) For the first time, the professional system equipment and software platform in the field of rail transit industrial control technology have been decoupled, solving the problems of data islands, logic islands, and technology islands caused by the customized development of traditional systems, as well as the difficulty of interconnection between professional systems and between lines; (2) Using the industry extended model building tool, based on the EXCEL file of the industrial control point table of a rail transit station's fire alarm system, BAS system, passenger information system, power monitoring system, broadcasting system, AFC automatic fare collection system, etc., the tool is used to build the element equipment model, subsystem model, system model, spatial architecture model, and equipment organization architecture model, and configure the industrial control channel model and its read / write configuration to form a configuration file, which constitutes the business basic mechanism data model; (3) It can flexibly support industry extension models, that is, it can meet the full objectification of modeling nesting, association and integration of rail transit equipment, including meta-equipment models, spatial equipment models, subsystem models, system models, equipment organizational structure models, etc.; at the same time, it integrates data access, alarm and early warning, historical data access and trend monitoring.
Claims
1. A multi-protocol decoupling gateway system for rail transit, characterized in that... The gateway system includes a core data service unit, an intelligent logic service unit, a device mapping service unit, an external data service unit, a monitoring view data service unit, and an industry extended model construction service unit. The intelligent logic service unit communicates with the core data service unit via the SOCKET communication protocol; the device mapping service unit communicates with the core data service unit via the MQTT communication protocol; the monitoring view data service unit communicates with the core data service unit via the WEB SOCKET communication protocol; the external data service unit is integrated with the core data service unit and has an external interface; the industry extended model construction service unit is communicatively connected to both the device mapping service unit and the core data service unit. The equipment mapping service unit communicates with each rail transit professional system, and the equipment mapping service unit communicates with the core data service unit by carrying pseudo-instructions through the MQTT communication protocol. The industry extended model construction service unit builds a model file based on the EXCEL file of the industrial control point table. The equipment mapping service unit and the core data service unit determine the underlying equipment information through the model file. The intelligent logic service unit communicates with the core data service unit via the SOCKET communication protocol. The core data service unit forwards the control commands sent by the monitoring view data service unit to the intelligent logic service unit. The intelligent logic service unit determines whether the control command is a scene control command or a device control command. If the control command is a scene control command, it matches the edited scene rules and sends device control pseudo-commands to the device mapping service unit in a sequential manner. If the control command is a device control command, it directly forwards the control command to the device mapping service unit.
2. The rail transit multi-protocol decoupling gateway system according to claim 1, characterized in that... The monitoring view data service unit provides data services to the HMI front-end operation interface, pushing measurement events, alarm events, alarm feedback events, command events, and command feedback event data from each of the rail transit professional systems to the HMI front-end operation interface in real time. The control commands are issued through the HMI front-end operation interface on the monitoring view data service unit.
3. A decoupling method relating to the multi-protocol decoupling gateway system for rail transit as described in any one of claims 1-2, characterized in that... The decoupling method includes the following steps: the monitoring view data service unit sends control commands to the core data service unit; the core data service unit sends the control commands to the intelligent logic service unit for parsing; the intelligent logic service unit returns the parsed sequential control pseudo-commands to the core data service unit; the core data service unit sends the sequential control pseudo-commands to the device mapping service unit for translation; if the sequential control pseudo-commands do not exist, they are returned to the core data service unit; if the sequential control pseudo-commands exist, they are translated into real commands and returned to the device mapping service unit, then sent to the rail transit professional system for equipment control; finally, the control data from the rail transit professional system is returned, completing the decoupling process.
Citation Information
Patent Citations
Intelligent cloud gateway of industrial IoT (Internet of Things) and communication method of gateway
CN109150703A
Virtualization integrated control system of rail transit comprehensive backup panel
CN211528973U
