An automated method and apparatus for testing a temporary speed limit information package

Abstract

This application discloses an automated testing method and apparatus for temporary speed limit information packets, relating to the field of train testing technology. Its main objective is to achieve efficient, accurate, and repeatable testing of temporary speed limit information packets. The technical solution is as follows: First, transponder information and temporary speed limit information are acquired. Second, the transponder information and temporary speed limit information are input into a real test environment to obtain actual CTCS-2 level speed limit parameters. The real test environment is used to control the train dispatching centralized system simulator to send temporary speed limit commands to the temporary speed limit server, triggering the temporary speed limit server to generate actual CTCS-2 level speed limit parameters. Third, the transponder information and temporary speed limit information are input into a theoretical calculation engine to obtain expected CTCS-2 level speed limit parameters. The theoretical calculation engine is used to perform differentiated calculations of expected CTCS-2 level speed limit parameters for different temporary speed limit scenarios in a base coordinate system. Fourth, based on the comparison results between the actual CTCS-2 level speed limit parameters and the expected CTCS-2 level speed limit parameters, the temporary speed limit information packet is verified to have passed the test.

Description

Technical Field

[0001] This application relates to the field of train testing technology, and in particular to an automated testing method and apparatus for temporary speed limit information packets. Background Technology

[0002] In the field of rail transit signal control, the reliability of the interaction between the Temporary Speed ​​Limit Server (TSRS) and the Automatic Train Operation (ATO) system is directly related to train operation safety. The CTCS-2 Temporary Speed ​​Limit Information Packet (included in the ETCS-44 message packet) is the core carrier for the TSRS to transmit speed limit instructions to the train. Its content must accurately reflect the speed limit location, length, and speed value within the transponder's jurisdiction. With the increasing complexity of high-speed rail networks, scenarios such as mixed multi-kilometer standards, frequent link breaks, and overlapping speed limit sections are proliferating, placing higher demands on the verification of the CTCS-2 level temporary speed limit information packet.

[0003] Currently, existing testing methods mainly fall into two categories: manual verification and automated testing. Manual verification requires testers to manually calculate speed limit parameters at different resolutions, especially for overlapping speed limits, which necessitates segment-by-segment calculation, resulting in low efficiency and a high error rate. Automated testing tools, on the other hand, only support single-kilometer speed limit verification within a single kilometer scale, failing to cover complex scenarios such as chain break compensation, multi-kilometer scale conversion, and double-rounding overlap. This leads to low test coverage and weak generalization ability in complex scenarios, thus affecting testing efficiency and accuracy. Therefore, an automated testing method for temporary speed limit information packets is urgently needed to address the significant shortcomings of the aforementioned testing methods. Summary of the Invention

[0004] In view of the above problems, this application provides an automated testing method and apparatus for temporary speed limit information packets, the main purpose of which is to achieve efficient, accurate and repeatable testing of temporary speed limit information packets.

[0005] To solve the above-mentioned technical problems, this application proposes the following solution: Firstly, this application provides an automated testing method for temporary speed limit information packets, the method comprising: Acquire transponder information and temporary speed limit information. The transponder information includes at least the jurisdiction of the transponder and the endpoint location corresponding to the jurisdiction. The temporary speed limit information includes at least the endpoint location, speed limit value and resolution corresponding to the speed limit section within the jurisdiction. The transponder information and the temporary speed limit information are input into the real test environment to obtain the actual CTCS-2 level speed limit parameters. The real test environment is used to control the train dispatching centralized system simulator to send temporary speed limit commands to the temporary speed limit server to trigger the temporary speed limit server to generate the actual CTCS-2 level speed limit parameters. The transponder information and the temporary speed limit information are input into the theoretical calculation engine to obtain the expected CTCS-2 level speed limit parameters. The theoretical calculation engine is used to perform differentiated calculations of the expected CTCS-2 level speed limit parameters for different temporary speed limit scenarios in the base coordinate system. Based on the comparison results between the actual CTCS-2 level speed limit parameters and the expected CTCS-2 level speed limit parameters, verify whether the temporary speed limit information package passes the test.

[0006] Secondly, this application provides an automated testing device for temporary speed limit information packets, the device comprising: An acquisition unit is used to acquire transponder information and temporary speed limit information. The transponder information includes at least the jurisdiction of the transponder and the endpoint position corresponding to the jurisdiction. The temporary speed limit information includes at least the endpoint position, speed limit value and resolution corresponding to the speed limit section within the jurisdiction. The test unit is used to input the transponder information and the temporary speed limit information obtained by the acquisition unit into the real test environment to obtain the actual CTCS-2 level speed limit parameters. The real test environment is used to control the train dispatching centralized system simulator to send a temporary speed limit command to the temporary speed limit server real machine to trigger the temporary speed limit server real machine to generate the actual CTCS-2 level speed limit parameters. The calculation unit is used to input the transponder information and the temporary speed limit information obtained by the acquisition unit into the theoretical calculation engine to obtain the expected CTCS-2 level speed limit parameters. The theoretical calculation engine is used to perform differentiated calculations of the expected CTCS-2 level speed limit parameters for different temporary speed limit scenarios in the base coordinate system. The verification unit is used to verify whether the temporary speed limit information package passes the test based on the comparison results between the actual CTCS-2 level speed limit parameters obtained by the test unit and the expected CTCS-2 level speed limit parameters obtained by the calculation unit.

[0007] To achieve the above objectives, according to a third aspect of this application, a storage medium is provided, the storage medium including a stored program, wherein, when the program is executed, the device where the storage medium is located is controlled to perform the automated testing method for the temporary rate limit information packet of the first aspect.

[0008] To achieve the above objectives, according to a fourth aspect of this application, a processor is provided for running a program, wherein the program executes the automated testing method for the temporary rate limit information packet of the first aspect.

[0009] Using the above technical solution, this application provides an automated testing method and apparatus for temporary speed limit information packets. First, transponder information and temporary speed limit information are acquired. The transponder information includes at least the transponder's jurisdiction and the corresponding endpoint positions. The temporary speed limit information includes at least the endpoint positions, speed limit values, and resolutions of the speed limit sections within the jurisdiction. Next, the transponder information and temporary speed limit information are input into a real test environment to obtain actual CTCS-2 level speed limit parameters. The real test environment is used to control the train dispatching centralized system simulator to send temporary speed limit commands to the temporary speed limit server, triggering the temporary speed limit server to generate actual CTCS-2 level speed limit parameters. Then, the transponder information and temporary speed limit information are input into a theoretical calculation engine to obtain expected CTCS-2 level speed limit parameters. The theoretical calculation engine is used to perform differentiated calculations of expected CTCS-2 level speed limit parameters for different temporary speed limit scenarios in a base coordinate system. Finally, based on the comparison results between the actual CTCS-2 level speed limit parameters and the expected CTCS-2 level speed limit parameters, the temporary speed limit information packet is verified to have passed the test. The technical solution provided in this application allows for the acquisition of transponder information including the transponder's jurisdiction and endpoint location, and temporary speed limit information including the endpoint location of the speed-limited section, speed limit value, and resolution. These two information are then input into a real test environment consisting of a train dispatching centralized system simulator and a temporary speed limit server simulator to obtain actual CTCS-2 level speed limit parameters. Additionally, a theoretical calculation engine capable of differentiated calculations for different temporary speed limit scenarios in a base coordinate system is input to obtain temporary CTCS-2 level speed limit parameters. Finally, the temporary speed limit information packet is verified by comparing the two types of parameters to determine whether it passes the test, thereby achieving efficient, accurate, and repeatable testing of the temporary speed limit information packet.

[0010] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description

[0011] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings: Figure 1 A flowchart illustrating an automated testing method for a temporary speed limit information packet provided in an embodiment of this application is shown. Figure 2 This illustration shows a block diagram of an automated testing device for a temporary speed limit information packet provided in an embodiment of this application. Figure 3 A block diagram of an automated testing apparatus for another temporary speed limit information packet provided in an embodiment of this application is shown. Detailed Implementation

