Railway dispatching command terminal supporting multi-point approval and system thereof

Abstract

The invention discloses a railway dispatching command terminal supporting multi-point approval and a system thereof, the system is deployed in the terminal, the system supports multi-point approval, and in combination with an automatic approval process, the manual transmission and confirmation time is shortened, and the approval speed is improved; examination and approval posts can be automatically matched according to command types, manual intervention is reduced, and unauthorized examination and approval and batch missing are prevented; in addition, cross-system state synchronization can be realized; real-time linkage of approval posts such as military special dispatchers and on-duty owners on the CTC side and the TDMS side is realized; meanwhile, the irreversibility of the approval process is ensured through rigid constraints (such as prohibiting deletion of an approval post and automatically resetting the state during re-approval); in addition, the dispatcher can master the state of each approval post in real time through a state visualization function, and abnormal conditions can be handled in time.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of railway transportation technology, and in particular to a railway dispatching command terminal supporting multi-point approval and a system thereof. BACKGROUND

[0002] Railway dispatching command approval is a core control link for train operation safety, involving multiple departments such as train operation, locomotive operation, and electric power operation. The traditional railway CTC (Centralized Traffic Control) dispatching command approval process relies on manual transmission and single-point authorization, and cannot meet the growing needs of practical applications. For example, a dispatching management requirement of a certain railway administration: some commands do not need to be approved, some commands only need to be approved by the shift leader of a certain zone, some commands need to be approved by the shift leader of a certain zone and the shift leader, and some commands need to be approved by the military and special dispatchers and the shift leader on the TDMS (Transportation Dispatching Management System) side. Therefore, the traditional CTC dispatching command approval process has the following industry pain points: (1) Cross-system coordination obstacles: The approval processes of CTC and TDMS are independent of each other, and real-time state synchronization of cross-department approval such as military and special dispatchers and emergency command cannot be achieved.

[0003] (2) Permission adaptation rigidity: The existing system uses static approval post configuration, and the commands are divided into commands that need to be approved and commands that do not need to be approved. The commands that need to be approved are only fixedly approved by the shift leader on the CTC side in a single point, and multi-point approval is not supported.

[0004] In addition, the existing system is a CTC dispatching command control system based on single-point approval, mainly manifested in: (1) only one approval post is supported; (2) the approval post can only be set on the CTC side; (3) when editing the command, the approval post can be manually selected or deselected; (4) the command that fails to pass the approval needs to be modified and then applied for approval again; (5) the command that passes the approval is issued to the station or locomotive by the train dispatcher.

[0005] Therefore, the existing system mainly has the following disadvantages: (1) unable to support multi-post coordination: when involving special departments such as military and special dispatchers and shift leaders on the TDMS side, offline coordination and communication are required, affecting the timeliness of the command. (2) Lack of permission control: the approval post can be manually deselected, which poses a risk of unauthorized issuance.

[0006] In addition, although there are currently automatic and cross-system approval schemes, for example, Chinese Patent Application for Invention No. CN113222539A “Approval Process Implementation Method and Device” and Chinese Patent Application for Invention No. CN110610315A “Cross-System Complete Process Workflow Approval Method”. However, the above schemes cannot be directly applied to multi-point cross-system automatic approval of railway dispatching commands.

[0007] Therefore, the present application is proposed. SUMMARY

[0008] The purpose of the present application is to provide a railway dispatching command terminal supporting multi-point approval and a system thereof, which can improve the approval speed, reduce manual intervention, avoid the risk of unauthorized issuance, and realize real-time linkage between the approval posts on the CTC side and the TDMS side.

[0009] The purpose of the present application is achieved by the following technical solutions: A railway dispatching command system supporting multi-point approval comprises: A TD interface subsystem is used to realize the transmission of information between the approval posts on the CTC side and the TDMS side by combining an interface server and an interactive protocol; wherein the CTC is a dispatching centralized system, and the TDMS is a transportation dispatching management system; An approval post topology management unit is used to realize the topology management of the approval posts by setting an approval post list, wherein the approval posts include the approval posts on the CTC side and the TDMS side; A dispatching command creation and editing unit is used to create a dispatching command according to the type of the current dispatching command by calling a corresponding dispatching command template, and to edit the dispatching command; An approval post dynamic matching unit is used to automatically match the corresponding approval post in the approval post list according to the type of the current dispatching command; An approval process triggering unit is used to determine whether to trigger the approval process according to the received external control command; if yes, the dispatching command is sent to the matched approval post; A multi-level approval state machine is used to update the state of the dispatching command in combination with the signed receipt state of each approval post.

