Monitoring platform of transformer substation

Abstract

The embodiment of the invention is suitable for the technical field of transformer substations, and provides a transformer substation monitoring platform, which comprises a business application layer, a business platform layer and a container resource layer, the business application layer is arranged on the upper layer of the monitoring platform of the transformer substation and is used for calling the interface service of the business platform layer to realize a corresponding business function when a business application runs; the business platform layer is arranged in the middle layer of the monitoring platform, adopts a cloud native micro-service architecture, and provides basic services uniformly deployed on the container resource layer and corresponding service interfaces; the container resource layer is arranged at the bottom layer of the monitoring platform and comprises a container cluster management platform and a hardware resource pool, and the container cluster management platform is used for operating the micro-service corresponding to the service function in the hardware resource pool as a container instance; the hardware resource pool is a cluster formed by host equipment providing a running environment of the container instance. By adopting the platform, the monitoring of a complex power network and large-scale data processing can be met.

Description

Technical Field

[0001] The present application belongs to the technical field of substations, and in particular, relates to a monitoring platform for substations. Background Art

[0002] In the power system, the substation monitoring platform is a key component to ensure the safety and stability of power operation, and is used to realize the daily inspection and operation and maintenance of the substation.

[0003] Among them, with the rapid development of the power industry, modern industry has become increasingly strict with indicators such as voltage, current, and power supply reliability of electric energy, and the power network has become increasingly complex, and the amount of power data generated has also gradually increased. Therefore, the monitoring platform has become a technical support for the safe and efficient operation of the power industry.

[0004] However, traditional monitoring platforms may face performance bottlenecks and scalability challenges when facing complex power networks and large-scale data processing. With the construction of new power systems, the availability requirements for substation monitoring systems are becoming increasingly higher. In other words, traditional monitoring platforms can no longer meet the needs. Summary of the invention

[0005] The embodiment of the present application provides a monitoring platform for a substation, which can solve the problem that traditional monitoring platforms can no longer meet the needs of complex power networks and large-scale data processing.

[0006] In a first aspect, an embodiment of the present application provides a monitoring platform for a substation, including: a business application layer, a business platform layer, and a container resource layer;

[0007] The business application layer is set up on the upper layer of the substation monitoring platform to provide business applications and call the interface service of the business platform layer to implement the corresponding business functions when the business application is running;

[0008] The business platform layer is set in the middle layer of the monitoring platform. It adopts the cloud-native microservice architecture and provides the basic modules required for the operation of business applications. The basic modules at least include modules that provide interface services. The interface services are uniformly deployed on the service interfaces corresponding to the basic services on the container resource layer.

[0009] The container resource layer is set at the bottom layer of the monitoring platform, including the container cluster management platform and the hardware resource pool. The container cluster management platform is used to manage containerized business applications; management includes running the microservices corresponding to the business functions in the hardware resource pool as container instances; the hardware resource pool includes a cluster composed of host devices corresponding to each container node, which is used to provide the operating environment of the container instance; the host device includes the device that interacts with the hardware facilities of the substation.

[0010] Compared with the prior art, the beneficial effects of the embodiments of the present application are as follows: the monitoring platform of the substation provided by the embodiment is divided into a business application layer, a business platform layer and a container resource layer. Specifically, the business application layer is arranged at the upper layer of the substation monitoring platform, and is used to provide business applications, and when the business application is running, the interface service of the business platform layer is called to implement the corresponding business functions. A cloud-native microservice architecture is adopted to provide the basic modules required for the operation of business applications. Specifically, the basic module includes at least an interface service module that provides interface services, and the interface services are uniformly deployed on the service interfaces corresponding to the basic services on the container resource layer. Therefore, when the business application is running, it can be run in the container resource layer by calling the service interface on the business platform layer. Among them, since the business application is in the business application layer, the interface to be called is in the business platform layer. That is, the coupling between the business application and the corresponding interface is low, which can make the monitoring platform highly customizable and realize the diversification of business applications. And, the container resource layer is set at the bottom layer of the substation monitoring platform and includes a container cluster management platform and a hardware resource pool. The container cluster management platform is used to manage containerized business applications; management includes running the microservices corresponding to the business functions in the hardware resource pool as container instances; the hardware resource pool includes a cluster composed of host devices corresponding to each container node, which is used to provide an operating environment for the container instance; the host device includes a device that interacts with the hardware facilities of the substation. That is, the container instance corresponding to the business application will run in the container resource layer. Based on this, according to the above three-level settings, the monitoring platform of the substation can decouple the business application from the container resource layer so that the business application can have a unified container resource layer. Furthermore, the business application layer and the business platform layer only need to care about the logical implementation of the business function, without caring about the underlying mechanisms such as data collection and information interaction between devices, so as to improve the development efficiency of business applications and the maintainability of the system to meet the monitoring of complex power networks and large-scale data processing. Moreover, in the container resource layer, through the container cluster technology, the host devices corresponding to each container node can integrate and control each container node, which can not only realize the unified management of the hardware resources of the host device, but also improve the utilization, scalability and availability of each host device. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0012] Figure 1 A schematic diagram of the structure of a monitoring platform for a substation provided in an embodiment of the present application is shown;

