Method and apparatus for parallel maintenance of power common information model based on fragmentation

Abstract

The application provides a power common information model-based sharding parallel maintenance method and device and electronic equipment. The method comprises the following steps: dividing a power common information model into multiple shards according to a maintenance range division and a hierarchical relationship of the power common information model, each shard containing a complete hierarchical structure of the power common information model; generating an offline maintenance copy corresponding to each shard from a real-time database storing the power common information model according to the divided shards, the offline maintenance copy containing data of a model object in the power common information model; performing an add, delete, modify and query operation on the offline maintenance copy corresponding to each shard, and publishing the maintained shard offline maintenance copy to the real-time database.

Description

Technical Field

[0001] This invention relates to the field of power automation, and specifically to a segmented parallel maintenance method, apparatus, and electronic equipment based on a power public information model. Background Technology

[0002] In the field of power dispatch automation monitoring systems, real-time data and power grid models are stored in real-time databases to meet the needs of rapid calculations in applications. Maintenance personnel need to maintain the power grid model in the real-time database in a timely manner according to the development and changes of the power grid to ensure that the model used in the application calculations is correct. For large-scale power dispatch systems, the power grid changes frequently, and single-person maintenance cannot meet the requirements. Therefore, multiple people are needed to maintain the model information in the real-time database in parallel. Ensuring the efficiency and reliability of parallel maintenance is crucial for the safe operation of power dispatch automation systems. Summary of the Invention

[0003] This application aims to provide a method, device, and electronic equipment for sharded parallel maintenance based on a power public information model. By dividing the real-time library model into multiple sharded maintenance copies through the hierarchical relationship and maintenance scope of the public information model, parallel maintenance of the copies within each shard can be achieved.

[0004] According to one aspect of this application, a segmented parallel maintenance method based on a power public information model is proposed, comprising:

[0005] The power public information model is divided into multiple segments according to the division of maintenance scope and the hierarchical relationship of the power public information model. Each segment contains the complete hierarchical structure of the power public information model.

[0006] Based on the partitioned data, an offline maintenance copy corresponding to each partition is generated from the real-time database storing the power public information model. The offline maintenance copy contains data of the model objects in the power public information model.

[0007] Perform CRUD operations on the offline maintenance replicas corresponding to the shards, and publish the maintained offline maintenance replicas of the shards to the real-time database.

[0008] According to some embodiments, the method includes:

[0009] The model objects in the shards are used to generate critical paths according to the hierarchical relationship of the public information model, and the critical path cache is stored along with the shard information to which the model objects belong.

[0010] According to some embodiments, the method includes:

[0011] The operations of adding, deleting, modifying, and querying the offline maintenance replicas corresponding to the shards, and publishing the maintained offline maintenance replicas to the real-time database, include:

[0012] Receive CRUD commands for the offline maintenance copy, perform corresponding operations on the offline maintenance copy, and record maintenance logs for each step of the operation.

[0013] When the maintenance operation only involves model data within a shard, the integrity of the maintenance result is verified. If the verification passes, the offline maintenance copy of the shard is published to the real-time database. If the verification fails, an error message is returned.

[0014] According to some embodiments, the method includes:

[0015] The step of performing CRUD operations on the offline maintenance replicas corresponding to the shards, and publishing the maintained offline maintenance replicas to the real-time database, further includes:

[0016] When maintenance operations involve other shards, cross-shard cross-maintenance is achieved based on cross-shard conflict negotiation and resolution mechanisms and cross-shard maintenance integrity verification.

[0017] According to some embodiments, the method includes:

[0018] When maintenance operations involve other shards, cross-shard cross-maintenance is achieved based on cross-shard conflict negotiation and resolution mechanisms and cross-shard maintenance integrity checks, including:

[0019] Obtain the maintenance record log;

[0020] The critical path cache is searched for the shard information involved in the cross-shard maintenance operation, where the shard information is the shard to which the maintenance object belongs;

[0021] Based on the maintenance log of this shard, compare whether there is a maintenance conflict. If there is, perform conflict negotiation and resolution. After resolving the conflict, perform cross-shard maintenance integrity verification. If there is no conflict, perform cross-shard maintenance integrity verification directly.

