A power data management system

Abstract

This invention relates to the field of power supply technology, specifically providing a power data management system, comprising: a first subsystem and a second subsystem. The first subsystem adopts a microservice architecture. The microservice architecture includes: a data persistence service for managing a self-built database that stores power data; an interface management service for data interaction with the second subsystem; and a security service for performing security verification on the data transmitted through the interface. This invention effectively utilizes power data while ensuring its security.

Description

Technical Field

[0001] This invention relates to the field of power supply technology, and more specifically to a power data management system. Background Technology

[0002] Currently, building and applying information systems using power data and external energy data can effectively guide economic operations. However, information application systems deployed on the power side cannot be opened to external access requests, making it impossible to realize the value of power data. This turns power data into "isolated data" and prevents it from truly realizing its social application value. Summary of the Invention

[0003] To address the problem of low application of power data due to the inability to publicly disclose power data and effectively integrate it with external energy data in existing technologies, this invention provides a power data management system to solve the aforementioned technical problems.

[0004] In a first aspect, the present invention provides a power data management method, comprising:

[0005] The first subsystem and the second subsystem, wherein the first subsystem adopts a microservice architecture;

[0006] The microservice architecture includes:

[0007] A data persistence service is provided for managing a self-built database that stores power data.

[0008] Interface management service, used for data interaction with the second subsystem;

[0009] Security services are used to perform security verification on the data transmitted through the interface.

[0010] Furthermore, the security service is also used for:

[0011] The system intercepts requests sent to the second subsystem, writes a randomly generated verification code into the request, sends the request to the interface management service, caches the verification code locally, and clears the verification code after the cache time reaches the set time.

[0012] The system intercepts response data received from the second subsystem by the interface management service and uses firewall functionality to inspect the response data. If no risk is detected in the response data, the system parses the CAPTCHA in the response data and performs a consistency check between the parsed CAPTCHA and the locally cached CAPTCHA. If the check passes, the system sends the response data to the data persistence service. If the check fails, the system destroys the response data, regenerates a CAPTCHA for the request, and sends the request and the new CAPTCHA to the second subsystem.

[0013] Furthermore, the second subsystem includes:

[0014] The business unit is used to retrieve target data from the distributed database according to the request, and encapsulate the target data and the verification code carried in the request into response data;

[0015] The backup unit caches the target data and requests, and clears the target data and requests after the cache time reaches a set time.

[0016] A communication unit is used to send the response data to the interface management service of the first subsystem;

[0017] The request processing unit is used to determine whether there is a cached request that matches the received request. If a cached request exists, the cached target data corresponding to the cached request and the verification code of the received request are encapsulated into response data; if no cached request exists, the business unit is called to process the received request.

[0018] Furthermore, the first subsystem also includes:

[0019] Network management services are used to connect to clients via a local area network;

[0020] The registration management service is used to receive user registration information, generate user information based on the user registration information, and grant permissions to generate user information.

[0021] Furthermore, the network management service includes a security layer, which comprises a firewall and an intrusion prevention system.

[0022] Furthermore, the data persistence service is set up within a service container, which is a container for running microservices and is implemented using an embedded server approach.

[0023] Furthermore, the service container also includes:

[0024] Display services are used to perform browser interface design.

[0025] IOC components are used to manage application dependencies.

[0026] Furthermore, the first subsystem also includes:

[0027] The log service is used to record the running logs of various services and to filter out abnormal logs from all running logs.

[0028] Furthermore, the first subsystem also includes:

[0029] The serialization service supports exposing business logic via REST or RPC, supports customizable serialization mechanisms, supports outputting JSON message format to browsers, and supports outputting high-performance Binary message format to local applications on wireless devices.

[0030] Furthermore, the second subsystem connects to the client via the Internet.

[0031] Secondly, a terminal is provided, including:

[0032] Processor, memory, among which,

[0033] This memory is used to store computer programs.

[0034] The processor is used to retrieve and run the computer program from memory, enabling the terminal to execute the aforementioned system.

[0035] Thirdly, a computer storage medium is provided, wherein instructions are stored therein, which, when executed on a computer, cause the computer to perform the systems described in the preceding aspects.

