Electric power open platform system based on digitization capability

Abstract

The invention relates to an electric power open platform system based on digitization capability. The system comprises an achievement acquisition layer, a local service layer and a two-stage sharing layer. The achievement collection layer is responsible for collecting and integrating digital achievements of a data medium station, a technology medium station, a business medium station, an Internet of Things platform, a cloud platform and a business system of the electric power company; the local service layer manages the data and capability obtained from the achievement acquisition layer in a centralized manner, and provides customized services for the requirements of local electric power companies; a Spring Boot micro-service framework is used to realize decoupling and independent deployment of services, and Kubernetes is used to carry out container arrangement, management service expansion, load balancing and automatic recovery; the two-level sharing layer realizes sharing of achievements between a local electric power formula and a head office. According to the invention, the security can be guaranteed, the performance can be improved, and a flexible and extensible service and achievement sharing mechanism can be provided at the same time.

Description

Technical Field

[0001] The present invention relates to the field of data management, and in particular to an electric power open platform system based on digital capabilities. Background Art

[0002] In the current wave of digital transformation, enterprises and organizations in various industries are actively exploring how to closely integrate digital technology with their own business to improve operational efficiency, optimize user experience and stimulate new business growth points. As one of the traditional energy industries, the digital transformation of the power industry is particularly important and urgent. By integrating advanced information technology, data analysis and intelligent management methods, power companies can better realize the intelligent and refined management of power production, transmission and distribution, consumption and operation and maintenance.

[0003] With the rapid development of technologies such as the Internet of Things, big data, cloud computing and artificial intelligence, the power industry is facing a profound technological change. These technologies provide power systems with more powerful data collection, management and analysis capabilities. Traditional isolated systems are gradually being replaced by integrated data platforms that can connect various business departments and data assets of the enterprise to work together. Summary of the invention

[0004] In order to solve the above problems, the purpose of the present invention is to provide an open power platform system based on digital capabilities, which can provide flexible and scalable services and results sharing mechanisms while ensuring safety and improving performance.

[0005] To achieve the above object, the present invention adopts the following technical solutions:

[0006] An open power platform system based on digital capabilities, with a results collection layer, a local service layer and a two-level sharing layer;

[0007] The achievement collection layer is responsible for collecting and integrating the digital achievements of the power company's data center, technology center, business center, IoT platform, cloud platform and business system;

[0008] The local service layer centrally manages the data and capabilities obtained from the results collection layer and provides customized services for the needs of local power companies. It uses the Spring Boot microservice framework to achieve service decoupling and independent deployment, and uses Kubernetes for container orchestration to manage service expansion, load balancing, and automatic recovery.

[0009] The two-level sharing layer enables the sharing of results between local power formulae and the head office, supports cross-regional coordination and cooperation, manages the aggregated results through results management, and opens relevant results and capabilities to various units in need through the capability opening module.