[0022] After verification, multiple offline maintenance copies are published to the real-time database.

[0023] According to some embodiments, the method includes:

[0024] When maintenance operations involve other shards, the method of implementing cross-shard cross-maintenance based on cross-shard conflict negotiation and resolution mechanisms and cross-shard maintenance integrity verification also includes:

[0025] Send a notification message, including the model object and attribute information corresponding to the conflicting maintenance object;

[0026] Displays multiple maintenance results for the conflicting maintenance objects;

[0027] In response to confirmation of the adopted maintenance result, the maintenance result is notified to other shards that maintain the conflicting maintenance objects, and the maintenance result is written to the offline maintenance copies corresponding to the multiple shards that participated in the conflict negotiation and resolution.

[0028] According to some embodiments, the method includes:

[0029] When maintenance operations involve other shards, cross-shard cross-maintenance is achieved based on cross-shard conflict negotiation and resolution mechanisms and cross-shard maintenance integrity checks, including:

[0030] The integrity of multiple fragments is verified according to the integrity verification rules of the public information model. If the verification passes, the association relationship of the public information model is verified. If the verification fails, a verification error message is returned.

[0031] According to some embodiments, the method includes:

[0032] When maintenance operations involve other shards, the method of implementing cross-shard cross-maintenance based on cross-shard conflict negotiation and resolution mechanisms and cross-shard maintenance integrity verification also includes:

[0033] The public information model association verification includes verifying whether objects within a shard and objects maintained across shards have a complete public information model association. If the association is complete, the verification passes; otherwise, an error message is returned.

[0034] According to some embodiments, the method includes:

[0035] The critical path cache records the full path information of the maintenance object. The full path information is a hierarchical string composed of the names of the maintenance objects at each level from the root node down to the maintenance object according to the power public information model.

[0036] According to another aspect of this application, a segmented parallel maintenance device based on a power public information model is provided, comprising:

[0037] The segmentation management module is used to divide the power public information model into multiple segments according to the maintenance scope and hierarchical relationship of the power public information model. Each segment contains the complete hierarchical structure of the power public information model. Based on the segmentation, the real-time database storing the power public information model generates an offline maintenance copy corresponding to the segment. The offline maintenance copy contains the data of the model objects in the power public information model.

[0038] The intra-shard maintenance and inter-shard coordination module is used to perform CRUD operations on the offline maintenance copies corresponding to the shards, and publish the maintained offline maintenance copies of the shards to the real-time database.

[0039] According to another aspect of this application, an electronic device is provided, comprising:

[0040] A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the method described in any one of the above methods.

[0041] According to another aspect of this application, a computer program product is provided, comprising a computer program or instructions that, when executed by a processor, implement the method described in any one of the above methods.

[0042] According to the example embodiment of this application, the real-time library model is divided into multiple sharded maintenance copies by means of the hierarchical relationship and maintenance scope of the public information model, so as to realize the parallel maintenance of the copies within the shards.

[0043] It should be understood that the above general description and the following detailed description are merely exemplary and do not limit this application. Attached Figure Description

[0044] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below.

[0045] Figure 1 A flowchart illustrating a segmented parallel maintenance method based on a power public information model according to an example embodiment of this application is shown.

[0046] Figure 2 A schematic diagram of fragment maintenance according to an example embodiment of this application is shown.

[0047] Figure 3 A schematic diagram of the sharded parallel maintenance process according to an example embodiment of this application is shown.

[0048] Figure 4 A schematic diagram of the on-chip maintenance process according to an example embodiment of this application is shown.

[0049] Figure 5 A schematic diagram of the inter-chip coordination and maintenance process according to an example embodiment of this application is shown.

[0050] Figure 6 A schematic diagram of a conflict negotiation and resolution process according to an example embodiment of this application is shown.

[0051] Figure 7 A schematic diagram of the cross-chip maintenance integrity verification process according to an example embodiment of this application is shown.

[0052] Figure 8 A diagram illustrating a device for sliced ​​parallel maintenance based on a power public information model according to an example embodiment of this application is shown.

[0053] Figure 9 A block diagram of an electronic device according to an exemplary embodiment is shown. Detailed Implementation

[0054] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the embodiments set forth herein; rather, they are provided so that this application will be thorough and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted.

