Integrated monitoring system and data synchronization system and method suitable for staged construction

Abstract

The application provides a comprehensive monitoring system and data synchronization system suitable for staged construction, characterized in that the system comprises a first-stage line system, a firewall and a second-stage line system; the first-stage line system comprises a first control center comprehensive monitoring system and a plurality of first-stage stations, and each first-stage station is provided with a first-stage station comprehensive monitoring system; the second-stage line system comprises a second control center comprehensive monitoring system and a plurality of second-stage stations, and each second-stage station is provided with a second-stage station comprehensive monitoring system; the application utilizes the differences between the center and the station access subsystems, arranges the database according to partitions, and respectively deploys the data of the center and the station in different partitions. The application sets a temporary independent control center in the second stage of the subway, realizes the monitoring, configuration and debugging of the non-operated stations and specialities, and avoids affecting the operation of the operated line.

Description

Technical Field

[0001] This invention relates to a comprehensive monitoring system and data synchronization method suitable for phased construction, belonging to the field of comprehensive monitoring systems for urban rail transit. Background Technology

[0002] Currently, due to factors such as project planning and construction difficulties, urban rail transit lines are increasingly adopting a phased construction and operation model, with a final unified operation. The Integrated Monitoring System (ISCS), as an automated monitoring platform for urban rail transit, also needs to meet the requirements of this phased construction and operation model. Figure 2 This is a schematic diagram illustrating the process of ISCS being constructed and put into operation in two phases.

[0003] Phase 1: Complete the installation, deployment, commissioning, and operation of the first phase of ISCS;

[0004] Phase Two: Complete the installation, deployment, and commissioning of Phase Two ISCS; and eliminate and improve the Phase One ISCS that has already been put into operation;

[0005] Phase 3: Complete the merging of all functions of ISCS Phase 1 and 2, and achieve unified management and operation of full-line configuration and real-time data.

[0006] According to the above process, compared with the traditional one-time construction and commissioning, the main problems and risks of phased construction and commissioning lie in the second and third stages, specifically including:

[0007] How to deploy the integrated monitoring system in the second phase;

[0008] In the second phase, how can the configuration, debugging, and other operations and data of the Phase II integrated monitoring system not affect the normal operation of the Phase I line system?

[0009] The third phase involves merging the functions of the Phase I and Phase II line systems, and ensuring the data integrity and functional correctness of the ISCS after the merger.

[0010] The existing technology, "Connection Scheme for Integrated Monitoring System of Initial and Subsequent Sections of Urban Rail Transit," published in Urban Rail Transit Research, discloses a connection scheme for the initial and subsequent sections of an integrated monitoring system. The subsequent section successfully connects with the initial section's ISCS (Integrated Monitoring System Control Center) without affecting its normal operation. All backup work is completed before connection, shortening construction time and reducing the risks associated with excessive human intervention. However, this method completely isolates the first-phase control center from the second-phase control center, preventing connection during second-phase commissioning and hindering data synchronization from the first-phase control center to the second-phase control center for testing and verification. This increases the risk of system failure after connection.

[0011] The existing technology, "Segmented Implementation Plan for the Integrated Monitoring System of Metro," published in Urban Rail Transit Research, proposes a model architecture for integrating the integrated monitoring system of the extended section into the existing control system and provides a detailed integration scheme. This scheme proposes that after the first phase of the project ceases operation at night, the real-time server, historical server, and workstations of the temporary control center will be connected to the control center for debugging the interface functions of the central-level integrated monitoring system. However, because the temporary control center does not restrict the scope of operations on the configuration database, it may mistakenly modify data related to the first phase of the project, increasing the resistance and risk to debugging the interface functions of the central-level integrated monitoring system. After the interface functions of the temporary control center are debugged, importing the data from the temporary control center into the existing control center equipment requires integrating the data from the temporary control center and the formal control center, increasing the workload and risk of database merging. Summary of the Invention

[0012] This invention discloses a comprehensive monitoring system and data synchronization system and method suitable for phased construction of subway lines. By setting up a temporary, independently operating control center in the second phase of subway construction (phased construction phase), it enables monitoring, configuration, and debugging of stations and specialties not yet in operation (phase two), avoiding impact on the operation of already operational lines. Simultaneously, based on data partitioning, it achieves operational isolation and data synchronization between the already operational (phase one) system and the not yet operational (phase two) system. After the second phase line debugging is completed, the operational data for the entire line can be successfully generated based on the phase two configuration data. This meets the needs of phased construction and commissioning of subway lines, and ultimately, unified operation.

[0013] The technical solution of this application is as follows:

[0014] A comprehensive monitoring and data synchronization system suitable for phased construction includes a phase one line system, a firewall, and a phase two line system;

[0015] The first phase of the line system includes a first control center integrated monitoring system and several first phase stations, with each first phase station equipped with a first phase station integrated monitoring system; the second phase of the line system includes a second control center integrated monitoring system and several second phase stations, with each second phase station equipped with a second phase station integrated monitoring system.

[0016] The first control center integrated monitoring system includes a first network, a first control center server, a first control center workstation, and a first configuration database;

[0017] The second control center integrated monitoring system includes a second network, a second control center server, a second control center workstation, and a second configuration database;

[0018] The Phase I station integrated monitoring system includes a Phase I station server and a Phase I station workstation. The Phase I station server connects to the first control center server to realize real-time data communication between the current Phase I station and the first control center integrated monitoring system. The Phase I station workstation performs corresponding Phase I station operation or debugging operations.

