Urban rail transit network-level train monitoring system based on cloud platform

Abstract

An urban rail transit network-level train monitoring system based on a cloud platform, wherein a network-level train monitoring system NATS is arranged in a network center cloud platform, and is used for collecting line ATS data for analysis and providing a network-level operation management function; additionally, the NATS has the functions of traffic command, operation index analysis, fully-automatic mapping, network and line coordinated command, transportation organization and assistant decision making. Compared with the prior art, the system has the advantage of displaying information of the comprehensive rail network for a large city, so that the network center can carry out overall operation command and dispatching for the city.

Description

Urban rail transit line network-level train monitoring system based on cloud platform Technical Field

[0001] The present invention relates to a train signal control system, and in particular to a cloud platform-based urban rail transit line network-level train monitoring system. Background Art

[0002] Currently, domestic rail transit ATS (Automatic Train Monitoring) systems primarily utilize a line-level architecture, encompassing control centers and station equipment. As a key component of subway signal control systems, the ATS system works alongside other signaling systems, including computer interlocking, trackside train control systems, onboard train control systems, and departure indicators, to achieve centralized monitoring of signaling equipment and control the automated operation of trains within the mainline according to pre-defined operational plans.

[0003] The ATS also interfaces with clock, wireless, and integrated monitoring systems to acquire data collected by external systems. This data is then combined with the signaling system data to provide a rich display of on-site conditions for train dispatchers and on-duty personnel at the control center and stations, enabling them to make dispatching decisions. The ATS provides signaling and train operation data to external systems through these interfaces, enabling these systems to complete their tasks.

[0004] However, with the sustained, rapid, and healthy development of the national economy and the implementation of the new urbanization strategy, urban rail transit is becoming increasingly characterized by high speed, density, diversification, networking, and intelligence. At the same time, how to meet passengers' needs for convenient travel while ensuring safe, stable, and controllable operations has become a technical challenge that needs to be addressed.

[0005] Summary of the Invention

[0006] The purpose of the present invention is to overcome the defects of the above-mentioned prior art and provide an urban rail transit line network-level train monitoring system based on a cloud platform.

[0007] The purpose of the present invention can be achieved by the following technical solutions:

[0008] According to the first aspect of the present invention, a cloud platform-based urban rail transit network-level train monitoring system is provided. The network-level train monitoring system NATS is set in the network center cloud platform to collect line ATS data for analysis and provide network-level operation management functions; at the same time, the NATS has driving command, operation indicator analysis, fully automatic mapping, network and line coordinated command, transportation organization and auxiliary decision-making functions.

[0009] As an optimal technical solution, the NATS adopts a cloud platform design and designs a virtual data center (VDC) and a virtual private cloud (VPC). The cloud platform transforms physical resources into virtual pools through VDC, and flexibly allocates data centers through different logical isolation methods. The resource pool within the VDC is divided into VPCs to achieve unified deployment of system resources.

[0010] As a preferred technical solution, the virtual data center VDC is divided according to professional or city lines.

[0011] As an optimal technical solution, the NATS design has a full-line data center to carry the computing and storage resources required by the center-level hardware of each professional system, and the data sharing center capacity meets the subsequent line expansion needs.

[0012] As an optimal technical solution, the NATS is provided with a workstation which uses a desktop cloud. All software runs on the cloud desktop server and displays the results on the desktop cloud workstation. The desktop cloud is divided into business network, storage network and management network as needed, and logical isolation is adopted between the networks.

[0013] As a preferred technical solution, the NATS access cloud platform network setting meets the following requirements:

[0014] NATS is hosted in the secure production network;

[0015] NATS networks are redundant and logically isolated, with a single network bandwidth of no less than 100M;

[0016] NATS network adopts a ring network mode, and single point failure of the network will not affect the operation of the system;

[0017] The maximum end-to-end network delay is less than 50ms, and the maximum switch switching delay is less than 50ms.

[0018] As a preferred technical solution, the devices deployed by NATS in the cloud platform include:

[0019] Virtual NATS interface server, virtual NATS application server, virtual NATS database server, virtual switch, and virtual Ethernet. The virtual NATS interface server, virtual NATS application server, virtual NATS database server, and virtual switch are all configured with dual-machine hot standby redundancy.

[0020] As a preferred technical solution, the NATS is logically divided into an interface layer, a platform layer, and an application layer.

[0021] As a preferred technical solution, the interface layer includes:

