A method and device for virtualizing and packaging relay protection resources based on cloud platform

Abstract

The present application belongs to the field of relay protection technology, and discloses a method and device for virtualizing and packaging relay protection resources based on a cloud platform, the method comprising: obtaining relay protection entity resources to be packaged of a preset service type; functionally packaging the relay protection entity resources to obtain relay protection virtual resources of a preset service type; connecting the relay protection virtual resources to a cloud service platform through a preset service adapter, and the relay protection virtual resources and the cloud service platform perform data interaction to provide relay protection services of a preset service type. The present application can achieve the effect of sharing and reusing the underlying foundation on which the relay protection function depends.

Description

Technical Field

[0001] The present application relates to the field of relay protection technology, and in particular to a cloud platform-based relay protection resource virtualization packaging method and device. Background Art

[0002] Relay protection is an important measure to detect faults or abnormal conditions in the power system, thereby issuing alarm signals, or directly isolating and removing the faulty part. After the development of electromechanical, rectifier, transistor and integrated circuit types, power system relay protection has now developed to the microcomputer protection stage. Microcomputer relay protection refers to relay protection based on intelligent devices with complex microprocessors.

[0003] With the rapid development of the electric power industry, the traditional power calculation model can no longer meet the growing needs of power data processing, and the traditional power grid needs to be digitally transformed. However, in the current digital power grid implementation process, due to the differences in communication protocols and interfaces of relay protection intelligent devices from different manufacturers, models and periods, the data has strong heterogeneity; and there are many commonly used relay protection systems, such as protection information systems, setting calculation systems, etc. Each relay protection system is usually developed by multiple manufacturers, and each system has a different construction model for the same data, which makes data interaction between systems difficult and relay protection functions cannot be dynamically reused. Therefore, there are data barriers in the implementation of relay protection digital power grids.

[0004] In summary, the existing technology has the problem that the underlying infrastructure on which the relay protection function relies is difficult to share and reuse. Summary of the invention

[0005] The present application provides a cloud platform-based relay protection resource virtualization packaging method, device, computer equipment and computer-readable storage medium, which can realize the shared reuse of the underlying foundation on which the relay protection function depends.

[0006] In a first aspect, an embodiment of the present application provides a method for virtualizing and packaging relay protection resources based on a cloud platform, the method comprising:

[0007] Get the relay protection entity resource to be encapsulated of the preset service type;

[0008] Functionally encapsulate the relay protection entity resources to obtain relay protection virtual resources of preset service types;

[0009] The relay protection virtual resources are connected to the cloud service platform through a preset service adapter, and the relay protection virtual resources interact with the cloud service platform for data to provide relay protection services of preset service types.

[0010] In some implementations, obtaining a relay protection entity resource to be packaged of a preset service type includes:

[0011] receiving an encapsulation instruction carrying preset service type information, and determining the preset service type according to the preset service type information;

[0012] Obtaining relay protection data corresponding to preset service types from multiple current power systems, wherein the multiple power systems include a security system, a setting management system, an energy management system, and a power dispatching management system;

[0013] The relay protection data corresponding to the acquired preset service type is described uniformly to obtain the relay protection entity resources to be encapsulated of the preset service type.

[0014] In some implementations, the relay protection entity resources are functionally encapsulated to obtain relay protection virtual resources of a preset service type, including:

[0015] Encapsulate the relay protection data described uniformly in the relay protection entity resource to obtain the resource attribute information corresponding to the relay protection entity resource;

[0016] Encapsulate the information interaction mode between services of relay protection entity resources to obtain interface information, event information and data flow information corresponding to the relay protection entity resources;

[0017] According to resource attribute information, interface information, event information and data flow information, a relay protection virtual resource of a preset service type is constructed. The relay protection virtual resource is configured with available interfaces, events, data flows and resource attributes.

