Urban rail working diagram whole-line network cooperation method and system oriented to heterogeneous signal system

Abstract

The embodiment of the invention provides a heterogeneous signal system-oriented urban rail working diagram whole-line network collaboration method and system, and is applied to the technical field of rail traffic signals. The method comprises the following steps: starting a timed task at a preset moment, and obtaining a global loading plan from an M private database; generating a global intraday running diagram according to the global loading plan and writing the global intraday running diagram into an M private database; splitting the global day running diagram according to lines to obtain line day running diagrams corresponding to the lines, and respectively writing the line day running diagrams into single line databases of the corresponding lines; and pushing the current-day running diagram of the line to the corresponding actual line equipment by using the line application server. In this way, non-inductive operation can be achieved for the accessed network heterogeneous signal system.

Description

Technical Field

[0001] This disclosure relates to the field of rail transit signaling technology, and in particular to a method and system for coordinated operation of urban rail transit timetables across the entire network for heterogeneous signaling systems. Background Technology

[0002] In urban rail transit operations, in single-line operation scenarios, the globally planned operation schedule needs to be exported as a timetable file by the network planner, and then imported offline by the line operator into the line signaling system and loaded into the line's operation plan list. In interconnection scenarios, the operation plan is issued globally to the line operator, and after the line operator stores it in its own database, the line operator's dispatcher needs to reload it into the operation plan list.

[0003] However, this model has obvious drawbacks: First, the signal systems of different lines come from different manufacturers and have different system architectures, so the loading of planned schedules and the loading of daily schedules depend on the line dispatching; second, the line dispatching only focuses on the train operation plan of its own line, while in actual operation, the lines are closely connected by transfers and cross-line interconnections, requiring a holistic planning of the operation plan, which the existing system cannot meet the needs of the entire network for collaborative management; third, after the global dispatching formulates and issues the global plan for multi-line interconnection, the global equipment cannot directly intervene in the line operation plan, resulting in limited operability. Summary of the Invention

[0004] This disclosure provides a method and system for coordinated operation of urban rail transit timetables across the entire network for heterogeneous signaling systems. It solves the technical problems in urban rail transit networks with heterogeneous signaling systems, where each line relies on its own scheduling, making it difficult to coordinate the timetable globally, and where global equipment has limited intervention in line plans, thus failing to achieve unified management of multiple line timetables, fully automatic loading, and flexible operation of both global and single-line timetables.

[0005] According to a first aspect of this disclosure, a method for coordinated operation of urban rail transit network-wide timetables for heterogeneous signaling systems is provided. The method includes: A scheduled task is started at a preset time to retrieve the global loading plan from the M private database; Generate a global daily operation chart based on the global loading plan and write it to the M private database; The global daily operation map is split by line to obtain the daily operation map of each line, and written into the single-line database of the corresponding line respectively. The daily operation map of the line is pushed to the corresponding actual line equipment using the line application server.

[0006] In addition to the aspects and any possible implementations described above, a further implementation is provided, wherein the method further includes: A runtime graph interface with a split-view architecture is built in the global device, and a database logical isolation method is used to build an M private database and multiple single-line databases.

[0007] In addition to the aspects and any possible implementations described above, a further implementation is provided, wherein the construction of a runtime graph interface with a split-view architecture in a global device, and the construction of an M private database and multiple single-line databases using a database logical isolation method, includes: The split-view architecture's runtime interface includes a single-line view and a global view. The single-line view supports direct manipulation of the corresponding line's runtime plan, while the global view supports loading network-level interconnection runtime diagrams. Load plans generated by a single-line view are stored in a single-line database, while load plans generated by a global view are stored in an M-private database.

[0008] In addition to the aspects and any possible implementations described above, a further implementation is provided, wherein splitting the global daily operation map by line to obtain the daily operation map corresponding to each line, and writing them into the single-line database of the corresponding line, includes: In the single-line view, a loading plan is independently formulated for the selected single line, and the daily operation chart of the single line is directly written into the corresponding single-line database. In the global view, if a global loading plan has been created for a single line, it is prohibited to create an independent loading plan for that single line again; conversely, if an independent loading plan has been created for a single line, it is prohibited to create a global loading plan for that single line.

