CN-121979563-A - Version management, line acquisition and message verification method for RBC data
Abstract
A version management, line acquisition and message verification method for RBC data comprises the steps of managing the RBC data in a database according to a service dimension organization into a multi-layer tree structure, wherein the multi-layer tree structure sequentially comprises a line layer, a data version layer and an RBC equipment layer from top to bottom, each layer in the multi-layer tree structure is provided with respective attribute identifications, each layer is uniquely determined through the respective management identifications, the management identifications of each layer comprise all upper-layer attribute identifications and attribute identifications of a layer, when version updating is needed for data of a target layer, all existing data of the target layer stored in the database are matched and deleted based on the management identifications corresponding to the target layer, after the deleting operation is completed, updated data of the target layer are inserted into the database, wherein the deleting operation and the inserting operation are packaged in the same database transaction to ensure the atomicity of version updating operation, and the reliability and efficiency of data management are improved.
Inventors
- ZHANG MING
- SHI LIWEI
- ZHANG CHANGSHUAI
- MENG XIAOTONG
- CHANG YINGYING
- ZHANG JING
- LIU YI
Assignees
- 北京和利时系统工程有限公司
Dates
- Publication Date
- 20260505
- Application Date
- 20260123
Claims (10)
- 1. The RBC data version management method is characterized in that the RBC data is organized in a database according to service dimensions to be managed in a multi-layer tree structure, wherein the multi-layer tree structure sequentially comprises a line layer for marking each railway line, a data version layer for marking different versions of the RBC data in the railway line and an RBC equipment layer for marking each RBC equipment under the control of the RBC data of each version from top to bottom, each layer in the multi-layer tree structure has a respective attribute identifier, each layer is uniquely determined by the respective management identifier, and the management identifier of each layer comprises attribute identifiers of all upper layers and attribute identifiers of the layer, wherein the method comprises the following steps: When version updating is required to be carried out on the data of the target level, all the existing data of the target level stored in the database are matched and deleted based on the management identifier corresponding to the target level; after the deleting operation is completed, inserting updated data of the target level into the database; Wherein the delete operation and the insert operation are encapsulated in the same database transaction to ensure atomicity of the version-up operation.
- 2. The method of claim 1, wherein the multi-tiered tree structure further comprises, in order from top to bottom, a case version layer for a set version of test scenarios for the RBC device, and a test data layer for marking data snapshots generated by any test execution.
- 3. The method according to claim 1 or 2, characterized in that the method further comprises: When the database executes data updating operation, recording a management identifier corresponding to each operation record in an operation log of the database; And according to the management identifier corresponding to the operation record in the operation log, performing historical version tracing on any level of data in the multi-layer tree structure.
- 4. The driving license line acquisition method is characterized by comprising the following steps of: Using the set starting transponder as a calculation starting point, and circularly executing a forward extending step and a backtracking replacing step based on line data maintained by the method according to any one of claims 1 to 3 until all stations which can be reached from the starting transponder are traversed, wherein: The forward extending step is to extend the path forwards from the starting point along the driving direction according to the line data, screen all legal car receiving routes according to the port information of the station when extending to the station, and continue extending after matching the corresponding departure route for each car receiving route until the extending distance reaches the distance threshold value of the current line, so as to generate a driving permission line; backtracking and replacing the route from the end point of the current route to the route selection node of the nearest station, replacing a legal vehicle receiving route which is not traversed, and matching the legal vehicle receiving route with a corresponding departure route; And outputting all driving permission lines generated in the circulating process.
- 5. The method of claim 4, wherein the matching the corresponding departure route for each pickup route includes screening out all legal departure routes starting from the strand from the route data based on the strand identification accessed by the pickup route.
- 6. The method of claim 4, wherein the distance threshold is determined according to a route type, and the method comprises the steps of setting a first distance threshold for a positive route and a second distance threshold for a lateral route, wherein the first distance threshold is greater than the second distance threshold, and in the forward extension step, determining the route type of the current extension route in real time and applying the corresponding distance threshold.
- 7. The RBC message verification method is characterized by comprising the following steps: acquiring an actual test message and an expected message preset by a test case, which are acquired under a test scene corresponding to a driving license line, wherein the driving license line is generated based on the method of any one of claims 4 to 6; Performing field level comparison on the actual test message and the expected message, identifying a difference field, and associating the difference field with a test intention of a test case for generating the expected message to obtain an association result, wherein the test intention is used for describing what function, logic or behavior the test case is executed to check the RBC system; Classifying the difference fields in the association result based on a preset difference classification rule base, wherein the difference classification rule base predefines at least one classification of a key function field difference, a non-core configuration field difference and a format compliance difference; and according to the classification result of the difference field, acquiring and outputting the product problem investigation direction information which is matched with the classification result and determined by the test intention.
- 8. The method of claim 7, wherein the product problem-solving direction information is obtained by querying a mapping library of preset differences and problems; the mapping library of the differences and the problems stores the mapping relation between the difference characteristics, the test scene types and the potential product defect modules or the fault links, wherein the test scene types are divided according to test intention.
- 9. A storage medium having a computer program stored therein, wherein the computer program is arranged to perform the method of any of claims 1 to 8 when run.
- 10. An electronic device comprising a memory and a processor, wherein the memory has stored therein a computer program, the processor being arranged to run the computer program to perform the method of any of claims 1 to 8.
Description
Version management, line acquisition and message verification method for RBC data Technical Field The present disclosure relates to rail transit technologies, and in particular, to a method for version management, line acquisition, and message verification of RBC data. Background In a railway signaling system, a radio block center (Radio Block Center, RBC) acts as a critical train control device, the operation and testing of which relies on a series of basic data with complex correlations. These data typically exhibit multi-level, multi-version features that are difficult to manage. In the prior art, complex version association tables are relied on to record and maintain the association relationship between data items. This approach attempts to preserve the historical relevance of the data, but as versions iterate frequently, the data hierarchy increases, resulting in a dramatic increase in database storage costs. More importantly, the complex association relation is easy to be confused, inconsistent or broken in the continuous updating and maintaining process, and the data integrity and reliability are difficult to guarantee. The second scheme is to directly perform full overwrite writing on the target data at the time of version update. This approach, while simple to operate, thoroughly destroys the historical state of the data, making it impossible to trace back and reproduce any historical version. Meanwhile, in a complex multi-layer data context, the rough updating mode is extremely easy to cause data inconsistency or conflict across layers, and potential risks are brought to stable operation of the whole system. Therefore, how to manage the version of RBC data is a technical problem to be solved. Disclosure of Invention The embodiment of the application provides a RBC data version management, line acquisition and message verification method. The method for managing the version of the RBC data comprises the steps of organizing the RBC data into a multi-layer tree structure in a database according to service dimension, wherein the multi-layer tree structure sequentially comprises a line layer for marking each railway line, a data version layer for marking different versions of the RBC data in the railway line and an RBC equipment layer for marking each RBC equipment under the management of the RBC data of each version from top to bottom, each layer in the multi-layer tree structure has a respective attribute identifier, each layer is uniquely determined by the respective management identifier, and the management identifier of each layer comprises attribute identifiers of all upper layers and attribute identifiers of the layer, wherein the method comprises the following steps: When version updating is required to be carried out on the data of the target level, all the existing data of the target level stored in the database are matched and deleted based on the management identifier corresponding to the target level; after the deleting operation is completed, inserting updated data of the target level into the database; Wherein the delete operation and the insert operation are encapsulated in the same database transaction to ensure atomicity of the version-up operation. A driving license line acquisition method comprises the following steps: and circularly executing a forward extending step and a backtracking replacing step by taking the set starting transponder as a calculation starting point based on the line data maintained by the method until all stations which can be reached from the starting transponder are traversed, wherein: The forward extending step is to extend the path forwards from the starting point along the driving direction according to the line data, screen all legal car receiving routes according to the port information of the station when extending to the station, and continue extending after matching the corresponding departure route for each car receiving route until the extending distance reaches the distance threshold value of the current line, so as to generate a driving permission line; backtracking and replacing the route from the end point of the current route to the route selection node of the nearest station, replacing a legal vehicle receiving route which is not traversed, and matching the legal vehicle receiving route with a corresponding departure route; And outputting all driving permission lines generated in the circulating process. A RBC message verification method comprises the following steps: Acquiring an actual test message and an expected message preset by a test case, which are acquired under a test scene corresponding to a driving permission line, wherein the driving permission line is generated by the method; Performing field level comparison on the actual test message and the expected message, identifying a difference field, and associating the difference field with a test intention of a test case for generating the expected message to obtain an association res