[0018] In some implementations, the resource attributes of the relay protection virtual resource include static attributes, dynamic attributes, and usage attributes. The relay protection data uniformly described in the relay protection entity resource is encapsulated to obtain resource attribute information corresponding to the relay protection entity resource, including:

[0019] Relay protection data corresponding to static attributes, dynamic attributes and usage attributes are respectively extracted from relay protection data uniformly described in relay protection entity resources as static attribute information, dynamic attribute information and usage attribute information;

[0020] The name, static attribute information, dynamic attribute information and usage attribute information of the relay protection entity resource are formally described using quadruple to obtain the resource attribute information corresponding to the relay protection entity resource.

[0021] In some implementations, the information interaction mode between services includes remote call, event notification and data stream; encapsulating the information interaction mode between services of the relay protection entity resource to obtain interface information, event information and data stream information corresponding to the relay protection entity resource includes:

[0022] Encapsulate the functions corresponding to the remote call of the relay protection entity resources to obtain the interface information corresponding to the relay protection entity resources;

[0023] Encapsulating the event corresponding to the event notification of the relay protection entity resource to obtain the event information corresponding to the relay protection entity resource; and,

[0024] The data request corresponding to the data stream of the relay protection entity resource is encapsulated to obtain the data stream information corresponding to the relay protection entity resource.

[0025] In some embodiments, the method further comprises:

[0026] Register, cancel, update service status and monitor real-time operation status of relay protection services;

[0027] Configure and manage each relay protection service connected to the cloud service platform;

[0028] Monitor all requests to access the relay protection service and perform current limiting protection on the relay protection service when the access volume to the relay protection service exceeds a preset threshold; and,

[0029] In response to the service call request received by the cloud service platform, a session is established and a relay protection service corresponding to the service call request is provided.

[0030] In a second aspect, an embodiment of the present application provides a cloud platform-based relay protection resource virtualization packaging device, the device comprising:

[0031] An entity resource acquisition module, used to acquire relay protection entity resources to be encapsulated of a preset service type;

[0032] A functional encapsulation module is used to functionally encapsulate relay protection entity resources to obtain relay protection virtual resources of a preset service type;

[0033] The cloud service platform access module is used to connect the relay protection virtual resources to the cloud service platform through a preset service adapter. The relay protection virtual resources interact with the cloud service platform to provide relay protection services of preset service types.

[0034] In some implementations, the service adapter includes a service registration and management module, a dynamic configuration management module, a service quality management module, and a service invocation module, wherein:

[0035] The service registration and management module is used to register, deregister, update service status and monitor the real-time operation status of relay protection services;

[0036] Dynamic configuration management module, used to configure and manage various relay protection services connected to the cloud service platform;

[0037] The service quality management module is used to monitor all requests for accessing the relay protection service and to limit the flow of the relay protection service when the access volume of the relay protection service exceeds a preset threshold;

[0038] The service calling module is used to respond to the service calling request received by the cloud service platform, establish a session and provide the relay protection service corresponding to the service calling request.

[0039] In a third aspect, an embodiment of the present application provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, a cloud platform-based relay protection resource virtualization packaging method such as any of the above embodiments is implemented.

[0040] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, a cloud platform-based relay protection resource virtualization packaging method as described in any of the above embodiments is implemented.

[0041] In summary, compared with the prior art, the technical solution provided by this application has at least the following beneficial effects:

[0042] The present application provides a method for virtualizing and packaging relay protection resources based on a cloud platform, which can obtain the corresponding relay protection entity resources to be packaged for a preset service type; by functionally packaging the relay protection entity resources, a relay protection virtual resource of a preset service type is obtained, and the relay protection virtual resource is connected to the cloud service platform through a preset service adapter, and the relay protection virtual resource interacts with the cloud service platform to provide a relay protection service of the preset service type. Among them, the relay protection entity resources can be obtained according to the service type for virtualization packaging, and the relay protection virtual resource corresponding to the service type is obtained, and the relay protection virtual resource is connected to the cloud service platform through the service adapter, so that the relay protection virtual resources of different service types can provide relay protection services to users through the cloud service platform, and users only need to access the cloud service platform with standard interfaces or events, thereby shielding the heterogeneity of relay protection resources of various manufacturers. The above method can realize the sharing and reuse of the underlying foundation on which the relay protection function depends. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figure 1A flowchart of a cloud platform-based relay protection resource virtualization packaging method provided as an exemplary embodiment of the present application.