[0009] In addition to the aspects and any possible implementations described above, a further implementation is provided in which the step of pushing the daily operation map of the line to the corresponding actual line equipment using the line application server includes: The daily operation map of the line is stored in the corresponding line logical database using the line application server. The line interface machine sends the daily line operation diagram stored in the line logic database to the actual line equipment of the line.

[0010] In addition to the aspects and any possible implementations described above, a further implementation is provided, wherein the method further includes: The actual line equipment will upload the execution data of the operation diagram to the line application server through the line interface machine; The line application server writes execution data into the line logic database; the line logic database centrally stores historical operation graph data.

[0011] In addition to the aspects and any possible implementations described above, a further implementation is provided, wherein the method further includes: Receive manually triggered network plan operation instructions, the network plan operation instructions including network plan writing instructions or network plan deletion instructions; According to the network plan operation instructions, write or delete the global daily operation map to the M private database, and at the same time write or delete the split line daily operation map to the corresponding single line database. Send execution instructions matching the network plan operation instructions to the application servers of each line; Receive the operation results from the application servers on each line, and output the prompt information of the operation results through the cluster front end.

[0012] According to a second aspect of this disclosure, a city rail transit network-wide coordinated system for heterogeneous signaling systems is provided. The system includes: The acquisition module is used to start a scheduled task at a preset time and retrieve the global loading plan from the M private database; The generation module is used to generate a global daily running chart based on the global loading plan and write it to the M private database; The writing module is used to split the global daily operation map by line to obtain the daily operation map of each line, and write it into the single-line database of the corresponding line respectively. The push module is used to push the daily operation map of the line to the corresponding actual line equipment using the line application server.

[0013] According to a third aspect of this disclosure, an electronic device is provided. The electronic device includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the program to implement the method described above.

[0014] According to a fourth aspect of this disclosure, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the methods according to the first and / or second aspects of this disclosure.

[0015] In this disclosure, the application server proactively initiates scheduled tasks instead of relying on manual line scheduling. It retrieves the global loading plan from the M private database and generates the operation diagram, eliminating the need for line operators to formulate separate loading strategies. This achieves fully automated distribution of the network-level operation diagram without human intervention, significantly reducing scheduling costs and the probability of human error. By splitting the global diagram into a layered process, it avoids direct connection of global devices to various heterogeneous line signal systems. Instead, the line side receives data according to its own system characteristics, ensuring that different signal systems can accurately receive the operation diagram, thus achieving compatibility between global coordination and heterogeneous adaptation.

[0016] It should be understood that the description in the Summary of the Invention is not intended to limit the key or essential features of the embodiments of this disclosure, nor is it intended to restrict the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0017] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. The drawings are provided for a better understanding of the invention and are not intended to limit the scope of this disclosure. In the drawings, the same or similar reference numerals denote the same or similar elements, wherein: Figure 1 A flowchart is shown for a method of coordinating the entire urban rail transit network for heterogeneous signaling systems, according to an embodiment of the present disclosure. Figure 2 A block diagram of a city rail transit timetable network-wide collaborative system for heterogeneous signaling systems, according to an embodiment of the present disclosure, is shown. Figure 3 A block diagram of an exemplary electronic device capable of implementing embodiments of the present disclosure is shown. Detailed Implementation

[0018] To make the objectives, technical solutions, and advantages of the embodiments of this disclosure clearer, the technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this disclosure.

[0019] Furthermore, the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0020] In this disclosure, the application server proactively initiates scheduled tasks instead of relying on manual line scheduling. It retrieves the global loading plan from the M private database and generates the operation diagram, eliminating the need for line operators to formulate separate loading strategies. This achieves fully automated distribution of the network-level operation diagram without human intervention, significantly reducing scheduling costs and the probability of human error. By splitting the global diagram into a layered process, it avoids direct connection of global devices to various heterogeneous line signal systems. Instead, the line side receives data according to its own system characteristics, ensuring that different signal systems can accurately receive the operation diagram, thus achieving compatibility between global coordination and heterogeneous adaptation.

