An automatic testing method for the interaction code position of the interlocking system and the external system interface

Abstract

The present invention provides an automated testing method for the interface code positions of an interlocking system and an external system. The method obtains the route and signal information of the interface between the interlocking system and the external system, as well as the code position information of the interaction between the interlocking system and the external system through an interface information table; performs simulation on a general use case of a test scenario written in a formal language through automatic testing software, traverses the test objects of the station, and generates instantiated use cases based on the general use case and station field data; assigns a value to the input code position of the interlocking system, and the automatic testing software automatically calculates according to the interlocking rules of the interlocking system to obtain the calculated value of the output code position; the automatic testing software performs a consistency comparison to determine whether the output code position of the interface between the interlocking system and the external system meets expectations. The present invention can improve test efficiency and coverage of test objects, reduce manual testing time, and avoid manual omissions.

Description

Technical Field

[0001] The present invention relates to the field of system testing, and in particular to an automatic testing method for interactive code bits of an interlocking system and an external system interface. Background Art

[0002] The interlocking system (CI) ensures the safe operation of trains within stations and is a key subsystem of the train control system. It performs a series of functions, including automatic external input acquisition, interlocking logic operations, and output of control commands to external devices. The interlocking system has numerous interfaces with external systems, such as the interface between the interlocking system and the train control center (CI-TCC) and the interface between the interlocking system and the radio block center (CI-RBC). The accuracy of the information exchanged between these interfaces directly affects train safety. Therefore, testing the code bits of the CI-TCC and CI-RBC interfaces has always been a key part of interlocking testing, but currently there is a lack of automated testing technology for these aspects. Summary of the Invention

[0003] The present invention provides an automatic testing method for the interactive code bits of an interlocking system and an external system interface, which can respectively test the interactive code bit information between CI-TCC interfaces and CI-RBC interfaces, thereby improving the testing efficiency.

[0004] To achieve the above objectives, the technical solution of the present invention is to provide an automated testing method for the interface code between the interlocking system and the external system. Through the interface information table, the route and signal information of the interface between the interlocking system and the external system, as well as the code information of the interaction between the interlocking system and the external system are obtained;

[0005] For general use cases of test scenarios written in formal languages, use automatic testing software to perform simulations, traverse the test objects of the station, and generate instantiated use cases based on general use cases and station data;

[0006] Assign values ​​to the input code bits of the interlocking system, and the automatic test software automatically calculates according to the interlocking rules of the interlocking system to obtain the calculated values ​​of the output code bits;

[0007] The automatic test software performs a consistency comparison to determine whether the output code bits of the interlocking system and the external system interface are as expected.

[0008] Optionally, the external system includes a train control center TCC;

[0009] When the automatic test method is used to automatically test the interface code position between the interlocking system and the train control center, the interface information table between the interlocking system and the train control center is read in, and the station basic information file, the station yard basic information file, and other external interface files are obtained;

[0010] Obtaining, through the interface information table between the interlocking system and the train control center, the route name and direction signal name of the interface with the train control center, as well as the code position information exchanged between the interlocking system and the train control center; the code position information includes the code positions collected by the interlocking system from the train control center and the code positions sent by the interlocking system to the train control center;

[0011] The station basic information file includes interlocking tables, station signals, switches, basic attributes of sections, and directional blocking information;

[0012] The basic information file of the station includes the topological connection relationship of the station and all the equipment attribute information of the station;

[0013] The external interface file includes an interface information code table between the interlocking system and the trackside, an interface information table between the interlocking system and the radio block center, and an interface information code table between the interlocking system and the adjacent station interlocking system.

[0014] Optionally, general use cases written in a formal programming language that are recognizable by the automatic testing software, including test cases corresponding to the train control center test scenarios;

[0015] The test cases include route establishment, signal opening and different signals displayed in the open state, normal unlocking, manual unlocking of routes, and section / signal / switch failure scenarios. In different scenarios, in the test cases, the command issuance operation is simulated by setting initial values ​​for input parameters, and the waiting time is set to execute the interlocking rules. The corresponding expected values ​​of the train control center interface variables are also set as reference values ​​for consistency comparison.

[0016] Optionally, the automatic test software performs a consistency comparison to determine whether the output code bits sent by the interlocking system to the train control center are consistent with expectations. If they are consistent with expectations, a test pass result is given; otherwise, a test case failure result is given;