[0044] Figure 2 A flowchart of functional packaging steps is provided for an exemplary embodiment of the present application.

[0045] Figure 3 An architectural diagram of a relay protection resource virtualization packaging method provided for an exemplary embodiment of the present application.

[0046] Figure 4 A structural diagram of the functional packaging of fault recording resources provided for yet another exemplary embodiment of the present application.

[0047] Figure 5 A timing diagram of a fault recording resource service call provided for yet another exemplary embodiment of the present application.

[0048] Figure 6 A structural diagram of a cloud platform-based relay protection resource virtualization packaging device provided as an exemplary embodiment of the present application.

[0049] Figure 7 A structural diagram of a service adapter provided for an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0050] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0051] See also Figure 1 The embodiment of the present application provides a method for virtualizing and packaging relay protection resources based on a cloud platform, which is described by taking a server as an example. The method specifically includes the following steps:

[0052] Step S1, obtaining relay protection entity resources to be packaged of a preset service type.

[0053] Among them, the relay protection entity resources to be encapsulated of the preset service type are the relevant relay protection data corresponding to the preset service type, which may include the equipment information of the relay protection device, the data collected by the relay protection device, the related information of the equipment and the data, etc.; the preset service type can be any type of relay protection service type, and the relay protection service is the relay protection function requirement in actual application, such as waveform display, constant value verification, fault archiving, etc.

[0054] Specifically, the server can obtain the equipment information of the relay protection equipment corresponding to the preset service type, the data collected by the relay protection equipment, the associated information of the equipment and data, etc. from the existing power grid systems according to the preset service type as the relay protection entity resources to be packaged.

[0055] Step S2, functionally encapsulate the relay protection physical resources to obtain relay protection virtual resources of a preset service type.

[0056] Among them, functional encapsulation includes resource attribute encapsulation and information interaction mode encapsulation of relay protection entity resources. Through functional encapsulation, the differences of multi-source heterogeneous resources of the underlying relay protection can be shielded to form a global unified virtual resource pool. Specifically, the server can functionally encapsulate the relay protection entity resources to obtain relay protection virtual resources of preset service types.

[0057] Step S3: Connect the relay protection virtual resource to the cloud service platform through a preset service adapter, and the relay protection virtual resource interacts with the cloud service platform to provide a relay protection service of a preset service type.

[0058] Since multi-system data integration was not considered at the beginning of the relay protection system design, the systems are currently independent of each other and cannot be connected. Therefore, in order to connect relay protection resources to cloud services, it is necessary to realize the interaction between relay protection resources and cloud services through service adapters after functional encapsulation. The service adapter contains several modules required for the normal operation of the cloud service platform, which communicates with the relay protection virtual resources internally and exchanges data with the cloud service platform externally.

[0059] A cloud platform-based relay protection resource virtualization packaging method provided in the above embodiment can obtain the corresponding relay protection entity resources to be packaged for the preset service type; obtain the relay protection virtual resources of the preset service type by functionally packaging the relay protection entity resources, connect the relay protection virtual resources to the cloud service platform through the preset service adapter, and the relay protection virtual resources interact with the cloud service platform to provide relay protection services of the preset service type. Among them, the relay protection entity resources can be obtained according to the service type for virtualization packaging to obtain the relay protection virtual resources corresponding to the service type, and connect the relay protection virtual resources to the cloud service platform through the service adapter, so that the relay protection virtual resources of different service types can provide relay protection services to users through the cloud service platform. Users only need to access the cloud service platform with standard interfaces or events, thereby shielding the heterogeneity of relay protection resources of various manufacturers. The above method can realize the sharing and reuse of the underlying foundation on which the relay protection function depends.

