A monitoring system for a rail transit train subsystem and its configuration method

By constructing a visual and configurable monitoring system for rail transit train subsystems, the problem of independent subsystems was solved, unified data management and visual display were achieved, the flexibility and maintainability of the monitoring system were improved, and the configuration process was simplified.

CN123104732APending Publication Date: 2026-11-17CRRC CHANGCHUN RAILWAY VEHICLES CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611622426.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-10-20
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing rail transit train monitoring systems have independent subsystems, making data sharing difficult, resulting in poor monitoring flexibility, high maintenance costs, unintuitive status visualization, and difficulty in quickly locating faults.

Method used

A visual, configurable, and interactive rail transit train subsystem status monitoring system is constructed, adopting a layered architecture design, including a storage layer, a middleware service layer, and an application layer. It supports zero-code configuration and realizes unified data management and visual display.

Benefits of technology

It enables centralized monitoring of the overall train status, reduces maintenance costs, improves the visualization and intuitiveness of status and the efficiency of information transmission, supports flexible configuration of judgment conditions, and simplifies the configuration process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123104732A_ABST
    Figure CN123104732A_ABST
Patent Text Reader

Abstract

This invention relates to the field of intelligent operation and maintenance technology for rail transit, and provides a monitoring system for rail transit train subsystems and its configuration method. This invention unifies the access, management, and analysis of operational data from various train subsystems, achieving centralized monitoring and unified management of the entire train's operational status, and providing reliable information support for overall decision-making by maintenance personnel. It employs a configurable implementation scheme, and the configuration process does not require modification of the system source code or recompilation and deployment. Real-time vehicle operational status data is dynamically correlated, enabling visualized monitoring of train component-level operational status. Furthermore, through configuration, data can be displayed according to the physical location relationships of train carriages, reducing the cognitive load on users. The invention provides multiple judgment condition configuration methods, such as multi-level threshold configuration and logical expression rules, to differentiate various states, shortening the user's identification time for key information and improving information transmission efficiency.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of intelligent operation and maintenance technology for rail transit, and in particular to a monitoring system for a rail transit train subsystem and its configuration method. Background Technology

[0002] Rail transit trains are highly complex mechatronic systems, comprising multiple subsystems such as bogies, air conditioning, door systems, pantographs, braking, and traction. These subsystems are interconnected and work in concert. During daily operation, a failure in any subsystem will affect the reliability, availability, maintainability, and safety of the entire train. Therefore, real-time monitoring of subsystem status is of paramount importance.

[0003] Traditional rail transit train monitoring systems mainly have the following problems: 1. The monitoring functions of each subsystem are relatively independent, and the data is stored separately, forming a self-contained system. This makes it difficult for different subsystems to share information and interact, which is not conducive to monitoring personnel obtaining overall information for overall decision-making. 2. The judgment conditions and early warning rules of the existing PHM system are mostly hard-coded or statically configured. When the operation scenario, equipment configuration or maintenance strategy of rail transit vehicles changes, the system source code needs to be modified or the system redeployed. The adjustment cycle is long, the maintenance cost is high and the flexibility is poor. 3. Current monitoring systems mostly use general dashboards and tables / charts to visualize train status. While these can display key parameter values ​​and trend curves, they are not good at intuitively reflecting the spatial relationships between train equipment, which makes it difficult for maintenance personnel to quickly locate faults from the vehicle's perspective.

[0004] In summary, there are application scenarios for an intelligent monitoring system that can achieve unified monitoring and management of various subsystems of rail transit trains, support flexible configuration of judgment conditions and visualization logic, and has high scalability and adaptability. Summary of the Invention

[0005] The core objective of this invention is to construct a visual, configurable, interactive, and intelligent rail transit train subsystem status monitoring system and its configuration method. This system enables customized configuration for visualizing the status of rail transit train subsystems, unifying and synchronously displaying the status of multiple subsystems to the user in real time, achieving data integration and a simple, intuitive visualization. It supports zero-code configuration by maintenance personnel, with an efficient, flexible, zero-code, and reusable process. After configuration, users can view the data immediately, significantly simplifying the usage process and eliminating redundant processes such as retrieval. This helps users analyze problems or gain insights through data-driven approaches, providing a reliable visual data foundation for operational safety, train maintenance, problem troubleshooting, and resource optimization.