[0010] A railway dispatching command terminal supporting multi-point approval, wherein the terminal is deployed with the system described above; after the multi-point approval of the dispatching command by the deployed system, if the state of the dispatching command is approved, the dispatching command is issued to the station or the locomotive.

[0011] As can be seen from the technical solutions provided by the present application, the approval posts can be automatically matched according to the type of the command, manual intervention is reduced, unauthorized approval and missed approval are prevented, cross-system cooperation is introduced, information transmission between the approval posts of different systems is realized, multi-point approval is supported, the time for manual transmission and confirmation is reduced in combination with the automatic approval process, and the approval speed is improved. BRIEF DESCRIPTION OF DRAWINGS

[0012] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed in the embodiment description will be briefly introduced as follows. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0013] Figure 1A schematic diagram of a railway dispatch command system supporting multi-point approval provided by an embodiment of the present application.

[0014] Figure 2 A schematic diagram of an approval post list provided by an embodiment of the present application.

[0015] Figure 3 A system pop-up prompt schematic diagram in an approval process trigger link provided by an embodiment of the present application.

[0016] Figure 4 A schematic diagram of a trigger re-issuing mechanism provided by an embodiment of the present application.

[0017] Figure 5 A system pop-up prompt schematic diagram in a re-issuing mechanism provided by an embodiment of the present application.

[0018] Figure 6 A state reset schematic diagram of an approval post under a re-examination mechanism provided by an embodiment of the present application.

[0019] Figure 7 A state visualization schematic diagram provided by an embodiment of the present application.

[0020] Figure 8 A system pop-up prompt schematic diagram when no approval post is selected in a station authorization link provided by an embodiment of the present application.

[0021] Figure 9 A system pop-up prompt schematic diagram when an approved approval post is selected in a station authorization link provided by an embodiment of the present application. DETAILED DESCRIPTION

[0022] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without creative labor fall within the protection scope of the present application.

[0023] First, the terms that can be used in this text are described as follows: The terms “include”, “contain”, “have”, “possess” or other similar semantic descriptions should be interpreted as non-exclusive inclusion. For example: including a technical feature element (such as raw materials, components, ingredients, carriers, dosage forms, materials, sizes, parts, components, mechanisms, devices, steps, processes, methods, reaction conditions, processing conditions, parameters, algorithms, signals, data, products or articles, etc.), should be interpreted as not only including the explicitly listed technical feature element, but also including other technical feature elements that are not explicitly listed but are well known in the art.

[0024] The term "consisting of" denotes an exclusion of any element, not explicitly listed. If the term is used in the claims, the term will make the claims closed and will not include any element, not specified in the claims. If the term is only used in the description, it will only serve to define the scope of the application, but will not exclude any element, not specified in the claims, from the application.

[0025] Unless otherwise defined, the terms "mounting", "connected", "connecting", "fixed", and the like are to be construed in a broad sense, for example: can be fixed connection, can also be detachable connection, or integral connection; can be mechanical connection, can also be electrical connection; can be directly connected, can also be indirectly connected through an intermediate medium, can be internal communication of two elements. For those skilled in the art, the specific meaning of the above terms in this paper can be understood according to the specific circumstances.

[0026] A railway dispatch command terminal supporting multi-point approval and a system thereof provided by the present application are described in detail below. The contents not described in detail in the embodiments of the present application belong to the prior art known to those skilled in the art. If no specific conditions are specified in the embodiments of the present application, the conventional conditions or the conditions recommended by the manufacturer are followed. If no manufacturer of the reagent or instrument used in the embodiments of the present application is specified, it is a conventional product that can be obtained by market purchase.

