Operation regulation database system of nuclear power unit

Abstract

The invention provides a nuclear power unit operation regulation database system comprising a local regulation server which is in communication connection with a central server and is used for sending a data request instruction; the data center database is used for storing nuclear power unit operation regulation data, the data center database comprises a master database and a plurality of slave databases, and the master database and the slave databases synchronize database data in real time in a synchronous replication mode; and the central server comprises a data processing module and is used for acquiring and processing the corresponding nuclear power unit operation regulation data from the data center database according to the data request instruction and returning the processed data to the local regulation server and the data center database. According to the method, a double-database redundancy design and a high-availability cluster technology are adopted, so that the service interruption time is effectively shortened, and backup and restoration of data are ensured.

Description

Technical Field

[0001] The present invention mainly relates to the field of nuclear power technology, and in particular to a nuclear power unit operation procedure database system. Background Art

[0002] The existing nuclear power unit operation procedure database system usually provides data storage, query and data processing functions, and has certain data security guarantees. However, the existing nuclear power unit operation procedure database system has obvious shortcomings in the following aspects:

[0003] Insufficient data synchronization and backup mechanisms: Existing databases often use simple timed synchronization strategies for data synchronization and backup, lacking real-time synchronization and failover mechanisms. In scenarios such as nuclear power unit operating procedures that require extremely high real-time and reliability, once a database fails, data loss or business interruption may occur.

[0004] Low high availability and fault tolerance: Although existing technical solutions may adopt certain high availability and fault tolerance designs, in extreme cases such as power outages, hardware failures, etc., the database may not work properly, resulting in business interruption and data loss.

[0005] Limited performance and scalability: Some existing technical solutions do not adequately consider database performance optimization and scalability. With the increase in the number of nuclear power units and the continuous accumulation of procedural data, database query performance may decline and fail to meet the needs of efficient data processing and query. Summary of the invention

[0006] The technical problem to be solved by the present invention is to provide a nuclear power unit operation procedure database system to solve the problems of low high availability and fault tolerance and insufficient data synchronization and backup mechanism of the existing nuclear power unit operation procedure database system.

[0007] To solve the above technical problems, the present invention provides a nuclear power unit operating procedure database system, comprising: a local procedure server, which is communicated with a central server and is used to send data request instructions; a data center database, which is used to store nuclear power unit operating procedure data, the data center database includes a master database and multiple slave databases, and the master database and the multiple slave databases synchronize database data in real time through synchronous replication; the central server includes a data processing module, which is used to obtain and process the corresponding nuclear power unit operating procedure data from the data center database according to the data request instructions, and return the processed data to the local procedure server and the data center database.

[0008] Optionally, the master database and multiple slave databases form a high-availability cluster, and the central server also includes: a control module, which is used to adopt a dynamic load balancing strategy in the high-availability cluster to dynamically adjust data distribution and access strategies according to the real-time load conditions of each node.

[0009] Optionally, the central server also includes a fault judgment module, which is used to monitor the operating status of the main database and multiple slave databases, and judge whether the main database and multiple slave databases have faults based on the operating status; the control module is also used to obtain a judgment result from the fault judgment module, and when the main database fails, the control module automatically selects the best slave database for switching based on the judgment result and preset priority and path selection strategy.

[0010] Optionally, the central server also includes a fault prediction module, which is used to perform data analysis on the operating status of the master database and multiple slave databases to predict the database that may fail; the control module is also used to obtain prediction results from the fault prediction module, and when the database that may fail includes the master database, the best slave database is automatically selected for switching based on the prediction results and the preset priority and path selection strategy.

[0011] Optionally, the local procedure server is also used to edit the operating procedure data of the nuclear power unit, and synchronize data with the data center database at regular intervals to achieve real-time updating and backup of data.

[0012] Optionally, when the local protocol server periodically synchronizes data with the data center database, an incremental synchronization technology is used to synchronize only data that has changed since the last synchronization.

