A method, device, storage medium and electronic device for managing RBC data

Abstract

A method, device, storage medium and electronic device for managing RBC data. The method comprises: step 10, obtaining configuration data of RBC in a preset application scenario to obtain intermediate data; step 20, using the obtained intermediate data as current data, executing steps 21 to 23, until all the use cases to be verified are verified, and executing step 30; wherein: step 21, generating management data of different objects in each application scenario according to current data to obtain the use cases to be verified; step 22, verifying the use cases to be verified using preset benchmark data; step 23, if at least part of the use cases to be verified fail to pass the verification, updating the current data according to the benchmark data as the new current data, and continuing to execute step 21; step 24, if all the use cases to be verified pass the verification, executing step 30; step 30, generating a binary file required for RBC initialization using the current data.

Description

Technical Field

[0001] The present invention relates to data verification technology, and more particularly to a method, device, storage medium and electronic device for managing RBC data. Background Art

[0002] The Radio Block Center (RBC) is the core ground equipment of the third-generation train control system. It obtains train driving permits by comprehensively analyzing the information of physical equipment passing through the line, and then transmits them to the on-board subsystem through the train-to-ground communication channel to ensure the safe operation of all trains under its jurisdiction. The operation control of RBC equipment is based on the configuration data in the equipment, so RBC data verification has become the key to affecting the safe and efficient operation of high-speed railways.

[0003] The development and design personnel use the engineering data of the design institute as input, and generate the data required for RBC by calculating the input data. The data is presented in the created table, and then the test personnel verify and confirm the data in the table. After confirmation, the data in the table is converted into a binary file used by RBC, burned into the equipment, and system testing and verification are carried out. In the entire process, the process of converting Excel table data into binary is relatively simple, and the conversion tools are mature, so the focus of testing and verification is on the intermediate table data verification link in the intermediate process. In actual applications, the processing efficiency of the intermediate table data verification link is low. Summary of the invention

[0004] Embodiments of the present application provide a method, device, storage medium, and electronic device for managing RBC data.

[0005] A method for managing RBC data, comprising: Step 10: Acquire the configuration data of the RBC in a preset application scenario to obtain intermediate data, wherein the configuration data is used to generate the management data of the RBC for other objects in the railway train system; Step 20: Use the obtained intermediate data as the current data and execute steps 21 to 23 until all the use cases to be verified pass the verification, and then execute step 30; wherein: Step 21: Generate management data of different objects in each application scenario based on current data to obtain a use case to be verified; Step 22: Verify the use case to be verified using preset benchmark data; Step 23: If at least part of the use cases to be verified fail to pass the verification, the current data is updated according to the benchmark data as new current data, and step 21 is continued; Step 24: If all the test cases to be verified pass the verification, execute step 30; Step 30: Generate a binary file required for RBC initialization using the current data.

[0006] A RBC data management device includes an acquisition module, a verification module and a generation module, wherein: The acquisition module is configured to acquire configuration data of the RBC in a preset application scenario to obtain intermediate data, wherein the configuration data is used to generate management data of the RBC for other objects in the railway train system; The verification module is used to use the obtained intermediate data as the current data and execute steps 21 to 23 until all the use cases to be verified pass the verification, thereby triggering the generation module to perform operations; wherein: Step 21: Generate management data of different objects in each application scenario based on current data to obtain a use case to be verified; Step 22: Verify the use case to be verified using preset benchmark data; Step 23: If at least part of the use cases to be verified fail to pass the verification, the current data is updated according to the benchmark data as new current data, and step 21 is continued; The generation module is configured to use current data to generate a binary file required for RBC initialization.

[0007] A storage medium stores a computer program, wherein the computer program is configured to execute the method described above when running.

[0008] An electronic device comprises a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the method described above.

[0009] In the embodiment of the present application, the configuration data of RBC in a preset application scenario is obtained to generate intermediate data, and the intermediate data is automatically verified, thereby significantly improving the processing efficiency of data verification; management data of different objects in each application scenario is generated to obtain use cases to be verified, so that the use cases to be verified can cover the management data corresponding to different objects in each application scenario, so that the use cases to be verified include the management content corresponding to different objects in each application scenario, the management content, the communication port used for transmission of the management content, and the data format of the message carrying the content, thereby achieving full coverage of core data and improving the coverage rate of data verification; by using benchmark data to verify the use cases to be verified, and updating the current data according to the benchmark data when some use cases fail, the security and reliability of the intermediate data can be enhanced, and the accuracy of the binary file can be effectively improved.