[0013] Figure 2 The diagram is a schematic diagram of the architecture of the container resource layer 30 in a monitoring platform of a substation. DETAILED DESCRIPTION

[0014] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0015] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, wholes, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.

[0016] It should be noted that the information collection process (such as face image collection process, fingerprint information collection process, etc.) / feature extraction process involved in this application is performed with the user's knowledge and permission, that is, the information collection process / feature extraction process complies with the requirements of laws and regulations and does not constitute an act that harms the public interest.

[0017] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.

[0018] In the power system, the substation monitoring platform is a key component to ensure the safety and stability of power operation, and is used to realize the daily inspection and operation and maintenance of the substation.

[0019] Among them, with the rapid development of the power industry, modern industry has become increasingly strict with indicators such as voltage, current, and power supply reliability of electric energy, and the power network has become increasingly complex, and the amount of power data generated has also gradually increased. Therefore, the monitoring platform has become a technical support for the safe and efficient operation of the power industry.

[0020] However, traditional monitoring platforms may face performance bottlenecks and scalability challenges when facing complex power networks and large-scale data processing. With the construction of new power systems, the availability requirements for substation monitoring systems are becoming increasingly higher. In other words, traditional monitoring platforms can no longer meet the needs.

[0021] Based on this, in order to break the performance bottleneck of the traditional monitoring platform and achieve scalability, an embodiment of the present application provides a monitoring platform for a substation.

[0022] See also Figure 1 , Figure 1 The schematic diagram of the structure of a monitoring platform for a substation provided in an embodiment of the present application is shown. The monitoring platform for a substation includes: a business application layer 10, a business platform layer 20 and a container resource layer 30.

[0023] The business application layer 10 is arranged at the upper layer of the monitoring platform of the substation, and is used to provide business applications, and when the business applications are running, the interface services of the business platform layer 20 are called to implement corresponding business functions.

[0024] In one embodiment, the business application may be a local autonomous business application related to the substation field. Exemplarily, the business application includes but is not limited to panoramic monitoring, operation control, intelligent error prevention, intelligent alarm, and intelligent operation and maintenance, etc., which are not limited to this.

[0025] In another embodiment, the business application layer 10 may also include cloud-edge collaborative business applications. The cloud-edge collaborative business application refers to the efficient collaboration of business processes within the enterprise or between the enterprise and its partners through information technology to improve the production efficiency and management efficiency of the enterprise, thereby supporting the rapid development of the enterprise.

[0026] Exemplarily, cloud-edge collaborative business applications include, but are not limited to, telecontrol, online monitoring, information security, PDC, and metering applications, without limitation.

[0027] It should be noted that cloud-edge collaborative business applications can not only involve cooperation between departments within the enterprise, but also include collaboration with external partners, aiming to meet needs through sharing information and resources. Furthermore, based on cloud-edge collaborative business applications, the scalability and diversification of business applications can be improved.

[0028] In one embodiment, the interface service is used to provide an interface for a business application to run. When a business application runs, it is necessary to call a corresponding service interface from the interface service to implement a certain business function.

[0029] Among them, the service interface can be used for business applications and monitoring platforms, or for transmitting, sharing and interacting with external systems for data and information. Among them, one business application can correspond to multiple service interfaces to realize different business functions.

