Method and system for checking shunting route data

Abstract

The application provides a method and system for checking shunting route data, the method comprising: reading a target configuration file, the target configuration file being a configuration file of shunting route data; and performing correctness checking on the shunting route data in the target configuration file. The system executes the method. The application reads a target configuration file, identifies the shunting route data in the target configuration file, and then performs relevant correctness checking on the identified shunting route data, thereby replacing the traditional manual checking of shunting route data, which is inefficient and difficult to effectively check all data errors, and the checking process is prone to manual errors.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of rail transit technology, and in particular to a method and system for checking shunting route data. BACKGROUND

[0002] The CBTC2.0 system is an interconnected train automatic control system for commanding and controlling train operation and ensuring train safety. The CBTC2.0 system includes an ATP (Automatic Train Protection), an ATO (Automatic Train Operation), an ATS (Automatic Train Supervision), a ZC (Zone Controller), a CI (Computer Interlocking), and a simulation test environment.

[0003] A vehicle depot is one of the important units of a railway system, mainly responsible for the operation, preparation, and maintenance of train vehicles (excluding the locomotive). The vehicle depot is also a place for the operation management, parking, maintenance, and repair of vehicles in a city rail transit system (subway and urban light rail).

[0004] The station yard line of a subway vehicle depot is complex. In order to complete various complex shunting operations, the interlocking system often needs to support hundreds of short shunting routes and long shunting routes. A shunting route is a path that a shunting train passes through in a station, including a short shunting route and a long shunting route. A short shunting route refers to a single unit shunting route from a starting shunting signal to a next blocking signal. A long shunting route is a combined shunting route of a short shunting route, which is composed of two or more short shunting routes, and the number of long shunting routes is larger than that of short shunting routes.

[0005] The interlocking system can command the completion of complex shunting operations, provided that the interlocking logic software stores the various shunting route data supported by the vehicle depot station yard in advance by reading the interlocking data configuration file, including short shunting routes and long shunting routes.

[0006] The data of short shunting routes and long shunting routes are configured in an interlocking configuration file, whether the interlocking data configuration file is configured manually or generated by relevant tool software. Due to the complexity of the depot station and the bulk of the shunting route data, certain data errors are prone to occur, resulting in failure of the interlocking system in guiding shunting operation by arranging routes. Once the shunting route data in the interlocking data configuration file is incorrect, if the traditional method of manually checking the shunting route data is adopted, it is very difficult to check due to the huge amount of data, which is not only low in efficiency, but also difficult to effectively check all data errors, and the process of checking is prone to manual errors.

[0007] Therefore, how to quickly check the correctness of a large amount of shunting route data and effectively exclude potential data errors is very important. SUMMARY

[0008] The shunting route data checking method and system provided by the application are used to solve the problem of low efficiency and difficulty in effectively checking all data errors and the process of checking being prone to manual errors in the prior art by manually checking shunting route data.

[0009] The shunting route data checking method provided by the application comprises the following steps.

[0010] Reading a target configuration file, wherein the target configuration file is a configuration file of shunting route data;

[0011] Checking the correctness of the shunting route data in the target configuration file.

[0012] According to the shunting route data checking method provided by the application, the step of checking the correctness of the shunting route data in the target configuration file comprises the following steps.

[0013] Checking the correctness of a first parameter in a first configuration file, a second configuration file and a third configuration file, wherein the target configuration file comprises the first configuration file, the second configuration file and the third configuration file, the first parameter comprises a first shunting route quantity and a second shunting route quantity, the first shunting route quantity is the sum of a long shunting route quantity and a short shunting route quantity, the second shunting route quantity is the long shunting route quantity, a short shunting route comprises one starting signal machine and one terminal signal machine, and a long shunting route comprises a plurality of short shunting routes;

[0014] Checking the correctness of a second parameter in the first configuration file and the second configuration file, wherein the second parameter comprises a shunting route identifier and the short shunting route quantity;

[0015] The correctness of the third parameter in the second configuration file is checked. The third parameter includes the start button identifier and the end button identifier of the long shunting route.

[0016] Check whether the short shunting route included in the long shunting route in the first configuration file is correct.

