Electric power algorithm engine

Abstract

The invention discloses an electric power algorithm engine, which comprises a core algorithm module used for completing loading of an electric power algorithm; the basic data module is used for acquiring basic data required by a power algorithm; the application algorithm module is used for performing power algorithm calculation on the basic data and inputting an obtained result to the application service module; the application service module is used for providing an acquisition demand for the application algorithm module and obtaining a result corresponding to the demand fed back by the application algorithm module; the application algorithm module is communicated with the core algorithm module through a standardized interface, and the core algorithm module is communicated with the basic data module through a standardized interface. The modular design of the system is realized by dividing the core algorithm module, the basic data module, the application algorithm module and the application service module. When the algorithm solution needs to be replaced, only the corresponding core algorithm module or application algorithm module needs to be replaced or updated, and the whole system does not need to be comprehensively reconstructed.

Description

Technical Field

[0001] The present invention relates to the field of electric power automation technology, and in particular to an electric power algorithm engine. Background Art

[0002] If existing power companies have application scenarios that require the use of grid algorithms, they need to ask one or more suppliers to develop them. However, within the existing technical architecture framework, switching to algorithm solutions from other suppliers is often accompanied by a comprehensive reconstruction of existing service programs. This process is not only time-consuming and labor-intensive, but also easily leads to redundant investment in the development of existing functions and interfaces, as well as cumbersome model docking definition work, which seriously restricts the flexibility and efficiency of technology iteration; at the same time, in the environment of cross-vendor algorithm integration, the flow and storage of basic data inevitably cross different application boundaries. If the traditional manual management model is adopted, the risk of data leakage will increase significantly, posing a severe challenge to the protection of sensitive information; under more traditional data management systems, data islands are common, and different types of data are separated and stored in multiple systems. The data access process is lengthy and complicated, involving multiple links such as permission verification, cross-system query, and data encapsulation. When data flows between multiple services, it needs to go through repeated packaging, transmission, parsing, and reprocessing processes, which greatly slows down the overall efficiency of data transmission and processing. Summary of the invention

[0003] The purpose of the present invention is to overcome the shortcomings of the prior art in application scenarios where power grid algorithms need to be used, such as rigid iteration of power algorithms, increased information security risks, and bottlenecks in data transmission efficiency, and to provide a power algorithm engine.

[0004] The purpose of the present invention is achieved through the following technical solutions: An electric power algorithm engine, comprising: The core algorithm module is used to complete the loading of the power algorithm; Basic data module, used to obtain basic data required for power algorithms; The application algorithm module is used to perform power algorithm calculations on basic data, and the results are input into the application service module; The application service module is used to make acquisition requirements to the application algorithm module and obtain the results corresponding to the requirements fed back by the application algorithm module; The application algorithm module and the core algorithm module communicate using standardized interfaces, and the core algorithm module and the basic data module communicate using standardized interfaces.

[0005] This solution realizes the modular design of the system by dividing the core algorithm module, basic data module, application algorithm module and application service module. When the algorithm solution needs to be replaced, it is only necessary to replace or update the corresponding core algorithm module or application algorithm module without the need to completely reconstruct the entire system. The basic data required for the power algorithm is centrally managed through the basic data module, which reduces the flow and storage of data between different application boundaries, thereby reducing the risk of data leakage. Through modular design and standardized interface communication, the packaging, transmission, parsing and reprocessing processes that need to be experienced when data flows between multiple services are reduced, making data transmission more direct and efficient.

[0006] Preferably, the power algorithm engine also includes an application data persistence module, which is in communication with the application algorithm module and is used to monitor and record the operating status of the application algorithm module, and also to record the format and rules of the application algorithm module during operation.

[0007] Preferably, the application algorithm module includes a basic application algorithm module and a basic data acquisition algorithm module. The basic application algorithm module is used to calculate the basic data according to the power algorithm and input the results to the application service module. The basic data acquisition algorithm module is used to obtain the basic data required for the power algorithm according to user input parameters and feed the basic data back to the application service module.

[0008] Preferably, the core algorithm module further includes an algorithm registration and management module, which performs the following steps when running: Upload the algorithm jar package to the specified directory; Verify whether the algorithm jar package implements a unified interface and whether the interface is normal; Build a registry to record relevant information of the algorithm jar package; Load the algorithm jar package.

[0009] Preferably, the algorithm registration and management module also performs uninstallation and update steps on the algorithm jar package, uninstalls the specified algorithm jar package, and deletes registry related information; when the algorithm jar package changes, re-registers the algorithm and updates the registry information.

[0010] Preferably, the basic data module includes measurement basic data, topology basic data and asset basic data.