[0019] The Phase II station integrated monitoring system includes a Phase II station server and a Phase II station workstation. Each Phase II station server connects to the second control center server to achieve real-time data communication between the current Phase II station and the second control center integrated monitoring system. The Phase II station workstation performs the corresponding Phase II station operation or debugging operations.

[0020] The integrated monitoring systems of the first control center, the second control center, the first phase station, and the second phase station all deploy ISCS (Integrated Monitoring System) software. That is, the servers of the first control center, the first control center, the second control center, the second control center, the first phase station, the first phase station, the second phase station, and the second phase station all deploy ISCS software.

[0021] The first and second networks are connected via a firewall.

[0022] The first control center server is used to control the configuration management, real-time data management of the first phase line system, and the configuration management and real-time data management of the entire line system after the phased construction is completed. The first control center workstation is used to control the debugging and operation of the first phase line system and the operation of the entire line system after the phased construction is completed. The first configuration database stores the configuration data of the first phase line system and the configuration data of the entire line system after the phased construction is completed.

[0023] The second control center server is used to control the configuration management and real-time data management of the second phase line system, as well as the configuration management and real-time data management of the entire line system after the phased construction is completed. The second control center workstation is used to control the debugging and operation of the second phase line system, as well as the operation of the entire line system after the phased construction is completed. The second configuration database stores the configuration data of the first phase line system and the configuration data of the entire line system after the phased construction is completed.

[0024] A comprehensive monitoring system and data synchronization method suitable for phased construction includes the following steps:

[0025] S1. In the first phase of urban rail transit construction, a Phase I line system is set up for Phase I stations and Phase I data access, and for the operation monitoring of the Phase I line system; all configuration data of the Phase I line system is stored in the first configuration database.

[0026] S2. In the second phase of urban rail transit construction, a second control center integrated monitoring system will be set up in the second phase line system. The second control center integrated monitoring system is an unoperated ISCS (Integrated Monitoring System) used for data access, monitoring and configuration debugging of unoperated stations; all data in the current first configuration database will be backed up and restored to the second configuration database to achieve consistency between the configuration data of the second phase line system and the first phase line system.

[0027] S3. The second control center server loads the second configuration database data, generates the real-time database of the second phase line system, and connects the second control center workstation and the second phase station integrated monitoring system (not yet in operation) through the second network to realize data access, monitoring and configuration debugging of the unoperated stations;

[0028] S4. During the second phase of urban rail transit construction:

[0029] The configuration information of the second configuration database is managed by configuring a data partition permission management strategy to prevent the first-phase data and common data in the second configuration database from being modified during the debugging of the second-phase line system; the configuration modifications of the first-phase line system are synchronized from the first configuration database to the second configuration database based on the configuration data partition synchronization method.

[0030] The real-time operation data of the Phase I line system is synchronized from the first control center server to the second control center server of the Phase II line system using a real-time one-way data synchronization method.

[0031] S5. In the third phase of urban rail transit construction, back up all data in the current second configuration database and restore it to the first configuration database, and disconnect the second control center integrated monitoring system (disconnect the first network from the second network and remove the second network, the second control center server, the second control center workstation, and the firewall); connect the second phase station integrated monitoring system to the first network.

[0032] S6. The first control center server reloads all partition configuration data from the first configuration database after data restoration in step S2, generates a real-time database for the entire line, and connects to the first control center workstation and all phase one station integrated monitoring systems through the first network to perform operation monitoring of the entire line.

[0033] The configuration of the urban rail transit system is stored in the first configuration database; the data of the entire line is divided into several different data partitions according to the station or purpose, including the public partition, the first phase dedicated partition and the second phase dedicated partition;

[0034] The first phase of dedicated partitions includes the first phase power monitoring partition, the first phase train operation partition, the first phase control center partition, and the first phase station partitions; the second phase of dedicated partitions includes the second phase power monitoring partition, the second phase train operation partition, the second phase control center partition, and the second phase station partitions; each data partition is assigned a unique data partition number; a PartitionId field is added to each data table in the first configuration database and the first configuration database, and a PartitionId attribute is added to each data object. The PartitionId attribute is used to record the unique data partition number to which the data object belongs, and it is not null;

[0035] The public partition stores data shared by the Phase I and Phase II line systems, including ISCS operation settings data, global configuration information data, and screen element template data;

[0036] The Phase I dedicated partition stores the collected data, monitoring screen data, real-time calculation configuration data, and alarm information configuration data of the stations connected to the Phase I line system. The Phase I dedicated partition includes the Phase I power monitoring partition, the Phase I train operation partition, the Phase I control center partition, and the Phase I station partitions.

[0037] The Phase II dedicated partition stores the collected data, monitoring screen data, real-time calculation configuration data, and alarm information configuration data of the stations connected to the Phase II line system. The Phase II dedicated partition includes the Phase II power monitoring partition, the Phase II train operation partition, the Phase II control center partition, and the Phase II station partitions.

[0038] To ensure data security, the Phase II line system uses a configuration data partition permission management strategy to restrict data operation permissions within each data partition. Partition permissions are bound to the machine nodes of the Phase II line system (the machine nodes of the Phase II line system include the second control center server, the second control center workstation, the Phase II station server, and the Phase II station workstation). A specified encrypted configuration file PartitionAuthConf.ini is added to the machine nodes of the Phase II line system to record the operation permissions of the machine nodes of the Phase II line system for each data partition.

[0039] The encryption configuration file PartitionAuthConf.ini includes a read-only array ReadOnlyPartitions and a read-write array WriteAndReadPartitions, which respectively store the data partition numbers that are allowed to be read and written by the current machine node. The current machine node does not have permission to access data partitions whose numbers are not in the ReadOnlyPartitions and WriteAndReadPartitions arrays.