[0017] When performing consistency comparison, it includes checking whether the TCC variable changes of the route / equipment to be tested are in line with expectations, whether the TCC variables of other unrelated routes / equipment at this station are not affected, and whether the RBC variable status of unrelated routes at this station is not affected; among them, RBC refers to the radio block center.

[0018] Optionally, the consistency comparison performed includes:

[0019] Traverse each access route to the train control center interface and perform the following checks when executing the test cases corresponding to the train control center test scenario:

[0020] Determine whether the state changes of TCC variables related to the route are in line with expectations;

[0021] Determine whether the TCC variable status changes of all other unrelated routes other than this route are not affected;

[0022] Determine whether the state changes of RBC variables of all unrelated pathways are not affected;

[0023] Also, traverse each route that does not interface with the train control center and perform the following checks when executing the test cases corresponding to the train control center test scenario:

[0024] Determine whether the state changes of TCC variables related to the route are not affected;

[0025] Determine whether the TCC variable status changes of all unrelated routes are not affected;

[0026] Determine whether the RBC variable state changes of all unrelated routes are not affected.

[0027] Optionally, the external system includes a radio block center RBC;

[0028] When the automatic test method is used to automatically test the interface code position between the interlocking system and the radio block center, the interface information table between the interlocking system and the radio block center is read in, and the station basic information file, the station yard basic information file, and other external interface files are obtained;

[0029] Using the interface information table between the interlocking system and the radio block center, for routes that use the RBC1, RBC2, or RBC3 protocol interface, the route name and code information exchanged between the interlocking system and the radio block center are obtained; the code information includes the code sent by the interlocking system to the radio block center. For routes that use the RBC2 protocol interface, the name of the authorized point signal is also obtained from the interface information table.

[0030] The station basic information file includes interlocking tables, station signals, switches, basic attributes of sections, and directional blocking information;

[0031] The basic information file of the station includes the topological connection relationship of the station and all the equipment attribute information of the station;

[0032] The external interface file includes an interface information code table between the interlocking system and the trackside, an interface information table between the interlocking system and the train control center, and an interface information code table between the interlocking system and the adjacent station interlocking system.

[0033] Optionally, general use cases written in a formal programming language and recognizable by the automatic test software, including test cases corresponding to the RBC test scenario;

[0034] Test cases applicable when the interface adopts the RBC2 protocol include scenarios such as route establishment, signal closure due to an error, normal unlocking of the positive route, manual unlocking, and section / signal / turnout equipment failure.

[0035] Test cases applicable when the interface adopts the RBC1 or RBC3 protocol. The included scenarios can be used to test the changes in related variables when the RBC route status transitions between each other. The RBC route status transition relationships include: "Inactive <-> Normal", "Inactive <-> Guided", "Unavailable -> Inactive", "In Use -> Inactive", "Normal <-> In Use", "Guided <-> Passing", "Unavailable <-> Normal", and "Unavailable <-> Guided";

[0036] In different scenarios, the test cases simulate command issuance operations by setting initial values ​​for input parameters and setting waiting times to execute interlocking rules; they also set corresponding expected values ​​of RBC interface variables as reference values ​​for consistency comparison.

[0037] Optionally, a consistency comparison is performed by automatic test software to determine whether the output code bits sent by the interlocking system to the radio block center are consistent with expectations. If they are consistent with expectations, a test pass result is given; otherwise, a test case failure result is given;

[0038] When performing consistency comparison, it includes checking whether the RBC variable change status of the route / authorization point to be tested is as expected, whether the RBC variable status of other unrelated routes / authorization points of this station is not affected, and whether the TCC variable status of unrelated routes of this station is not affected; among them, TCC refers to the train control center.

[0039] Optionally, when the interface adopts the RBC2 protocol and the authorization point has a corresponding sub-route, the consistency comparison performed includes:

[0040] Traverse each route that interfaces with the RBC2 protocol and execute the test cases applicable to the RBC2 protocol to perform the following checks:

[0041] Determine whether the status of the variables related to the signal authorization point corresponding to the route meets expectations;

[0042] Determine whether the states of variables related to signal authorization points corresponding to all other irrelevant routes other than this route are not affected;