[0010] Other features and advantages of the present application will be described in the following description, and partly become apparent from the description, or be understood by implementing the present application. Other advantages of the present application can be realized and obtained by the schemes described in the description and the drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The accompanying drawings are used to provide an understanding of the technical solution of the present application and constitute a part of the specification. Together with the embodiments of the present application, they are used to explain the technical solution of the present application and do not constitute a limitation on the technical solution of the present application.

[0012] Figure 1 A flowchart of a method for managing RBC data provided in an embodiment of the present application; Figure 2 A schematic diagram of the structure of the RBC data management device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0013] The present application describes multiple embodiments, but the description is exemplary rather than restrictive, and it is obvious to those skilled in the art that there may be more embodiments and implementations within the scope of the embodiments described in the present application. Although many possible feature combinations are shown in the drawings and discussed in the specific embodiments, many other combinations of the disclosed features are also possible. Unless specifically limited, any feature or element of any embodiment may be used in combination with any other feature or element in any other embodiment, or may replace any other feature or element in any other embodiment.

[0014] The present application includes and contemplates combinations of features and elements known to those of ordinary skill in the art. The embodiments, features and elements disclosed in the present application may also be combined with any conventional features or elements to form a unique invention scheme. Any features or elements of any embodiment may also be combined with features or elements from other invention schemes to form another unique invention scheme. Therefore, it should be understood that any feature shown and / or discussed in the present application may be implemented individually or in any appropriate combination. Therefore, except for the limitations made according to the attached claims and their equivalents, the embodiments are not subject to other restrictions. In addition, various modifications and changes may be made within the scope of protection of the attached claims.

[0015] In addition, when describing representative embodiments, the specification may have presented the method and / or process as a specific sequence of steps. However, to the extent that the method or process does not rely on the specific order of the steps described herein, the method or process should not be limited to the steps of the specific order described. As will be understood by those of ordinary skill in the art, other sequences of steps are also possible. Therefore, the specific sequence of the steps set forth in the specification should not be interpreted as a limitation to the claims. In addition, the claims for the method and / or process should not be limited to the steps of performing them in the order written, and those skilled in the art can easily understand that these sequences can be changed and still remain within the spirit and scope of the embodiments of the present application.

[0016] In the process of implementing this application, it was found that the verification of intermediate process data had the following problems: The previous verification method relied on manual judgment and identification, and required the consultation of various table data during the verification process. It involved multiple modules, objects, and fields, had a large amount of calculation, a long testing cycle, and was prone to missed tests and wrong tests.

[0017] Based on the above analysis, this application proposes the following solutions, including: Figure 1 Schematic diagram of the process of managing RBC data provided in the embodiment of the present application. Figure 1 As shown, the method includes:

[0018] Step 10: Acquire the configuration data of the RBC in a preset application scenario to obtain intermediate data, wherein the configuration data is used to generate the management data of the RBC for other objects in the railway train system; Among them, other objects in the railway train system can be balises, signal machines, routes, stations, track sections, driving permits, lines, etc.; application scenarios include driving permits, grade conversions, boundary transfers, etc.; The configuration data includes the generated management content, the communication port used for transmission of the management content, and the data format of the message carrying the content.

[0019] Step 20: Use the obtained intermediate data as the current data and execute steps 21 to 23 until all the use cases to be verified pass the verification, and then execute step 30; wherein: Step 21: Generate management data of different objects in each application scenario based on current data to obtain a use case to be verified; The use cases to be verified cover the management data corresponding to different objects in each application scenario, including management content, communication ports and message data formats, achieving comprehensive coverage of core data.

[0020] Step 22: Verify the use case to be verified using preset benchmark data; The benchmark data includes engineering data, configuration data of each RBC communication interface and data in the RBC message database, and the access permission of the benchmark data is set to read-only; Among them, the engineering data is used to verify the management content in the use case to be verified; the configuration data of each communication interface in the RBC is used to verify the interface used by the use case to be verified, and the data in the RBC message database is used to verify the data format of the use case to be verified.

