A method for analyzing peak path in CTC3.0 system

Abstract

The present invention discloses a method for parsing a peak route for a CTC3.0 system, comprising: obtaining a shunting operation plan; parsing the contents of the shunting operation plan using a station bus terminal; matching a hump track type when the hook type name is X or D, locating the terminal hump track as the target track for the peak route through the hump track type; parsing the corresponding peak route according to the hook type ID and the hump track type; and automatically parsing the peak route in the form of a shunting hook plan to a station server for use in handling the peak route for shunting operations. The present invention can automatically identify the peak route type, accurately locate the target hump track, and automatically parse the corresponding shunting route or train route.

Description

Technical Field

[0001] The present invention relates to the technical field of rail transit signal control, and in particular to a method for peak route analysis in a CTC3.0 system. Background Art

[0002] The centralized dispatching system (CTC for short) is a railway signaling technology equipment that commands and manages trains and shunting operations within the jurisdiction section, and realizes centralized control through signal equipment such as interlocking, train control, and section blocking. It is an important driving equipment and command center for railway transportation. The centralized dispatching system adopts the principle of decentralized self-discipline design and uses distributed computing and control technology. On the basis of the train operation adjustment plan, it identifies the conflicts between train operations and shunting operations in time and space, and realizes unified control of train and shunting operations. Today, the CTC3.0 system is used in various scenarios of various railway bureaus and local railways. More large and complex stations, especially those with frequent shunting operations, have put forward higher requirements for the CTC3.0 system. In special stations such as the marshalling yard arrival yard, the CTC3.0 system cannot identify the peak route and the route cannot be parsed, resulting in the inability to activate the full function of the CTC system, which affects the station's use of the centralized dispatching system.

[0003] The push-up route is a route where the locomotive starts at the hump repeater signal at the arrival yard, pushes the train or vehicle to the push line, and ends at the unbranched section at the top of the hump. The push-up route generally exists in the arrival yard of a marshaling station. In order to adapt to the complex yard requirements of shunting operations, it is both a key and a difficult point to overcome the automatic and accurate analysis of the push-up route sequence at the arrival yard of a marshaling station.

[0004] For shunting operations at marshalling yards, there are various types of peak-pushing operations at arrival yards, high traffic density, and complex operation conditions, which lead to the following problems in the existing system:

[0005] 1. Peak pushing operations include not only single-machine peak-up and peak-down operations, but also single-group shunting and multi-group shunting operations. Single-machine peak-up and peak-down operations are treated as shunting routes, while shunting operations are treated as train routes (in accordance with the requirements of "6502 Electrical Concentrated Circuits"). However, the existing system cannot automatically identify the type of peak pushing operations, nor can it automatically parse the route type and the corresponding route sequence.

[0006] 2. The push-up operation cannot accurately resolve the hump track, and there is a risk of erroneously resolving it to a non-target hump track terminal, resulting in the wrong approach.

[0007] Therefore, in order to better meet the needs of pushing hump operations in the marshalling yard and arrival yard, a method that can automatically identify the type of pushing hump operations, accurately locate the target hump track and automatically analyze the corresponding shunting route or train route has emerged. Summary of the invention

[0008] The purpose of the present invention is to provide a method for peak path analysis of a CTC3.0 system, so as to solve the problems existing in the above-mentioned prior art.

[0009] In order to solve the above technical problems, the present invention is implemented by the following technical solutions:

[0010] A method for parsing a peak route in a CTC3.0 system, comprising: obtaining a shunting operation plan. Parsing the contents of the shunting operation plan using a station busy board terminal. When the hook type name of the hook type is X or D, matching the hump track type, and locating the terminal hump track as the target track of the peak route through the hump track type. Parsing the corresponding peak route according to the hook type ID and the hump track type. The automatically parsed peak route is saved in the station server in the form of a shunting hook plan for use in handling the peak route of the shunting operation.

[0011] Optionally, the step of obtaining the shunting operation plan includes: obtaining the shunting operation plan through the railway vehicle production operation system by means of a network interface or by local manual compilation, and sending it to the station busy board terminal.

[0012] Optionally, the step of using the station busy board terminal to parse the content of the shunting operation plan includes: the station busy board terminal parses the shunting operation plan to obtain the shunting track and the hook type information.

[0013] Optionally, the station busy board terminal pre-stores static shunting route data, static shunting rule data, static hook type data, static hump track data and static train route table data; the station busy board terminal configures and matches the hook type with the hook type in the static hook type data to obtain the hook type name and hook type ID of the hook type.