[0010] Furthermore, the collection layer enables Apache Nifi to automatically extract, transform and load data into the central data warehouse; and through the data proxy component, it accesses the data of each platform in a non-invasive manner to ensure system stability; formulates data format standards and ensures the consistency of data formats through data conversion tools; uses the Hadoop ecosystem to provide storage solutions for unstructured data, and uses relational databases (to store structured data; builds a data lake to store and analyze all types of data, including structured, semi-structured and unstructured data.

[0011] Furthermore, the functions of the local service layer are modularized according to business needs, including customer management services, billing services, equipment monitoring services, and data analysis services; an event-driven architecture is used to handle asynchronous requests and high-concurrency scenarios, and the message queue RabbitMQ is used to implement event communication; and an independent RESTful API is designed for each service module to ensure that the interface is simple, easy to use, and clearly documented; OpenAPI / Swagger is used to generate and maintain documentation for the API.

[0012] Furthermore, the Spring Boot microservice framework is used to achieve decoupling and independent deployment of services, as follows:

[0013] Use Spring Boot for microservice development, integrate Spring Data JPA or MyBatis for data persistence, and use Spring Security to implement security policies;

[0014] Write Dockerfile for each Spring Boot microservice, define service packaging, dependency installation, configuration injection, and service startup commands; customize Docker Compose files to manage local development and test environments;

[0015] Set up continuous integration and deployment pipelines using Jenkins or GitLab CI / CD to automate building, testing, and publishing Docker images.

[0016] Furthermore, Kubernetes is used for container orchestration to manage service expansion, load balancing, and automatic recovery, as follows:

[0017] Create a Kubernetes Deployment definition, specifying the number of replicas, container images, and update strategies for each microservice module;

[0018] Use Kubernetes ConfigMap and Secret to manage application configuration and secret data;

[0019] Use Kubernetes Service Object to implement service discovery and load balancing;

[0020] Use Ingress Controller and Ingress resources to configure external access routes and enable HTTPS and reverse proxy functions;

[0021] Configure Horizontal Pod Autoscaler to automatically scale based on resource usage or custom metrics;

[0022] Use Liveness Probe and Readiness Probe to set up health checks to ensure that the container is in normal working condition and support automatic restart mechanism.

[0023] Furthermore, the two-level sharing layer adopts a hybrid cloud architecture, combining the local end of local power companies with the cloud resources of the head office, using VPN or SD-WAN technology to ensure the security and stability of cross-regional communications; using distributed system coordination tools to achieve service registration, configuration distribution and status synchronization; and building a cross-regional data sharing platform, using data virtualization technology to provide a unified data access layer, and using data exchange protocols to achieve real-time data synchronization and transmission.

[0024] Furthermore, the head office implements a data governance framework to ensure quality and consistency in the data sharing process; uses metadata management tools to track and manage the directory and lineage of shared data; implements a results lifecycle management strategy covering the creation, review, release, archiving and abandonment of results; uses a version control system to manage various versions of results and supports version backtracking; uses an elastic storage system to store results, and accelerates cross-regional access through CDN, providing RESTful API and GraphQL interfaces for local power companies to find and use results.

[0025] The present invention has the following beneficial effects:

[0026] 1. The present invention can provide a flexible and scalable service and achievement sharing mechanism while ensuring security and improving performance;

[0027] 2. The present invention uses a combination of Spring Boot, Docker, and Kubernetes to effectively realize the flexible, stable, and efficient deployment and management of microservices, provide reliable digital platform support for power companies, and ensure the compatibility of development and production environments, high availability of services, and simplicity of expansion and maintenance;

[0028] 3. Through the two-level sharing layer, this system can efficiently realize the sharing of results and cross-regional collaboration between local power companies and the head office, and open up capabilities to demand units in a safe and reliable manner. It not only supports the digital transformation of the power industry, but also promotes the maximum utilization of internal resources and strategic cooperation. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 This is a system architecture diagram of the present invention;

[0030] Figure 2 This is a diagram of the local service layer architecture in one embodiment of the present invention;

[0031] Figure 3 Schematic diagram of two-level sharing in one embodiment of the present invention. DETAILED DESCRIPTION

[0032] The present invention is further described in detail below with reference to the accompanying drawings and specific embodiments:

[0033] refer to Figure 1 ,In this embodiment, a power open platform system based on digital capabilities is provided, which is characterized by an achievement collection layer, a local service layer and a two-level sharing layer;

[0034] The achievement collection layer is responsible for collecting and integrating the digital achievements of the power company's data center, technology center, business center, IoT platform, cloud platform and business system;

[0035] The local service layer centrally manages the data and capabilities obtained from the results collection layer and provides customized services for the needs of local power companies. It uses the Spring Boot microservice framework to achieve service decoupling and independent deployment, and uses Kubernetes for container orchestration to manage service expansion, load balancing, and automatic recovery.

[0036] The two-level sharing layer enables the sharing of results between local power formulae and the head office, supports cross-regional coordination and cooperation, manages the aggregated results through results management, and opens relevant results and capabilities to various units in need through the capability opening module.

[0037] In this embodiment, the results collection layer enables Apache Nifi to automatically extract, convert and load data into the central data warehouse; and through the data proxy component, it accesses the data of each platform in a non-invasive manner to ensure system stability; formulates data format standards and ensures the consistency of data formats through data conversion tools; uses the Hadoop ecosystem (such as HDFS, Hive) to provide storage solutions for unstructured data, and uses relational databases (such as MySQL, PostgreSQL) to store structured data; builds a data lake for storing and analyzing all types of data, including structured, semi-structured and unstructured data.

[0038] refer to Figure 2 In this embodiment, the functions of the local service layer are modularized according to business needs, including customer management services, billing services, equipment monitoring services, and data analysis services; an event-driven architecture is used to handle asynchronous requests and high-concurrency scenarios, and the message queue RabbitMQ is used to implement event communication; and an independent RESTful API is designed for each service module to ensure that the interface is simple, easy to use, and clearly documented; OpenAPI / Swagger is used to generate and maintain documentation for the API.

[0039] In this embodiment, the Spring Boot microservice framework is used to achieve decoupling and independent deployment of services, as follows:

[0040] Use Spring Boot for microservice development, integrate Spring Data JPA or MyBatis for data persistence, and use Spring Security to implement security policies;

[0041] Write Dockerfile for each Spring Boot microservice, define service packaging, dependency installation, configuration injection, and service startup commands; customize Docker Compose files to manage local development and test environments;

[0042] Set up continuous integration and deployment pipelines using Jenkins or GitLab CI / CD to automate building, testing, and publishing Docker images.

[0043] In this embodiment, Kubernetes is used for container orchestration and management of service expansion, load balancing, and automatic recovery, as follows:

[0044] Create a Kubernetes Deployment definition, specifying the number of replicas, container images, and update strategies for each microservice module;

[0045] Use Kubernetes ConfigMap and Secret to manage application configuration and secret data;

[0046] Use Kubernetes Service Object to implement service discovery and load balancing;

[0047] Use Ingress Controller and Ingress resources to configure external access routes and enable HTTPS and reverse proxy functions;

[0048] Configure Horizontal Pod Autoscaler to automatically scale based on resource usage or custom metrics;

[0049] Use Liveness Probe and Readiness Probe to set up health checks to ensure that the container is in normal working condition and support automatic restart mechanism.

[0050] refer to Figure 3 In this embodiment, the two-level sharing layer adopts a hybrid cloud architecture, combining the local end of local power companies with the cloud resources of the head office to improve scalability and coordination efficiency. Use VPN or SD-WAN technology to ensure the security and stability of cross-regional communications; use distributed system coordination tools (such as Zookeeper or etcd) to achieve service registration, configuration distribution and state synchronization; and build a cross-regional data sharing platform, use data virtualization technology (such as Denodo) to provide a unified data access layer, and use data exchange protocols (such as EDI or Apache Kafka) to achieve real-time data synchronization and transmission.

[0051] In this embodiment, the head office implements a data governance framework to ensure the quality and consistency of data sharing; uses metadata management tools (such as Apache Atlas) to track and manage the directory and lineage of shared data; implements a results lifecycle management strategy, covering the creation, review, release, archiving and abandonment of results; uses a version control system (such as Git) to manage various versions of results and supports version backtracking; uses an elastic storage system (such as Amazon S3) to store results, and accelerates cross-regional access through CDN, providing RESTful API and GraphQL interfaces for local power companies to find and use results

[0052] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0053] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0054] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0055] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0056] The above is only a preferred embodiment of the present invention, and does not limit the present invention in other forms. Any technician familiar with the profession may use the above disclosed technical content to change or modify it into an equivalent embodiment with equivalent changes. However, any simple modification, equivalent change and modification made to the above embodiment according to the technical essence of the present invention without departing from the technical solution of the present invention still belongs to the protection scope of the technical solution of the present invention.