[0017] According to a shunting route data inspection method provided by the present invention, the correctness check of the second parameter in the first configuration file and the second configuration file includes:

[0018] Check if the long shunting route code in the long shunting route interlocking table in the first configuration file is correct;

[0019] Check whether the long shunting route code in the long shunting route button table in the second configuration file is correct;

[0020] Check whether the short shunting route codes included in the long shunting routes in the first configuration file exist in the shunting route button table in the second configuration file;

[0021] Check whether the short shunting route code included in the long shunting route interlocking table exists in the shunting route interlocking table;

[0022] Check if the long shunting route code in the long shunting route interlocking table exists in the long shunting route button table;

[0023] Check whether the long shunting route code in the long shunting route button table exists in the long shunting route interlocking table;

[0024] Check whether the Hamming code of the long shunting route code in the long shunting route interlocking table is correct;

[0025] Check if the Hamming code of the long shunting car route code in the long shunting car route button table is correct;

[0026] The shunting route identifier includes a long shunting route identifier and a short shunting route identifier. The long shunting route identifier includes a long shunting route code and a Hamming code of the long shunting route code. The short shunting route identifier includes a short shunting route code and a Hamming code of the short shunting route code.

[0027] According to a shunting route data inspection method provided by the present invention, the correctness check of the third parameter in the second configuration file, wherein the third parameter includes a start button identifier and a terminal button identifier, includes:

[0028] Check whether the start button code of the long shunting route in the long shunting route button table is the same as the start button code of the first short shunting route included in the long shunting route;

[0029] checking whether the terminal end button code of the long shunting route in the long shunting route button table is same as the terminal end button code of the last short shunting route included in the long shunting route.

[0030] According to the shunting route data checking method provided by the application, the correctness of the short shunting routes included in the long shunting route in the first configuration file is checked, and the method comprises the following steps of:

[0031] obtaining the short shunting route codes of the short shunting routes included in the long shunting route in the first configuration file;

[0032] determining the short shunting routes corresponding to the short shunting route codes;

[0033] checking whether the departure section code of the first short shunting route and the approach section code of the second short shunting route are same, wherein the initial end signal of the second short shunting route is same as the terminal end signal of the first short shunting route.

[0034] According to the shunting route data checking method provided by the application, after the correctness of the shunting route data in the target configuration file is checked, the method further comprises the following steps of:

[0035] storing the correctness checking result.

[0036] The application further provides a shunting route data checking system, which comprises an obtaining module and a checking module.

[0037] The obtaining module is used for reading a target configuration file, wherein the target configuration file is a configuration file of shunting route data.

[0038] The checking module is used for checking the correctness of the shunting route data in the target configuration file.

[0039] The application further provides an electronic device, which comprises a processor and a memory storing a computer program, and the processor implements the shunting route data checking method according to any one of the above-mentioned methods when executing the program.

[0040] The application further provides a non-transient computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the shunting route data checking method according to any one of the above-mentioned methods.

[0041] The application further provides a computer program product, which comprises a computer program, and the computer program is executed by a processor to implement the shunting route data checking method according to any one of the above-mentioned methods.

[0042] The application provides a shunting route data checking method and system, which comprises the following steps: reading a target configuration file, identifying shunting route data in the target configuration file, and checking the identified shunting route data for correctness. BRIEF DESCRIPTION OF DRAWINGS

[0043] In order to more clearly illustrate the technical solutions in the application or prior art, the following will briefly introduce the drawings needed to be used in the embodiments or prior art description. Obviously, the drawings in the following description are some embodiments of the application, and other drawings can be obtained by those skilled in the art without any creative effort on the basis of these drawings.

[0044] Figure 1 Fig. 1 is a flowchart of the shunting route data checking method provided by the application;

[0045] Figure 2 Fig. 2 is an interface diagram of the shunting route automatic checking tool provided by the application;

[0046] Figure 3 Fig. 3 is a diagram of the maximum shunting route quantity parameter and the maximum long shunting route quantity parameter in the lskzmac1.h file provided by the application;

[0047] Figure 4 Fig. 4 is a diagram of the shunting route interlocking table in the ShuntTab.c file provided by the application;