[0013] Optionally, the local server includes a local procedure database, which is used to store the operating procedure data of the nuclear power unit; in the event of a network interruption or a power outage or hardware failure in the data center database, the local server is also used to obtain and process the corresponding nuclear power unit operating procedure data from the local procedure database according to the data request instruction, store the processed data in the local procedure database, and when the normal working environment is restored, manually synchronize the data in the local procedure database to the data center database.

[0014] Optionally, the data center database supports multi-version data management. By retaining data versions at different time points, users can choose to restore to any version of the data state as needed.

[0015] Optionally, the nuclear power unit operating procedure data includes procedure data and authority data, and the central server also includes a permission management module, which is used to determine whether the user has the authority to access the procedure data based on the data request instruction and the authority data. If the user does not have the authority, a prohibited access prompt message is returned to the user.

[0016] Optionally, the nuclear power unit operation procedure data includes procedure data, flow chart data, logic diagram data, dynamic diagram data, file server data, user data and authority data.

[0017] Compared with the prior art, the nuclear power unit operation procedure database system of the present invention has the following advantages:

[0018] 1. Real-time data synchronization and failover mechanism

[0019] The present invention uses synchronous replication technology to achieve real-time synchronization of database data, ensuring the real-time and consistency of data. At the same time, by using the failover mechanism, it can quickly switch to the standby database when a database failure occurs, thereby ensuring the continuity and stability of the business. This advantage enables the present invention to maintain the normal operation of the database even in extreme cases, providing a strong guarantee for the safe and efficient operation of the nuclear power industry.

[0020] 2. Flexible data synchronization and backup strategies

[0021] The present invention designs a flexible data synchronization and backup strategy that can be customized according to actual needs. The local protocol server of each plant station synchronizes data with the data center database regularly, realizing real-time data update and backup. At the same time, in the event of network interruption or other extreme situations, the local server can continue to work instead of the main server, ensuring the normal operation of the business. This strategy not only ensures the real-time nature of the data, but also improves the reliability of the data.

[0022] 3. Data security and integrity are ensured

[0023] The present invention adopts dual database redundancy design and high-availability cluster technology, effectively reducing service interruption time and ensuring data backup and restoration. This design enables the database to quickly switch to the backup database when a failure occurs, thereby ensuring business continuity. The database system also provides a permission management function to ensure that different users can only access data within their permission range. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The accompanying drawings are included to provide a further understanding of the present application. They are included and constitute a part of the present application. The accompanying drawings illustrate embodiments of the present application and together with the present specification serve to explain the principles of the present application. In the accompanying drawings:

[0025] Figure 1 4 is a system block diagram of a nuclear power unit operation procedure database system according to an embodiment of the present invention.

[0026] Figure 2 yes Figure 1 A system block diagram of a nuclear power unit operating procedure database system of an optimized embodiment.

[0027] Figure 3 yes Figure 1 A system block diagram of a nuclear power unit operating procedure database system according to another optimized embodiment. DETAILED DESCRIPTION

[0028] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for the description of the embodiments. Obviously, the drawings described below are only some examples or embodiments of the present application. For ordinary technicians in this field, the present application can also be applied to other similar scenarios based on these drawings without creative work. Unless it is obvious from the language environment or otherwise explained, the same reference numerals in the figures represent the same structure or operation.

[0029] Figure 1 FIG. 1 is a system block diagram of a nuclear power unit operation procedure database system according to an embodiment of the present invention. Figure 1 As shown, the nuclear power plant operation procedure database system 100 includes:

[0030] A local procedure server 1, a central server 2 and a data center database 3. The data center database 3 is used to store the nuclear power unit operation procedure data. The data center database 3 includes a master database 31 and multiple slave databases 32. The master database 31 and the multiple slave databases 32 synchronize database data in real time through synchronous replication. The local procedure server 1 is communicatively connected to the central server 2, and the central server 2 includes a data processing module 21. The local procedure server 1 is used to send data request instructions. The data processing module 21 is used to obtain and process the corresponding nuclear power unit operation procedure data from the data center database 3 according to the data request instruction, and return the processed data to the local procedure server 1 and the data center database 3.

[0031] Optionally, the data processing module 21 may obtain all the nuclear power unit operation procedure data corresponding to the data request instruction from the main database 31. The data processing module 21 may also obtain part of the nuclear power unit operation procedure data corresponding to the data request instruction from the main database 31. The other part of the nuclear power unit operation procedure data may be obtained from multiple slave databases 32.

