Railway ATS system data automatic generation method

Abstract

The application discloses a kind of track ATS system data automatic generation method, according to project demand, define project overall relevant data, draw line CAD edition monorail chart, compile line interlocking table, generate ATS system partial data, according to approach table generation basic approach information table, according to the entity station defined in monorail chart, virtual station, line uplink and downlink and data generation rule generation platform data table, simultaneously generate secondary input data, according to existing information generation line relevant data, other data needed secondary input generates default value or null value, configuration personnel according to actual project operation needs, configure track type, destination code data, manually secondary input data, generate ATS system each software relevant line data.

Description

Technical Field

[0001] This invention belongs to the field of automation technology, specifically relating to a data generation technology. Background Technology

[0002] Currently, the data configuration of the urban rail transit ATS system relies on automated tools. Although this achieves the automatic generation of project data, the amount of configuration data in the early stages is large, and the data configuration entry is done manually, requiring manual modification of the database file.

[0003] On the one hand, not only is the data configuration workload large, but the logic between various data is also complex, frequently leading to data configuration errors. On the other hand, as the project design progresses, the relevant data is constantly updated, requiring manual comparison and system data revision, which increases the complexity of comparison, verification, and modification, making it impossible to guarantee the accuracy and completeness of the data.

[0004] When data configuration errors occur, data configuration personnel often find it difficult to identify the problem, resulting in a longer time to resolve the issue, which in turn affects the testing, debugging, and project implementation schedules. Summary of the Invention

[0005] In order to solve the problems existing in the prior art, the present invention proposes an automatic data generation method for an orbital ATS system. To achieve the above objective, the present invention adopts the following technical solution.

[0006] Based on project requirements, define overall project-related data, draw the CAD version of the monorail map, compile interlocking tables, generate partial data for the ATS system, generate a basic route information table based on the route table, generate a platform data table based on the physical stations, virtual stations, line up / down routes, and data generation rules defined in the monorail map, and generate secondary input data. Generate line-related data based on existing information, and generate default values ​​or null values ​​for other data requiring secondary input. Configuration personnel configure track type and destination code data according to actual project operation needs, manually input secondary data, and generate relevant line data for each software in the ATS system.

[0007] Furthermore, the overall project-related data includes: data that is related to the overall implementation of the project but cannot be marked on the system monorail diagram. This data cannot be directly obtained from the drawn CAD monorail diagram of the line, such as the starting index of the trains running on the line, the train group number, the interlocking number defined by the line, the ZC number, the discrete relay index, etc.

[0008] Furthermore, the CAD monorail diagram of the line includes: a monorail diagram of the line drawn according to the project line conditions and signal system design principles, and a signal system designed in conjunction with the line conditions, mainly involving the layout of signals, transponders, beacons, and axle counters, the division of logical sections, turnouts, and switch points, the division of line mileage, and the division of segment data, etc.

[0009] Furthermore, the line interlocking table includes: data related to routes compiled according to the line stepping and interlocking system design principles, which is used by the ATS system to generate route arrangement, inspection and triggering data.

[0010] Furthermore, the manual secondary input data includes: the route trigger track has generated a track name and track number in the secondary input table. The configuration personnel determine whether the tracks already included in the line need to be configured as route trigger tracks based on the triggering status of each route, that is, in the track type in the secondary input data.

[0011] Furthermore, the data for each software line includes: combined with the already generated ATS partial data and secondary input data, the runtime data generated for each software according to the data generation rules of each software, the database format used by each software, and the field definitions used in the database. This data is generated according to the database format and data table field types used by the software, and does not require manual modification and can be directly deployed and run with the software.

[0012] Furthermore, the data for each software line includes: dispatcher workstation HMI data, application server data, local operator workstation LOW data, central / local interface workstation FEP software data, and simulator TS data, supporting SQLite, Oracle, and Access database formats.

[0013] The beneficial effects of this invention are: it can automatically generate the data of each software in the ATS system based on the project parameter definition, the line CAD single-track diagram and the interlocking table, while meeting the needs of continuous updating of project files and automatic generation of related data, improving the data configuration efficiency, avoiding the error defects of configuration data, and quickly, accurately and automatically generating the line data required by each software in the ATS system. Attached Figure Description

[0014] Figure 1 This is a flowchart of the ATS system data generation process. Figure 2 This is a diagram of the ATS system data files. Detailed Implementation

[0015] The technical solution of the present invention will be described in detail below with reference to the accompanying drawings.

[0016] The system data generation process is as follows: Figure 1As shown, the system uses a project parameter definition table, a CAD monorail diagram, and an interlocking table as databases. Based on the different attributes of each data point in each software of the ATS system, the system filters out the data required by each software, generates a complete ATS data set and a manual secondary input table. Users manually input secondary input data into the secondary input table according to the line conditions and operational requirements. The secondary input table and the ATS system partial data table are then integrated to output the operational data required by each software of the ATS system.

[0017] The project parameter definition table is used to define project-level data and elements that cannot be defined in CAD monorail drawings. It mainly includes: indexes of elements such as track, turnout, signal, axle counter, station, platform, emergency stop button, discrete relay, turnaround button, route, control area, protection section, flood gate, etc., as well as train index, train group number, ZC number, interlocking area number, segment index, etc.