[0022] Interface with the network center / line CATS system to process and upload the information of various disciplines integrated and interconnected by the network center or this line according to the access standard of NATS;

[0023] The interface with the data sharing center is used to upload all the line CATS information data collected by NATS to the data sharing center, and upload the processed operation diagram data and driving index data in the format required by the data sharing center.

[0024] As an optimal technical solution, the platform layer is a business logic processing layer, including a real-time database, a historical database, a logic processing engine, and an intelligent analysis engine, which is used to collect line-side ATS data, perform specific logic analysis and processing, and send the results to the application layer.

[0025] As a preferred technical solution, the application layer includes:

[0026] The full network map display module is used to display all the locally planned rail transit lines in a window in the form of vector diagrams;

[0027] The station map display module is used to display the track, turnout, signal, static position information and other required information on the station map interface, so that dispatchers can understand the real-time status of signal equipment on site;

[0028] The train operation information display module is used to display the train operation information, wherein the train operation information includes the train identification number, the train destination number, the train early or late status, the train detention status, the train skipping status, the train location information, the train tracking mode, the train driving mode, and the train door status;

[0029] The train diagram display module is used to display the train diagram in a graphical interface. Based on the planned and actual train diagram data uploaded by the line, NATS stores the data and displays it on the diagram interface, allowing dispatchers to view the train's operating status. The actual train diagram can be refreshed in real time as the train moves.

[0030] Alarm event display module, used to view the alarms occurring on the line in real time in the system's alarm view;

[0031] The operation index analysis and display module is used to analyze and calculate the operation indexes related to driving based on the planned operation diagram and actual operation diagram data collected from the line, and then display the operation indexes on the user interface;

[0032] The statistical report query module is used to query and display commonly used statistical information and alarm event information, so that dispatchers can view statistical information and analyze historical data;

[0033] The playback module is used to playback the historical operation information of the system to view the historical operation status or conduct troubleshooting analysis.

[0034] As a preferred technical solution, the playback module directly reads the playback data file recorded when the application server software is running, can switch lines to view the playback information of different lines, and allows the user to control the playback speed and quickly locate the time required for playback by dragging the time scroll bar.

[0035] Compared with the prior art, the present invention has the following advantages:

[0036] 1. Compared with the traditional ATS system that can only display the route map of the line, the NATS system of the present invention can display information of the entire road network for large cities, so that the network center can conduct overall operation command and dispatch for the city;

[0037] 2. Compared with the single line traffic dispatching and commanding function of the traditional ATS system, the NATS system of the present invention provides operation management functions such as traffic command, operation index analysis, automatic map compilation, line network and line coordinated command, transportation organization and decision support, etc., realizing more centralized management of urban rail transit monitoring and dispatching;

[0038] 3. Compared to the traditional ATS system architecture, which is large and complex, the NATS signaling system of the present invention can be virtualized on the cloud platform with the help of a cloud platform, eliminating the need for extensive and in-depth modifications to the system itself. Leveraging the characteristics of the cloud platform, the hardware resources of each line can be integrated, reducing hardware settings. Flexible configuration can be achieved based on the scale of the NATS system, facilitating data migration of existing lines and subsequent line access and expansion, significantly improving overall system performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] FIG1 is a schematic diagram of the structure of the cloud platform network design of the present invention;

[0040] FIG2 is a schematic diagram of the structure of the cloud platform design of the present invention;

[0041] FIG3 is a schematic diagram of the NATS cloud platform architecture of the present invention;

[0042] Figure 4 is a schematic diagram of the CATS cloud platform architecture for new lines;

[0043] Figure 5 is a schematic diagram of the physical hardware architecture of the existing CATS entity;

[0044] Figure 6 is a schematic diagram of the LATS physical hardware architecture;

[0045] FIG7 is a schematic diagram of the NATS functional architecture of the present invention. DETAILED DESCRIPTION

[0046] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of the present invention.

[0047] The present invention designs a NATS (network-level train monitoring) system for urban rail transit based on a cloud platform. The rail transit network information cloud platform is designed in a comprehensive manner based on the short-term and long-term construction status of large-scale urban rail transit. It adopts technologies such as cloud platform, big data analysis and mining, and information sharing platform based on cloud computing to carry three major business categories: operation and production, enterprise management, and passenger service management. The cloud platform carries NATS / ATS (network / line-level train monitoring), NISCS / ISCS (network / line-level integrated monitoring system), NAFC / AFC (network / line-level automatic ticket vending and checking system), NACS / ACS (network / line-level access control system), NPSCADA / PSCADA (network / line-level power monitoring system) and other services of each line in the data center.

