Interface design method of virtual power plant dynamic performance analysis and evaluation system

Abstract

The invention relates to an interface design method for a dynamic performance analysis and evaluation system of a virtual power plant. The interface design method comprises the following steps: dividing the dynamic performance analysis and evaluation system of the virtual power plant into a sensing layer, a communication layer, a data access layer, a data layer, a service layer, an application layer and a display layer according to functions; different interfaces are designed for each level, including a standardized data acquisition protocol and a high-frequency data transmission mechanism of a sensing layer, a multi-protocol compatibility and protocol conversion design of a communication layer, a unified data format and efficient data transmission of a data access layer, and a database interface and file storage interface design of a data layer. The authentication service, authority management and data access service of the service layer, the modular interface design and real-time data interaction of the application layer, and the cross-browser compatible design and data visualization function of the display layer. By optimizing the design of the system interface, efficient, safe and stable data processing and communication are realized, and the real-time performance, compatibility and user experience of the system are improved.

Description

Technical Field

[0001] The present invention relates to the technical field of virtual power plants, and in particular to an interface design method for a dynamic performance analysis and evaluation system of a virtual power plant. Background Art

[0002] In recent years, with the increasing complexity of power systems and the increase in the proportion of renewable energy, virtual power plants (VPPs) have received widespread attention and application as an emerging power system management model. Virtual power plants integrate a variety of distributed energy resources (such as wind power generation, photovoltaic power generation, energy storage systems, etc.) and load control, optimize scheduling and energy management, thereby achieving efficient control of power systems and optimal resource utilization. This model not only helps to improve the flexibility and reliability of power systems, but also supports better integration of renewable energy and promotes the development of green electricity.

[0003] Interface design plays a vital role in the dynamic performance analysis and evaluation system of virtual power plants. The existing solutions have the following problems:

[0004] (1) The problem of inconsistent data formats and protocols leads to poor compatibility between different systems. For example, when different systems use different data formats and protocols, complex conversion and adaptation are required, which increases the difficulty of system integration and development costs. In addition, the lack of standardized protocols may lead to unstable data exchange between systems and affect the reliability of data transmission.

[0005] (2) Data security issues involved in the data transmission process. Existing interface design solutions have deficiencies in data security. For example, some interfaces may lack effective data encryption measures, making data vulnerable to attacks during transmission. In addition, the identity authentication and permission control mechanisms are not perfect, which may lead to data leakage or unauthorized access, affecting the security of the system.

[0006] (3) There are limitations in compatibility and scalability. For example, the interface may not take into account future technology upgrades and functional expansion requirements, resulting in the system being unable to upgrade or expand smoothly when faced with new requirements. In addition, the design of the interface may not fully consider compatibility with other systems, resulting in problems with the integration of different systems.

[0007] (4) There are problems with slow data transmission speed and long response time. When faced with large-scale data streams or high-frequency requests, the performance of the interface may not meet the requirements, resulting in data transmission delays and low system efficiency. This problem affects the real-time performance and user experience of the system, especially in application scenarios that require fast response. Summary of the invention

[0008] The technical problem to be solved by the present invention is to provide an interface design method for a virtual power plant dynamic performance analysis and evaluation system, which can solve the problems existing in the interface design of the existing virtual power plant dynamic performance analysis and evaluation system and improve the real-time performance, compatibility and user experience of the system.

[0009] The technical solution adopted by the present invention to solve the technical problem is: to provide an interface design method for a virtual power plant dynamic performance analysis and evaluation system, comprising the following steps:

[0010] The dynamic performance analysis and evaluation system of virtual power plant is divided into perception layer, communication layer, data access layer, data layer, service layer, application layer and display layer according to its functions;

[0011] A data acquisition protocol based on a plug-in design is built in the perception layer to identify and configure the perception device interface, and then load the corresponding protocol plug-in to perform data transmission with the perception device;

[0012] Constructing a protocol conversion module in the communication layer to realize data transmission between different communication protocols, and realizing secure data transmission through encryption technology and identity authentication;

[0013] Constructing a Web service interface at the data access layer, and selecting a corresponding API to provide Web services according to the complexity of the transaction processing scenario;

[0014] Constructing a database connection pool and a file storage interface supporting multiple types of databases at the data layer to enable uploading and downloading of files of different formats in the multiple types of databases;