[0021] Figure 1 A flowchart of a method 100 for coordinated operation of urban rail transit timetables across the entire network, according to an embodiment of this disclosure, is shown. Figure 1 As shown, method 100 includes: S101, at a preset time, starts a scheduled task to obtain the global loading plan from the M private database.

[0022] In some embodiments, a runtime graph interface of a split-view architecture is constructed in a global device, and a database logical isolation method is used to construct an M private database and multiple single-line databases.

[0023] In some embodiments, the runtime interface of the split-view architecture includes a single-line view and a global view. The single-line view supports direct operation of the runtime plan of the corresponding line, while the global view supports loading the network-level interconnection runtime diagram. Load plans generated by a single-line view are stored in a single-line database, while load plans generated by a global view are stored in an M-private database.

[0024] Specifically, in the global device, the operation diagram interface is designed with a split-view architecture. The system supports switching between multiple single-line views and interconnected global views. In each single-line view, the operation plan of a single line can be directly manipulated, and in the multi-line view, the operation diagram of the interconnected network can be loaded. Multiple single-line databases and M private databases are established using a database logical isolation method. The loading plan generated by the single-line view is stored in the single-line database, and the loading plan generated by the multi-line view is stored in the M private database. The operation diagram data of each line is logically isolated, but can be managed in a unified manner.

[0025] In some embodiments, the scheduled task is initiated by the overall application server to ensure that the task is executed stably during non-peak operating periods. The clock of the overall application server and the global device cluster are synchronized through the NTP (Network Time Protocol) server to ensure that the time error of all devices is ≤1 second, and to prevent the scheduled task triggering delay due to clock inconsistency.

[0026] In some embodiments, after a scheduled task is started, the system will generate a log in the application server log module to record the task ID, trigger time, current load status, and task status (starting / started). The log is kept for 30 days to facilitate subsequent fault tracing. If the task is not triggered, the log can be used to query whether it is due to excessive load or clock abnormality.

[0027] In some embodiments, after the scheduled task starts, the application server coordinates the process of targeted request + permission verification + data verification to read the global loading plan that meets the conditions from the M private database, ensuring that the obtained data is accurate and available.

[0028] S102, Generate a global daily running chart based on the global loading plan and write it to the M private database.

[0029] In some embodiments, the generation process must adhere to three insurmountable constraints to ensure that the operational plan complies with urban rail transit safety operation standards: Time constraints: The departure / arrival times of all trains must fall within the first and last train times of the corresponding line; the stopping time of cross-line trains at transfer stations must be greater than or equal to the walking time for transfers within the station; Safety constraints: The departure interval between two adjacent trains on the same line is greater than or equal to the minimum safe interval; the train running time within a section is greater than or equal to the standard running time. Resource constraints: The number of trains participating in operation is less than or equal to the total number of trains available on the day; the passenger capacity of trains during peak hours is less than or equal to 120% of the rated passenger capacity of each carriage.

[0030] In some embodiments, the generated visual running graph is converted into structured data, such as data table records, and written to the M private database.

[0031] S103, the global daily operation map is split by line to obtain the daily operation map of each line, and written into the single-line database of the corresponding line respectively.

[0032] In some embodiments, under a single-line view, a loading plan is independently formulated for the selected single line, and the daily operation chart of the single line is directly written into the corresponding single-line database. In the global view, if a global loading plan has been created for a single line, it is prohibited to create an independent loading plan for that single line again; conversely, if an independent loading plan has been created for a single line, it is prohibited to create a global loading plan for that single line.

[0033] In some embodiments, the splitting of the global daily operation map needs to be based on line affiliation rules and data adaptation requirements. At the same time, it is necessary to establish a mapping relationship between global data and single-line database in advance to ensure that the split data can be recognized by the single-line signal system.