[0030] The business platform layer 20 is set in the middle layer of the monitoring platform and adopts a cloud-native microservice architecture to provide the basic modules required for the operation of business applications; the basic modules include at least an interface service module 201 that provides interface services, and the interface services are uniformly deployed on the service interfaces corresponding to the basic services on the container resource layer 30.

[0031] In one embodiment, the above-mentioned interface service has been explained in the business application layer 10 and will not be described again. It should be noted that microservices is a software architecture style that divides a large business application into a group of small, autonomous and loosely coupled services. Each microservice is responsible for performing specific business functions and collaborates with each other through lightweight communication mechanisms (such as HTTP). Each microservice can be independently developed, deployed and expanded, making business applications more flexible, scalable and maintainable. In this example, a cloud-native microservice architecture is used to provide the basic modules required for the runtime of business applications.

[0032] Among them, since the interface service is uniformly deployed on the service interface corresponding to the basic service on the container resource layer 30, when the business platform layer 10 calls the corresponding service interface to implement the business function, the container resource layer 30 can run the microservice corresponding to the business function in the container resource layer 30 as a container instance.

[0033] Among them, containers are a virtualization technology that allows business applications and all their runtime environments (such as libraries, configuration files, etc.) to be packaged into an independent, standardized unit. Containers use the kernel of the host operating system at runtime, making them more lightweight and efficient than traditional virtual machines.

[0034] Based on the above description, in this embodiment, each microservice corresponding to the above business application can use container technology to instantiate the microservice into a container instance for running in the container resource layer 30. Among them, the container image of the business application needs to be built in the container resource layer 30 to ensure that the container image contains all the components and configurations required for the operation of the business functions, so that it can realize the operation of the container instance in the container resource layer 30. In addition, the microservice adopts containerized deployment, and the high availability characteristics of the service can also be achieved through multi-instance redundancy and container migration self-recovery mechanisms.

[0035] Specifically, the monitoring platform can pre-combine kubernetes (k8s, managing containerized applications on multiple host devices in the cloud platform) technology and Docker (virtualization technology based on the operating system level, packaging business applications and their dependencies as container instances) technology to provide a unified container management interface (i.e., provide a unified interface service) for the microservices corresponding to the business applications. Furthermore, the number of container instances can be easily adjusted to achieve high availability and scalability of business applications.

[0036] Among them, the container instance generated based on Docker technology can run in any environment that supports Docker. In addition, the container instances are isolated from each other and can transmit information to each other through specific channels. That is, when the above container instance is generated using Docker technology, the container resource layer 30 can also enable the container instance to run in a lightweight, secure, and portable isolated environment.

[0037] It should be noted that since the business application is in the business application layer 10, the service interface to be called is in the business platform layer 20. That is, the coupling between the business application and the corresponding interface is relatively low, which can make the monitoring platform highly customizable and realize the diversification of business applications.

[0038] As a specific example, the interface service module 201 may include units such as a service bus and a message bus. Among them, the service bus, as a service hub system, can provide a unified service interface (i.e., the above-mentioned service interface) to realize functions such as unified management of microservices, protocol conversion, and data format conversion. And, the message bus is used to transmit messages. Specifically, the interface service module 201 can monitor messages sent by business applications (for example, interface call requests) through the message bus to determine the business functions that the business application needs to implement, or the service interface that needs to be called.

[0039] In one embodiment, the container resource layer 30 includes a hardware resource pool 310, which is a cluster of host devices corresponding to multiple container nodes. Through the above service interface, the container resource layer 30 can run the microservices corresponding to the business functions on each host device in the hardware resource pool 310 as container instances.

[0040] As an example, the business platform layer 20 may also include: a data center module 202 , a basic service module 203 and a middleware module 204 .

[0041] The data center module 202 is used to operate the data during the operation of the business application; the operation includes at least one of data collection, data processing, data management, data reading and writing, and data visualization.

[0042] The data include but are not limited to the electric energy data of each equipment in the substation, such as voltage and current, and may also include non-electric energy data, such as alarm information and maintenance information, without limitation.