[0040] The data in the public partition is shared by the Phase I and Phase II line systems. In order to ensure the stable operation of the already operational portion of the Phase I line system, only the Phase I line system has the right to modify the configuration data of the public partition.

[0041] The WriteAndReadPartitions array includes the partition numbers of the Phase II dedicated partitions, while ReadOnlyPartitions includes the partition numbers of the public partitions and the Phase I dedicated partitions. The Phase II line system only has read-only permissions, effectively avoiding database errors caused by configuration operation conflicts.

[0042] Configuring data partition permission management policies specifically includes the following steps:

[0043] S101. Complete the configuration of the PartitionAuthConf.ini file for the Phase II line system and upload it to all machine nodes of the Phase II line system;

[0044] S102. When the machine node of the second phase line system starts, it loads the PartitionAuthConf.ini file and parses and obtains ReadOnlyPartitions and WriteAndReadPartitions information. If the PartitionAuthConf.ini file does not exist or fails to load, the machine node has no permission to all configuration data of the ISCS system and terminates the process. Otherwise, proceed to step S103.

[0045] S103. Each time an operation is performed on a data object (query, modify, delete), the PartitionId attribute of the data object being operated on is compared with the ReadOnlyPartitions and WriteAndReadPartitions information loaded in step S102, and data partition permission management is performed based on the comparison result.

[0046] The PartitionId attribute is the data partition number of the record. The "ReadOnlyPartitions" and "WriteAndReadPartitions" information are also the corresponding data partition numbers. When the corresponding data partition number is in "ReadOnlyPartitions", read-only permission is granted; when the corresponding data partition number is in "WriteAndReadPartitions", read and write permissions are granted.

[0047] The configuration data partition synchronization method is used to synchronize configuration data from the Phase I line system to the Phase II line system. It enables the synchronization of data modifications in the Phase I public partition and Phase I dedicated partition to the Phase II line system during the second phase of urban rail transit construction. Only one partition can be synchronized at a time.

[0048] The data of the modified data partitions in the Phase I line system is exported, and the exported data is compared with the data of the Phase II partitions. After checking and confirming the data based on the comparison, it is imported into the Phase II line system, so as to realize the synchronization of the configuration changes of the Phase I line system to the Phase II line system.

[0049] Before importing the data into the Phase II line system, the Phase II configuration database is backed up by exporting and importing one data partition at a time.

[0050] The configuration data partition synchronization method specifically includes the following steps: S201: Scan all data tables in the first configuration database and export the records in the data tables whose PartitionId field value is equal to the partition number being operated on. The exported data of each data table is a JSON format export file named after the table name.

[0051] S202: Compare the exported file with the corresponding data table records in the second configuration database according to the file name, and generate difference comparison information; the difference comparison information includes the data object addition, deletion and modification information of the partition operated on in the first configuration database relative to the second configuration database. The difference comparison information of each data table is stored in the difference comparison information file, which is a JSON file named "table_name_diff"; S203: Check the difference information and confirm whether to perform the partition data import operation. If confirmed, proceed to step S204; otherwise, terminate the process;

[0052] S204: Read the difference comparison information file sequentially, and synchronize the difference information to the corresponding data table in the second configuration database according to the difference comparison information file. Record the import execution record after each successful synchronization of difference information. The import execution record of the entire data table is in the same format as the difference comparison information file.

[0053] S205: Compare the import execution record generated in S204 with the difference information generated in S202. Compare the execution status of each difference information according to the content format. If the comparison is consistent, the import is successful; otherwise, the import fails, and the database backup is restored.

[0054] The Phase I and Phase II line systems synchronize real-time data from the Phase I line system to the Phase II line system using a one-way real-time data synchronization method. This one-way real-time data synchronization method is achieved through communication between the first control center server and the second control center server. The one-way transmission of real-time data is realized through firewall settings between the first and second control center servers. The firewall only allows the second control center server to send data request packets with specified content to the first control center server, while there are no restrictions on the reverse data transmission.

[0055] The first control center server selectively sends data to the second control center server using a blacklist and whitelist mechanism.

[0056] The blacklist and whitelist configurations for transmission are stored in the stationsync.ini configuration file on the first control center server.

[0057] Partitions is used to store the partition numbers of data that are allowed to be synchronized. If the PartitionId of a data object is not in this list, it will not be synchronized with the second control center server.

[0058] BlackObjects is used to store blacklist information. All data values ​​of the data object types contained in this list are prohibited from being sent to the second control center server.

[0059] WhiteObjects is used to store whitelist information. The data objects in this list are only allowed to send specified attribute values ​​to the second control center server.

[0060] Data objects not on the blacklist or whitelist are unrestricted, and all their attribute values ​​are sent to the second control center server.

[0061] Compared with the prior art, the present invention has the following beneficial effects:

[0062] This application discloses a comprehensive monitoring system and data synchronization method applicable to phased construction. Utilizing the different access subsystems of the central control center and stations, the database is arranged according to partitions, with data from the central control center and stations deployed in different partitions. During the phased commissioning of the subway, the Phase I control center and the Phase II control center are not completely isolated; configuration and real-time data synchronization are achieved through network connection. This application starts the Phase II line system based on the configuration of the Phase I line system, and divides the configuration database by partitions, strictly limiting the scope of operations on the configuration database by Phase I and Phase II. Furthermore, during the Phase II line system process, modifications to the Phase I line system are synchronized to the Phase II line system, and data from the Phase I line system is also synchronized to the Phase II line system for viewing, display, and verification. The merging of all configuration data is completed during the Phase II line system process. After the Phase II line system is completed, the real-time database for the entire line is directly generated from the Phase II line system configuration, eliminating the need for further dedicated database merging and verification.