[0027] Embodiment one The embodiments of the present application provide a railway dispatch command system supporting multi-point approval, as shown in Figure 1 The main components are as follows: A TD interface subsystem is used to combine an interface server and an interactive protocol to realize the transmission of information between the approval posts of CTC side and TDMS side; wherein, the CTC is a dispatch centralized system, and the TDMS is a transportation dispatch management system; An approval post topology management unit is used to realize the topology management of the approval post through the set approval post list, wherein the approval post includes the approval post of CTC side and TDMS side; A dispatch command creation and editing unit is used to create a dispatch command according to the type of the current dispatch command by calling the corresponding dispatch command template, and to edit it; An approval post dynamic matching unit is used to automatically match the corresponding approval post according to the type of the current dispatch command and the approval post list; An approval flow triggering unit is used to judge whether to trigger the approval flow according to the received external control command; if yes, the dispatch command is sent to the matched approval post; A multi-level approval state machine is used to update the dispatch command state in combination with the receipt state of each approval post.

[0028] Preferably, the system further comprises a reissue and review unit for reissuing the dispatch command to a designated approval post or re-sending the dispatch command to all matched approval posts.

[0029] Preferably, the system further comprises a state visualization unit for displaying the receipt and receipt feedback state of each approval post corresponding to each dispatch command.

[0030] Preferably, the system further comprises a dispatch command deletion unit for deleting the dispatch command that has been approved or not approved.

[0031] Preferably, the system further comprises a station authorization unit for granting approval authority to a new approval post.

[0032] In the embodiment of the application, the automatic matching of the corresponding approval post in the approval post list according to the type of the current dispatch command comprises: automatically checking the approval post in the approval post list according to the type of the current dispatch command, or checking the designated approval post in combination with the external input command, and all the checked approval posts are the matched approval posts; and after triggering the approval process, all the matched approval posts are in a locked state and cannot perform the adding or deleting operation.

[0033] In the embodiment of the application, the updating of the dispatch command state in combination with the receipt feedback state of each approval post comprises: when the dispatch command is created, the state is in a to-be-approved state; when the receipt feedback state of each approval post is agreed, the state is updated to an approved state; and when the receipt feedback state of any approval post is refused, the state is updated to an unapproved state.

[0034] In the embodiment of the application, the reissuing of the dispatch command to the designated approval post comprises: after the dispatch command is sent to the matched approval post, if no automatic receipt of a certain approval post is received, the dispatch command is reissued to the corresponding approval post.

[0035] In the embodiment of the application, the re-sending of the dispatch command to all the matched approval posts comprises: after the dispatch command is sent to the matched approval post, if the state of the dispatch command is unapproved, the dispatch command is re-sent to all the matched approval posts through a review mechanism, and the state of the dispatch command is reset; wherein the re-sent dispatch command can be the unapproved dispatch command or the dispatch command after the content is adjusted.

[0036] The above-mentioned scheme provided by the embodiment of the application mainly has the following beneficial effects: (1) Approval efficiency is improved: automatic approval process reduces the time of manual delivery and confirmation, and improves the approval speed; the time consumption of approval process is reduced by 40% (from 15 minutes to 3 minutes on average).

[0037] (2) Security is enhanced: strict permission management and state monitoring mechanism prevent unauthorized approval and missing approval, and the risk of unauthorized operation is reduced by 90%.

[0038] (3) Real-time monitoring: the state visualization function enables the dispatcher to monitor the state of each approval post in real time, facilitating the timely handling of abnormal situations.

[0039] (4) Compatibility optimization: seamless integration of TDCS / TDMS heterogeneous systems is supported, and the approval coverage rate of special departments such as military special dispatch and shift director is improved to 100%.

[0040] In order to more clearly show the technical solutions provided by the present application and the technical effects generated, the system provided by the embodiments of the present application is described in detail below with specific examples.

[0041] I. Introduction of each part of the system.

[0042] 1. Approval post topology management.