Claims

1. A power open platform system based on digital capabilities, characterized in that: Results collection layer, local service layer and two-level sharing layer; The achievement collection layer is responsible for collecting and integrating the digital achievements of the power company's data center, technology center, business center, IoT platform, cloud platform and business system; The local service layer centrally manages the data and capabilities obtained from the results collection layer and provides customized services for the needs of local power companies; Use the Spring Boot microservice framework to achieve service decoupling and independent deployment, and use Kubernetes for container orchestration to manage service expansion, load balancing, and automatic recovery; The two-level sharing layer enables the sharing of results between local power formulae and the head office, supports cross-regional coordination and cooperation, manages the aggregated results through results management, and opens relevant results and capabilities to various units in need through the capability opening module.

2. The electric power open platform system based on digital capability according to claim 1, characterized in that: The results collection layer enables Apache Nifi to automatically extract, convert and load data into the central data warehouse; and through the data proxy component, it accesses the data of each platform in a non-invasive manner to ensure system stability; formulates data format standards and ensures the consistency of data formats through data conversion tools; Use the Hadoop ecosystem to provide storage solutions for unstructured data, use relational databases to store structured data; build a data lake to store and analyze all types of data, including structured, semi-structured, and unstructured data.

3. The electric power open platform system based on digital capability according to claim 1 is characterized in that: The functions of the local service layer are modularized according to business needs, including customer management services, billing services, equipment monitoring services, and data analysis services. An event-driven architecture is used to handle asynchronous requests and high-concurrency scenarios, and the message queue RabbitMQ is used to implement event communication. An independent RESTful API is designed for each service module to ensure that the interface is simple, easy to use, and clearly documented. OpenAPI / Swagger is used to generate and maintain documentation for the API.