[0011] Preferably, the technical architecture adopted by the application algorithm module when performing power algorithm calculation on basic data includes basic analysis services, algorithm node clusters, zookeeper clusters and message queues; Zookeeper is used to coordinate information between basic analysis services and algorithm nodes. Basic analysis services are used to receive various computing and analysis requests and execute scheduled tasks and batch tasks. Algorithm nodes perform the steps of node information registration, algorithm execution, result preservation, and log archiving. At the same time, they record the running time of each step of the power algorithm. The message queue is used to save task information.

[0012] Preferably, when executing scheduled tasks and batch tasks, the basic analysis service decomposes the tasks and sends them to a message queue.

[0013] Preferably, the node information registration is used to register the node address and algorithm information on each node to the instantaneous node of Zookeeper, and the basic analysis service synchronously obtains the node address and algorithm information on each node.

[0014] The beneficial effects of the present invention are as follows: the present invention realizes the modular design of the system by dividing the core algorithm module, the basic data module, the application algorithm module and the application service module. When the algorithm solution needs to be replaced, it is only necessary to replace or update the corresponding core algorithm module or application algorithm module without the need to completely reconstruct the entire system. The basic data required for the power algorithm is centrally managed by the basic data module, which reduces the flow and storage of data between different application boundaries, thereby reducing the risk of data leakage. Through modular design and standardized interface communication, the packaging, transmission, parsing and reprocessing processes that need to be experienced when data flows between multiple services are reduced, making data transmission more direct and efficient. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 It is a structural schematic diagram of the present invention; Figure 2 It is a schematic diagram of the algorithm registration of the present invention; Figure 3 It is a technical architecture diagram of the present invention. DETAILED DESCRIPTION

[0016] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this application will be more comprehensive and complete and fully convey the concept of the example embodiments to those skilled in the art.

[0017] In addition, described feature, structure or characteristic can be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present application. However, those skilled in the art will appreciate that the technical scheme of the present application can be put into practice without one or more of the specific details, or other methods, components, devices, steps, etc. can be adopted. In other cases, known methods, devices, realizations or operations are not shown or described in detail to avoid blurring the various aspects of the application.

[0018] 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 may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0019] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.

[0020] Example: A power algorithm engine, taking the power flow algorithm as an example, Figure 1 As shown, including: The core algorithm module is used to complete the loading of the power algorithm; Basic data module, used to obtain basic data required for power algorithms; The application algorithm module is used to perform power algorithm calculations on basic data, and the results are input into the application service module; The application service module is used to make acquisition requirements to the application algorithm module and obtain the results corresponding to the requirements fed back by the application algorithm module; The application algorithm module and the core algorithm module communicate using standardized interfaces, and the core algorithm module and the basic data module communicate using standardized interfaces.

[0021] In this embodiment, the core algorithm module and the basic data module are based on the power algorithm engine platform, and the application service module and the core algorithm module are the superstructure. The platform foundation and the platform superstructure cooperate with each other to efficiently complete the algorithm calculation.

[0022] The application service module and the application algorithm module can be expanded according to different user needs, so that the platform can meet user needs to the greatest extent. The core algorithm module and the basic data module are mainly responsible for algorithm management and algorithm data preparation. This solution realizes the modular design of the system by dividing the core algorithm module, the basic data module, the application algorithm module and the application service module. When the algorithm solution needs to be replaced, it is only necessary to replace or update the corresponding core algorithm module or application algorithm module without the need to completely reconstruct the entire system. The basic data required for the power algorithm is centrally managed through the basic data module, which reduces the flow and storage of data between different application boundaries, thereby reducing the risk of data leakage. Through modular design and standardized interface communication, the packaging, transmission, parsing, and reprocessing processes that need to be experienced when data flows between multiple services are reduced, making data transmission more direct and efficient.

[0023] The power algorithm engine also includes an application data persistence module, which is connected to the application algorithm module in communication, and is used to monitor and record the running status of the application algorithm module, and record the format and rules of the application algorithm module during operation. Specifically, it includes an algorithm log persistence module: in this module, the running status of each module will be monitored in a variety of ways, and the running status of the calculation flow will be evaluated from multiple dimensions. For example: algorithm calculation time efficiency, number of algorithm calls, etc. This log module will use aop as the basis to minimize the coupling between the algorithm and the log. And the log will be reasonably persisted. Algorithm data persistence module: the flow algorithm will be persisted, especially the flow of scheduled task calculation will be processed, including persistent storage format, persistence rules, etc.

[0024] The application service module provides services to users directly or indirectly, mainly including the following functions: Single feeder calculation service: Users input a single feeder, and the system will calculate the power flow in real time and return the result to the user. This service is a synchronous calculation service. This service will support all data users to input custom data. For example, users can process and modify topological data and then input it into the analysis service. The system will use the user's topological data to analyze the power flow.