[0055] Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a thorough understanding of embodiments of this application. However, those skilled in the art will recognize that the technical solutions of this application can be practiced without one or more of the specific details, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known methods, apparatuses, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of this application.

[0056] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0057] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0058] It should be understood that although the terms first, second, third, etc., may be used herein to describe various components, these components should not be limited by these terms. These terms are used to distinguish one component from another. Therefore, the first component discussed below may be referred to as the second component without departing from the teachings of this application. As used herein, the term "and / or" includes all combinations of any one and more of the associated listed items.

[0059] Those skilled in the art will understand that the accompanying drawings are merely schematic diagrams of exemplary embodiments, and the modules or processes in the drawings are not necessarily essential for implementing this application, and therefore cannot be used to limit the scope of protection of this application.

[0060] In traditional techniques, multiple maintenance personnel simultaneously modify the same real-time database model. Since the power grid model must pass integrity verification before it can be submitted to the operating program, if some personnel have not completed their maintenance work while others submit their own maintenance content, the integrity verification program may fail to verify the entire real-time database due to the incomplete model parts, affecting the timely submission of the completed parts and impacting maintenance efficiency. Furthermore, during parallel maintenance, two parties involved may modify the model parts that the other is maintaining (i.e., cross-maintenance). In this case, according to the logic of the real-time database, the earlier submitted modification will be directly overwritten by the later submitted modification. This situation has a certain probability of causing the real-time database model submitted to the operating program to be inconsistent with the actual situation, adversely affecting the stable operation of the power dispatch automation system.

[0061] Therefore, traditional methods suffer from low processing efficiency and reliability issues when performing parallel maintenance of real-time databases. Based on this, it is necessary to address these technical problems by providing a real-time database sharding parallel maintenance method based on a power public information model. This method aims to improve maintenance parallelism, reduce mutual interference during parallel maintenance, and thus improve maintenance efficiency.

[0062] This application discloses a real-time database sharding parallel maintenance method based on a common information model (CIM). Addressing the issue of mutual interference caused by multiple concurrent maintenance of real-time database models in the field of power dispatch automation monitoring systems, this method proposes a real-time database sharding parallel maintenance approach based on a CIM. This method divides the real-time database model into multiple sharded maintenance copies through the hierarchical relationship and maintenance scope of the CIM, achieving parallel maintenance of copies within each shard. It resolves the cross-sharding cross-maintenance problem of the real-time database based on cross-sharding conflict negotiation and resolution mechanisms and cross-sharding maintenance integrity verification mechanisms. Furthermore, it improves the efficiency of quickly locating cross-sharding conflicts by searching for maintenance shard information in the critical path cache based on the full path information of the maintained object.

[0063] Compared with existing technologies, it achieves the effects of segmented isolation, parallel maintenance, and parallel submission of maintenance results, thus improving maintenance efficiency. At the same time, the cross-segment coordination mechanism solves the stability problems caused by multiple people modifying the model during parallel maintenance, ensuring the operational reliability of the power dispatch automation system.

[0064] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of this application.

[0065] Figure 1A flowchart illustrating a segmented parallel maintenance method based on a power public information model according to an example embodiment of this application is shown.

[0066] See Figure 1 In S101, the power public information model is divided into multiple segments according to the division of maintenance scope and the hierarchical relationship of the power public information model. Each segment contains the complete hierarchical structure of the power public information model.

[0067] The Common Information Model (CIM) is an abstract model used to describe all major objects of a power company, particularly those related to power operation. It provides a standard method for representing power system resources using object classes and attributes and the relationships between them.

[0068] According to some embodiments, the power CIM model and real-time data are stored in a real-time database. The power CIM model here can be any model in the field of power automation, such as a power business model or a power monitoring model.

[0069] For example, the power monitoring business model in the real-time database is divided into several segments according to the maintenance division of labor and the hierarchical relationship of the CIM model. Each segment contains a complete local hierarchical structure. All objects in each segment are used to generate critical paths according to the hierarchical relationship of the CIM model and stored in the critical path cache along with the segment information to which the objects belong. A detailed diagram of segment maintenance can be found here. Figure 2 As shown.