[0021] The engineering data may be data of basic physical equipment of railway train routes, such as balise location table, signal machine data table, information table of each station under jurisdiction, station approach information table, turnout information table, line change turnout table, etc.; Among them, the configuration data of each communication interface in the RBC may be interface data with the dispatching centralized system, interlocking equipment, speed limit server, etc.; The data in the RBC message database is the data for information exchange with other devices.

[0022] The above-mentioned benchmark data is used to verify the use cases to be verified, thus achieving comprehensive verification of the core data of the entire device.

[0023] Among them, by setting the access permission of the benchmark data to read-only, it can be ensured that the content of the benchmark data is not tampered with, and the originality and integrity of the data content are guaranteed.

[0024] Step 23: If at least part of the use cases to be verified fail to pass the verification, the current data is updated according to the benchmark data as new current data, and step 21 is continued; The above update operation can be automatically corrected, or manually corrected by outputting an alarm message.

[0025] Step 30: Generate a binary file required for RBC initialization using the current data; Since the current data has been verified, the accuracy of the data content is guaranteed. Using the data to generate a binary file as the RBC initialization file can effectively ensure the accuracy of the data content.

[0026] The method provided in the embodiment of the present application obtains the configuration data of RBC in a preset application scenario to generate intermediate data, and automatically verifies this data, thereby significantly improving the processing efficiency of data verification; generates management data of different objects in each application scenario, and obtains use cases to be verified, so that the use cases to be verified can cover the management data corresponding to different objects in each application scenario, so that the use cases to be verified include the management content corresponding to different objects in each application scenario, the management content, the communication port used for transmission of the management content, and the data format of the message carrying the content, thereby achieving full coverage of core data and improving the coverage rate of data verification; by using benchmark data to verify the use cases to be verified, and updating the current data according to the benchmark data when some use cases fail, the security and reliability of the intermediate data can be enhanced, and the accuracy of the binary file can be effectively improved.

[0027] The method provided in the embodiment of the present application is described below: In an exemplary embodiment, an RBC message database and an intermediate table database are provided, wherein the intermediate table database is used to store intermediate data.

[0028] The RBC message database is mainly responsible for storing message data. Usually, no modification of the data in the database is allowed to ensure the originality and integrity of the data. As a newly added database, the intermediate table database has the ability to obtain and update data, which greatly enhances the flexibility of data processing.

[0029] In view of the characteristics and requirements of these two databases, this application adopts differentiated control methods: For the RBC message database, the existing data structure is used to generate the data format required by the use case to be verified, and the effective reading of the message data is achieved by associating the selected message use case with different use cases to be verified. At the same time, in order to strictly protect the integrity of the message data, the database permission is set to read-only, and deletion and writing operations are prohibited, effectively preventing data damage caused by misoperation or malicious attacks.

[0030] For the intermediate table database, read and write operations are allowed through customized data structures and program codes, so that it can flexibly handle various data operation requirements.

[0031] In the above exemplary embodiment, the composite design pattern is used to operate the two databases, which can realize data operations more efficiently and specifically; the above control method not only gives full play to the advantages of each database, but also realizes the maximum utilization of data resources, laying a solid foundation for the performance improvement and function expansion of data verification tools.

[0032] When a read operation is received for an object in the RBC message database, a judgment logic flow is triggered, wherein the judgment logic flow includes: verifying whether the account initiating the operation has the corresponding management authority. If the account does have management authority, the system executes the read operation in the request.

[0033] When a modification request for an intermediate table database object is received from the user interface, adaptive processing is required based on the specific situation.

[0034] Specifically, after receiving a user's request to update current data, the user's management authority is obtained; when the user's management authority meets the preset authority conditions, the object operated by the update request is obtained; when it is detected that the object is in the list of objects allowed to be updated, the update request is responded to.