[0043] Determine whether the TCC variables and RBC1 and RBC3 variable states of all unrelated routes are not affected;

[0044] Furthermore, each route that does not use the RBC2 protocol interface is traversed, and the test cases applicable to the RBC2 protocol are executed to perform the following checks:

[0045] Determine whether the states of variables related to the signal authorization points corresponding to these routes are not affected;

[0046] Determine whether the states of variables related to the signal authorization points corresponding to all irrelevant routes are not affected;

[0047] Determine whether the TCC variables and RBC1 and RBC3 variable states of all unrelated routes are not affected;

[0048] When the interface adopts the RBC2 protocol and the authorization point has no corresponding sub-path, the consistency comparison performed is to traverse the relevant signal authorization points, execute the RBC2 interface test cases, and determine whether the variable state changes of the relevant RBC2 signal authorization points are in line with expectations;

[0049] The routes that do not interface with the RBC2 protocol include routes that do not interface with the radio block center, and also include routes that interface with the radio block center using protocols other than the RBC2 protocol.

[0050] Among them, irrelevant paths mean that when the executed test case has an impact on the RBC variable / TCC variable of any path, the path needs to be excluded.

[0051] Optionally, when the interface adopts the RBC1 or RBC3 protocol, the consistency comparison performed includes:

[0052] Traverse each route that interfaces with the RBC using the RBC1 or RBC3 protocol, execute the test cases applicable to the RBC1 or RBC3 protocol, and perform the following checks:

[0053] Determine whether the changes in the RBC1 and RBC3 variable states related to the route are in line with expectations;

[0054] Determine whether the RBC1 variable status and RBC3 variable status changes of all other unrelated routes other than this route are not affected;

[0055] Determine whether the status changes of TCC variables and RBC2 variables of all unrelated routes are not affected.

[0056] Traverse each route that does not use the RBC1 or RBC3 protocol interface, execute the test case applicable to the RBC1 or RBC3 protocol, and perform the following checks:

[0057] Determine whether the RBC1 variable status and RBC3 variable status changes related to the route are not affected;

[0058] Determine whether the RBC1 variable status and RBC3 variable status changes of all unrelated routes are not affected;

[0059] Determine whether the state changes of TCC variables and RBC2 variables of all unrelated routes are not affected;

[0060] Among them, routes that do not interface with the RBC1 or RBC3 protocols include routes that do not interface with the Radio Block Center, and also include routes that interface with the Radio Block Center using protocols other than RBC1 and RBC3 protocols;

[0061] Among them, irrelevant paths mean that when the executed test case has an impact on the RBC variable / TCC variable of any path, the path needs to be excluded.

[0062] Compared with the prior art, the above technical solution of the present application has the following beneficial effects:

[0063] (1) A formalized automatic test script is used. The general test script and the station data are independent. Therefore, the test case has good versatility. When the interlocking data input proposed by the present invention is met, the test script of the present invention can be used to perform the test;

[0064] (2) The universal test case of the present invention has good scalability and supports the addition of test cases for other external interface code positions such as the CI and the neighboring station CI;

[0065] (3) Execute test cases in a traversal manner to achieve 100% coverage of the test objects, which saves time and effort compared to manual testing and avoids omission of test objects due to manual negligence;

[0066] (4) In addition to testing scenario-related RBC / TCC variable state changes, the test script of the present invention also adds a check that irrelevant variables are not affected, making the test variable range more comprehensive. BRIEF DESCRIPTION OF THE DRAWINGS

[0067] Figure 1 Flowchart of the CI-TCC interface code position automatic testing method of the present invention;

[0068] Figure 2 This is a flow chart of the CI-RBC interface code bit automatic testing method of the present invention. DETAILED DESCRIPTION

[0069] The present invention will be described in detail below with reference to the accompanying drawings and specific embodiments.

[0070] This paper provides an automated testing method for the interface codes between an interlocking system and external systems. This method primarily tests the code information exchanged between the CI-TCC and CI-RBC interfaces, two safety interfaces in the national railway interlocking system. TCC and RBC represent two external systems: the train control center and the radio block center.