[0036] The beneficial effects of this invention are that the power data management system provided by this invention constructs two systems, with a non-public system interfacing with a public system. The non-public system can send data to the public system through the interface, while the public system needs to verify the data it sends to the public system. Therefore, the information interaction between the non-public and public systems is proactive, ensuring the data security of the non-public system while also enabling the application of power data in the non-public system. This invention effectively utilizes power data while ensuring its security.

[0037] Furthermore, the design principle of this invention is reliable, the structure is simple, and it has a very wide range of application prospects. Attached Figure Description

[0038] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0039] Figure 1 This is a schematic block diagram of a system according to an embodiment of the present invention. Detailed Implementation

[0040] To enable those skilled in the art to better understand the technical solutions of this invention, the technical solutions of the embodiments of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this invention, and not all embodiments. Based on the embodiments of this invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this invention.

[0041] The key terms used in this invention will be explained below.

[0042] The core idea of ​​microservices is to consider creating applications around business domain components, which can be developed, managed, and accelerated independently. Using microservices cloud architectures and platforms with distributed components simplifies deployment, management, and service delivery.

[0043] DropWizard is a backend service development framework contributed by the Yammer development team. It integrates the best components from various problem domains in the Java ecosystem, helping developers quickly build a RESTful backend service. The DropWizard web service structure consists of: 1. Configuration: Used to set the service configuration, such as the port the service is exposed on, the database configuration, etc. 2. Service: The main entry point of the service, defining which configuration file the service uses, which resources are exposed, and what health checks the service requires, etc. 3. Resource: Defines a resource, including how to obtain the resource and the corresponding business logic when performing Get / Post / Delete / Query operations on the resource. 4. Representation: Defines a service return value object. When the service returns this object, it automatically generates a JSON string based on the object's attribute values ​​and returns it to the service caller. 5. HealthCheck: Used in the OM framework provided by DropWizard for each service, it allows you to check the availability of the current service at any time.

[0044] like Figure 1 As shown, the power data management system provided by this invention adopts the DropWizard framework. Specifically, the system includes:

[0045] The system consists of two subsystems. The first subsystem adopts a microservice architecture. The first subsystem is a non-public system used to process power data within the power grid, while the second subsystem is a public system used to manage external energy data and display power data to the outside world.

[0046] The microservice architecture of the first subsystem includes:

[0047] A data persistence service is provided for managing a self-built database that stores power data.

[0048] Interface management service, used for data interaction with the second subsystem;

[0049] Security services are used to perform security verification on the data transmitted through the interface.

[0050] The data persistence service is set up inside the service container, which is the container for running microservices and is implemented using an embedded server approach.

[0051] The service container also includes: a display service for performing browser interface design; and an IOC component for managing application dependencies.

[0052] To enhance the data security of the first subsystem, security services are also used for:

[0053] The system intercepts requests sent to the second subsystem, writes a randomly generated verification code into the request, sends the request to the interface management service, caches the verification code locally, and clears the verification code after the cache time reaches the set time.

[0054] The system intercepts response data received from the second subsystem by the interface management service and uses firewall functionality to inspect the response data. If no risk is detected in the response data, the system parses the CAPTCHA in the response data and performs a consistency check between the parsed CAPTCHA and the locally cached CAPTCHA. If the check passes, the system sends the response data to the data persistence service. If the check fails, the system destroys the response data, regenerates a CAPTCHA for the request, and sends the request and the new CAPTCHA to the second subsystem.

[0055] Correspondingly, the second subsystem includes:

[0056] The business unit is used to retrieve target data from the distributed database according to the request, and encapsulate the target data and the verification code carried in the request into response data;

[0057] The backup unit caches the target data and requests, and clears the target data and requests after the cache time reaches a set time.

[0058] A communication unit is used to send the response data to the interface management service of the first subsystem;

[0059] The request processing unit is used to determine whether there is a cached request that matches the received request. If a cached request exists, the cached target data corresponding to the cached request and the verification code of the received request are encapsulated into response data; if no cached request exists, the business unit is called to process the received request.

[0060] The data interaction between the first and second subsystems is entirely initiated by the first subsystem. That is, data sent from the first subsystem to the second subsystem does not require review or oversight. The second subsystem only sends response data to the first subsystem when a request is made. This response data undergoes verification through both a firewall and a CAPTCHA. Furthermore, if the second subsystem's response is too slow, causing the CAPTCHA to time out, the CAPTCHA is immediately refreshed, and the request is resent. The second subsystem can then return the previously cached data to the first subsystem.