[0035] Since the update operation may include adding, deleting or changing the functional object, for the data verification link of the intermediate table, some objects play a vital role in the test process or historical records. As key element data, their accuracy and integrity are not allowed to be tampered with at will. Therefore, in an embodiment of the present application, the modification authority of the object has strict restrictions. Only when the operating account has management authority, it is allowed to perform the modification operation, thereby ensuring that the accuracy and security of the functional object are guaranteed to the greatest extent, and effectively avoiding the potential risks caused by misoperation or malicious tampering.

[0036] For complex scenarios such as station tracks, especially for complex tracks such as siding track 3G, it can be flexibly subdivided into multiple sections such as "3G1", "3G2" and "3G3" to meet different verification needs. Among them, in rail transit, station tracks usually refer to the track facilities inside the station; siding track 3G refers to the down-going siding track numbered 3, which is one of the tracks for train parking in the station, specifically located at the third position in the down direction.

[0037] In addition, other scenarios with complex station roads include: Marshalling yard: Specialized in the marshaling and dismantling of trains, as well as other technical operations on vehicles and trains, equipped with facilities such as locomotive depot and vehicle depot, arrival and departure lines, shunting lines, draw-out lines and humps.

[0038] Section station: A station located at the boundary of the traction section, mainly engaged in train technical inspection, locomotive replacement, section-side detachment and coupling of trains and reorganization of small operating trains, etc.

[0039] The use case to be verified may require different verification schemes depending on the line or station. You can use the overall track name (such as 3G) for verification, or subdivide the track into independent device entity names (such as "3G1", "3G2", "3G3") for separate verification. Before performing the verification comparison, this application will comprehensively traverse and search for the entity names of the use case to be verified, obtain its naming rules, and automatically calculate and judge the match with the content of the use case to be verified.

[0040] In view of the above scenario, this application proposes the following solutions, including: In an exemplary embodiment, the verifying the use case to be verified by using preset benchmark data includes: For each use case to be verified, the following operations are performed, including: Obtain the naming rules of the entities in the current use case to be verified in the benchmark data; Determine the naming information of the entity in the current use case to be verified in the benchmark data according to the naming rule, and obtain the search keyword; Using the search keyword to obtain benchmark data matching the current use case to be verified in the benchmark data; The matched benchmark data is used to verify the current use case to be verified, and a verification result of the current use case to be verified is obtained.

[0041] The verification process of the 3G track is divided into the following steps, and how to apply the above method is explained in detail: Step A1, obtaining the naming rule of track 3G; The naming rules may include the numbering method of the track (such as 3G, 3G1, 3G2, etc.); or, whether the track name contains a specific prefix or suffix; or, the number of digits and the range of digits in the track number.

[0042] Step A2, determining the naming information of track 3G; According to the obtained naming rules, determine the naming information of track 3G in the benchmark data. For example, if 3G is an overall track name, use it as the search keyword. If 3G can be subdivided into independent equipment entity names such as 3G1, 3G2, and 3G3, then it is necessary to determine the rules for these subdivided names.

[0043] Step A3, generating search keywords for Stock Track 3G; Using the determined naming information, generate search keywords. For track 3G, the search keywords may be: "3G" (when used as a whole track); "3G1", "3G2", "3G3" (when used as independent equipment entities).

[0044] Step A4: obtaining matching benchmark data; Use the search keywords to find data matching Stock Channel 3G in the benchmark data.

[0045] Step A5: Verify the use case to be verified; The matched benchmark data is used to verify the use cases to be verified for Track 3G.

[0046] Through the above steps, the verification process of track 3G can be ensured to be comprehensive and accurate, thereby improving the safety and reliability of the rail transit system.

[0047] In addition, the names of the fields in the use case to be verified may be inconsistent with the fields in each entity table. For example, when the track section entity crosses the train control jurisdiction boundary, the same block section may correspond to different station names, or the information of the same section in the signal and interlocking interface entities may be inconsistent.

[0048] For example, a large railway hub such as HZ East Station contains multiple yards, such as HH Chang Yard and NH Yong Yard, which are governed by different RBCs. When a train moves from one yard to another in the hub, it will pass through the jurisdiction of different RBCs.

[0049] When the train departs from HH Changchang of HZ East Station, since HH Changchang is governed by RBC1, the train is recorded as "HH Changchang" in the system of RBC1; when the train moves to NH Yongchang, this yard is governed by RBC2, and in the system of RBC2, the same location may be recorded as "NH Yongchang". Although the train is actually at the same geographical location, due to the different RBCs, the same track section entity may have different names in different RBC systems.