[0012] Exemplary embodiments of the present application will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present application are shown in the drawings, it should be understood that the present application may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this application will be thorough and complete, and will fully convey the scope of the present application to those skilled in the art.

[0013] Currently, existing testing solutions for temporary speed limit information packets mainly fall into two categories: manual verification and automated testing. Manual verification requires testers to manually calculate speed limit parameters at different resolutions, especially for overlapping speed limits, which necessitates segment-by-segment calculation, resulting in low efficiency and a high error rate. Automated testing tools, on the other hand, only support single-kilometer speed limit verification within a single kilometer scale, failing to cover complex scenarios such as chain break compensation, multi-kilometer scale conversion, and double-rounding overlap. This leads to low test coverage and weak generalization ability in complex scenarios, thus affecting testing efficiency and accuracy.

[0014] In-depth research revealed that transponder information and temporary speed limit information can be input into a real test environment consisting of a train dispatching centralized system simulator and a temporary speed limit server simulator, respectively, to obtain actual CTCS-2 level speed limit parameters. On the other hand, the parameters can be input into a theoretical calculation engine to obtain the desired CTCS-2 level speed limit parameters. This theoretical calculation engine performs differentiated calculations based on the base kilometer system for scenarios with single speed limits, multiple speed limits, and different resolutions. The consistency of the two results can be compared to achieve efficient, accurate, and repeatable testing of temporary speed limit information packets.

[0015] Therefore, this application provides an automated testing method for temporary speed limit information packets. This method enables efficient, accurate, and repeatable testing of temporary speed limit information packets. The specific execution steps are as follows: Figure 1 As shown, it includes: 101. Obtain transponder information and temporary speed limit information.

[0016] The transponder information includes at least the jurisdiction of the transponder and the endpoint location corresponding to the jurisdiction, and the temporary speed limit information includes at least the endpoint location, speed limit value and resolution corresponding to the speed limit section within the jurisdiction.

[0017] In this step, the transponder information, jurisdiction area, and endpoint locations are entered in kilometer markers, for example, "Jurisdiction start point: K1+000, jurisdiction end point: K1+500" (endpoint locations are K1+000 and K1+500, corresponding to the actual mileage coordinates of the line). In addition, transponder information includes basic identifiers, chain break status, and transponder direction. Basic identifiers include the transponder number (e.g., "B1") and the line it belongs to (e.g., "Beijing-Shanghai High-Speed ​​Railway Beijing Section"); chain break status involves supplementing the information on chain breaks within the jurisdiction, for example, "Chain break location: K1+200, chain break type: long chain, chain break length: 50m"; transponder direction is "along the positive direction of the line" or "along the negative direction of the line" (e.g., if transponder B1 is selected as "along the positive direction of the line," the endpoint order will be determined by the positive direction when calculating speed limits that overlap with the jurisdiction area).

[0018] Regarding temporary speed limit information, the speed limit section refers to the specific mileage coordinates of the physical section where the temporary speed limit is in effect within the transponder's jurisdiction, expressed in kilometer markers, including the start and end points of the speed limit section. The speed limit value refers to the maximum operating speed that trains must adhere to within the temporary speed limit section. Resolution refers to the measurement accuracy of distance and length parameters in the temporary speed limit information packet, which is typically 1m or 10m.

[0019] 102. Input the transponder information and temporary speed limit information into the actual test environment to obtain the actual CTCS-2 level speed limit parameters.

[0020] The real test environment is used to control the train dispatching centralized system simulator to send temporary speed limit commands to the temporary speed limit server, so as to trigger the temporary speed limit server to generate actual CTCS-2 level speed limit parameters.

[0021] In this step, a realistic test environment can be pre-built. This can be achieved by deploying a train dispatching centralized system simulator, a real temporary speed limit server, and other necessary simulators. The train dispatching centralized system simulator sends temporary speed limit commands to the real temporary speed limit server. Upon receiving the commands, the server generates the actual CTCS-2 level speed limit parameters. The real temporary speed limit server uses actual TSRS equipment deployed on-site, configured with hardware parameters consistent with the operating line. The train dispatching centralized system simulator is built using an industrial control computer (IPC) pre-installed with CTC system simulation software. The two are connected via Ethernet (TCP / IP protocol), with the port configured as the standard communication port between CTC and TSRS (e.g., port 50001) to ensure command transmission conforms to the CTCS-2 level train control system communication specifications. Transponder information and temporary speed limit information are input into the real test environment. This environment simulates a train passing a specific transponder, triggering the temporary speed limit server to send a temporary speed limit information packet to the train, thus obtaining the actual CTCS-2 level speed limit parameters. The actual CTCS-2 level speed limit parameters specifically include: resolution, distance to the next speed limit zone (d_tsr), length of the speed limit zone (l_tsr), and speed limit value (v_tsr). For example, resolution: 1m (consistent with the data entered in step 101); (d_tsr): 100m; (l_tsr): 250m; (v_tsr): 60km / h.

[0022] After obtaining the actual CTCS-2 level speed limit parameters, they are automatically stored in the test system's database (such as MySQL) and associated with the corresponding test task number and transponder number, facilitating subsequent comparison with the expected CTCS-2 level speed limit parameters.

[0023] 103. Input the transponder information and temporary speed limit information into the theoretical calculation engine to obtain the desired CTCS-2 level speed limit parameters.

[0024] Among them, the theoretical calculation engine is used to perform differentiated calculations of the expected CTCS-2 level speed limit parameters for different temporary speed limit scenarios in the base coordinate system.

[0025] In this step, the theoretical calculation engine defaults to setting the kilometer coordinate system (e.g., K-system) of the transponder jurisdiction entered in step 101 as the base coordinate system. If the entered temporary speed limit information includes other kilometer coordinate systems (e.g., NK-system), it automatically performs a kilometer coordinate system conversion operation to ensure a unified calculation benchmark. For example, if the starting point of a speed limit section in the temporary speed limit information is NK1+100, and the kilometer coordinate system conversion point determines that NK1+000 corresponds to K1+000, then the theoretical calculation engine converts NK1+100 to K1+100, where K1+100 is the starting point of a speed limit section in the base coordinate system. This kilometer coordinate system conversion point can be inherent to the line or included in the temporary speed limit information entered in step 101. Alternatively, the NK-system can be set as the base coordinate system, and subsequent kilometer coordinate system conversion operations can be performed. This embodiment does not limit this, only requiring that the unified calculation benchmark be ensured.

[0026] After the kilometer marker system is completed, the number of speed-limited sections entered in step 101 is used to determine whether the current temporary speed-limiting scenario is a "single speed-limiting scenario" or a "multiple speed-limiting scenario." Then, differential calculations are performed based on resolution to obtain the desired CTCS-2 level speed limit parameters. A single speed-limiting scenario refers to a scenario with only one speed-limited section within the jurisdiction, while a multi-speed-limiting scenario refers to a scenario with multiple speed-limited sections within the jurisdiction. When performing differential calculations based on resolution, the endpoint positions of the speed-limited sections need to be adjusted according to different resolutions. It is also necessary to determine whether any speed-limited sections exceed the jurisdiction and whether adjacent speed-limited sections overlap in a multi-speed-limiting scenario. This ensures efficient and accurate calculation of the desired CTCS-2 level speed limit parameters. These desired CTCS-2 level speed limit parameters also include: resolution, distance to the next speed-limited section (d_tsr), length of the speed-limited section (l_tsr), and speed limit value (v_tsr).

[0027] 104. Based on the comparison results between the actual CTCS-2 level speed limit parameters and the expected CTCS-2 level speed limit parameters, verify whether the temporary speed limit information package passes the test.