[0070] In S103, based on the partitioned segments, an offline maintenance copy corresponding to each segment is generated from the real-time database storing the power CIM model. The offline maintenance copy contains data of the model objects in the power CIM model.

[0071] According to some embodiments, the running real-time library is divided into shards to generate offline maintenance copies. Each shard corresponds to one maintenance copy. The maintenance copy contains model data, and the corresponding real-time data is not refreshed. It is only used for model maintenance, thereby preventing the maintenance process from directly affecting the online running real-time library.

[0072] In S105, add, delete, modify, and query operations are performed on the offline maintenance replicas corresponding to the shards, and the maintained offline maintenance replicas of the shards are published to the real-time database.

[0073] According to some embodiments, by loading a maintenance copy containing a complete power grid model, the system receives CRUD commands from maintenance personnel, performs corresponding operations on the maintenance copy, and records maintenance logs for each step of the operation.

[0074] When maintenance operations only involve intra-slice models, the integrity of the intra-slice model maintenance results can be verified. If it passes, the maintained model within the slice scope will be published to the running real-time library. If it fails, the verification error will be fed back to the maintenance personnel for modification and verification again. When maintenance operations involve other slices, an application can be submitted to the inter-slice coordination maintenance module, which will complete the cross-slice collaborative verification and model publication. The inter-slice coordination maintenance module is only a name set for implementing the inter-slice coordination maintenance function and can be replaced with other names in specific applications.

[0075] When maintenance operations involve other shards, cross-shard cross-maintenance is achieved based on cross-shard conflict negotiation and resolution mechanisms and cross-shard maintenance integrity verification. For details, please refer to [link to documentation / document]. Figure 5 and Figure 6 As shown.

[0076] The aforementioned method for parallel maintenance of real-time database shards based on the power CIM model divides the real-time database model into multiple shard maintenance copies through the hierarchical relationship and maintenance scope of the CIM model, enabling parallel maintenance of copies within each shard. It addresses the issue of cross-shard maintenance of the real-time database based on cross-shard conflict negotiation and resolution mechanisms and cross-shard maintenance integrity verification mechanisms. Furthermore, it provides technical support for rapid location of cross-shard conflicts by searching for maintenance shard information in the critical path cache based on the full path information of the maintenance object, thus improving location efficiency.

[0077] Compared with existing technologies, it achieves the effects of segmentation and isolation, parallel maintenance, and parallel submission of maintenance results, thus improving the efficiency of parallel maintenance. At the same time, the cross-segment coordination mechanism solves the stability problems caused by multiple people modifying the model during parallel maintenance, thereby improving the operational reliability of the power dispatch automation system.

[0078] Figure 2 A schematic diagram of fragment maintenance according to an example embodiment of this application is shown.

[0079] See Figure 2 The power CIM models in the real-time database, such as power monitoring business models, are divided according to maintenance scope. The maintenance scope includes, for example, the main control area, sub-control areas (dispatch areas A and B), each substation, and the internal hierarchical structure of the substations. Dispatch area A and its subordinate substations 1 and 2 are divided into one segment, dispatch area B and its subordinate substations 3 and 4 are divided into another segment, and the main control area as a whole is divided into two segments. Each segment contains a complete local hierarchical structure.

[0080] Figure 3 A schematic diagram of the sharded parallel maintenance process according to an example embodiment of this application is shown.

[0081] See Figure 3According to some embodiments, when implementing the segmented parallel maintenance method based on the power CIM model, it can be achieved through a segmented management module, an intra-segment maintenance module, an inter-segment coordinated maintenance module, and a critical path cache module.

[0082] The segmentation management module divides the power monitoring business model in the real-time database into several segments according to the maintenance division of labor and the hierarchical relationship of the CIM model. Each segment contains a complete local hierarchical structure. It generates critical paths for all objects in each segment according to the CIM model hierarchical relationship and stores them in the critical path cache along with the segment information to which the objects belong. It generates offline maintenance copies of the running real-time database according to the segments, with one maintenance copy corresponding to one segment. The maintenance copy contains model data, and the dynamic real-time data is not refreshed; it is only used for model maintenance, thus preventing the maintenance process from directly affecting the online running real-time database. The segmentation management module distributes the copies to multiple parallel in-segment maintenance modules, which then complete the segment maintenance work.