[0006] To achieve the above objectives, the present invention adopts the following technical solution: A monitoring system for a rail transit train subsystem includes: The storage layer includes a data storage module for receiving pre-processed data collected by vehicle-end sensors and storing it in a standardized database. The data covers the overall status data of the train, system and component status data, and environmental parameter data. The middleware service layer includes a data management module and an interface call module. The data management module is used to manage the data in the storage layer and establish logical relationships between the data. The interface call module is used to provide data call services to the application layer through standardized interfaces. The application layer includes a monitoring item configuration service module and a conditional execution service module. The monitoring item configuration service module includes a data item management submodule, a data association submodule, a display mode configuration submodule, a logic configuration submodule, and a preview and release submodule, which are used to implement data item creation, subsystem binding of data items, display mode configuration, logical expression editing and verification, and preview and release operations, respectively. The conditional execution service module is used to execute automatic judgment logic based on the configured logical expression. The presentation layer includes a process configuration interface module and a subsystem status monitoring interface module. The process configuration interface module provides a data item management interface and a monitoring data item configuration interface, allowing users to complete zero-code configuration operations. The subsystem status monitoring interface module is used to display the status data of each subsystem monitoring item in list form or trend chart form after the configuration is published.

[0007] Furthermore, in the data storage module of the storage layer, the data processing chain is as follows: after the vehicle-side sensors collect data, it undergoes filtering and noise reduction preprocessing in sequence, and then is transmitted to the ground system through the MVB bus, and finally stored in the database with the standardized structure.

[0008] Furthermore, the data management module of the middle platform service layer is also used to: establish logical relationships between different data, support data addition, deletion, modification and query operations, and maintain the binding relationship between data items and subsystems; the interface call module provides data access services to the application layer through standardized interfaces.

[0009] Furthermore, in the application layer's monitoring item configuration service module: the data item management submodule is used to query parameters and create data items in the knowledge base management system, grouping similar parameters from different compartments of the same vehicle model into the same data item; the data association submodule is used to provide an interactive interface for subsystem selection and data item association, and to receive vehicle model binding information; the display mode configuration submodule is used to receive user-configured list-style or trend chart-style display parameters, including display format selection and physical space layout mapping parameters; the logic configuration submodule is used to receive user-edited conditional expressions, and to perform syntax validation and operator parameter type matching validation on the expressions; the preview and release submodule is used to call the conditional execution service module to generate preview data, and after user confirmation, to perform a release operation to write the configuration data into the middleware service layer.

[0010] Furthermore, the process configuration interface module of the presentation layer provides interfaces including a configuration process homepage, a list-style configuration interface, and a trend graph-style configuration interface. The configuration process homepage provides entry points for predefined system monitoring and custom monitoring pages. The subsystem status monitoring interface module includes a list monitoring view and a trend graph monitoring view. The list monitoring view displays the real-time status of each subsystem monitoring item in a list format, and the trend graph monitoring view displays the data trend of the monitoring item in the form of a time series curve.

[0011] This invention also provides a method for configuring monitoring of a rail transit train subsystem, which applies the rail transit train subsystem monitoring system described above, and includes the following steps: S1. Data item creation steps: Obtain the monitored item parameters of the subsystem in the knowledge base management system, create data items, group the same type of parameters of different carriages of the same train into the same data item and perform structured processing, and the data item serves as the basic unit for subsequent configuration; S2. Subsystem data item binding steps: In the monitoring data item configuration interface, select a preset subsystem or a newly created subsystem, associate the created data items with the subsystem, and determine the data source range by vehicle type binding. The system automatically obtains the real-time data of the corresponding carriage from the storage layer according to the bound data items. S3. Display mode configuration steps: Configure the display mode for each data item through a graphical interactive interface. The display mode includes list mode and trend chart mode. The list mode configuration includes display format as text or icons, and supports layout mapping configuration based on the train's physical space. The trend chart mode configuration includes the selection of current data or historical data and the display mode of summary or discrete display. S4. Logical Expression Editing and Verification Steps: Configure conditional expressions through the graphical interactive interface. The conditional expressions include comparison operators and / or logical operators. Use comparison operators and logical operators to construct judgment rules and map the real-time values ​​of data items to different icon styles or color states. After the system performs syntax verification on the conditional expressions, it stores them in the middle platform service layer. S5. Preview generation steps: The application layer generates preview data for the monitoring page based on the configured data items, display methods, and conditional expressions, and displays the preview effect through the presentation layer; S6. Publishing and Permission Distribution Steps: After confirming that the configuration is correct, publish the configuration information. The configuration data is written to the middleware service layer through the application layer and takes effect immediately. Based on the publishing settings, the configuration page is distributed to be visible to all users or to individuals.

