Management method for rail transit private network communication operation and maintenance engine and medium

Abstract

The invention provides a management method for a rail transit private network communication operation and maintenance engine. The management method comprises the following steps: S1, centralized management of service subsystems; s2, obtaining and processing operation and maintenance data; and S3, fault alarms are pushed in a graded manner. The invention further provides a readable storage medium. The management method for the rail transit private network communication operation and maintenance engine and the medium have the advantages that multiple service subsystems in a communication operation and maintenance system are managed in a centralized mode, the equipment operation states and alarm information of all the subsystems are collected through an event-driven mechanism, fault information is pushed in time, and the operation and maintenance efficiency of the communication operation and maintenance engine is improved. Operation and maintenance personnel are assisted to accurately position and solve faults, and the fault processing efficiency is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to a rail transit private network communication operation engine, and in particular to a management method and medium for a rail transit private network communication operation engine. BACKGROUND

[0002] In recent years, private network communication operation systems have been widely used in urban rail transit, industrial Internet of Things and other scenarios. However, existing systems often lack unified management and analysis capabilities, resulting in low resource utilization and high operation and maintenance costs.

[0003] Currently, the private network communication solution in the industry usually relies on independent subsystem monitoring tools to provide limited alarm management functions for single subsystems. For example, SCADA system is an industrial automation system for monitoring and controlling distributed devices and production processes, which consists of field devices, communication networks, central control systems, databases and other parts. However, these systems lack overall coordination capabilities and are difficult to support cross-system collaboration and fault linkage processing. In terms of fault location, there is also a lack of intuitive and accurate picture switching and fault location functions, which makes the operation and maintenance personnel still need to spend a lot of time and effort when handling faults. SUMMARY

[0004] In order to solve the problems in the prior art, the present application provides a management method and medium for a rail transit private network communication operation engine.

[0005] The present application provides a management method for a rail transit private network communication operation engine, comprising the following steps:

[0006] S1, centralized management of business subsystems;

[0007] S2, acquisition and processing of operation and maintenance data;

[0008] S3, hierarchical push of fault alarms.

[0009] As a further improvement of the present application, in step S1, the private network communication comprehensive operation engine divides the rail transit communication system into a plurality of independent microservice modules according to business fields through a microservice architecture.

[0010] As a further improvement of the present application, the independent microservice modules include:

[0011] Device health management microservice: adopts edge computing architecture, deploys lightweight database at station level, and only reports warning events to cloud center service through MQTT protocol, which can independently manage the whole life cycle data of switches and overhead line equipment;

[0012] Emergency dispatching and command microservice: uses a graph database to store emergency plan correlation, receives real-time exception event streams from track state monitoring services through Kafka, integrates unmanned aerial vehicle inspection data and digital twin simulation engine, and is responsible for emergency event handling processes;

[0013] Energy consumption dynamic monitoring microservice: uses a time series database to store minute-level energy consumption data, uses a LightGBM algorithm to realize independent update of an energy consumption prediction model, and is responsible for traction power supply and energy consumption analysis of the environmental control system;

[0014] Security risk management and control microservice: uses a document database to store multi-dimensional risk profiles, calculates risk indexes in real time through Flink, is responsible for risk quantitative assessment and closed-loop disposal tracking, and helps operation and maintenance personnel locate system data;

[0015] Data intelligent analysis microservice: uses a data lake architecture to store raw data, uses a Spark StructuredStreaming stream processing engine to realize stream-batch integrated processing, can provide support for multi-source data fusion and decision-making, integrates heterogeneous data streams such as signal systems, and has real-time analysis and prediction capabilities;

[0016] Low-altitude cooperative inspection microservice: uses an edge computing node to process real-time video streams, uses a YOLOv7 algorithm to realize track foreign object detection, and stores inspection track and abnormal point data in a time-space database.