[0015] Constructing a data service interface based on a role-based access control model and a cache mechanism in the service layer;

[0016] An independent and extensible API is set for each application module of the application layer, and the APIs of different application modules adopt a unified interface specification;

[0017] A web front-end based on a modern front-end framework is built on the display layer, and dynamic adjustment of interfaces for different terminal devices is achieved through responsive design.

[0018] Furthermore, the method of selecting a corresponding API to provide a Web service according to the complexity of the transaction processing scenario includes:

[0019] For complex transaction processing scenarios, SOAP API is used for processing, otherwise Web services are provided through RESTful API.

[0020] Furthermore, the file storage interface enables uploading and downloading of files of different formats through a RESTful API.

[0021] Furthermore, the data collected by the perception layer is encrypted after selecting a corresponding data transmission protocol through communication protocol conversion at the communication layer and transmitted to the data access layer; the data access layer transmits the received data to the data layer, and dynamically adjusts the data transmission strategy according to the database performance-related information fed back by the data layer; the data layer dynamically selects a storage strategy according to the data type of the received data, and feeds back the database performance-related information in real time; the service layer automatically adjusts the data cache update strategy according to the database performance-related information, and at the same time monitors specific events related to the data cache at the data layer to perform corresponding cache data operations in response to the specific events.

[0022] Furthermore, dynamically selecting a storage strategy according to the data type of the received data includes:

[0023] Store real-time data into NoSQL databases;

[0024] Store batch data in SQL database.

[0025] Furthermore, the automatically adjusting the data cache update strategy according to the database performance related information includes:

[0026] When processing complex transactions, the service layer temporarily saves data changes through a cache mechanism, and after the complex transaction is completed, feeds back information related to the database performance so that the data layer writes the cached data changes into the database in batches;

[0027] When processing concurrent transactions, the service layer caches and diverts some requests in high-concurrency scenarios, and processes cached requests in low-concurrency scenarios.

[0028] Furthermore, the application layer processes the large-scale data in slices and pushes the slices to the presentation layer in batches via WebSocket, and then the presentation layer renders the slices in steps according to the received data.

[0029] Furthermore, the presentation layer extracts real-time data from the data of the application layer received through WebSocket, and directly pushes the data to the visualization component of the web page front end.

[0030] Furthermore, different processing is performed according to the data type and protocol characteristics of the sensing terminal, including:

[0031] For non-standard protocol data packets, the edge nodes of the perception layer pre-process the data locally through edge computing devices, package them into a standardized format that can be recognized and processed by the system according to the application scenario, and then transmit them to the data layer layer by layer;

[0032] For standard protocol data packets, the perception layer directly transmits them to the data layer.

[0033] Furthermore, it also includes:

[0034] A data retransmission mechanism is constructed in the perception layer to identify network fluctuations, cache data when the network fluctuates, and retransmit cached data that has not been sent successfully after the network recovers.

[0035] Furthermore, the protocol plug-in is used to implement industrial standard protocols including Modbus and IEC 61850.

[0036] Furthermore, the encryption technology includes SSL / TLS, and the identity authentication adopts a two-way authentication mechanism.

[0037] Furthermore, the data access layer adopts JSON or XML as the data exchange format and supports transmission protocols including HTTP / HTTPS and MQTT.

[0038] Furthermore, the multi-type databases include SQL databases and NoSQL databases.

[0039] Furthermore, the data layer uses a distributed file system for file storage.

[0040] Furthermore, the application layer performs real-time data interaction with the presentation layer through AJAX and WebSocket technologies, and provides a batch data processing interface.

[0041] Beneficial Effects

[0042] Due to the adoption of the above-mentioned technical scheme, the present invention has the following advantages and positive effects compared with the prior art: the present invention systematically solves the compatibility, efficiency and security issues of various links such as data collection, transmission, storage, processing and display in the virtual power plant system through a clear layered interface design architecture and reasonable division and optimization of interface design, thereby improving the overall performance and integration efficiency of the system; the interface design scheme of the present invention has good scalability on the basis of ensuring the existing functions of the system, can flexibly adapt to the development of future technologies and the access of new functions, is suitable for a variety of application scenarios, significantly reduces the maintenance cost and development complexity of the system, and ensures the long-term availability of the system; the present invention makes the integration between systems more convenient and efficient through unified interface standards and security policy design, ensures the security of data transmission and the uniformity of data interaction between systems, and avoids compatibility issues caused by inconsistent data formats in the system; the present invention improves the real-time data processing capability of the system as a whole through the optimization of interface design and the collaborative work of various levels. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figure 1 It is a system architecture diagram of dynamic performance analysis and evaluation of a virtual power plant according to an embodiment of the present invention;