[0032] Optionally, the nuclear power unit operation procedure data includes, but is not limited to, procedure data, flow chart data, logic diagram data, dynamic diagram data, file server data, user data and authority data.

[0033] The nuclear power unit operation procedure database system of the present invention has a data center database including a master database and multiple slave databases. This redundant design ensures high availability of the database. The master database and the multiple slave databases synchronize database data in real time through synchronous replication, ensuring data consistency and reliability.

[0034] Figure 2 yes Figure 1 System block diagram of the nuclear power unit operation procedure database system of the optimized embodiment. Figure 2 As shown, the central server 2 of the nuclear power unit operation procedure database system 200 also includes a control module 20. Among them, the main database 31 and multiple slave databases 32 constitute a high availability cluster (High Availability Cluster, referred to as HA Cluster). High availability cluster refers to a server cluster technology aimed at reducing service interruption time, that is, when the current server fails, the services, resources, IP, etc. in the server can be transferred to another server to meet the continuity of the business. In other words, the main database 31 is arranged on a server, and each of the multiple slave databases 32 is arranged on a server. Each database is called a node in the high availability cluster. The control module 20 is used to adopt a dynamic load balancing strategy in the high availability cluster, and dynamically adjust the data distribution and access strategy according to the real-time load conditions of each node to ensure that each node in the cluster can be fully utilized, while avoiding performance bottlenecks caused by single point overload. Load balancing is to balance the load (work tasks or access requests) and distribute them to multiple databases for execution.

[0035] Optionally, the central server 2 also includes a fault judgment module 22. The fault judgment module 22 is used to monitor the operating status of the main database 31 and multiple slave databases 32, and judge whether the main database and multiple slave databases are faulty according to the operating status. The control module 20 is also used to obtain the judgment result from the fault judgment module 22. When the main database 31 fails, the best slave database is automatically selected for switching according to the judgment result and the preset priority and path selection strategy. For example, the preset priority and path selection strategy is for the main database 31 to preferably select the nearest slave database in the cluster as the best standby database. If the nearest slave database is not available, the second nearest slave database is selected as the best standby database, and so on. In the process of fault transfer of the present invention, the nuclear power unit operation procedure database system supports multi-path fault switching. When the main database fails, the system will automatically select the best standby database for switching according to the preset priority and path selection strategy. This multi-path switching method greatly improves the success rate and efficiency of fault transfer.

[0036] In addition to conventional fault detection and switching, the nuclear power unit operation procedure database system of the present invention also introduces intelligent monitoring and fault prediction technology. Optionally, the central server 2 also includes a fault prediction module 23. The fault prediction module 23 is used to perform data analysis on the operating status of the main database and multiple slave databases to predict the database that may fail. The control module 20 is also used to obtain the prediction result from the fault prediction module 23. When the database that may fail includes the main database, the best slave database is automatically selected for switching based on the prediction result and the preset priority and path selection strategy. Through continuous monitoring and data analysis of the operating status of the database, the system can predict possible failures, and provide early warnings and processing. This preventive fault handling method greatly improves the stability and reliability of the system.

[0037] Optionally, the central server 2 further includes a rights management module 24, which is used to determine whether the user has the rights to access the procedure data according to the data request instruction and the rights data, and if the user does not have the rights, return a prohibited access prompt message to the user.

[0038] Figure 3 yes Figure 1 A system block diagram of a nuclear power plant operation procedure database system in another optimized embodiment. Figure 3As shown, in the nuclear power unit operation procedure database system 300, the local procedure server 1 is also used to edit the nuclear power unit operation procedure data, and synchronizes data with the data center database 3 at regular intervals to achieve real-time data update and backup. For example, the procedure compiler edits new nuclear power unit operation procedure data through the local procedure server 1, or the procedure compiler modifies the nuclear power unit operation procedure data in the data center database 3 through the local procedure server 1. Specifically, the data request instruction is an instruction to obtain the nuclear power unit operation procedure data, and the data processing module 21 is used to obtain the corresponding nuclear power unit operation procedure data from the data center database 3 according to the data request instruction, and then return the nuclear power unit operation procedure data to the local procedure server 1, and the procedure compiler modifies the nuclear power unit operation procedure data through the local procedure server 1 according to the demand. The local procedure server 1 synchronizes data with the data center database 3 at regular intervals, and synchronizes the modified nuclear power unit operation procedure data to the data center database 3.