[0028] In this step, the actual CTCS-2 level speed limit parameters and the expected CTCS-2 level speed limit parameters, obtained based on the same transponder information and temporary speed limit information, are compared for consistency. Specifically, the four core fields described in steps 102 and 103 above—resolution, d_tsr, l_tsr, and v_tsr—are compared. For multi-speed-limit scenarios, the comparison must be performed sequentially according to the speed limit segments, such as first speed limit segment versus first speed limit segment, second speed limit segment versus second speed limit segment, and so on. If all fields are completely consistent, the temporary speed limit information packet test is considered passed. If any field is inconsistent, the temporary speed limit information packet test is considered failed, and the differing field and its specific value are marked, such as "Difference field: d_tsr, Actual value: 105m, Expected value: 100m". The comparison results will automatically generate a test log (in PDF / Excel format). The log includes "information input record, actual parameter extraction record, theoretical calculation process, and comparison result details". The log will be automatically associated with the test task number and can be downloaded for archiving or used for problem tracing.

[0029] Based on the above Figure 1 As can be seen from the implementation method, the automated testing method for temporary speed limit information packets provided in this application first obtains transponder information including the transponder's jurisdiction and endpoint location, and temporary speed limit information including the endpoint location of the speed limit section, speed limit value, and resolution. Then, the two are respectively input into a real test environment composed of a train dispatching centralized system simulator and a temporary speed limit server simulator to obtain actual CTCS-2 level speed limit parameters, and input into a theoretical calculation engine that can perform differentiated calculations for different temporary speed limit scenarios in a base coordinate system to obtain CTCS-2 level speed limit parameters. Finally, the temporary speed limit information packet is verified by comparing the two types of parameters to determine whether it passes the test, thereby achieving efficient, accurate, and repeatable testing of the temporary speed limit information packet.

[0030] Furthermore, in this embodiment, the specific execution process of inputting transponder information and temporary speed limit information into the theoretical calculation engine to obtain the desired CTCS-2 level speed limit parameters is as follows: a base kilometer system is constructed within the jurisdiction, and kilometer conversion is performed on the endpoint positions of the jurisdiction and the endpoint positions of the speed limit sections based on the base kilometer system; if it is a single speed limit scenario, the distance between the starting position of the jurisdiction and the starting position of the speed limit section is used as the distance parameter, and the length between the starting position and the ending position of the speed limit section is used as the length parameter, and the distance parameter, length parameter, resolution, and speed limit value are used together as the desired CTCS-2 level speed limit parameters; if it is a multi-speed limit scenario, the distance between the starting position of the jurisdiction and the starting position of each speed limit section is used as the distance parameter of each speed limit section, and the length between the starting position and the ending position of each speed limit section is used as the length parameter of each speed limit section, and the distance parameter, length parameter, resolution, and speed limit value are used together as the desired CTCS-2 level speed limit parameters.

[0031] In this step, the kilometer marker system within the transponder's jurisdiction can be used as the base kilometer marker system to avoid increasing computational complexity due to additional benchmarks. If the transponder information does not specify the kilometer marker system, the kilometer marker system covering the most speed limit sections can be selected from the temporary speed limit information in step 101 as the base kilometer marker system. For example, if two out of the three speed limits are K-series, then the base kilometer marker system is K-series.

[0032] After determining the base kilometer system, taking the transponder base system as the K system and a certain speed-limited section as the NK system (NK1+100-NK1+300), with the conversion point NK1+000=K1+000 as an example: Comparing the transponder base kilometer system (K system) and the speed-limited section kilometer system (NK system), it is determined to be a multi-kilometer system, requiring conversion; through the route direction information, confirm the consistency of coordinate increases and decreases between the NK system and the K system, that is, if in the positive direction of the route, the NK system coordinates increase with the increase of mileage, i.e., consistent with the K system, then the conversion formula is "K coordinate = NK coordinate - NK conversion point coordinate + K conversion point coordinate". Therefore, the conversion process for the starting point NK1+100 of the speed-limited section is: NK1+100-NK1+000. +000+K1+000=K1+100. The conversion process for the end point of the speed limit section, NK1+300, is: NK1+300-NK1+000+K1+000=K1+300, ultimately converting NK1+100-NK1+300 to K1+100-K1+300. Furthermore, to ensure the accuracy and validity of subsequent calculations, it can be verified whether the endpoint of the converted speed limit section is within the transponder's jurisdiction. For example, the converted K1+100-K1+300 is within the transponder's K1+000-K1+500 range. If the converted speed limit section is completely outside the jurisdiction, it is marked as "This speed limit section is irrelevant to the transponder and will not participate in subsequent calculations."

[0033] After kilometer marker conversion, the current temporary speed limit scenario can be determined based on the number of speed limit sections, including single-speed-limit and multi-speed-limit scenarios. When only one speed limit section overlaps with the transponder's jurisdiction, the calculation enters the single-speed-limit scenario. In this case, different processing situations will arise due to factors such as resolution differences, whether the speed limit section exceeds the jurisdiction, and whether there is a chain break. From a resolution perspective, there are mainly two cases: 1m resolution and 10m resolution. At 1m resolution, the calculation logic is relatively straightforward, requiring no special adjustments to distance or length, and is directly calculated based on actual mileage data. However, at 10m resolution, special processing is required according to safety principles; this is the core difference from 1m resolution, and this processing method will be further refined later.

[0034] From the perspective of the positional relationship between the speed-limited section and the transponder's jurisdiction, there are two scenarios: One is that the speed-limited section is entirely within the transponder's jurisdiction, in which case the calculation directly uses the endpoint position of the speed-limited section itself. The other is that part of the speed-limited section extends beyond the jurisdiction, such as the starting point of the speed-limited section being outside the jurisdiction but the ending point being within it, or vice versa. In this case, the starting and ending points of the transponder's jurisdiction must be used as boundaries to truncate the portion extending beyond the jurisdiction, and the calculation is based only on the section within the jurisdiction. Furthermore, the presence of a broken chain within the transponder's jurisdiction will also affect the calculation. If a broken chain exists (long or short), the length data needs to be adjusted according to the type of broken chain (add for long chains, subtract for short chains) when calculating the length of the speed-limited section. If there is no broken chain, the length is calculated directly based on the normal mileage difference.

[0035] When there are two or more speed-limited sections overlapping within the jurisdiction of a transponder, these sections must first be sorted before calculation. Different situations may arise during sorting and calculation due to information differences. The sorting process is mainly affected by the transponder's direction. If the transponder's direction is the same as the positive direction of the line (i.e., the starting kilometer marker of the jurisdiction is smaller than the ending kilometer marker), then the sections are sorted from smallest to largest starting kilometer marker. If the transponder's direction is opposite to the positive direction of the line (i.e., the starting kilometer marker of the jurisdiction is larger than the ending kilometer marker), then the sections are sorted from largest to smallest starting kilometer marker, ensuring that the sorting result is consistent with the speed limit order perceived by the actual train operation. The calculation process also needs to consider resolution: at a 1m resolution, only the distance and length parameters of each speed-limited section need to be calculated sequentially without additional processing. The distance parameter includes the distance between the ending position of the previous speed-limited section and the starting position of the next speed-limited section. For the first speed-limited section, it is the distance from the transponder's starting point to its own starting point, i.e., the distance between the starting position of the jurisdiction and the starting position of the first speed-limited section. At 10m resolution, in addition to calculating the basic parameters, a special case needs to be considered: whether different speed limit sections overlap after rounding. If there is overlap, the speed limit value and section range of the overlapping area need to be adjusted according to the safety principle. This is also the key difference between multi-speed limit scenarios and single-speed limit scenarios at 10m resolution and 1m resolution scenarios.