[0034] In some embodiments, the application server automatically executes the global daily operation map by line, and performs splitting, transformation and writing for each line one by one.

[0035] Specifically, the application server filters global train data by line. For a target line, it filters train records belonging to that line from the M private database. For each filtered train record, it extracts its running data on the target line, converts the running data into a new format, and writes it into the corresponding single-line database through a security mechanism.

[0036] In some embodiments, the operation diagram of any single line can be operated independently without affecting other lines in the network, thus meeting the temporary adjustment needs of a single line.

[0037] Specifically, the view switch must be completed first to ensure that the operation corresponds to the target line; the loading or deletion plan formulated under the single line view only includes the parameters of this line and does not involve cross-line data; after the independent loading plan is formulated, an independent daily operation chart for this line is generated and written to the corresponding single line database.

[0038] In some embodiments, to prevent two different versions of the running plan from appearing on the same line, which could lead to device conflicts, a line cannot have both a global loading plan and a single-line loading plan at the same time.

[0039] Specifically, if a single-line loading plan has been formulated for Line 1, and Line 1 needs to adjust its time separately due to construction, Line 1 will be automatically excluded from the global loading plan and cannot be included in the global plan; if the global loading plan already includes Line 1, and Line 1 participates in cross-line operation, then a single-line loading plan cannot be formulated for Line 1.

[0040] S104 uses the line application server to push the daily line operation map to the corresponding actual line equipment.

[0041] In some embodiments, the daily operation map of the line is stored in the corresponding line logical database using the line application server. The daily line operation diagram stored in the line logic database is sent to the actual line equipment via the line interface machine. In some embodiments, the actual line equipment uploads the execution data of the running diagram to the line application server through the line interface machine; The line application server writes execution data into the line logic database; the line logic database centrally stores historical operation graph data.

[0042] In some embodiments, since the actual equipment on each line (such as signal lights, train dispatching terminals, and platform displays) comes from different manufacturers (heterogeneous systems), their data interface protocols and data formats differ significantly. It is necessary to build an adaptation channel in advance between the line application server, the line interface machine, and the actual equipment to ensure that the data can be transmitted correctly and identified accurately.

[0043] Specifically, the line logic database is the core carrier for runtime graph push buffering and execution data storage, and needs to be deployed independently for each line, using a MySQL master-slave architecture. The line interface machine is the "translator" between the line application server and the actual equipment. It needs to be configured with dedicated protocol conversion rules for equipment from different manufacturers. Each line should be configured with 1-2 line interface machines (master and backup redundancy to prevent single point of failure). The interface machine needs to support multiple types of physical interfaces and adapt to the connection methods of different devices.

[0044] Specifically, the overall application server sends instructions to the line application server, which then stores the current line's operation diagram in the line logical database. This data is then distributed to the actual line equipment by the line interface machine. Simultaneously, the actual line equipment uploads real-time operation data while executing the line operation diagram. This data is received by the line application server and written into the line logical database, enabling centralized storage and traceability of historical data.

[0045] In some embodiments, the line logic database centrally stores historical execution data, supporting dispatchers and maintenance personnel to query and analyze it.

[0046] Specifically, the system provides a historical data query interface in the single-line view of global equipment, allowing users to filter data by date, line, train number, and equipment type. The system automatically compiles historical data to generate on-time rate reports and equipment failure rate reports, which can be exported to Excel format. When operational anomalies occur (such as a train being 10 minutes late), the cause can be traced through historical data—by querying the actual time the train passed each signal, determining whether the delay was caused by a signal failure, and providing data support for operation and maintenance.

[0047] In some embodiments, a manually triggered network plan operation instruction is received, the network plan operation instruction including a network plan writing instruction or a network plan deletion instruction; According to the network plan operation instructions, write or delete the global daily operation map to the M private database, and at the same time write or delete the split line daily operation map to the corresponding single line database. Send execution instructions matching the network plan operation instructions to the application servers of each line; Receive the operation results from the application servers on each line, and output the prompt information of the operation results through the cluster front end.