[0043] In one embodiment, data collection can be transmitted through the middleware module 204. Data processing includes but is not limited to deduplication, removal of erroneous data, classification and other processing. Data management is used to standardize the feature composition, constraint inspection rules, and coding rules of various types of data, and formulate, publish, review, and revise data standards in accordance with standardized management processes. Data reading and writing is used to write various types of data into the database, or read corresponding data from the database. Data visualization is to visualize the data for user observation and realize the monitoring of the substation.

[0044] The basic service module 203 is used to deploy basic services on the container resource layer 30 .

[0045] The host device may be a server, or a tablet computer, laptop or other electronic device, without limitation. The above basic services include but are not limited to model management, graphics services, basic communications, alarm services, log services, artificial intelligence engines, etc., without limitation.

[0046] Exemplarily, model management can be used to provide data services in Json or Stl format corresponding to model standard files. Image services can be used to provide data services for graphic information, including but not limited to SVG images or vector graphics. Basic communications can be used to provide communication between various modules of the business platform layer 20. The alarm service can be used to generate and publish corresponding alarm messages based on preset alarm rules and data from the data center. The log service can be used to record the logs of the monitoring platform and provide services such as log collection, storage, processing, retrieval analysis, consumption and delivery. The artificial intelligence engine is a software system or platform with "self-learning and self-evolution" capabilities, which can realize data analysis, decision-making and prediction by simulating human intelligent behavior.

[0047] The middleware module 204 is used to provide a message transmission mechanism for the interface service module 201, the data center module 202 and the basic service module 203. The middleware module 204 may be formed by units such as a database, a file storage, a message middleware, a service gateway, a security component, and a cluster management component.

[0048] The database includes but is not limited to different types of databases such as relational databases, real-time databases, time series databases, etc. For example, MySQL databases, Oracle databases, and ACCESS databases, which are not limited.

[0049] Specifically, a relational database stores data in the format of a table with rows and columns. A real-time database is a database that archives and stores data in real time. A time series database is a database that specializes in managing time series data, that is, a database of data with time tags.

[0050] And, the above-mentioned file storage can be to store data in the form of files on a storage medium rather than a unit of a database. The above-mentioned message middleware can provide synchronous or asynchronous message transmission for business applications in a network environment based on queue and message passing technology. The service gateway can provide a security architecture for accessing the database. The security component is a component that is set for access security to prevent external applications from over-consuming internal resources. The cluster management component is used to uniformly manage and coordinate a cluster (composed of multiple computing resources, such as physical machines, virtual machines or cloud servers) to provide high availability, elasticity and scalability services. The business platform layer 20 can manage the cluster corresponding to the hardware resource pool 310 according to the above-mentioned cluster management component. For example, add or delete the host device corresponding to the container node.

[0051] To sum up, the above content is an explanation of the business platform layer 20. Based on the above explanation, it can be seen that the monitoring platform decouples the business application from the container resource layer 30, so that the business application layer 10 and the business platform layer 20 only need to care about the logical implementation of the business functions, without having to care about the underlying mechanisms such as data collection and information interaction between devices, thereby improving the development efficiency of business applications and the maintainability of the system.

[0052] The container resource layer 30 is arranged at the bottom layer of the monitoring platform, and includes a container cluster management platform 300 and a hardware resource pool 310. The container cluster management platform 300 is used to manage containerized business applications; management includes running the microservices corresponding to the business functions in the hardware resource pool 310 as container instances; the hardware resource pool 310 includes a cluster composed of host devices corresponding to each container node, which is used to provide an operating environment for the container instance; the host device includes a device that interacts with the hardware facilities of the substation.

[0053] In one embodiment, one of the above host devices may correspond to one virtual container node, and the collection of each container node is the above cluster. Figure 2 , Figure 2 This is a schematic diagram of the architecture of the container resource layer in the substation monitoring platform. Figure 2 The three server nodes in the figure can be considered as container nodes corresponding to the host devices respectively. A collection of multiple container nodes is a cluster. Also, the monitoring workstation can be considered as a device including a business application layer 10 and a business platform layer 20, which is used to interact with the container resource layer 30 and undertake functions such as local monitoring and viewing and system management.

[0054] Among them, the container resource layer 30 can be built using k8s technology to generate a k8s cluster platform (i.e., the container resource layer 30 corresponding to the cluster). The upper-level business applications can run in the container environment (each container node) and be uniformly scheduled and managed by k8s to achieve elastic scaling of cluster resources (for example, CPU resources and memory resources) and support flexible expansion and reliable operation of the business platform layer 20 and the business application layer 10.