[0025] Batch calculation service: Users can input the city bureau and county bureau, and the system will analyze all the feeders under the city bureau and county bureau, and send these feeders into the platform for batch calculation. Since the amount of flow data calculated by the city bureau and county bureau is huge and the waiting time is long, this service exists in an asynchronous way, and the system background will directly store the calculation results.

[0026] Similarly, for scheduled task calculation, the operation and maintenance personnel can write the city bureau and county bureau that need to be calculated regularly into the configuration file. The system will regularly decompose and calculate all the feeders under the county bureau and city bureau, and directly store the results in the database.

[0027] Basic data acquisition service: Users can flexibly obtain the topological data, measurement data, and asset data required for power flow calculation by entering relevant parameters.

[0028] The application algorithm module includes a basic application algorithm module and a basic data acquisition algorithm module. The basic application algorithm module is used to calculate the basic data according to the power algorithm and input the obtained results to the application service module. The basic data acquisition algorithm module is used to obtain the basic data required for the power algorithm according to the user input parameters and feed the basic data back to the application service module. In this embodiment, the basic application algorithm module will obtain measurement, topology, and asset data according to the user input parameters. The acquisition of measurement and asset data will be based on the acquisition of topology data.

[0029] The basic application algorithm module runs in two stages: In the basic data acquisition stage, the topology data will be first obtained based on the feeder, and the asset data and measurement data of related data will be obtained based on the topology data.

[0030] The core power flow algorithm calculation stage, in this stage the system will calculate the power flow according to the algorithm selected by the user. The input parameters of the core power flow algorithm are the topology data, asset data, and measurement data of stage 1.

[0031] In addition, a custom application algorithm can also be generated. The custom application algorithm will be based on the specific parameters input by the user. If the user inputs topology data, the data acquisition stage from the system will be omitted in the data acquisition stage of the basic application algorithm, and the user-input data will be directly used for power flow calculation and analysis.

[0032] The basic data module includes measurement basic data, topology basic data and asset basic data. The system will obtain the topology data of the feeder from the topology center according to the feeder ID. Asset and measurement data acquisition will obtain resource measurement data from the measurement and asset center according to the topology data, and a completion algorithm will be used in the middle to perform the completion operation.

[0033] The core power flow algorithm module also includes an algorithm registration and management module, which performs the following steps at runtime: Figure 2 As shown: Upload the algorithm jar package to the specified directory; Verify whether the algorithm jar package implements a unified interface and whether the interface is normal; Build a registry to record relevant information of the algorithm jar package, including: algorithm name, implementation manufacturer, version number, algorithm registration time, etc.

[0034] Load the algorithm jar package. Load the jar packages implemented by different manufacturers into the system memory, and support different versions of jars from the same manufacturer to coexist in the platform.

[0035] The algorithm registration and management module also performs uninstall and update steps for the algorithm jar package, uninstalls the specified algorithm jar package, and deletes the registry related information; when the algorithm jar package changes, re-registers the algorithm and updates the registry information.

[0036] The technical architecture adopted by the application algorithm module when performing power algorithm calculation on basic data is as follows: Figure 3 As shown, it includes basic analysis services, algorithm node clusters, zookeeper clusters, and message queues; Zookeeper is used to coordinate information between basic analysis services and algorithm nodes. Basic analysis services are used to receive various computing and analysis requests and execute scheduled tasks and batch tasks. Algorithm nodes perform the steps of node information registration, algorithm execution, result preservation, and log archiving. At the same time, they record the running time of each step of the power algorithm. The message queue is used to save task information.

[0037] When executing scheduled tasks and batch tasks, the basic analysis service decomposes the tasks and sends them to the message queue.

[0038] The node information registration is used to register the node address and algorithm information on each node to the instantaneous node of Zookeeper, and the basic analysis service synchronously obtains the node address and algorithm information on each node.

[0039] In summary, the solution of this embodiment has the following advantages: 1. Interface standardization definition: Build a standardized framework for the flow calculation application algorithm interface and the basic data acquisition algorithm interface to lay a solid foundation for technology integration.

[0040] 2. Algorithm registration and dynamic integration: Manufacturers submit application algorithms for registration, and the intelligent engine instantly generates algorithm nodes and efficiently loads them into the memory pool to achieve rapid integration and dynamic management of algorithms.

[0041] 3. Seamless access to user data: User basic data is seamlessly accessed to the algorithm engine through a secure channel, ensuring the smooth start of the data processing process.

[0042] 4. Advanced application process of the power flow calculation function: When the power flow calculation function is activated, external requests must first undergo a sophisticated permission verification process to ensure the legitimacy and security of the request before being forwarded to the algorithm engine platform to begin executing data processing and analysis functions.

