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

Abstract

The application relates to an interface design method of a virtual power plant dynamic performance analysis and evaluation system, which comprises the following steps: dividing the virtual power plant dynamic performance analysis and evaluation system into a perception layer, a communication layer, a data access layer, a data layer, a service layer, an application layer and a display layer according to functions; designing different interfaces for each layer, including a standardized data acquisition protocol and a high-frequency data transmission mechanism of the perception layer, multi-protocol compatibility and protocol conversion design of the communication layer, unified data format and efficient data transmission of the data access layer, database interface and file storage interface design of the data layer, authentication service, permission management and data access service of the service layer, modular interface design and real-time data interaction of the application layer, and cross-browser compatibility design and data visualization function of the display layer. Through the design optimization 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 application relates to the technical field of virtual power plants, and in particular to an interface design method for a virtual power plant dynamic performance analysis and evaluation system. BACKGROUND

[0002] In recent years, with the increasing complexity of power systems and the increasing proportion of renewable energy, virtual power plants (VPP) as a new power system management mode have received extensive attention and application. Virtual power plants integrate various distributed energy resources (such as wind power, photovoltaic power, energy storage systems, etc.) and load control, optimize scheduling and energy management, thereby achieving efficient control and resource optimization of the power system. This mode not only helps to improve the flexibility and reliability of the power system, but also supports better integration of renewable energy and promotes the development of green power.

[0003] Interface design plays a crucial role in the virtual power plant dynamic performance analysis and evaluation system, and the existing solutions have the following problems:

[0004] (1) Inconsistent data formats and protocols, leading 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 and development cost of system integration. In addition, the lack of standardized protocols may lead to unstable data exchange between systems, affecting the reliability of data transmission.

[0005] (2) Data security issues involved in data transmission. 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 mechanism is not perfect, which may lead to data leakage or unauthorized access, affecting the security of the system.

[0006] (3) Limitations in compatibility and scalability. For example, the interface may not consider future technology upgrades and functional expansion needs, making it difficult for the system to upgrade or expand smoothly when facing new demands. In addition, the design of the interface may not fully consider the compatibility with other systems, leading to integration problems between different systems.

[0007] (4) There are problems of slow data transmission speed and long response time. In the face of large-scale data flow or high-frequency requests, the performance of the interface may not meet the demand, leading to data transmission delay 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

[0008] The technical problems to be solved by the present application are to provide an interface design method of a virtual power plant dynamic performance analysis and evaluation system, which can solve the problems existing in the interface design of the 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 application to solve the technical problems is to provide an interface design method of a virtual power plant dynamic performance analysis and evaluation system, comprising the following steps:

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

[0011] A data acquisition protocol based on 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] A protocol conversion module is constructed in the communication layer to realize the transmission of data between different communication protocols, and to realize the secure transmission of data through encryption technology and identity authentication;

[0013] A Web service interface is constructed in the data access layer, and the corresponding API is selected according to the complexity of the transaction processing scenario to provide Web service;

[0014] A database connection pool supporting multiple types of databases and a file storage interface are constructed in the data layer to realize the uploading and downloading of files in different formats in the multiple types of databases;

[0015] A data service interface based on a role-based access control model and a cache mechanism is constructed 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 in the display layer, and a dynamic adjustment to the interface of different terminal devices is realized through responsive design.

[0018] Further, the corresponding API is selected according to the complexity of the transaction processing scenario to provide Web service, which comprises:

[0019] For complex transaction processing scenarios, SOAP API is used for processing, otherwise RESTful API is used to provide Web service.

[0020] Further, the file storage interface realizes the uploading and downloading of files in different formats through RESTful API.

[0021] Further, the data collected by the perception layer is transmitted to the data access layer after being encrypted by a corresponding data transmission protocol through a communication protocol conversion in the communication 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 listens to specific events related to the data layer and data cache to perform corresponding cache data operations in response to the specific events.

[0022] Further, the dynamically selected storage strategy according to the data type of the received data comprises:

[0023] storing real-time data into a NoSQL database;

[0024] storing batch data into a SQL database.

[0025] Further, the automatically adjusted data cache update strategy according to the database performance related information comprises:

[0026] when processing a complex transaction, the service layer temporarily saves data changes through a cache mechanism, and feeds back the database performance related information after the completion of the complex transaction, 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 shunts part of the requests in a high concurrency scenario, and processes cache requests in a low concurrency scenario.

[0028] Further, after the application layer processes large-scale data in slices, the data is pushed to the display layer in batches through WebSocket, and then rendered by the display layer according to the received data.

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

[0030] Further, different processing is performed according to the data type and protocol characteristics of the perception terminal, comprising:

[0031] for non-standard protocol data packets, the edge node of the perception layer pre-processes the data through an edge computing device, packs the data into a standardized format that can be recognized and processed by the system according to the application scenario, and then transmits the data to the data layer layer by layer;

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

[0033] Further, it also includes:

[0034] The perception layer constructs a data retransmission mechanism to identify network fluctuations, buffer data during network fluctuations, and retransmit buffered data that has not been successfully sent after the network recovers.

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

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

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

[0038] Further, the multi-type database includes SQL databases and NoSQL databases.

[0039] Further, the data layer adopts a distributed file system for file storage.

[0040] Further, the application layer interacts with the presentation layer in real time through AJAX and WebSocket technologies and provides a batch data processing interface.

[0041] Advantages

[0042] Compared with the prior art, the application has the following advantages and positive effects: The application has a clear layered interface design architecture, reasonably divides and optimizes the interface design, systematically solves the compatibility, efficiency and security problems of data acquisition, transmission, storage, processing and display in the virtual power plant system, improves the overall performance and integration efficiency of the system, and has good expansibility on the basis of ensuring the existing functions of the system. It can flexibly adapt to the development of future technologies and the access of new functions, is suitable for various application scenarios, significantly reduces the maintenance cost and development complexity of the system, and ensures the long-term usability of the system. The application designs a unified interface standard and security strategy, making the integration between systems more convenient and efficient, ensuring the security of data transmission and the uniformity of data interaction between systems, and avoiding compatibility problems caused by inconsistent data formats in the system. The application optimizes the interface design and coordinates the work of each level, and improves the real-time data processing capability of the system as a whole. BRIEF DESCRIPTION OF DRAWINGS

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

[0044] Figure 2 is a virtual power plant dynamic performance analysis and evaluation system interface architecture diagram of an embodiment of the present application. DETAILED DESCRIPTION

[0045] The present application will be further described with reference to the following specific examples. It should be understood that these examples are intended to illustrate the present application and are not intended to limit the scope of the present application. Furthermore, it should be understood that various modifications and changes can be made to the present application by those skilled in the art upon reading the contents of the present application, and such equivalent forms are also within the scope of the appended claims.

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

[0047] The virtual power plant dynamic performance analysis and evaluation system is divided into multiple levels according to function;

[0048] Different interfaces are designed for each level, so that the entire system can meet compatibility, security, scalability, stability and efficiency.

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

[0050] Figure 2 The convenient and efficient interface design architecture of the virtual power plant dynamic performance analysis and evaluation system is shown, 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 compatible design and data visualization function of the display layer. Through the optimization design of these interfaces, the system realizes efficient, secure and stable data processing and communication, significantly improving the real-time performance, compatibility and user experience of the system.

[0051] The following detailed description describes the interface design of each functional level and the coordination between the interfaces of different functional levels.

[0052] I. Interface design of each functional level

[0053] (I) Sensing layer interface design

[0054] The sensing layer mainly involves data collection of various power generation units and load aggregation systems. In the sensing layer, standardized data collection protocols such as IEC 61850 are adopted, and compatibility with multiple devices is achieved through plug-in design. The data of various distributed energy and load devices is 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 newly connected devices, greatly simplifying the configuration process of device access. In actual operation, the delay of data collection is reduced by about 30%, and the automation 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. Adopt plug-in design, so that the system can be compatible with different devices by loading different protocol plug-ins.

[0057] Adaptive data collection: design a mechanism to automatically identify and configure device interfaces, reducing manual intervention and improving 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, ensuring the real-time and accuracy of data.