[0048] Figure 5 Fig. 5 is a diagram of the long shunting route interlocking table in the ShuntTab.c file provided by the application;

[0049] Figure 6 Fig. 6 is a diagram of the shunting route button table in the lsfdata3.c file provided by the application;

[0050] Figure 7 Fig. 7 is a diagram of the shunting route button table in the lsfdata3.c file provided by the application;

[0051] Figure 8 Fig. 8 is a structural diagram of the shunting route data checking system provided by the application;

[0052] Figure 9 Fig. 9 is a physical structure diagram of the electronic device provided by the application. DETAILED DESCRIPTION

[0053] In order to make the objects, technical solutions and advantages of the present application clearer, the technical solutions in the present application will be described clearly and completely below in conjunction with the drawings in the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the protection scope of the present application.

[0054] Figure 1 is a flowchart of a method for checking shunting route data provided by the present application, as shown in Figure 1 , the method comprises the following steps.

[0055] Step 110, reading a target configuration file, wherein the target configuration file is a configuration file of shunting route data.

[0056] Step 120, performing correctness checking on the shunting route data in the target configuration file.

[0057] It should be noted that the execution subject of the above method can be a computer device or an application program installed on the computer device. The shunting route data checking method provided by the present application will be described in detail below with the execution subject of the above method being an application program.

[0058] Optionally, the target configuration file can be specifically a configuration file of shunting route data, for example, an interlocking data configuration file configured in advance or an interlocking data configuration file stored in the local in advance.

[0059] The application program identifies the shunting route data in the target configuration file by reading the target configuration file. The shunting route data can specifically include long shunting route data and short shunting route data. The reading can be specifically importing the target configuration file into the application program.

[0060] Optionally, after reading the target configuration file and identifying the shunting route data therein, the application program can store the identified shunting route data.

[0061] The application program can be specifically developed by using a C# programming language to obtain a shunting route automatic checking tool. The target configuration file is read by the shunting route automatic checking tool to identify and store the short shunting route data and the long shunting route data. Then, the correctness checking of the shunting route data is realized through corresponding algorithm logic.

[0062] The application provides a shunting route data checking method, which comprises the following steps: reading a target configuration file, identifying shunting route data in the target configuration file, and performing relevant correctness checking on the identified shunting route data.

[0063] Further, in one embodiment, the correctness checking on the shunting route data in the target configuration file can specifically include:

[0064] correctness checking on first parameters in first, second and third configuration files, the target configuration file comprising the first, second and third configuration files, the first parameters comprising a first shunting route quantity and a second shunting route quantity, the first shunting route quantity being a sum of a long shunting route quantity and a short shunting route quantity, the second shunting route quantity being the long shunting route quantity, a short shunting route comprising one starting signal machine and one terminal signal machine, and a long shunting route comprising a plurality of short shunting routes;

[0065] correctness checking on second parameters in the first and second configuration files, the second parameters comprising a shunting route identifier and the short shunting route quantity;

[0066] correctness checking on third parameters in the second configuration file, the third parameters comprising a starting button identifier and a terminal button identifier of a long shunting route;

[0067] checking whether the long shunting route in the first configuration file correctly comprises the short shunting routes.

[0068] Optionally, the target configuration file can specifically comprise three configuration files, namely a first configuration file, a second configuration file and a third configuration file, wherein the first configuration file can specifically comprise a shunting route interlocking table, the shunting route interlocking table can specifically comprise a long shunting route interlocking table, and the long shunting route interlocking table stores long shunting route data (the long shunting route data is stored in the long shunting route interlocking table, a long shunting route code is found from a data structure of the long shunting route data, and a short shunting route quantity and corresponding short shunting route codes included in a long shunting route corresponding to the long shunting route code are found) and short shunting route data (short shunting route codes, approach section codes and departure section codes of short shunting routes are obtained from a data structure of the short shunting route data, and the quantity of the short shunting routes, the short shunting route codes, the approach section codes and the departure section codes of the short shunting routes are counted).