[0014] Optionally, when the hook type name is X, X represents multiple groups of slides from the upper peak; when the hook type name is D, D represents a single group of slides from the upper peak.

[0015] Optionally, when the hook type name is X, the hook type ID is 101; when the hook type name is D, the hook type ID is 102.

[0016] Optionally, the station busy board terminal locates the hump track attribute in the static hump track data through the hook type ID, and when the "hump track" attribute is identified, the terminal hump track is located as the target track of the push-hump route through the hump track attribute.

[0017] Optionally, the station busy board terminal automatically parses out the corresponding train route sequence according to the hook type ID, the hump track and the shunting track in the static hump track data, and the static train route table data.

[0018] Optionally, the station busy board terminal searches and calculates the train-related routes in the static train route table according to the hook type ID, the hump track in the static hump track data, and the shunting track, and parses to obtain the train route sequence in which the locomotive starts at the hump repeater signal and pushes the train or vehicle to the push line with the unbranched section at the hump top as the terminal.

[0019] Optionally, the peak route includes the train route sequence.

[0020] Optionally, it also includes: if the hook type name of the hook type is other, the hook type ID is a corresponding number within 100 1, 2, 3...

[0021] Optionally, it also includes: the station busy board terminal automatically parses out a corresponding shunting route sequence according to the hook type ID and the shunting track, based on the static shunting path data and the static shunting rule data.

[0022] Optionally, the shunting route sequence is a shunting route sequence with the starting track position as the starting point and the target shunting track as the end point.

[0023] Optionally, the peak-pushing route includes the shunting route sequence.

[0024] Optionally, the station busy board terminal is a station busy board terminal in the CTC3.0 system.

[0025] On the other hand, the present invention further provides an electronic device, including a processor and a memory, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the method described above is implemented.

[0026] In yet another aspect, the present invention further provides a readable storage medium, wherein the readable storage medium stores a computer program, and when the computer program is executed by a processor, the method described above is implemented.

[0027] The present invention has at least one of the following advantages:

[0028] The present invention provides a method for automatic parsing of CTC3.0 system peak route. Compared with the existing system, the method can realize automatic parsing of CTC peak route in the arrival yard of a marshaling station, realize the automatic parsing function of the route in the entire station, and improve the automation and intelligence level of the existing CTC3.0 system.

[0029] The present invention defines a binding method of the hook type name X / D and the special hook type ID number 101, 102, and matches the bus stop program logic in the station bus stop terminal, thereby providing a powerful configuration basis for realizing train route handling, train number tracking, and full-function activation of CTC shunting in complex marshaling stations, and significantly improving the efficiency, accuracy and safety of shunting operations in marshaling stations.

[0030] The present invention realizes accurate positioning of the target track when parsing the train route by pushing the hump route through accurate identification of the hump track type, thereby avoiding the risk of mis-arranging the route due to erroneous parsing to a non-target hump track terminal. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 A flowchart of a method for peak path analysis in a CTC3.0 system provided by an embodiment of the present invention;

[0032] Figure 2 A schematic diagram of a process flow of peak shunting route parsing in a method for peak shunting route parsing in a CTC3.0 system provided in one embodiment of the present invention;

[0033] Figure 3 A flowchart of peak train route parsing in a method for peak train route parsing in a CTC3.0 system provided in one embodiment of the present invention. DETAILED DESCRIPTION

[0034] The following is a further detailed description of a method for analyzing the peak path of the CTC3.0 system proposed by the present invention in combination with the accompanying drawings and specific embodiments. According to the following description, the advantages and features of the present invention will be clearer. It should be noted that the accompanying drawings are in a very simplified form and use non-precise proportions, which are only used to conveniently and clearly assist in explaining the purpose of the embodiments of the present invention. In order to make the purposes, features and advantages of the present invention more obvious and easy to understand, please refer to the accompanying drawings. It should be noted that the structures, proportions, sizes, etc. illustrated in the accompanying drawings of this specification are only used to match the contents disclosed in the specification for people familiar with this technology to understand and read, and are not used to limit the limiting conditions for the implementation of the present invention, so they have no technical substantive significance. Any modification of the structure, change in the proportional relationship or adjustment of the size, without affecting the effects that the present invention can produce and the purposes that can be achieved, should still fall within the scope of the technical content disclosed by the present invention.

[0035] Combination Figure 1 to Figure 3 As shown, this embodiment provides a method for analyzing a peak path in a CTC3.0 system, including:

[0036] Step S11, obtaining a shunting operation plan.

[0037] In this embodiment, the shunting operation plan is obtained through the railway vehicle production operation system (current vehicle system) using a network interface or local manual compilation, and is sent to the station busy board terminal in the CTC3.0 system.

[0038] Step S12: using the station busy board terminal to parse the contents of the shunting operation plan.

[0039] In this embodiment, the step S12 specifically includes: the station busy board terminal parses the shunting operation plan to obtain the information of the shunting track and hook type.

[0040] Step S13, determine the name of the hook type. When the hook type name is other (such as → or O, etc.), proceed to step S14; when the hook type name is X or D, proceed to step S15.

[0041] The step S13 includes: the station busy board terminal has pre-stored in the busy board software static shunting route data, static shunting rule data, static hook type data, static hump track data and static train route table data.

[0042] The station busy board terminal configures and matches the hook type with the hook type in the static hook type data to determine the hook type name of the hook type and obtain the hook type ID corresponding to the hook type name.

[0043] Step S14, when the hook type name of the hook type is other, the hook type ID corresponds to a number within 100 1, 2, 3...; (for example, → corresponds to 1, O corresponds to 2, etc.).

[0044] The station busy board terminal automatically parses out the corresponding shunting route sequence according to the hook type ID and the shunting track, the static shunting path data and the static shunting rule data.

[0045] In this embodiment, the shunting route sequence is a shunting route sequence with the starting track position as the starting point and the target shunting track as the end point; then, step 17 is entered.

[0046] Step S15, when the hook type name of the hook type is X or D, match the hump track type, and locate the terminal hump track as the target track of the push-hump route through the hump track type; enter step S16.

[0047] In this embodiment, when the hook type name is X, X represents multiple groups of slides from the upper peak; when the hook type name is D, D represents a single group of slides from the upper peak.

[0048] When the tick type name is X or D, the corresponding tick type ID is the special processing ID number 101 or 102.

[0049] Preferably, when the hook type name is X, the hook type ID is 101; when the hook type name is D, the hook type ID is 102.

[0050] In this embodiment, the step S15 further includes: the station busy board terminal locates the hump track attribute in the static hump track data through the hook type ID, and when the "hump track" attribute is identified, the terminal hump track is located as the target track of the push-hump route through the hump track attribute.

[0051] Step S16, the station busy board terminal automatically parses out the corresponding train route sequence according to the hook type ID, the static hump track data, the shunting track and the static train route table data, and enters step S17.

[0052] In this embodiment or some other embodiments, step S16 specifically includes: the station busy board terminal searches and calculates the train-related routes in the static train route table according to the hook type ID, the static hump track data and the shunting track, and parses to obtain the train route sequence in which the locomotive starts at the hump repeater signal and pushes the train or vehicle to the push line with the unbranched section at the hump top as the terminal.

[0053] Step S17, the automatically parsed peak route is saved in the station server in the form of a shunting hook plan, and can be used for the peak route processing of shunting operations.

[0054] In this embodiment, the peak-pushing route includes the shunting route sequence; and / or the peak-pushing route includes the train route sequence.

[0055] On the other hand, this embodiment further provides an electronic device, including a processor and a memory, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the method described above is implemented.

[0056] On the other hand, this embodiment further provides a readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the method described above is implemented.

[0057] In summary, this embodiment provides a method for automatic parsing of CTC3.0 system peak routes. Compared with the existing system, it realizes automatic parsing of CTC peak routes in the arrival yard of the marshalling station, realizes the automatic parsing function of the routes in the entire station, and improves the automation and intelligence level of the existing CTC system.

[0058] The binding method of hook types X, D and special hook type ID numbers 101, 102 defined in this embodiment matches the logic of the busy board program, providing a strong configuration foundation for realizing train route management, train number tracking, and full-function opening of CTC shunting in complex marshalling stations, and significantly improving the efficiency, accuracy and safety of shunting operations in marshalling stations.

[0059] This embodiment achieves accurate positioning of the target track when parsing the train route by pushing the hump route through accurate identification of the hump track type, thus avoiding the risk of mis-arranging the route due to erroneous parsing to a non-target hump track terminal.

[0060] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0061] It should be noted that the devices and methods disclosed in the embodiments of this article can also be implemented in other ways. The device implementation described above is only schematic. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to multiple embodiments of this article. In this regard, each box in the flowchart or block diagram can represent a part of a module, program or code, and the module, program segment or part of the code contains one or more executable instructions for implementing the specified logical function, and the module, program segment or part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart can be implemented by a dedicated hardware-based system for performing a specified function or action, or can be implemented by a combination of dedicated hardware and computer instructions.