[0048] The present invention discloses a NATS system based on an information cloud platform. The system is set on the line network center cloud platform, collects line ATS data for analysis, and provides line network-level operation management functions. Compared with the traditional ATS system that can only display the route map of the line, the NATS system can display information of the entire road network for large cities, so that the line network center can conduct overall operation command and scheduling for the city. The NATS system provides operation management functions such as driving command, operation index analysis, automatic mapping, line network and line coordinated command, transportation organization and auxiliary decision-making, so as to achieve more centralized management of urban rail transit monitoring and scheduling. At the same time, the cloud platform design can integrate the hardware resources of each line, reduce hardware settings, and flexibly configure according to the scale of the NATS system, which is convenient for subsequent line access and expansion.

[0049] The present invention mainly includes the connection of the ATS systems of existing urban lines and lines under construction to the NATS system. The NATS system is connected to the line ATS, and the data collected from each line is uploaded to the data sharing center. At the same time, it provides operational management functions such as driving command, operation index analysis, fully automatic mapping, line network and line coordinated command, transportation organization and auxiliary decision-making.

[0050] The NATS system is deployed on an online network center cloud platform and has scalability to accommodate future capacity expansion. Furthermore, as an urban transportation system with high security requirements, NATS involves the personal and property safety of passengers, placing high security demands on its data. Therefore, NATS utilizes private cloud services within its cloud platform, which places high security demands on its data.

[0051] The specific process of the present invention is as follows:

[0052] 1) Cloud platform network design

[0053] a) Based on different application, management, and security protection levels, the cloud platform network is divided into a secure production network, an internal management network, and an external service network. Each business system is deployed in the secure production network, internal management network, and external service network according to its business attributes. Strong isolation technology of corresponding levels is used between the internal management network and the external service network; logical isolation technology is used between the secure production network and the internal management network. Security measures such as network boundary protection, intrusion prevention detection, web application protection, and DDOS traffic scrubbing are deployed. If both secure production and external service businesses exist, they should be deployed independently. An independent out-of-band management network is established to centrally manage the secure production network, internal management network, and external service network. See Figure 1.

[0054] b) The production safety network is primarily used for data communication and sharing across systems related to production safety and management, transportation command, and emergency command and dispatch. A separate dedicated network is set up for the NATS system safety network, which is closely related to driving safety.

[0055] c) The internal management network is mainly used for data communication and data sharing of enterprise information-related business systems such as enterprise management, operation management, construction management, and resource management.

[0056] d) The external service network is mainly used for data communication and data sharing of portal websites and other related external or public business systems.

[0057] 2) NATS Cloud Platform Design

[0058] a) The NATS system for new lines adopts a cloud platform design, while existing lines can maintain the physical equipment architecture or implement cloud-based equipment during major renovations.

[0059] b) Design virtual data centers (VDCs) and virtual private clouds (VPCs). The cloud platform uses VDCs to transform physical resources into virtual pools. Data centers can be flexibly allocated through different logical isolation methods. Resource pools within a VDC can be divided into VPCs to achieve unified deployment of system resources.

[0060] c) VDCs can be divided by discipline or city line. If VDCs are divided by discipline, each discipline, such as NATS / LATS, NISCS / ISCS, NAFC / AFC, NACS / ACS, and NPSCADA / PSCADA, is divided into VDCs. Lines 1, 2, ..., and N are divided into VPCs, each connected to a specific discipline's VDC. If VDCs are divided by city line, each line is divided into VDCs, and each discipline is divided into VPCs. While the disciplines within a city line are typically fixed, the number of lines increases due to urban expansion. Therefore, a more rational design is to divide by discipline, with disciplines divided into VDCs and lines divided into VPCs, to meet operational, production, and management needs. See Figure 2 for details.

[0061] d) Design a data center for the entire line to carry the computing and storage resources required by the center-level hardware of each professional system. The capacity of the data sharing center must meet the needs of subsequent line expansion. For example, the VDC divided by NATS in the early stage must meet the NATS business access of the subsequent expansion line.