[0063] This application proposes to set up a temporary, independently operating control center in the second phase (phased construction phase) of the subway system to monitor, configure, and debug stations and professional equipment that are not yet in operation (phase two), thereby avoiding any impact on the operation of lines already in operation.

[0064] This application employs configuration data partitioning permission management technology to ensure that the configuration data of the already operational parts of the first phase is not modified during the commissioning of the second phase line system, thus guaranteeing data security and avoiding conflicts between the configuration data of the first and second phases.

[0065] This application employs configuration data partitioning and synchronization technology to synchronize and save configuration modifications of the Phase I operational system to the Phase II system during the commissioning process of the Phase II line system. This ensures the commissioning needs of the Phase II line system while avoiding the need for merging the databases of the Phase I and Phase II line systems.

[0066] This application employs real-time data one-way synchronization technology to unidirectionally synchronize real-time data from the first phase of operation to the second phase line system, enabling the second phase line system to conduct commissioning work involving the entire line, and avoiding any impact of the second phase line system data on the first phase line system. Attached Figure Description

[0067] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:

[0068] Figure 1 This embodiment is applicable to a schematic diagram of a comprehensive monitoring system and data synchronization system constructed in phases;

[0069] Figure 2 Schematic diagram of the construction and commissioning of the phased integrated monitoring system;

[0070] Figure 3 Schematic diagram of data partition permission management configuration;

[0071] Figure 4 Diagram illustrating the configuration of data partition synchronization. Detailed Implementation

[0072] The technical solution of the present invention will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0073] like Figure 1 As shown, a comprehensive monitoring system and data synchronization system suitable for phased construction includes a phase one line system, a firewall, and a phase two line system.

[0074] The first phase of the line system includes a first control center integrated monitoring system and several first phase stations, with each first phase station equipped with a first phase station integrated monitoring system; the second phase of the line system includes a second control center integrated monitoring system and several second phase stations, with each second phase station equipped with a second phase station integrated monitoring system.

[0075] The first control center integrated monitoring system includes a first network, a first control center server, a first control center workstation, and a first configuration database;

[0076] The second control center integrated monitoring system includes a second network, a second control center server, a second control center workstation, and a second configuration database;

[0077] The Phase I station integrated monitoring system includes a Phase I station server and a Phase I station workstation. The Phase I station server connects to the first control center server to realize real-time data communication between the current Phase I station and the first control center integrated monitoring system. The Phase I station workstation performs corresponding Phase I station operation or debugging operations.

[0078] The Phase II station integrated monitoring system includes a Phase II station server and a Phase II station workstation. Each Phase II station server connects to the second control center server to achieve real-time data communication between the current Phase II station and the second control center integrated monitoring system. The Phase II station workstation performs the corresponding Phase II station operation or debugging operations.

[0079] The integrated monitoring systems of the first control center, the second control center, the first phase station, and the second phase station all deploy ISCS (Integrated Monitoring System) software. That is, the servers of the first control center, the first control center, the second control center, the second control center, the first phase station, the first phase station, the second phase station, and the second phase station all deploy ISCS software.

[0080] The first and second networks are connected via a firewall.

[0081] The first control center server is used to control the configuration management, real-time data management of the first phase line system, and the configuration management and real-time data management of the entire line system after the phased construction is completed. The first control center workstation is used to control the debugging and operation of the first phase line system and the operation of the entire line system after the phased construction is completed. The first configuration database stores the configuration data of the first phase line system and the configuration data of the entire line system after the phased construction is completed.

[0082] The second control center server is used to control the configuration management and real-time data management of the second phase line system, as well as the configuration management and real-time data management of the entire line system after the phased construction is completed. The second control center workstation is used to control the debugging and operation of the second phase line system, as well as the operation of the entire line system after the phased construction is completed. The second configuration database stores the configuration data of the first phase line system and the configuration data of the entire line system after the phased construction is completed.

[0083] A comprehensive monitoring system and data synchronization method suitable for phased construction includes the following steps:

[0084] S1. In the first phase of urban rail transit construction, a Phase I line system is set up for Phase I stations and Phase I data access, and for the operation monitoring of the Phase I line system; all configuration data of the Phase I line system is stored in the first configuration database.

[0085] S2. In the second phase of urban rail transit construction, a second control center integrated monitoring system will be set up in the second phase line system. The second control center integrated monitoring system is an unoperated ISCS (Integrated Monitoring System) used for data access, monitoring and configuration debugging of unoperated stations; all data in the current first configuration database will be backed up and restored to the second configuration database to achieve consistency between the configuration data of the second phase line system and the first phase line system.

[0086] S3. The second control center server loads the second configuration database data, generates the real-time database of the second phase line system, and connects the second control center workstation and the second phase station integrated monitoring system (not yet in operation) through the second network to realize data access, monitoring and configuration debugging of the unoperated stations;

[0087] S4. During the second phase of urban rail transit construction:

[0088] The configuration information of the second configuration database is managed by configuring a data partition permission management strategy to prevent the first-phase data and common data in the second configuration database from being modified during the debugging of the second-phase line system; the configuration modifications of the first-phase line system are synchronized from the first configuration database to the second configuration database based on the configuration data partition synchronization method.

[0089] The real-time operation data of the Phase I line system is synchronized from the first control center server to the second control center server of the Phase II line system using a real-time one-way data synchronization method.

