A method for scheduling centralized data update and disaster recovery based on light memory

Abstract

The present invention discloses a method for updating and disaster recovery of scheduling centralized data based on lightweight memory. Lightweight memory is introduced on the basis of existing data transmission methods to solve the data consistency, data access efficiency and security problems existing in the current methods. Specifically: a data transmission model is constructed to ensure that read and write operations do not occur at the same time, prevent data consistency problems, and ensure the accuracy of scheduling centralized data; at the same time, it can significantly improve the access efficiency of scheduling centralized data, thereby improving the overall performance of the scheduling centralized system program.

Description

Technical Field

[0001] The present invention relates to the technical field of data updating and disaster recovery of centralized scheduling data, and in particular to a method for updating and disaster recovery of centralized scheduling data based on a light memory. Background Art

[0002] The centralized dispatching system is a highly automated train dispatching and command system centered around train operation planning and control, utilizing a combination of network communication, computer, and modern control technologies. The centralized dispatching data records all train status and command information within the system's jurisdiction, providing crucial data support for train dispatchers to monitor the dispatching section's status in real time, adjust train operation plans, and optimize and improve line capacity. The centralized dispatching data is divided into static data loaded at program startup (such as text templates, timetable basemaps, station configurations, and track configurations) and dynamic data accessed during program execution (such as command text content, command receipt status, construction registration information, real-time operating lines, and construction markings). The centralized dispatching data contains a large number of data items related to dispatching and command operations, and these data items often have dependencies (such as the dependency between real-time operating line nodes and station configurations, the dependency between command text content and text templates, and the dependency between construction markings and the timetable basemap). This data is characterized by its large size and complex relationships.

[0003] The scheduling centralized data is loaded into the application cache by the scheduling centralized system program. The application cache can be loaded and modified through the human-machine interface terminal, stored in the database through a remote connection, or stored locally through a data file. The existing data update method stores the scheduling centralized data through text files or XML files. When the remote connection to the database is normal, the scheduling centralized system program backs up the data through the data update method. Due to network congestion, server failure or the influence of third-party software, the remote connection to the database may be disconnected. If the remote connection is disconnected, the scheduling centralized system program accesses the local data file to obtain data to ensure that the application runs correctly as expected. If the remote connection is restored, the scheduling centralized system program updates the local data modified during the remote connection interruption to the database through the data disaster recovery method. The transmission model of scheduling centralized data is as follows Figure 1 shown.

[0004] Existing technologies allow centralized scheduling system programs to directly connect to application caches and connect to databases and local data files through remote connections and local access. However, when the network is blocked, the server fails, or is affected by third-party software, existing technologies have the following problems and shortcomings:

[0005] (1) Data consistency problem: When the scheduling centralized data uses file storage, when the scheduling centralized system program reads and writes to a file at the same time, it will cause data inconsistency problem.

[0006] (2) Low data access efficiency: When using file storage for centralized data scheduling, manual code must be written to read and write data, which is cumbersome and inefficient. File storage also cannot provide efficient data access capabilities for large-scale data and complex query requirements. Summary of the Invention

[0007] The purpose of the present invention is to provide a scheduling centralized data update and disaster recovery method based on light memory, which can solve the data consistency and data access efficiency problems existing in the current method.

[0008] The purpose of the present invention is achieved through the following technical solutions:

[0009] A method for scheduling centralized data update and disaster recovery based on lightweight storage, comprising:

[0010] A scheduling centralized data transmission model based on lightweight storage is constructed. The scheduling centralized data transmission model includes a database, application cache, and lightweight storage for storing scheduling centralized data. The human-machine interface terminal of the scheduling centralized system program is directly connected to the application cache. The application cache establishes a remote connection with the database and a local access connection with the lightweight storage. For each category of scheduling centralized data, a corresponding data type number is assigned to the database, application cache, and lightweight storage.

[0011] When the remote connection is normal, the scheduling centralized system program combines the data operation status of the human-machine interface terminal and the configured data type number to control the transmission flow of the corresponding category of scheduling centralized data in the database, application cache and light storage to achieve data update;

[0012] When the remote connection is disconnected, the scheduling centralized system program combines the data operation status of the human-machine interface terminal and the configured data type number to control the transmission flow of the corresponding category of scheduling centralized data in the application cache and light memory to achieve data update;

[0013] When the remote connection is interrupted and then restored to normal, the data disaster recovery method is triggered. The scheduling centralized system program combines the data operation status of the human-machine interface terminal and the configured data type number to control the transmission flow of the corresponding category of scheduling centralized data stored during the remote connection interruption in the database, application cache and lightweight storage to achieve data disaster recovery.

[0014] It can be seen from the technical solutions provided by the present invention that: (1) a data transmission model is constructed to ensure that read and write operations do not occur at the same time, thereby preventing data consistency problems and ensuring the accuracy of the scheduling centralized data; (2) the access efficiency of the scheduling centralized data can be significantly improved, thereby improving the overall performance of the scheduling centralized system program. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0016] Figure 1 A schematic diagram of an existing centralized scheduling data transmission model provided as background technology of the present invention;

[0017] Figure 2 A flowchart of a method for scheduling centralized data update and disaster recovery based on lightweight storage provided by an embodiment of the present invention;

[0018] Figure 3 A schematic diagram of a scheduling centralized data transmission model based on lightweight memory provided by an embodiment of the present invention;