[0062] e) The workstation uses desktop cloud, and all software runs on the cloud desktop server and displays the results on the desktop cloud workstation. The desktop cloud can be divided into business network, storage network and management network as needed, and logical isolation is used between networks to ensure that the basic platform will not be damaged by users.

[0063] f) The network settings for NATS access to the cloud platform meet the following requirements:

[0064] The NATS system is hosted in the secure production network;

[0065] NATS networks should be redundant and logically isolated, with a single network bandwidth of no less than 100M;

[0066] The NATS network should adopt a ring network mode so that a single point failure of the network will not affect the system operation;

[0067] Performance indicators such as the maximum end-to-end network delay (less than 50ms) and the maximum switch switching delay (less than 50ms) can meet the requirements of relevant specifications.

[0068] 3) The ATS system can be divided into three levels: the network-level NATS system, the line-level CATS system, and the station-level LATS system. The NATS system interfaces with the network center, data sharing center, and line CATS system for information exchange.

[0069] 4) The cloud platform IaaS layer deploys the cloud resource management platform according to the safety production network, internal management network, and external service network. The ATS system is incorporated into the cloud platform in an IaaS manner and meets the following requirements:

[0070] a) Network-level NATS and line-level CATS should be integrated into the cloud platform for unified management and divided into independent physical resource pools. Station-level LATS should be set up using independent physical machines;

[0071] b) In line-level NATS, line-level application servers, database servers, and interface devices are integrated into the cloud platform, and workstations use desktop cloud terminals;

[0072] c) In line-level CATS, line application servers, database servers, and interface devices are integrated into the cloud platform, and workstations use desktop cloud terminals;

[0073] d) Redundant virtual machines deployed by ATS on the cloud platform should not be set up on the same physical machine.

[0074] 5) The NATS system is deployed on a cloud platform. The system architecture is shown in Figure 3. It mainly includes the following cloud devices: virtual NATS interface server (dual-machine hot standby redundant configuration), virtual NATS application server (dual-machine hot standby redundant configuration), virtual NATS database server (dual-machine hot standby redundant configuration), virtual switch (dual-machine hot standby redundant configuration) and virtual Ethernet; desktop cloud devices: NATS monitoring workstation (desktop cloud terminal), large-screen interface computer (desktop cloud terminal); and external cloud devices: interface switch and firewall (dual-machine hot standby redundant configuration).

[0075] 6) The line center CATS system is deployed on the line control center cloud platform. New lines can generally be deployed using the cloud platform. The system architecture, shown in Figure 4, primarily includes the following cloud-based devices: a virtual CATS interface server (in a dual-host hot standby redundant configuration), a virtual communication front-end (in a dual-host hot standby redundant configuration), a virtual CATS application server (in a dual-host hot standby redundant configuration), a virtual CATS database server (in a dual-host hot standby redundant configuration), a virtual Ethernet network, and a virtual switch (in a dual-host hot standby redundant configuration). Desktop cloud-based devices include the following: a timetable editing workstation (desktop cloud terminal), a CATS dispatcher workstation (desktop cloud terminal), a CATS maintenance workstation (desktop cloud terminal), and a large-screen interface computer (desktop cloud terminal). External cloud devices include an interface switch and firewall (in a dual-host hot standby redundant configuration).

[0076] 7) The line center CATS system is deployed on traditional line physical hardware, which is generally maintained on existing lines. The system architecture, shown in Figure 5, primarily includes the following physical equipment: CATS interface server (dual hot standby redundant configuration), communication front-end processor (dual hot standby redundant configuration), CATS application server (dual hot standby redundant configuration), CATS database server (dual hot standby redundant configuration), timetable editing workstation, CATS dispatcher workstation, CATS maintenance workstation, and large-screen interface computer.

[0077] 8) The LATS system at line stations is deployed on the physical hardware of the line stations. The system architecture is shown in Figure 6, which mainly includes physical equipment: station server (dual-machine hot standby redundant configuration), station monitoring workstation, etc.

[0078] 9) The NATS system can be logically divided into an access platform, a data processing platform, and a human-computer interaction platform, namely the interface layer, platform layer, and application layer. The system functional architecture is shown in Figure 7.

[0079] 10) Interface layer: The NATS system is deployed on the cloud platform, using the NATS interface server to interface with the line CATS system (Line 1 ATS access, Line 2 ATS access... Line n ATS access), and to exchange information with the data sharing center through a virtual switch in the cloud.