[0071] In the described test method, the CI-TCC or CI-RBC interface information table is used to obtain the route, signal information, and corresponding interactive code information of the interlocking system CI and TCC or RBC interface; a general use case of the test scenario is written in a formal language; the simulation is performed by automatic testing software to traverse the test objects of this station, and instantiated use cases are generated based on the general use case and station data; the consistency comparison is performed by the automatic testing software to determine whether the output code of the CI-TCC or CI-RBC meets expectations. In addition to checking the interface variables related to this test, the test case also traverses and checks the irrelevant interface variables of the entire station to make the test surface more comprehensive. Among them, the test objects of the interlocking system are station equipment (signals / turnouts / sections) and routes.

[0072] The automatic testing software supports reading and identifying test case scripts modeled in formal languages ​​and written in formal languages. A test case is a set of input-output relationships including input, execution conditions and output, which is used to test whether a program meets a specific requirement. The main implementation method of the test case is to assign values ​​to the input code bits of the interlocking system. The automatic testing software automatically calculates according to the interlocking rules of the interlocking system, and can provide the calculation results of any code bits, compare whether the calculated values ​​of the required code bits are consistent with the expected results, and give a test pass result if they are consistent, and a test case failure result if they are inconsistent; the automatic testing software provides functions such as a visual station diagram interface, post-instantiation use case debugging and variable tracking.

[0073] The automated testing software can traverse all test objects based on the general use cases of the test scenario, generate corresponding instantiated test cases, and support debugging and variable tracking of the instantiated test cases. The general use cases are test scripts written in a formal language and support for foreach traversal of test objects, wait / during delay settings, and expect settings for expected results, making the scripts highly readable.

[0074] The interlocking rule is a set of BOOL expressions. The BOOL variables involved include input variables, intermediate variables, and output variables. The variable values ​​are Bool type values. The values ​​of the intermediate variables and output variables can be calculated based on the input variable values ​​and the BOOL expressions.

[0075] like Figure 1 As shown, the CI-TCC interface code position automatic testing method of the present invention has the following specific steps:

[0076] Step S101: Read the CI-TCC interface information table to obtain the station basic information file, the station yard basic information file, and other external interface files;

[0077] Step S102: Using the CI-TCC interface information table, obtain the route name, direction signal name, and corresponding interactive code position information of the TCC interface;

[0078] Step S103: Using a formal programming language, write a general use case of the TCC test scenario that can be identified by the automatic testing software;

[0079] Step S104: Execute simulation through the automatic test software, traverse the test objects of the station, and generate instantiated use cases based on the general use cases and station data;

[0080] Step S105: Perform consistency comparison using automatic testing software to determine whether the output code bits of CI->TCC meet expectations.

[0081] Among them, the CI-TCC interface information table includes information such as the route, direction signal, shunting danger signal, disaster alarm, etc. interacted between CI and TCC, as well as the code position information interacted between CI and TCC, including the code positions collected by CI from TCC and the code positions sent by CI to TCC.

[0082] The station basic information file includes interlocking tables, basic attributes of station signals, switches, sections, direction blocking information and other equipment information of the station.

[0083] The station basic information file includes the topological connection relationship of the station and all equipment attribute information of the station.

[0084] The external interface file includes the interface information code bit table between CI and trackside, the interface information table between CI and RBC, and the interface information code bit table between the current CI and the neighboring station CI.

[0085] The TCC test scenarios include test cases for route establishment, signal release (different signal displays), normal unlocking, manual route unlocking, and section / signal / switch failure scenarios. In each scenario, the test cases simulate command issuance by setting initial values ​​for input parameters and setting wait times for executing interlocking rules. Expected values ​​for corresponding TCC interface variables are also set as reference values ​​for consistency comparison.

[0086] The consistency comparison includes checking whether the TCC variable changes of the tested route / equipment itself are in line with expectations, whether the TCC variables of other unrelated routes / equipment at this site are not affected, and whether the RBC variable status of unrelated routes at this site is not affected.

[0087] Specifically, the consistency comparison of the CI->TCC interface needs to check the following:

[0088] (1) Traverse each path to the TCC interface and execute the TCC interface test case:

[0089] ① Determine whether the state changes of the TCC variables related to the route are in line with expectations;

[0090] ② Determine whether the TCC variable status changes of all other unrelated routes other than this route are not affected;

[0091] ③ Determine whether the RBC variable state changes of all unrelated routes are not affected.

[0092] (2) Traverse each route that does not interface with the TCC and execute the TCC interface test case:

[0093] ① Determine whether the state changes of TCC variables related to the route are not affected;

[0094] ② Determine whether the TCC variable status changes of all unrelated routes are not affected;

[0095] ③ Determine whether the RBC variable state changes of all unrelated routes are not affected.

[0096] Among them, irrelevant paths refer to when the executed test case has an impact on the RBC variable / TCC variable of a certain path, and the path needs to be excluded.

[0097] like Figure 2 As shown, the CI-RBC interface code position automatic testing method of the present invention has the following specific steps:

[0098] Step S201: Read the CI-RBC interface information table to obtain the station basic information file, the station yard basic information file, and other external interface files;

[0099] Step S202: Using the CI-RBC interface information table, obtain the route name, authorization point signal name, and corresponding interaction code information for the RBC interface. The authorization point signal name is only obtained when using the RBC protocol 2 interface mode.

[0100] Step S203: Using a formal programming language, write a general use case of the RBC test scenario that can be identified by the automatic testing software;

[0101] Step S204: Execute simulation through the automatic test software, traverse the test objects of the station, and generate instantiated use cases based on the general use cases and station data;

[0102] Step S205: Perform consistency comparison using automatic testing software to determine whether the output code bits of CI->RBC meet expectations.

[0103] Among them, the CI-RBC interface information table includes the interaction information table with CI when using RBC protocol 1, protocol 2, and protocol 3 (RBC1, RBC2, RBC3), including the route information of the RBC1 / RBC3 interface, the route information of the RBC2 interface, and the signal authorization point information and disaster area information corresponding to each route. Specifically, through the CI-RBC interface information table, the route name of the RBC1 or RBC3 interface and the corresponding interactive code position information can be obtained; or the route name, authorization point information (authorization point signal machine name) and the corresponding interactive code position information with the RBC2 interface can be obtained. The code position information includes the relevant code positions sent by CI to RBC, mainly the route / signal authorization point related code positions.

[0104] The station basic information file includes interlocking tables, basic attributes of station signals, switches, sections, direction blocking information and other equipment information of the station.

[0105] The basic information file of the station includes the topological connection relationship of the station and all the equipment attribute information of the station.

[0106] The external interface file includes the interface information code bit table between CI and trackside, the interface information table between CI and TCC, and the interface information code bit table between the current CI and the neighboring station CI.

[0107] The test cases corresponding to the RBC test scenarios include, when the interface adopts the RBC2 protocol, testing route establishment, signal closure due to reasons, normal unlocking of the positive route, manual unlocking, and section / signal / switch equipment failure scenarios. When the interface adopts the RBC1 or RBC3 protocol, the test cases include testing the changes in relevant variables during the conversion of RBC route states as specified in the "CTCS-3 Level Train Control System Radio Block Center (RBC) Interface Specification Part 1: RBC-CBI Interface". Among them, the RBC route state conversion relationships include: "Inactive <-> Normal", "Inactive <-> Guidance", "Unavailable -> Inactive", "In Use -> Inactive", "Normal <-> In Use", "Guidance <-> Passing", "Unavailable <-> Normal", and "Unavailable <-> Guidance". The meaning of each route state can be found in the "CTCS-3 Level Train Control System Radio Block Center (RBC) Interface Specification Part 1: RBC-CBI Interface" document.

[0108] In different scenarios, the test cases simulate command issuance operations by setting initial values ​​for input parameters and setting waiting times to execute interlocking rules; they also set corresponding expected values ​​of RBC interface variables as reference values ​​for consistency comparison.

[0109] The consistency comparison includes checking whether the RBC variable change status of the route / authorization point to be tested is consistent with expectations, whether the RBC variable status of other irrelevant routes / authorization points of this site is not affected, and whether the TCC variable status of irrelevant routes of this site is not affected.

[0110] Specifically, the consistency comparison of the CI->RBC (Protocol 2) interface needs to check the following:

[0111] The authorization point has a corresponding sub-path:

[0112] (1) Traverse each path with RBC2 protocol interface and execute the test cases applicable to RBC2 protocol:

[0113] ① Determine whether the status of the variables related to the signal authorization point corresponding to the route meets expectations;

[0114] ② Determine whether the states of variables related to the signal authorization points corresponding to all other irrelevant routes other than this route are not affected;