[0048] In some embodiments, if unforeseen circumstances necessitate temporary adjustments, manual intervention is required, namely, the manual loading and deletion of network plans.

[0049] Specifically, the overall application server receives operation instructions triggered by the scheduler only in the global view, writes the temporarily adjusted global daily plan operation map to the M private database, splits the adjusted global daily plan operation map by line, writes the adjusted line daily operation map to the single-line database of the corresponding line, and pushes the global operation map to the cluster devices. The line application server pushes the line operation map to each map-using device of its line. The deletion process is similar, deleting the daily plan in the M private database and the line database respectively. The overall application server and the line application server complete the daily map update of the cluster and line devices respectively.

[0050] In some embodiments, the overall application server receives the operation results fed back by the application servers of each line, and outputs the operation results prompt information through the cluster front end; wherein, the operation results include the cluster device operation map update results and the corresponding line application map device operation map update results.

[0051] Specifically, if the operation diagram interface is in the global view, a prompt message will pop up on the interface indicating the update results of the cluster device operation diagram; if the operation diagram interface is in the single-line view, a prompt message will pop up on the interface indicating the update results of the corresponding line device operation diagram.

[0052] According to embodiments of this disclosure, in the management of urban rail transit network operation diagrams, a unified global operation diagram is formulated for multiple interconnected lines. The global diagram is then directly distributed to each line for execution from the global dispatch workstation. At the same time, the operation diagram operation of a specific line can be completed through the same global dispatch workstation without affecting other lines in the network. Seamless operation is achieved for heterogeneous signaling systems from multiple manufacturers connected to the network, eliminating the need for manual import or reloading by the line operators, and completely solving the coordination problems caused by the barriers between traditional system manufacturers.

[0053] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this disclosure is not limited to the described order of actions, because according to this disclosure, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to this disclosure.

[0054] The above is an introduction to the method embodiments. The following describes the solution described in this disclosure further through device embodiments.

[0055] Figure 2 A block diagram of a city rail transit network-wide cooperative system 200 for heterogeneous signaling systems, according to an embodiment of the present disclosure, is shown. Figure 2 As shown, the device 200 includes: Module 201 is used to start a scheduled task at a preset time and obtain the global loading plan from the M private database. Generation module 202 is used to generate a global daily operation chart based on the global loading plan and write it into the M private database; The writing module 203 is used to split the global daily operation map by line to obtain the daily operation map of each line, and write it into the single-line database of the corresponding line respectively. The push module 204 is used to push the daily operation map of the line to the corresponding actual line equipment using the line application server.

[0056] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the described module can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0057] The acquisition, storage, and application of user personal information involved in the technical solution disclosed herein comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0058] According to embodiments of this disclosure, this disclosure also provides an electronic device, a readable storage medium, and a computer program product.

[0059] Figure 3 A schematic block diagram of an electronic device 300 that can be used to implement embodiments of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0060] Electronic device 300 includes a computing unit 301, which can perform various appropriate actions and processes according to a computer program stored in ROM 302 or a computer program loaded into RAM 303 from storage unit 308. RAM 303 can also store various programs and data required for the operation of electronic device 300. The computing unit 301, ROM 302, and RAM 303 are interconnected via bus 304. I / O interface 305 is also connected to bus 304.

[0061] Multiple components in electronic device 300 are connected to I / O interface 305, including: input unit 306, such as keyboard, mouse, etc.; output unit 307, such as various types of displays, speakers, etc.; storage unit 308, such as disk, optical disk, etc.; and communication unit 309, such as network card, modem, wireless transceiver, etc. Communication unit 309 allows electronic device 300 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0062] The computing unit 301 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 301 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 301 performs the various methods and processes described above, such as method 100. For example, in some embodiments, method 100 may be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 308. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 300 via ROM 302 and / or communication unit 309. When the computer program is loaded into RAM 303 and executed by the computing unit 301, one or more steps of method 100 described above may be performed. Alternatively, in other embodiments, the computing unit 301 may be configured to perform method 100 by any other suitable means (e.g., by means of firmware).