[0036] Furthermore, based on the above description of a single speed limit scenario, in a single speed limit scenario, according to the resolution, the distance between the starting position of the jurisdiction and the starting position of the speed limit section is used as a distance parameter, and the length between the starting and ending positions of the speed limit section is used as a length parameter. The specific execution process of using the distance parameter, length parameter, resolution, and speed limit value together as the expected CTCS-2 level speed limit parameter is as follows: If the resolution is the first resolution, then according to the first resolution, the distance between the starting position of the jurisdiction and the starting position of the speed limit section is used as a distance parameter, and the length between the starting and ending positions of the speed limit section is used as a length parameter. The distance parameter, length parameter, resolution, and speed limit value together are used as the expected CTCS-2 level speed limit parameter. If the resolution is the second resolution, then according to the second resolution, the endpoint position of the speed limit section is rounded, the distance between the starting position of the jurisdiction and the starting position of the speed limit section is used as a distance parameter, and the length between the starting and ending positions of the speed limit section is used as a length parameter. The distance parameter, length parameter, resolution, and speed limit value together are used as the expected CTCS-2 level speed limit parameter.

[0037] In this step, a single speed limit scenario refers to a situation where there is only one speed limit section overlapping with the transponder's jurisdiction. The distance parameter (d_tsr) and length parameter (l_tsr) need to be calculated based on the resolution (1m / 10m). The distance parameter is the distance from the start of the transponder's jurisdiction to the start of the speed limit section, and the length parameter refers to the actual length of the speed limit section within the transponder's jurisdiction. The first resolution can be 1m, while the second resolution can be 10m. The rounding process follows safety principles and is set for the second resolution, specifically rounding the distance down and the length up. That is, d_tsr is rounded down, and l_tsr is rounded up.

[0038] For example, in calculations with a resolution of 1m, no rounding is needed; the calculation is performed directly. Taking the transponder's jurisdiction range (K1+000-K1+500), speed-limited section (K1+100-K1+300), and speed limit (60km / h) as an example, the distance parameter d_tsr is calculated as: K1+100-K1+000=100m (from the starting position of the jurisdiction range to the starting position of the speed-limited section); the length parameter l_tsr is calculated as: K1+300-K1+100=200m (i.e., the basic length of the speed-limited section). The expected CTCS-2 level speed limit parameters are: {resolution: 1m, d_tsr: 100m, l_tsr: 200m, v_tsr: 60km / h}. In calculations with a resolution of 10m, rounding is required according to safety principles. The same single speed limit data is used, but the resolution is changed to 10m. First, calculate the base values ​​at a 1m resolution: base d = 100m (distance), base l = 200m (length); then, round down to a 10m resolution: round the distance parameter d_tsr: d' = d / 10 (round down), i.e., 100 / 10 = 10 (unit: 10m, i.e., actual 100m); round the length parameter l_tsr: l' = (l + (d - 10 × d')) / 10 (round up), substitute d = 100, d' = 10, l = 200, then l' = 200 / 10 = 20 (unit: 10m, i.e., actual 200m). The expected CTCS-2 speed limit parameters at this time are: {resolution: 10m, d_tsr: 10 (100m), l_tsr: 25 (250m), v_tsr: 60km / h} (the actual mileage is in parentheses, and the CTCS-2 information packet is stored in "unit 10m").

[0039] Furthermore, based on the above description of multiple speed limit scenarios, in such scenarios, according to the resolution, the distance between the starting position of the jurisdiction and the starting position of each speed limit segment is used as the distance parameter for each speed limit segment, and the length between the starting and ending positions of each speed limit segment is used as the length parameter for each speed limit segment. The specific execution process of using the distance parameter, length parameter, resolution, and speed limit value together as the expected CTCS-2 level speed limit parameter is as follows: If the resolution is the first resolution, then according to the first resolution, the distance between the starting position of the jurisdiction and the starting position of each speed limit segment, the distance between the ending position of the previous speed limit segment and the starting position of the next speed limit segment in two adjacent speed limit segments, and the distance between the starting position of the last speed limit segment and the ending position of the jurisdiction are used as distance parameters. The length between the points is used as the length parameter of each speed-limited section, and the distance parameter, length parameter, resolution, and speed limit value are used together as the expected CTCS-2 level speed limit parameters. If the resolution is the second resolution, the endpoint positions of the speed-limited sections are rounded according to the second resolution. The distance between the starting position of the jurisdiction and the starting position of each speed-limited section, the distance between the ending position of the previous speed-limited section and the starting position of the next speed-limited section, and the distance between the starting position of the last speed-limited section and the ending position of the jurisdiction are used as the distance parameter. The length between the starting and ending positions of each speed-limited section is used as the length parameter. The speed limit value is adjusted according to whether two adjacent speed-limited sections overlap. The distance parameter, length parameter, resolution, and speed limit value are used together as the expected CTCS-2 level speed limit parameters.

[0040] In this step, a multiple speed limit scenario refers to a situation where there are two or more speed limit sections overlapping within the transponder's jurisdiction. In this case, the sections need to be sorted first, and then calculated according to resolution. The sorting process needs to be determined based on the transponder's direction. For example, assuming the transponder's direction is along the positive direction of the line (K value increases to positive), and there are two speed limit sections: Speed ​​limit section a: 1K1+100-K1+300 (v=60km / h), and speed limit section b: 2K1+350-K1+450 (v=45km / h). The sorting principle is to sort along the transponder's direction by the starting K value of the speed limit sections from smallest to largest, meaning the sorting result is from speed limit section a to speed limit section b. Conversely, if the transponder's direction is in the opposite direction (K value decreases to positive), then the sections are sorted by the starting K value from largest to smallest, meaning the sorting result is from speed limit section b to speed limit section a.

[0041] After sorting, calculations still need to be performed based on resolution. The first resolution can be 1m, while the second resolution can be 10m. The rounding process follows safety principles for the second resolution, specifically rounding the distance down and the length up. That is, d_tsr is rounded down, while l_tsr is rounded up. It should be noted that in multi-speed-limit scenarios, d_tsr refers to the distance from the end of the previous speed limit to the beginning of the next speed limit.

[0042] It should be noted that in multi-speed-limit scenarios, because multiple speed-limit sections are rounded simultaneously, if two adjacent speed-limit sections are close together, they may overlap after rounding. In this case, the speed limit value and section range of the overlapping area must be adjusted according to the safety principle to ensure the accuracy of subsequent tests. Therefore, it is necessary to determine whether two adjacent speed-limit sections overlap. The specific execution process for adjusting the speed limit value based on whether two adjacent speed-limit sections overlap is as follows: if the end position of the preceding speed-limit section crosses the start position of the following speed-limit section, then the two adjacent speed-limit sections are determined to overlap; the speed limit value corresponding to the overlapping area between the two adjacent speed-limit sections is adjusted according to the principle of prioritizing the minimum speed limit value.

[0043] The principle of prioritizing the minimum speed limit means that if the speed limits of two adjacent speed limit sections are different, the speed limit of the overlapping area shall be based on the smaller speed limit; if the speed limits of two adjacent speed limit sections are the same, the speed limit of the previous speed limit section shall be used.