4. The electric power open platform system based on digital capability according to claim 1, characterized in that: The Spring Boot microservice framework is used to achieve decoupling and independent deployment of services, as follows: Use Spring Boot for microservice development, integrate Spring Data JPA or MyBatis for data persistence, and use Spring Security to implement security policies; Write a Dockerfile for each Spring Boot microservice, defining service packaging, dependency installation, configuration injection, and service startup commands; Customized Docker Compose files to manage local development and testing environments; Set up continuous integration and deployment pipelines using Jenkins or GitLab CI / CD to automate building, testing, and publishing Docker images.

5. The electric power open platform system based on digital capability according to claim 1, characterized in that: The use of Kubernetes for container orchestration, management of service expansion, load balancing, and automatic recovery is as follows: Create a Kubernetes Deployment definition, specifying the number of replicas, container images, and update strategies for each microservice module; Use Kubernetes ConfigMap and Secret to manage application configuration and secret data; Use Kubernetes Service Object to implement service discovery and load balancing; Use Ingress Controller and Ingress resources to configure external access routes and enable HTTPS and reverse proxy functions; Configure Horizontal Pod Autoscaler to automatically scale based on resource usage or custom metrics; Use Liveness Probe and Readiness Probe to set up health checks to ensure that the container is in normal working condition and support automatic restart mechanism.

6. The electric power open platform system based on digital capability according to claim 1, characterized in that: The two-level sharing layer adopts a hybrid cloud architecture, combining the local end of local power companies with the cloud resources of the head office, and using VPN or SD-WAN technology to ensure the security and stability of cross-regional communications; using distributed system coordination tools to achieve service registration, configuration distribution and status synchronization; and building a cross-regional data sharing platform, using data virtualization technology to provide a unified data access layer, and using data exchange protocols to achieve real-time data synchronization and transmission.

7. The electric power open platform system based on digital capability according to claim 6, characterized in that: The head office implements a data governance framework to ensure quality and consistency in the data sharing process; Use metadata management tools to track and manage the catalog and lineage of shared data; implement a results lifecycle management strategy covering the creation, review, publication, archiving, and disposal of results; Use a version control system to manage various versions of the results and support version backtracking; use an elastic storage system to store the results, and accelerate cross-regional access through CDN, providing RESTful API and GraphQL interfaces for local power companies to search and use the results.

Images