Multi-database integrated platform management system
By designing a multi-database integrated platform management system, data synchronization and sharing are used to synchronize and share data, the problems of untimely updates, chaotic access rights and low data synchronization security in heterogeneous database management are solved, and data is realized efficient management and security.
Patent Information
- Application Number
- CN202410891485.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-04
- Publication Date
- 2025-02-18
- Estimated Expiration
- 2044-07-04
AI Technical Summary
The heterogeneous database management between different platforms has defects such as untimely updates, chaotic access permissions, and low data synchronization security. Especially when multi-platform mutual communication and sharing, the shared data takes up too much space, which increases the system burden.
Design a multi-database integrated platform management system, connect more than two sub-databases and a shared database through a synchronization module, set up a first storage node and a second storage node, the first storage node stores non-shared data, and the second storage node stores Share data, the shared database integrates the shared data of each sub-database. The data synchronization is synchronized by a timed polling module, a first data synchronization encryption and decryption module and a second data synchronization encryption and decryption module, and the stored procedure statements are stored through the standby module to realize data sharing and recovery.
By decoupling data editing and query functions, data delay problems when the user querys information under heterogeneous database systems are avoided, source data security is improved, efficient data management and triple backup mechanism are realized, and data loss is eliminated The situation.
Smart Images

Figure CN118779380B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of database management, and in particular to a multi-database integrated platform management system. Background Art
[0002] In today's information age, with the increasing division of labor in the industry and the requirements of laws and administrative regulations, information exchange and sharing between different platforms has become an industry necessity. However, heterogeneous database management between different platforms has defects such as untimely updates, confusing access rights, and low data synchronization security. In addition, when there are many platforms that need to communicate and share, it is inevitable that shared data will occupy too much space and increase the system burden. Summary of the invention
[0003] In order to solve the shortcomings of the existing technology, the present invention provides a multi-database integrated platform management system, including more than two sub-databases and a shared database, and the more than two sub-databases are connected with the shared database information through a synchronization module;
[0004] Each sub-database is provided with a first storage node and a second storage node, the first storage node stores non-shared data, and the second storage node stores shared data;
[0005] The shared database integrates the shared data in the second storage node of each sub-database;
[0006] The synchronization module includes a timing polling module, a first data synchronization encryption and decryption module and a second data synchronization encryption and decryption module which are sequentially connected in information. The timing polling module is used to regularly poll the update information of the shared data in the second storage node in each sub-database, and notify the first data synchronization encryption module to synchronize and share the updated data to the shared database when an update occurs;
[0007] It also includes a backup module for storing stored procedure statements, which cooperates with the first data synchronization encryption and decryption module, the second data synchronization encryption and decryption module and the shared database to jointly complete the synchronization of shared data.
[0008] Among them, a complete implementation mechanism for the sub-database to transmit shared data to the shared database includes:
[0009] First data synchronization encryption and decryption module part:
[0010] Step 1: Obtain a list of storage processes for shared data and a source code file of encrypted information from the second storage node;
[0011] Step 2: Obtain the parameter information and text information of the shared data from the stored procedure list through semantic recognition;
[0012] Step 3: Concatenate parameter information and text information to obtain a stored procedure statement;
[0013] Step 4: Extract the initial encryption information and initial decryption information of the shared data from the source code file of the encrypted information;
[0014] Step 5: obtaining advanced encryption information and advanced decryption information by updating the security level of the initial encryption information and the initial decryption information;
[0015] Step 6: Transmit the advanced decryption information to the second data synchronization encryption and decryption module;
[0016] Step 7: Use advanced encryption information to encrypt the stored procedure statement obtained in step 3 and the source code file of the encrypted information obtained in step 1, and transmit the encrypted stored procedure statement and the source code file of the encrypted information to the second data synchronization encryption and decryption module.
[0017] Second data synchronization encryption and decryption module part:
[0018] Step 8: Decrypt the encrypted stored procedure statement and the source code file of the encrypted information transmitted in step 7 using the advanced decryption information to obtain the decrypted stored procedure statement and the source code file of the encrypted information;
[0019] Step 9: The decrypted stored procedure statement is transmitted to the shared database, and the decrypted stored procedure statement and the source code file of the encrypted information are transmitted to the standby module;
[0020] Backup module part: stores the decrypted stored procedure statements and the source code files of the encrypted information;
[0021] Shared database part: obtain the shared data of the second storage node based on the stored procedure statement.
[0022] When a sub-database fails, the process of restoring shared data based on the backup module includes:
[0023] Second data synchronization encryption and decryption module part:
[0024] Step a, obtaining the stored procedure statements of the corresponding shared data and the source code files of the encrypted information from the backup module;
[0025] Step b, extracting the initial encryption information and initial decryption information of the shared data from the source code file of the encrypted information;
[0026] Step c, obtaining advanced encryption information and advanced decryption information by updating the security level of the initial encryption information and the initial decryption information;
[0027] Step d, using advanced encryption information to encrypt the stored procedure statement obtained in step a;
[0028] Step e: transmitting the advanced decryption information and the encrypted stored procedure statement to the first data synchronization encryption and decryption module.
[0029] The first data synchronization encryption and decryption module part: uses the advanced decryption information to decrypt the encrypted stored procedure statement to obtain the decrypted stored procedure statement, and transmits the decrypted stored procedure statement to the second storage node of the corresponding sub-database;
[0030] Sub-database part: obtains the shared data of the second storage node based on the stored procedure statement.
[0031] When a shared database fails, the process of restoring shared data based on the backup module includes: obtaining a stored procedure statement of the shared data from the backup module, and obtaining the shared data of the second storage node based on the stored procedure statement.
[0032] When a standby module fails, the process of recovering data from the shared database includes:
[0033] Second data synchronization encryption and decryption module part:
[0034] Step 1, obtaining a list of stored procedures for shared data in a shared database and a source code file for encrypted information;
[0035] Step m: Obtain parameter information and text information of shared data from the stored procedure list through semantic recognition;
[0036] Step n, concatenating parameter information and text information to obtain a stored procedure statement;
[0037] Step o: transfer the source code file of the stored procedure statement and the encrypted information to the backup module.
[0038] When a standby module fails, the process of recovering data from the sub-database includes:
[0039] First data synchronization encryption and decryption module part:
[0040] Step p, obtaining a storage process list of shared data and a source code file of encrypted information from the second storage node;
[0041] Step q: Obtain parameter information and text information of shared data from the stored procedure list through semantic recognition;
[0042] Step r, concatenate parameter information and text information to obtain a stored procedure statement;
[0043] Step s, extracting the initial encryption information and initial decryption information of the shared data from the source code file of the encrypted information;
[0044] Step t, obtaining advanced encryption information and advanced decryption information by updating the security level of the initial encryption information and the initial decryption information;
[0045] Step u, transmitting the advanced decryption information to the second data synchronization encryption and decryption module;
[0046] Step v: encrypt the stored procedure statement obtained in step r and the source code file of the encrypted information obtained in step p using advanced encryption information, and transmit the encrypted stored procedure statement and the source code file of the encrypted information to the second data synchronization encryption and decryption module.
[0047] Second data synchronization encryption and decryption module part:
[0048] Step w, using the advanced decryption information to decrypt the encrypted stored procedure statement and the source code file of the encrypted information transmitted in step v, to obtain the decrypted stored procedure statement and the source code file of the encrypted information;
[0049] Step x: transfer the decrypted stored procedure statement and the source code file of the encrypted information to the backup module.
[0050] The multi-data integrated platform management system provided by the present invention provides a set of systematic heterogeneous database data management methods and systems based on the needs of existing multi-platform data intercommunication and sharing, decouples data editing and query functions, avoids data delay problems when users query information in heterogeneous database systems, and improves source data security. At the same time, the triple data backup mechanism not only saves data storage space to the maximum extent, but also ensures efficient data management and prevents data loss. BRIEF DESCRIPTION OF THE DRAWINGS
[0051] Figure 1 : Logical framework diagram of the multi-database integrated platform management system of the present invention. DETAILED DESCRIPTION
[0052] In order to have a further understanding of the technical solution and beneficial effects of the present invention, the technical solution and beneficial effects produced by the present invention are described in detail below with reference to the accompanying drawings.
[0053] Figure 1 The multi-database integrated platform management system provided by the present invention comprises more than two sub-databases and a shared database, and the more than two sub-databases are connected with the shared database information through a synchronization module.
[0054] Sub-databases can be used by platforms to exchange and share information according to needs, and the shared database integrates the data of each sub-database to achieve information exchange and sharing among multiple platforms;
[0055] Taking real estate registration as an example, according to legal requirements, the agriculture, forestry, ocean and other departments should realize data intercommunication and sharing. Then multiple sub-databases can be used for agriculture, forestry, ocean and other departments to store the data involved in their business, while the shared database integrates the data that the agriculture, forestry, ocean and other departments need to intercommunication and sharing. In this way, due to the setting of the shared database, a unified shared information query interface is provided, the editing and viewing functions of the data are decoupled, the data delay problem when the user query information in the heterogeneous database system is avoided, and the source data security is improved; at the same time, the setting of the shared database is equivalent to setting up a common backup database for multiple sub-databases, and the data of multiple sub-databases are uniformly backed up, monitored and managed, simplifying the data management process.
[0056] In the present invention, taking one of the sub-databases as an example, the synchronization implementation mechanism of each sub-database and the shared database is described in detail.
[0057] Two storage nodes can be set in the sub-database, and the size of the storage node is set according to the needs of the business. One storage node (hereinafter referred to as the first storage node) stores business process data, and the other storage node (second storage node) stores shared data that needs to be communicated and shared; wherein, business process data refers to all original data, process data, or historical update data involved in the business processing process. These data are convenient for later verification and use. Without special circumstances, they are only used for archiving and have no sharing needs. Therefore, for this type of data, backup and monitoring management are performed according to ordinary data management methods; and shared data mostly involves business processing results or user's direct registration information and other data that need to be communicated and shared. Therefore, for this type of data, backup and monitoring management are performed according to the method of the present invention.
[0058] The synchronization module includes a timing polling module, a first data synchronization encryption and decryption module and a second data synchronization encryption and decryption module which are connected in sequence. The timing polling module is used to periodically poll the update information of the shared data in the second storage node, and notify the first data synchronization encryption module to synchronize and share the updated data to the shared database when an update occurs.
[0059] The second storage node stores the timestamp of the relevant database. When the data in the second storage node changes (such as the administrator deletes, adds or modifies it), the time information corresponding to the timestamp is updated accordingly. The timed polling module polls and stores the timestamp in the second storage node at a predetermined period, and then compares it with the timestamp stored in the previous polling cycle: if they are consistent, it means that the data in the second storage node has not changed in the current polling cycle, and no processing is performed; if they are inconsistent, it means that the data in the second storage node has been updated in the current polling cycle. At this time, the timed polling module notifies the first data synchronization encryption module to synchronize and share the updated data to the shared database.
[0060] In the shared database, the updated data will overwrite the previous data; in the sub-database, the data before the update is stored as process data in the first storage node, and the second storage node only stores the latest updated data.
[0061] The present invention also includes a backup module for storing stored procedure statements, which cooperates with the first data synchronization encryption and decryption module, the second data synchronization encryption and decryption module and the shared database to jointly complete the synchronization of shared data. A complete implementation mechanism is as follows:
[0062] First data synchronization encryption and decryption module part:
[0063] 1. Obtain the storage process list of shared data and the source code file of encrypted information from the second storage node;
[0064] 2. Obtain the parameter information and text information of shared data from the stored procedure list through semantic recognition;
[0065] 3. Concatenate parameter information and text information to obtain the stored procedure statement;
[0066] 4. Extract the initial encryption information and initial decryption information of the shared data from the source code file of the encrypted information;
[0067] 5. By updating the security level of the initial encryption information and the initial decryption information, advanced encryption information and advanced decryption information are obtained;
[0068] 6. Transmit the advanced decryption information to the second data synchronization encryption and decryption module;
[0069] 7. Use the advanced encryption information to encrypt the stored procedure statement obtained in step 3 and the source code file of the encrypted information obtained in step 1, and transmit the encrypted stored procedure statement and the source code file of the encrypted information to the second data synchronization encryption and decryption module.
[0070] Second data synchronization encryption and decryption module part:
[0071] 8. Use the advanced decryption information to decrypt the encrypted stored procedure statement and the source code file of the encrypted information transmitted in step 7 to obtain the decrypted stored procedure statement and the source code file of the encrypted information;
[0072] 9. Transfer the decrypted stored procedure statement to the shared database, and transfer the decrypted stored procedure statement and the source code file of the encrypted information to the backup module;
[0073] Backup module part: stores the decrypted stored procedure statements and the source code files of the encrypted information;
[0074] Shared database part: obtain the shared data of the second storage node based on the stored procedure statement.
[0075] At this point, a complete data synchronization process is completed.
[0076] It can be understood that, based on the above data sharing mechanism, the standby module stores the stored procedure statements of the shared data in the second storage node of all sub-databases, so when a shared database or any sub-database fails, the shared data can be restored through the stored procedure statements in the standby module; similarly, when a standby module fails, the stored procedure statements can also be extracted from the shared data in the shared database or sub-database. Therefore, the present invention is equivalent to providing a triple protection mechanism, ensuring that the data will not be damaged, and because the standby module stores the stored procedure statements, it does not take up too much space.
[0077] When a sub-database fails, the process of restoring shared data based on the standby module is as follows:
[0078] Second data synchronization encryption and decryption module part:
[0079] a. Obtain the stored procedure statements of the corresponding shared data and the source code files of the encrypted information from the backup module;
[0080] b. Extract the initial encryption information and initial decryption information of the shared data from the source code file of the encrypted information;
[0081] c. Obtaining advanced encryption information and advanced decryption information by updating the security level of the initial encryption information and the initial decryption information;
[0082] d. Use advanced encryption information to encrypt the stored procedure statement obtained in step a;
[0083] e. Transmit the advanced decryption information and the encrypted stored procedure statement to the first data synchronization encryption and decryption module.
[0084] The first data synchronization encryption and decryption module part: uses the advanced decryption information to decrypt the encrypted stored procedure statement to obtain the decrypted stored procedure statement, and transmits the decrypted stored procedure statement to the second storage node of the corresponding sub-database;
[0085] Sub-database part: Get the shared data of the second storage node based on the stored procedure statement (the shared data includes the stored procedure list and the encrypted information source code file. Therefore, in the process of data recovery based on the stored procedure statement, there is no need to transmit the encrypted information source code file. The next time the shared data of the second storage node needs to be shared to the shared database, the stored procedure list of the shared data and the encrypted information source code file can still be obtained through step 1 above).
[0086] When a shared database fails, the process of restoring shared data based on the backup module is as follows: obtaining a stored procedure statement of the shared data from the backup module, and obtaining the shared data of the second storage node based on the stored procedure statement.
[0087] In other words, in the present invention, the sub-databases are independent of different sub-platforms, while the shared database and the backup module run on the same shared platform, so when the shared database recovers data from the backup module, there is no need to encrypt the interacted data.
[0088] Furthermore, the second data synchronization encryption and decryption module runs on the same shared platform as the shared database and the backup module. Therefore, when the backup module fails, data recovery is performed from the shared database first. In this way, the recovered data does not need to be transmitted through the first data synchronization encryption and decryption module and the second data synchronization encryption and decryption module, and therefore there is no need to encrypt the data. Moreover, the data can be recovered after one transmission process. Only when the shared database also fails does the backup module need to recover data from each sub-database one by one.
[0089] When a standby module fails, the process of restoring data from the shared database is as follows:
[0090] Second data synchronization encryption and decryption module part:
[0091] 1. Obtain the list of stored procedures for shared data in the shared database and the source code files for encrypted information;
[0092] m. Obtain the parameter information and text information of shared data from the stored procedure list through semantic recognition;
[0093] n. Concatenate parameter information and text information to obtain a stored procedure statement;
[0094] o. Transfer the source code files of the stored procedure statements and encrypted information to the backup module.
[0095] When a standby module fails, the process of restoring data from the sub-database is as follows:
[0096] First data synchronization encryption and decryption module part:
[0097] p. Obtain the storage process list of shared data and the source code file of encrypted information from the second storage node;
[0098] q. Obtain the parameter information and text information of shared data from the stored procedure list through semantic recognition;
[0099] r. Concatenate parameter information and text information to obtain stored procedure statements;
[0100] s. Extract the initial encryption information and initial decryption information of the shared data from the source code file of the encrypted information;
[0101] t. By updating the security level of the initial encryption information and the initial decryption information, the advanced encryption information and the advanced decryption information are obtained;
[0102] u. Transmitting the advanced decryption information to the second data synchronization encryption and decryption module;
[0103] v. Use the advanced encryption information to encrypt the stored procedure statement obtained in step r and the source code file of the encrypted information obtained in step p, and transmit the encrypted stored procedure statement and the source code file of the encrypted information to the second data synchronization encryption and decryption module.
[0104] Second data synchronization encryption and decryption module part:
[0105] w. Decrypt the encrypted stored procedure statement and the source code file of the encrypted information transmitted in step v using the advanced decryption information to obtain the decrypted stored procedure statement and the source code file of the encrypted information;
[0106] x. Transfer the decrypted stored procedure statements and the source code files of the encrypted information to the backup module.
[0107] It should be noted that: in the present invention, whether it is a data sharing process or a data recovery process, the information transmitted by the first data synchronization encryption and decryption module and the second data synchronization encryption and decryption module are all stored procedure statements, rather than shared data itself. In this way, even if the information is intercepted during the transmission process, outside the network environment or integrated environment where the multi-database integrated platform management system of the present invention is located, it is impossible to obtain the final shared data based on the intercepted information. Therefore, when a sub-database or a shared database fails, data recovery is performed based on the backup module. Only when the backup module also fails, the sub-database will perform data recovery through the shared database, or the shared database will perform data recovery through the sub-database.
[0108] In the present invention, in order to ensure the security of data transmission between the first data synchronization encryption and decryption modules in the sub-databases, multiple first data synchronization encryption and decryption modules can be set corresponding to the multiple sub-databases, so that a first data synchronization encryption and decryption module is set on the platform on which each sub-database runs, and the timing polling module is connected to the multiple first data synchronization encryption and decryption modules. When the shared data in the corresponding sub-database is found to change, the corresponding first data synchronization encryption and decryption module is notified to share the data.
[0109] The present invention also includes an abstract interface module and a permission verification module. The permission verification module is informationally connected to the abstract interface module, and the abstract interface module is connected to each sub-database and a shared database. The permission verification module stores the operation permissions of all upper-level users on the data in each sub-database and a shared database. The operation permissions include read permissions and write permissions. The write permissions include all operation permissions that can cause data changes, such as adding, deleting, and modifying. The present invention sets the write permission only for the sub-database, that is, all upper-level users can only read the data in the shared database, but cannot write or modify it. The abstract interface module encapsulates all interface call instances for reading or writing each sub-database and a shared database. According to the permissions of the upper-level users obtained from the permission verification module, the corresponding interface is fed back for the upper-level user to call, so as to read or write the data in the sub-database or the shared database.
[0110] It can be understood that the abstract interface module of the present invention encapsulates the read interface call instance and the write interface call instance of each sub-database, as well as the read interface call instance of the shared database.
[0111] Therefore, the present invention encapsulates the interface call instances of each sub-database and shared database through an abstract interface module, decouples data management from actual access management, and eliminates the need to perform permission verification through data setting label rows in each sub-database and shared database. When modifying permissions, only the permission setting data in the permission verification module needs to be changed, making permission management and data management more convenient.
[0112] In the actual application scenario, the data intercommunication and sharing of the three departments of agriculture, forestry and ocean are still taken as an example: the staff of the agricultural department can only access the data of the sub-database corresponding to the agricultural department, and for the data of the forestry and ocean departments, they need to access the shared database. The staff of the agricultural department cannot directly read the data in the sub-database corresponding to the forestry and ocean departments (that is, the personnel of other departments can only see the data that can be shared outside the department, and have no access to the process data involved in the business process, etc.). Therefore, the specific working logic of the permission verification module of the present invention is as follows:
[0113] The permission verification module stores a sub-database operation permission library for each sub-database. At the same time, a shared data read permission library is stored for the shared database. Each sub-database operation permission library corresponds to an access tag that is unique to the sub-database; each upper-level user corresponds to an access object tag, and the access object tag corresponds to the access tag one by one.
[0114] When an upper-level user needs to access data in a sub-database, the permission verification module first needs to verify whether the upper-level user's access object label is consistent with the access label of the corresponding sub-database:
[0115] If they are consistent, it means that the upper-level user has the access rights to the corresponding sub-database (for example, when the staff of the marine department access the sub-database of the marine department, they will get consistent verification results, but when the staff of the marine department want to access the sub-database of the forestry department, they will get inconsistent verification results). Then, the specific operation permissions of the upper-level user are further determined (involving read-only permissions and read-write permissions);
[0116] In case of inconsistency, the upper-level user is directly denied access to the relevant sub-database.
[0117] The shared data read permission library does not need to set access tags. It directly verifies whether the upper-level user has the permission to read the shared data in the shared database based on the permission data stored in the permission library.
[0118] In summary, the present invention can achieve the following technical effects:
[0119] 1. By setting up shared databases and sub-databases, the editing and querying functions of data are decoupled, avoiding the data delay problem when the user queries information in a heterogeneous database system, and improving the security of source data;
[0120] 2. The settings of shared database, backup module and sub-database provide a triple protection mechanism for the management of the entire data, completely eliminating the defect of data loss in unexpected circumstances;
[0121] 3. The setting of the first storage node and the second storage node of the sub-database ensures that the original data is isolated from the shared data on the basis of data intercommunication and sharing, which not only satisfies data sharing, but also ensures the security of the original data and saves the space occupied by the shared data. At the same time, the setting of the shared data storage process statement in the standby module also saves the space occupied by data backup.
[0122] 4. By updating the security level of the initial encryption information and the initial decryption information, and combining the encryption, transmission and decryption of the stored procedure statements, the data transmission security is guaranteed to the greatest extent;
[0123] 5. The settings of shared database, backup module and sub-database provide a triple guarantee mechanism for the management of the entire data and a complete data recovery mechanism. Based on the different platforms to which the data belongs, different recovery methods are customized and applicable to a variety of data recovery scenarios;
[0124] 6. Through the setting of abstract interface modules, the interface call instances of each sub-database and shared database are encapsulated, and data management is decoupled from actual access management. There is no need to verify permissions through the data setting tag lines in each sub-database and shared database. When modifying permissions, only the permission setting data in the permission verification module needs to be changed, making permission management and data management more convenient;
[0125] 7. Based on the requirements of different platforms for data permissions, different user permissions are determined for shared databases and each sub-database, further ensuring the security of data in each sub-database while meeting data sharing needs.
[0126] Although the present invention has been described using the above preferred embodiments, they are not intended to limit the scope of protection of the present invention. Any person skilled in the art may make various changes and modifications to the above embodiments without departing from the spirit and scope of the present invention. The scope of protection of the present invention shall be based on the definition of the claims.
Claims
1. Multi-database integrated platform management system, characterized by: It is applicable to more than two sub-databases and one shared database, and the more than two sub-databases are connected with the shared database information through the synchronization module; Each sub-database is provided with a first storage node and a second storage node, the first storage node stores non-shared data, and the second storage node stores shared data; The shared database integrates the shared data in the second storage node of each sub-database; The synchronization module includes a timing polling module, a first data synchronization encryption and decryption module and a second data synchronization encryption and decryption module which are sequentially connected in information. The timing polling module is used to regularly poll the update information of the shared data in the second storage node in each sub-database, and notify the first data synchronization encryption module to synchronize and share the updated data to the shared database when an update occurs; It also includes a backup module for storing stored procedure statements, which cooperates with the first data synchronization encryption and decryption module, the second data synchronization encryption and decryption module and the shared database to jointly complete the synchronization of shared data; A complete implementation mechanism for transferring shared data from a sub-database to a shared database includes: First data synchronization encryption and decryption module part: Step 1: Obtain a list of storage processes for shared data and a source code file of encrypted information from the second storage node; Step 2: Obtain the parameter information and text information of the shared data from the stored procedure list through semantic recognition; Step 3: Concatenate parameter information and text information to obtain a stored procedure statement; Step 4: Extract the initial encryption information and initial decryption information of the shared data from the source code file of the encrypted information; Step 5: obtaining advanced encryption information and advanced decryption information by updating the security level of the initial encryption information and the initial decryption information; Step 6: Transmit the advanced decryption information to the second data synchronization encryption and decryption module; Step 7: Encrypt the stored procedure statement obtained in step 3 and the source code file of the encrypted information obtained in step 1 by using the advanced encryption information, and transmit the encrypted stored procedure statement and the source code file of the encrypted information to the second data synchronization encryption and decryption module; Second data synchronization encryption and decryption module part: Step 8: Decrypt the encrypted stored procedure statement and the source code file of the encrypted information transmitted in step 7 using the advanced decryption information to obtain the decrypted stored procedure statement and the source code file of the encrypted information; Step 9: The decrypted stored procedure statement is transmitted to the shared database, and the decrypted stored procedure statement and the source code file of the encrypted information are transmitted to the standby module; Backup module part: stores the decrypted stored procedure statements and the source code files of the encrypted information; Shared database part: obtaining the shared data of the second storage node based on the stored procedure statement; When a sub-database fails, the process of restoring shared data based on the standby module includes: Second data synchronization encryption and decryption module part: Step a, obtaining the stored procedure statements of the corresponding shared data and the source code files of the encrypted information from the backup module; Step b, extracting the initial encryption information and initial decryption information of the shared data from the source code file of the encrypted information; Step c, obtaining advanced encryption information and advanced decryption information by updating the security level of the initial encryption information and the initial decryption information; Step d, using advanced encryption information to encrypt the stored procedure statement obtained in step a; Step e: transmitting the advanced decryption information and the encrypted stored procedure statement to the first data synchronization encryption and decryption module; The first data synchronization encryption and decryption module part: uses the advanced decryption information to decrypt the encrypted stored procedure statement to obtain the decrypted stored procedure statement, and transmits the decrypted stored procedure statement to the second storage node of the corresponding sub-database; Sub-database part: obtains the shared data of the second storage node based on the stored procedure statement; When a shared database fails, the process of restoring shared data based on the backup module includes: obtaining a stored procedure statement of the shared data from the backup module, and obtaining the shared data of the second storage node based on the stored procedure statement.
2. The multi-database integrated platform management system according to claim 1, characterized in that: When a standby module fails, the process of restoring data from the shared database includes: Second data synchronization encryption and decryption module part: Step 1, obtaining a list of stored procedures for shared data in a shared database and a source code file for encrypted information; Step m: Obtain parameter information and text information of shared data from the stored procedure list through semantic recognition; Step n, concatenating parameter information and text information to obtain a stored procedure statement; Step o: transfer the source code file of the stored procedure statement and the encrypted information to the backup module.
3. The multi-database integrated platform management system according to claim 1, characterized in that: When a standby module fails, the process of restoring data from the sub-database includes: First data synchronization encryption and decryption module part: Step p, obtaining a storage process list of shared data and a source code file of encrypted information from the second storage node; Step q: Obtain parameter information and text information of shared data from the stored procedure list through semantic recognition; Step r, concatenate parameter information and text information to obtain a stored procedure statement; Step s, extracting the initial encryption information and initial decryption information of the shared data from the source code file of the encrypted information; Step t, obtaining advanced encryption information and advanced decryption information by updating the security level of the initial encryption information and the initial decryption information; Step u, transmitting the advanced decryption information to the second data synchronization encryption and decryption module; Step v, using the advanced encryption information to encrypt the stored procedure statement obtained in step r and the source code file of the encryption information obtained in step p, and transmitting the encrypted stored procedure statement and the source code file of the encryption information to the second data synchronization encryption and decryption module; Second data synchronization encryption and decryption module part: Step w, using the advanced decryption information to decrypt the encrypted stored procedure statement and the source code file of the encrypted information transmitted in step v, to obtain the decrypted stored procedure statement and the source code file of the encrypted information; Step x: transfer the decrypted stored procedure statement and the source code file of the encrypted information to the backup module.
Citation Information
Patent Citations
Block chain-based data information sharing system and cloud platform thereof
CN114911868A