[0044] Figure 2 It is an interface architecture diagram of a virtual power plant dynamic performance analysis and evaluation system according to an implementation mode of the present invention. DETAILED DESCRIPTION

[0045] The present invention will be further described below in conjunction with specific embodiments. It should be understood that these embodiments are only used to illustrate the present invention and are not intended to limit the scope of the present invention. In addition, it should be understood that after reading the content taught by the present invention, those skilled in the art can make various changes or modifications to the present invention, and these equivalent forms fall within the scope limited by the appended claims of the application equally.

[0046] The embodiment of the present invention relates to an interface design method for a virtual power plant dynamic performance analysis and evaluation system, comprising the following steps:

[0047] Divide the virtual power plant dynamic performance analysis and evaluation system into multiple levels according to its functions;

[0048] Different interfaces are designed for each layer to ensure that the entire system meets the requirements of compatibility, security, scalability, stability and efficiency.

[0049] like Figure 1 As shown in the figure, the dynamic performance analysis and evaluation system of the virtual power plant can be divided into multiple levels, starting from the perception layer, through the communication layer, data access layer, data layer, service layer, application layer, and finally to the display layer. Each level represents a part of the functional module of the system. The various levels of the system exchange and communicate data through well-defined interfaces to ensure the efficient operation of the system and the seamless flow of information. The figure specifically shows the main functions of each level, such as data collection and processing at the perception layer, multi-protocol support and encrypted transmission at the communication layer, and standardized data format and transmission protocol at the data access layer.

[0050] Figure 2 The convenient and efficient interface design architecture of the virtual power plant dynamic performance analysis and evaluation system is demonstrated, including the standardized data acquisition protocol and high-frequency data transmission mechanism of the perception layer, the multi-protocol compatibility and protocol conversion design of the communication layer, the unified data format and efficient data transmission of the data access layer, the database interface and file storage interface design of the data layer, the authentication service, permission management and data access service of the service layer, the modular interface design and real-time data interaction of the application layer, and the cross-browser compatibility design and data visualization function of the display layer. Through the optimized design of these interfaces, the system realizes efficient, safe and stable data processing and communication, and significantly improves the real-time performance, compatibility and user experience of the system.

[0051] The following describes in detail the interface design of each functional level and the collaborative work between interfaces at different functional levels.

[0052] 1. Interface design at each functional level

[0053] 1. Perception layer interface design

[0054] The perception layer mainly involves data collection from various power generation units and load aggregation systems. In the perception layer, standardized data collection protocols such as IEC 61850 are adopted, and compatibility with multiple devices is achieved through plug-in design. Data from various distributed energy and load devices are uploaded to the central system in real time through the MQTT protocol. Through the adaptive data collection mechanism, the system can automatically identify and configure the interface of the newly connected device, greatly simplifying the configuration process of device access. In actual operation, the delay of data collection is reduced by about 30%, and the automated configuration improves the operation and maintenance efficiency.

[0055] 1) Data Collection Protocol

[0056] Standardized protocol support: Support for commonly used industrial standard protocols such as Modbus, IEC 61850, etc. The plug-in design enables the system to be compatible with different devices by loading different protocol plug-ins.

[0057] Adaptive data acquisition: Design a mechanism to automatically identify and configure device interfaces to reduce manual intervention and improve configuration efficiency.

[0058] 2) Data transmission

[0059] High-frequency data transmission: Use real-time transmission protocols (such as MQTT) to achieve high-frequency data transmission to ensure the real-time and accuracy of data.

[0060] Data buffering and retransmission mechanism: When the network fluctuates, the data can be cached and the unsuccessfully sent data packets can be automatically retransmitted after the network recovers.

[0061] (II) Communication layer interface design

[0062] The communication layer is responsible for data transmission and network security. The design of the communication layer adopts multi-protocol support and secure transmission mechanism. By supporting communication protocols such as TCP / IP and UDP, the system can achieve stable communication in different network environments. The present invention also ensures the security of data transmission through SSL / TLS encryption technology, and the two-way identity authentication mechanism prevents unauthorized data access. Actual tests show that the system can still maintain efficient communication stability under complex network conditions, and the security of data transmission has been significantly improved.