[0044] For example, in calculations with a resolution of 1m, no rounding is needed; calculations can be performed directly. Taking the transponder's jurisdiction (K1+000-K1+500), speed-limited section a (K1+100-K1+300), speed-limited section b (K1+350-K1+450), the speed limit of speed-limited section a (60km / h), and the speed limit of speed-limited section b (45km / h) as examples, the d_tsr and l_tsr of each speed-limited section are calculated. That is, the d_tsr1 of speed-limited section a (K1+100-K1+300) is: K1+100-K1+000=100m (from the starting position of the jurisdiction to the starting position of speed-limited section a), and the l_tsr1 of speed-limited section a (K1+100-K1+300) is K1+300-K1+100=200m. For speed-limited section b (K1+350-K1+450), the d_tsr2 is: K1+350-K1+300=50m (from the end point of speed-limited section a to the beginning point of speed-limited section b). The l_tsr2 for speed-limited section b (K1+350-K1+450) is: K1+450-K1+350=100m. The expected CTCS-2 level speed limit parameters are: [{resolution: 1m, d_tsr: 100m, l_tsr: 200m, v_tsr: 60km / h}, {resolution: 1m, d_tsr: 50m, l_tsr: 100m, v_tsr: 45km / h}]. For calculations with a resolution of 10m, rounding is required according to safety principles. The above multiple speed limit data are still used, i.e., the above two speed limit data are used, but the resolution is changed to 10m. Based on a 1m resolution, the basic values ​​are calculated as follows: Speed ​​limit section a: d1=100m, l1=200m; Speed ​​limit section b: d2=50m (adjacent distance), l2=100m; Rounding down to a 10m resolution: Speed ​​limit section a: d1'=100 / 10=10 (100m) l1'=(200+(100-10×10)) / 10=20 (200m); Speed ​​limit section b: First calculate the actual K value of the starting position of speed limit section b=K1+300 (end point of speed limit 1)+50m(d2)=K1+350, then the basic value of d2=50m, d2'=50 / 10=5 (50m), l2'=100 / 10=10 (100m). Rounded speed limit sections: Speed ​​limit section a (K1+100-K1+350, 20×10m), speed limit section b (K1+350-K1+450, 10×10m). If there is overlap after rounding (e.g., the starting point of speed limit 2 is rounded to K1+340): then the overlapping area (K1+340-K1+350) is adjusted according to the "minimum speed limit value (45km / h)", that is, the length of speed limit section a is shortened to K1+340, and the starting position of speed limit section b is adjusted to K1+340.The expected CTCS-2 level speed limit parameters at this time are: [{resolution: 10m, d_tsr: 10 (100m), l_tsr: 20 (200m), v_tsr: 60km / h}, {resolution: 10m, d_tsr: 5 (50m), l_tsr: 10 (100m), v_tsr: 45km / h}].

[0045] Furthermore, regarding the rounding process described above for single and multiple speed limit scenarios, the specific execution process for rounding the endpoint positions of speed-limited sections is as follows: The endpoint positions of the speed-limited sections are rounded down according to the principle of rounding the distance parameter down and the length parameter up. That is, d_tsr is minimized as much as possible, while l_tsr is increased, thereby ensuring safety in actual operation.

[0046] It should be noted that a special scenario may exist during the rounding process: the rounded speed limit section may exceed the jurisdictional area, including both the starting point and ending point exceeding the jurisdictional area. In this case, if the calculation is still based on the rounded endpoint position of the speed limit section, it will lead to calculation errors. Since in this embodiment, when a train passes a transponder, the calculation area targeted by the temporary speed limit information packet is actually the entire jurisdictional area, after rounding, it is necessary to determine the positional relationship between the speed limit section and the jurisdictional area. That is, it is necessary to further verify whether the rounded speed limit section exceeds the transponder's jurisdictional area to avoid the calculation parameters becoming disconnected from the actual jurisdictional scenario due to rounding, thus ensuring the accuracy of subsequent calculations. Specifically, after rounding the endpoint position of the speed limit section, the process also includes: determining whether the speed limit section exceeds the jurisdictional area based on the endpoint positions of the jurisdictional area and the speed limit section; if it does, then the starting or ending position of the jurisdictional area is used as the new starting or ending position of the speed limit section at the point where it exceeds the jurisdictional area.

[0047] In this step, since the speed limit section may have either its starting point or its ending point outside the jurisdiction, the following explanations address single and multiple speed limit scenarios.

[0048] For a single speed limit scenario, which refers to a scenario where there is only one overlapping speed limit within the transponder's coverage area, taking an example with a 10m resolution and the endpoint of the speed limit section exceeding the limit after rounding: After rounding, the endpoint exceeds the transponder's coverage area: At 1m resolution, the original speed-limited zone range is K1+485-K1+510, with a speed limit of v=45km / h; Calculation before rounding: d=485m, l=25m (K1+510-K1+485). Rounding to 10m resolution: Distance rounding: d'=485 / 10=48 (unit: 10m, i.e., actual 480m); Length rounding: l'=(25+(485-10×48)) / 10=(25+5) / 10=3 (unit: 10m, i.e., actual 30m). Speed-limited zone after rounding: Starting point: K1+000+480m=K1+480, Ending point: K1+480+30m=K1+510.

[0049] If the current endpoint of the jurisdiction is K1+500, while the endpoint of the speed-limited section after rounding is K1+510, then it is determined that the endpoint has been exceeded. If only the endpoint has exceeded, the endpoint of the jurisdiction is used as the new endpoint of the speed-limited section, while the starting point remains unchanged. Therefore, the new endpoint is K1+500, and the new speed-limited section range is K1+480-K1+500. The parameters are recalculated: the new length l_tsr = K1+500-K1+480 = 20m (i.e., 2 units at 10m resolution), and the distance d_tsr remains 480m (48 units). The final expected CTCS-2 speed limit parameters are: {resolution 10m, d_tsr = 48 (480m), l_tsr = 2 (20m), v_tsr = 45km / h}.

[0050] It should be noted that, based on the above-mentioned situation where the end point of a single speed limit section exceeds the limit, the same applies to the situation where the starting point of a single speed limit section exceeds the limit, as well as any speed limit section exceeding the jurisdiction in a multi-speed limit scenario. These points will not be elaborated on further here.

[0051] Furthermore, since transponder information also includes chain breakage within the jurisdiction, when the transponder information includes chain breakage (long chain or short chain) within the jurisdiction, based on the calculation of the distance parameter (d_tsr) and length parameter (l_tsr), the parameters need to be adjusted by adding or subtracting according to the chain breakage type (long chain / short chain) and location to ensure that the calculation result meets expectations. Specifically, before using the distance parameter, length parameter, resolution, and speed limit value together as the expected CTCS-2 level speed limit parameter, the following steps are also included: if the chain breakage type corresponding to the chain breakage is a long chain, then the long chain length is added to the distance parameter and length parameter; if the chain breakage type corresponding to the chain breakage is a single chain break, then the short chain length is subtracted from the distance parameter and length parameter.

[0052] In this step, a chain break refers to a discrepancy between the actual mileage of a railway line and its marked mileage (i.e., the kilometer markers used in the line design). Essentially, this is due to changes in line design, rerouting, or construction adjustments, resulting in a mismatch between the actual physical length of a certain section of the line and the originally marked mileage. The difference needs to be clearly identified through a chain break marker to ensure accurate mileage positioning during train operation. Therefore, this must also be considered when calculating the desired CTCS-2 speed limit parameters. The following detailed implementation will supplement the existing examples of single and multiple speed limit scenarios with chain break information.

[0053] Based on the original example, new chain break information is added within the transponder's jurisdiction. The unified base kilometer system is K-series, and the transponder's jurisdiction range is K1+000-K1+500 (positive direction). Specific chain break parameters are as follows: Chain Break 1: Location K1+200, Type "Long Chain", Length 50m (i.e., the actual mileage at K1+200 is 50m longer than the marked mileage; the marked mileage at K1+200 corresponds to the actual mileage K1+250); Chain Break 2: Location K1+300, Type "Short Chain", Length 30m (i.e., the actual mileage at K1+300 is 30m shorter than the marked mileage; the marked mileage at K1+300 corresponds to the actual mileage K1+270). If the start / end point or distance calculation path of the speed-limited section includes a chain break location, the distance and length parameters need to be adjusted according to the chain break type. The specific principle is to add the length for long chains and deduct the length for short chains.