[0019] Figure 4 A schematic diagram of data type numbering provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0020] The following is a clear and complete description of the technical solutions in the embodiments of the present invention, in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0021] First, the following terms may be used in this article:

[0022] The terms "include," "comprises," "contains," "has," or other similar expressions should be interpreted as non-exclusive. For example, "including certain technical features (such as raw materials, components, ingredients, carriers, dosage forms, materials, dimensions, parts, components, mechanisms, devices, steps, procedures, methods, reaction conditions, processing conditions, parameters, algorithms, signals, data, products, or manufactured articles, etc.) should be interpreted as including not only the technical features explicitly listed, but also other technical features known in the art that are not explicitly listed.

[0023] The term "consisting of" excludes any technical features not explicitly listed. If used in a claim, this term renders the claim closed, excluding any technical features other than those explicitly listed, except for conventional impurities associated with them. If this term appears only in a clause of a claim, it limits only the elements explicitly listed in that clause; elements listed in other clauses are not excluded from the claim as a whole.

[0024] The following describes in detail a method for scheduling centralized data updates and disaster recovery based on lightweight memory, as provided by the present invention. Any matters not described in detail in the embodiments of the present invention are prior art known to those skilled in the art. For any unspecified conditions in the embodiments of the present invention, the conditions generally used in the art or recommended by the manufacturer shall prevail.

[0025] like Figure 1 FIG. 1 is a flowchart of a method for scheduling centralized data update and disaster recovery based on a lightweight memory according to an embodiment of the present invention, which mainly includes the following steps:

[0026] Step 1: Construct a scheduling centralized data transmission model based on lightweight memory.

[0027] In the embodiment of the present invention, the following Figure 3 The scheduling centralized data transmission model based on light memory (referred to as the scheduling centralized data transmission model for short) shown in the figure includes a database, application cache and light memory for storing scheduling centralized data. The human-computer interface terminal of the scheduling centralized system program is directly connected to the application cache. The application cache establishes a remote connection with the database and a local access connection with the light memory. For each category of scheduling centralized data, corresponding data type numbers are configured for the database, application cache and light memory.

[0028] In the embodiment of the present invention, lightweight memory is a general technical term in this field. The characteristic of lightweight memory is that it has a data storage method of a database. The stored data is retained in the computer hard disk in the form of files, and the storage space occupied is significantly reduced compared to traditional databases.

[0029] In the implementation of the embodiment of the present invention, the scheduling centralized data includes four categories: static data, external data, table structure data and dynamic data; the static data is the data loaded when the scheduling centralized system program is started; the dynamic data is the data accessed when the scheduling centralized system program is running; the table structure data is information used to describe the database table structure; external data refers to data stored in the database and written and updated by other users.

[0030] Among them, the data type numbers configured for static data, external data, and table structure data are the same, and are database, application cache, and lightweight storage from small to large; the data type numbers configured for dynamic data are application cache, lightweight storage, and database from small to large.

[0031] Step 2: When the remote connection is normal or disconnected, the direction of data transmission is precisely controlled according to the pre-set update rules to achieve data update and ensure the integrity and accuracy of the data during transmission.

[0032] In this step, the data update methods are different when the remote connection is normal or disconnected, which are introduced below.

[0033] (1) When the remote connection is normal, the scheduling centralized system program combines the data operation status of the human-machine interface terminal and the configured data type number to control the transmission flow of the corresponding category of scheduling centralized data in the database, application cache and light storage to achieve data update.

[0034] In this case, the data operation states of the human-machine interface terminal include: the human-machine interface terminal reloading the scheduling centralized data, the human-machine interface terminal performing a write data operation, and the human-machine interface terminal performing a read data operation. The following describes the data update methods corresponding to the above three data operation states.

[0035] (1.1) If the data operation status of the human-machine interface terminal is: the human-machine interface terminal reloads the scheduling centralized data, then the data update involves the scheduling centralized data categories including: structure data, static data, external data and dynamic data; the scheduling centralized system program obtains table structure data, static data, external data and dynamic data from the database in sequence, and each category of scheduling centralized data is first transmitted to the application cache, and then transmitted from the application cache to the lightweight storage.

[0036] (1.2) If the data operation status of the human-machine interface terminal is: the human-machine interface terminal performs a write data operation, then the scheduling centralized data categories involved in the data update include: dynamic data; the scheduling centralized system program obtains the dynamic data from the application cache, first transmits it to the database, and then transmits it to the light storage.

[0037] (1.3) If the data operation status of the human-machine interface terminal is: the human-machine interface terminal performs a data read operation, then the scheduling centralized data categories involved in the data update include: external data and dynamic data; the scheduling centralized system program obtains external data from the database and transmits it to the application cache, and then transmits it from the application cache to the lightweight storage; thereafter, the scheduling centralized system program obtains dynamic data from the database and transmits it to the application cache, and then transmits it from the application cache to the lightweight storage.

[0038] (2) When the remote connection is disconnected, the scheduling centralized system program combines the data operation status of the human-machine interface terminal and the configured data type number to control the transmission flow of the corresponding category of scheduling centralized data in the application cache and light memory to achieve data update.

[0039] In this case, the data operation states of the human-machine interface terminal include: the human-machine interface terminal reloading the scheduling centralized data, the human-machine interface terminal performing a write data operation, and the human-machine interface terminal performing a read data operation. The following describes the data update methods corresponding to the above three data operation states.