[0063] 1)Multi-protocol support

[0064] Multi-protocol compatibility: Compatibility with common communication protocols such as TCP / IP and UDP to ensure stable communication in different network environments.

[0065] Protocol conversion: Design a protocol conversion module to enable data of different communication protocols to communicate seamlessly and improve the flexibility of the system.

[0066] 2) Secure transmission

[0067] Encrypted transmission: Use encryption technologies such as SSL / TLS to ensure the security of data during transmission.

[0068] Identity verification: A two-way authentication mechanism is used to ensure the legitimacy of the identities of both the data sender and the data receiver.

[0069] (III) Data access layer interface design

[0070] The data access layer is the aggregation point of the data transmission protocol and the WebService interface. The data access layer uses a unified data format (JSON / XML) and an efficient data transmission protocol (HTTP / HTTPS, MQTT). The RESTful API interface provides convenient data access and integration services for external systems, while the SOAP API is used for complex transaction processing scenarios. In actual applications, the data access layer realizes the unified management and efficient transmission of multi-source data, simplifies the system integration process, and significantly improves the compatibility and processing efficiency of system data.

[0071] 1) Standardized transmission protocol

[0072] Unified data format: Use JSON or XML as the data exchange format to ensure the readability and parsability of data between different systems.

[0073] Efficient data transmission: Supports transmission protocols such as HTTP / HTTPS and MQTT to ensure efficient data transmission.

[0074] 2) WebService interface

[0075] RESTful API: Design RESTful API interfaces to provide CRUD operations (create, read, update, delete) and query services to ensure that external systems can be easily called and integrated.

[0076] SOAP API: SOAP API support is provided for scenarios that require complex transaction processing.

[0077] (IV) Data layer interface design

[0078] The data layer is responsible for data storage and management. The data layer is designed with multi-database support and file storage interfaces. This layer uses distributed databases and file systems (such as HDFS) to process and store large amounts of system data. Through the application of database connection pools, the system's data access efficiency and concurrent processing capabilities have been greatly improved. In the actual operating environment, the system's data storage and retrieval speed has increased by about 35%, effectively supporting the needs of large-scale data processing.

[0079] 1) Database interface

[0080] Database connection pool: Design a database connection pool to improve the efficiency and concurrency of database access.

[0081] Multiple database support: Supports SQL and NoSQL databases, such as MySQL, PostgreSQL, MongoDB, etc., to meet different data storage needs.

[0082] 2) File storage interface

[0083] File upload and download: Provides a RESTful API interface to upload and download files, supporting multiple file formats (PDF, Excel, Word, PNG, JPG).

[0084] Distributed storage: Use distributed file systems (such as HDFS) to improve the reliability and scalability of file storage.

[0085] (V) Service layer interface design

[0086] The service layer provides various application services, such as security services, data access services, etc. At the service layer, the present invention provides a wealth of security services and data access services. Through the authentication mechanisms of OAuth 2.0 and JWT, the system ensures the identity security of users and services. RBAC authority management control realizes the refined management of data access. The introduction of caching mechanisms (such as Redis) further improves the speed of data access and the response performance of the system. Actual tests show that the improvement of the service layer has increased the system response speed by about 25% and effectively ensured the security of data.

[0087] 1) Security Services

[0088] Identity authentication: Use authentication mechanisms such as OAuth 2.0 and JWT to ensure the security of user and system identity authentication.

[0089] Permission management: Provides fine-grained permission management control and a role-based access control (RBAC) model to ensure the security and compliance of data access.

[0090] 2) Data access service

[0091] Cache mechanism: Design a cache mechanism (such as Redis) to improve data access speed and system response performance.

[0092] Data service API: provides API interface for data query and processing, supporting complex query and data analysis operations.

[0093] (VI) Application layer interface design

[0094] The application layer includes functional modules such as home page, archive management, and dynamic summary. The application layer interface is designed with independent API interfaces and unified interface specifications. Each functional module provides services through independent interfaces, supporting flexible functional expansion and external system calls. Through real-time data interaction technology (AJAX, WebSocket), the system can realize dynamic data display and interaction between the front and back ends. In actual applications, the optimization of the application layer improves the ease of use and scalability of the system, and the real-time and flexibility of user operations have been greatly improved.