[0055] In one embodiment, the host device includes a device that interacts with hardware facilities of the substation, and can interact with various grid devices of the substation through the spacer layer device 40. For example, it can interact with transformers, circuit breakers, combined electrical appliances, capacitors and other devices.

[0056] Among them, the interval layer equipment 40 can be a component equipment in the power system automation structure, which has the functions of carrying out protection control of primary equipment, collecting and summarizing real-time data information of this interval process layer, and promoting the operation locking function of this interval, which will not be described in detail.

[0057] Among them, multiple access protocols can be set in the spacer layer device 40 to receive data input from different power grid devices. Among them, the access protocols include but are not limited to IEC61850, IEC6103, IEC6104 and other protocols, which are not limited to this.

[0058] Among them, the management of business applications by the container cluster management platform 300 not only includes running the microservices corresponding to the business functions as container instances in the hardware resource pool 310, but also includes automated deployment, expansion and management of containerized applications, providing resource scheduling, container monitoring and other management to ensure efficient operation and elastic scaling of the containerized environment.

[0059] As a specific example, the container cluster management platform 300 includes: a container service module 301 , a network service module 302 , a storage service module 303 , an application warehouse module 304 and a container cluster management module 305 .

[0060] The container service module 301 is used to implement container deployment.

[0061] Among them, the steps of container deployment can be to select a suitable container engine and container management tools, such as Docker, k8s. Then, define the container image of the business application, including the required dependencies, environment variables and startup commands. Build the container image. For example, use Dockerfile to build the container image of the business application, ensure that the container image contains all the components and configurations required for runtime, and deploy the built container image to each container node on the container resource layer 30. Among them, after the container is deployed, the container instance can be run on each container node.

[0062] It should be noted that after the microservice is instantiated as a container instance, when the business application is running, one business function can correspond to one container instance or multiple container instances, without limitation.

[0063] In this embodiment, a business function can be set to correspond to several container instances. Then, when any container instance fails to run in the container resource layer 30 due to an external fault, the business function can be run according to other container instances corresponding to the business function, or another container instance can be started to continue running. Based on this, through the redundancy mechanism, the monitoring platform can be more resistant to external faults, the fault tolerance of the microservices corresponding to the business function can be improved, and the continuous and stable operation of the monitoring platform can be ensured.

[0064] Among them, starting another container instance can restart the container instance corresponding to the business function to continue running.

[0065] The network service module 302 is used to realize the internal interaction between each container node and the interaction with the external network.

[0066] The network service module 302 includes a service module for interaction within the cluster and a service module for interaction with an external network, which is not limited. That is, the container node running the container instance can interact with other container nodes or power grid devices through the network service module 302.

[0067] As an example, in order to ensure the security of internal and external interactions, the network service module 302 may include a network security management unit for isolating the interactions between container nodes and isolating the interactions between container nodes and external networks using preset isolation rules.

[0068] The isolation rule includes at least one of identity authentication and access whitelist.

[0069] In one embodiment, the above-mentioned identity authentication is to authenticate the identity of the access to the business application or container node; and the access whitelist can be set in advance by the staff, which can not only set the users who can access, but also set the permissions of the users who access. Furthermore, through the above-mentioned isolation rules, the interaction between each container node is isolated, and the interaction between the container node and the external network is isolated, which can prevent abnormal interaction between container nodes and prevent external applications from over-consuming internal data resources.

[0070] The storage service module 303 is used to redundantly store the monitoring data of the substation using multiple container nodes.

[0071] The monitoring data may be the electric energy data described above, or may be non-electric energy data, which is not limited. The redundant storage of the monitoring data may be performed by a host device corresponding to the container node, storing the monitoring data in a hard disk.

[0072] In one embodiment, the container resource layer 30 can use a strong consistency redundancy protocol to control the host devices corresponding to multiple container nodes and perform redundant storage of monitoring data. Furthermore, when a hard disk of a host device fails, the fault can be self-healed based on the monitoring data stored in the remaining host devices, thereby improving the cluster of container nodes in the face of various challenges, and still maintaining a high degree of reliability, ensuring the stable operation of business applications.