[0062] In addition, the functional modules in the various embodiments of this document may be integrated together to form an independent part, or each module may exist independently, or two or more modules may be integrated to form an independent part.

[0063] Although the content of the present invention has been described in detail through the above preferred embodiments, it should be appreciated that the above description should not be considered as a limitation of the present invention. After reading the above content, it will be apparent to those skilled in the art that various modifications and substitutions of the present invention will occur. Therefore, the protection scope of the present invention should be limited by the appended claims.

Claims

1. A method for peak path analysis in a CTC3.0 system, characterized in that: include: Obtain shunting operation plan; Using the station bus terminal to analyze the contents of the shunting operation plan; The station busy board terminal pre-stores static shunting path data, static shunting rule data, static hook type data, static hump track data and static train route table data; the station busy board terminal configures and matches the hook type with the hook type in the static hook type data to obtain the hook type name and hook type ID of the hook type; When the hook type name is X or D, the hump track type is matched, and the hump track type is used to locate the terminal hump track as the target track for the push-hump approach; Specifically, the station busy board terminal locates the hump track attribute in the static hump track data through the hook type ID, and when the "hump track" attribute is identified, the terminal hump track is located as the target track of the push hump route through the hump track attribute; According to the hook type ID and the hump track type, the corresponding hump route is parsed; The automatically parsed peak-pushing route is saved in the station server in the form of a shunting hook plan for use in the peak-pushing route processing of shunting operations.

2. The method for peak path analysis of CTC3.0 system according to claim 1, characterized in that: The step of obtaining the shunting operation plan comprises: The shunting operation plan is obtained through the railway vehicle production operation system by means of a network interface or a local manual compilation method, and is sent to the station busy board terminal.

3. The method for peak path analysis of CTC3.0 system as claimed in claim 2, characterized in that: The step of using the station busy board terminal to analyze the content of the shunting operation plan includes: The station busy board terminal parses the shunting operation plan to obtain the information of the shunting track and the hook type.

4. The method for peak path analysis of CTC3.0 system as claimed in claim 3, characterized in that: When the hook type name is X, X means multiple groups of slides are released from the upper peak; when the hook type name is D, D means a single group of slides is released from the upper peak.

5. The method for peak path analysis of CTC3.0 system as claimed in claim 4, characterized in that: When the hook type name is X, the hook type ID is 101; when the hook type name is D, the hook type ID is 102.

6. The method for peak path analysis of CTC3.0 system as claimed in claim 5, characterized in that: The station busy board terminal automatically parses out the corresponding train route sequence according to the hook type ID, the static hump track data, the shunting track and the static train route table data.

7. The method for peak path analysis of CTC3.0 system as claimed in claim 6, characterized in that: The station busy board terminal searches and calculates the train-related routes in the static train route table according to the hook type ID, the static hump track data and the shunting track, and analyzes to obtain the train route sequence in which the locomotive starts at the hump repeater signal and pushes the train or vehicle to the push line with the unbranched section at the hump top as the terminal.

8. The method for peak path analysis of CTC3.0 system as claimed in claim 7, characterized in that: The peak route includes the train route sequence.

9. The method for peak path analysis of CTC3.0 system as claimed in claim 1, characterized in that: Also includes: If the hook type name of the hook type is other, the hook type ID is a corresponding number within 100, 1, 2, 3...

10. The method for peak path analysis of CTC3.0 system as claimed in claim 9, characterized in that: Also includes: The station busy board terminal automatically parses out the corresponding shunting route sequence according to the hook type ID and the shunting track, the static shunting path data and the static shunting rule data.

11. The method for peak path analysis of CTC3.0 system according to claim 10, characterized in that: The shunting route sequence is a shunting route sequence with the starting track position as the starting point and the target shunting track as the end point.

12. The method for peak path analysis of CTC3.0 system according to claim 11, characterized in that: The peak-pushing route includes the shunting route sequence.

13. The method for peak path analysis of CTC3.0 system according to claim 1, characterized in that: The station busy board terminal is the station busy board terminal in the CTC3.0 system.

14. An electronic device, characterized in that: The method comprises a processor and a memory, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the method according to any one of claims 1 to 13 is implemented.

15. A readable storage medium, characterized in that: The readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 13 is implemented.

Images