[0043] The existing approval posts on the TDMS side, such as military special dispatch and shift director network deployment, are maintained as they are, and the CTC side accesses the system through the TD interface server to realize the transmission of approval-related information. According to actual needs, military special dispatch, shift director and other TDMS-side approval posts are added in the ordered unit of the CTC dispatch command terminal. In order to facilitate management, an approval post list is added to the interface of the CTC dispatch command terminal, as shown in Figure 2 Figure 2 In the above, the "partition shift director" displayed in the approval post list is the partition shift director on the CTC side; the "shift director" is the approval post on the TDMS side.

[0044] In addition, in order to automatically match the approval post subsequently, according to the dispatch command management process requirements of the dispatch office, the required approval post is configured according to the dispatch command template type, including the number, approval post identifier, etc. Among them, the approval post identifier needs to be agreed by both parties of the command interaction, and the numbering rules of CTC and TDMS may be different.

[0045] In the embodiments of the present application, the dispatch command has the following key elements: command template type, command text, station ordered point, wireless ordered point, ordered place text, etc.

[0046] 2. Dynamic matching mechanism of approval post.

[0047] ​According to the approval process of each railway bureau, the required approval post is configured for different dispatching post according to the type of dispatching command template (related to the type of dispatching command). In actual application, the matched post to be approved can be found from the approval post category, and the check box is automatically set as the approval post of the current dispatching command.

[0048] During the process of creating a new dispatching command by the train dispatcher, the corresponding approval post is automatically checked when selecting the dispatching command template. The approval post can be set on the CTC side or the TDMS side.

[0049] 3. Approval process triggering.

[0050] After the dispatching command is edited, the user clicks "Apply for Approval", and the system prompts as shown in Figure 3 The prompt contains cancel and confirm buttons. If the confirm button is clicked, the approval process is triggered, and the dispatching command is sent to the matched approval post. If the cancel button is clicked, the process is terminated.

[0051] 4. Multi-level approval state machine.

[0052] The command state includes: pending approval (0x01), approval passed (0x02), and approval failed (0x03).

[0053] The command that needs approval is created as "pending approval". Only when all approval posts agree, the command state is updated to "approval passed", and the command can be issued to the station or locomotive. If any approval post refuses, the command state is set to "approval failed". The command that fails to pass the approval cannot be authorized and can only be re-applied for approval.

[0054] The multi-level approval state machine updates the command state according to the receipt status code of each approval post.

[0055] 5. Reissue and re-examination mechanism.

[0056] The reissue mechanism is mainly for the approval posts that do not receive automatic receipts, and a prompt box is displayed. As shown in Figure 4 The automatic receipt of the duty officer approval post is not received, so the reissue mechanism is triggered, and a prompt box is displayed, as shown in Figure 5 When the user clicks the "Yes" button, the reissue and re-examination unit will receive the corresponding control information and send the dispatching command to the duty officer again.

[0057] The re-examination mechanism is mainly for the dispatching command that fails to pass the approval. The content of the dispatching command can be edited (the approval post cannot be changed), and then the approval process triggering link is returned again. After clicking "Apply for Approval", the dispatching command is sent to all matched approval posts again, as shown in Figure 3All the status of the approval post (whether accepted, signed state) are reset, as shown in Figure 6

[0058] 6. Status visualization.

[0059] The CTC / TDMS terminal displays the real-time status of each approval post, and the icon code represents different states, which facilitates the dispatcher to monitor and handle abnormal situations, as shown in Figure 7

[0060] Figure 7 The first behavior is editing, the second behavior is no receipt during approval, the third behavior is automatic receipt during approval, the fourth behavior is signed receipt during approval, and the signed receipt is approval, and the fifth behavior is signed receipt during approval, and the signed receipt is rejection.

[0061] 7. Forced interlocking constraint.

[0062] (1) The automatically selected approval post is not allowed to be manually selected.

[0063] (2) Once the approval process is started (approval in progress, approval passed, and approval failed), the approval post cannot be increased or decreased.

[0064] (3) Both the approval passed and the rejection command can be deleted.

[0065] 8. On-site authorization.

[0066] Considering that the approval post personnel may not be able to sign the command in time under some special scenarios, the on-site authorization function is added.

[0067] Select the approval post, and you can authorize one by one.