[0018] The CAD monorail drawing is used to define trackside elements such as turnouts, platforms, signals, axle counters, transponders, gradients, speed limits, and curves. Different types of trackside elements are placed on different layers for easy identification. The numbers of trackside elements are also assigned to their corresponding layers for easy identification. A specific identification range is set based on the coordinates of a trackside element in the CAD drawing, and the corresponding element number is searched from its assigned number layer to identify each trackside element. The kilometer marker layer is searched from the horizontal coordinate of the trackside element to obtain and save the kilometer markers for the corresponding line. The C# language is used to interface with the various software databases of the ATS system to filter out the required data, including the trackside element's number, location, and topological relationships.

[0019] The interlocking table is used to define data such as track route, protected section, track, turnout, signal, floodgate, platform screen door, discrete relay, side protection, and turnaround button.

[0020] The above data is based on the top-level design of the specific project and the input data provided by the external interlocking system, and is used to generate ATS system data.

[0021] Based on project-level design data and external interlocking system design data, partial data for the ATS system and manually input secondary data are generated. According to the kilometer markers at the start and end points of the virtual section of the line, trackside elements are searched, the topological relationships of trackside elements on the virtual section are established, the logical relationships corresponding to the trackside elements are generated, and the basic information and topological relationships of the line signal elements required by each software component of the ATS system are generated. Specific information is as follows:

[0022] 1) Based on the CAD monorail drawing, identify the basic information of elements from the layers, such as the name and location information of tracks, switches, signals, platforms, stations, and segments. Based on the project parameter definition table, match the index information of each signal element.

[0023] 2) Based on the elements such as tracks and turnouts drawn in the CAD monorail drawing, identify the topological relationships of the elements from the layers, generate the preceding and following track information of the logical track association, and generate the preceding, second preceding, following, and second following track information of the turnout.

[0024] 3) Based on the interlocking table determined by the interlocking system, generate route-related data required by the ATS system, such as route data, protected area data, route elements, and proximity areas.

[0025] Following the above logic, all the data required by each software component of the ATS system, as well as the data requiring manual secondary data, are generated. Data configuration personnel input secondary data into the manual secondary input table based on route maps, route operation requirements, and design communication documents.

[0026] The following inputs require a second input:

[0027] 1) Destination code data associated with platforms, destination code data associated between stations, and track type data.

[0028] 2) Route trigger data, proximity area data, route protection zone trigger data, and protection zone proximity data, etc.

[0029] 3) Equipment information, fault codes and information, power supply zone information, etc.

[0030] Based on the manual input data from the configuration personnel, combined with the generated ATS partial data and CAD monorail diagram, runtime data is generated for various software running on the ATS system according to the data generation rules of each software, the database format used by each software, and the field definitions used in the database. This data is generated entirely according to the database format and data table field types used by the software during runtime. After generation, it can be directly deployed and run with the software without manual modification.

[0031] ATS system data files such as Figure 2 As shown, the system generates data for each software component of the ATS system, including dispatcher workstation HMI data, application server data, local operator workstation LOW data, central / local interface workstation FEP software data, and simulator TS data. The output data files support SQLite, Oracle, Access, and other database formats to meet the database requirements for the software operation.

[0032] The above are embodiments of the present invention and do not limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention are included within the protection scope of the present invention.

Claims

1. A method for automatically generating data for a rail ATS system, the method comprising: The application relates to a method for generating ATS system data, which comprises the following steps: according to project requirements, defining project overall related data, drawing line CAD single-track diagram, compiling line interlocking table, generating ATS system part data, generating basic route information table according to route table, generating platform data table according to the entity station, virtual station, line up and down and data generation rules in the single-track diagram, simultaneously generating secondary input data, generating line related data according to existing information, generating default value or null value of other secondary input data, configuring track type and destination code data according to actual project operation needs of a configuration personnel, manually inputting data, and generating ATS system software related line data; the project overall related data comprises data related to project overall implementation, which cannot be marked in the system single-track diagram and cannot be directly obtained according to the drawn line CAD single-track diagram; the line interlocking table comprises route related data compiled according to line data and interlocking system design principles, which is used for generating route arrangement, checking and triggering data of the ATS system; the software line data comprises operation data generated for each software according to software data generation rules, database formats used by each software and database field definitions, which is generated according to the database format and data table field type used by the software, does not need manual modification and can be directly deployed and run with the software. The line CAD single-track diagram comprises a line single-track diagram drawn according to project line conditions and signal system design principles, and a signal system designed in combination with the line conditions.

2. The method of claim 1, wherein, The manually inputted secondary data comprises route triggering track, track name and track number of which have been generated in the secondary input table, and track type in the secondary input data is configured by a configuration personnel according to the triggering condition of each route to determine whether the track contained in the line needs to be configured as the route triggering track.

3. The method of claim 1, wherein, The software line data further comprises dispatcher workstation HMI data, application server data, local operator workstation LOW data, central / local interface working FEP software data and simulator TS data, and supports Sqlite, oracle and access format databases.

4. The method of claim 1, wherein, ​

Images