[0060] In some embodiments, step S1 specifically includes the following steps:

[0061] An encapsulation instruction carrying preset service type information is received, and the preset service type is determined according to the preset service type information.

[0062] Relay protection data corresponding to preset service types are obtained from multiple current power systems.

[0063] The relay protection data corresponding to the acquired preset service type is described uniformly to obtain the relay protection entity resources to be encapsulated of the preset service type.

[0064] Among them, the encapsulation instruction can carry one or more service type information; the current multiple power systems include but are not limited to the security system, setting management system, power dispatching management system (OMS, Outage Management System), energy management system (EMS, Energy Management System) and so on currently working in the power grid system. These systems are provided by the power grid and store the original relay protection data.

[0065] Specifically, after receiving the encapsulation instruction carrying the preset service type information, the server determines the preset service type according to the preset service type information, thereby determining which relay protection resources to be encapsulated; then, the relay protection data of the relay protection resources to be encapsulated are obtained from multiple power grid systems, and according to the service type, the attribute names of the data of different manufacturers and models obtained from multiple systems such as the security system, setting management system, OMS, EMS, etc. are analyzed and unified to obtain the relay protection entity resources to be encapsulated.

[0066] In some embodiments, see Figure 2 Step S2 is a functional packaging step, which specifically includes the following steps:

[0067] Step S21, encapsulating the relay protection data described uniformly in the relay protection entity resource to obtain resource attribute information corresponding to the relay protection entity resource.

[0068] In the specific implementation process, the resource attributes of the relay protection virtual resource include static attributes, dynamic attributes and usage attributes. The resource attributes can be used to describe the data capabilities of the relay protection resource. Step S21 specifically includes the following steps:

[0069] Relay protection data corresponding to static attributes, dynamic attributes and usage attributes are respectively extracted from the relay protection data uniformly described in the relay protection entity resources as static attribute information, dynamic attribute information and usage attribute information.

[0070] The name, static attribute information, dynamic attribute information and usage attribute information of the relay protection entity resource are formally described using quadruple to obtain the resource attribute information corresponding to the relay protection entity resource.

[0071] Specifically, the resources are formally described using quadruple to encapsulate the relay protection resources, as shown in the following formula:

[0072] P=(P name ,P static ,P dynamic ,P using )

[0073] Where: P name : The name of the relay protection entity resource, P static : Static attributes of relay protection entity resources, P dynamic : Dynamic attributes of relay protection entity resources, P using : Usage attributes of relay protection entity resources.

[0074] Step S22, encapsulating the information interaction mode between services of the relay protection entity resource to obtain the interface information, event information and data flow information corresponding to the relay protection entity resource.

[0075] In the specific implementation process, the information interaction methods between services include remote calls, event notifications and data flows.

[0076] Step S22 may include the following steps:

[0077] The functions corresponding to the remote calls of the relay protection entity resources are encapsulated to obtain the interface information corresponding to the relay protection entity resources.

[0078] Specifically, the interface is the encapsulation of the relay protection function. A relay protection function can be divided into multiple interfaces. Each interface consists of several operation methods. Each operation method has several input parameters and output parameters. The interface information is expressed as:

[0079] interface={interfaceid,interfacename,method 1 ,method 2 ,…,method n}

[0080] Among them: interfaceid is the unique identifier of the function, interfacename is the function name, method i (i=1,2,…,n) is the operation method that the interface can provide, expressed as:

[0081] method i={methodid,methodname,inparameter,outparameter}

[0082] Among them: inparameter represents the input parameter of the operation method, and outparameter represents the output parameter of the operation method.

[0083] The event corresponding to the event notification of the relay protection entity resource is encapsulated to obtain the event information corresponding to the relay protection entity resource.