[0068] If the approval post is not selected, when the "authorization" is clicked, a pop-up box is prompted as shown in Figure 8 If the selected approval post has been approved, the pop-up box is prompted as shown in Figure 9 .

[0069] 9. Cross-system collaboration based on TD interface subsystem.

[0070] The TD interface subsystem described in the present application is the TD interface server set in the existing CTC system, which supports functions such as receiving the dispatching command from the TDMS side by the CTC dispatching command terminal, sending the dispatching command to the terminal on the TDMS side, etc.

[0071] ​​When the approval post is set up on the TDMS side, the existing TD integration protocol is expanded by adding information flow related to scheduling command approval application and approval opinion. This enables the approval process of the CTC side to the TDMS side approval post. Specifically, in order to realize the function of sending command approval application to the TDMS side approval post and receiving approval results, the CTC internal scheduling information protocol is expanded. For example, two subtypes are added: 0x1A = application approval and 0x1B = approval result.

[0072] II. System Flow Introduction.

[0073] The following section uses an application scenario from a railway bureau as an example to introduce the main workflow of this system.

[0074] On the CTC side, one approval post (District Duty Supervisor) is set up, and on the TDMS side, two approval posts are set up (Military Special Dispatch, Duty Supervisor). When the dispatcher selects the dispatch command template "Change Train Route," the system automatically selects the "District Duty Supervisor" and "Duty Supervisor" approval posts. After the dispatcher selects the relevant stations, adds the relevant train numbers, fills in the command text, and confirms that the command is correct, they click the "Issue" button, and the command is automatically sent to the corresponding approval post. Commands sent to the "District Duty Supervisor" are directly delivered within the CTC system, and the District Duty Supervisor's approval opinion is also directly returned to the system. Commands sent to the "Duty Supervisor" are converted by the TD interface subsystem into a command approval application as required by the "Data Exchange Regulations between the Transportation Information Integration Platform and the Transportation Dispatch Management System (TDMS), Train Dispatch Command / Dispatch Centralization System (TDCS / CTC)" before being issued. After receiving the application, the Duty Supervisor checks the command content. If there are no objections, an approval receipt is sent; if an error is found, a rejection receipt is sent. The receipt is converted into the approval result of the CTC internal protocol by the TD interface subsystem and then sent to the system. If a rejection receipt is received from any approval post, the "Change Train Route" command needs to be modified and re-approved. Only when approval receipts are received from all approval posts is the "Change Train Route" dispatching command approved and can be further issued to the station and locomotive.

[0075] Based on the above solution, the system of the present invention has the following advantages: (1) Dynamic permission adaptation: Automatically match the approval post according to the command type to reduce manual intervention.

[0076] (2) Cross-system status synchronization: Real-time linkage between the approval positions such as military special investigation and duty director on the CTC side and TDMS side.

[0077] (3) Ensure the atomicity of the process: The approval process is irreversible through rigid constraints (such as prohibiting the deletion of the approval post, automatically resetting the status when re-approving).

[0078] Optionally, the blockchain technology can be introduced in the embodiments of the present application. (1) Blockchain node: each approval post is a blockchain node, which stores and verifies the dispatching command. (2) Smart contract: the approval rules are defined by the smart contract, and the approval process is automatically executed. (3) Distributed ledger: all approval records are stored in the distributed ledger to ensure that the data cannot be tampered with.

[0079] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the division of the above functional modules is taken as an example for illustration, and in actual application, the above functions can be completed by different functional modules according to needs, that is, the internal structure of the system is divided into different functional modules to complete all or part of the functions described above.

[0080] Embodiment two The embodiments of the present application also provide a railway dispatching command terminal supporting multi-point approval, which is provided with the system of the aforementioned embodiment one; after the multi-point approval of the dispatching command by the deployed system, if the state of the dispatching command is approved, the dispatching command is issued to the station or the locomotive. In actual application, the terminal can specifically include a CTC terminal configured on the CTC side and a TDMS terminal configured on the TDMS side.