[0017] As a further improvement of the present application, in step S2, dynamic cooperation and efficient response between each independent microservice module are realized using an event-driven architecture, and through a standardized event bus and a multi-stage processing pipeline, a closed loop from data acquisition to decision response is realized.

[0018] As a further improvement of the present application, in step S2,

[0019] A multi-source data acquisition layer composed of device health management microservice, energy consumption dynamic monitoring microservice, and low-altitude cooperative inspection microservice is constructed to form a device operation data acquisition network. Industrial-grade vibration sensors are deployed in the device health management microservice to monitor component state data. Real-time unmanned aerial vehicle video streams are received in the low-altitude cooperative inspection microservice, and recognition models are deployed on edge computing nodes to realize automatic track foreign object recognition. The energy consumption dynamic monitoring microservice directly interfaces with the energy consumption management system to collect three-phase current and voltage data from power supply stations.

[0020] As a further improvement of the application, an industrial-grade vibration sensor is deployed in the equipment health management microservice to continuously monitor the state data of key components such as bogies with a high-precision sampling frequency of 200 ms; in the low-altitude cooperative inspection microservice, a YOLOv7 model is deployed on the edge computing node to realize automatic identification of track foreign objects by receiving real-time 4K video streams of unmanned aerial vehicles through the RTMP protocol; in the energy consumption dynamic monitoring microservice, the energy consumption management system is directly connected to collect three-phase current and voltage data of power supply stations at a frequency of 1 Hz.

[0021] As a further improvement of the application, in step S2,

[0022] A standardized event definition specification is formulated to establish a unified event Schema containing four layers of eventID, type, timestamp, and payload.

[0023] As a further improvement of the application, the payload is strictly constrained by JSON Schema.

[0024] As a further improvement of the application, three types of core events are defined: a device abnormal event is triggered when the device vibration value exceeds the threshold, a track intrusion event is generated when the confidence of the object identified by the unmanned aerial vehicle exceeds the threshold, and an energy consumption exceeding event is issued when the energy consumption of the power supply station continuously exceeds the threshold for a period of time, ensuring that all microservices use unified semantics for communication.

[0025] As a further improvement of the application, three types of core events are defined: a device abnormal event is triggered when the device vibration value exceeds 5 mm / s, a track intrusion event is generated when the confidence of the object identified by the unmanned aerial vehicle exceeds 90%, and an energy consumption exceeding event is issued when the energy consumption of the power supply station continuously exceeds the threshold for 15 minutes, ensuring that all microservices use unified semantics for communication.

[0026] As a further improvement of the application, in step S2,

[0027] A distributed event bus is designed, a three-level Topic system is built based on Apache Pulsar, the real-time alarm channel uses QoS=2 to ensure key event transmission, the analysis data channel sets QoS=1 to balance timeliness and reliability, the historical storage channel uses QoS=0 to realize batch data storage, an MQTT gateway protocol converter is deployed on the station-level edge node to unify the data of various Internet of Things terminal devices and access the cloud event bus, forming a hierarchical data processing capability.

[0028] As a further improvement of the application, in step S2,

[0029] A multi-level processing pipeline is formed, the stream processing layer uses Flink to realize sliding window calculation, and analyzes the operation of the equipment; the batch processing layer associates historical event data with the maintenance order database through Spark, and establishes an equipment health evaluation model; and the inference layer deploys a deep learning model to perform alarm and predictive maintenance.

[0030] As a further improvement of the application, in step S2,

[0031] For old devices that do not support event push and cannot be upgraded, data collection is performed through polling and edge agents, and is forwarded to the private network communication integrated operation and maintenance engine.

[0032] As a further improvement of the application, in step S3,

[0033] Integrated in the emergency dispatch command microservice, combined with the digital twin simulation engine and the large screen display, according to the severity of the fault or anomaly or the alarm level, a hierarchical push strategy is implemented;

[0034] When a serious fault occurs, a high-priority alarm is triggered, which is displayed on the operation and maintenance screen, and the responsible person or emergency response team is immediately contacted;