[0084] Specifically, when there are some external events in the relay protection operation (for example, the external event is triggered by a power grid fault), it is necessary to actively send the event to the relay protection resource for processing when it is triggered. The encapsulation of each external event can be divided into events that can be generated by the relay protection resource and events that can be consumed. The event information is expressed as:

[0085] event={eventname, 1 ,p 1 >, 2 ,p 2 >,…, n ,p n >}

[0086] Among them: eventname represents the event name, i ,p i >(i=1,2,…,n) in a i Indicates the attribute name, p i Represents an attribute value.

[0087] The data request corresponding to the data stream of the relay protection entity resource is encapsulated to obtain the data stream information corresponding to the relay protection entity resource.

[0088] Specifically, data streams can be used to represent data requests for long connections such as video and audio. Data stream information is represented as follows:

[0089] streamdata={sdname,sdtype,sdformat,…,data}

[0090] Among them: sdname is the data stream name, sdtype is the data stream type, sdformat is the data storage format, and data is the data stream data.

[0091] Step S23, constructing a relay protection virtual resource of a preset service type according to the resource attribute information, interface information, event information and data flow information, wherein the relay protection virtual resource is configured with available interfaces, events, data flows and resource attributes. ​​​​

[0092] Specifically, the server constructs a relay protection virtual resource of a preset service type based on the resource attribute information, interface information, event information and data flow information obtained in the above steps.

[0093] In the above embodiment, the server abstracts and describes the relay protection entity resources through computer language, abstracts the available interfaces, generated events and provided data, and constructs relay protection virtual resources, which can shield the differences in the underlying relay protection multi-source heterogeneous resources through functional encapsulation to form a global unified virtual resource pool.

[0094] In some embodiments, the architecture of the cloud platform-based relay protection resource virtualization packaging method is as follows: Figure 3 As shown, the fourth layer (physical resource layer) can include the power system's security system, setting management system, EMS, OMS, etc. These systems are provided by the power system and store the most original relay protection data; the third layer (physical resource layer) can realize functional encapsulation, including resource attribute encapsulation, interface encapsulation, event encapsulation and data flow and other functional modules; the second layer (service layer encapsulation) includes various functions implemented by the service adapter, such as service registration and management, dynamic configuration management, service quality management and service call, etc. The third layer (physical resource layer) publishes services to the outside through the second layer (service layer encapsulation) to provide advanced applications to users.

[0095] In this embodiment, the method further comprises the following steps:

[0096] Register, deregister, update service status and monitor real-time operation status of relay protection services.

[0097] Specifically, the service adapter establishes a registration center to realize service registration and management. The registration center registers the address information of all relay protection services. Each registered relay protection service is automatically registered to the registration center when it is started. When the relay protection service goes offline, the registration center automatically monitors and cancels the service, and promptly displays the real-time status of the service such as connection and offline in the registration center.

[0098] At the same time, this method can also monitor the real-time operation status of all relay protection services connected to the cloud service platform through the heartbeat monitoring mechanism. For example, a heartbeat is sent to the registration center every 5 seconds. The heartbeat carries information such as the service name, service address, and service port. When the heartbeat monitoring does not receive the heartbeat packet from the service provider in time, the service will be considered unhealthy. At the same time, the registration center will also actively initiate a health check to the client service. If there is no heartbeat within 15 seconds and the health check fails, the instance is considered unhealthy. If the health check fails within 30 seconds, the service is removed.

[0099] The above method can timely discover service problems through service registration and management, and maintain monitoring of the real-time operation status of the service.

[0100] Configure and manage each relay protection service connected to the cloud service platform.

[0101] Specifically, the configuration of all services is managed in the registration center. By establishing configuration data in the same format as the relay protection service, the configuration can be changed and managed in real time and effectively through the registration center, avoiding the repackaging and restarting of the service. Taking the database connection information as an example, the main steps are as follows: according to the service name and configuration file type registered with the database connection information, a configuration management file of the service name configuration file type is added; after the configuration is added, the configuration is published through the publishing function, and after the client connects to the server, the specific database connection information can be obtained according to the identification information such as dataID and group.