[0050] At HZ East Station, a specific track section may be identified as "1G" in the signal entity to control the train route. The same track section may require a more detailed identification in the interlocking interface entity, such as "HH Changchang 1G" to indicate that the section belongs to HH Changchang, to indicate that this section is part of HH Changchang. Although the trains are actually at the same geographical location, the station information in the signal entity and the interlocking interface entity is inconsistent.

[0051] The above situation may result in different names for the same entity in the benchmark data, which may result in the inability to find matching benchmark data. To solve the above technical problems, this application proposes the following solutions, including:

[0052] In an exemplary embodiment, the step of using the search keyword to obtain benchmark data matching the current use case to be verified from the benchmark data includes: When the first name of the first entity and the second name of the second entity are used as search keywords to obtain the benchmark data, if the benchmark data is not found, the following operations are performed: Using the name of the first entity as a search keyword to query the name of the second entity, and obtain candidate names; Determining whether the object corresponding to the candidate name and the object corresponding to the second name belong to the same main station; When it is determined that they belong to the same master station, determining whether the deployment areas where the object corresponding to the candidate name and the object corresponding to the second name are located are located in adjacent positions of a TCC (Train Control Center) jurisdiction boundary; If it is determined that the location is adjacent to the TCC jurisdiction boundary, the second name in the search keyword is updated to the candidate name as the updated search keyword; The updated search keyword is used to obtain benchmark data that matches the current use case to be verified.

[0053] Taking the track section as an example, first, the section name and station name will be matched; if the match fails, only the section name will be matched; if there are multiple matching station information, the signal entity data will be introduced as a constraint to further check whether the two stations are adjacent and whether there are disputed entities in their adjacent positions. In this way, the use case to be verified can be accurately found and subsequent verification operations can be continued. The specific steps are as follows:

[0054] Step B1: Preliminary matching: In the signal table, the corresponding signal entity was searched by matching the station name "DT South Station" and the track section name "XA1LQG" as search keywords, but no match was found successfully.

[0055] Step B2: Match based on segment name only: Since the initial matching failed, only the track section name "XA1LQG" was used for matching, and XA1LQG corresponding to the DT South train operation was found in the signal table.

[0056] Step B3: Station information matching: Use the station information table to determine whether DT South EMU Operation Depot and DT South Station belong to the same main station. The result is that they belong to the same main station.

[0057] Step B4: Determination of TCC jurisdiction boundaries: Further determine whether DT South EMU Operation Center and DT South Station are located in adjacent locations of the TCC jurisdiction boundary. By analyzing the station information table and TCC jurisdiction boundary data, it is confirmed that the two stations are indeed located in adjacent locations.

[0058] Step B5: Update search keywords: Based on the above information, the "DT South Station" in the benchmark data is updated to "DT South EMU Operation Station" as the new search keyword.

[0059] Step B6: Rematch: In the signal table, the updated search keywords "DT South EMU Operation Station" and track section "XA1LQG" were used for matching, and the corresponding signal entity was successfully matched.

[0060] By integrating the data of the signal table, interlocking interface table and station information table, a closed-loop verification process is formed to ensure the accuracy and completeness of the verification process. The above method is not only applicable to the verification of track sections, but also to the verification of signal machines and interlocking interface equipment, and the processing methods are similar.

[0061] In an exemplary embodiment, an auxiliary table is pre-stored, wherein the auxiliary table includes an ID for uniquely identifying an entity, a custom parameter name, and a custom instruction; The step of generating management data of different objects in each application scenario according to current data to obtain a use case to be verified includes: Using the auxiliary table to generate management data of different objects in each application scenario according to current data, to obtain a use case to be verified; The method of verifying the use case to be verified by using preset benchmark data includes: Utilizing the auxiliary table, parsing the content of the use case to be verified to obtain a parsing result; The analytical result is verified using the benchmark data to obtain a verification result.

[0062] For fields in the use case to be verified that do not require automatic generation tools or are non-core, auxiliary tables can be used to process them. For example, they can be directly used as use case content, or used to assist use case generation and verify the use case to be verified.