[0040] (2.1) If the data operation status of the human-machine interface terminal is: the human-machine interface terminal reloads the scheduling centralized data, then the scheduling centralized data categories involved in the data update include: static data, external data and dynamic data; the scheduling centralized system program obtains the static data, external data and dynamic data from the light memory in sequence, and transmits them to the application cache in sequence.

[0041] (2.2) If the data operation status of the human-machine interface terminal is: the human-machine interface terminal performs a write data operation, then the scheduling centralized data categories involved in the data update include: dynamic data; the scheduling centralized system program obtains the dynamic data from the application cache and then transmits it to the lightweight storage.

[0042] (2.3) If the data operation status of the human-machine interface terminal is: the human-machine interface terminal performs a data read operation, then the scheduling centralized data categories involved in the data update include: external data and dynamic data; the scheduling centralized system program obtains the external data and dynamic data from the light memory in sequence, and transmits them to the application cache in sequence.

[0043] Step 3: When the remote connection is interrupted and then restored to normal, start the data disaster recovery plan.

[0044] In an embodiment of the present invention, when the remote connection is interrupted and then restored to normal, the data disaster recovery method is triggered, and the scheduling centralized system program combines the data operation status of the human-machine interface terminal and the configured data type number to control the transmission flow of the corresponding category of scheduling centralized data stored during the remote connection interruption in the database, application cache and lightweight storage to achieve data disaster recovery.

[0045] In this case, the data operation status of the human-machine interface terminal includes: the human-machine interface terminal performs a write data operation and the human-machine interface terminal performs a read data operation. The following describes the data disaster recovery methods corresponding to the above two data operation states.

[0046] (3.1) If the data operation status of the human-machine interface terminal is: the human-machine interface terminal performs a write data operation, then the scheduling centralized data categories involved in data disaster recovery include: dynamic data; the scheduling centralized system program obtains the dynamic data stored during the remote connection interruption from the lightweight storage, first transfers it to the application cache, and then transfers it to the database from the application cache.

[0047] (3.2) If the data operation status of the human-machine interface terminal is: the human-machine interface terminal performs a data read operation, then the scheduling centralized data categories involved in data disaster recovery include: external data;

[0048] The scheduling centralized system program obtains the external data stored during the remote connection interruption from the database, first transfers it to the application cache, and then transfers it to the lightweight storage from the application cache.

[0049] In order to more clearly demonstrate the technical solution and technical effects provided by the present invention, the method provided by the embodiment of the present invention is described in detail below with reference to specific embodiments.

[0050] 1. Scheduling centralized data transmission model.

[0051] Based on the existing scheduling centralized data transmission model, the present invention proposes a scheduling centralized data transmission model based on light memory, such as Figure 3 As shown, the local data files in the existing centralized data transmission model are replaced with lightweight storage. Lightweight storage is characterized by its database-like data storage method, where stored data is retained as files on the computer's hard drive, significantly reducing the storage space occupied by traditional databases. Lightweight storage is a lightweight database that provides complete data storage, data persistence, and data sharing capabilities. Data management adheres to the principles of atomicity, consistency, isolation, and persistence, ensuring the integrity and accuracy of database transactions.

[0052] In addition, the scheduling centralized data transmission model proposed in the present invention also adds the data transmission content of external data and table structure data on the basis of the existing scheduling centralized data transmission model. External data refers to data stored in the database and written and updated by other users. For the current user, only read operations can be performed on these external data, and no write or update operations can be performed. These external data can come from different information systems or different data sources and cannot be directly modified by the current user. Table structure data is information that describes the structure of the database table, including the table's field name, data type, constraints and other attributes. In order to ensure the effectiveness of data transmission, the lightweight memory needs to be consistent with the definition of the database table. Therefore, it is necessary to obtain table structure data from the database to ensure the accuracy of the data during transmission.

[0053] In the embodiment of the present invention, according to different data sources and data types, the symbolic definition of the centralized data transmission model is shown in Table 1.

[0054] Table 1: Symbolic definitions of the data transmission model

[0055]

[0056] In Table 1, A, B, C, and D represent static data, external data, table-structured data, and dynamic data, respectively. Because centralized scheduling data is stored simultaneously in the database, application cache, and local database, data type numbers are defined for data from different sources and types to ensure reliable data updates. The numbers following the symbols in Table 1 represent the data type numbers. Figure 4 Shows the specific data type number definition.

[0057] Lightweight storage, as the database backup mechanism in this invention, ensures that the human-machine interface terminal operates correctly as designed in the event of a database failure. The data types for static data, external data, and table structure data are numbered as database, application cache, and lightweight storage, respectively. Dynamic data, which requires frequent access and reading, is preferably updated in lightweight storage and then synchronized to the database. This improves data access performance and reduces database load. The data types for dynamic data are numbered as application cache, lightweight storage, and database, respectively.

[0058] In the embodiment of the present invention, based on the existing remote connection status, application scenarios of human-machine interface terminal data operations are added as shown in Table 2.

[0059] Table 2: Application scenarios of remote connection and human-machine interface

[0060]