[0102] Monitor all requests for accessing the relay protection service, and perform current limiting protection on the relay protection service when the access volume of the relay protection service exceeds a preset threshold.

[0103] Specifically, in order to ensure the quality of the cloud platform under the multi-service state, the cloud service is dynamically maintained according to the status of the relay protection resources, and the request address, time, query rate per second and response time of all requests are monitored. During peak traffic, the access volume of different services is checked, and the service is targeted for flow control, degradation and other control to prevent the service from becoming unstable. When a problem occurs, it is immediately possible to find out which request link caused the accident, and track it to the specific service according to the link.

[0104] In response to the service call request received by the cloud service platform, a session is established and a relay protection service corresponding to the service call request is provided.

[0105] In the above embodiment, the method can realize the automated management of virtualized encapsulated resources and platforms, dynamically adjust virtual hardware resources through automatic monitoring and optimal configuration of services, meet the needs of elastic load and massive data access, and ensure the availability, reliability and security of infrastructure services.

[0106] In some embodiments, the virtualization packaging process is described by taking the fault recording service as an example. The above method specifically includes the following steps:

[0107] First, obtain the relay protection entity resources to be encapsulated of the fault recording service.

[0108] Specifically, relevant data is determined according to the fault recording service requirements, and the relevant data includes the following hardware resources and software resources: 1. Fault recorder hardware information; 2. Fault recording waveform data; 3. Equipment information detected by the fault recorder, etc.; relevant data is obtained from each power system, and the attribute names of the obtained relevant data are unified.

[0109] Secondly, the relay protection entity resources are functionally encapsulated to obtain the relay protection virtual resources for fault recording services.

[0110] On the one hand, the resource attributes of the fault recording service are encapsulated, and the resources are formally described using four-tuples to encapsulate the fault recording resource attributes, as shown in the following formula:

[0111] P=(P name ,P static ,P dynamic ,P using )

[0112] Where:

[0113] P name : Recording data name;

[0114] P static : Equipment attributes of fault recording, including protection settings of fault-related relay protection equipment (such as protection start settings, reclosing, etc.) and parameters of protection equipment (such as primary and secondary transformation ratio of transformer, etc.);

[0115] P dynamic : Recording properties of fault recording, including fault recording information (recording data within a period of time of fault);

[0116] P using :The usage properties of the fault recording include the calculated values ​​such as fault phase, fault cause, fault distance, etc. analyzed based on the fault recording information.

[0117] On the other hand, the information interaction mode of the fault recording service is encapsulated. The fault recording service contains two functional classes: access control class (request to access recording data) and control function class (calculate basic fault information based on recording data); in addition, when a power grid fault occurs, the recording will be actively sent to the platform, so the fault recording resource can be encapsulated into two interfaces (IObjectInfo and IControl) and an event (eventFaultWave). For the structural diagram of the functional encapsulation of the fault recording resource, please refer to Figure 4 .

[0118] Finally, the relay protection virtual resources are connected to the cloud service platform through the service adapter, and the relay protection virtual resources interact with the cloud service platform to provide relay protection services for fault recording services.

[0119] The specific steps include:

[0120] (1) Service registration and management: The person requesting the fault recording function must be a registered user in the cloud service platform. The administrator can manage permissions in the service registration center, and operation requests can be viewed in the service platform.

[0121] (2) Dynamic configuration management: Platform managers can implement dynamic configuration management to manage the configuration of all services in a centralized and dynamic manner, redeploy applications and services as needed, and make configuration changes more efficient and agile.

[0122] (3) Service quality management: Platform managers can dynamically maintain the service quality of cloud services based on the status of relay protection resources.