[0095] 1) Modular interface

[0096] Independent module interface: Each functional module provides an independent API interface to facilitate external system calls and function expansion.

[0097] Unified interface specifications: Define unified interface specifications and documentation to ensure ease of use and consistency of the interface.

[0098] 2) Data Interaction

[0099] Real-time data interaction: AJAX, WebSocket and other technologies are used to achieve real-time data interaction and dynamic display between the front and back ends.

[0100] Batch operation support: Provides batch data processing interface to improve data processing efficiency.

[0101] (VII) Display layer interface design

[0102] The presentation layer mainly displays data through various browsers. The presentation layer achieves cross-browser compatibility through modern front-end frameworks (Vue.js, React), and adopts responsive design to ensure a good user experience on different devices. Data visualization uses tools such as ECharts to provide users with rich chart display and interactive functions. In actual operation, the optimization of the presentation layer enhances the user's visual experience, and the real-time performance and visualization of data have been significantly improved.

[0103] 1) Cross-browser compatibility

[0104] Front-end framework selection: Use modern front-end frameworks such as Vue.js and React to ensure compatibility and performance in multiple browsers.

[0105] Responsive design: Implement responsive design to ensure a good user experience on different devices (PC, mobile phones, tablets).

[0106] 2) Front-end interface

[0107] Data visualization: Use data visualization libraries such as ECharts and D3.js to provide rich data display effects and interactive functions.

[0108] Real-time update: Use WebSocket to realize real-time push of data and real-time update of pages.

[0109] 2. Collaboration between interfaces at different functional levels

[0110] (I) Collaborative optimization of interfaces and protocols between the perception layer and the communication layer:

[0111] 1. Interface protocol adaptation:

[0112] When a sensing device is connected to the system, the sensing layer first determines the communication protocol used by the device through the protocol identification module. According to the protocol type, the corresponding protocol plug-in is loaded, and the data is transmitted to the communication layer through a standardized interface. After the communication layer receives the sensing layer data, the protocol conversion module performs dynamic protocol conversion according to the configuration, selects a suitable data transmission protocol (such as MQTT, HTTP, etc.), and transmits it to the data access layer after encryption.

[0113] 2. Network fluctuation processing mechanism:

[0114] The perception layer monitors the network quality and starts the data caching mechanism when it detects network anomalies (such as increased latency or packet loss). When the network recovers, the perception layer automatically retransmits the cached data through the protocol conversion module of the communication layer. If the network fluctuates frequently, the communication layer will reduce the transmission frequency to ensure the stability of the system.

[0115] (II) Collaborative optimization of data access layer and data layer interfaces and protocols:

[0116] 1. Data transmission feedback mechanism

[0117] When the data access layer transfers data to the data layer, the data layer will provide real-time feedback on database performance (including read and write pressure, storage space usage, etc.). Based on the feedback from the data layer, the data access layer can dynamically adjust the data transmission strategy. For example, when the data layer reports that the write pressure is high, the data access layer can temporarily slow down the transmission rate of low-priority data to prioritize the transmission of high-priority data.

[0118] 2. Dynamic storage strategy

[0119] The data layer dynamically selects a storage strategy based on the type of data passed in by the data access layer. For example, when real-time data is passed in, the data layer automatically stores it in a NoSQL database to ensure fast data writing and subsequent efficient reading; for batch data, the data layer will choose a SQL database for storage to ensure data integrity and transactionality. The data access layer can call the data layer's storage strategy interface through an API to understand the current data storage pressure, dynamically adjust the data transmission frequency and batch processing strategy, and further optimize system performance.

[0120] 3. File transfer and storage collaboration

[0121] When transferring files in batches, the data access layer can work with the distributed file system interface of the data layer through the RESTful API. The file storage interface of the data layer should support parallel upload and shard reorganization to ensure that the data access layer can quickly and reliably transfer large data files. The data layer provides real-time storage feedback information, and the data access layer can decide whether to compress or shard the transferred files based on this information to ensure the efficiency of file transfer.

[0122] (III) Collaborative optimization of service layer and data layer interfaces and protocols:

[0123] 1. Cache mechanism and real-time feedback from database