[0090] S5. In the third phase of urban rail transit construction, back up all data in the current second configuration database and restore it to the first configuration database, and disconnect the second control center integrated monitoring system (disconnect the first network from the second network and remove the second network, the second control center server, the second control center workstation, and the firewall); connect the second phase station integrated monitoring system to the first network.

[0091] S6. The first control center server reloads all partition configuration data from the first configuration database after data restoration in step S2, generates a real-time database for the entire line, and connects to the first control center workstation and all phase one station integrated monitoring systems through the first network to perform operation monitoring of the entire line.

[0092] The configuration of the urban rail transit system is stored in the first configuration database; the data for the entire line is divided into several different data partitions according to stations or uses, such as... Figure 3 As shown, the data partitions include a public partition, a Phase I dedicated partition, and a Phase II dedicated partition;

[0093] The first phase of dedicated partitions includes the first phase power monitoring partition, the first phase train operation partition, the first phase control center partition, and the first phase station partitions; the second phase of dedicated partitions includes the second phase power monitoring partition, the second phase train operation partition, the second phase control center partition, and the second phase station partitions; each data partition is assigned a unique data partition number; a PartitionId field is added to each data table in the first configuration database and the first configuration database, and a PartitionId attribute is added to each data object. The PartitionId attribute is used to record the unique data partition number to which the data object belongs, and it is not null;

[0094] The public partition stores data shared by the Phase I and Phase II line systems, including ISCS operation settings data, global configuration information data, and screen element template data;

[0095] The Phase I dedicated partition stores the collected data, monitoring screen data, real-time calculation configuration data, and alarm information configuration data of the stations connected to the Phase I line system. The Phase I dedicated partition includes the Phase I power monitoring partition, the Phase I train operation partition, the Phase I control center partition, and the Phase I station partitions.

[0096] The Phase II dedicated partition stores the collected data, monitoring screen data, real-time calculation configuration data, and alarm information configuration data of the stations connected to the Phase II line system. The Phase II dedicated partition includes the Phase II power monitoring partition, the Phase II train operation partition, the Phase II control center partition, and the Phase II station partitions.

[0097] To ensure data security, the Phase II line system uses a configuration data partition permission management strategy to restrict data operation permissions within each data partition. Partition permissions are bound to the machine nodes of the Phase II line system (the machine nodes of the Phase II line system include the second control center server, the second control center workstation, the Phase II station server, and the Phase II station workstation). A specified encrypted configuration file PartitionAuthConf.ini is added to the machine nodes of the Phase II line system to record the operation permissions of the machine nodes of the Phase II line system for each data partition.

[0098] The encryption configuration file PartitionAuthConf.ini includes a read-only array ReadOnlyPartitions and a read-write array WriteAndReadPartitions, which respectively store the data partition numbers that are allowed to be read and written by the current machine node. The current machine node does not have permission to access data partitions whose numbers are not in the ReadOnlyPartitions and WriteAndReadPartitions arrays.

[0099] The data in the public partition is shared by the Phase I and Phase II line systems. In order to ensure the stable operation of the already operational portion of the Phase I line system, only the Phase I line system has the right to modify the configuration data of the public partition.

[0100] The WriteAndReadPartitions array includes the partition numbers of the Phase II dedicated partitions, while ReadOnlyPartitions includes the partition numbers of the public partitions and the Phase I dedicated partitions. The Phase II line system only has read-only permissions, effectively avoiding database errors caused by configuration operation conflicts.

[0101] Configuring data partition permission management policies specifically includes the following steps:

[0102] S101. Complete the configuration of the PartitionAuthConf.ini file for the Phase II line system and upload it to all machine nodes of the Phase II line system;

[0103] S102. When the machine node of the second phase line system starts, it loads the PartitionAuthConf.ini file and parses and obtains ReadOnlyPartitions and WriteAndReadPartitions information. If the PartitionAuthConf.ini file does not exist or fails to load, the machine node has no permission to all configuration data of the ISCS system and terminates the process. Otherwise, proceed to step S103.

[0104] S103. Each time an operation is performed on a data object (query, modify, delete), the PartitionId attribute of the data object being operated on is compared with the ReadOnlyPartitions and WriteAndReadPartitions information loaded in step S102, and data partition permission management is performed based on the comparison result.

[0105] The PartitionId attribute is the data partition number of the record. The "ReadOnlyPartitions" and "WriteAndReadPartitions" information are also the corresponding data partition numbers. When the corresponding data partition number is in "ReadOnlyPartitions", read-only permission is granted; when the corresponding data partition number is in "WriteAndReadPartitions", read and write permissions are granted.

[0106] like Figure 4 As shown, the configuration data partition synchronization method is used to synchronize configuration data from the Phase I line system to the Phase II line system. This enables the data modifications of the Phase I public partition and Phase I dedicated partition to be synchronized to the Phase II line system in the second phase of urban rail transit construction. Only one partition can be synchronized at a time.

[0107] The data of the modified data partitions in the Phase I line system is exported, and the exported data is compared with the data of the Phase II partitions. After checking and confirming the data based on the comparison, it is imported into the Phase II line system, so as to realize the synchronization of the configuration changes of the Phase I line system to the Phase II line system.

[0108] Before importing the data into the Phase II line system, the Phase II configuration database is backed up by exporting and importing one data partition at a time.

[0109] The configuration data partition synchronization method specifically includes the following steps: S201: Scan all data tables in the first configuration database and export the records in the data tables whose PartitionId field value is equal to the partition number being operated on. The exported data of each data table is a JSON format export file named after the table name.