[0069] The second configuration file can specifically include a shunting route button table, which can specifically include a long shunting route button table, and the long shunting route button table can store long shunting route button data (each row of data in the long shunting route button table represents one piece of long shunting route button data, from which the start button code of the long shunting route, the end button code of the long shunting route, and the long shunting route code are obtained, and the number of long shunting routes in the table is counted) and short shunting route button data.

[0070] The third configuration file can have two shunting route numbers, specifically a first shunting route number and a second shunting route number. The first shunting route number can be specifically the sum of the number of long shunting routes and the number of short shunting routes, and the second shunting route number can be specifically the number of long shunting routes. The number of long shunting routes can be specifically the number of long shunting routes, and the number of short shunting routes can be specifically the number of short shunting routes. The long shunting route can be specifically composed of multiple short shunting routes, and the short shunting route can be specifically a shunting route including one start signal and one end signal.

[0071] The first parameter can specifically include two shunting route numbers, specifically the first shunting route number and the second shunting route number.

[0072] The application program checks the correctness of the first shunting route number and the second shunting route number in the three configuration files (i.e., the first configuration file, the second configuration file, and the third configuration file). Specifically, the correctness of the first shunting route number in the three configuration files and the correctness of the second shunting route number in the three configuration files are checked. Specifically, the first shunting route number in the shunting route interlocking table in the first configuration file, the first shunting route number in the shunting route button table in the second configuration file, and the first shunting route number in the third configuration file are checked. If they are equal, it is correct; if they are not equal, it is incorrect, and the result is output to the target log file to report an error.

[0073] The second shunting route number in the long shunting route interlocking table, the second shunting route number in the long shunting route button table, and the second long shunting route number in the third configuration file are checked. If they are equal, it is correct; if they are not equal, it is incorrect, and the result is output to the target log file to report an error.

[0074] The application program checks the correctness of the second parameter in the first configuration file and the second configuration file. The second parameter can specifically include a shunting route identifier and a short shunting route number. The shunting route identifier is unique and can be specifically used to distinguish different shunting routes.

[0075] The application program checks whether the number of short shunting routes in the long shunting route interlocking table is correct. Specifically, it is checked whether the number of short shunting route values in the long shunting route interlocking table is equal to the total number of short shunting route codes. If they are equal, it is correct, otherwise it is incorrect, and an error is output to the target log file.

[0076] The application program checks the correctness of a third parameter in the second configuration file. The third parameter can specifically include the start button identifier of the long shunting route and the end button identifier of the long shunting route. The start button identifier can specifically identify the start signal of the first short shunting route included in the long shunting route. The end button identifier can specifically identify the end signal of the last short shunting route included in the long shunting route. Both the start button identifier and the end button identifier are unique.

[0077] The application program also needs to check whether the short shunting routes included in the long shunting route in the first configuration file are correct.

[0078] Further, in one embodiment, the correctness checking of the second parameter in the first configuration file and the second configuration file can specifically include:

[0079] checking whether the long shunting route code in the long shunting route interlocking table in the first configuration file is correct;

[0080] checking whether the long shunting route code in the long shunting route button table in the second configuration file is correct;

[0081] checking whether the short shunting route code included in the long shunting route in the first configuration file exists in the shunting route button table in the second configuration file;

[0082] checking whether the short shunting route code included in the long shunting route in the long shunting route interlocking table exists in the shunting route interlocking table;

[0083] checking whether the long shunting route code in the long shunting route interlocking table exists in the long shunting route button table;

[0084] checking whether the long shunting route code in the long shunting route button table exists in the long shunting route interlocking table;

[0085] checking whether the Hamming code of the long shunting route code in the long shunting route interlocking table is correct;

[0086] checking whether the Hamming code of the long shunting route code in the long shunting route button table is correct;

[0087] The long shunting route identification includes a long shunting route code and a Hamming code of the long shunting route code, and the short shunting route identification includes a short shunting route code and a Hamming code of the short shunting route code.

[0088] Optionally, it is checked whether the long shunting route code in the long shunting route interlocking table in the first configuration file is correct.