[0123] (4) Service call: Manage the service calls in the cloud platform, timely discover the user's request for two interfaces related to fault recording (IObjectInfo and IControl) and the triggering of an event (eventFaultWave), establish a session and provide services. The fault recording resource service call sequence diagram is shown in the figure below: Figure 5 shown.

[0124] See also Figure 6 Another embodiment of the present application provides a cloud platform-based relay protection resource virtualization packaging device, the device comprising:

[0125] The entity resource acquisition module 100 is used to acquire the relay protection entity resources to be packaged of the preset service type;

[0126] The functional packaging module 200 is used to perform functional packaging on the relay protection entity resources to obtain relay protection virtual resources of a preset service type;

[0127] The cloud service platform access module 300 is used to connect the relay protection virtual resources to the cloud service platform through a preset service adapter. The relay protection virtual resources interact with the cloud service platform to provide relay protection services of a preset service type.

[0128] In some embodiments, see Figure 7 The service adapter includes a service registration and management module, a dynamic configuration management module, a service quality management module and a service call module, among which:

[0129] The service registration and management module 301 is used to register, deregister, update the service status and monitor the real-time operation status of the relay protection service;

[0130] Dynamic configuration management module 302, used to perform configuration management on each relay protection service connected to the cloud service platform;

[0131] The service quality management module 303 is used to monitor all requests for accessing the relay protection service and to perform current limiting protection on the relay protection service when the access volume of the relay protection service exceeds a preset threshold;

[0132] The service calling module 304 is used to establish a session and provide a relay protection service corresponding to the service calling request in response to the service calling request received by the cloud service platform.

[0133] For the specific limitations of the cloud-based relay protection resource virtualization packaging device, please refer to the limitations of the cloud-based relay protection resource virtualization packaging method above, which will not be repeated here. Each module in the above-mentioned cloud-based relay protection resource virtualization packaging device can be implemented in whole or in part through software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0134] An embodiment of the present application provides a computer device, which includes a processor, a memory, a network interface and a database connected through a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the processor calls the computer program in the memory, the steps of the cloud platform-based relay protection resource virtualization encapsulation method are executed as in any of the above embodiments.

[0135] An embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of the cloud platform-based relay protection resource virtualization packaging method as described in any of the above embodiments are implemented.

[0136] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0137] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0138] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims

1. A virtualization packaging method for relay protection resources based on cloud platform, It is characterized in that The method comprises: Obtaining relay protection entity resources to be packaged of a preset service type; specifically, obtaining relay protection entity resources to be packaged of a preset service type includes: receiving a packaging instruction carrying preset service type information, and determining the preset service type according to the preset service type information; respectively obtaining relay protection data corresponding to the preset service type from multiple current power systems, the multiple power systems including a security system, a setting management system, an energy management system, and a power dispatching management system; the relay protection data includes equipment information of the relay protection device and data collected by the relay protection device; uniformly describing the obtained relay protection data corresponding to the preset service type to obtain the relay protection entity resources to be packaged of the preset service type; Functionally encapsulate the relay protection entity resource to obtain the relay protection virtual resource of the preset service type; specifically, encapsulate the relay protection data described in a unified manner in the relay protection entity resource to obtain the resource attribute information corresponding to the relay protection entity resource; encapsulate the information interaction mode between services of the relay protection entity resource to obtain the interface information, event information and data flow information corresponding to the relay protection entity resource; construct the relay protection virtual resource of the preset service type according to the resource attribute information, the interface information, the event information and the data flow information, and the relay protection virtual resource is configured with the available interface, event, data flow and resource attributes; The relay protection virtual resource is connected to the cloud service platform through a preset service adapter, and the relay protection virtual resource interacts with the cloud service platform for data to provide the relay protection service of the preset service type.