[0110] S202: The exported file is compared with the corresponding data table records in the second configuration database according to the file name, and difference comparison information is generated. The difference comparison information includes the data object addition, deletion and modification information of the partition operated on in the first configuration database relative to the second configuration database. The difference comparison information of each data table is stored in the difference comparison information file, which is a JSON file named "table_name_diff".

[0111] S203: Check the difference information and confirm whether to perform the partition data import operation. If confirmed, proceed to step S204; otherwise, terminate the process.

[0112] S204: Read the difference comparison information file sequentially, and synchronize the difference information to the corresponding data table in the second configuration database according to the difference comparison information file. Record the import execution record after each successful synchronization of difference information. The import execution record of the entire data table is in the same format as the difference comparison information file.

[0113] S205: Compare the import execution record generated in S204 with the difference information generated in S202. Compare the execution status of each difference information according to the content format. If the comparison is consistent, the import is successful; otherwise, the import fails, and the database backup is restored.

[0114] The Phase I and Phase II line systems synchronize real-time data from the Phase I line system to the Phase II line system using a one-way real-time data synchronization method. This one-way real-time data synchronization method is achieved through communication between the first control center server and the second control center server. The one-way transmission of real-time data is realized through firewall settings between the first and second control center servers. The firewall only allows the second control center server to send data request packets with specified content to the first control center server, while there are no restrictions on the reverse data transmission.

[0115] The first control center server selectively sends data to the second control center server using a blacklist and whitelist mechanism.

[0116] The blacklist and whitelist configurations for transmission are stored in the stationsync.ini configuration file on the first control center server.

[0117] The configuration file content format is as follows:

[0118]

[0119] in:

[0120] Partitions is used to store the partition numbers of data that are allowed to be synchronized. If the PartitionId of a data object is not in this list, it will not be synchronized with the second control center server.

[0121] BlackObjects is used to store blacklist information. All data values ​​of the data object types contained in this list are prohibited from being sent to the second control center server.

[0122] WhiteObjects is used to store whitelist information. The data objects in this list are only allowed to send specified attribute values ​​to the second control center server.

[0123] Data objects not on the blacklist or whitelist are unrestricted, and all their attribute values ​​are sent to the second control center server.

[0124] The technical solution of the present invention has been described above with reference to the preferred embodiments shown in the accompanying drawings. However, it will be readily understood by those skilled in the art that the scope of protection of the present invention is obviously not limited to these specific embodiments. Without departing from the principles of the present invention, those skilled in the art can make equivalent changes or substitutions to the relevant technical features, and the technical solutions after such changes or substitutions will all fall within the scope of protection of the present invention.

[0125] Numerous specific details are set forth in the specification provided herein. However, it will be understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures, and techniques have not been shown in detail so as not to obscure the understanding of this specification.

[0126] Similarly, it should be understood that, in order to streamline this disclosure and aid in understanding one or more of the various aspects of the invention, in the above description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof. However, this method of disclosure should not be interpreted as reflecting an intention that the claimed invention requires more features than expressly recited in each claim. Rather, as reflected in the claims, inventive aspects lie in fewer than all features of a single foregoing disclosed embodiment. Therefore, the claims following the detailed description are hereby expressly incorporated into that detailed description, wherein each claim itself is a separate embodiment of the invention.

[0127] Those skilled in the art will understand that the modules, units, or groups of devices in the examples disclosed herein can be arranged in the device as described in this embodiment, or alternatively, can be located in one or more devices different from the device in this example. The modules in the foregoing examples can be combined into a single module or, in addition, can be divided into multiple sub-modules.

[0128] Those skilled in the art will understand that modules in the device of the embodiments can be adaptively changed and placed in one or more devices different from that embodiment. Modules, units, or groups in the embodiments can be combined into a single module, unit, or group, and further, they can be divided into multiple sub-modules, sub-units, or sub-groups. Except where at least some of such features and / or processes or units are mutually exclusive, any combination can be used to combine all features disclosed in this specification (including the accompanying claims, abstract, and drawings) and all processes or units of any method or device so disclosed. Unless expressly stated otherwise, each feature disclosed in this specification (including the accompanying claims, abstract, and drawings) may be replaced by an alternative feature that serves the same, equivalent, or similar purpose.

[0129] Furthermore, those skilled in the art will understand that although some embodiments described herein include certain features but not others included in other embodiments, combinations of features from different embodiments are intended to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments can be used in any combination.

[0130] Furthermore, some of the embodiments described herein are methods or combinations of method elements that can be implemented by a processor of a computer system or by other means of performing the functions. Therefore, a processor having the necessary instructions for implementing the methods or method elements forms means for implementing the methods or method elements. Furthermore, the elements described herein in the apparatus embodiments are examples of means for implementing the functions performed by elements for the purposes of carrying out the invention.

[0131] The various techniques described herein can be implemented in combination with hardware or software, or a combination thereof. Thus, the methods and apparatus of the present invention, or certain aspects or portions thereof, can take the form of program code (i.e., instructions) embedded in a tangible medium, such as a floppy disk, CD-ROM, hard disk, or any other machine-readable storage medium, wherein when the program is loaded into and executed by a machine such as a computer, the machine becomes an apparatus for practicing the present invention.