[0115] ③ Determine whether the TCC variables and RBC1 / RBC3 variable status of all unrelated routes are not affected.

[0116] (2) Traverse each path that does not use the RBC2 protocol interface and execute the test cases applicable to the RBC2 protocol:

[0117] ① Determine whether the status of the variables related to the signal authorization points corresponding to these routes are not affected;

[0118] ② Determine whether the status of the variables related to the signal authorization points corresponding to all irrelevant routes are not affected;

[0119] ③ Determine whether the TCC variables and RBC1 / RBC3 variable states of all unrelated routes are unaffected. Routes that do not interface with the RBC2 protocol include routes that do not interface with the RBC and routes that interface with the RBC via other protocols (except the RBC2 protocol).

[0120] The authorization point has no corresponding sub-path:

[0121] Traverse the relevant signal authorization points, execute the applicable test cases when the RBC2 protocol is executed, and determine whether the variable state changes of the relevant RBC2 signal authorization points are in line with expectations.

[0122] Specifically, the consistency comparison of the CI->RBC (Protocol 1 / Protocol 3) interface needs to check the following:

[0123] (1) Traverse each path with RBC1 or RBC3 protocol interface and execute RBC1 / RBC3 interface test cases:

[0124] ① Determine whether the state changes of the RBC1 and RBC3 variables related to the route are in line with expectations;

[0125] ② Determine whether the state changes of RBC1 and RBC3 variables of all other unrelated routes other than this route are not affected;

[0126] ③ Determine whether the state changes of TCC variables and RBC2 variables of all unrelated routes are not affected.

[0127] (2) Traverse each route that does not use the RBC1 or RBC3 protocol interface and execute the RBC1 / RBC3 interface test case:

[0128] ① Determine whether the state changes of RBC1 and RBC3 variables related to the route are not affected;

[0129] ② Determine whether the state changes of RBC1 and RBC3 variables of all unrelated routes are not affected;

[0130] ③ Determine whether the state changes of TCC variables and RBC2 variables of all unrelated routes are not affected.

[0131] Paths that do not interface with the RBC1 or RBC3 protocols include those that do not interface with RBC, as well as those that interface with RBC using other protocols (other than RBC1 / RBC3). Irrelevant paths are defined as those that need to be excluded when the executed test case affects the RBC variables / TCC variables of a particular path.

[0132] In summary, the present invention provides an automated testing method for the interface code positions between an interlocking system and an external system. It adopts a formalized test script to write test cases, and utilizes an automatic testing tool to facilitate the automatic testing of information code positions between interfaces, effectively improving the testing efficiency of the interlocking system and the external interface code positions, and the coverage of the test objects, reducing manual testing time, and avoiding manual omissions.

[0133] Although the present invention has been described in detail through the above preferred embodiments, it should be understood that the above description is not intended to limit the present invention. After reading the above description, various modifications and substitutions of the present invention will become apparent to those skilled in the art. Therefore, the scope of protection of the present invention should be defined by the appended claims.

Claims

1. An automated testing method for the interface code between an interlocking system and an external system, characterized in that: Through the interface information table, obtain the route and signal information of the interface between the interlocking system and the external system, as well as the code position information of the interaction between the interlocking system and the external system; For general use cases of test scenarios written in formal languages, use automatic testing software to perform simulations, traverse the test objects of the station, and generate instantiated use cases based on general use cases and station data; Assign values ​​to the input code bits of the interlocking system, and the automatic test software automatically calculates according to the interlocking rules of the interlocking system to obtain the calculated values ​​of the output code bits; The automatic test software performs consistency comparison to determine whether the output code bits of the interlocking system and the external system interface are as expected; The external system includes a train control center TCC; when the automatic test method is used to automatically test the interface code position between the interlocking system and the train control center, the interface information table between the interlocking system and the train control center is read in, and the station basic information file, the station yard basic information file, and other external interface files are obtained; The external interface file includes an interface information table between the interlocking system and the radio block center; When performing consistency comparison, the following steps are performed: checking whether the TCC variable changes of the route / equipment to be tested are in line with expectations, whether the TCC variables of other unrelated routes / equipment at the site are not affected, and whether the RBC variable status of unrelated routes at the site is not affected; RBC refers to the Radio Block Center; When checking the RBC variable status of irrelevant routes of this station, it further includes judging whether the RBC variable status changes of all irrelevant routes are not affected when traversing each route that interfaces with the train control center, or when traversing each route that does not interface with the train control center.