[0061] In an embodiment of the present invention, the remote connection of the scheduling centralized data transmission model is divided into three application scenarios: disconnection, normal, and restoration to normal. The restart of the human-machine interface terminal corresponds to the operation of reloading static data, external data, table structure data, and dynamic data when the scheduling centralized system program is restarted after abnormal shutdown or when the daily shift is handed over. The writing of data by the human-machine interface terminal corresponds to the operation of the scheduling centralized system program storing the text content and operation diagram information displayed on the interface into the database and lightweight storage. The reading of data by the human-machine interface terminal corresponds to the operation of the scheduling centralized system program using the database or lightweight storage as the data source to refresh the text content and operation diagram information displayed on the interface. The application scenarios of remote connection and human-machine interface can be combined with each other to form the synchronization scenarios of the scheduling centralized data transmission model as shown in Table 3.

[0062] Table 3: Synchronous scenarios of the centralized data transmission model

[0063]

[0064]

[0065] In the synchronous scenario of the data transmission model shown in Table 3, the data update method precisely controls the flow of data transmission according to pre-defined update rules, both when the remote connection is normal and when it is disconnected. This ensures data integrity and accuracy during transmission. If the remote connection is interrupted for some reason and then restored, the data disaster recovery method is activated. This data disaster recovery method follows specific disaster recovery rules and aims to effectively recover centralized dispatching data that may have been lost during the remote connection loss. This ensures the continuity and stability of dispatching and command operations when the centralized dispatching system program faces data transmission issues. Due to the common dependencies between dispatching and command data items, the centralized dispatching system program does not process static data, external data, table structure data, and dynamic data simultaneously. Instead, it processes data in the order of table structure data, static data, external data, and dynamic data. In the synchronous scenario, the order of data transmission remains consistent with the order in which the centralized dispatching system program processes data.

[0066] 2. Introduction to data transmission flow in synchronization scenarios.

[0067] In the embodiment of the present invention, the data transmission flows of the eight synchronization scenarios shown in Table 3 are introduced respectively.

[0068] 1. Synchronize the data transmission direction of scenario 1.

[0069] When the remote connection is interrupted, the connection between the scheduling centralized system program and the database is disconnected. The data transmission flow when the scheduling centralized system program calls the data update method to reload the data is shown in formula (1). In formula (1), (1) (4) represents synchronization scenario 1. In this scenario, the order of data transmission executed by the scheduling centralized system program is static data, external data, and dynamic data.

[0070] (1)(4){(A3,A2),(B3,B2),(D2,D1)}(1)

[0071] When the centralized scheduling system program reloads data during a connection interruption, it retrieves static and external data from the lightweight storage and transfers them to the application cache, ensuring that the centralized scheduling data remains accessible even when the remote connection is unavailable. This process corresponds to (A3, A2) and (B3, B2) in Equation (1). Because a connection to the database cannot be established, dynamic data cannot be directly updated in the database. The centralized scheduling system program transfers the dynamic data from the lightweight storage to the application cache. Once the remote connection is restored, the dynamic data is retransmitted and stored in the database. This process corresponds to (D2, D1) in Equation (1).

[0072] In the data transfer flow formulas for each synchronization scenario, the two items in parentheses indicate that the corresponding data is transferred from the left item to the right item. For example, (A3, A2) indicates that static data in the lightweight memory is transferred to the application cache.

[0073] 2. Synchronize the data transmission direction of scenario 2.

[0074] When the remote connection is normal, the connection between the scheduling centralized system program and the database is available. The data transmission flow when the scheduling centralized system program calls the data update method to reload data is shown in formula (2). In formula (2), (2) and (4) represent synchronization scenario 2. In this scenario, the scheduling centralized system program executes data transmission in the order of table structure data, static data, external data, and dynamic data.

[0075] (2)(4){(C1,C2),(C2,C3),(A1,A2),(A2,A3),(B1,B2),(B2,B3),(D3,D1),(D1,D2))(2)

[0076] When the centralized scheduling system program reloads data during a normal connection, it retrieves table structure data, static data, and external data from the database, first loading it into the application cache and then storing it in lightweight storage for backup. This process corresponds to (C1, C2), (C2, C3), (A1, A2), (A2, A3), and (B1, B2), (B2, B3) in Equation (2). When the remote connection is normal, the centralized scheduling system program retrieves dynamic data from the database and transfers it to the application cache. Subsequently, the dynamic data is further stored in lightweight storage as backup data in the event of a remote connection interruption. This process corresponds to (D3, D1), (D1, D2) in Equation (2).

[0077] 3. Synchronize the data transmission direction of scenario 3.

[0078] When the remote connection is interrupted, the connection between the scheduling centralized system program and the database is disconnected. The data transmission flow when the scheduling centralized system program calls the data update method to perform the write data operation is shown in formula (3). In formula (3), (1) and (5) represent synchronization scenario 3. In this scenario, the data transmitted by the scheduling centralized system program is only dynamic data.

[0079] (1)(5){(D1,D2)}(3)

[0080] Since the connection with the database cannot be established, the dynamic data cannot be directly updated in the database. The scheduling centralized system program transfers the dynamic data from the application cache to the lightweight storage. After the remote connection is restored, the dynamic data is retransmitted and stored in the database. This process corresponds to (D1, D2) in formula (3).

[0081] 4. Synchronize the data transmission direction of scenario 4.

[0082] When the remote connection is normal, the connection between the scheduling centralized system program and the database is available. The data transmission flow when the scheduling centralized system program calls the data update method to perform the write data operation is shown in formula (4). In formula (4), (2) and (5) represent synchronization scenario 4. In this scenario, the data transmitted by the scheduling centralized system program is only dynamic data.

[0083] (2)(5){(D1,D3),(D1,D2)}(4)