[0080] 11) Interface requirements with the network center / line CATS system: The network center / line CATS system will process and upload the information of various disciplines integrated and interconnected by the network center / this line according to the access standards of NATS. In principle, the network center / line CATS system will upload all information to NATS.

[0081] 12) Interface requirements with the data sharing center: The data sharing center is set up on the cloud platform. NATS needs to upload all collected line CATS information data to the data sharing center, and upload the processed operation diagram data and driving index data in the format required by the data sharing center.

[0082] 13) The NATS system is deployed on an information-based cloud platform, and the hardware is provided by the cloud platform. Hardware requirements for the cloud platform must be put forward based on the scale of the NATS system.

[0083] 14) Platform layer

[0084] The platform layer is the business logic processing layer, including a real-time database, a historical database, a logic processing engine, and an intelligent analysis engine. It collects line-side ATS data, performs specific logic analysis and processing, and sends the results to the application layer.

[0085] 15) Application layer NATS provides the following functions

[0086] a) Full network map display function: The full network map display function displays all the locally planned rail transit lines in a window in the form of a vector diagram. The full network map is displayed according to the approximate direction of the actual line through a certain deformation process. The line color is the standard identification color of the local rail transit line, and the unopened lines are displayed in gray. Specific lines can be displayed or hidden or specific stations can be marked through settings. Trains are displayed as small dots on the full network map. The trains move on the line according to the actual running direction (up or down), and the train number is displayed next to the small dot. Specific trains can be marked as needed. NATS interfaces with other business systems to obtain the status of equipment such as ATS, ISCS, AFC, ACS, and PSCADA, and display more abundant equipment status or alarm prompts on the full network interface.

[0087] b) Station Map Display: This function primarily displays track, turnout, signal, static location information, and other required information (such as overhead line status) on the station map interface, allowing dispatchers to understand the real-time status of on-site signaling equipment. Static data displayed on the station map interface includes, but is not limited to, station name, signal name, track section / axle counting section name, turnout name, destination number, and line kilometer mark. Based on the equipment status data uploaded on the line, the information dynamically displayed on the station map interface includes but is not limited to: the clearing status, occupation status, locking status, removal status, and train control system report failure status of the track section / axle counting section; for lines using the communication-based mobile block signaling system (CBTC system), for relatively long track sections / axle counting sections, they can be divided into multiple virtual small sections according to display needs (one virtual small section corresponds to one train number window), and NATS can display the occupation or clearing status of each virtual small section according to the train position report information uploaded on the line; the positioning status, reverse position status, occupation status, locking status, squeezed switch status, and single locking status of the switch; the section removal status; the train control system report failure status; the status of each light position of the signal machine, the automatic passing mode status, the light off status, and the near locking status; the station control, remote control, and emergency station control of the centralized station control mode; the train stop status, train detention status, skip stop status, emergency closure status, and platform door status of the platform.

[0088] c) Train operation information display function: Train information includes but is not limited to: train identification number, train destination number, train early or late status, train detention status, train skipped stop status, train location information, train tracking mode, train driving mode, train door status, etc. The system provides the function of viewing the parking lot / depot entry and exit plan for the day, and supports the query of historical entry and exit plans.

[0089] d) Train Diagram Display: The system provides a graphical interface for displaying train diagrams. Based on the uploaded planned and actual train diagram data, NATS stores the data and displays it on the diagram interface, allowing dispatchers to review train operation status. The actual train diagram is refreshed in real time as the train moves. Diagram data is stored in a historical database, and historical diagrams can be viewed on the diagram interface. Diagrams support zooming. The diagram interface provides a line view switching menu, allowing users to switch between diagrams for different lines in the network.

[0090] e) Alarm event display function: Alarms occurring on the line can be viewed in real time in the system's alarm view. Alarms are divided into five levels according to their severity; alarms at level 0 (i.e., pop-up alarms) will be displayed directly in a dialog box on the workstation. The alarm window supports user filtering. Each alarm or event contains the following information: Time: the year, month, day, hour, minute, and second when the alarm occurred; Level: a numerical definition of the importance of the alarm or event; Line number: indicates which line the alarm originated from; Type: a numerical description of the type of alarm or event, including four types: operation command, signal status, train information, and system event.