2. The automated testing method according to claim 1, wherein: Obtaining, through the interface information table between the interlocking system and the train control center, the route name and direction signal name of the interface with the train control center, as well as the code position information exchanged between the interlocking system and the train control center; the code position information includes the code positions collected by the interlocking system from the train control center and the code positions sent by the interlocking system to the train control center; The station basic information file includes interlocking tables, station signals, switches, basic attributes of sections, and directional blocking information; The basic information file of the station includes the topological connection relationship of the station and all the equipment attribute information of the station; The external interface file includes an interface information code table between the interlocking system and the trackside, an interface information table between the interlocking system and the radio block center, and an interface information code table between the interlocking system and the adjacent station interlocking system.

3. The automated testing method according to claim 2, wherein: Common use cases written in a formal programming language that can be recognized by the automatic test software, including test cases corresponding to the train control center test scenarios; The test cases include route establishment, signal opening and different signals displayed in the open state, normal unlocking, manual unlocking of routes, and section / signal / turnout failure scenarios; In different scenarios, in the test cases described, the command issuance operation is simulated by setting initial values ​​for the input parameters and setting waiting times to execute the interlocking rules; the corresponding expected values ​​of the train control center interface variables are also set as reference values ​​for consistency comparison.

4. The automated testing method according to claim 3, wherein: Automatic test software is used to perform consistency comparisons to determine whether the output code bits sent by the interlocking system to the train control center meet expectations. If they are consistent with expectations, a test pass result is given; otherwise, a test case failure result is given.

5. The automated testing method according to claim 4, wherein: The consistency comparisons performed include: Traverse each access route to the train control center interface and perform the following checks when executing the test cases corresponding to the train control center test scenario: Determine whether the state changes of TCC variables related to the route are in line with expectations; Determine whether the TCC variable status changes of all other unrelated routes other than this route are not affected; Determine whether the state changes of RBC variables of all unrelated pathways are not affected; Also, traverse each route that does not interface with the train control center and perform the following checks when executing the test cases corresponding to the train control center test scenario: Determine whether the state changes of TCC variables related to the route are not affected; Determine whether the TCC variable status changes of all unrelated routes are not affected; Determine whether the RBC variable state changes of all unrelated routes are not affected.

6. An automated testing method for the interface code between an interlocking system and an external system, characterized in that: Through the interface information table, obtain the route and signal information of the interface between the interlocking system and the external system, as well as the code position information of the interaction between the interlocking system and the external system; For general use cases of test scenarios written in formal languages, use automatic testing software to perform simulations, traverse the test objects of the station, and generate instantiated use cases based on general use cases and station data; Assign values ​​to the input code bits of the interlocking system, and the automatic test software automatically calculates according to the interlocking rules of the interlocking system to obtain the calculated values ​​of the output code bits; The automatic test software performs consistency comparison to determine whether the output code bits of the interlocking system and the external system interface are as expected; The external system includes a radio block center (RBC). When automatically testing the interface code between the interlocking system and the radio block center using the automated testing method, the interface information table between the interlocking system and the radio block center is read, and the station basic information file, the station yard basic information file, and other external interface files are obtained. Using the interface information table between the interlocking system and the radio block center, for routes that utilize the RBC1, RBC2, or RBC3 protocol, the route name that interfaces with the radio block center and code information exchanged between the interlocking system and the radio block center are obtained. The code information includes the code sent by the interlocking system to the radio block center. For routes using the RBC2 protocol interface, the name of the authorized point signal is also obtained through the interface information table; When performing consistency comparison, it includes checking whether the RBC variable change status of the route / authorization point to be tested is consistent with expectations, whether the RBC variable status of other unrelated routes / authorization points of the station is not affected, and whether the TCC variable status of unrelated routes of the station is not affected. Among them, TCC refers to the train control center; The station basic information file includes interlocking tables, station signals, switches, basic attributes of sections, and directional blocking information; The basic information file of the station includes the topological connection relationship of the station and all the equipment attribute information of the station; The external interface file includes an interface information code table between the interlocking system and the trackside, an interface information table between the interlocking system and the train control center, and an interface information code table between the interlocking system and the adjacent station interlocking system.