[0054] For single-speed-limited scenarios, using the 10m resolution, the original speed-limited range K1+100-K1+300, after rounding, requires handling of link breaks: If the speed-limited section includes a long chain, the speed-limited section (1m resolution) starts at K1+100 and ends at K1+300, with a speed limit of 60km / h. Chain break information: A 50m long chain is located at K1+200, meaning the chain break is within the speed-limited section. Parameter calculations without considering chain breaks: Distance parameter d_tsr: K1+100-K1+000=100m, Length parameter l_tsr: 300-100=200m. Chain break adjustment (long chain overlay): Distance parameter d_tsr adjustment: Since the distance calculation path (K1+000-K1+100) does not pass through the chain break K1+200, d_tsr remains unchanged at 100m. Length parameter l_tsr adjustment: Since the speed-limited section includes a long chain, the actual length = base length + long chain length = 200 + 50 = 250m. Adjusted parameters (1m resolution): d_tsr=100m, l_tsr=250m. Combined with rounding for 10m resolution and exceeding the limit judgment: After rounding, d' = 10 (100m), l' = 25 (250m), and the speed limit zone range is K1+100-K1+350 (including the actual mileage of the long chain). Final expected parameters: {resolution 10m, d_tsr = 10 (100m), l_tsr = 25 (250m), v_tsr = 60km / h}.

[0055] If the speed-limited section includes a short chain, the speed-limited section (1m resolution) starts at K1+250 and ends at K1+350, with a speed limit of v=45km / h. Chain break information: A 30m short chain at K1+300 (located within the speed-limited section). Parameter calculations without considering chain breaks: Distance parameter d_tsr: K1+250-K1+000=250m, Length parameter l_tsr: 350-250-100m. Chain break adjustment (short chain deduction): Since K1+300 is between K1+250 and K1+350, the distance parameter d_tsr: the path K1+000-K1+250 does not involve a chain break, so it remains unchanged at 250m. The length parameter l_tsr: Actual length = base length - short chain length = 100-30=70m. Adjusted parameters (1m resolution): d_tsr = 250m, l_tsr = 70m. Combining with a 10m resolution and rounding: d' = 250 / 10 = 25 (250m) l' = (70 + (250 - 10 × 25)) / 10 = 7 (70m). Final desired parameters: {10m resolution, d_tsr = 25 (250m), l_tsr = 7 (70m), v_tsr = 45km / h}.

[0056] It should be noted that, based on the calculation process for the single speed limit scenario combined with the chain breakage situation, the calculation process for the multi-speed limit scenario combined with the chain breakage situation is the same, and will not be elaborated on here.

[0057] Furthermore, in this embodiment, in addition to the single-speed-limit scenario and the multi-speed-limit scenario mentioned above, testing can also be performed on the unlimited-speed-limit scenario. Specifically, this includes: obtaining the initialization status of the temporary speed-limiting server; if the temporary speed-limiting server is not initialized, then the expected CTCS-2 level speed-limiting parameter is the parameter calculated based on the minimum line speed limit value for the entire area within the transponder's jurisdiction; if the temporary speed-limiting server is initialized and there is no speed limit overlapping with the transponder within the jurisdiction, then the expected CTCS-2 level speed-limiting parameter is the parameter calculated based on the maximum line speed for the entire area within the transponder's jurisdiction.

[0058] In this step, the core logic of the unlimited speed scenario is to determine the speed limit benchmark (minimum speed limit or maximum speed of the line) for the entire area under the jurisdiction of the transponder based on the initialization state of the temporary speed limit server, and then generate the expected CTCS-2 level speed limit parameters.

[0059] Before conducting unlimited speed scenario testing, two key basic data sets need to be confirmed to provide a benchmark for subsequent state determination and parameter calculation: Transponder basic information: This information must be unified to the jurisdiction of a base kilometer system (e.g., the K-system), including the starting and ending points, and the total length of the jurisdiction; the transponder direction must be consistent with the positive direction of the line, with no broken links. Pre-set speed parameters for the line: The "minimum speed limit" (denoted as V_min, e.g., 40km / h, which is the mandatory speed limit benchmark when the temporary speed limit server is not initialized) and the "maximum speed" (denoted as V_max, e.g., 80km / h, which is the default speed limit benchmark when the temporary speed limit server is initialized and there is no speed limit) are pre-stored in the configuration library of the theoretical calculation engine and can be directly accessed.

[0060] The theoretical calculation engine obtains the real-time initialization status of the temporary speed limit server through a "status interaction interface" to ensure the accuracy of status determination. The specific implementation is as follows: An "initialization status query command" is sent to the temporary speed limit server via the communication interface between the train dispatching centralized system simulator and the actual temporary speed limit server. Upon receiving the command, the temporary speed limit server returns a status message containing either "initialization complete" or "not initialized." If the theoretical calculation engine does not receive the status message from the temporary speed limit server within a preset time (e.g., 5 seconds), or if the message fields are missing or incorrectly formatted, it automatically determines "status acquisition failed" and triggers a retry mechanism (maximum of 3 retries). If the retry still fails, a log message "Test paused, communication link between the temporary speed limit server and the train dispatching centralized system simulator needs to be checked" is output, pausing subsequent parameter calculations. The obtained "initialization complete" or "not initialized" status result is associated with the current test task number and transponder number and stored in the test database for easy traceability in subsequent parameter calculations.

[0061] Based on the initialization state of the train dispatching centralized system simulator, the expected parameters are calculated differently for two scenarios: "uninitialized" and "initialized with no speed limit," to determine the "full-area speed limit value" and the corresponding distance / length parameters. The following section details the calculation of the expected CTCS-2 level speed limit parameters for each scenario.

[0062] Scenario 1: If the temporary speed limit server is not initialized, the minimum speed limit value of the line will be used for calculation. When the temporary speed limit server is not initialized, regardless of whether there is temporary speed limit information within the transponder's jurisdiction (even if temporary speed limit information is entered, it will not take effect because the temporary speed limit server has not been initialized), the parameters for the entire area must be calculated based on the minimum speed limit value V_min. Specifically, there is no need to check the overlap between the temporary speed limit information and the transponder's jurisdiction; the default is "no effective speed limit in the entire area," and calculations are performed uniformly based on V_min. The default resolution is 1m (if a 10m resolution is specified for testing, it can be rounded according to the rules); the distance parameter (d_tsr) is set to 0m. Because the entire area has the same speed limit and there is no "next speed limit segment," the "distance to the next speed limit segment" is defined as 0, representing the start point of the transponder's jurisdiction, i.e., entering the minimum speed limit area. Length parameter (l_tsr): Set to a total length of 500m within the transponder's jurisdiction, representing that the minimum speed limit covers all mileage within the transponder's jurisdiction; Speed ​​limit value (v_tsr): Calls the minimum line speed limit value V_min=40km / h from the configuration library. The final expected CTCS-2 level speed limit parameters are: {resolution: 1m, d_tsr: 0m, l_tsr: 500m, v_tsr: 40km / h}. This means that when the temporary speed limit server is not initialized, within the transponder's jurisdiction, trains must run at the minimum speed limit for the entire route, without segmented speed limits, and this speed limit is enforced from the transponder's starting point.

[0063] Scenario 2: If the temporary speed-limiting server has been initialized and has no speed limit, the calculation will be based on the maximum speed of the line.

[0064] When the temporary speed limit server is initialized, it is necessary to first determine whether there is a temporary speed limit overlapping with the control area of ​​the transponder. If not, (i.e., no speed limit), the parameters for the entire area are calculated according to the "maximum line speed V_max". Specifically, all temporary speed limit information input in step 101 is retrieved and unified to the base kilometer system of the transponder. The positional relationship between the start and end points of each speed limit section and the control area of ​​the transponder is checked one by one. If all speed limit sections are completely outside the control area, it is determined that there is no speed limit overlapping with the transponder within the control area, i.e., no speed limit. If any speed limit section is partially or completely within the control area, the unlimited speed scenario is exited, and the calculation is switched to a single or multiple speed limit scenario. Resolution: consistent with scenario 1, default 1m resolution; distance parameter (d_tsr): set to 0m. This means the entire area has the same maximum speed limit, with no next speed limit section, and the distance is calculated from the starting point of the jurisdiction as 0; the length parameter (l_tsr): is set to the total length of the jurisdiction, representing that the maximum speed covers all mileage within the jurisdiction; the speed limit value (v_tsr): calls the maximum line speed V_max=80km / h from the configuration library. The final expected CTCS-2 level speed limit parameters are: {resolution: 1m, d_tsr: 0m, l_tsr: 500m, v_tsr: 80km / h}.