[0063] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0064] The program code used to implement the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0065] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0066] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including voice input, speech input, or tactile input).

[0067] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0068] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact via communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other. Servers can be cloud servers, servers in distributed systems, or servers incorporating blockchain technology.

[0069] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this disclosure can be achieved, and this is not limited herein.

[0070] The specific embodiments described above do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure should be included within the scope of protection of this disclosure.

Claims

1. A method for coordinated operation of the entire urban rail transit network for heterogeneous signaling systems, characterized in that, include: A scheduled task is started at a preset time to retrieve the global loading plan from the M private database; Generate a global daily operation chart based on the global loading plan and write it to the M private database; The global daily operation map is split by line to obtain the daily operation map of each line, and written into the single-line database of the corresponding line respectively. The daily operation map of the line is pushed to the corresponding actual line equipment using the line application server.

2. The method according to claim 1, characterized in that, The method further includes: A runtime graph interface with a split-view architecture is built in the global device, and a database logical isolation method is used to build an M private database and multiple single-line databases.

3. The method according to claim 2, characterized in that, The process of constructing a runtime graph interface with a split-view architecture in the global device, and using a database logical isolation method to construct an M private database and multiple single-line databases includes: The split-view architecture's runtime interface includes a single-line view and a global view. The single-line view supports direct manipulation of the corresponding line's runtime plan, while the global view supports loading network-level interconnection runtime diagrams. Load plans generated by a single-line view are stored in a single-line database, while load plans generated by a global view are stored in an M-private database.

4. The method according to claim 1, characterized in that, The step of splitting the global daily operation map by line to obtain the daily operation map of each line, and writing them into the single-line database of the corresponding line, includes: In the single-line view, a loading plan is independently formulated for the selected single line, and the daily operation chart of the single line is directly written into the corresponding single-line database. In the global view, if a global loading plan has been created for a single line, it is prohibited to create an independent loading plan for that single line again; conversely, if an independent loading plan has been created for a single line, it is prohibited to create a global loading plan for that single line.

5. The method according to claim 1, characterized in that, The process of using a line application server to push the daily line operation map to the corresponding actual line equipment includes: The daily operation map of the line is stored in the corresponding line logical database using the line application server. The line interface machine sends the daily line operation diagram stored in the line logic database to the actual line equipment of the line.

6. The method according to claim 5, characterized in that, The method further includes: The actual line equipment will upload the execution data of the operation diagram to the line application server through the line interface machine; The line application server writes execution data into the line logic database; the line logic database centrally stores historical operation graph data.

7. The method according to claim 1, characterized in that, The method further includes: Receive manually triggered network plan operation instructions, the network plan operation instructions including network plan writing instructions or network plan deletion instructions; According to the network plan operation instructions, write or delete the global daily operation map to the M private database, and at the same time write or delete the split line daily operation map to the corresponding single line database. Send execution instructions matching the network plan operation instructions to the application servers of each line; Receive the operation results from the application servers on each line, and output the prompt information of the operation results through the cluster front end.

8. A city rail transit network-wide coordinated system for heterogeneous signaling systems, characterized in that, include: The acquisition module is used to start a scheduled task at a preset time and retrieve the global loading plan from the M private database; The generation module is used to generate a global daily running chart based on the global loading plan and write it to the M private database; The writing module is used to split the global daily operation map by line to obtain the daily operation map of each line, and write it into the single-line database of the corresponding line respectively. The push module is used to push the daily operation map of the line to the corresponding actual line equipment using the line application server.

9. An electronic device, characterized in that, include: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method described in any one of claims 1-7.

10. A non-transitory computer-readable storage medium storing computer instructions, characterized in that, The computer instructions are used to cause the computer to perform the method according to any one of claims 1-7.

Images