7. The automated testing method according to claim 6, wherein: General use cases that can be recognized by the automatic test software and written in a formal programming language, including test cases corresponding to the radio block center test scenarios; Test cases applicable when the interface adopts the RBC2 protocol include scenarios such as route establishment, signal closure due to an error, normal unlocking of the positive route, manual unlocking, and section / signal / turnout equipment failure. Test cases applicable when the interface adopts the RBC1 or RBC3 protocol. The included scenarios can be used to test the changes in related variables when the RBC route status transitions between each other. The RBC route status transition relationships include: "Inactive <—> Normal", "Inactive <—> Guiding", "Unavailable -> Inactive", "In Use -> Inactive", "Normal <—> In Use", "Guided <—> Passing", "Unavailable <—> Normal", and "Unavailable <—> Guiding". In different scenarios, the test cases simulate command issuance operations by setting initial values ​​for input parameters and setting waiting times to execute interlocking rules; they also set corresponding expected values ​​of RBC interface variables as reference values ​​for consistency comparison.

8. The automated testing method according to claim 7, wherein: Automatic test software performs consistency comparison to determine whether the output code bits sent by the interlocking system to the radio block center meet expectations. If they are consistent with expectations, the test is given a pass result; otherwise, the test case is given a fail result.

9. The automated testing method according to claim 8, wherein: When the interface uses the RBC2 protocol and the authorization point has a corresponding sub-route, the consistency comparison performed includes: Traverse each route that interfaces with the RBC2 protocol and execute the test cases applicable to the RBC2 protocol to perform the following checks: Determine whether the status of the variables related to the signal authorization point corresponding to the route meets expectations; Determine whether the states of variables related to signal authorization points corresponding to all other irrelevant routes other than this route are not affected; Determine whether the TCC variables and RBC1 and RBC3 variable states of all unrelated routes are not affected; Furthermore, each route that does not use the RBC2 protocol interface is traversed, and the test cases applicable to the RBC2 protocol are executed to perform the following checks: Determine whether the states of variables related to the signal authorization points corresponding to these routes are not affected; Determine whether the states of variables related to the signal authorization points corresponding to all irrelevant routes are not affected; Determine whether the TCC variables and RBC1 and RBC3 variable states of all unrelated routes are not affected; When the interface adopts the RBC2 protocol and the authorization point has no corresponding sub-path, the consistency comparison performed is to traverse the relevant signal authorization points, execute the RBC2 interface test cases, and determine whether the variable state changes of the relevant RBC2 signal authorization points are in line with expectations; The routes that do not interface with the RBC2 protocol include routes that do not interface with the radio block center, and also include routes that interface with the radio block center using protocols other than the RBC2 protocol. Among them, irrelevant paths mean that when the executed test case has an impact on the RBC variable / TCC variable of any path, the path needs to be excluded.

10. The automated testing method according to claim 8, wherein: When the interface uses the RBC1 or RBC3 protocol, the consistency comparison performed includes: Traverse each route that interfaces with the RBC using the RBC1 or RBC3 protocol, execute the test cases applicable to the RBC1 or RBC3 protocol, and perform the following checks: Determine whether the changes in the RBC1 and RBC3 variable states related to the route are in line with expectations; Determine whether the RBC1 variable status and RBC3 variable status changes of all other unrelated routes other than this route are not affected; Determine whether the state changes of TCC variables and RBC2 variables of all unrelated routes are not affected; Traverse each route that does not use the RBC1 or RBC3 protocol interface, execute the test case applicable to the RBC1 or RBC3 protocol, and perform the following checks: Determine whether the RBC1 variable status and RBC3 variable status changes related to the route are not affected; Determine whether the RBC1 variable status and RBC3 variable status changes of all unrelated routes are not affected; Determine whether the state changes of TCC variables and RBC2 variables of all unrelated routes are not affected; Among them, routes that do not interface with the RBC1 or RBC3 protocols include routes that do not interface with the Radio Block Center, and also include routes that interface with the Radio Block Center using protocols other than RBC1 and RBC3 protocols; Among them, irrelevant paths mean that when the executed test case has an impact on the RBC variable / TCC variable of any path, the path needs to be excluded.

Images