[0035] When a problem that does not seriously affect operation occurs, it is highlighted on the operation and maintenance screen and the maintenance personnel are notified to maintain;

[0036] When a device daily fluctuation and reminder occurs, a low-priority alarm is triggered, which is pushed to the operation and maintenance personnel in the form of log file recording or regular report for regular inspection.

[0037] As a further improvement of the application, the management method further comprises:

[0038] S4, the operation and maintenance personnel log in to the private network;

[0039] A centralized management interface is designed based on Web, which can display the running state, alarm information and system log of the private network communication integrated operation and maintenance engine, so as to facilitate real-time monitoring, fault diagnosis and management of the operation and maintenance personnel, the front end is developed using React, Vue and Angular framework to build an intuitive user interface, and the back end service is built using Spring Boot and Node.js technology to process all operation and maintenance requests and data access;

[0040] Through VPN, the operation and maintenance personnel are ensured to access the private internal network and be encrypted when accessing the operation and maintenance engine system, so as to prevent data leakage or external attacks;

[0041] In order to avoid unauthorized access, two-step verification is used to improve account security and reduce the risk of sensitive data leakage;

[0042] Set access control and permission management, and combine with audit log function, the private network communication comprehensive operation and maintenance engine records all login behaviors and operation records, ensures that the problem can be traced back.

[0043] The application further provides a readable storage medium, wherein the readable storage medium stores execution instructions, and the execution instructions are used for implementing the method when executed by a processor.

[0044] The application has the beneficial effects that: a management method and medium for track traffic private network communication operation and maintenance engine are provided, a plurality of business subsystems in the communication operation and maintenance system are managed in a centralized manner, the device operation states and alarm information of all the subsystems are collected through an event-driven mechanism, fault information is timely pushed, the operation and maintenance personnel are assisted to accurately locate and solve the faults, and the fault processing efficiency is improved. BRIEF DESCRIPTION OF DRAWINGS

[0045] In order to more clearly illustrate the technical solutions of the embodiments of the application, the drawings needed to be used in the embodiment description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the application, and other solutions can be obtained by those skilled in the art without creative labor on the basis of these drawings.

[0046] Figure 1 It is a private network communication comprehensive engine transmission line diagram. DETAILED DESCRIPTION

[0047] It should be noted that the embodiments in the application and the features in the embodiments can be combined with each other without conflict.

[0048] In the description of the application, it should be understood that the terms "center", "longitudinal", "transverse", "upper", "lower", "front", "rear", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer" and the like indicate the orientation or positional relationship based on the orientation or positional relationship shown in the drawings, and are only for the convenience of describing the application and simplifying the description, and do not indicate or imply that the device or element must have a particular orientation, be constructed and operated in a particular orientation, therefore, it cannot be understood as a limitation on the scope of protection of the application. In addition, the terms "first", "second" and the like are only for the purpose of description, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the technical features indicated. Therefore, the features limited by "first", "second" and the like can explicitly or implicitly include one or more features. In the description of the application, unless otherwise specified, the meaning of "a plurality of" is two or more.

[0049] In the description of the present application, it should be noted that unless otherwise expressly specified and limited, the terms "mounting", "connection", "connecting" should be understood in a broad sense, for example, it can be fixed connection, or detachable connection, or integrally connected; it can be directly connected, or indirectly connected through an intermediate medium, or the internal communication of two elements. For those skilled in the art, the specific meaning of the above terms in the present application can be understood according to the specific circumstances.

[0050] The present application will be further described in the following description and specific embodiments in conjunction with the accompanying drawings.