[0091] f) Operation index analysis and display function: The system analyzes and calculates the operation indexes related to train operation based on the planned operation diagram and actual operation diagram data collected from the line, and then displays the operation indexes on the user interface. The main operation indexes include: the number of trains running on the train operation diagram, the number of delayed trains departing from the train operation diagram, the number of delayed trains arriving at the train operation diagram, the number of planned departure trains on the train operation diagram, the number of departure trains at each station on the train operation diagram, the number of online train sets on the train operation diagram, the fulfillment rate of the train operation diagram, the punctuality rate of the train operation diagram, the delay data of the train operation diagram (arrival and departure), the minimum departure interval of the train operation diagram, the maximum departure interval of the train operation diagram, and the up-line operation time of the train operation diagram. , train timetable downlink operation time, data on the number of passenger trains planned to be operated on the day according to the train timetable, data on the number of passenger trains actually operated on the day according to the train timetable, data on the number of delayed trains departing on the day according to the train timetable, data on the number of delayed trains arriving on the day according to the train timetable, data on the time of interrupted operation of the train timetable, data on the number of trains stopped on the day according to the train timetable, data on the number of trains dropped from the line on the day according to the train timetable, data on the number of trains turning back midway on the day according to the train timetable, data on the number of trains passing through the train timetable on the day, data on the number of temporary passenger trains added on the day according to the train timetable, data on the number of trains returning to empty on the day according to the train timetable, data on the number of rescue trains on the day according to the train timetable, data on the number of trains operating online on the day according to the train timetable.

[0092] g) Statistical Report Query: The statistical report function allows for querying and displaying commonly used statistical information and alarm event information, allowing dispatchers to view statistical information and analyze historical data. Queryable statistical reports include: train mileage reports, driver mileage reports, dispatch log reports, reserve vehicle reports, train maintenance status reports, operating commands, and alarm events.

[0093] h) Playback function: The playback software is used to play back the system's historical operating information (station signal equipment status changes and train operation information, etc.) to view historical operating conditions or conduct troubleshooting analysis.

[0094] The playback software directly reads the playback data files recorded by the application server software during runtime. Playback does not require any other software to run and will not affect other software operations. You can switch between channels to view playback information for different channels. The playback software allows users to control the playback speed, including normal, fast, fastest, slow, slowest, pause, start, step, and second-by-second. You can also quickly locate the desired playback time by dragging the time scroll bar.

[0095] Specific embodiments

[0096] As shown in Figure 3, the NATS system cloud platform architecture includes an in-cloud device interface server, application server, database server, virtual switch, desktop cloud terminal device monitoring workstation, large-screen interface computer, external-cloud device interface switch, and firewall. The NATS interface server interfaces with the line CATS system, the data sharing center, and the line network command center. The NATS application server analyzes and processes NATS data, submitting the analyzed data for display on the workstation interface. The NATS database server stores NATS data. The virtual switch allows for information exchange between in-cloud NATS and external-cloud interface switches. The NATS monitoring workstation displays system status, and the large-screen interface computer interfaces with the line network NATS display screen. The interface switch allows information exchange between the backbone network and the in-cloud NATS system. The firewall provides network information security.

[0097] The interfaces of the NATS system include the interface with the line CATS system, the interface with the data sharing center and the line network center interface.

[0098] Step 1: Information exchange with the Line CATS system is established through the interface server. Requirements for the Line CATS interface are: Two redundant 100M Ethernet interfaces. The IP addresses of hosts connecting the Line CATS system to NATS will be in the NATS address segment and will be uniformly assigned by NATS. Data exchange between NATS and the Line CATS system will be conducted over a redundant TCP / IP-based network. Information exchange between NATS and the Line CATS system will utilize periodic and event-triggered communication. The Line CATS system processes and uploads information from various disciplines within the integrated line according to NATS's access standards. In principle, the Line CATS system uploads all information to NATS.

[0099] Step 2: The interface system interface with the line data sharing center (DSC) exchanges information via the interface server. Data exchange between NATS and the DSC is accomplished via a redundant TCP / IP-based network or FTP. Information exchange between NATS and the DSC utilizes periodic and event-triggered communication. NATS and the DSC provide the relevant interface functions as outlined in the Interface Function Requirements List. NATS is required to upload all collected line ATS information to the DSC, including processed diagram data and driving indicator data in the format specified by the DSC.

[0100] Step 3: Deploy the NATS system on an information-based cloud platform, with the cloud platform providing the hardware. Hardware requirements for the cloud platform will need to be determined based on the scale of the NATS system.