[0089] The application program checks whether the long shunting route code in the long shunting route button table in the second configuration file is correct, specifically, the route code in the long shunting route button table is operated with 0x0000f000, and if the result is equal to 0x00008000 or 0x00009000, the long shunting route code is correct, otherwise, it is incorrect, and an error is output to the log.

[0090] The application program checks whether the long shunting route code in the long shunting route button table in the second configuration file is correct, specifically, the long shunting route code in the long shunting route button table is operated with 0x0000f000, and if the result is equal to 0x00008000 or 0x00009000, the long shunting route code is correct, otherwise, it is incorrect, and an error is output to the log.

[0091] The application program checks whether the short shunting route code included in the long shunting route in the first configuration file exists in the shunting route button table in the second configuration file, specifically, the short shunting route code included in the long shunting route in the long shunting route interlocking table is compared with each short shunting route code in the shunting route button table, if it exists, it is correct, if it does not exist, it is incorrect, and an error is output to the log file.

[0092] The application program checks whether the short shunting route code included in the long shunting route in the long shunting route interlocking table exists in the shunting route interlocking table, specifically, the short shunting route code included in the long shunting route in the long shunting route interlocking table is compared with each short shunting route code in the shunting route interlocking table, if it exists, it is correct, if it does not exist, it is incorrect, and an error is output to the target log file.

[0093] The application program checks whether the long shunting route code in the long shunting route interlocking table exists in the long shunting route button table, specifically, the long shunting route code corresponding to the long shunting route in the long shunting route interlocking table is compared with each long shunting route code in the long shunting route button table, if it exists, it is correct, if it does not exist, it is incorrect, and an error is output to the target log file.

[0094] The application program checks whether the long shunting route code in the long shunting route button table exists in the long shunting route interlocking table, specifically, the long shunting route code corresponding to the long shunting route in the long shunting route button table is compared with each long shunting route code in the long shunting route interlocking table, if it exists, it is correct, if it does not exist, it is wrong, and the error is output to the target log file.

[0095] The application program checks whether the Hamming code of the long shunting route code in the long shunting route interlocking table is correct, specifically, the Hamming code of the long shunting route code is recalculated according to the last four digits of the long shunting route code in the long shunting route interlocking table using the Hamming code calculation formula, and compared with the original Hamming code of the long shunting route code (i.e. the first four digits of the long shunting route code), if they are the same, it is correct, if they are different, it is wrong, and the error is output to the target log file.

[0096] The application program checks whether the Hamming code of the long shunting route code in the long shunting route button table is correct, specifically, the Hamming code of the long shunting route code is recalculated according to the last four digits of the long shunting route code in the long shunting route button table using the Hamming code calculation formula, and compared with the original Hamming code of the long shunting route code (i.e. the first four digits of the long shunting route code), if they are the same, it is correct, if they are different, it is wrong, and the error is output to the target log file.

[0097] The shunting route identifier includes a long shunting route identifier and a short shunting route identifier, the long shunting route identifier includes a long shunting route code and a Hamming code of the long shunting route code, and the short shunting route identifier includes a short shunting route code and a Hamming code of the short shunting route code.

[0098] Further, in one embodiment, the third parameter in the second configuration file is checked for correctness, and the third parameter includes a start button identifier and an end button identifier, and can specifically include:

[0099] Check whether the start button code of the long shunting route in the long shunting route button table is the same as the start button code of the first short shunting route included in the long shunting route;

[0100] Check whether the end button code of the long shunting route in the long shunting route button table is the same as the end button code of the last short shunting route included in the long shunting route.

[0101] Optionally, the application program checks whether the start button code of the long shunting route in the long shunting route button table is the same as the start button code of the first short shunting route in it, specifically, the start button code of the long shunting route is obtained by finding the corresponding data in the long shunting route button table through the long shunting route code in the long shunting route interlocking table; the start button code of the first short shunting route is obtained by finding the corresponding data in the shunting route button table through the first short shunting route code in the long shunting route, and then it is compared whether the start button code of the short shunting route is the same as the start button code of the long shunting route, if the same, it is correct, if different, it is wrong, and the error is output to the target log file.