[0051] The present application proposes a management method for track traffic special network communication operation and maintenance engine, aiming at the problems of single function, insufficient data processing capacity, slow alarm response and other problems in the existing communication operation and maintenance system in the track traffic industry, which leads to the difficulty in timely discovering and solving the operation and maintenance faults. At the same time, each subsystem runs independently, and it is difficult to realize unified data collection, management and analysis. Therefore, the present application aims to manage multiple business subsystems by centralized management, push fault information in real time, and link with the operation and maintenance platform through the event-driven mechanism, so that the maintenance personnel can timely and accurately master the fault information and equipment status, and improve the fault handling efficiency and the reliability of the system.

[0052] A management method for track traffic special network communication operation and maintenance engine mainly includes 4 steps. Step one is business subsystem centralized management, step two is operation and maintenance data acquisition and processing, step three is fault alarm hierarchical push, and step four is operation and maintenance personnel special network login.

[0053] Through this method, the operation and maintenance personnel can centrally manage the track traffic business subsystem and meet the demand of monitoring and early warning alarm, solving the problems of insufficient demonstration, unreasonable design and imperfect system in the design of communication operation and maintenance system in the industry.

[0054] As shown in Figure 1 The special network communication comprehensive operation and maintenance engine adopts micro-service + event-driven architecture, integrates multiple communication protocols and distributed data processing framework, centrally manages the business subsystems of track traffic, and reflects the running status of each subsystem to the computer in the control center. When a fault occurs, the special network communication comprehensive operation and maintenance engine can obtain alarm information and key parameters through multiple ways, and push the fault information through the triggering mechanism of the operation and maintenance platform, so that the operation and maintenance personnel can timely and accurately understand the running status of the entire track traffic system equipment, fault information and key equipment information, in order to assist the command personnel to handle the emergency fault, so that the special network communication comprehensive operation and maintenance engine can be linked with the business application to provide fault positioning function.

[0055] Step one, business subsystem centralized management

[0056] The private network communication comprehensive operation and maintenance engine divides the existing rail transit communication system into independent microservice modules according to business fields through a microservice architecture, specifically including: a device health management module, an emergency dispatch command module, an energy consumption dynamic monitoring module, an operation and maintenance process management module, a safety risk control module, a data intelligent analysis module, and a low-altitude collaborative monitoring module.

[0057] ①Device health management microservice: An edge computing architecture is adopted, a lightweight database is deployed at the station level, and only warning events are reported to the cloud center service through the MQTT protocol. The full life cycle data of devices such as switches and overhead lines can be independently managed.

[0058] ②Emergency dispatch command microservice: A graph database is used to store the correlation of emergency plans, and real-time exception event streams from the track state monitoring service are received through Kafka. The unmanned aerial vehicle inspection data and the digital twin simulation engine are integrated to be responsible for the emergency event disposal process.

[0059] ③Energy consumption dynamic monitoring microservice: A time series database is used to store minute-level energy consumption data, and a LightGBM algorithm is used to realize independent update of the energy consumption prediction model. It is responsible for energy consumption analysis of traction power supply and environmental control systems.

[0060] ④Safety risk control microservice: A document database is used to store multi-dimensional risk profiles, and a Flink real-time computing risk index is used. It is responsible for risk quantification evaluation and closed-loop disposal tracking, and helps operation and maintenance personnel to locate system data.

[0061] ⑤Data intelligent analysis microservice: A data lake architecture is used to store raw data, and a Spark StructuredStreaming stream processing engine is used to realize stream batch integrated processing. It can provide support for multi-source data fusion and decision-making, integrate heterogeneous data streams such as signal systems, and has real-time analysis and prediction capabilities.

[0062] ⑥Low-altitude collaborative inspection microservice: An edge computing node is used to process real-time video streams, a YOLOv7 algorithm is used to realize track foreign object detection, and inspection track and abnormal point data are stored in a spatio-temporal database.

[0063] The microservice architecture can provide flexible service splitting and expansion capabilities to adapt to future business growth, and the event-driven architecture ensures the system's rapid response to abnormal events, enabling immediate triggering of fault handling processes. The operation and maintenance engine based on the microservice architecture and the event-driven architecture greatly reduces the coupling between different services, improves the robustness, maintainability, and scalability of the operation and maintenance engine.