[0081] Of course, the terminal must also include a matching hardware device, but the present application does not limit the specific hardware, which can be configured by the user in actual application, and can meet the deployment and normal use of the system. The terminal is usually configured in the dispatching center and the higher-level management area, the dispatchers in the dispatching center can issue the dispatching command through the terminal, and the managers in the management area serve as the approval post to approve the received dispatching command.

[0082] The above is only a preferred specific implementation of the present application, but the protection scope of the present application is not limited to this, any changes or replacements within the technical range disclosed in the present application can be easily thought of by those skilled in the art, which should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims. The information disclosed in the background section of the present application is only intended to deepen the understanding of the overall background of the present application, and should not be regarded as acknowledging or implying in any form that the information constitutes prior art known to those skilled in the art.

Claims

1. A railway dispatching command system supporting multi-point approval, characterized in that, include: The TD interface subsystem is used to combine the interface server and the interaction protocol to realize the transmission of information between the approval positions on the CTC side and the TDMS side; wherein, CTC is a centralized dispatch system and TDMS is a transportation dispatch management system. The Approval Post Topology Management Unit is used to manage the topology of approval posts through a set list of approval posts, which includes approval posts on both the CTC side and the TDMS side. The scheduling command creation and editing unit is used to create scheduling commands by calling the corresponding scheduling command template according to the type of the current scheduling command, and then edit them. The approval post dynamic matching unit is used to automatically match the corresponding approval post in the approval post list based on the type of the current scheduling command; The approval process triggering unit is used to determine whether to trigger the approval process based on the received external control command; if so, it sends the scheduling command to the matching approval post. A multi-level approval state machine is used to update the status of scheduling commands by combining the signed receipt status of each approval post.

2. The railway dispatching command system supporting multi-point approval according to claim 1, characterized in that, The step of automatically matching the corresponding approval post in the approval post list based on the type of the current scheduling command includes: Based on the type of the current dispatch command, the approval positions are automatically selected from the list of approval positions, or the specific approval positions are selected by combining external input commands. All the selected approval positions are the matching approval positions. Furthermore, once the approval process is triggered, all matching approval positions are locked, and cannot be added or deleted.

3. A railway dispatching command system supporting multi-point approval according to claim 1, characterized in that, The step of updating the scheduling command status by combining the signed receipt status of each approval post includes: When a scheduling command is created, it is in a pending approval state; When the status of the signed receipt from each approval post is "approved", update it to "approved". When the status of the signed receipt for any approval post is rejected, it is updated to the status of approval not approved.

4. A railway dispatching command system supporting multi-point approval according to claim 1, characterized in that, The system also includes a reissue and re-review unit, used to reissue scheduling orders to designated approval positions or resend scheduling orders to all matching approval positions.

5. A railway dispatching command system supporting multi-point approval according to claim 4, characterized in that, The step of reissuing the scheduling command to the designated approval post includes: after the scheduling command is sent to the matching approval post, if no automatic acknowledgment is received from the approval post, then the scheduling command is reissued to the corresponding approval post.

6. A railway dispatching command system supporting multi-point approval according to claim 4, characterized in that, The step of resending the scheduling command to all matching approval posts includes: When a scheduling command is sent to a matching approval post, if the status of the scheduling command is "approved but not approved", the scheduling command will be resent to all matching approval posts through the re-approval mechanism, and the status of the scheduling command will be reset. The resent scheduling command is either the scheduling command that failed to pass approval or the scheduling command with revised content.

7. A railway dispatching command system supporting multi-point approval according to claim 1, characterized in that, The system also includes a status visualization unit, which displays the receipt and signing status of each approval post corresponding to each scheduling command.

8. A railway dispatching command system supporting multi-point approval according to claim 1, characterized in that, The system also includes a scheduling command deletion unit, used to delete scheduling commands that have been approved or have not been approved.

9. A railway dispatching command system supporting multi-point approval according to claim 1, characterized in that, The system also includes an on-site authorization unit, used to grant approval authority to new approval positions.

10. A railway dispatching command terminal supporting multi-point approval, characterized in that, The terminal is equipped with the system described in any one of claims 1 to 9; after the dispatching command is approved by multiple points through the deployed system, if the status of the dispatching command is approved, it is issued to the station or locomotive.

Images