[0061] In a preferred embodiment of the present invention, the first subsystem further includes:

[0062] A network management service is used to connect to clients via a local area network; the network management service has a security layer, which includes a firewall and an intrusion prevention system.

[0063] The registration management service is used to receive user registration information, generate user information based on the user registration information, and grant permissions to generate user information.

[0064] The log service is used to record important framework layer logs, metrics, and call chain data, record the running logs of each service, and filter all running logs for exceptions.

[0065] The serialization service supports exposing business logic via REST or RPC, supports customizable serialization mechanisms, supports outputting JSON message format to browsers, and supports outputting high-performance Binary message format to local applications on wireless devices.

[0066] The second subsystem, as a public system, connects to clients via the internet and publicly displays data from the distributed database. A distributed database (DDBS) comprises a distributed database management system (DDBMS) and a distributed database (DDB). In a distributed database system, an application can transparently operate on the database. Data is stored in different local databases, managed by different DBMSs, running on different machines, supported by different operating systems, and connected by different communication networks. Besides displaying data to users, the second subsystem also provides data modification operations; however, modification operations require user permission verification, meaning only authorized users can modify the data.

[0067] Although the present invention has been described in detail with reference to the accompanying drawings and preferred embodiments, the invention is not limited thereto. Various equivalent modifications or substitutions can be made to the embodiments of the invention by those skilled in the art without departing from the spirit and essence of the invention, and such modifications or substitutions should all be within the scope of the invention. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the invention should also be covered within the protection scope of the invention. Therefore, the protection scope of the invention should be determined by the scope of the claims.

Claims

1. A power data management system, characterized in that, include: The first subsystem and the second subsystem, wherein the first subsystem adopts a microservice architecture; The microservice architecture includes: A data persistence service is provided for managing a self-built database that stores power data. Interface management service, used for data interaction with the second subsystem; Security services are used to perform security verification on the data transmitted through the interface; The security service is also used for: The system intercepts requests sent to the second subsystem, writes a randomly generated verification code into the request, sends the request to the interface management service, caches the verification code locally, and clears the verification code after the cache time reaches the set time. The system intercepts response data received from the second subsystem by the interface management service and uses firewall functionality to inspect the response data. If no risk is detected in the response data, the system parses the CAPTCHA in the response data and performs a consistency check between the parsed CAPTCHA and the locally cached CAPTCHA. If the check passes, the system sends the response data to the data persistence service. If the check fails, the system destroys the response data, regenerates a CAPTCHA for the request, and sends the request and the new CAPTCHA to the second subsystem. The second subsystem includes: The business unit is used to retrieve target data from the distributed database according to the request, and encapsulate the target data and the verification code carried in the request into response data; The backup unit caches the target data and requests, and clears the target data and requests after the cache time reaches a set time. A communication unit is used to send the response data to the interface management service of the first subsystem; The request processing unit is used to determine whether there is a cached request that matches the received request. If a cached request exists, it encapsulates the cached target data corresponding to the cached request and the verification code of the received request into response data; if no cached request exists, it calls the business unit to process the received request. The first subsystem also includes: Network management services are used to connect to clients via a local area network; The registration management service is used to receive user registration information, generate user information based on the user registration information, and grant permissions to generate user information.

2. The system according to claim 1, characterized in that, The network management service has a security layer, which includes a firewall and an intrusion prevention system.

3. The system according to claim 1, characterized in that, The data persistence service is set up within a service container, which is a container for running microservices and is implemented using an embedded server approach.

4. The system according to claim 3, characterized in that, The service container also includes: Display services are used to perform browser interface design. IOC components are used to manage application dependencies.

5. The system according to claim 1, characterized in that, The first subsystem also includes: The log service is used to record the running logs of various services and to filter out abnormal logs from all running logs.

6. The system according to claim 1, characterized in that, The first subsystem also includes: The serialization service supports exposing business logic via REST or RPC, supports customizable serialization mechanisms, supports outputting JSON message format to browsers, and supports outputting high-performance Binary message format to local applications on wireless devices.

7. The system according to claim 1, characterized in that, The second subsystem connects to the client via the Internet.

Images