[0043] 5. Intelligent algorithm matching and resource evaluation: According to the request content, the optimal basic data acquisition algorithm, core power flow algorithm and power flow calculation application algorithm combination are intelligently selected. At the same time, resource consumption estimation and decomposability analysis are performed on the task to provide a basis for task optimization.

[0044] 6. Intelligent task scheduling and decomposition: Automatically determine the task decomposition strategy based on the real-time status of the server node and the task resource requirements. When necessary, use advanced task decomposition algorithms to coordinate cross-node processing to maximize resource utilization.

[0045] 7. Verification before algorithm execution: Strictly confirm the algorithm logic before execution and implement multi-module health checks to ensure that each module is in the best operating state.

[0046] 8. Detailed monitoring of the execution process: During the execution process, the format and content compliance of input and output parameters are automatically verified, and key indicators such as the call time and resource consumption of each module are monitored and recorded in real time to provide data support for performance optimization and algorithm comparison.

[0047] 9. Result summary and verification feedback: After the algorithm is executed, the results are immediately summarized and strictly verified to ensure that the data is accurate, and then fed back to the external system through efficient channels to support upper-level applications.

[0048] At the same time, the solution of this embodiment also has the following beneficial effects: visual comparison of algorithm performance. The platform provides an intuitive algorithm performance comparison function, which helps users accurately evaluate algorithm performance and optimize the decision-making process through visual chart display.

[0049] Algorithm lifecycle management implements strict algorithm registration and retirement mechanisms, while supporting the rapid iteration and deployment of new algorithms to maintain the advancement and flexibility of the technology system.

[0050] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the embodiments disclosed herein. The present application is intended to cover any variations, uses or adaptations of the present application, which follow the general principles of the present application and include common knowledge or customary technical means in the art that are not disclosed in the present application.

[0051] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A power algorithm engine, characterized in that: include: The core algorithm module is used to complete the loading of the power algorithm; Basic data module, used to obtain basic data required for power algorithms; The application algorithm module is used to perform power algorithm calculations on basic data, and the results are input into the application service module; The application service module is used to make acquisition requirements to the application algorithm module and obtain the results corresponding to the requirements fed back by the application algorithm module; The application algorithm module and the core algorithm module communicate using standardized interfaces, and the core algorithm module and the basic data module communicate using standardized interfaces.

2. The power algorithm engine according to claim 1, characterized in that: It also includes an application data persistence module, which is in communication connection with the application algorithm module and is used to monitor and record the running status of the application algorithm module, and also to record the format and rules of the application algorithm module during operation.

3. The power algorithm engine according to claim 1, characterized in that: The application algorithm module includes a basic application algorithm module and a basic data acquisition algorithm module. The basic application algorithm module is used to calculate the basic data according to the power algorithm and input the results to the application service module. The basic data acquisition algorithm module is used to obtain the basic data required for the power algorithm according to user input and feed the basic data back to the application service module.

4. The power algorithm engine according to claim 1, characterized in that: The core algorithm module also includes an algorithm registration and management module, which performs the following steps when running: Upload the algorithm jar package to the specified directory; Verify whether the algorithm jar package implements a unified interface and whether the interface is normal; Build a registry to record relevant information of the algorithm jar package; Load the algorithm jar package.

5. The power algorithm engine according to claim 4, characterized in that: The algorithm registration and management module also performs uninstallation and update steps on the algorithm jar package, uninstalls the specified algorithm jar package, and deletes the registry related information; When the algorithm jar package changes, re-register the algorithm and update the registry information.

6. The power algorithm engine according to claim 1, characterized in that: The basic data module includes measurement basic data, topology basic data and asset basic data.

7. The power algorithm engine according to claim 1, characterized in that: The technical architecture adopted by the application algorithm module when performing power algorithm calculation on basic data includes basic analysis services, algorithm node clusters, zookeeper clusters and message queues; Zookeeper is used to coordinate information between basic analysis services and algorithm nodes. Basic analysis services are used to receive various computing and analysis requests and execute scheduled tasks and batch tasks. Algorithm nodes perform the steps of node information registration, algorithm execution, result preservation, and log archiving. At the same time, they record the running time of each step of the power algorithm. The message queue is used to save task information.

8. The power algorithm engine according to claim 7, characterized in that: When executing scheduled tasks and batch tasks, the basic analysis service decomposes the tasks and sends them to the message queue.

9. The power algorithm engine according to claim 7, characterized in that: The node information registration is used to register the node address and algorithm information on each node to the instantaneous node of Zookeeper, and the basic analysis service synchronously obtains the node address and algorithm information on each node.

Images