[0084] When the remote connection is normal, the scheduling centralized system program obtains dynamic data from the application cache and transfers it to the database. Subsequently, the dynamic data is further stored in the lightweight memory as backup data in the event of a remote connection interruption. This process corresponds to (D1, D3) and (D1, D2) in formula (4).

[0085] 5. Synchronize the data transmission direction of scenario 5.

[0086] When the remote connection is reestablished and returns to normal, the scheduling centralized system program automatically triggers the data disaster recovery method to retransmit and store the data that was previously unsuccessfully written to the database due to the connection interruption. The data transmission flow when the scheduling centralized system program writes unstored data to the database is shown in formula (5). In formula (5), (3) and (5) represent synchronization scenario 5. In this scenario, the data transmitted by the scheduling centralized system program is only dynamic data.

[0087] (3)(5){(D2,D1),(D1,D3)}(5)

[0088] When the remote connection is restored, the scheduling system program retrieves the dynamic data stored during the connection interruption from the lightweight storage and transfers it to the application cache. The dynamic data is then reloaded and transferred back to the database for persistent storage. This process corresponds to (D2, D1) and (D1, D3) in Equation (5).

[0089] 6. Synchronize the data transmission direction of scenario 6.

[0090] When the remote connection is interrupted, the connection between the scheduling centralized system program and the database is disconnected. The data transmission flow when the scheduling centralized system program calls the data update method to perform the data read operation is shown in formula (6). In formula (6), (1)(6) represents synchronization scenario 6. In this scenario, the scheduling centralized system program executes data transmission in the order of external data and dynamic data.

[0091] (1)(6){(B3,B2),(D2,D1)}(6)

[0092] When the remote connection is disconnected, the scheduling centralized system program obtains the previously stored external data and dynamic data from the lightweight memory and transfers it to the application cache to ensure that the program can still read the scheduling centralized data normally when the remote connection is disconnected. This process corresponds to (B3, B2), (D2, D1) in formula (6).

[0093] 7. Synchronize the data transmission direction of scenario 7.

[0094] When the remote connection is normal, the connection between the scheduling centralized system program and the database is available. When the scheduling centralized system program calls the data update method to perform the data read operation, the data transmission flow is shown in formula (7). In formula (7), (2) and (6) represent synchronization scenario 7. In this scenario, the scheduling centralized system program executes data transmission in the order of external data and dynamic data.

[0095] (2)(6){(B1,B2),(B2,B3),(D3,D1),(D1,D2)}(7)

[0096] When the remote connection is normal, the scheduling centralized system program retrieves external data from the database and transfers it to the application cache. This data is then stored in lightweight storage as backup data in the event of a remote connection interruption. This process corresponds to (B1, B2), (B2, B3) in formula (7). The scheduling centralized system program then retrieves dynamic data from the database and transfers it to the application cache. This data is then stored in lightweight storage as backup data in the event of a remote connection interruption. This process corresponds to (D3, D1), (D1, D2) in formula (7).

[0097] 8. Synchronize the data transmission direction of scenario 8.

[0098] When the remote connection is reestablished and returns to normal, the centralized scheduling system program automatically triggers the data disaster recovery method to retransmit and read the data that was previously unsuccessfully updated due to the connection interruption. The data transmission flow when the centralized scheduling system program reads external data into the application cache is shown in formula (8). In formula (8), (3) and (6) represent synchronization scenario 8. In this scenario, the data transmitted by the centralized scheduling system program is only external data.

[0099] (3)(6){(B1,B2),(B2,B3)}(8)

[0100] When the remote connection is restored, the centralized scheduling system retrieves the external data updated during the disconnection from the database and transfers it to the application cache for timely processing. The external data is then reorganized and transferred to lightweight storage for backup. This process corresponds to (B1, B2) and (B2, B3) in Equation (8).

[0101] 3. Example description

[0102] In order to further introduce the above-mentioned scheme of the present invention, the transmission process of scheduling command data (which is a specific type of scheduling centralized data) in the scheduling centralized system program is taken as an example. The working mode of the scheduling centralized data update and disaster recovery method can be demonstrated as the 8 specific application cases shown in Table 4.

[0103] Table 4: Data update and disaster recovery method application cases

[0104]

[0105]

[0106] Based on dispatch and command requirements, the centralized dispatch system program loads text templates or construction commands onto the human-machine interface (HMI) terminal for display. Users then complete the dispatch command content in the blank spaces within the text templates. Once completed, the command body is stored. During the transmission of dispatch command data, the text templates are static data, the construction commands are external data, and the field names, data types, and constraints of the text template and construction command tables in the database are table structure data. The command body is dynamic data.

[0107] In the application cache, text templates, command bodies, and construction commands are stored in different data structures. In the database and lightweight storage, text templates, command bodies, and construction commands are stored in the text template table, command body table, and construction command table, respectively. The table structures of the data tables in the database and lightweight storage are consistent.

[0108] 1. Offline loading of scheduling command data.

[0109] When performing a shift handover operation or exiting and restarting after an error occurs when the remote connection is disconnected, the centralized scheduling system program calls the data update method to perform offline loading of scheduling command data according to the data transmission flow in synchronization scenario 1. The offline loaded scheduling command data includes the text template table, command body table, and construction command table. Since the database cannot be connected when the remote connection is disconnected, the transmitted data does not contain table structure data. The scheduling command data is loaded in the order of formula (1). The specific steps are as follows:

[0110] (1.1) The dispatching centralized system program obtains the text template table from the light memory and transfers it to the application cache. The dispatching centralized system program calls the text template table in the application cache and calls the text template on the human-machine interface.

[0111] (1.2) The centralized scheduling system program retrieves the construction order table from the lightweight storage and transfers it to the application cache. The centralized scheduling system program calls the construction order table in the application cache and displays the construction orders from other data sources on the human-machine interface.

[0112] (1.3) The centralized scheduling system program retrieves the command text table from the lightweight memory and transfers it to the application cache. The centralized scheduling system program calls the command text table in the application cache and calls the command text of the current shift and the previous shifts on the human-machine interface.

[0113] 2. Load scheduling command data online.

[0114] When performing a shift handover operation or exiting and restarting due to an error under normal remote connection conditions, the centralized scheduling system program calls the data update method to perform the online loading of scheduling command data according to the data transmission flow in synchronization scenario 2. The scheduling command data loaded online includes the table structure data of the text template table, the table structure data of the construction command table, the text template table, the command body table, and the construction command table. The scheduling command data is loaded in the order of formula (2). The specific steps are as follows:

[0115] (2.1) The centralized scheduling system program retrieves the table structure data for the text template table and the construction order table from the database and transfers it to the application cache. By loading the table structure data from the application cache, the centralized scheduling system program updates the table structure of the text template table and the construction order table in the lightweight memory to ensure consistency with the text template table and the construction order table in the database.

[0116] (2.2) The scheduling centralized system program obtains the text template table from the database and transfers it to the application cache. The text template table data is further transferred to the lightweight storage as backup data, allowing the scheduling centralized system program to call the text template in the event of a remote connection interruption.

[0117] (2.3) The centralized scheduling system program retrieves the construction order table from the database and transfers it to the application cache. The construction order table data is further transferred to lightweight storage as backup data, allowing the centralized scheduling system program to display construction orders from other data sources if the remote connection is interrupted.

[0118] (2.4) The centralized scheduling system program retrieves the command text table from the database and transfers it to the application cache. The command text table is further transferred to lightweight storage as backup data, allowing the centralized scheduling system program to recall the command text for the current shift and previous shifts in the event of a remote connection interruption.

[0119] 3. Store command text offline.

[0120] When the command body is cached through the human-machine interface when the remote connection is disconnected, the scheduling centralized system program calls the data update method to perform the operation of offline storage command body according to the data transmission flow in synchronization scenario 3. The offline stored command body is loaded into the command body table of the light memory. The command body is loaded in the order of formula (3). The specific steps are as follows:

[0121] After the scheduling centralized system program confirms the storage of the command text, the dynamic data cannot be directly updated in the database because it cannot establish a connection with the database. The command text is transferred from the application cache to the command text table in the lightweight storage as backup data. After the remote connection is restored, the command text of the current shift and historical shifts is retransmitted and stored in the database.

[0122] 4. Store command text online.

[0123] When the remote connection is normal and the command text is cached through the human-machine interface, the scheduling centralized system program calls the data update method to perform the online storage command text operation according to the data transmission flow in synchronization scenario 4. The online stored command text is loaded into the command text table of the database and the light memory respectively. The command text is loaded in the order of formula (4). The specific steps are as follows:

[0124] (4.1) After the scheduling centralized system program confirms the storage of the command text, the command text is transferred from the application cache to the command text table of the database, and the command text of the current shift or the historical shift is persisted.

[0125] (4.2) After the scheduling centralized system program confirms the storage of the command text, the command text is transferred from the application cache to the command text table of the lightweight storage as backup data, so that the scheduling centralized system program can call the command text of the current shift and the historical shift when the remote connection is interrupted.

[0126] 5. Store the command text after resuming online.

[0127] After the remote connection is restored to normal, the scheduling centralized system program will automatically trigger the data disaster recovery method to retransmit and store the command body that was previously unsuccessfully written to the database due to the connection interruption. Maintain the data consistency of the command body in the database, application cache, and lightweight storage. The scheduling centralized system program calls the data disaster recovery method according to the data transmission flow in synchronization scenario 5 to perform the operation of storing the command body after the online recovery. After the online recovery, the command body is loaded into the database command body table. The command body is loaded in the order of formula (5). The specific steps are as follows:

[0128] (5.1) After the scheduling centralized system program and the remote connection are restored, the scheduling centralized system program obtains the command text stored during the connection interruption from the light memory.

[0129] (5.2) The scheduling centralized system program reloads the command text in the application cache and transfers it to the command text table of the database, and stores the command text of the current shift or the historical shift persistently.

[0130] 6. Read scheduling command data offline.

[0131] When refreshing the construction commands and command text displayed on the human-machine interface when the remote connection is disconnected, the centralized scheduling system program calls the data update method according to the data transmission flow in synchronization scenario 6 to perform the offline reading of the scheduling command data. The offline reading of the scheduling command data includes the command text table and the construction command table. The command text table and the construction command table are loaded from the lightweight memory into the application cache. The command text is loaded according to the order of formula (6). The specific steps are as follows:

[0132] (6.1) After the scheduling centralized system program confirms the reading of the construction command, the construction command is transferred from the light memory to the application cache to ensure that the program can display the construction commands from other data sources when the remote connection is disconnected.

[0133] (6.2) After the scheduling centralized system program confirms that the command text has been read, the command text is transferred from the light memory to the application cache to ensure that the program can normally read the command text of the current shift and the historical shift when the remote connection is disconnected.