[0012] Furthermore, in step S1, the parameter data types of the data items include boolean type and unsigned type. The data items are structured according to the same type of parameters for different carriages of the same model, so that a single data item contains the same type of parameter values ​​for multiple carriage dimensions.

[0013] Furthermore, in step S2, a subsystem is associated with multiple data items, and the system automatically filters and displays matching carriage data from the storage layer based on the bound vehicle model and data items.

[0014] Furthermore, in step S3, the specific method of configuring the list-style layout mapping is as follows: by adjusting the arrangement order of different parameters in the data items, a correspondence is established between the data display position of each parameter and the equipment installation position in the actual physical space of the train.

[0015] Furthermore, in step S3, the list-style icon display method supports system-preset icons and user-uploaded custom icons.

[0016] Furthermore, in step S4, the logical operators include AND, OR, and NOT; multiple comparison operations are combined through logical operators to form a compound conditional expression, and the system performs matching verification on the operand types of each operator during the verification process.

[0017] Furthermore, in step S6, the pre-set subsystem monitoring page is visible to all users after it is published; the user's custom subsystem monitoring page can be selected to be visible only to the user or to all users when it is published.

[0018] Compared with the prior art, the present invention has the following beneficial effects: 1. High system integration: This invention unifies the access, management and analysis of the operating data of various train subsystems, realizing centralized monitoring and unified management of the entire train's operating status and providing reliable information support for the overall planning and decision-making of maintenance personnel; 2. The system boasts strong scalability and low maintenance costs. This invention employs a configurable implementation scheme, and the configuration process requires no modification to the system source code or recompilation and deployment. When train formations are adjusted, operating lines are switched, or maintenance strategies change, maintenance personnel only need to make corresponding adjustments through the configuration interface to adapt the system to the new monitoring requirements, significantly reducing system maintenance costs and reliance on developers. 3. The status is visualized and intuitive. This invention dynamically correlates the real-time operational status data of the vehicle, achieving visualized monitoring of the operational status at the train component level. Furthermore, through configuration, the data can be displayed according to the physical location relationship of the train carriages, reducing the cognitive load on the user. 4. Flexible configuration of judgment conditions: The multi-level threshold configuration, logical expression rules and other judgment condition configuration methods provided by this invention can flexibly adapt to the complex monitoring needs of various subsystems, differentiate between various states, shorten the user's identification time of key information and improve information transmission efficiency. Attached Figure Description

[0019] To more clearly illustrate the technical solution and advantages of the present invention, a description in conjunction with the following drawings will make it clearer and easier to understand. It should be noted that the drawings shown herein are only partial schematic diagrams related to this application, and not all of the drawings; those skilled in the art can still obtain other related drawings based on these drawings without any inventive effort.

[0020] Figure 1 This is a schematic diagram of the train subsystem status monitoring system architecture of the present invention; Figure 2 This is a schematic diagram of the configuration method of the present invention; Figure 3 This is a schematic diagram of the subsystem selection interface in the configuration process of this invention; Figure 4 This is a schematic diagram of the list-style configuration interface of the present invention; Figure 5 This is a schematic diagram of the train subsystem list monitoring interface of the present invention; Figure 6 This is a schematic diagram of the train subsystem trend chart monitoring interface of the present invention. Detailed Implementation

[0021] The technical solution of the present invention will be described in detail below with reference to the accompanying drawings. The following embodiments are used to explain the present invention and are not intended to limit the scope of protection of the present invention.

[0022] This invention provides a monitoring system for a rail transit train subsystem, which adopts a layered architecture design, such as... Figure 1 As shown, from bottom to top, the layers are storage layer, middleware service layer, application layer, and presentation layer, and the layers communicate with each other through standardized interfaces.

[0023] Storage Layer: Includes a data storage module. This module receives pre-processed data collected by onboard sensors and stores it in a standardized database. The data covers overall train status data, system and component status data, and environmental parameter data. Specifically, the onboard system deploys various types of sensors, including temperature sensors, pressure sensors, speed sensors, and vibration sensors. These sensors collect operating parameters of each subsystem in real time at a preset sampling frequency. The raw data is first pre-processed, including filtering and noise reduction, to eliminate interference components in the sensor signals and improve data quality. The pre-processed data is then transmitted to the ground system via MVB. Upon arrival at the ground system, the data is parsed and format converted before being finally stored in the standardized database. The database may be a relational database or a time-series database, with the appropriate storage scheme selected based on the data type and access frequency. The overall status data includes global data such as train formation information and train direction of travel; the system and component status data includes the operating parameters and fault information of each subsystem such as traction system status, braking system status, door system status, air conditioning system status, and pantograph status; and the environmental parameter data includes environmental monitoring data such as interior temperature, exterior temperature, humidity, and air pressure.