[0073] The application warehouse 304 is used to store and manage container images of business applications.

[0074] The container image has been explained above and will not be described again. It should be noted that since the application warehouse stores the container image of the business application, and the container image is also described above, it includes the required dependencies, environment variables and startup commands.

[0075] Based on this, before running the container instance, the monitoring platform can also run the business application in the container image in the virtual environment to determine whether there is a fault in the operation of the business application. Furthermore, when it is determined that no fault occurs after running the business application in the container image, it can be considered that the main body file of the business application corresponding to the container image has not been tampered with, so that the container instance corresponding to the business application will not crash when running. Otherwise, when a fault occurs, it can be considered that the main body file of the business application corresponding to the container image may be tampered with, and the operation of the business application can be terminated to ensure the stable and reliable operation of the monitoring platform.

[0076] As an example, the application warehouse 304 includes an application security management unit for performing security checks on business applications and integrity checks on container images of business applications.

[0077] In one embodiment, the security detection includes at least one of intrusion detection, privilege escalation detection and key file detection; the integrity detection includes at least one of digital signature detection and vulnerability scanning detection.

[0078] Among them, the microservices corresponding to the business functions run by the business application have been instantiated as container instances. Therefore, the container resource layer 30 can complete the security detection of the above business application by security detection of the container instance.

[0079] In one embodiment, intrusion detection is to monitor the network without affecting network performance, thereby providing real-time protection against internal attacks, external attacks and misoperation. Privilege escalation detection refers to the use of technical means to check whether there are security vulnerabilities or configuration errors that may lead to privilege escalation. Key file detection refers to the ability to detect tampering of key data and support backup and recovery.

[0080] And, digital signature detection is a security mechanism used to verify the authenticity, integrity and identity of the sender of a digital signature. Among them, digital signatures can ensure that information has not been tampered with during transmission through encryption technology, thereby maintaining the integrity of data. Vulnerability scanning detection is used to automatically detect security vulnerabilities and weaknesses in computer systems, network devices, applications, and websites.

[0081] In this embodiment, by implementing the above security mechanism on the container image in the container resource layer 30, the robustness of the monitoring platform can be ensured. In terms of the main body of the business application, potential security threats are monitored and prevented through intrusion detection, privilege escalation detection, and key file detection. In terms of container images, digital signature detection and vulnerability scanning detection are used to ensure the integrity of the image.

[0082] The container cluster management module 305 is used to implement lifecycle management of container nodes; lifecycle management at least includes load balancing management.

[0083] The load balancing management may be to manage the load resources of the host device corresponding to each container node so as to balance the available resource margins of each host device.

[0084] In one embodiment, the above-mentioned lifecycle management may also include security monitoring, alarm, fault self-healing, upgrade and other management of the host device corresponding to each container node, which is not limited to this.

[0085] As an example, the container cluster management module 305 further includes a container cluster resource allocation unit, which is used to control the running container instances corresponding to the running business applications according to the resources on each container node.

[0086] In one embodiment, the above resources include but are not limited to the CPU, memory and other resources of the host device. Among them, controlling the running container instance can be to reduce the number of running container instances or exit the running business application, which is not limited.

[0087] In a specific embodiment, the container cluster resource allocation unit includes a container cluster resource allocation sub-unit, which is used to control the running container instance according to the resource consumption required by each running business application and the business level corresponding to the business function when the resource margin at the current moment is less than the safety resource margin.

[0088] In one embodiment, the resource margin at the current moment is the resource that each container node can still use, which is the sum of the resources that all container nodes can use. The security resource margin can be set according to the actual situation and is not limited to this. And, the resource consumption is the resource required by the host device to support the running business application. Generally, the resources required for different business applications to run are not the same.

[0089] It is understandable that when the resource margin is greater than or equal to the safe resource margin, it can be considered that each container node of the virtualized container cluster has sufficient resources to run the above-mentioned running container instance. Therefore, in this scenario, there is no need to control the running container instance.

[0090] In one embodiment, when the resource margin includes the CPU margin and the memory margin, when any margin is less than the preset safety resource margin, it can be considered that the host devices corresponding to all container nodes do not have much available resources. Therefore, it is necessary to control the running container instances to maintain the stable operation of the cluster.