[0064] Step two, acquisition and processing of operation and maintenance data

[0065] ①Build a multi-source data collection layer composed of device health management microservices, energy consumption dynamic monitoring microservices, and low-altitude cooperative inspection microservices to form a device operation data collection network. Deploy industrial-grade vibration sensors in the device health management microservices to continuously monitor the state data of key components such as bogies with a high-precision sampling frequency of 200ms; in the low-altitude cooperative inspection microservices, receive real-time 4K video streams from drones through the RTMP protocol, and deploy the YOLOv7 model on edge computing nodes to achieve automatic identification of track intrusions; in the energy consumption dynamic monitoring microservices, directly interface with the energy consumption management system to collect three-phase current and voltage data from power supply stations at a frequency of 1Hz.

[0066] ②Develop standardized event definition specifications and establish a unified event Schema with four layers of structure: eventID, type, timestamp, and payload. The payload is strictly constrained using JSON Schema. Define three types of core events: trigger a device anomaly event when the device vibration value exceeds 5mm / s, generate a track intrusion event when the drone identifies a track intrusion object with a confidence level greater than 90%, and issue an energy consumption exceeding event when the power supply station's energy consumption exceeds the threshold for 15 consecutive minutes, ensuring that all microservices use a unified semantic for communication.

[0067] ③Design a distributed event bus based on Apache Pulsar to build a three-level Topic system. Use QoS=2 for real-time alert channels to ensure key event transmission, set QoS=1 for analysis data channels to balance timeliness and reliability, and use QoS=0 for historical storage channels to achieve batch data storage. Deploy an MQTT gateway protocol converter on station-level edge nodes to unify various Internet of Things terminal device data and access the cloud event bus, forming a hierarchical data processing capability.

[0068] ④Form a multi-level processing pipeline. The stream processing layer uses Flink to implement sliding window calculations and analyze device operation; the batch processing layer associates historical event data with the maintenance work order database through Spark to establish a device health assessment model; and the inference layer deploys deep learning models for alarm and predictive maintenance.

[0069] ⑤For old and outdated devices that do not support event pushing and cannot be upgraded, data can be collected through polling and edge agents and forwarded to the private network communication integrated operation and maintenance engine to ensure full coverage of monitoring scenarios.

[0070] Use event-driven architecture to achieve dynamic collaboration and efficient response between microservices, replacing the inefficient mode of traditional hard-coded linkage. Through a standardized event bus and a multi-level processing pipeline, achieve a closed loop from data collection to decision response.

[0071] Step three, fault alarm hierarchical push

[0072] Integrate the emergency dispatching and command microservice with the digital twin simulation engine and large-screen display, and implement a hierarchical push strategy based on the severity or alarm level of the fault or anomaly.

[0073] ① Trigger a high-priority alarm when a serious fault (such as device downtime) occurs, display it on the operation and maintenance large screen, and immediately contact the responsible person or emergency response team through channels such as SMS and phone;

[0074] ② Highlight the problem on the operation and maintenance large screen when the system runs slowly or consumes excessive resources, and notify the operation and maintenance personnel through the app or email for maintenance;

[0075] ③ Trigger a low-priority alarm for device daily fluctuations and reminders, which can be pushed to ordinary operation and maintenance personnel for regular inspection through log file records or regular reports.

[0076] Step four, operation and maintenance personnel private network login

[0077] ① Design a centralized management interface based on Web, which can display the running status, alarm information, system log, and other information of the operation and maintenance engine system, facilitating real-time monitoring, fault troubleshooting, and management. Use React, Vue, and Angular frameworks to develop the front end and build an intuitive user interface, and use Spring Boot and Node.js technology to build the back-end service to handle all operation and maintenance requests and data access;

[0078] ② Ensure that the operation and maintenance personnel access the operation and maintenance engine system through a dedicated internal network and encryption through VPN to prevent data leakage or external attacks;