[0039] Optionally, when the local protocol server 1 synchronizes data with the data center database 3 on a regular basis, an incremental synchronization technology is used to synchronize only the data that has changed since the last synchronization. Different from the general full synchronization, the present invention uses an incremental synchronization technology to synchronize only the data that has changed since the last synchronization, which greatly reduces the synchronization time and bandwidth usage and improves the synchronization efficiency.

[0040] like Figure 3 As shown, the local server 1 includes a local procedure database 11. The local procedure database 11 is used to store the operation procedure data of the nuclear power unit. In the case of network interruption or power failure of the data center database 3 or hardware failure, the local server 1 is also used to obtain and process the corresponding operation procedure data of the nuclear power unit from the local procedure database according to the data request instruction, and store the processed data in the local procedure database 11. When the normal working environment is restored, the data of the local procedure database 11 is manually synchronized to the data center database 3. The present invention designs a flexible data synchronization and backup strategy. The local procedure server of each plant station synchronizes data with the data center database regularly, realizing real-time update and backup of data. At the same time, in the event of network interruption or other extreme situations, the local server can continue to work instead of the central server, ensuring the normal operation of the business. This strategy not only ensures the real-time nature of the data, but also improves the reliability of the data. The real-time update and backup of data are ensured by combining scheduled synchronization and manual synchronization.

[0041] Optionally, in order to cope with data requirements in different scenarios, the data center database supports multi-version data management. By retaining data versions at different time points, users can choose to restore to any version of the data state as needed, thereby improving data flexibility and availability.

[0042] The basic concepts have been described above. Obviously, for those skilled in the art, the above invention disclosure is only used as an example and does not constitute a limitation of the present application. Although not explicitly stated herein, those skilled in the art may make various modifications, improvements and amendments to the present application. Such modifications, improvements and amendments are suggested in the present application, so such modifications, improvements and amendments still belong to the spirit and scope of the exemplary embodiments of the present application.

[0043] At the same time, the present application uses specific words to describe the embodiments of the present application. For example, "one embodiment", "an embodiment", and / or "some embodiments" refer to a certain feature, structure or characteristic related to at least one embodiment of the present application. Therefore, it should be emphasized and noted that "one embodiment" or "an embodiment" or "an alternative embodiment" mentioned twice or more in different positions in this specification does not necessarily refer to the same embodiment. In addition, some features, structures or characteristics in one or more embodiments of the present application can be appropriately combined.

[0044] As shown in this application, unless the context clearly indicates an exception, the words "a", "an", "a kind" and / or "the" do not refer to the singular, but also include the plural. Generally speaking, the terms "include" and "comprise" only indicate the inclusion of the steps and elements that have been clearly identified, and these steps and elements do not constitute an exclusive list. The method or device may also include other steps or elements.

[0045] Unless otherwise specifically stated, the relative arrangement, numerical expressions and numerical values ​​of the parts and steps set forth in these embodiments do not limit the scope of the application. Meanwhile, it should be understood that, for ease of description, the sizes of the various parts shown in the accompanying drawings are not drawn according to actual proportional relationships. The technology, methods and equipment known to those of ordinary skill in the relevant art may not be discussed in detail, but in appropriate cases, the technology, methods and equipment should be considered as a part of the specification. In all examples shown and discussed here, any specific value should be interpreted as being merely exemplary, rather than as a limitation. Therefore, other examples of exemplary embodiments may have different values. It should be noted that similar reference numerals and letters represent similar items in the following drawings, and therefore, once a certain item is defined in an accompanying drawing, it does not need to be further discussed in subsequent drawings.