[0060] Data buffering and retransmission mechanism: when the network fluctuates, it can cache data and automatically retransmit the data packets that have not been successfully sent 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 invention also uses SSL / TLS encryption technology to ensure the security of data transmission, and the two-way identity authentication mechanism prevents unauthorized data access. Actual tests show that the system can still maintain high 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: Achieve compatibility with common communication protocols such as TCP / IP, UDP, etc., ensuring stable communication in different network environments.

[0065] Protocol conversion: Design a protocol conversion module to seamlessly interconnect data from different communication protocols, improving system flexibility.

[0066] 2) Secure transmission

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

[0068] Identity verification: Adopt a two-way authentication mechanism to ensure the legitimacy of both data sending and receiving parties.

[0069] (Three) Data access layer interface design

[0070] The data access layer is the aggregation point of data transmission protocols and WebService interfaces. The data access layer uses a unified data format (JSON / XML) and efficient data transmission protocols (HTTP / HTTPS, MQTT). RESTful API interfaces provide convenient data access and integration services for external systems, while SOAP API is used for complex transaction processing scenarios. In practical applications, the data access layer realizes unified management and efficient transmission of multi-source data, simplifying the integration process of the system, and significantly improving 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 data readability and parsability between different systems.

[0073] Efficient data transmission: Support HTTP / HTTPS, MQTT, and other transmission protocols 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, ensuring that external systems can easily call and integrate.

[0076] SOAP API: Provide SOAP API support for scenarios requiring complex transaction processing.

[0077] (Four) Data layer interface design

[0078] The data layer is responsible for data storage and management. It designs multi-database support and file storage interfaces. This layer uses distributed databases and file systems (such as HDFS) to handle and store large amounts of system data. Through the application of database connection pooling, the system's data access efficiency and concurrent processing capacity have been greatly improved. In the actual running 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] Multi-database support: Support 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: Provide RESTful API interfaces to implement file upload and download, 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] (Five) Service Layer Interface Design

[0086] The service layer provides various application services such as security services and data access services. In the service layer, the invention provides rich 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 permission management control realizes fine-grained management of data access. The introduction of cache 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 makes the system response speed increase by about 25%, and effectively guarantees 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 verification.

[0089] Permission management: Provide fine-grained permission management control based on the Role-Based Access Control (RBAC) model to ensure the security and compliance of data access.

[0090] 2) Data Access Services

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

[0092] Data service API: Provide API interfaces for data query and processing, support complex query and data analysis operations.

[0093] (VI) Application layer interface design

[0094] The application layer includes homepage, archive management, dynamic summary and other functional modules. The application layer interface designs independent API interfaces and unified interface specifications. Each functional module provides services through independent interfaces, supporting flexible function extension and external system call. Through real-time data interaction technology (AJAX, WebSocket), the system can realize dynamic data display and interaction between front and back end. In practical application, the optimization of the application layer improves the usability and scalability of the system, and the real-time and flexibility of user operation are greatly improved.

[0095] 1) Modular interface

[0096] Independent module interface: Each functional module provides independent API interface, which is convenient for external system call and function extension.

[0097] Unified interface specification: Define unified interface specification and document to ensure the usability and consistency of the interface.

[0098] 2) Data interaction

[0099] Real-time data interaction: Use AJAX, WebSocket and other technologies to realize real-time data interaction and dynamic display between front and back end.

[0100] Batch operation support: Provide interfaces for batch data processing to improve data processing efficiency.

[0101] (VII) Display layer interface design

[0102] The display layer mainly displays data through various browsers. The display layer realizes cross-browser compatibility through modern front-end frameworks (Vue.js, React), and uses responsive design to ensure good user experience on different devices. Data visualization uses tools such as ECharts to provide users with rich chart display and interaction functions. In actual operation, the optimization of the display layer enhances the user's visual experience, and the real-time and visualization effect of data has 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 on multiple browsers.

[0105] Responsive Design: Implement responsive design to ensure good user experience on different devices (PC, mobile phone, tablet).

[0106] 2) Front-end Interface

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

[0108] Real-time Update: Use WebSocket to realize real-time data pushing and real-time page updating.

[0109] II. Coordination between interfaces of different functional levels

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

[0111] 1. Interface protocol adaptation:

[0112] When a perception device accesses the system, the perception layer first determines the communication protocol used by the device through the protocol identification module. According to the protocol type, load the corresponding protocol plug-in, and transmit the data to the communication layer through the standardized interface. After receiving the data from the perception layer, the protocol conversion module in the communication layer performs dynamic protocol conversion according to the configuration, selects the appropriate 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 network quality and starts the data caching mechanism when network anomalies (such as increased delay or packet loss) are detected. When the network recovers, the perception layer automatically retransmits the cached data through the protocol conversion module in the communication layer. If network fluctuations are frequent, the communication layer will reduce the transmission frequency to ensure the stability of the system.

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

[0116] 1. Data transmission feedback mechanism

[0117] During data transmission from the data access layer to the data layer, the data layer will provide real-time feedback on the performance-related information of the database (including read-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 feedbacks 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 transmitted by the data access layer. For example, when real-time data is transmitted, the data layer automatically stores it in a NoSQL database to ensure fast writing and subsequent efficient reading of data. For batch data, the data layer selects 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 and dynamically adjust the data transmission frequency and batch processing strategy to further optimize system performance.

[0120] 3. File transfer and storage coordination

[0121] When transmitting files in batches, the data access layer can work with the data layer's distributed file system interface through RESTful API. The data layer's file storage interface should support parallel uploading and shard reorganization to ensure that the data access layer can quickly and reliably transmit large data files. The data layer provides real-time storage feedback information, and the data access layer can decide whether to compress, shard, or perform other operations on the transmitted files based on this information to ensure efficient file transfer.

[0122] (Three) Service layer and data layer interface and protocol coordination optimization:

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

[0124] Cache and data synchronization mechanism: The service layer can automatically adjust the cache update strategy based on real-time feedback from the data layer. For example, when the database load is high, the service layer can temporarily increase the use frequency of the cache to reduce direct access to the database. When the database load recovers, the data in the cache is synchronized to the database in batches to ensure the eventual 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 and reloaded with the latest data in real time through event listening, ensuring the timeliness and accuracy of the cache data.

[0126] 2. Transaction processing and database coordination

[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 performance overhead caused by frequent write operations. After the transaction is completed, the cache data is written to the database in batches to achieve efficient transaction processing.

[0128] Concurrent transaction control: The service layer can dynamically adjust the concurrency strategy of transactions by cooperating with the data layer. For high-concurrency scenarios, the service layer can distribute part of the requests through caching to avoid database bottlenecks. Moreover, in distributed transaction processing, the service layer can ensure data consistency and integrity through the transaction management mechanism of the database.

[0129] (IV) Coordination optimization of application layer and presentation layer interface and protocol:

[0130] 1. Efficient data transmission and update mechanism

[0131] Batch pushing and sharding processing: When the application layer pushes data in batches, the presentation layer renders as needed according to the data volume. For large-scale data, the application layer can perform sharding processing on the data and push it to the presentation layer in batches through WebSocket. The presentation layer renders step by step based on the received data to ensure smooth page loading.

[0132] Real-time data synchronization: After receiving real-time data from the application layer through WebSocket, the presentation layer can directly push the data to the front-end visualization components (such as Echarts or D3.js), achieving automatic updating of charts without the need for users to refresh the page to view the latest data.

[0133] 2. Performance optimization of data transmission

[0134] Compressed data transmission: For a large amount of real-time data, the application layer can first 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 display.

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

[0136] (V) Optimization of data packaging 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 custom formats or specific protocol data), edge computing devices can be introduced to preprocess these data. At the edge nodes of the perception layer, data can be locally packaged according to the data type and protocol characteristics of the terminal. This can unify various protocols (such as Modbus, IEC 61850, REST API, etc.) into a standardized format that the system can recognize and process, such as JSON or XML.

[0139] The role of edge computing: When the terminal device sends out data, the edge device can preprocess the data, remove redundant information, or perform format conversion, and package it according to the application scenario, making it easier 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 using standard protocols such as MQTT and CoAP, these devices themselves already have relatively good data packaging capabilities, especially the MQTT protocol itself is suitable for resource-constrained devices and can achieve lightweight message transmission. For the packaging behavior of these devices, the system can adopt the strategy of "direct transmission to the data layer and then unpacking".

[0142] The specific process is:

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

[0144] Data layer unpacking: In the data layer, for these standard protocol packets (such as MQTT packets), data can be automatically unpacked, parsed, and stored in the appropriate database according to the protocol standard. This method can reduce the computational burden of the perception layer, especially suitable for scenarios with small data and frequent transmission.

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

[0146] Introduce a dynamic processing engine that dynamically identifies data packaging and unpacking requirements for different terminal devices in the perception layer. This engine can determine the type of data packets sent by different terminals and choose different processing methods based on the different terminal protocols. For non-standard protocol data that needs to be packaged, packaging is completed directly in the perception layer; for data that has been packaged according to standard protocols, it is directly uploaded to the data layer.

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

[0148] Multi-protocol compatibility: The perception layer can support multiple protocol stacks and has adaptive capabilities for different terminal protocols. For example, through a unified API gateway, it can handle HTTP / HTTPS, WebSocket protocols, as well as MQTT, CoAP, and other Internet of Things protocols.

Claims

1. An interface design method of a virtual power plant dynamic performance analysis evaluation system, characterized by, The method comprises the following steps: The virtual power plant dynamic performance analysis evaluation system is divided into a perception layer, a communication layer, a data access layer, a data layer, a service layer, an application layer, and a display layer according to functions; A data acquisition protocol based on plug-in design is built in the perception layer to identify and configure a perception device interface, and then corresponding protocol plug-ins are loaded to perform data transmission with the perception device; A protocol conversion module is built in the communication layer to realize data transmission between different communication protocols, and to realize secure data transmission through encryption technology and identity authentication; A Web service interface is built in the data access layer, and a corresponding API is selected to provide Web services according to the complexity of a transaction processing scenario; A database connection pool supporting multiple types of databases and a file storage interface are built in the data layer to realize uploading and downloading of files in different formats in the multiple types of databases; A role-based access control model and a data service interface based on a cache mechanism are built in the service layer; An independent and extensible API is set for each application module in 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 in the display layer, and a dynamic adjustment is realized for different terminal device interfaces through responsive design; The data collected by the perception layer is transmitted to the data access layer after being encrypted by selecting a corresponding data transmission protocol through communication protocol conversion in the communication 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; when the data layer feeds back that the write pressure is large, the data access layer slows down the transmission rate of low-priority data to ensure the transmission of high-priority data; 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 simultaneously listens to the data changes in the data layer based on an event-driven mechanism and loads the latest data.

2. The method of claim 1, wherein, The corresponding API is selected to provide Web services according to the complexity of a transaction processing scenario, which comprises: For complex transaction processing scenarios, SOAP API is used for processing, otherwise RESTful API is used to provide Web services.

3. The method of claim 2, wherein, The file storage interface realizes uploading and downloading of files in different formats through RESTful API.

4. The method of claim 1, wherein, The storage strategy is dynamically selected according to the data type of the received data, which comprises: Real-time data is stored in a NoSQL database; Batch data is stored in a SQL database.

5. The method of claim 1, wherein, The data cache update strategy is automatically adjusted according to the database performance related information, which comprises: When the database load is high, the service layer increases the use frequency of the cache to reduce the request for directly accessing the database, and when the database load recovers, the service layer synchronizes the data in the cache to the database in batches.

6. The method of claim 1, wherein, The application layer will be large-scale data fragmentation processing, through the WebSocket batch push to the display layer, and then by the display layer according to the received data step rendering.

7. The method of claim 6, wherein, The display layer extracts the real-time data in the data received by the WebSocket from the application layer and directly pushes it to the visualization component of the web front end.

8. The method of claim 1, wherein, According to the data type and protocol characteristics of the sensing terminal, different processing is carried out, including: For non-standard protocol data packets, the edge node of the sensing layer pre-processes the data through the edge computing device, packages it into a standardized format that the system can recognize and process according to the application scenario, and then transmits it to the data layer layer by layer. For standard protocol data packets, the sensing layer directly transmits them to the data layer.

9. The method of claim 1, wherein, It also includes: A data retransmission mechanism is constructed in the sensing layer to identify network fluctuations, cache data during network fluctuations, and retransmit the cached data that has not been successfully sent after the network recovers.

Images