[0024] The middleware service layer includes a data management module and an interface call module. The data management module manages the data in the storage layer and establishes logical relationships between data. Specific functions include: performing CRUD operations on data to ensure data integrity and consistency; establishing logical relationships between different data types, such as mapping data items to subsystems and establishing correspondences between data items and carriage numbers; and maintaining the binding relationships between data items and subsystems, recording which data items are associated with each subsystem and which vehicle type they are bound to. The interface call module provides data call services to the application layer through standardized interfaces.

[0025] Application Layer: This layer includes a monitoring item configuration service module, a conditional execution service module, and a chart generation service module. The monitoring item configuration service module is the core business module of the system, responsible for providing zero-code configurable monitoring page construction capabilities. This module is further subdivided into five sub-modules: data item management sub-module, data association sub-module, display mode configuration sub-module, logic configuration sub-module, and preview / release sub-module. The specific functions of each sub-module will be described in detail in the subsequent configuration method description. The conditional execution service module is used to execute automatic judgment logic based on the configured logical expression, transforming the raw data value into a status identifier with business meaning. For example, when the real-time value of the air conditioner temperature data item is 32℃, the conditional execution service module determines that the data is in a high-temperature abnormal state according to the configured judgment rule "parameter value > 28", and returns the status identifier to the presentation layer for corresponding color and icon rendering. The chart generation service supports line chart templates; the front-end only needs to call this service to generate relevant line trend charts on the page.

[0026] The presentation layer includes a process configuration interface module and a subsystem status monitoring interface module. The process configuration interface module provides a data item management interface and a monitoring data item configuration interface, allowing users to complete zero-code configuration operations. The subsystem status monitoring interface module displays the status data of each subsystem monitoring item in list or trend chart format after configuration is published. These interfaces are implemented using Web technology, providing users with a graphical interface through a browser, enabling them to configure and display the monitoring page through visual drag-and-drop and form filling interactions.

[0027] The data flow between the various layers of the system is as follows: the storage layer is responsible for persistent data storage and provides raw data support to the middle platform service layer; the middle platform service layer organizes, manages, and logically associates the data in the storage layer and provides data services to the application layer through standardized interfaces; the application layer receives configuration requests and user operation instructions from the presentation layer, calls the data services provided by the middle platform service layer to complete business logic processing, and returns the processing results to the presentation layer for display; the presentation layer directly provides an interactive interface to the user, receives user operations, and renders and displays the results.

[0028] like Figure 2 As shown, this invention applies a rail transit train subsystem monitoring system as described above to provide a rail transit train subsystem monitoring configuration method. The detailed implementation process of the specific configuration method is as follows: Step S1: Data item creation steps.

[0029] In this step, the operator first queries the knowledge base management system for the parameters of the monitored items in the subsystem. The knowledge base management system pre-maintains a parameter database for each train subsystem, including metadata information such as the name and data type of each parameter. The operator then queries the list of parameters to be monitored based on the monitoring requirements. For example, for the door system, the parameters to be monitored include door lock status, door opening mode, and door obstacle detection status. After the query is completed, the operator creates a data item. When creating a data item, the data item name, associated parameters, and applicable vehicle model must be specified. The system will automatically group similar parameters from different carriages of the same vehicle model into the same data item. For example, when creating the "Door Locking" data item, the system will automatically group all the locking status signals of doors 1 to 6 of each of the 8 carriages into this data item, forming a structured data set containing 48 parameter values ​​(8 carriages × 6 doors).

[0030] The backend processing flow involved in this step is as follows: The user initiates a data item creation request through the presentation layer; the middleware layer calls an interface to query parameters in the database (storage layer). If the result is not empty, the parameter is valid. When the user initiates a data item save request through the presentation layer, the data item management module validates the request parameters, checking whether similar parameters have already been merged into existing data items to avoid duplicate creation. After successful validation, the data item information is written to the data management module of the middleware service layer.

[0031] Step S2: Subsystem data item binding step.