[0101] Step 4: Information is exchanged with the line network center interface through the backbone network, and the line-level CATS information collected by the NATS system is uploaded to the line network center.

[0102] As shown in Figure 4, the cloud platform architecture for the newly built line CATS system includes an in-cloud interface server, application server, database server, communication front-end processor (FEP), virtual switch, cloud desktop terminal device, schedule editing workstation, dispatcher workstation, maintenance workstation, large-screen interface computer, external device interface switch, and firewall. The CATS interface server interfaces with the line network NATS system in the cloud. The CATS application server analyzes and processes CATS data, submitting the analyzed data to the workstation interface for display. The CATS database server stores CATS data. The virtual switch facilitates information exchange between in-cloud NATS and external interface switches. The FEP is used to exchange information with external departments (such as PIS, PA, ISCS, and clock). The schedule editing workstation is used to edit operation diagrams. The CATS dispatcher workstation is used to issue traffic monitoring commands. The CATS maintenance workstation is used for historical record playback and system parameter configuration. The large-screen interface computer is used to interface with the line center's large screen. The interface switch facilitates information exchange between the backbone network and the in-cloud CATS system. The firewall provides network information security.

[0103] As shown in Figure 5, the physical hardware of the existing line CATS system includes an interface server, application server, database server, timetable editing workstation, communication front-end processor, dispatcher workstation, maintenance workstation, and large-screen interface computer. The CATS interface server interfaces with the line network NATS system through the backbone network. The CATS application server analyzes and processes CATS data, submitting the analyzed data to the workstation interface for display. The CATS database server stores CATS data, the timetable editing workstation is used to edit the operation diagram, the communication front-end processor is used to exchange information with external professional departments (such as PIS, PA, ISCS, clock, etc.), the CATS dispatcher workstation is used to issue traffic monitoring commands, the CATS maintenance workstation is used for historical record playback and system parameter configuration, and the large-screen interface computer is used to interface with the line center large-screen.

[0104] As shown in Figure 6, the LATS system physical hardware architecture includes a station server and a monitoring workstation. The station server is used to exchange information with the CATS application server, and the station monitoring workstation is used to issue commands related to station operation monitoring.

[0105] As shown in FIG7 , the system includes an interface layer, a platform layer, and an application layer.

[0106] Step 1: The interface layer includes the access to the ATS system of each line in the city. The ATS system aggregates the line driving operation information to the platform layer for logical analysis and then transmits it to the line network dispatching and command system for related applications.

[0107] Step 2: The system first transmits the station diagram information, operation diagram information, interface status information, alarm events, train operation information, playback information and other data of each line ATS system to the platform layer through the interface layer. The platform layer receives the data of the line ATS system, and performs logical analysis through the real-time database, historical database, logic processing engine, and intelligent analysis engine. The application layer reads the analysis results of the platform layer, and performs full network map display, station diagram display, operation diagram display, interface status monitoring, alarm event display, train operation information, statistical report query, playback function, operation indicator analysis display, and sends instructions from the line network command center to the line.

[0108] Step 3: The platform layer is the business logic processing layer, which includes a real-time database, a historical database, a logic processing engine, and an intelligent analysis engine. It collects line-side ATS data and performs specific logic analysis and processing.

[0109] Step 4: The application layer collects line data, uploads it to the network command center and data sharing center, displays the entire network map, station map, and operation diagram, issues instructions from the network command center to the lines, monitors interface status, displays alarm events, provides train operation information, provides statistical report query and playback functions, and analyzes and displays operational indicators. The application layer reads the platform layer data to monitor and control the lines.

[0110] The foregoing description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any person skilled in the art will readily conceive of various equivalent modifications or substitutions within the technical scope disclosed herein, and such modifications or substitutions are intended to be encompassed within the scope of protection of the present invention. Therefore, the scope of protection of the present invention shall be subject to the scope of protection of the claims.

Claims

1. A cloud platform-based urban rail transit network-level train monitoring system, characterized in that: The network-level train monitoring system NATS is set up in the network center cloud platform to collect line ATS data for analysis and provide network-level operation management functions; at the same time, the NATS has train command, operation indicator analysis, fully automatic mapping, network and line coordinated command, transportation organization and auxiliary decision-making functions.

2. According to the cloud platform-based urban rail transit line network-level train monitoring system of claim 1, it is characterized in that: The NATS adopts a cloud platform design and designs a virtual data center VDC and a virtual private cloud VPC. The cloud platform transforms physical resources into virtual pools through VDC, flexibly allocates data centers through different logical isolation methods, and divides the resource pool within the VDC into VPCs to achieve unified deployment of system resources.