[0091] Among them, business applications can usually realize multiple business functions. However, the realization of each business function is of great significance to the monitoring of the substation. Therefore, the business level corresponding to each business function can also be pre-set to control the running container instance based on the business level and the resource consumption required by each running business application.

[0092] As a specific example, the container cluster resource allocation subunit can manage the target container instances corresponding to the running business applications whose business levels are lower than the preset level until the resource margin is greater than or equal to the safety resource margin; management includes reducing the number of target container instances, or exiting the running business applications.

[0093] The service level corresponding to each container instance can be preset. Specifically, the container instance corresponds to the service function of the service application, so the service level corresponding to each service function can be preset. The above preset levels can be set according to actual conditions and are not limited to this.

[0094] Furthermore, the service level can be represented by important, medium, unimportant, or by numbers. For example, it can be represented by numbers such as 1, 2, 3, 4, 5, 6, 7, etc. The larger the number, the higher the service level. For example, the preset level can be 3.

[0095] As an example, the service level of platform basic services can be 7, the service level of monitoring and control services can be 6, the service level of error prevention services can be 5, the service level of alarm services can be 4, the service level of auxiliary control services can be 3, the service level of operation and maintenance services can be 2, and the service level of other services can be 1.

[0096] It should be added that the target container instance is the container instance that needs to be managed, and the resource margin is greater than or equal to the safety resource margin is the goal to be achieved after management. In another embodiment, since there may be many business applications running, there are many target container instances that need to be managed. In addition, it has been explained above that there are multiple container instances corresponding to one business function.

[0097] Based on this, in order to reduce the number of running target container instances that need to be exited and to retain as many running business applications as possible, you can first exit the target container instances corresponding to the running business applications with the largest resource consumption based on the resource consumption required by each running business application. For example, make the number of its target container instances only 1. That is, there is only 1 target container instance corresponding to the running business application in the end. Then, when the resource margin is still less than the safe resource margin, exit the target container instances corresponding to other running business applications in turn according to resource consumption until the resource margin is greater than or equal to the safe resource margin.

[0098] It should be added that when the resource margin is still less than the safe resource margin, the running business applications can be exited in sequence based on resource consumption again. That is, the running business applications will no longer be run at this time, and the number of corresponding target container instances is 0.

[0099] Based on this, the above method is used to control the load balancing of the virtualized container cluster, which can ensure the stability and reliability of the core business functions in the resource-constrained virtualized container cluster. In addition, based on the business level of the business function, the target container instance corresponding to the business function below the preset level is controlled, which can effectively reduce the resource occupation of non-core business functions and ensure the operation of core business functions. In addition, when managing the target container instance, the running business applications can be retained as much as possible, thereby improving the robustness and business continuity of the entire monitoring platform.

[0100] To summarize the above description, the monitoring platform of the substation provided in this embodiment is divided into a business application layer, a business platform layer and a container resource layer. Specifically, the business application layer is arranged at the upper layer of the substation monitoring platform, and is used to provide business applications, and when the business application is running, the interface service of the business platform layer is called to implement the corresponding business functions. A cloud-native microservice architecture is adopted to provide the basic modules required for the operation of business applications. Specifically, the basic module includes at least an interface service module that provides interface services, and the interface services are uniformly deployed on the service interfaces corresponding to the basic services on the container resource layer. Therefore, when the business application is running, it can be run in the container resource layer by calling the service interface on the business platform layer. Among them, since the business application is in the business application layer, the interface to be called is in the business platform layer. That is, the coupling between the business application and the corresponding interface is low, which can make the monitoring platform highly customizable and realize the diversification of business applications. And, the container resource layer is set at the bottom layer of the substation monitoring platform and includes a container cluster management platform and a hardware resource pool. The container cluster management platform is used to manage containerized business applications; management includes running the microservices corresponding to the business functions in the hardware resource pool as container instances; the hardware resource pool includes a cluster composed of host devices corresponding to each container node, which is used to provide an operating environment for the container instance; the host device includes a device that interacts with the hardware facilities of the substation. That is, the container instance corresponding to the business application will run in the container resource layer. Based on this, according to the above three-level settings, the monitoring platform of the substation can decouple the business application from the container resource layer so that the business application can have a unified container resource layer. Furthermore, the business application layer and the business platform layer only need to care about the logical implementation of the business function, without caring about the underlying mechanisms such as data collection and information interaction between devices, so as to improve the development efficiency of business applications and the maintainability of the system to meet the monitoring of complex power networks and large-scale data processing. Moreover, in the container resource layer, through the container cluster technology, the host devices corresponding to each container node can integrate and control each container node, which can not only realize the unified management of the hardware resources of the host device, but also improve the utilization, scalability and availability of each host device.