[0102] The application program checks whether the terminal button of the long shunting route is the same as the terminal button of the last short shunting route in it, specifically, the terminal button code of the long shunting route is obtained by finding the corresponding data in the long shunting route button table through the long shunting route code in the long shunting route interlocking table; the terminal button code of the last short shunting route is obtained by finding the corresponding data in the shunting route button table through the last short shunting route code in the long shunting route, and then it is compared whether the terminal button code of the short shunting route is the same as the terminal button code of the long shunting route, if the same, it is correct, if different, it is wrong, and the error is output to the target log file.

[0103] Further, in one embodiment, the checking whether the short shunting routes included in the long shunting route in the first configuration file are correct can specifically include:

[0104] Obtaining the short shunting route codes included in the long shunting route in the first configuration file;

[0105] Determining the short shunting routes corresponding to the short shunting route codes;

[0106] Checking whether the departure section code of the first short shunting route and the approach section code of the second short shunting route in the multiple short shunting routes are the same, the start signal of the second short shunting route being the same as the terminal signal of the first short shunting route.

[0107] Optionally, the application program checks whether the short shunting routes in the long shunting route in the first configuration file are connected head to tail, that is, the departure section code of the previous short shunting route (i.e., the first short shunting route) is equal to the approach section code of the next short shunting route (i.e., the second short shunting route), specifically, by the short shunting route code contained in the long shunting route in the first configuration file, finding the corresponding short shunting route in the shunting route interlocking table, obtaining the departure section code and the approach section code of the short shunting route, and comparing the departure section codes and the approach section codes of the previous and next short shunting routes in turn, if the same, it is correct, if different, it is wrong, and the error is output to the target log file. Wherein, the terminal signal of the previous short shunting route is the same as the start signal of the second short shunting route.

[0108] The shunting route data checking method provided by the application reads three configuration files through the developed application program, identifies and stores the shunting route and long shunting route data in the three configuration files, and then performs relevant correctness checking on the short shunting route data and the long shunting route data through program logic, thereby replacing the traditional manual checking of shunting route data, which is inefficient and difficult to effectively check all data errors, and the process of checking is prone to human error, thereby improving the shunting route data checking efficiency and accuracy.

[0109] Further, in one embodiment, after the correctness of the shunting route data in the target configuration file is checked, the method can further specifically include:

[0110] The correctness checking result is stored.

[0111] Optionally, after the correctness of the shunting route data in the target configuration file is checked, the obtained correctness checking result is output to the target log file for storage.

[0112] For example, the target configuration file is three interlocking data configuration files of ShuntTab.c, lsfdata3.c and lskzmac1.h, wherein ShuntTab.c is the first configuration file, lsfdata3.c is the second configuration file, and lskzmac1.h is the third configuration file, Figure 2 is the schematic diagram of the automatic checking tool interface of the shunting route provided by the application, as Figure 2As shown, by clicking the "Select File" control in the shunting route automatic inspection tool interface, the target configuration file is imported into the tool for reading. The lskzmac1.h file is read, and the values ​​of the two parameters, SHUNT_MAX (the number of first shunting routes, i.e., the maximum number of shunting routes) and LONG_SHUNT_MAX (the number of long shunting routes, i.e., the maximum number of long shunting routes), are obtained from it. Specifically, as shown... Figure 3 As shown.

[0113] Read the ShuntTab.c file and retrieve the short shunting route data stored in the ShuntTable interlocking table, such as... Figure 4 As shown, the short shunting route code, the approach section code, and the departure section code of the short shunting route are obtained from the data structure of the short shunting route data, and the number of short shunting routes in this table is counted.

[0114] Read the ShuntTab.c file and retrieve the long shunting route data stored in the LongShuntTable long shunting route interlocking table, such as... Figure 5 As shown, the long shunting route code, the number of short shunting routes included in the long shunting route corresponding to the long shunting route code, and the short shunting route code are obtained from the data structure of the long shunting route data, and the number of long shunting routes is counted.

[0115] Read the lsfdata3.c file and retrieve the short shunting route data stored in the ShuntBtnTable, such as... Figure 6 As shown, each row of data in the shunting route button table represents a short shunting route button data. The start button code, end button code, and short shunting route code of the short shunting route are obtained from it, and the number of short shunting routes in this table is counted.