[0083] The intra-segment maintenance module loads a maintenance copy containing a complete power grid model. It receives CRUD (Create, Read, Update, Delete) commands from maintenance personnel and performs corresponding operations on the maintenance copy, recording maintenance logs for each step. When maintenance operations only involve the intra-segment model, the intra-segment maintenance module can verify the integrity of the maintenance results. If successful, the maintained model within the segment is published to the running real-time database. If unsuccessful, the error is fed back to the maintenance personnel for correction and re-verification. When maintenance operations involve other segments, the intra-segment maintenance module submits an application to the inter-segment coordination maintenance module, which then completes cross-segment collaborative verification and model publication.

[0084] The inter-shard coordination and maintenance module searches for the shard information involved in cross-shard maintenance in the critical path cache based on the maintenance records. The retrieved shard information is the shard to which the maintained object belongs according to the sharding rules. It then obtains the maintenance records for this shard and compares whether there are any maintenance conflicts, i.e., multiple shards maintaining the same attribute of the same object at the same time. If such conflicts exist, the module enters the conflict negotiation and resolution process. After resolving the conflicts, the module enters the cross-shard maintenance integrity verification process. If no conflicts exist, the module enters the cross-shard maintenance integrity verification process. After the verification process, the maintenance results of multiple shard models are published to the running real-time library.

[0085] The conflict negotiation and resolution process is initiated by the inter-segment coordination and maintenance module. It notifies the maintenance segment to which the conflicting model object belongs, as well as the specific conflicting model object and attribute information. The maintenance tool interface of this segment displays multiple maintenance results for the conflicting object. The personnel responsible for the maintenance of this segment confirm which maintenance result to adopt, notify other segments that have maintained the conflicting model object, and write the result into the maintenance copies of multiple segments participating in the conflict negotiation and resolution process.

[0086] Figure 4 A schematic diagram of the on-chip maintenance process according to an example embodiment of this application is shown.

[0087] See Figure 4 According to some embodiments, by loading a maintenance copy containing a complete power grid model, the system receives CRUD commands from maintenance personnel, performs corresponding operations on the maintenance copy, and records maintenance logs for each step of the operation.

[0088] When the maintenance operation only involves the on-chip model, the on-chip maintenance module performs an integrity check on the on-chip model maintenance results, such as whether the device is idle or whether there is a corresponding time threshold value for exceeding the limit. If it passes, the model within the maintained segment range is published to the running real-time library. If it fails, the error is fed back to the maintenance personnel for modification and verification again.

[0089] When maintenance operations involve other shards, the intra-shard maintenance module submits a request to the inter-shard coordination maintenance module, which then completes the cross-shard collaborative verification and model release.

[0090] Figure 5 A schematic diagram of the inter-chip coordination and maintenance process according to an example embodiment of this application is shown.

[0091] According to some embodiments, the shard information involved in cross-shard maintenance is searched in the critical path cache based on the maintenance records. The retrieved shard information is the shard to which the maintained object belongs according to the sharding rules. The maintenance records of this shard are then obtained, and a comparison is made to see if there is a maintenance conflict. That is, multiple shards maintain the same attribute of the same object at the same time. For example, if the same line spans two shards, a conflict may occur if both shards modify the capacity parameters of the line. If a conflict exists, a conflict negotiation and resolution process is initiated. After the conflict is resolved, a cross-shard maintenance integrity verification process is initiated. If no conflict exists, a cross-shard maintenance integrity verification process is initiated. The maintenance results of multiple shard models after the verification process are published to the running real-time library.

[0092] The critical path cache records the full path information of model objects, which is a hierarchical string composed of object names from the root node down to the maintenance object in the CIM model. For example, the object names at each level are separated by " / " from left to right to form the full path name from the root object to the end object, and the corresponding segment name is composed of a key-value pair <full path name, segment name>. For example, <Substation A / 110kV / Interval I / Switch 501# / Active Power P,part01>, where the full path information Substation A / 110kV / Interval I / Switch 501# / Active Power P represents the full path of the active power P measuring point object under the device Switch 501#, with the substation name being Substation A, the voltage level being 110kV, the interval name being Interval I, and the device name being Switch 501#. This is used as the key, and the segment name part01 is used as the value.