[0063] For example, the names of parameters are usually fixed and do not need to be dynamically generated, so they can be directly imported from auxiliary tables. For example, the device ID field does not carry actual business logic meaning, but only serves as an identifier to distinguish entities of the same type. Since the tool cannot directly calculate the device ID based on logic, it can be directly read and applied from the data to be tested.

[0064] In this solution, the auxiliary table template is designed to be flexible and efficient, allowing necessary format adjustments based on the data to be tested. At the same time, to ensure the accuracy and independence of use case generation, the system will fine-tune the existing data template to be tested, retaining only the fields that are critical to the current use case generation and discarding all irrelevant information.

[0065] In addition, a key constraint is added during the use case data generation phase: autonomous introduction of auxiliary data is prohibited to avoid potential data interference from the source. Only during the comparison and verification phase, when the tool automatically recognizes that it has entered this specific phase, will the system be allowed to read and apply auxiliary data.

[0066] Based on the above description, it can be seen that using auxiliary tables for data management not only enriches the use case content and comparison and verification methods, but also reduces the risk of over-reliance on auxiliary data through carefully designed mechanisms and constraints, ensuring the robustness and accuracy of the testing process.

[0067] Figure 2 This is a schematic diagram of the structure of the RBC data management device provided in the embodiment of the present application. Figure 2 As shown, the device includes an acquisition module 201, a verification module 202 and a generation module 203, wherein:

[0068] The acquisition module 201 is configured to acquire configuration data of the RBC in a preset application scenario to obtain intermediate data, wherein the configuration data is used to generate management data of the RBC for other objects in the railway train system; The verification module 202 is used to use the obtained intermediate data as the current data, and execute steps 21 to 23 until all the use cases to be verified pass the verification, thereby triggering the generation module to perform operations; wherein: Step 21: Generate management data of different objects in each application scenario based on current data to obtain a use case to be verified; Step 22: Verify the use case to be verified using preset benchmark data; Step 23: If at least part of the use cases to be verified fail to pass the verification, the current data is updated according to the benchmark data as new current data, and step 21 is continued; The generating module 203 is configured to generate a binary file required for RBC initialization using current data.

[0069] The device provided in the embodiment of the present application obtains the configuration data of RBC in a preset application scenario to generate intermediate data, and automatically verifies this data, thereby significantly improving the processing efficiency of data verification; generates management data of different objects in each application scenario, and obtains use cases to be verified, so that the use cases to be verified can cover the management data corresponding to different objects in each application scenario, so that the use cases to be verified include the management content corresponding to different objects in each application scenario, the management content, the communication port used for transmission of the management content, and the data format of the message carrying the content, thereby achieving full coverage of core data and improving the coverage rate of data verification; by using benchmark data to verify the use cases to be verified, and updating the current data according to the benchmark data when some use cases fail, the security and reliability of the intermediate data can be enhanced, and the accuracy of the binary file can be effectively improved.

[0070] An embodiment of the present application provides a storage medium, in which a computer program is stored, wherein the computer program is configured to execute the method described above when running.

[0071] An embodiment of the present application provides an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the method described above.

[0072] It will be appreciated by those skilled in the art that all or some of the steps, systems, and functional modules / units in the methods disclosed above may be implemented as software, firmware, hardware, and appropriate combinations thereof. In hardware implementations, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed by several physical components in cooperation. Some or all components may be implemented as software executed by a processor, such as a digital signal processor or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or non-transitory medium) and a communication medium (or transient medium). As is known to those skilled in the art, the term "computer storage medium" includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer. In addition, it is well known to those skilled in the art that communication media typically contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

Claims

1. A method for managing RBC data, characterized in that: include: Step 10: Acquire the configuration data of the RBC in a preset application scenario to obtain intermediate data, wherein the configuration data is used to generate the management data of the RBC for other objects in the railway train system; Step 20: Use the obtained intermediate data as the current data and execute steps 21 to 23 until all the use cases to be verified pass the verification, and then execute step 30; wherein: Step 21: Generate management data of different objects in each application scenario based on current data to obtain a use case to be verified; Step 22: Verify the use case to be verified using preset benchmark data; Step 23: If at least part of the use cases to be verified fail to pass the verification, the current data is updated according to the benchmark data as new current data, and step 21 is continued; Step 24: If all the test cases to be verified pass the verification, execute step 30; Step 30: Generate a binary file required for RBC initialization using the current data.