3. The urban rail transit line network-level train monitoring system based on a cloud platform according to claim 2 is characterized in that: The virtual data center VDC is divided according to professional or city lines.

4. The urban rail transit line network-level train monitoring system based on a cloud platform according to claim 1 is characterized in that: The NATS is designed to have a full-line data center to carry the computing and storage resources required by the center-level hardware of each professional system, and the data sharing center capacity meets the subsequent line expansion needs.

5. The urban rail transit line network-level train monitoring system based on a cloud platform according to claim 1 is characterized in that: The NATS is provided with a workstation which uses a desktop cloud. All software runs on a cloud desktop server and displays the results on the desktop cloud workstation. The desktop cloud is divided into a business network, a storage network and a management network as required, and logical isolation is used between networks.

6. The urban rail transit line network-level train monitoring system based on a cloud platform according to claim 1 is characterized in that: The NATS access cloud platform network settings meet the following requirements: NATS is hosted in the safety production network; NATS networks are mutually redundant and logically isolated, and the bandwidth of a single network is no less than 100M; NATS network adopts a ring network mode, and single point failure of the network does not affect the operation of the system; The maximum end-to-end network delay is less than 50ms, and the maximum switch switching delay is less than 50ms.

7. The urban rail transit line network-level train monitoring system based on a cloud platform according to claim 1 is characterized in that: The devices deployed by NATS in the cloud platform include: Virtual NATS interface server, virtual NATS application server, virtual NATS database server, Virtual switches and virtual Ethernet, including virtual NATS interface server, virtual NATS application server, virtual NATS database server, and virtual switch, are all configured with dual-machine hot standby redundancy.

8. The cloud platform-based urban rail transit line network-level train monitoring system according to claim 1 is characterized in that: The NATS is logically divided into an interface layer, a platform layer and an application layer.

9. The cloud platform-based urban rail transit line network-level train monitoring system according to claim 8, characterized in that: The interface layer comprises: Interface with the network center / line CATS system to process and upload the information of various disciplines of the network center or the integrated interconnection of the line according to the access standard of NATS; The interface with the data sharing center is used to upload all line CATS information data collected by NATS to the data sharing center, and upload the processed operation diagram data and driving index data in the format required by the data sharing center.

10. The urban rail transit line network-level train monitoring system based on a cloud platform according to claim 8, characterized in that: The platform layer is a business logic processing layer, including a real-time database, a historical database, a logic processing engine, and an intelligent analysis engine. It is used to collect the line-side ATS data, perform specific logic analysis and processing, and send the results to the application layer.

11. The urban rail transit line network-level train monitoring system based on a cloud platform according to claim 8, characterized in that: The application layer includes: The whole network map display module is used to display all the local rail transit lines in one window in the form of vector diagrams; The station map display module is used to display the tracks, switches, signals, static position information and other information that needs to be displayed on the station map interface, so that the dispatching personnel can understand the real-time status of the signal equipment on site; The train operation information display module is used to display the train operation information, wherein the train operation information includes the train identification number, the train destination number, the train early or late status, the train detention status, the train skipping status, the train location information, the train tracking mode, the train driving mode, and the train door status; The operation diagram display module is used to display the operation diagram in a graphical interface. According to the planned operation diagram and actual operation diagram data uploaded by the line, NATS stores the data and displays it on the operation diagram interface for dispatchers to view the operation status of the train. The actual operation diagram can be refreshed and displayed in real time as the train runs; The alarm event display module is used to view the alarms occurring on the line in real time in the system's alarm view; The operation index analysis and display module is used to analyze and calculate the operation indexes related to driving according to the planned operation diagram and actual operation diagram data collected from the line, and then display the operation indexes on the user interface; The statistical report query module is used to query and display commonly used statistical information and alarm event information, so that dispatchers can view statistical information and analyze historical data; The playback module is used to playback the historical operation information of the system to view the historical operation status or conduct troubleshooting analysis.

12. The urban rail transit line network-level train monitoring system based on a cloud platform according to claim 11, characterized in that: The playback module directly reads the playback data file recorded when the application server software is running, can switch lines to view playback information of different lines, and allows the user to control the playback speed and quickly locate the time required for playback by dragging the time scroll bar.

Images