2. The method according to claim 1, It is characterized in that The resource attributes of the relay protection virtual resource include static attributes, dynamic attributes and usage attributes. The encapsulation of the relay protection data uniformly described in the relay protection entity resource to obtain resource attribute information corresponding to the relay protection entity resource includes: Extracting the relay protection data corresponding to the static attribute, the dynamic attribute and the usage attribute from the relay protection data uniformly described in the relay protection entity resource as static attribute information, dynamic attribute information and usage attribute information; The name of the relay protection entity resource, the static attribute information, the dynamic attribute information and the usage attribute information are formally described using a quaternary group to obtain resource attribute information corresponding to the relay protection entity resource.

3. The method according to claim 1, It is characterized in that The information interaction mode between services includes remote call, event notification and data stream; the information interaction mode between services of the relay protection entity resource is encapsulated to obtain interface information, event information and data stream information corresponding to the relay protection entity resource, including: Encapsulating the function corresponding to the remote call of the relay protection entity resource to obtain the interface information corresponding to the relay protection entity resource; Encapsulating the event corresponding to the event notification of the relay protection entity resource to obtain the event information corresponding to the relay protection entity resource; and, The data request corresponding to the data stream of the relay protection entity resource is encapsulated to obtain the data stream information corresponding to the relay protection entity resource.

4. The method according to any one of claims 1 to 3, It is characterized in that The method further comprises: Register, deregister, update service status and monitor real-time operation status of the relay protection service; Performing configuration management on each of the relay protection services connected to the cloud service platform; monitoring all requests for accessing the relay protection service, and performing current limiting protection on the relay protection service when the access volume of the relay protection service exceeds a preset threshold; and, In response to the service call request received by the cloud service platform, a session is established and a relay protection service corresponding to the service call request is provided.

5. A cloud platform-based relay protection resource virtualization packaging device, It is characterized in that The device comprises: A physical resource acquisition module, used to acquire relay protection physical resources to be packaged of a preset service type; specifically, receiving a packaging instruction carrying preset service type information, and determining the preset service type according to the preset service type information; respectively acquiring relay protection data corresponding to the preset service type from multiple current power systems, wherein the multiple power systems include a security system, a setting management system, an energy management system, and a power dispatching management system; the relay protection data includes device information of the relay protection device and data collected by the relay protection device; uniformly describing the acquired relay protection data corresponding to the preset service type, and obtaining the relay protection physical resources to be packaged of the preset service type; A functional encapsulation module is used to functionally encapsulate the relay protection entity resource to obtain the relay protection virtual resource of the preset service type; specifically, encapsulate the relay protection data described in a unified manner in the relay protection entity resource to obtain the resource attribute information corresponding to the relay protection entity resource; encapsulate the information interaction mode between services of the relay protection entity resource to obtain the interface information, event information and data flow information corresponding to the relay protection entity resource; construct the relay protection virtual resource of the preset service type according to the resource attribute information, the interface information, the event information and the data flow information, and the relay protection virtual resource is configured with the available interface, event, data flow and resource attributes; The cloud service platform access module is used to connect the relay protection virtual resource to the cloud service platform through a preset service adapter, and the relay protection virtual resource interacts with the cloud service platform for data to provide the relay protection service of the preset service type.

6. The device according to claim 5, It is characterized in that The service adapter includes a service registration and management module, a dynamic configuration management module, a service quality management module and a service calling module, wherein: The service registration and management module is used to register, deregister, update the service status and monitor the real-time operation status of the relay protection service; The dynamic configuration management module is used to perform configuration management on each of the relay protection services connected to the cloud service platform; The service quality management module is used to monitor all requests for accessing the relay protection service and to perform current limiting protection on the relay protection service when the access volume of the relay protection service exceeds a preset threshold; The service calling module is used to establish a session and provide a relay protection service corresponding to the service calling request in response to the service calling request received by the cloud service platform.

7. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, It is characterized in that When the processor executes the computer program, the steps of the method according to any one of claims 1 to 4 are implemented.

8. A computer-readable storage medium having a computer program stored thereon, It is characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 4 are implemented.

Images