[0032] In this step, such as Figure 3 As shown, the operator first selects a preset subsystem or creates a new one. The system provides a batch of preset subsystems, such as the traction system, braking system, door system, air conditioning system, and hot axle box detection system. The operator can directly select and configure these subsystems, or create a custom subsystem. After selecting a subsystem, the operator enters the monitoring data item configuration interface (e.g., ...). Figure 4 (As shown). The left side of the interface displays a list of data items, and the right side displays a configuration preview area. Operators can associate existing data items with this subsystem by clicking the "Add Monitoring Data Item" button to proceed to detailed configuration steps. A subsystem supports associating multiple data items, but only one data item can be added per configuration process. Users will see the available data items in the drop-down menu and can select one.

[0033] The backend processing flow involved in this step is as follows: users query and select data items through the presentation layer, retrieve data items created in the middle platform data management module through the configuration service of the application layer, and simultaneously initiate a data subscription request to the storage layer through the interface call module to establish a real-time data acquisition channel.

[0034] Step S3: Display mode configuration steps.

[0035] In this step, the operator configures the display method for each data item through a graphical user interface. The interface displays the configuration information for each associated data item.

[0036] For list-style display, operators need to configure the following: select text or icon as the display format; if icon display is selected, select an icon from the system's preset icon library or upload a custom SVG format icon; configure the physical space layout mapping parameters of the data.

[0037] Let's take the train door system as an example for a detailed explanation. The door lock status data item contains the lock signals of the six doors in each carriage, and the data type is boolean. The operator selects the icon display method, choosing "Locked" and "Unlocked" icons from the system's preset icon library. Since the six doors of a train carriage are symmetrically distributed on both sides (three on the left and three on the right), the operator adjusts the arrangement of the parameters in the data item to configure the display position of the six door parameters in a 2x3 layout. After arrangement, the three icons in the first row correspond to the status of doors 1, 2, and 3 on the left, respectively, and the three icons in the second row correspond to the status of doors 1, 2, and 3 on the right, respectively. In this way, maintenance personnel can intuitively identify the actual physical location of each door on the train by the position of the icons when viewing the monitoring interface, without the need for additional text labels. For the air conditioning temperature data item, the data type is unsigned, and the parameter value represents the temperature value. The operator selects the text display method.

[0038] For trend chart display, operators need to configure the following: configure the time axis range, display current data (last hour) or historical data (0:00 to 24:00); select summary display or discrete display mode.

[0039] The background processing flow involved in this step is as follows: The presentation layer sends the user's display configuration parameters to the chart generation service in the application layer. The chart generation service validates the configuration parameters, and if the validation passes, the application saves the configuration parameters.

[0040] Step S4: Logical expression editing and verification steps.

[0041] In this step, operators configure conditional expressions through a graphical user interface. The "Display Logic" field can be selected in the configuration area for each data item, where operators can enter the conditional expression.

[0042] Conditional expressions are composed of comparison operators and logical operators, as detailed in Table 1: Table 1. Conditional Expressions type Operators / Functions illustrate Comparison operations >, <, >=, <=, ==, != Numerical comparison, with support for threshold judgment Logical operations AND, OR, NOT Combining conditions to construct complex logic Taking the air conditioner temperature data item as an example, the operator configures the following conditional expressions: "value<=12", "12<value<=19", "19<value<=28 |" and "value>28". The expressions define four temperature intervals: ≤12°C is low temperature abnormality, 12 to 19°C is low temperature normal, 19 to 28°C is normal temperature normal, and >28°C is high temperature abnormality. Each interval corresponds to a different icon style and color: the low temperature abnormality corresponds to a purple abnormality icon, the low temperature normal corresponds to a blue normal icon, the normal temperature normal corresponds to a green normal icon, and the high temperature abnormality corresponds to a red abnormality icon.

[0043] Taking the door lock status data item as another example, since its data type is boolean, the operator configures the conditional expressions as: "value==0", that is, when the parameter value is 0 (unlocked), a red unlocked icon is displayed, and "value==1", that is, when the parameter value is 1 (locked), a green locked icon is displayed.

[0044] The system performs two layers of verification on the conditional expression: the first layer is syntax verification, which checks whether the parentheses of the expression are matched, the use of operators is legal, and the operands are complete; the second layer is parameter type matching verification, which checks whether the types of operands on both sides of the operator are compatible (for example, boolean type data items should not use numerical comparison operators such as greater than and less than). After the verification is passed, the conditional expression and its mapping rules are stored in the middle platform service layer; when the verification fails, the system highlights the error location and error reason on the interface, and prompts the operator to make modifications.

[0045] The background processing flow involved in this step is: the presentation layer sends the conditional expression input by the user to the condition execution service of the application layer to verify the expression. After all nodes pass the verification, the expression is compiled into executable condition judgment logic and stored.