[0079] ③ To avoid unauthorized access, use two-step verification to improve account security and reduce the risk of sensitive data leakage;

[0080] ④ Set up access control and permission management, and combine with the audit log function. The operation and maintenance engine will record all login behavior and operation records to ensure that problems can be traced back.

[0081] Based on the above steps, the entire operation and maintenance engine system design is completed, realizing the full-process management of rail transit private network communication comprehensive operation and maintenance engine collection, aggregation, analysis, and display. The main improvement is to replace the existing single architecture or traditional centralized management mode in the rail transit industry. The microservice and event-driven architecture make the modules loosely coupled, solving the problems of response lag, fault diffusion, etc., which helps to improve the safety of rail transit operation and resource utilization, and reduce the operation and maintenance cost.

[0082] The application provides a management method for a rail transit private network communication operation engine, which realizes rapid data reporting and centralized management of various business subsystems of rail transit through a micro-service architecture and an event-driven architecture, realizes intelligent pushing of alarm information and linkage of fault positioning, and meets operation and maintenance requirements in different scenarios.

[0083] Compared with existing rail transit private network communication operation system platforms, the management method for the rail transit private network communication operation engine has stronger integration capability, can integrate data of multiple business subsystems, can centrally display fault state data, reduces information island problems, shortens fault processing time by receiving and processing fault information in real time and pushing alarms to maintenance personnel, and makes the system intelligently and automatically respond to faults, thereby improving the efficiency and reliability of the entire system.

[0084] The above is a further detailed description of the application in combination with specific preferred embodiments, and the specific implementation of the application cannot be limited to these descriptions. For ordinary skilled persons in the technical field to which the application belongs, some simple deductions or substitutions can be made without departing from the concept of the application, and all of them should be regarded as falling within the protection scope of the application.

Claims

1. A management method for a rail transit private network communication operation and maintenance engine, characterized in that, Comprise the following steps: S1, centralized management of business subsystems; S2, acquisition and processing of operation and maintenance data; S3, hierarchical push of fault alarms.

2. The management method for the rail transit private network communication operation and maintenance engine according to claim 1, characterized in that: In step S1, the private network communication comprehensive operation and maintenance engine divides the rail transit communication system into several independent microservice modules according to business fields through a microservice architecture.

3. The management method for the rail transit private network communication operation and maintenance engine according to claim 2, characterized in that: The independent microservice modules include: Device health management microservice: adopts an edge computing architecture, deploys a lightweight database at the station level, and only reports warning events to the cloud center service through the MQTT protocol, which can independently manage the whole life cycle data of switches and overhead line systems; Emergency dispatching and command microservice: uses a graph database to store emergency plan correlation, receives real-time exception event streams from the track state monitoring service through Kafka, integrates unmanned aerial vehicle inspection data and digital twin simulation engine, and is responsible for emergency event disposal processes; Energy consumption dynamic monitoring microservice: uses a time series database to store minute-level energy consumption data, uses a LightGBM algorithm to realize independent update of the energy consumption prediction model, and is responsible for traction power supply and energy consumption analysis of the environmental control system; Safety risk management and control microservice: uses a document database to store multi-dimensional risk profiles, calculates risk indexes in real time through Flink, is responsible for risk quantification evaluation and closed-loop disposal tracking, and helps operation and maintenance personnel locate system data; Data intelligent analysis microservice: uses a data lake architecture to store raw data, uses a SparkStructuredStreaming stream processing engine to realize stream-batch integrated processing, can provide support for multi-source data fusion and decision-making, integrates heterogeneous data streams such as signal systems, and has real-time analysis and prediction capabilities; Low-altitude cooperative inspection microservice: uses an edge computing node to process real-time video streams, uses a YOLOv7 algorithm to realize track foreign object detection, and stores inspection tracks and abnormal point data into a time-space database.