[0093] When the cross-shard coordination and maintenance module looks for shard information related to a model object contained in a maintenance record, it searches for the parent object of the model object in the real-time library, and then searches for the parent's parent object, and so on recursively until the root node object is found. Then, it searches for the shard information corresponding to this full path in the critical path cache library according to the full path string consisting of the complete object name from the root object to the maintained model object.

[0094] Figure 6 A schematic diagram of a conflict negotiation and resolution process according to an example embodiment of this application is shown.

[0095] According to some embodiments, the conflict negotiation and resolution process can be initiated by the inter-segment coordination and maintenance module, which notifies the maintenance segment to which the conflicting model object belongs of the specific conflicting model object and attribute information, and displays multiple maintenance results of the conflicting object in the maintenance tool interface of this segment, such as line capacity parameters spanning two segments. The personnel responsible for the maintenance of this segment confirm which maintenance result to adopt, notify other segments that have maintained the conflicting model object, and write the result into the maintenance copies of multiple segments participating in the conflict negotiation and resolution process.

[0096] Figure 7 A schematic diagram of the cross-chip maintenance integrity verification process according to an example embodiment of this application is shown.

[0097] According to some implementations, the cross-segment maintenance integrity verification process verifies the integrity of multiple segments according to the CIM model integrity verification rules. If it passes, it proceeds to the CIM association verification; if it fails, it returns a verification error message and requires maintenance personnel to make further modifications. The CIM association verification checks whether the objects within a segment have a complete CIM association relationship with the objects maintained across segments. For example, a line is associated with substation A and substation B, and the two substations belong to different segments. The name and ID of the line's counterpart substation B need to be recorded in the substation A object, and the name and ID of the line's counterpart substation A also need to be recorded in the substation B object. If the association relationship is complete, the verification passes; if the relationship is incomplete, it returns a verification error message and requires maintenance personnel to make further modifications.

[0098] It should be clearly understood that this application describes how specific examples are formed and used, but this application is not limited to any details of these examples. Rather, based on the teachings of the disclosure of this application, these principles can be applied to many other embodiments.

[0099] Those skilled in the art will understand that all or part of the steps of the above embodiments are implemented as a computer program executed by a CPU. When the computer program is executed by the CPU, the program that performs the functions defined by the methods provided in this application can be stored in a computer-readable storage medium, such as a read-only memory, a magnetic disk, or an optical disk.

[0100] Furthermore, it should be noted that the above figures are merely illustrative representations of the processes included in the method according to exemplary embodiments of this application, and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal order of these processes. Additionally, it is readily understood that these processes may be executed synchronously or asynchronously, for example, in multiple modules.

[0101] Through the description of the exemplary embodiments, those skilled in the art will readily understand that, according to the embodiments of this application... Figure 1 The segmented parallel maintenance method based on the power CIM model shown in the example embodiment of this application has at least one or more of the following advantages.

[0102] According to the example implementation, the real-time library model is divided into multiple shard maintenance copies by the CIM model hierarchy and maintenance scope, realizing parallel maintenance of copies within shards; the cross-shard conflict negotiation resolution mechanism and the cross-shard maintenance integrity verification mechanism solve the problem of cross-shard maintenance of the real-time library; and the maintenance shard information is searched in the critical path cache according to the full path information of the maintenance object to provide technical support for the rapid location of cross-shard conflicts, thereby improving the location efficiency.

[0103] According to the example implementation, the effects of segmentation and isolation, parallel maintenance, and parallel submission of maintenance results are achieved, which improves the efficiency of parallel maintenance. At the same time, the cross-segment coordination mechanism solves the stability problem caused by multiple people modifying the model in parallel maintenance, and improves the operational reliability of the power dispatch automation system.

[0104] The following describes an apparatus embodiment of this application, which can be used to perform the method embodiment of this application. For details not disclosed in the apparatus embodiment of this application, please refer to the method embodiment of this application.

[0105] Figure 8 A block diagram of a segmented parallel maintenance device based on a power public information model, according to an exemplary embodiment, is shown. Figure 8 The apparatus shown can perform the methods described above according to the embodiments of this application.