[0046] Step S5: Preview generation step.

[0047] In this step, the operator views the configuration effect through the preview function. A "status monitoring preview" area is provided on the right side of the interface, and a selection drop-down box for the preview train number (such as T01) is displayed in the preview area. After the operator selects the preview train, the application layer execution service module reads the real-time data of the train from the storage layer, and generates preview data according to the configured display mode, logical expression and mapping rules. The preview area of the presentation layer displays the preview data as a renderings consistent with the actual monitoring interface.

[0048] Step S6: Publishing and permission shunting step.

[0049] In this step, after the operator confirms that the configuration is correct, the configuration information is published.

[0050] For the pre-configured subsystem monitoring page, the configuration data takes effect immediately after publication, and all operations and maintenance personnel can view the configuration page in the subsystem status monitoring interface after logging into the system.

[0051] For user-defined subsystem monitoring pages, the system offers permission options during publishing: visible only to the user or visible to all users. When "visible only to the user" is selected, the configuration page only appears in the monitoring interface of the operator's personal account and cannot be seen by other users; when "visible to all" is selected, the configuration page is visible to all users, just like the default page.

[0052] After the configuration data is published, it is persistently stored in the data management module of the middleware service layer via the application layer. The middleware service layer immediately pushes the new configuration information to the presentation layer of each online user. The presentation layer reloads and renders the monitoring interface according to the new configuration, so that the configuration information takes effect immediately.

[0053] The detailed implementation methods of each module of the system are described below: The data storage module of the storage layer is implemented as follows: a time-series database is used to store sensor data with time-series characteristics, and a relational database is used to store device ledger information and configuration information. The time-series database uses high-performance time-series database engines such as InfluxDB or TDengine, supporting high-throughput data writing and efficient time-range-based queries. The data entry process is as follows: after the vehicle-side sensor data reaches the ground gateway via the MVB bus, the data acquisition program performs protocol parsing and format conversion, writing each parameter into the time-series database according to a unified format of "data item ID-carriage number-device number-timestamp-parameter value". Simultaneously, the data acquisition program publishes data change events to a message queue, and the conditional execution service module achieves real-time data updates by subscribing to the message queue.

[0054] The data management module of the middle platform service layer is implemented as follows: Data item tables, subsystem tables, binding relationship tables, and configuration parameter tables are established in a relational database. The data item table records information such as the name, type, applicable vehicle model, and list of associated parameters for each data item; the subsystem table records information such as the name, type (preset or custom), and creator of the subsystem; the binding relationship table records the association between the subsystem and the data item, as well as vehicle model binding information; and the configuration parameter table records the display configuration, logical expression configuration, and mapping rules for each data item. The interface call module exposes a data query interface through a RESTful API, supporting GET requests to query real-time data by data item ID and historical data by time range, and supporting POST requests to submit configuration data.

[0055] The application layer's monitoring item configuration service module employs a microservice architecture for its sub-modules. The data item management sub-module provides interfaces for creating, querying, modifying, and deleting data items, and integrates a data synchronization mechanism with the knowledge base management system to ensure consistency between the parameter information in data items and the knowledge base management system. The data association sub-module provides the interaction logic for subsystem management and data item association, automatically triggering the establishment or release of data subscription channels when the binding relationship changes through an event-driven mechanism. The display mode configuration sub-module maintains the data model for display mode configuration parameters, including list-style and trend chart-style configuration models, each corresponding to different data structures. The logic configuration sub-module has a built-in expression parsing engine, using a recursive descent parsing algorithm to perform lexical and syntactic analysis of conditional expressions and compile them into executable judgment logic. The preview and release sub-module coordinates the conditional execution service module and the presentation layer to generate and render preview data, and performs configuration persistence and push during the release operation.

[0056] The presentation layer's configuration interface module is implemented based on a front-end web framework. The configuration process employs a step-by-step guided design, dividing the process into four steps, which users follow sequentially to complete. A list-style configuration interface (e.g.) is used. Figure 4 As shown, the interface uses a left-right split layout. The left side displays the data item configuration list and operation buttons, while the right side is a real-time preview area. Each data item configuration entry supports operations such as moving up, moving down, pinning, editing, copying, and deleting, allowing users to flexibly adjust the configuration. The subsystem status monitoring interface module includes a list monitoring view (such as...). Figure 5 (as shown) and trend monitoring views (such as) Figure 6 (As shown). The list monitoring view displays the status of each subsystem in a card-style layout. Each card corresponds to a subsystem or data item, and the status values ​​of each piece of equipment in each carriage are displayed in list form. The trend chart monitoring view is implemented based on a front-end chart plugin service and supports interactive functions such as time axis zooming and hovering over data points to view details.