[0124] Cache and data synchronization mechanism: The service layer can automatically adjust the cache update strategy based on the real-time feedback from the data layer. For example, when the database load is high, the service layer can temporarily increase the frequency of cache usage and reduce requests to directly access the database. When the database load is restored, the data in the cache is synchronized to the database in batches to ensure the final consistency of the data.

[0125] Real-time cache invalidation mechanism: The cache in the service layer can be implemented through an event-driven mechanism. When certain key data in the data layer changes, the cache in the service layer can be invalidated in real time by listening to events and reload the latest data to ensure the timeliness and accuracy of the cached data.

[0126] 2. Collaboration between transaction processing and database

[0127] Delayed writing in transaction processing: When processing complex transactions, the service layer can temporarily save data changes through the cache mechanism and delay writing to the database to avoid the performance overhead caused by frequent write operations. After the transaction is completed, the cached data is written to the database in batches to achieve efficient transaction processing.

[0128] Concurrent transaction control: The service layer can dynamically adjust the transaction concurrency strategy by coordinating with the data layer. For high-concurrency scenarios, the service layer can divert some requests through caching to avoid database bottlenecks. In addition, when processing distributed transactions, the service layer can ensure data consistency and integrity through the database's transaction management mechanism.

[0129] (IV) Collaborative optimization of application layer and presentation layer interfaces and protocols:

[0130] 1. Efficient data transmission and update mechanism

[0131] Batch push and shard processing: When the application layer pushes data in batches, the presentation layer renders on demand based on the amount of data. For large-scale data, the application layer can process the data in shards and push them to the presentation layer in batches through WebSocket. The presentation layer renders in steps based on the received data to ensure smooth page loading.

[0132] Real-time data synchronization: After the presentation layer receives the real-time data from the application layer through WebSocket, it can directly push the data to the front-end visualization component (such as Echarts or D3.js) to achieve automatic updating of the chart. Users can view the latest data without refreshing the page.

[0133] 2. Data transmission performance optimization

[0134] Compressed data transmission: For large amounts of real-time data, the application layer can compress the data before transmitting it through WebSocket, reducing the amount of data transmitted and thus reducing network latency. The presentation layer decompresses and renders the data after receiving it, ensuring efficient transmission and presentation.

[0135] Multi-threaded data processing: The presentation layer can introduce Web Workers for multi-threaded data processing to ensure that the rendering task of the main thread is not affected when processing large amounts of data, thereby improving the overall response speed.

[0136] (V) Optimization of data sending and unpacking process:

[0137] 1. Preprocessing and packaging based on edge computing

[0138] For non-standard data packets sent by sensors or IoT devices (such as data in custom formats or specific protocols), edge computing devices can be introduced to pre-process these data. At the edge node of the perception layer, data can be packaged and processed locally according to the data type and protocol characteristics of the terminal. In this way, multiple protocols (such as Modbus, IEC 61850, REST API, etc.) can be unified into a standardized format that the system can recognize and process, such as JSON or XML.

[0139] The role of edge computing: When a terminal device sends data, the edge device can pre-process the data, remove redundant information, or convert the format, and package it according to the application scenario for subsequent transmission and storage. This not only reduces the processing burden of the central system, but also improves the efficiency of data transmission.

[0140] 2. Direct transmission and unpacking of IoT terminal data

[0141] For IoT devices that use standard protocols (such as MQTT and CoAP), these devices already have relatively good data packaging capabilities. In particular, the MQTT protocol itself is suitable for resource-constrained devices and can achieve lightweight message transmission. For the packet sending behavior of these devices, the system can adopt the strategy of "directly transmitting to the data layer and then unpacking".

[0142] The specific process is:

[0143] Direct upload at the perception layer: For these standard protocol devices, no additional edge preprocessing is required, and the perception layer can directly upload data to the data layer through the communication layer.

[0144] Unpacking at the data layer: In the data layer, for packets of these standard protocols (such as MQTT packets), data can be automatically disassembled and parsed according to the protocol standards and stored in the appropriate database. This method can reduce the computing pressure of the perception layer, especially for scenarios with small data and frequent transmission.

[0145] 3. Dynamic processing based on universal data interface

[0146] A dynamic processing engine is introduced to dynamically identify the data packet sending and unpacking requirements of different terminal devices at the perception layer. The engine can determine the type of data packets sent by different terminals and select different processing methods according to different terminal protocols. For non-standard protocol data that needs to be packaged, the packaging is completed directly at the perception layer; for data that has been packaged according to the standard protocol, it is directly uploaded to the data layer.