4. The management method for the rail transit private network communication operation and maintenance engine according to claim 1, characterized in that: In step S2, an event-driven architecture is used to realize dynamic cooperation and efficient response between the various independent microservice modules, and through a standardized event bus and a multi-stage processing pipeline, a closed loop from data acquisition to decision response is realized.

5. The management method for the rail transit private network communication operation and maintenance engine according to claim 4, characterized in that: In step S2, A multi-source data acquisition layer composed of device health management microservice, energy consumption dynamic monitoring microservice, and low-altitude cooperative inspection microservice is constructed to form a device operation data acquisition network. Industrial-grade vibration sensors are deployed in the device health management microservice to monitor the state data of components; In the low-altitude cooperative inspection microservice, real-time unmanned aerial vehicle video streams are received, and recognition models are deployed on edge computing nodes to realize automatic recognition of track foreign objects; in the energy consumption dynamic monitoring microservice, the energy consumption management system is directly connected to collect three-phase current and voltage data from power supply stations; Standardized event definition specifications are formulated, and a unified event Schema containing eventID, type, timestamp, and payload is established.

6. The management method for the rail transit private network communication operation and maintenance engine according to claim 4, characterized in that: In step S2, A distributed event bus is designed, a three-level Topic system is built based on Apache Pulsar, a real-time alarm channel uses QoS=2 to guarantee key event transmission, an analysis data channel sets QoS=1 to balance timeliness and reliability, a historical storage channel uses QoS=0 to realize batch data storage, an MQTT gateway protocol converter is deployed on a station-level edge node to uniformly access various Internet of Things terminal device data to the cloud event bus, and a hierarchical data processing capability is formed; A multi-level processing pipeline is formed, a stream processing layer uses Flink to realize sliding window calculation and analyze device operation conditions, a batch processing layer associates historical event data with a maintenance work order database through Spark to establish a device health evaluation model, and an inference layer deploys a deep learning model to perform alarm and predictive maintenance.

7. The management method for the rail transit private network communication operation and maintenance engine according to claim 1, characterized in that: In step S2, For old devices that do not support event push and cannot be upgraded, data is collected through polling and edge agents and forwarded to the private network communication comprehensive operation and maintenance engine. 8.The management method of the rail transit private network communication operation and maintenance engine according to claim 1, characterized in that: In step S3, The integrated emergency dispatch command microservice, combined with the digital twin simulation engine and the large screen display, implements a hierarchical push strategy according to the severity of the fault or anomaly or the alarm level; A serious fault triggers a high-priority alarm, which is displayed on the operation and maintenance screen and immediately contacts the responsible person or emergency response team; A non-serious problem affecting operation is highlighted on the operation and maintenance screen and notified to the maintenance personnel; Device daily fluctuations and reminders trigger low-priority alarms, which are pushed to the maintenance personnel in the form of log files or regular reports for regular checks.

9. The management method for the rail transit private network communication operation and maintenance engine according to claim 1, characterized in that: The management method further includes: S4, the private network login of the maintenance personnel; A centralized management interface is designed based on Web, which can display the running state, alarm information and system log of the private network communication comprehensive operation and maintenance engine, facilitating real-time monitoring, fault diagnosis and management of the maintenance personnel, the front end is developed using React, Vue and Angular frameworks to build an intuitive user interface, and the back end service is built using Spring Boot and Node.js technology to handle all operation and maintenance requests and data access; VPN is used to ensure that the maintenance personnel access the private network and are encrypted when accessing the operation and maintenance engine system, preventing data leakage or external attacks; To avoid unauthorized access, two-step verification is used to improve account security and reduce the risk of sensitive data leakage; Access control and permission management are set, and combined with the audit log function, the private network communication comprehensive operation and maintenance engine records all login behaviors and operation records to ensure that problems can be traced back.

10. A readable storage medium, characterized by, The readable storage medium stores execution instructions, and the execution instructions are executed by the processor to implement the method in any one of claims 1 to 9.

Images