[0132] When the program code is executed on a programmable computer, the computing device generally includes a processor, a processor-readable storage medium (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device. The memory is configured to store program code; the processor is configured to execute the method of the present invention according to instructions in the program code stored in the memory.

[0133] By way of example, and not limitation, computer-readable media include computer storage media and communication media. Computer storage media stores information such as computer-readable instructions, data structures, program modules, or other data. Communication media generally embodies computer-readable instructions, data structures, program modules, or other data in the form of modulated data signals such as carrier waves or other transmission mechanisms, and includes any information delivery medium. Any combination of the above is also included within the scope of computer-readable media.

[0134] As used herein, unless otherwise specified, the use of ordinal numbers such as “first,” “second,” “third,” etc., to describe ordinary objects merely indicates different instances of similar objects and is not intended to imply that the objects being described must have a given order in time, space, ordering, or any other manner.

[0135] Although the invention has been described with reference to a limited number of embodiments, those skilled in the art will understand from the foregoing description that other embodiments are conceivable within the scope of the invention described herein. Furthermore, it should be noted that the language used in this specification has been chosen primarily for readability and edibility purposes, and not for the purpose of interpreting or limiting the subject matter of the invention. Therefore, many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the appended claims. The disclosure of the invention is illustrative and not restrictive, and the scope of the invention is defined by the appended claims.

Claims

1. A comprehensive monitoring system and data synchronization system suitable for phased construction, characterized in that, The system is suitable for integrated monitoring systems and data synchronization methods constructed in phases. The system includes a first-phase line system, a firewall, and a second-phase line system; The first phase of the line system includes a first control center integrated monitoring system and several first phase stations, with each first phase station equipped with a first phase station integrated monitoring system; the second phase of the line system includes a second control center integrated monitoring system and several second phase stations, with each second phase station equipped with a second phase station integrated monitoring system. The first control center integrated monitoring system includes a first network, a first control center server, a first control center workstation, and a first configuration database; The second control center integrated monitoring system includes a second network, a second control center server, a second control center workstation, and a second configuration database; The Phase I station integrated monitoring system includes a Phase I station server and a Phase I station workstation. The Phase I station server connects to the first control center server to realize real-time data communication between the current Phase I station and the first control center integrated monitoring system. The Phase I station workstation performs corresponding Phase I station operation or debugging operations. The Phase II station integrated monitoring system includes a Phase II station server and a Phase II station workstation. Each Phase II station server connects to the second control center server to achieve real-time data communication between the current Phase II station and the second control center integrated monitoring system. The Phase II station workstation performs the corresponding Phase II station operation or debugging operations. The first and second networks are connected via a firewall; The method includes the following steps: S1. In the first phase of urban rail transit construction, a Phase I line system is set up for Phase I stations and Phase I data access, and for the operation monitoring of the Phase I line system; all configuration data of the Phase I line system is stored in the first configuration database. S2. In the second phase of urban rail transit construction, a second control center integrated monitoring system is set up in the second phase line system. The second control center integrated monitoring system is used to access, monitor and configure stations that are not yet in operation; all data in the current first configuration database is backed up and restored to the second configuration database to achieve consistency between the configuration data of the second phase line system and the first phase line system. S3. The second control center server loads the second configuration database data, generates the real-time database of the second phase line system, and connects the second control center workstation and the second phase station integrated monitoring system through the second network to realize data access, monitoring and configuration debugging of stations that have not yet been put into operation. S4. During the second phase of urban rail transit construction: The configuration information of the second configuration database is managed by configuring a data partition permission management strategy to prevent the first-phase data and common data in the second configuration database from being modified during the debugging of the second-phase line system; the configuration modifications of the first-phase line system are synchronized from the first configuration database to the second configuration database based on the configuration data partition synchronization method. The real-time operation data of the Phase I line system is synchronized from the first control center server to the second control center server of the Phase II line system using a real-time one-way data synchronization method. S5. During the third phase of urban rail transit construction, back up all data in the current second configuration database and restore it to the first configuration database, then disconnect the second control center integrated monitoring system; connect the second phase station integrated monitoring system to the first network; S6. The first control center server reloads all partition configuration data from the first configuration database after data restoration in step S2, generates a real-time database for the entire line, and connects to the first control center workstation and all phase one station integrated monitoring systems through the first network to perform operation monitoring of the entire line. The configuration of the urban rail transit system is stored in the first configuration database; the data of the entire line is divided into several different data partitions according to the station or purpose, including the public partition, the first phase dedicated partition and the second phase dedicated partition; The first phase of dedicated partitions includes the first phase power monitoring partition, the first phase train operation partition, the first phase control center partition, and the first phase station partitions; the second phase of dedicated partitions includes the second phase power monitoring partition, the second phase train operation partition, the second phase control center partition, and the second phase station partitions; each data partition is assigned a unique data partition number; a PartitionId field is added to each data table in the first configuration database and the first configuration database, and a PartitionId attribute is added to each data object. The PartitionId attribute is used to record the unique data partition number to which the data object belongs, and it is not null; The public partition stores data shared by the Phase I and Phase II line systems, including ISCS operation settings data, global configuration information data, and screen element template data; The Phase I dedicated partition stores the collected data, monitoring screen data, real-time calculation configuration data, and alarm information configuration data of the stations connected to the Phase I line system. The Phase I dedicated partition includes the Phase I power monitoring partition, the Phase I train operation partition, the Phase I control center partition, and the Phase I station partitions. The Phase II dedicated partition stores the collected data, monitoring screen data, real-time calculation configuration data, and alarm information configuration data of the stations connected to the Phase II line system. The Phase II dedicated partition includes the Phase II power monitoring partition, the Phase II train operation partition, the Phase II control center partition, and the Phase II station partitions. The Phase II line system uses a configuration data partition permission management strategy to restrict data operation permissions within each data partition; partition permissions are bound to the machine nodes of the Phase II line system, and a specified encrypted configuration file PartitionAuthConf.ini is added to the machine nodes of the Phase II line system to record the operation permissions of the machine nodes of the Phase II line system for each data partition; The encryption configuration file PartitionAuthConf.ini includes a read-only array ReadOnlyPartitions and a read-write array WriteAndReadPartitions, which respectively store the data partition numbers that are allowed to be read and written by the current machine node. The current machine node does not have permission to access data partitions whose numbers are not in the ReadOnlyPartitions and WriteAndReadPartitions arrays. The data in the public partition is shared by both the Phase I and Phase II line systems, but only the Phase I line system has the right to modify the configuration data of the public partition. The WriteAndReadPartitions array includes the partition number of the Phase II dedicated partition, and the ReadOnlyPartitions array includes the partition number of the public partition and the Phase I dedicated partition. The Phase II line system only has read-only permissions. Configuring data partition permission management policies specifically includes the following steps: S101. Complete the configuration of the PartitionAuthConf.ini file for the Phase II line system and upload it to all machine nodes of the Phase II line system; S102. When the machine node of the second phase line system starts, it loads the PartitionAuthConf.ini file and parses and obtains ReadOnlyPartitions and WriteAndReadPartitions information. If the PartitionAuthConf.ini file does not exist or fails to load, the machine node has no permission to all configuration data of the ISCS system and terminates the process. Otherwise, proceed to step S103. S103. Each time an operation is performed on a data object, the PartitionId attribute of the data object being operated on is compared with the ReadOnlyPartitions and WriteAndReadPartitions information loaded in step S102, and data partition permission management is performed based on the comparison result.

2. The integrated monitoring system and data synchronization system suitable for phased construction as described in claim 1, characterized in that, The first control center server is used to control the configuration management, real-time data management of the first phase line system, and the configuration management and real-time data management of the entire line system after the phased construction is completed. The first control center workstation is used to control the debugging and operation of the first phase line system and the operation of the entire line system after the phased construction is completed. The first configuration database stores the configuration data of the first phase line system and the configuration data of the entire line system after the phased construction is completed. The second control center server is used to control the configuration management and real-time data management of the second phase line system, as well as the configuration management and real-time data management of the entire line system after the phased construction is completed. The second control center workstation is used to control the debugging and operation of the second phase line system, as well as the operation of the entire line system after the phased construction is completed. The second configuration database stores the configuration data of the first phase line system and the configuration data of the entire line system after the phased construction is completed.

3. The integrated monitoring system and data synchronization system suitable for phased construction as described in claim 1, characterized in that, The configuration data partition synchronization method is used to synchronize configuration data from the Phase I line system to the Phase II line system. It enables the synchronization of data modifications in the Phase I public partition and Phase I dedicated partition to the Phase II line system during the second phase of urban rail transit construction. Only one partition can be synchronized at a time. Export the data of the data partitions involved in the modification in the Phase I route system, compare the exported data with the data of the Phase II partitions, check and confirm the data based on the comparison data, and then import it into the Phase II route system to realize the synchronization of the configuration changes in the Phase I route system to the Phase II route system. Before importing the data into the Phase II line system, the Phase II configuration database is backed up by exporting and importing one data partition at a time.

4. The integrated monitoring system and data synchronization system suitable for phased construction as described in claim 3, characterized in that, The specific steps for configuring data partition synchronization are as follows: S201: Scan all data tables in the first configuration database and export the records in the data tables whose PartitionId field value is equal to the partition number being operated on. The exported data for each data table is a JSON format export file named after the table name. S202: Compare the exported file with the corresponding data table records in the second configuration database according to the file name, and generate difference comparison information; the difference comparison information includes the data object addition, deletion and modification information of the partition operated on in the first configuration database relative to the second configuration database. The difference comparison information of each data table is stored in the difference comparison information file, which is a JSON file named "table_name_diff"; S203: Check the difference information and confirm whether to perform the partition data import operation. If confirmed, proceed to step S204; otherwise, terminate the process; S204: Read the difference comparison information file sequentially, and synchronize the difference information to the corresponding data table in the second configuration database according to the difference comparison information file. Save the import execution record after each successful synchronization of difference information. The import execution record of the entire data table is in the same format as the difference comparison information file. S205: Compare the import execution record generated in S204 with the difference information generated in S202. Compare the execution status of each difference information according to the content format. If the comparison is consistent, the import is successful; otherwise, the import fails, and the database backup is restored.

5. The integrated monitoring system and data synchronization system suitable for phased construction according to claim 1, characterized in that, The Phase I and Phase II line systems synchronize real-time data from the Phase I line system to the Phase II line system using a one-way real-time data synchronization method. This one-way real-time data synchronization method is achieved through communication between the first control center server and the second control center server. The one-way transmission of real-time data is realized through firewall settings between the first and second control center servers. The firewall only allows the second control center server to send data request packets with specified content to the first control center server, while there are no restrictions on the reverse data transmission.

6. A comprehensive monitoring system and data synchronization system suitable for phased construction as described in claim 5, characterized in that, The first control center server selectively sends data to the second control center server using a blacklist and whitelist mechanism; The blacklist and whitelist configurations for transmission are stored in the stationsync.ini configuration file on the first control center server; Partitions is used to store the partition numbers of data that are allowed to be synchronized. If the PartitionId of a data object is not in this list, it will not be synchronized with the second control center server. BlackObjects is used to store blacklist information. All data values ​​of the data object types contained in this list are prohibited from being sent to the second control center server. WhiteObjects is used to store whitelist information. The data objects in this list are only allowed to send specified attribute values ​​to the second control center server. Data objects not on the blacklist or whitelist are unrestricted, and all attribute values ​​of data objects not on the blacklist or whitelist are sent to the second control center server.

Images