[0046] In the description of the present application, it should be understood that the directions or positional relationships indicated by directional words such as "front, back, up, down, left, right", "lateral, vertical, perpendicular, horizontal" and "top, bottom" are usually based on the directions or positional relationships shown in the drawings, and are only for the convenience of describing the present application and simplifying the description. Unless otherwise specified, these directional words do not indicate or imply that the device or element referred to must have a specific direction or be constructed and operated in a specific direction, and therefore cannot be understood as limiting the scope of protection of the present application; the directional words "inside and outside" refer to the inside and outside relative to the contours of each component itself.

[0047] For ease of description, spatially relative terms such as "above", "above", "on the upper surface of", "above", etc. may be used here to describe the spatial positional relationship between a device or feature and other devices or features as shown in the figure. It should be understood that spatially relative terms are intended to include different orientations of the device in use or operation in addition to the orientation described in the figure. For example, if the device in the accompanying drawings is inverted, the device described as "above other devices or structures" or "above other devices or structures" will be positioned as "below other devices or structures" or "below other devices or structures". Thus, the exemplary term "above" can include both "above" and "below". The device can also be positioned in other different ways (rotated 90 degrees or in other orientations), and the spatially relative descriptions used here are interpreted accordingly.

[0048] In addition, it should be noted that the use of words such as "first" and "second" to define components is only for the convenience of distinguishing the corresponding components. If not otherwise stated, the above words have no special meaning and cannot be understood as limiting the scope of protection of this application. In addition, although the terms used in this application are selected from well-known and commonly used terms, some terms mentioned in the specification of this application may be selected by the applicant at his or her discretion, and their detailed meanings are explained in the relevant parts of the description of this article. In addition, it is required to understand this application not only by the actual terms used, but also by the meaning implied by each term.

[0049] It should be understood that when a component is referred to as being "on another component," "connected to another component," "coupled to another component," or "contacting another component," it may be directly on, connected to, coupled to, or contacting the other component, or there may be intervening components. In contrast, when a component is referred to as being "directly on another component," "directly connected to," "directly coupled to," or "directly contacting" another component, there are no intervening components. Similarly, when a first component is referred to as being "electrically in contact with" or "electrically coupled to" a second component, there is an electrical path between the first component and the second component that allows current to flow. The electrical path may include capacitors, coupled inductors, and / or other components that allow current to flow, even without direct contact between conductive components.

[0050] Some aspects of the present application may be performed entirely by hardware, entirely by software (including firmware, resident software, microcode, etc.), or by a combination of hardware and software. The above hardware or software may be referred to as "data blocks", "modules", "engines", "units", "components" or "systems". The processor may be one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DAPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, or combinations thereof. In addition, various aspects of the present application may be expressed as computer products located in one or more computer-readable media, which include computer-readable program codes. For example, computer-readable media may include, but are not limited to, magnetic storage devices (e.g., hard disks, floppy disks, tapes ...), optical disks (e.g., compact disks CDs, digital versatile disks DVDs ...), smart cards, and flash memory devices (e.g., cards, sticks, key drives ...).

[0051] A computer-readable medium may include a propagated data signal containing computer program code, such as in baseband or as part of a carrier wave. The propagated signal may have a variety of manifestations, including electromagnetic, optical, etc., or a suitable combination. A computer-readable medium may be any computer-readable medium other than a computer-readable storage medium, which may be connected to an instruction execution system, device or apparatus to communicate, propagate or transmit a program for use. The program code on the computer-readable medium may be propagated via any suitable medium, including radio, cable, fiber optic cable, radio frequency signal, or similar medium, or any combination of the above mediums.

[0052] Similarly, it should be noted that in order to simplify the description of the disclosure of this application and thus help understand one or more embodiments of the invention, in the above description of the embodiments of the present application, multiple features are sometimes combined into one embodiment, figure or description thereof. However, this disclosure method does not mean that the subject of the present application requires more features than the features mentioned. In fact, the features of the embodiment are less than all the features of the single embodiment disclosed above.