[0134] 7. Read scheduling command data online.

[0135] When refreshing the construction commands and command text displayed on the human-machine interface under normal remote connection conditions, the centralized scheduling system program calls the data update method to perform the online reading of scheduling command data based on the data transmission flow in synchronization scenario 7. The scheduling command data read online includes the command text table and the construction command table. After the command text table and the construction command table are loaded from the database into the application cache, they are then loaded into the lightweight memory. The command text is loaded in the order of formula (7). The specific steps are as follows:

[0136] (7.1) After the centralized scheduling system confirms the read construction order, it retrieves the construction order from the database and transfers it to the application cache. This data is then stored in lightweight storage as a backup data in the event of a remote connection interruption, allowing the centralized scheduling system to display construction orders from other data sources even in the event of a remote connection interruption.

[0137] (7.2) After the centralized scheduling system confirms that it has read the command text, it retrieves the command text from the database and transfers it to the application cache. This data is then stored in lightweight storage as backup data in the event of a remote connection interruption, allowing the centralized scheduling system to recall the command text for the current shift and previous shifts even in the event of a remote connection interruption.

[0138] 8. Read the construction command after returning online.

[0139] After the remote connection is restored to normal, the scheduling command system program will automatically trigger the data disaster recovery method to retransmit and read the data that was not successfully updated due to the connection interruption. Maintain the data consistency of the construction command in the database, application cache, and lightweight storage. The scheduling centralized system program calls the data disaster recovery method according to the data transmission flow in the synchronization scenario 8 to execute the operation of reading the construction command after the online recovery. After the online recovery, the construction command is loaded from the database to the application cache. The construction command is loaded in the order of formula (8). The specific steps are as follows:

[0140] (8.1) After the centralized scheduling system program recovers its connection with the remote system, it obtains the construction orders updated during the interruption from the database and transfers them from the database to the application cache.

[0141] (8.2) The scheduling centralized system program reloads the construction commands in the application cache and transfers them to the lightweight storage for backup, so that the scheduling centralized system program can also display the construction commands from other data sources when the remote connection is interrupted.

[0142] Through the description of the above embodiments, those skilled in the art will clearly understand that the above embodiments can be implemented through software or by using software plus a necessary general-purpose hardware platform. Based on this understanding, the technical solutions of the above embodiments can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, a USB flash drive, a mobile hard disk, etc.) and includes a number of instructions for causing a computer device (such as a personal computer, a server, or a network device) to execute the methods described in the various embodiments of the present invention.

[0143] The above description is merely a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present invention should be included in the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

Claims

1. A method for scheduling centralized data update and disaster recovery based on lightweight memory, characterized in that: include: A scheduling centralized data transmission model based on lightweight storage is constructed. The scheduling centralized data transmission model includes a database, application cache, and lightweight storage for storing scheduling centralized data. The human-machine interface terminal of the scheduling centralized system program is directly connected to the application cache. The application cache establishes a remote connection with the database and a local access connection with the lightweight storage. For each category of scheduling centralized data, a corresponding data type number is assigned to the database, application cache, and lightweight storage. When the remote connection is normal, the scheduling centralized system program combines the data operation status of the human-machine interface terminal and the configured data type number to control the transmission flow of the corresponding category of scheduling centralized data in the database, application cache and light storage to achieve data update; When the remote connection is disconnected, the scheduling centralized system program combines the data operation status of the human-machine interface terminal and the configured data type number to control the transmission flow of the corresponding category of scheduling centralized data in the application cache and light memory to achieve data update; When the remote connection is interrupted and then restored to normal, the data disaster recovery method is triggered. The scheduling centralized system program combines the data operation status of the human-machine interface terminal and the configured data type number to control the transmission flow of the corresponding category of scheduling centralized data stored during the remote connection interruption in the database, application cache and lightweight storage to achieve data disaster recovery.

2. The method for scheduling centralized data update and disaster recovery based on lightweight memory according to claim 1, characterized in that: For each category of the centralized scheduling data, the corresponding data type numbers configured for the database, application cache, and lightweight storage include: Scheduling centralized data includes four categories: static data, external data, table structure data, and dynamic data. Static data refers to data loaded when the scheduling centralized system program starts; dynamic data refers to data accessed when the scheduling centralized system program runs; table structure data refers to information used to describe the database table structure; external data refers to data stored in the database and written and updated by other users. The data types configured for static data, external data, and table structure data are numbered the same, in ascending order: database, application cache, and lightweight storage; the data types configured for dynamic data are numbered in ascending order: application cache, lightweight storage, and database; A, B, C, and D are used to represent static data, external data, table structure data, and dynamic data respectively. For static data A, the corresponding data types for database, application cache, and lightweight storage configuration are numbered A1, A2, and A3, respectively. For external data B, the corresponding data types for database, application cache, and lightweight storage configuration are numbered B1, B2, and B3, respectively. For table structure data C, the corresponding data types for database, application cache, and lightweight storage configuration are numbered C1, C2, and C3, respectively. For dynamic data D, the corresponding data types for database, application cache, and lightweight storage configuration are numbered D3, D1, and D2, respectively.