2. The method according to claim 1, characterized in that: The benchmark data includes the engineering data, the configuration data of each communication interface in the RBC, and the data in the RBC message database, wherein the access right of the benchmark data is read-only; Among them, the engineering data is used to verify the management content in the use case to be verified; the configuration data of each communication interface in the RBC is used to verify the interface used by the use case to be verified, and the data in the RBC message database is used to verify the data format of the use case to be verified.

3. The method according to claim 1, characterized in that The updating of the current data according to the reference data comprises: After receiving a user's request to update current data, obtaining the user's management authority; When the management authority of the user meets the preset authority condition, obtaining the object operated by the update request; When it is detected that the object is in the list of objects allowed to be updated, the update request is responded to.

4. The method according to claim 1, characterized in that: The verifying the use case to be verified by using preset benchmark data includes: For each use case to be verified, the following operations are performed, including: Obtain the naming rules of the entities in the current use case to be verified in the benchmark data; Determine the naming information of the entity in the current use case to be verified in the benchmark data according to the naming rule, and obtain the search keyword; Using the search keyword to obtain benchmark data matching the current use case to be verified in the benchmark data; The matched benchmark data is used to verify the current use case to be verified, and a verification result of the current use case to be verified is obtained.

5. The method according to claim 4, characterized in that The step of using the search keyword to obtain benchmark data matching the current use case to be verified from the benchmark data includes: When the first name of the first entity and the second name of the second entity are used as search keywords to obtain the benchmark data, if the benchmark data is not found, the following operations are performed: Using the name of the first entity as a search keyword to query the name of the second entity, and obtain candidate names; Determining whether the object corresponding to the candidate name and the object corresponding to the second name belong to the same main station; When it is determined that they belong to the same master station, determining whether the deployment areas where the object corresponding to the candidate name and the object corresponding to the second name are located are located in adjacent locations of the TCC jurisdiction boundary; If it is determined that the location is adjacent to the TCC jurisdiction boundary, the second name in the search keyword is updated to the candidate name as the updated search keyword; Use the updated search keywords to obtain benchmark data that matches the current use case to be verified.

6. The method according to claim 5, characterized in that: The second entity is a track section or a signal machine or an interlocking interface device.

7. The method according to claim 1, characterized in that: An auxiliary table is pre-stored, wherein the auxiliary table includes an ID for uniquely identifying an entity, a custom parameter name, and a custom instruction; The step of generating management data of different objects in each application scenario according to current data to obtain a use case to be verified includes: Using the auxiliary table to generate management data of different objects in each application scenario according to current data, to obtain a use case to be verified; The method of verifying the use case to be verified by using preset benchmark data includes: Utilizing the auxiliary table, parsing the content of the use case to be verified to obtain a parsing result; The analytical result is verified using the benchmark data to obtain a verification result.

8. A RBC data management device, characterized in that: It includes acquisition module, verification module and generation module, among which: The acquisition module is configured to acquire configuration data of the RBC in a preset application scenario to obtain intermediate data, wherein the configuration data is used to generate management data of the RBC for other objects in the railway train system; The verification module is used to use the obtained intermediate data as the current data and execute steps 21 to 23 until all the use cases to be verified pass the verification, thereby triggering the generation module to perform operations; wherein: Step 21: Generate management data of different objects in each application scenario based on current data to obtain a use case to be verified; Step 22: Verify the use case to be verified using preset benchmark data; Step 23: If at least part of the use cases to be verified fail to pass the verification, the current data is updated according to the benchmark data as new current data, and step 21 is continued; The generation module is configured to use current data to generate a binary file required for RBC initialization.

9. A storage medium, characterized in that: The storage medium stores a computer program, wherein the computer program is configured to execute the method according to any one of claims 1 to 7 when executed.

10. An electronic device comprising a memory and a processor, characterized in that: A computer program is stored in the memory, and the processor is configured to run the computer program to perform the method according to any one of claims 1 to 7.

Images