[0116] Read the lsfdata3.c file and retrieve the long shunting route data stored in the ShuntBtnTable long shunting route button table, such as... Figure 7 As shown, each row of data represents a long shunting route button data. The start button code, end button code, and long shunting route code of the long shunting route are obtained from it, and the number of long shunting routes in this table is counted.

[0117] The automatic shunting route inspection tool performs logical calculations and processes according to the shunting route data inspection method provided by this invention to determine whether there are errors in the shunting route data in the interlocking data configuration files ShuntTab.c, lsfdata3.c and lskzmac1.h. If there are errors, the errors are printed out and can be exported to a target log file such as log.txt.

[0118] The application provides a shunting route data checking method, three configuration files are read through an application, shunting route data is identified and acquired from the three configuration files, the shunting route data is checked, and data errors in the checking are output to a target log file, so that the data errors are convenient to view.

[0119] The shunting route data checking system provided by the application is described below, and the shunting route data checking system described below can be correspondingly referred to the shunting route data checking method described above.

[0120] Figure 8 FIG. 1 is a structural schematic diagram of the shunting route data checking system provided by the application, as shown in the figure, comprising: Figure 8

[0121] The acquisition module 810 and the checking module 811;

[0122] The acquisition module 810 is used for reading a target configuration file, and the target configuration file is a configuration file of shunting route data.

[0123] The checking module 811 is used for performing correctness checking on the shunting route data in the target configuration file.

[0124] The shunting route data checking system provided by the application can identify the shunting route data in the target configuration file by reading the target configuration file, and then perform relevant correctness checking on the identified shunting route data, so as to replace the traditional manual checking of shunting route data, which is inefficient and difficult to effectively check all data errors, and the checking process is prone to manual errors.

[0125] Figure 9 FIG. 1 is a structural schematic diagram of the shunting route data checking system provided by the application, as shown in the figure, comprising: Figure 9 FIG. 1 is a structural schematic diagram of the shunting route data checking system provided by the application, as shown in the figure, comprising:

[0126] The acquisition module 810 is used for reading a target configuration file, and the target configuration file is a configuration file of shunting route data.

[0127] The checking module 811 is used for performing correctness checking on the shunting route data in the target configuration file.

[0128] ​In addition, the logic instructions in the above-mentioned memory can be realized in the form of a software function unit and sold or used as an independent product, and can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application essentially or the parts that contribute to the prior art or parts of the technical solutions can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a plurality of instructions to make a computer power supply screen (which can be a personal computer, a server, or a network power supply screen) execute all or part of the steps of the method described in each embodiment of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and various media that can store program codes.

[0129] Further, the present application discloses a computer program product, which comprises a computer program stored on a non-transitory computer readable storage medium, and the computer program comprises program instructions, and when the program instructions are executed by a computer, the computer can execute the shunting route data checking method provided by the above-mentioned method embodiments, for example, comprising:

[0130] reading a target configuration file, wherein the target configuration file is a configuration file of shunting route data;

[0131] performing correctness checking on the shunting route data in the target configuration file.

[0132] On the other hand, the present application also provides a non-transitory computer readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the shunting route data checking method provided by the above-mentioned embodiments is realized, for example, comprising:

[0133] reading a target configuration file, wherein the target configuration file is a configuration file of shunting route data;

[0134] performing correctness checking on the shunting route data in the target configuration file.

[0135] The system embodiments described above are only illustrative, wherein the units illustrated as separate components can or can not be physically separated, and the components illustrated as units can or can not be physical units, that is, they can be located in one place or distributed on multiple network units. Part or all of the modules can be selected to achieve the purpose of the present embodiment according to actual needs. Those skilled in the art can understand and implement without creative labor.

[0136] Those skilled in the art can clearly understand the technical solutions of the various embodiments from the above description of the embodiments, and the various embodiments can be implemented by means of software with the necessary general hardware platforms, and of course, can also be implemented by hardware. Based on such understanding, the above technical solutions, essentially or in other words, the part of the prior art that makes a contribution, can be embodied in the form of a software product, which can be stored in a computer readable storage medium, such as a ROM / RAM, a magnetic disk, an optical disk, and the like, and includes a number of instructions for causing a computer power supply screen (which can be a personal computer, a server, or a network power supply screen, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0137] Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: it can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacement for some technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the various embodiments of the present application.