[0065] Furthermore, as a response to the above Figure 1 The implementation of the method embodiment shown in this application provides an automated testing device for temporary speed limit information packets. This device is used to achieve efficient, accurate, and repeatable testing of temporary speed limit information packets. The embodiment of this device corresponds to the foregoing method embodiments. For ease of reading, this embodiment will not repeat the details of the foregoing method embodiments one by one, but it should be clear that the device in this embodiment can implement all the contents of the foregoing method embodiments. Specifically, as shown... Figure 2 As shown, the device includes: The acquisition unit 31 is used to acquire transponder information and temporary speed limit information. The transponder information includes at least the jurisdiction of the transponder and the endpoint position corresponding to the jurisdiction. The temporary speed limit information includes at least the endpoint position, speed limit value and resolution corresponding to the speed limit section within the jurisdiction. Test unit 32 is used to input the transponder information and the temporary speed limit information obtained by the acquisition unit 31 into the real test environment to obtain the actual CTCS-2 level speed limit parameters. The real test environment is used to control the train dispatching centralized system simulator to send a temporary speed limit command to the temporary speed limit server real machine to trigger the temporary speed limit server real machine to generate the actual CTCS-2 level speed limit parameters. The calculation unit 33 is used to input the transponder information and the temporary speed limit information obtained by the acquisition unit 31 into the theoretical calculation engine to obtain the expected CTCS-2 level speed limit parameters. The theoretical calculation engine is used to perform differentiated calculations of the expected CTCS-2 level speed limit parameters for different temporary speed limit scenarios in the base coordinate system. Verification unit 34 is used to verify whether the temporary speed limit information package passes the test based on the comparison results between the actual CTCS-2 level speed limit parameters obtained by the test unit 32 and the expected CTCS-2 level speed limit parameters obtained by the calculation unit 33.

[0066] Furthermore, such as Figure 3 As shown, the computing unit 33 includes: The conversion module 331 is used to construct the base kilometer marker system within the jurisdiction and to convert the kilometer markers of the endpoint positions of the jurisdiction and the endpoint positions of the speed limit sections based on the base kilometer marker system. The first calculation module 332 is used to, if it is a single speed limit scenario, take the distance between the starting position of the jurisdiction and the starting position of the speed limit section as a distance parameter, take the length between the starting position and the ending position of the speed limit section as a length parameter, and take the distance parameter, the length parameter, the resolution and the speed limit value together as the expected CTCS-2 level speed limit parameter. The second calculation module 333 is used to, in the case of a multi-speed-limit scenario, take the distance between the starting position of the jurisdiction and the starting position of each speed-limit section as the distance parameter of each speed-limit section, take the length between the starting position and the ending position of each speed-limit section as the length parameter of each speed-limit section, and take the distance parameter, the length parameter, the resolution and the speed limit value together as the expected CTCS-2 level speed limit parameter.

[0067] Furthermore, such as Figure 3 As shown, the first calculation module 332 specifically includes: If the resolution is a first resolution, then according to the first resolution, the distance between the starting position of the jurisdiction and the starting position of the speed limit section is used as the distance parameter, the length between the starting position and the ending position of the speed limit section is used as the length parameter, and the distance parameter, the length parameter, the resolution and the speed limit value are used together as the expected CTCS-2 level speed limit parameter. If the resolution is the second resolution, then according to the second resolution, the endpoint position of the speed limit section is rounded, the distance between the starting position of the jurisdiction and the starting position of the speed limit section is taken as the distance parameter, the length between the starting position and the ending position of the speed limit section is taken as the length parameter, and the distance parameter, the length parameter, the resolution and the speed limit value are taken together as the expected CTCS-2 level speed limit parameter.

[0068] Furthermore, such as Figure 3 As shown, the second calculation module 333 specifically includes: If the resolution is a first resolution, then according to the first resolution, the distance between the starting position of the jurisdiction and the starting position of each speed-limited section, the distance between the ending position of the previous speed-limited section and the starting position of the next speed-limited section, and the distance between the starting position of the last speed-limited section and the ending position of the jurisdiction are used as the distance parameters. The length between the starting position and the ending position of each speed-limited section is used as the length parameter of each speed-limited section. The distance parameters, the length parameters, the resolution, and the speed limit value are used together as the expected CTCS-2 level speed limit parameters. If the resolution is the second resolution, then according to the second resolution, the endpoint positions of the speed limit sections are rounded. The distance between the starting position of the jurisdiction and the starting position of each speed limit section, the distance between the ending position of the previous speed limit section and the starting position of the next speed limit section, and the distance between the starting position of the last speed limit section and the ending position of the jurisdiction are used as the distance parameters. The length between the starting and ending positions of each speed limit section is used as the length parameter. The speed limit value is adjusted according to whether two adjacent speed limit sections overlap. The distance parameter, the length parameter, the resolution, and the speed limit value are used together as the desired CTCS-2 level speed limit parameter.

[0069] Furthermore, such as Figure 3 As shown, the device further includes: After rounding the endpoint positions of the speed-limited section, it is determined whether the speed-limited section exceeds the jurisdiction based on the endpoint positions of the jurisdiction and the endpoint positions of the speed-limited section. If the speed limit is exceeded, the starting or ending position of the jurisdiction will be used as the new starting or ending position of the speed limit section beyond the end.

[0070] Furthermore, such as Figure 3 As shown, the device further includes: The endpoint positions of the speed-limited sections are rounded down according to the principle of rounding down the distance parameter and rounding up the length parameter.

[0071] Furthermore, such as Figure 3 As shown, the device further includes: If the end point of the first speed limit section crosses the start point of the second speed limit section in two adjacent speed limit sections, then the two adjacent speed limit sections are determined to overlap. The speed limit values ​​corresponding to the overlapping areas between two adjacent speed limit sections are adjusted according to the principle of prioritizing the minimum speed limit value.

[0072] Furthermore, such as Figure 3 As shown, the transponder information also includes chain breakage information within the jurisdiction; the device also includes: Before using the distance parameter, the length parameter, the resolution, and the speed limit value together as the desired CTCS-2 level speed limit parameter, if the chain break type corresponding to the chain break situation is a long chain, then the long chain length is superimposed on the distance parameter and the length parameter. If the chain breakage condition corresponds to a chain breakage type, then the short chain length is deducted from the distance parameter and the length parameter.

[0073] Furthermore, embodiments of this application also provide a storage medium for storing a computer program, wherein the computer program, when running, controls the device where the storage medium is located to execute the above-described... Figure 1 The automated testing method for the temporary speed limit information packet described in the document.

[0074] Furthermore, embodiments of this application also provide a processor for running a program, wherein the program executes the above-described... Figure 1 The automated testing method for the temporary speed limit information packet described in the document.

[0075] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0076] It is understood that the relevant features in the above methods and apparatus can be referenced interchangeably. Furthermore, the terms "first," "second," etc., in the above embodiments are used to distinguish between embodiments and do not represent the superiority or inferiority of any particular embodiment.

[0077] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0078] The algorithms and displays provided herein are not inherently related to any particular computer, virtual system, or other device. Various general-purpose systems can also be used in conjunction with the teachings herein. The required structure for constructing such systems is apparent from the above description. Furthermore, this application is not directed to any particular programming language. It should be understood that the content of this application described herein can be implemented using various programming languages, and the above description of specific languages ​​is for the purpose of disclosing the best mode of implementation of this application.