[0147] Dynamic identification mechanism: Through a unified data interface design, the engine can identify whether the data packet is a standard protocol (such as MQTT) or a non-standard protocol, and then select different processing paths.

[0148] Multi-protocol compatibility: The perception layer can support multiple protocol stacks and has the ability to adapt to different terminal protocols. For example, through a unified API gateway, it can handle HTTP / HTTPS, WebSocket protocols, as well as MQTT, CoAP and other IoT protocols.

Claims

1. An interface design method for a virtual power plant dynamic performance analysis and evaluation system, characterized in that: The following steps are involved: The dynamic performance analysis and evaluation system of virtual power plant is divided into perception layer, communication layer, data access layer, data layer, service layer, application layer and display layer according to its functions; A data acquisition protocol based on a plug-in design is built in the perception layer to identify and configure the perception device interface, and then load the corresponding protocol plug-in to perform data transmission with the perception device; Constructing a protocol conversion module in the communication layer to realize data transmission between different communication protocols, and realizing secure data transmission through encryption technology and identity authentication; Constructing a Web service interface at the data access layer, and selecting a corresponding API to provide Web services according to the complexity of the transaction processing scenario; Constructing a database connection pool and a file storage interface supporting multiple types of databases at the data layer to enable uploading and downloading of files of different formats in the multiple types of databases; Constructing a data service interface based on a role-based access control model and a cache mechanism in the service layer; An independent and extensible API is set for each application module of the application layer, and the APIs of different application modules adopt a unified interface specification; A web front-end based on a modern front-end framework is built on the display layer, and dynamic adjustment of interfaces for different terminal devices is achieved through responsive design.

2. The method according to claim 1, characterized in that The Web service provided by selecting a corresponding API according to the complexity of the transaction processing scenario includes: For complex transaction processing scenarios, SOAP API is used for processing, otherwise Web services are provided through RESTful API.

3. The method according to claim 2, characterized in that The file storage interface implements uploading and downloading of files of different formats through a RESTful API.

4. The method according to claim 1, characterized in that: The data collected by the perception layer is encrypted after the communication layer selects the corresponding data transmission protocol through communication protocol conversion; the data access layer transmits the received data to the data layer, and dynamically adjusts the data transmission strategy according to the database performance related information fed back by the data layer; the data layer dynamically selects the storage strategy according to the data type of the received data, and feeds back the database performance related information in real time; the service layer automatically adjusts the data cache update strategy according to the database performance related information, and monitors the specific events of the data layer related to the data cache to perform corresponding cache data operations in response to the specific events.

5. The method according to claim 4, characterized in that The dynamically selecting a storage strategy according to the data type of the received data includes: Store real-time data into NoSQL databases; Store batch data in SQL database.

6. The method according to claim 4, characterized in that The automatically adjusting the data cache update strategy according to the database performance related information includes: When processing complex transactions, the service layer temporarily saves data changes through a cache mechanism, and after the complex transaction is completed, feeds back information related to the database performance so that the data layer writes the cached data changes into the database in batches; When processing concurrent transactions, the service layer caches and diverts some requests in high-concurrency scenarios, and processes cached requests in low-concurrency scenarios.

7. The method according to claim 1, characterized in that The application layer processes the large-scale data in slices and pushes them to the presentation layer in batches via WebSocket, and then the presentation layer renders them step by step according to the received data.

8. The method according to claim 7, characterized in that The presentation layer extracts real-time data from the data of the application layer received through WebSocket, and directly pushes it to the visualization component of the web page front end.

9. The method according to claim 1, characterized in that: Different processing is performed according to the data type and protocol characteristics of the sensing terminal, including: For non-standard protocol data packets, the edge nodes of the perception layer pre-process the data locally through edge computing devices, package them into a standardized format that can be recognized and processed by the system according to the application scenario, and then transmit them to the data layer layer by layer; For standard protocol data packets, the perception layer directly transmits them to the data layer.

10. The method according to claim 1, characterized in that Also includes: A data retransmission mechanism is constructed in the perception layer to identify network fluctuations, cache data when the network fluctuates, and retransmit cached data that has not been sent successfully after the network recovers.

Images