[0057] The core innovations of this invention include: Innovation Point 1: A zero-code configurable monitoring system construction method. In traditional train monitoring systems, monitoring pages, judgment logic, and display rules are often hard-coded into the software. Modifications require developer intervention, resulting in long cycles and high costs. This invention innovatively proposes a complete zero-code configuration solution: through an interactive process of "data item management → data association → display method and logic configuration → preview and release," maintenance personnel can customize subsystem monitoring pages without writing any code. It is easy to learn, efficient, and reusable.

[0058] Data items, as structured reuse units, aggregate and manage similar parameters from different compartments of the same vehicle model, significantly improving configuration efficiency.

[0059] Configurations take effect immediately upon deployment, supporting both global and private implementations, thus enabling a high degree of flexibility and personalization in the monitoring system.

[0060] Innovation Point Two: Physical Space Mapping and Diverse Visualization. This invention breaks through the limitations of traditional monitoring systems that only display data in charts and graphs, mapping the physical spatial layout of the train to the monitoring data. Users can adjust the order of data items to establish a correspondence between the displayed data position and the actual physical position of the train (such as the symmetrical distribution of the six doors on both sides of the carriage), improving readability. Simultaneously, the system supports multiple display methods, including text, preset icons, and uploaded icons, and allows data values ​​to be dynamically mapped to different icons and color states through logical expressions, making abnormal states immediately apparent and greatly improving the information transmission efficiency of the monitoring interface.

[0061] Innovation Point Three: Reducing Redundant Operations Such as Queries. Traditional monitoring systems require users to go through multiple levels of menu searches, filtering, and queries to see the desired status data. This invention, through a pre-configured monitoring list and publishing mechanism, allows users to directly browse any train set after entering the system. Monitoring items are automatically displayed in a list format, showing the status of each carriage without any retrieval process. This data-driven problem analysis model helps users quickly gain insights, providing a reliable and visualized data foundation for operational safety, train maintenance, problem troubleshooting, and resource allocation.

[0062] Innovation Point Four: Layered Architecture Design. The system adopts a layered architecture design consisting of a storage layer, a middleware service layer, an application layer, and a presentation layer. The knowledge base management system uniformly maintains the train status parameter database, and the monitoring system retrieves data on demand through standardized interfaces, ensuring data consistency and traceability. This design allows changes to monitoring configurations to be independent of changes to the underlying data source, further enhancing the system's maintainability and reusability.

[0063] In summary, this invention, with configurability, visualization, and zero-code as its core, constructs a flexible, efficient, and easy-to-use monitoring system for rail transit train subsystems. It significantly reduces the maintenance cost and usage threshold of the monitoring system, providing an innovative technical solution for intelligent operation and maintenance of rail transit.

Claims

1. A rail transit train subsystem monitoring system, characterized in that, include: The storage layer includes a data storage module for receiving pre-processed data collected by vehicle-end sensors and storing it in a standardized database. The data covers the overall status data of the train, system and component status data, and environmental parameter data. The middleware service layer includes a data management module and an interface call module. The data management module is used to manage the data in the storage layer and establish logical relationships between the data. The interface call module is used to provide data call services to the application layer through standardized interfaces. The application layer includes a monitoring item configuration service module and a conditional execution service module. The monitoring item configuration service module includes a data item management submodule, a data association submodule, a display mode configuration submodule, a logic configuration submodule, and a preview and release submodule, which are used to implement data item creation, subsystem binding of data items, display mode configuration, logical expression editing and verification, and preview and release operations, respectively. The conditional execution service module is used to execute automatic judgment logic based on the configured logical expression. The presentation layer includes a process configuration interface module and a subsystem status monitoring interface module. The process configuration interface module provides a data item management interface and a monitoring data item configuration interface, allowing users to complete zero-code configuration operations. The subsystem status monitoring interface module is used to display the status data of each subsystem monitoring item in list form or trend chart form after the configuration is published.

2. The rail transit train subsystem monitoring system of claim 1, wherein, In the data storage module of the storage layer, the data processing chain is as follows: after the vehicle-side sensors collect data, it undergoes filtering and noise reduction preprocessing in sequence, and then is transmitted to the ground system through the MVB bus, and finally stored in the database with the standardized structure.