[0079] In addition, the memory may include non-permanent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0080] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0081] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0082] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0083] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0084] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0085] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0086] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0087] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0088] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0089] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for automated testing of temporary speed limit information packages, characterized in that The method includes: Acquire transponder information and temporary speed limit information. The transponder information includes at least the jurisdiction of the transponder and the endpoint location corresponding to the jurisdiction. The temporary speed limit information includes at least the endpoint location, speed limit value and resolution corresponding to the speed limit section within the jurisdiction. The transponder information and the temporary speed limit information are input into the real test environment to obtain the actual CTCS-2 level speed limit parameters. The real test environment is used to control the train dispatching centralized system simulator to send temporary speed limit commands to the temporary speed limit server to trigger the temporary speed limit server to generate the actual CTCS-2 level speed limit parameters. The transponder information and the temporary speed limit information are input into the theoretical calculation engine to obtain the expected CTCS-2 level speed limit parameters. The theoretical calculation engine is used to perform differentiated calculations of the expected CTCS-2 level speed limit parameters for different temporary speed limit scenarios under the base kilometer system. Based on the comparison results between the actual CTCS-2 level speed limit parameters and the expected CTCS-2 level speed limit parameters, verify whether the temporary speed limit information package passes the test.

2. The method of claim 1, wherein, The transponder information and the temporary speed limit information are input into the theoretical calculation engine to obtain the desired CTCS-2 level speed limit parameters, including: Within the jurisdiction, a base kilometer marker system is constructed, and the kilometer markers of the endpoints of the jurisdiction and the endpoints of the speed-limited sections are converted based on the base kilometer marker system. If it is a single speed limit scenario, then based on the resolution, the distance between the starting position of the jurisdiction and the starting position of the speed limit section is used as a distance parameter, the length between the starting position and the ending position of the speed limit section is used as a length parameter, and the distance parameter, the length parameter, the resolution and the speed limit value are used together as the expected CTCS-2 level speed limit parameter. If it is a multi-speed-limit scenario, then according to the resolution, the distance between the starting position of the jurisdiction and the starting position of each speed-limited section is used as the distance parameter of each speed-limited section, the length between the starting position and the ending position of each speed-limited section is used as the length parameter of each speed-limited section, and the distance parameter, the length parameter, the resolution and the speed limit value are used together as the expected CTCS-2 level speed limit parameter.

3. The method of claim 2, wherein, Based on the resolution, the distance between the starting point of the jurisdiction and the starting point of the speed-limited section is used as a distance parameter, and the length between the starting and ending points of the speed-limited section is used as a length parameter. The distance parameter, the length parameter, the resolution, and the speed limit value are collectively used as the desired CTCS-2 level speed limit parameter, including: If the resolution is a first resolution, then according to the first resolution, the distance between the starting position of the jurisdiction and the starting position of the speed limit section is used as the distance parameter, the length between the starting position and the ending position of the speed limit section is used as the length parameter, and the distance parameter, the length parameter, the resolution and the speed limit value are used together as the expected CTCS-2 level speed limit parameter. If the resolution is the second resolution, then according to the second resolution, the endpoint position of the speed limit section is rounded, the distance between the starting position of the jurisdiction and the starting position of the speed limit section is taken as the distance parameter, the length between the starting position and the ending position of the speed limit section is taken as the length parameter, and the distance parameter, the length parameter, the resolution and the speed limit value are taken together as the expected CTCS-2 level speed limit parameter.

4. The method of claim 2, wherein, Based on the resolution, the distance between the starting position of the jurisdiction and the starting position of each speed-limited section is used as the distance parameter of each speed-limited section, and the length between the starting and ending positions of each speed-limited section is used as the length parameter of each speed-limited section. The distance parameter, the length parameter, the resolution, and the speed limit value are collectively used as the desired CTCS-2 level speed limit parameter, including: If the resolution is a first resolution, then according to the first resolution, the distance between the starting position of the jurisdiction and the starting position of each speed-limited section, the distance between the ending position of the previous speed-limited section and the starting position of the next speed-limited section, and the distance between the starting position of the last speed-limited section and the ending position of the jurisdiction are used as the distance parameters. The length between the starting position and the ending position of each speed-limited section is used as the length parameter of each speed-limited section. The distance parameters, the length parameters, the resolution, and the speed limit value are used together as the expected CTCS-2 level speed limit parameters. If the resolution is the second resolution, then according to the second resolution, the endpoint positions of the speed limit sections are rounded. The distance between the starting position of the jurisdiction and the starting position of each speed limit section, the distance between the ending position of the previous speed limit section and the starting position of the next speed limit section, and the distance between the starting position of the last speed limit section and the ending position of the jurisdiction are used as the distance parameters. The length between the starting and ending positions of each speed limit section is used as the length parameter. The speed limit value is adjusted according to whether two adjacent speed limit sections overlap. The distance parameter, the length parameter, the resolution, and the speed limit value are used together as the desired CTCS-2 level speed limit parameter.

5. The method according to claim 3 or 4, characterized in that, After rounding the endpoint positions of the speed-limited section, the method further includes: Determine whether the speed-limited section exceeds the jurisdiction based on the endpoint locations of the jurisdiction and the endpoint locations of the speed-limited section; If the speed limit is exceeded, the starting or ending position of the jurisdiction will be used as the new starting or ending position of the speed limit section beyond the end.

6. The method according to claim 3 or 4, characterized in that, Rounding the endpoint positions of the speed-limited sections includes: The endpoint positions of the speed-limited sections are rounded down according to the principle of rounding down the distance parameter and rounding up the length parameter.

7. The method according to claim 3 or 4, characterized in that, Adjusting the speed limit value based on whether two adjacent speed limit sections overlap includes: If the end point of the first speed limit section crosses the start point of the second speed limit section in two adjacent speed limit sections, then the two adjacent speed limit sections are determined to overlap. The speed limit values ​​corresponding to the overlapping areas between two adjacent speed limit sections are adjusted according to the principle of prioritizing the minimum speed limit value.

8. An automated testing device for temporary speed limit information packages, characterized in that The device includes: An acquisition unit is used to acquire transponder information and temporary speed limit information. The transponder information includes at least the jurisdiction of the transponder and the endpoint position corresponding to the jurisdiction. The temporary speed limit information includes at least the endpoint position, speed limit value and resolution corresponding to the speed limit section within the jurisdiction. The test unit is used to input the transponder information and the temporary speed limit information obtained by the acquisition unit into the real test environment to obtain the actual CTCS-2 level speed limit parameters. The real test environment is used to control the train dispatching centralized system simulator to send a temporary speed limit command to the temporary speed limit server real machine to trigger the temporary speed limit server real machine to generate the actual CTCS-2 level speed limit parameters. The calculation unit is used to input the transponder information and the temporary speed limit information obtained by the acquisition unit into the theoretical calculation engine to obtain the expected CTCS-2 level speed limit parameters. The theoretical calculation engine is used to perform differentiated calculations of the expected CTCS-2 level speed limit parameters for different temporary speed limit scenarios under the base kilometer system. The verification unit is used to verify whether the temporary speed limit information package passes the test based on the comparison results between the actual CTCS-2 level speed limit parameters obtained by the test unit and the expected CTCS-2 level speed limit parameters obtained by the calculation unit.

9. A storage medium, characterized by The storage medium includes a stored program, wherein, when the program is executed, it controls the device where the storage medium is located to perform an automated testing method for a temporary speed limit information packet as described in any one of claims 1 to 7.

10. A processor, comprising: The processor is used to run a program, wherein the program executes an automated testing method for temporary speed limit information packets as described in any one of claims 1 to 7.

Images