[0101] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A monitoring platform for a substation, characterized in that: include: Business application layer, business platform layer and container resource layer; The business application layer is arranged on the upper layer of the monitoring platform of the substation, and is used to provide business applications, and when the business application is running, the interface service of the business platform layer is called to realize the corresponding business function; The business platform layer is arranged in the middle layer of the monitoring platform, adopts a cloud-native microservice architecture, and provides the basic modules required for the operation of the business application; The basic module at least includes an interface service module that provides the interface service, and the interface service is uniformly deployed on the service interface corresponding to the basic service on the container resource layer; The container resource layer is arranged at the bottom layer of the monitoring platform, and includes a container cluster management platform and a hardware resource pool. The container cluster management platform is used to manage the containerized business applications; the management includes running the microservices corresponding to the business functions in the hardware resource pool as container instances; the hardware resource pool includes a cluster composed of host devices corresponding to each container node, which is used to provide an operating environment for the container instance; the host device includes a device that interacts with the hardware facilities of the substation.

2. The monitoring platform according to claim 1, characterized in that: The business platform layer also includes: a data center module, a basic service module and a middleware module; The data center module is used to operate the data when the business application is running; the operation includes at least one of data collection, data processing, data management, data reading and writing, and data visualization; The basic service module is used to deploy basic services on the container resource layer; The middleware module is used to provide a message transmission mechanism for the interface service module, the data center module and the basic service module.

3. The monitoring platform according to claim 1, characterized in that: The container cluster management platform includes: a container service module, a network service module, a storage service module, an application warehouse module and a container cluster management module; The container service module is used to implement container deployment; The network service module is used to realize internal interaction between the container nodes and interaction with the external network; The storage service module is used to redundantly store the monitoring data of the substation using a plurality of the container nodes; The application warehouse is used to store and manage the container images of the business applications; The container cluster management module is used to implement lifecycle management of the container nodes; the lifecycle management at least includes load balancing management.

4. The monitoring platform according to claim 3, characterized in that: The network service module includes a network security management unit; The network security management unit is used to isolate the interaction between each of the container nodes and isolate the interaction between the container node and the external network by using a preset isolation rule; The isolation rule includes at least one of identity authentication and access whitelist.

5. The monitoring platform according to claim 3, characterized in that: The application warehouse includes an application security management unit; The application security management unit is used to perform security detection on the business application and integrity detection on the container image of the business application.

6. The monitoring platform according to claim 5, characterized in that: The security detection includes at least one of intrusion detection, privilege escalation detection and key file detection; the integrity detection includes at least one of digital signature detection and vulnerability scanning detection.

7. The monitoring platform according to claim 3, characterized in that: The container cluster management module also includes a container cluster resource allocation unit; The container cluster resource allocation unit is used to control the running container instances corresponding to the running business applications according to the resources on each of the container nodes.

8. The monitoring platform according to claim 7, characterized in that: The container cluster resource allocation unit includes a container cluster resource allocation subunit; The container cluster resource allocation subunit is used to control the running container instance according to the resource consumption required for each running business application and the business level corresponding to the business function when the resource margin at the current moment is less than the safety resource margin.

9. The monitoring platform according to claim 8, characterized in that: The method of controlling the running container instance includes: The target container instance corresponding to the running business application whose business level is lower than the preset level is managed until the resource margin is greater than or equal to the safety resource margin; the management includes reducing the number of the target container instances, or exiting the running business application.

10. The monitoring platform according to any one of claims 1 to 9, characterized in that: There are several container instances corresponding to one business function. When one container instance fails to run, the business function is run according to other container instances corresponding to the business function, or another container instance is started to continue running.

Images