3. The rail transit train subsystem monitoring system of claim 1, wherein, The data management module of the middle platform service layer is also used to: establish logical relationships between different data, support data addition, deletion, modification and query operations, and maintain the binding relationship between data items and subsystems; the interface call module provides data access services to the application layer through standardized interfaces.

4. The rail transit train subsystem monitoring system of claim 1, wherein, In the monitoring item configuration service module of the application layer: the data item management submodule is used to query parameters and create data items in the knowledge base management system, and to group similar parameters of different compartments of the same model into the same data item; The data association submodule provides an interactive interface for subsystem selection and data item association, and receives vehicle model binding information; The display mode configuration submodule is used to receive user-configured list-style or trend chart-style display parameters, including display format selection and physical space layout mapping parameters; The logic configuration submodule receives conditional expressions edited by the user and performs syntax validation and operator parameter type matching validation on the expressions; the preview and release submodule calls the conditional execution service module to generate preview data and performs a release operation to write the configuration data to the middle platform service layer after user confirmation.

5. The rail transit train subsystem monitoring system of claim 1, wherein, The process configuration interface module of the presentation layer provides an interface including a configuration process homepage, a list-style configuration interface, and a trend graph-style configuration interface. The configuration process homepage provides entry points for predefined system monitoring and custom monitoring pages. The subsystem status monitoring interface module includes a list monitoring view and a trend graph monitoring view. The list monitoring view displays the real-time status of each subsystem monitoring item in a list format, and the trend graph monitoring view displays the data trend of the monitoring item in the form of a time series curve.

6. A rail transit train subsystem monitoring configuration method, characterized in that, The application of a rail transit train subsystem monitoring system as described in any one of claims 1 to 5 includes the following steps: S1. Data item creation steps: Obtain the monitored item parameters of the subsystem in the knowledge base management system, create data items, group the same type of parameters of different carriages of the same train into the same data item and perform structured processing, and the data item serves as the basic unit for subsequent configuration; S2. Subsystem data item binding steps: In the monitoring data item configuration interface, select a preset subsystem or a newly created subsystem, associate the created data items with the subsystem, and determine the data source range by vehicle type binding. The system automatically obtains the real-time data of the corresponding carriage from the storage layer according to the bound data items. S3. Display mode configuration steps: Configure the display mode for each data item through a graphical interactive interface. The display mode includes list mode and trend chart mode. The list mode configuration includes display format as text or icons, and supports layout mapping configuration based on the train's physical space. The trend chart mode configuration includes the selection of current data or historical data and the display mode of summary or discrete display. S4. Logical Expression Editing and Verification Steps: Configure conditional expressions through the graphical interactive interface. The conditional expressions include comparison operators and / or logical operators. Use comparison operators and logical operators to construct judgment rules and map the real-time values ​​of data items to different icon styles or color states. After the system performs syntax verification on the conditional expressions, it stores them in the middle platform service layer. S5. Preview generation steps: The application layer generates preview data for the monitoring page based on the configured data items, display methods, and conditional expressions, and displays the preview effect through the presentation layer; S6. Publishing and Permission Distribution Steps: After confirming that the configuration is correct, publish the configuration information. The configuration data is written to the middleware service layer through the application layer and takes effect immediately. Based on the publishing settings, the configuration page is distributed to be visible to all users or to individuals.

7. The rail transit train subsystem monitoring configuration method of claim 6, wherein, In step S1, the parameter data types of the data items include boolean type and unsigned type. The data items are structured according to the same type of parameters for different carriages of the same model, so that a single data item contains the same type of parameter values ​​for multiple carriage dimensions.

8. The method of claim 6, wherein, In step S2, a subsystem is associated with multiple data items. The system automatically filters and displays matching carriage data from the storage layer based on the bound vehicle model and data items.

9. The method of claim 6, wherein, In step S3, the specific method of configuring the list-style layout mapping is as follows: by adjusting the arrangement order of different parameters in the data items, a correspondence is established between the data display position of each parameter and the equipment installation position in the actual physical space of the train.

10. The method of claim 6, wherein, In step S3, the list-style icon display method supports system-preset icons and user-uploaded custom icons.

11. The method of claim 6, wherein, In step S4, the logical operators include AND, OR, and NOT; multiple comparison operations are combined through logical operators to form a compound conditional expression, and the system performs matching verification on the operand types of each operator during the verification process.

12. The method of claim 6, wherein, In step S6, the pre-set subsystem monitoring page is visible to all users after it is published; the user's custom subsystem monitoring page can be selected to be visible only to the user or to all users when it is published.