[0053] In some embodiments, numbers describing the number of components and attributes are used. It should be understood that such numbers used in the description of the embodiments are modified by the modifiers "about", "approximately" or "substantially" in some examples. Unless otherwise specified, "about", "approximately" or "substantially" indicate that the numbers are allowed to vary by ±20%. Accordingly, in some embodiments, the numerical parameters used in the specification are approximate values, which may change according to the required features of individual embodiments. In some embodiments, the numerical parameters should take into account the specified significant digits and adopt the general method of retaining the digits. Although the numerical domains and parameters used to confirm the breadth of the range in some embodiments of the present application are approximate values, in specific embodiments, the setting of such numerical values ​​is as accurate as possible within the feasible range.

[0054] Although the present application has been described with reference to the current specific embodiments, ordinary technicians in this technical field should recognize that the above embodiments are only used to illustrate the present application, and various equivalent changes or substitutions may be made without departing from the spirit of the present application. Therefore, as long as the changes and modifications to the above embodiments are within the essential spirit of the present application, they will fall within the scope of the present application.

Claims

1. A nuclear power unit operation procedure database system, characterized in that: include: A local protocol server is connected to the central server for sending data request instructions; A data center database is used to store nuclear power unit operation procedure data, the data center database includes a master database and multiple slave databases, and the master database and the multiple slave databases synchronize database data in real time through synchronous replication; The central server includes a data processing module, which is used to obtain and process the corresponding nuclear power unit operation procedure data from the data center database according to the data request instruction, and return the processed data to the local procedure server and the data center database.

2. The nuclear power unit operation procedure database system according to claim 1, characterized in that: The master database and multiple slave databases form a high-availability cluster, and the central server also includes: The control module is used to adopt a dynamic load balancing strategy in the high-availability cluster to dynamically adjust the data distribution and access strategy according to the real-time load conditions of each node.

3. The nuclear power unit operation procedure database system according to claim 2, characterized in that: The central server also includes: A fault judgment module, used to monitor the operating status of the master database and the multiple slave databases, and judge whether the master database and the multiple slave databases have faults according to the operating status; The control module is also used to obtain a judgment result from the fault judgment module, and when a fault occurs in the master database, automatically select the best slave database for switching according to the judgment result and a preset priority and path selection strategy.

4. The nuclear power unit operation procedure database system according to claim 3, characterized in that: The central server also includes: A fault prediction module, used to perform data analysis on the operating status of the master database and multiple slave databases, and predict the database that may fail; The control module is also used to obtain prediction results from the fault prediction module, and when the database that may fail includes the master database, automatically select the best slave database for switching according to the prediction results and the preset priority and path selection strategy.

5. The nuclear power unit operation procedure database system according to claim 1, characterized in that: The local procedure server is also used to edit the operating procedure data of the nuclear power unit, and synchronize data with the data center database at regular intervals to achieve real-time update and backup of data.

6. The nuclear power unit operation procedure database system according to claim 5, characterized in that: When the local protocol server synchronizes data with the data center database at regular intervals, it adopts incremental synchronization technology to synchronize only the data that has changed since the last synchronization.

7. The nuclear power unit operation procedure database system according to claim 5, characterized in that: The local server includes a local procedure database, and the local procedure database is used to store the operation procedure data of the nuclear power unit; In the event of a network interruption or a power outage or hardware failure in the data center database, the local server is also used to obtain and process the corresponding nuclear power unit operating procedure data from the local procedure database according to the data request instruction, store the processed data in the local procedure database, and when the normal working environment is restored, manually synchronize the data in the local procedure database to the data center database.

8. The nuclear power unit operation procedure database system according to claim 1, characterized in that: The data center database supports multi-version data management. By retaining data versions at different time points, users can choose to restore to any version of the data state as needed.

9. The nuclear power unit operation procedure database system according to claim 1, characterized in that: The nuclear power unit operating procedure data includes procedure data and authority data. The central server also includes an authority management module. The authority management module is used to determine whether the user has the authority to access the procedure data based on the data request instruction and the authority data. If the user does not have the authority, a prohibited access prompt message is returned to the user.

10. The nuclear power unit operation procedure database system according to any one of claims 1 to 9, characterized in that: The nuclear power unit operation procedure data includes procedure data, flow chart data, logic diagram data, dynamic diagram data, file server data, user data and authority data.

Images