3. The method for scheduling centralized data update and disaster recovery based on lightweight memory according to claim 2, characterized in that: When the remote connection is normal, the scheduling centralized system program combines the data operation status of the human-machine interface terminal and the configured data type number to control the transmission flow of the corresponding category of scheduling centralized data in the database, application cache and light storage to realize data update, including: When the remote connection is normal, if the data operation status of the human-machine interface terminal is: the human-machine interface terminal reloads the scheduling centralized data, then the data update involves the scheduling centralized data categories including: structure data, static data, external data and dynamic data; The scheduling centralized system program obtains table structure data, static data, external data and dynamic data from the database in sequence. Each category of scheduling centralized data is first transferred to the application cache, and then transferred from the application cache to the lightweight storage.

4. The method for scheduling centralized data update and disaster recovery based on lightweight memory according to claim 2, characterized in that: When the remote connection is normal, the scheduling centralized system program combines the data operation status of the human-machine interface terminal and the configured data type number to control the transmission flow of the corresponding category of scheduling centralized data in the database, application cache and light storage to realize data update, including: When the remote connection is normal, if the data operation state of the human-machine interface terminal is: the human-machine interface terminal performs a write data operation, then the scheduling centralized data categories involved in the data update include: dynamic data; The scheduling centralized system program obtains dynamic data from the application cache, transfers it to the database first, and then transfers it to the lightweight storage.

5. The method for scheduling centralized data update and disaster recovery based on lightweight memory according to claim 2, characterized in that: When the remote connection is normal, the scheduling centralized system program combines the data operation status of the human-machine interface terminal and the configured data type number to control the transmission flow of the corresponding category of scheduling centralized data in the database, application cache and light storage to realize data update, including: When the remote connection is normal, if the data operation state of the human-machine interface terminal is: the human-machine interface terminal performs a read data operation, then the scheduling centralized data categories involved in the data update include: external data and dynamic data; The scheduling centralized system program obtains external data from the database and transmits it to the application cache, and then transmits it to the lightweight storage; thereafter, the scheduling centralized system program obtains dynamic data from the database and transmits it to the application cache, and then transmits it to the lightweight storage.

6. The method for scheduling centralized data update and disaster recovery based on lightweight memory according to claim 2, characterized in that: When the remote connection is disconnected, the scheduling centralized system program combines the data operation status of the human-machine interface terminal and the configured data type number to control the transmission flow of the corresponding category of scheduling centralized data in the application cache and the light memory to realize data update, including: When the remote connection is disconnected, if the data operation status of the human-machine interface terminal is: the human-machine interface terminal reloads the scheduling centralized data, then the scheduling centralized data categories involved in the data update include: static data, external data and dynamic data; The scheduling centralized system program obtains static data, external data and dynamic data from the light memory in sequence, and transmits them to the application cache in sequence.

7. The method for scheduling centralized data update and disaster recovery based on lightweight memory according to claim 2, characterized in that: When the remote connection is disconnected, the scheduling centralized system program combines the data operation status of the human-machine interface terminal and the configured data type number to control the transmission flow of the corresponding category of scheduling centralized data in the application cache and the light memory to realize data update, including: When the remote connection is disconnected, if the data operation status of the human-machine interface terminal is: the human-machine interface terminal performs a write data operation, then the data categories involved in the scheduling concentration of the data update include: dynamic data; The scheduling centralized system program obtains dynamic data from the application cache and then transfers it to the lightweight storage.

8. The method for scheduling centralized data update and disaster recovery based on lightweight memory according to claim 2, characterized in that: When the remote connection is disconnected, the scheduling centralized system program combines the data operation status of the human-machine interface terminal and the configured data type number to control the transmission flow of the corresponding category of scheduling centralized data in the application cache and the light memory to realize data update, including: When the remote connection is disconnected, if the data operation status of the human-machine interface terminal is: the human-machine interface terminal performs a read data operation, then the scheduling centralized data categories involved in the data update include: external data and dynamic data; The scheduling centralized system program obtains external data and dynamic data from the light memory in sequence and transfers them to the application cache in sequence.

9. The method for scheduling centralized data update and disaster recovery based on lightweight memory according to claim 2, characterized in that: When the remote connection is interrupted and then restored to normal, the data disaster recovery method is triggered, and the scheduling centralized system program combines the data operation status of the human-machine interface terminal and the configured data type number to control the transmission flow of the corresponding category of scheduling centralized data stored during the remote connection interruption in the database, application cache and lightweight storage to achieve data disaster recovery, including: When the remote connection is interrupted and then restored to normal, if the data operation status of the human-machine interface terminal is: the human-machine interface terminal performs a write data operation, then the scheduling centralized data categories involved in data disaster recovery include: dynamic data; The scheduling centralized system program obtains the dynamic data stored during the remote connection interruption from the lightweight storage, first transmits it to the application cache, and then transmits it to the database from the application cache.

10. The method for scheduling centralized data update and disaster recovery based on lightweight memory according to claim 2, characterized in that: When the remote connection is interrupted and then restored to normal, the data disaster recovery method is triggered, and the scheduling centralized system program combines the data operation status of the human-machine interface terminal and the configured data type number to control the transmission flow of the corresponding category of scheduling centralized data stored during the remote connection interruption in the database, application cache and lightweight storage to achieve data disaster recovery, including: When the remote connection is interrupted and then restored to normal, if the data operation status of the human-machine interface terminal is: the human-machine interface terminal performs a read data operation, then the scheduling centralized data categories involved in data disaster recovery include: external data; The scheduling centralized system program obtains the external data stored during the remote connection interruption from the database, first transfers it to the application cache, and then transfers it to the lightweight storage from the application cache.

Images