Claims

1. A method of car routing data checking, characterized by, The method comprises the following steps: reading a target configuration file, wherein the target configuration file is a configuration file of shunting route data; the target configuration file comprises a first configuration file and a second configuration file; checking the correctness of the shunting route data in the target configuration file, comprising: checking whether the short shunting routes included in the long shunting route in the first configuration file are correct, comprising: obtaining the short shunting route codes included in the long shunting route in the first configuration file; determining the short shunting routes corresponding to the short shunting route codes; checking whether the departure section code of a first short shunting route and the approach section code of a second short shunting route are the same, wherein the initial signal of the second short shunting route is the same as the terminal signal of the first short shunting route; checking the correctness of a third parameter in the second configuration file, wherein the third parameter comprises the initial button identification and the terminal button identification of the long shunting route, comprising: checking whether the initial button code of the long shunting route in the long shunting route button table is the same as the initial button code of the first short shunting route included in the long shunting route; checking whether the terminal button code of the long shunting route in the long shunting route button table is the same as the terminal button code of the last short shunting route included in the long shunting route.

2. The method of car routing data checking according to claim 1, wherein, The checking of the correctness of the shunting route data in the target configuration file further comprises: checking the correctness of a first parameter in the first configuration file, the second configuration file and the third configuration file, wherein the target configuration file further comprises the third configuration file, and the first parameter comprises the first shunting route quantity and the second shunting route quantity, wherein the first shunting route quantity is the sum of the long shunting route quantity and the short shunting route quantity, and the second shunting route quantity is the long shunting route quantity, the short shunting route is a shunting route comprising one initial signal and one terminal signal, and the long shunting route comprises a plurality of short shunting routes; checking the correctness of a second parameter in the first configuration file and the second configuration file, wherein the second parameter comprises the shunting route identification and the short shunting route quantity.

3. The method of car shunting route data checking according to claim 2, characterized in that, The checking of the correctness of the second parameter in the first configuration file and the second configuration file comprises: checking whether the long shunting route code in the long shunting route interlocking table in the first configuration file is correct; checking whether the long shunting route code in the long shunting route button table in the second configuration file is correct; checking whether the short shunting route code included in the long shunting route in the first configuration file exists in the shunting route button table in the second configuration file; checking whether the short shunting route code included in the long shunting route in the long shunting route interlocking table exists in the shunting route interlocking table; checking whether the long shunting route code in the long shunting route interlocking table exists in the long shunting route button table; checking whether the long shunting route code in the long shunting route button table exists in the long shunting route interlocking table; checking whether the Hamming code of the long shunting route code in the long shunting route interlocking table is correct; checking whether the Hamming code of the long shunting route code in the long shunting route button table is correct; The shunting route identifier includes a long shunting route identifier and a short shunting route identifier, the long shunting route identifier includes a long shunting route code and a Hamming code of the long shunting route code, and the short shunting route identifier includes a short shunting route code and a Hamming code of the short shunting route code.

4. The method of inspecting the shunting route data according to any one of claims 1 to 3, characterized in that, After the correctness of the shunting route data in the target configuration file is checked, the method further includes: storing the correctness checking result.

5. A car routing data checking system characterized by, The method for checking the shunting route data according to claim 1 comprises an obtaining module and a checking module. The obtaining module is configured to read a target configuration file, and the target configuration file is a configuration file of shunting route data. The checking module is configured to check the correctness of the shunting route data in the target configuration file.

6. An electronic device comprising a processor and a memory having a computer program stored therein, characterized in that The processor executes the computer program to implement the method for checking the shunting route data according to any one of claims 1 to 4.

7. A non-transitory computer-readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by the processor to implement the method for checking the shunting route data according to any one of claims 1 to 4.

8. A computer program product comprising a computer program, characterized in that, The computer program is executed by the processor to implement the method for checking the shunting route data according to any one of claims 1 to 4.

Images