[0106] like Figure 8 As shown, the embedded software authentication device may include: a chip management module 810 and an intra-chip maintenance and inter-chip coordination module 820.

[0107] See Figure 8 Referring to the preceding description, the segmentation management module 810 is used to divide the power CIM model into multiple segments according to the maintenance scope and hierarchical relationship of the power CIM model. Each segment contains the complete hierarchical structure of the power CIM model. Based on the segmentation, the real-time database storing the power CIM model generates an offline maintenance copy corresponding to the segment. The offline maintenance copy contains the data of the model objects in the power CIM model.

[0108] The intra-shard maintenance and inter-shard coordination module 820 is used to perform CRUD operations on the offline maintenance copies corresponding to the shards, and publish the maintained offline maintenance copies of the shards to the real-time database.

[0109] The device performs functions similar to those described above; other functions are described in the preceding descriptions and will not be repeated here.

[0110] Figure 9 A block diagram of an electronic device according to an exemplary embodiment is shown.

[0111] The following reference Figure 9 To describe an electronic device 200 according to this embodiment of the present application. Figure 9 The electronic device 200 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0112] like Figure 9As shown, the electronic device 200 is presented in the form of a general-purpose computing device. The components of the electronic device 200 may include, but are not limited to: at least one processing unit 210, at least one storage unit 220, a bus 230 connecting different system components (including storage unit 220 and processing unit 210), a display unit 240, etc.

[0113] The storage unit stores program code, which can be executed by the processing unit 210, causing the processing unit 210 to perform the methods described in this specification according to various exemplary embodiments of this application.

[0114] Storage unit 220 may include readable media in the form of volatile storage units, such as random access memory (RAM) 2201 and / or cache memory 2202, and may further include read-only memory (ROM) 2203.

[0115] Storage unit 220 may also include a program / utility 2204 having a set (at least one) program module 2205, such program module 2205 including but not limited to: operating system, one or more application programs, other program modules and program data, each or some combination of these examples may include an implementation of a network environment.

[0116] Bus 230 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the various bus structures.

[0117] Electronic device 200 can also communicate with one or more external devices 300 (e.g., keyboard, pointing device, Bluetooth device, etc.), and with one or more devices that enable a user to interact with electronic device 200, and / or with any device that enables electronic device 200 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 250. Furthermore, electronic device 200 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 260. Network adapter 260 can communicate with other modules of electronic device 200 via bus 230. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with electronic device 200, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0118] Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. The technical solutions according to the embodiments of this application 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, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, or network device, etc.) to execute the methods described above according to the embodiments of this application.

[0119] Software products may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example,, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: electrical connections with one or more wires, portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0120] Computer-readable storage media may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable storage medium may also be any readable medium other than a readable storage medium that can transmit, propagate, or transfer a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the readable storage medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.

[0121] Program code for performing the operations of this application can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's computing device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0122] Those skilled in the art will understand that the above modules can be distributed in the device as described in the embodiments, or they can be modified accordingly and located in one or more devices that are unique to this embodiment. The modules in the above embodiments can be combined into one module, or they can be further divided into multiple sub-modules.

[0123] Exemplary embodiments of this application have been specifically shown and described above. It should be understood that this application is not limited to the detailed structures, arrangements, or implementation methods described herein; rather, this application is intended to cover various modifications and equivalent arrangements contained within the spirit and scope of the appended claims.

Claims

1. A method for sharding and parallel maintenance based on power common information model, characterized in that, include: The power public information model is divided into multiple segments according to the division of maintenance scope and the hierarchical relationship of the power public information model. Each segment contains the complete hierarchical structure of the power public information model. Based on the partitioned data, an offline maintenance copy corresponding to each partition is generated from the real-time database storing the power public information model. The offline maintenance copy contains data of the model objects in the power public information model. Perform CRUD operations on the offline maintenance replicas corresponding to the shards, and publish the maintained offline maintenance replicas of the shards to the real-time database. The operations of adding, deleting, modifying, and querying the offline maintenance replicas corresponding to the shards, and publishing the maintained offline maintenance replicas to the real-time database, include: Receive CRUD commands for the offline maintenance copy, perform corresponding operations on the offline maintenance copy, and record maintenance logs for each step of the operation. When the maintenance operation only involves model data within a shard, the integrity of the maintenance result is checked. If the check passes, the offline maintenance copy of the shard is published to the real-time database. If the check fails, the error message of the check is returned. When maintenance operations involve other shards, cross-shard cross-maintenance is achieved based on cross-shard conflict negotiation and resolution mechanisms and cross-shard maintenance integrity verification.

2. The method of claim 1, wherein, Also includes: The model objects in the shards are used to generate critical paths according to the hierarchical relationship of the public information model, and the critical path cache is stored along with the shard information to which the model objects belong.

3. The method of claim 1, wherein, When maintenance operations involve other shards, cross-shard cross-maintenance is achieved based on cross-shard conflict negotiation and resolution mechanisms and cross-shard maintenance integrity checks, including: Obtain the maintenance record log; The critical path cache is searched for the shard information involved in the maintenance operation across shards, where the shard information is the shard to which the maintenance object belongs; Based on the maintenance log of this shard, compare whether there is a maintenance conflict. If there is, perform conflict negotiation and resolution. After resolving the conflict, perform cross-shard maintenance integrity verification. If there is no conflict, perform cross-shard maintenance integrity verification directly. After verification, multiple offline maintenance copies are published to the real-time database.

4. The method of claim 3, wherein, When maintenance operations involve other shards, the method of implementing cross-shard cross-maintenance based on cross-shard conflict negotiation and resolution mechanisms and cross-shard maintenance integrity verification also includes: Send a notification message, including the model object and attribute information corresponding to the conflicting maintenance object; Displays multiple maintenance results for the conflicting maintenance objects; In response to confirmation of the adopted maintenance result, the maintenance result is notified to other shards that maintain the conflicting maintenance objects, and the maintenance result is written to the offline maintenance copies corresponding to the multiple shards that participated in the conflict negotiation and resolution.

5. The method of claim 1, wherein, When maintenance operations involve other shards, cross-shard cross-maintenance is achieved based on cross-shard conflict negotiation and resolution mechanisms and cross-shard maintenance integrity checks, including: The integrity of multiple fragments is verified according to the integrity verification rules of the public information model. If the verification passes, the association relationship of the public information model is verified. If the verification fails, a verification error message is returned.

6. The method of claim 5, wherein, When maintenance operations involve other shards, the method of implementing cross-shard cross-maintenance based on cross-shard conflict negotiation and resolution mechanisms and cross-shard maintenance integrity verification also includes: The public information model association verification includes verifying whether objects within a shard and objects maintained across shards have a complete public information model association. If the association is complete, the verification passes; otherwise, an error message is returned.

7. The method of claim 2, wherein, The critical path cache records the full path information of the maintained object. The full path information is a hierarchical string composed of the names of the maintained objects at each level from the root node down to the maintained object according to the power public information model.

8. An apparatus for sharding and parallel maintenance based on an electric power common information model, characterized by, include: The segmentation management module is used to divide the power public information model into multiple segments according to the maintenance scope and hierarchical relationship of the power public information model. Each segment contains the complete hierarchical structure of the power public information model. Based on the segmentation, the real-time database storing the power public information model generates an offline maintenance copy corresponding to the segment. The offline maintenance copy contains the data of the model objects in the power public information model. The intra-shard maintenance and inter-shard coordination module is used to perform CRUD operations on the offline maintenance copies corresponding to the shards and publish the maintained offline maintenance copies of the shards to the real-time database. The intra-chip maintenance and inter-chip coordination module is also used for Receive CRUD commands for the offline maintenance copy, perform corresponding operations on the offline maintenance copy, and record maintenance logs for each step of the operation. When the maintenance operation only involves model data within a shard, the integrity of the maintenance result is checked. If the check passes, the offline maintenance copy of the shard is published to the real-time database. If the check fails, the error message of the check is returned. When maintenance operations involve other shards, cross-shard cross-maintenance is achieved based on cross-shard conflict negotiation and resolution mechanisms and cross-shard maintenance integrity verification.

9. An electronic device, comprising: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the method of any one of claims 1-7.

10. A computer program product comprising computer programs or instructions, characterized in that, When the computer program or instructions are executed by the processor, they implement the method as described in any one of claims 1-7.

Images